After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 512526 - "clock problem" happend when doing seek in avidemux
"clock problem" happend when doing seek in avidemux
Status: RESOLVED INCOMPLETE
Product: GStreamer
Classification: Platform
Component: dont know
0.10.12
Other All
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-01-28 10:24 UTC by jyang
Modified: 2009-01-10 22:03 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description jyang 2008-01-28 10:24:11 UTC
Please describe the problem:
I’ve added seek function in a sample player, but seems the seek function failed. The playback resumed at the same pause point.
I tried the following 2 functions, same error message. Any inputs?
    if (!gst_element_seek (player_status->demux, 1.0, GST_FORMAT_TIME, GST_SEEK_FLAG_FLUSH, GST_SEEK_TYPE_SET, time_nanoseconds,            GST_SEEK_TYPE_NONE, GST_CLOCK_TIME_NONE)) {
        g_print("Seek failed!\n");
    }

   if (!gst_element_seek_simple(player_status->demux, GST_FORMAT_TIME, GST_SEEK_FLAG_FLUSH, time_nanoseconds)) {
        g_print("Seek failed!\n");
   }

Here demux is gstreamer official "avidemux". I didn't use the "pipeline" in the first argument because it does not work. One thing to be mentioned is that I use 3rd party decoders, video/audio sink and clock. The 3rd party clock is already set to the whole pipeline.
Error message:
--------------------------------------------------------------------------
Warning: Internal GStreamer error: clock problem.  Please file a bug at http://bugzilla.gnome.org/enter_bug.cgi?product=GStreamer.


Steps to reproduce:
1. Wrote application code in sample player to link all necessary elements
2. Start the sample player, call the seek function to jump forward.



Actual results:
The playback paused with error message, after a while, the player resumed  playback at the pause point.

Expected results:
I expect the playback jump to the seek point specified by "time_nanoseconds"

Does this happen every time?
Yes

Other information:
Comment 1 Wim Taymans 2008-01-28 16:51:22 UTC
what 3rd party codecs and sinks are you using? What is the more details error message you get regarding the clock.
Comment 2 jyang 2008-01-29 03:08:18 UTC
Thanks for your reply. 
The 3rd party codecs and sinks are private. The codecs and sinks do not support seek, but they can accept the new data segment from "avidemux" and continue playback. So I do seek on "avidemux". No more details error message  regarding the clock. After the error(or warning?) message, the pipeline resumed playback. 
Can user do seek on one element "avidemux" regardless of the other following elements? Let's say the other elments can process the data afer seek on "avidemux". 
Comment 3 Tim-Philipp Müller 2008-04-06 20:28:56 UTC
If you parse the error/warning message with gst_message_parse_error or gst_message_parse_warning, what is the 'debug' string?

Could you make a GST_DEBUG=*:5 log available?
Comment 4 Jan Schmidt 2009-01-10 22:03:47 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!