[Bug 663458] qtdemux: Does not support LPCM audio

GStreamer (bugzilla.gnome.org) bugzilla at gnome.org
Tue Jan 8 19:19:20 PST 2013


https://bugzilla.gnome.org/show_bug.cgi?id=663458
  GStreamer | gst-plugins-good | 0.10.x

Youness Alaoui <youness.alaoui> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |youness.alaoui at collabora.co
                   |                            |.uk

--- Comment #13 from Youness Alaoui <youness.alaoui at collabora.co.uk> 2013-01-09 03:19:17 UTC ---
I've added LPCM support to qtdemux so it should technically work now. See my
commits on qtdemux and qtdemux-1.0 branches here :
http://cgit.collabora.com/git/user/kakaroto/gst-plugins-good.git/log/?h=qtdemux
(based on 0.10) and
http://cgit.collabora.com/git/user/kakaroto/gst-plugins-good.git/log/?h=qtdemux-1.0
(based on master)
It will parse the sound sample description and output the right caps depending
on the format.

The issue that remains though is what Tim-Philipp reported, it's pushing 6
bytes buffers which makes the CPU go crazy both by gst-launch and pulseaudio.

>From what I could see, there is a n_samples_per_chunk, but it seems to be given
by the file itself (stbl atom), and it says 1 in the file.
I think it's somehow unrelated though, I think it's more about how each sample
is stored in the file (interleaved chunks of audio and video) and the demuxer
should be smarter than that when pushing out buffers.
I haven't looked too much into how the buffers are output yet from the demuxer,
but I would suggest we merge my patches and close this bug and clone/open a new
one about the 6 bytes buffers issue, as it's unrelated to LPCM support itself.

With my fixes, transcoding the file actually fixes the sound issue but it took
me 35 seconds to transcode the 12s audio from raw to mp3.

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.


More information about the gstreamer-bugs mailing list