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 693792 - Quicktime video on trailers.apple.com is choppy at some moments
Quicktime video on trailers.apple.com is choppy at some moments
Status: RESOLVED OBSOLETE
Product: GStreamer
Classification: Platform
Component: gst-libav
1.0.2
Other Linux
: Normal normal
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2013-02-14 12:56 UTC by Peteris Krisjanis
Modified: 2013-07-17 13:41 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Peteris Krisjanis 2013-02-14 12:56:59 UTC 
OS: Fedora 18, with gstreamer1-libav-1.0.2 from RPM Fusion, and -base and -good from main repo.

1. Download Quicktime movie from trailers.apple.com (I used Totem plugin, used "play on Video player" in popup menu, and then saved a copy. It doesn't allow curl/wget downloads it seems, due of user agent propably);
2. run GST_DEBUG=*:3 totem video_you_just_saved
3. Getting tons of repeated these two lines, they repeat more often when frame skipping starts:
0:00:44.881353687  3509 0x7f7f78003190 ERROR                  libav :0:: Changing field mode (3 -> 3) between slices is not allowed
0:00:44.881385893  3509 0x7f7f78003190 ERROR                  libav :0:: decode_slice_header error

Expected behaviour: no choppy playback
Comment 1 Edward Hervey 2013-07-17 12:31:41 UTC 
Is this still an issue with current git ?

If so, Could you provide more info ?

 The URL used for example on which this can be reproduced.
Comment 2 Tim-Philipp Müller 2013-07-17 13:10:50 UTC 
This might be fixed in 1.0.7.

(could be related to bug #698649 and bug #694230)
Comment 3 Peteris Krisjanis 2013-07-17 13:37:00 UTC 
I just tried it on Fedora 18, where newest updates now includes also gstreamer1-1.0.7-1.fc18.i686 and I can't reproduce it anymore, so I can say it's fixed. Thanks guys.
Comment 4 Tim-Philipp Müller 2013-07-17 13:41:11 UTC 
Great, thanks for re-testing and confirming it's gone.