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 621973 - avidemux can't seek backward
avidemux can't seek backward
Status: RESOLVED DUPLICATE of bug 619064
Product: GStreamer
Classification: Platform
Component: gst-plugins-good
0.10.23
Other Linux
: Normal normal
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-06-18 09:17 UTC by Levente Farkas
Modified: 2010-06-29 12:13 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Levente Farkas 2010-06-18 09:17:41 UTC
assume that we record some video, then encode it to h264 with this command:
----------------------
gst-launch -e v4l2src device="/dev/video0" ! video/x-raw-yuv,width=720,height=576 ! timeoverlay  ! x264enc ! avimux ! filesink location="test.avi"                                        
----------------------
than we see back with this command:
----------------------
gst-launch filesrc location="test.avi" ! avidemux ! h264parse ! ffdec_h264 ! navseek ! xvimagesink
----------------------
then everything is working. but if we save in byte-stream mode ie:
----------------------
gst-launch -e v4l2src device="/dev/video0" ! video/x-raw-yuv,width=720,height=576 ! timeoverlay  ! x264enc byte-stream=true ! avimux ! filesink location="testbs.avi"
----------------------
then with the same command:
----------------------
gst-launch filesrc location="testbs.avi" ! avidemux ! h264parse ! ffdec_h264 ! navseek ! xvimagesink
----------------------
and try to seek backward than it's not working ie. lagging or wait or ... so not working properly.
if you need i can send a few example avi.
Comment 1 Mark Nauwelaerts 2010-06-23 08:48:11 UTC
I can't reproduce the above effect, at least not with video created as suggested.

Has this been tried with recent git (?), as there have been a few fixes that might affect timestamps (see e.g. bug #619064).
Comment 2 Levente Farkas 2010-06-23 09:40:37 UTC
that fix also fix it. thanks.
Comment 3 Tim-Philipp Müller 2010-06-29 12:13:10 UTC

*** This bug has been marked as a duplicate of bug 619064 ***