I still think the problem is of a gstreamer and pulseaudio combination. I've run two tests using a wav file: 1.- paplay test.wav -> pulseaudio rises to 14% cpu in my very old computer. The sound is ok. 2.- gst-launch filesrc location=test.wav ! wavparse ! audiocoert ! audioresample ! pulsesink -> pulseaudio rises to 95% cpu. No sound.
I ran pulseaudio in debug mode (-vvv) and the diference is that in the second case the log is full of lines with this sequence: (...) D: protocol-native.c: Requesting rewind due to rewrite. D: alsa-sink.c: Requested to rewind 15360 bytes. D: alsa-sink.c: Limited to 15040 bytes. D: alsa-sink.c: before: 3760 D: alsa-sink.c: after: 3760 D: alsa-sink.c: Rewound 15040 bytes. D: sink.c: Processing rewind... D: sink-input.c: Have to rewind 15040 bytes on render memblockq. D: sink-input.c: Have to rewind 27640 bytes on implementor. D: source.c: Processing rewind... (...) find attached both file logs. ** Attachment added: "pulseaudio log (paplay test.wav)" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/662337/+attachment/1701856/+files/paplay.log -- Very High CPU in pulseaudio https://bugs.launchpad.net/bugs/662337 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
