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 137052 - [alsasink] latest cvs broken
[alsasink] latest cvs broken
Status: RESOLVED DUPLICATE of bug 134007
Product: GStreamer
Classification: Platform
Component: gst-plugins
git master
Other Linux
: Normal normal
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-03-13 12:53 UTC by Arwed v. Merkatz
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
`gst-inspect alsasink` (14.41 KB, text/plain)
2004-04-08 19:31 UTC, Chris Ness
Details

Description Arwed v. Merkatz 2004-03-13 12:53:19 UTC
With the latest changes to alsasink it doesn't work anymore, it starts to
play (with sound), but then aborts with an assertion in alsalib.
This is with alsa-lib 1.0.3a.

arwed@Otherland:~/Movies/Anime/Chrno Crusade$ gst-launch-0.8 filesrc
location=\[Anime-Keep\]_Chrno_Crusade_-_01_\[2ED6DEF9\].avi ! avidemux
name=demux ! { queue ! spider ! xvimagesink } { demux. ! queue ! spider !
audioscale ! audio/x-raw-int,rate=48000 ! alsasink device=dsp1 }
RUNNING pipeline ...
[mpeg4 @ 0x411db578]header damaged

** (process:429): WARNING **: ffdec_mpeg4: decoding error
gst-launch-0.8: pcm.c:909: snd_pcm_delay: Assertion `pcm->setup' failed.
Aborted

gdb backtrace will follow as soon as i can reproduce it with coredumps
enabled ...
Comment 1 Stephane Loeuillet 2004-03-14 02:27:59 UTC
and does it work against alsa-libs 1.0.3b ?

2004-03-13  	alsa-lib 1.0.3b released - it fixes SIGSEGV problem for
dmix plugin (when a specific GCC version is used)
Comment 2 Arwed v. Merkatz 2004-03-14 10:32:28 UTC
I don't use dmix, but i'll update my alsa version and try again.
Comment 3 Benjamin Otte (Company) 2004-03-14 14:54:13 UTC
Shouldn't the device be named hw:1 ?

(It should properly signal an error though if it can't setup that device)
Comment 4 Arwed v. Merkatz 2004-03-14 15:00:09 UTC
dsp1 is fine, it's defined in my ~/.asoundrc, and it works fine
usually. I can't reproduce the error i got above anymore, now it just
hangs after some seconds.
Comment 5 Benjamin Otte (Company) 2004-03-24 14:40:38 UTC
Couls you have a look at bug 134007 and the related alsalib bug?

I suspect it is a bug in alsalib. You could try to work with them in that bug
report.
Comment 6 Johan (not receiving bugmail) Dahlin 2004-03-25 10:40:24 UTC
Looks to me like an ffmpeg bug:

** (process:429): WARNING **: ffdec_mpeg4: decoding error
Comment 7 Arwed v. Merkatz 2004-03-31 11:36:51 UTC
Haven't been able to reproduce it after that one time.
The ffdec_mpeg4 error is normal, every ffmpeg app gives that for lots of xvid4
encoded files.
Comment 8 Chris Ness 2004-04-08 19:31:34 UTC
Created attachment 26485 [details]
`gst-inspect alsasink`
Comment 9 Chris Ness 2004-04-08 19:32:38 UTC
Hi, 

Using the FreshRPM's alsa packages here.  And I get a failure with my freshly
compiled gst-plugins alsasink (rpm package didn't come with alsasink, this might
be why).

It works fine with osssink as shown (and yes, I do have alsa installed and
working).  At least AFAIK.

[nesscg@woman nesscg]$ gst-launch filesrc location=/music/\(Verve\ Pipe\)\ The\
Freshmen.mp3 ! mad ! osssink
RUNNING pipeline ...
Caught interrupt.
Execution ended after 21 iterations (sum 4960070000 ns, average 236193809 ns,
min 11745000 ns, max 261603000 ns).
[nesscg@woman nesscg]$ gst-launch filesrc location=/music/\(Verve\ Pipe\)\ The\
Freshmen.mp3 ! mad ! alsasink
RUNNING pipeline ...
gst-launch-0.8: pcm_plug.c:882: snd_pcm_plug_hw_params: Assertion `err >= 0' failed.
Aborted


Attaching my `gst-inspect alsasink` output.
Comment 10 Ronald Bultje 2004-05-16 21:04:18 UTC
That is 

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