Problems with Dolby Audio and typefind
neiljay at gmail.com
Fri Dec 7 03:54:39 PST 2012
> here's already an iec958 plugin, does that not handle it?
No that only supports formating AC3/DTS data into iec958 frames for
transmission to a spdif sink, not the other way around.
Ok, once I find the time I'll try putting together some patches.
On Thu, Dec 6, 2012 at 6:48 PM, Michael Smith <mlrsmith at gmail.com> wrote:
> On Thu, Dec 6, 2012 at 6:52 AM, Neil Jones <neiljay at gmail.com> wrote:
> > Hi,
> > Im having issue with typefind correctly detecting Dolby audio.
> > AC3:
> > If im using a normal big-endian ac3 file then typefind works, but if I
> > capturing AC3 from a spif input the data is little-endain and has big
> > of zeros in it (as its transported as 2 channel 48Khz 16bit PCM accross
> > spdif), typefind and aacparse fail to recognise this audio, if i manually
> > pipe this audio into my decoder (with out gstreamer) it plays it fine.
> > Should typefind / aacparse be able to deal with this data ? I had
> > writing an iec958-src component which detect the incoming data type PCM /
> > AC3/ DTS and strips out the zeros, has anyone done anything like this ?
> There's already an iec958 plugin, does that not handle it?
> I'm not sure how detectable (without a lot of false positives) that
> format is - if I'm wrong about that, implementing a typefinder for it
> sounds great.
> > EAC3:
> > I cannot get typefind to detect eac3 files correclty at all, using the
> > test sample 'eac3sample12.eac3' from dolby conformance test suite as an
> > example (I can probably upload this somewhere once i check its ok to do
> > it reports the file as:
> Probably nobody had enough sample files to implement this properly.
> You should write a patch to typefind to add an appropriate typefinder
> for this.
> gstreamer-devel mailing list
> gstreamer-devel at lists.freedesktop.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the gstreamer-devel