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 160116 - totem won't play audio from this file, but gst-launch would
totem won't play audio from this file, but gst-launch would
Status: RESOLVED DUPLICATE of bug 160130
Product: GStreamer
Classification: Platform
Component: gst-plugins
git master
Other Linux
: Normal normal
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks: 138435
 
 
Reported: 2004-12-01 17:39 UTC by Martijn van de Streek
Modified: 2005-02-08 17:56 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10


Attachments
Screenshot showing what's wrong (92.39 KB, image/jpeg)
2004-12-01 17:42 UTC, Martijn van de Streek
Details

Description Martijn van de Streek 2004-12-01 17:39: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"
Comment 1 Martijn van de Streek 2004-12-01 17:42:50 UTC
Created attachment 34369 [details]
Screenshot showing what's wrong
Comment 2 Martijn van de Streek 2004-12-01 20:03:32 UTC
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
Comment 3 Stephane Loeuillet 2004-12-12 21:47:03 UTC
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
Comment 4 Ronald Bultje 2004-12-19 01:23:25 UTC
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.
Comment 5 Stephane Loeuillet 2004-12-19 14:20:29 UTC
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
Comment 6 Stephane Loeuillet 2004-12-19 14:32:13 UTC
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 ?
Comment 7 Ronald Bultje 2004-12-19 14:51:39 UTC
This is different from 160130. There, the screen is garbled. Here, the colors
are wrong (but the screen is OK).
Comment 8 Ronald Bultje 2005-02-08 17:56:37 UTC
Hm, you're right. Dup of 160130.

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