GNOME Bugzilla – Bug 160116
totem won't play audio from this file, but gst-launch would
Last modified: 2005-02-08 17:56:37 UTC
The Xv output of GStreamer is garbled on my screen. The colors are BGR instead of RGB, and the right side of the screen is completely garbled. I'll attach a screen-shot of "gst-launch-0.8 videotestsrc ! xvimagesink"
Created attachment 34369 [details] Screenshot showing what's wrong
I can reproduce this outside of totem with: gst-launch-0.8 -v filesrc location=mvi_0033.avi ! avidemux name=demuxer ! { queue ! jpegdec ! ffmpegcolorspace ! xvimagesink } { demuxer. ! queue ! audioconvert ! audioscale ! esdsink } (mvi_0033.avi = http://foodfight.org/fotos/2004/10-02%20Demonstratie%20tegen%20kabinetsbeleid/mvi_0033.avi, 4.3M) Removing ffmpegcolorspace makes this become #160130
using CVS of gstreamer and totem : but no audio because of : ** (totem:16929): WARNING **: could not link audio/x-raw-int, endianness=(int)1234, width=(int)8, depth=(int)8, signed=(boolean)false, rate=(int)11024, channels=(int)1, codec_data=(buffer)000001000800 and there is the following additional output on console : "Corrupt JPEG data: 416 extraneous bytes before marker 0xda" x many times the video stops shortly ---------- using your pipeline, (just replacing esdsink by alsasink), video is ok, audio is ok and i've got the following : (process:16943): GStreamer-WARNING **: Unhandled state change from PLAYING to READY (2 times) + the corrupt 416 bytes for each JPEG frame/image
I cannot reproduce the audio warning. Video works fine for me. Something's weird with his display. Let's limit this bug report solely to that.
i only have the warning when using alsasink (when the video stops shortly) when using esdsink (which uses alsa), haven't got this audio warning, audio and video are ok => my observations are a different bug, limited to alsasink
all the jpegdec warnings look like bug #152436 the BGR/RGB issue is bug #160130 the alsasink error i have is bug #161704 so, which issue remains ?
This is different from 160130. There, the screen is garbled. Here, the colors are wrong (but the screen is OK).
Hm, you're right. Dup of 160130. *** This bug has been marked as a duplicate of 160130 ***