>> Looks like you need to resample audio to sample rate ac3 supports.
>
> I've just tried to convert two different Dolby E source from wav to u8, then
> ffprobe recognize them as a Dolby E stream, but it says that they're 44800Hz,
> I guess it should be 48000Hz. Perhaps there's a bug here ?
>
On 9/11/17, Mike Brown wrote:
> On Mon, Sep 11, 2017 at 09:23:36AM +0200, Fr?d?ric Busnel-Joncour wrote:
>> > Looks like you need to resample audio to sample rate ac3 supports.
>>
>> I've just tried to convert two different Dolby E source from wav to u8,
>> then ffprobe
On Mon, Sep 11, 2017 at 09:23:36AM +0200, Fr?d?ric Busnel-Joncour wrote:
> > Looks like you need to resample audio to sample rate ac3 supports.
>
> I've just tried to convert two different Dolby E source from wav to u8, then
> ffprobe recognize them as a Dolby E stream, but it says that they're
> Looks like you need to resample audio to sample rate ac3 supports.
I've just tried to convert two different Dolby E source from wav to u8, then
ffprobe recognize them as a Dolby E stream, but it says that they're 44800Hz, I
guess it should be 48000Hz. Perhaps there's a bug here ?
But I
On Sun, Sep 10, 2017 at 10:13:51AM +0200, Paul B Mahol wrote:
> On 9/10/17, Mike Brown wrote:
> > On Sat, Sep 09, 2017 at 05:24:24PM +0300, foo86 wrote:
> >> On Fri, Sep 08, 2017 at 05:08:54PM -0500, Mike Brown wrote:
> >> > On Fri, Sep 08, 2017 at 03:55:35PM +0200, Paul
On 9/10/17, Mike Brown wrote:
> On Sat, Sep 09, 2017 at 05:24:24PM +0300, foo86 wrote:
>> On Fri, Sep 08, 2017 at 05:08:54PM -0500, Mike Brown wrote:
>> > On Fri, Sep 08, 2017 at 03:55:35PM +0200, Paul B Mahol wrote:
>> > > You need to override input decoder so S302 is
On Sun, Sep 10, 2017 at 09:23:28AM +0200, Paul B Mahol wrote:
> On 9/9/17, foo86 wrote:
> > On Fri, Sep 08, 2017 at 05:08:54PM -0500, Mike Brown wrote:
> >> On Fri, Sep 08, 2017 at 03:55:35PM +0200, Paul B Mahol wrote:
> >> > You need to override input decoder so S302 is not
On Sat, Sep 09, 2017 at 05:24:24PM +0300, foo86 wrote:
> On Fri, Sep 08, 2017 at 05:08:54PM -0500, Mike Brown wrote:
> > On Fri, Sep 08, 2017 at 03:55:35PM +0200, Paul B Mahol wrote:
> > > You need to override input decoder so S302 is not used.
> >
> > Any update on how I override the s302
On 9/9/17, foo86 wrote:
> On Fri, Sep 08, 2017 at 05:08:54PM -0500, Mike Brown wrote:
>> On Fri, Sep 08, 2017 at 03:55:35PM +0200, Paul B Mahol wrote:
>> > You need to override input decoder so S302 is not used.
>>
>> Any update on how I override the s302 decoder?
>
> You
On Fri, Sep 08, 2017 at 05:08:54PM -0500, Mike Brown wrote:
> On Fri, Sep 08, 2017 at 03:55:35PM +0200, Paul B Mahol wrote:
> > You need to override input decoder so S302 is not used.
>
> Any update on how I override the s302 decoder?
You don't want to override s302m decoder, it has to be used
On 9/9/17, Mike Brown wrote:
> On Fri, Sep 08, 2017 at 03:55:35PM +0200, Paul B Mahol wrote:
>> On 9/8/17, Mike Brown wrote:
>> > On Fri, Sep 08, 2017 at 03:13:46PM +0200, Paul B Mahol wrote:
>> >> On 9/8/17, Mike Brown
On Fri, Sep 08, 2017 at 03:55:35PM +0200, Paul B Mahol wrote:
> On 9/8/17, Mike Brown wrote:
> > On Fri, Sep 08, 2017 at 03:13:46PM +0200, Paul B Mahol wrote:
> >> On 9/8/17, Mike Brown wrote:
> >> > Are you saying that it takes a version newer
On Fri, Sep 08, 2017 at 03:55:35PM +0200, Paul B Mahol wrote:
> On 9/8/17, Mike Brown wrote:
> > On Fri, Sep 08, 2017 at 03:13:46PM +0200, Paul B Mahol wrote:
> >> On 9/8/17, Mike Brown wrote:
> >> > Are you saying that it takes a version newer
On 9/8/17, Mike Brown wrote:
> On Fri, Sep 08, 2017 at 03:13:46PM +0200, Paul B Mahol wrote:
>> On 9/8/17, Mike Brown wrote:
>> > Are you saying that it takes a version newer than what I am using in
>> > order
>> > to decode Dolby-E to ac3?
>>
On Fri, Sep 08, 2017 at 03:13:46PM +0200, Paul B Mahol wrote:
> On 9/8/17, Mike Brown wrote:
> > Are you saying that it takes a version newer than what I am using in order
> > to decode Dolby-E to ac3?
>
> Yes.
Well, I have the latest available from the website
On 9/8/17, Mike Brown wrote:
> On Fri, Sep 08, 2017 at 02:30:08PM +0200, Paul B Mahol wrote:
>> On 9/8/17, Mike Brown wrote:
>> > On Fri, Sep 08, 2017 at 01:39:34PM +0200, Paul B Mahol wrote:
>> >> On 9/8/17, Mike Brown
On Fri, Sep 08, 2017 at 02:30:08PM +0200, Paul B Mahol wrote:
> On 9/8/17, Mike Brown wrote:
> > On Fri, Sep 08, 2017 at 01:39:34PM +0200, Paul B Mahol wrote:
> >> On 9/8/17, Mike Brown wrote:
> >
> > [trimmed]
> >
> >> > Why doesn't it matter?
On 9/8/17, Mike Brown wrote:
> On Fri, Sep 08, 2017 at 01:39:34PM +0200, Paul B Mahol wrote:
>> On 9/8/17, Mike Brown wrote:
>
> [trimmed]
>
>> > Why doesn't it matter?
>> >
>> > ffmpeg -i input_test.ts -map 0:1 -c:a pcm_s24le output_test.wav
On Fri, Sep 08, 2017 at 01:39:34PM +0200, Paul B Mahol wrote:
> On 9/8/17, Mike Brown wrote:
[trimmed]
> > Why doesn't it matter?
> >
> > ffmpeg -i input_test.ts -map 0:1 -c:a pcm_s24le output_test.wav
>
> You need -c:a copy here, but you may also need to override
On 9/8/17, Mike Brown wrote:
> On Fri, Sep 08, 2017 at 01:15:06PM +0200, Paul B Mahol wrote:
>> On 9/8/17, Mike Brown wrote:
>> > On Fri, Sep 08, 2017 at 09:34:50AM +0200, Paul B Mahol wrote:
>> >> On 9/8/17, Mike Brown
>
>
> > >> ffmpeg -i input.wav -c:a copy -f u8 out.u8
>
> > > ffmpeg -i - -c:a copy -f u24le - | \
>
> > > The Dolby-E is 24bit, not 8.
> >
> > Doesn't matter, your example will not work, try it.
>
> Why doesn't it matter?
>
>
When you copy a stream as-is, copying each byte individually or
On Fri, Sep 08, 2017 at 01:15:06PM +0200, Paul B Mahol wrote:
> On 9/8/17, Mike Brown wrote:
> > On Fri, Sep 08, 2017 at 09:34:50AM +0200, Paul B Mahol wrote:
> >> On 9/8/17, Mike Brown wrote:
> >> > On Fri, Sep 08, 2017 at 12:54:12AM +0200,
On 9/8/17, Mike Brown wrote:
> On Fri, Sep 08, 2017 at 09:34:50AM +0200, Paul B Mahol wrote:
>> On 9/8/17, Mike Brown wrote:
>> > On Fri, Sep 08, 2017 at 12:54:12AM +0200, Carl Eugen Hoyos wrote:
>> >> (Sorry, my knowledge of SMPTE 337M is
On Fri, Sep 08, 2017 at 09:34:50AM +0200, Paul B Mahol wrote:
> On 9/8/17, Mike Brown wrote:
> > On Fri, Sep 08, 2017 at 12:54:12AM +0200, Carl Eugen Hoyos wrote:
> >> (Sorry, my knowledge of SMPTE 337M is limited but I know that so far,
> >> this is the only "format"
On 9/8/17, Kieran O Leary wrote:
> On 8 Sep 2017 08:35, "Paul B Mahol" wrote:
>
> On 9/8/17, Mike Brown <
>
> No, you would need to copy audio to raw container, this raw container would
> be
> then detected as Dolby-E.
>
> ffmpeg -i input.wav -c:a copy
On 8 Sep 2017 08:35, "Paul B Mahol" wrote:
On 9/8/17, Mike Brown <
No, you would need to copy audio to raw container, this raw container would
be
then detected as Dolby-E.
ffmpeg -i input.wav -c:a copy -f u8 out.u8
This looks like an 8-bit format,is there a reason why 16 or
On 9/8/17, Mike Brown wrote:
> On Fri, Sep 08, 2017 at 12:54:12AM +0200, Carl Eugen Hoyos wrote:
>> (Sorry, my knowledge of SMPTE 337M is limited but I know that so far,
>> this is the only "format" for which FFmpeg supports Dolby-E, and that
>> adding support for other
2017-09-07 18:20 GMT+02:00 Frédéric Busnel-Joncour :
>> And one last question, is it possible to wrap Dolby-E stream in mov
>> or mxf container using ffmpeg without altering it in any way ?
Do you have a mov and / or mxf file containing Dolby-E so we
better understand what you
> Afaict, SMPTE 337M is a file format.
OK, thanks. I have made many search but can't find any info about it. With what
I've found, it seems to be more like a protocol (non-PCM stream transport in an
AES-3 link) than a file format ?
> Please do not top-post here, Carl Eugen
Sorry, I don't
2017-09-07 15:38 GMT+02:00 Frédéric Busnel-Joncour :
> Not sure to have well understood: can a SMPTE 337M file be in a wav
> container, or it has a specific wrap and file extension ?
Afaict, SMPTE 337M is a file format.
Please do not top-post here, Carl Eugen
Hi Carl Eugen,
Thanks for this quick reply !
Not sure to have well understood: can a SMPTE 337M file be in a wav container,
or it has a specific wrap and file extension ?
Best regards,
Fred
> 2017-09-07 15:20 GMT+02:00 Frédéric Busnel-Joncour :
>
>> I've seen that a Dolby
2017-09-07 15:20 GMT+02:00 Frédéric Busnel-Joncour :
> I've seen that a Dolby E decoder has been added to the last release of
> libavcodec.
So far, only SMPTE 337M files are supported, patch for more file types welcome!
Carl Eugen
Hi there,
First question here !
I've seen that a Dolby E decoder has been added to the last release of
libavcodec.
I'm sometimes delivered of stereo 24bit/48Khz wav file that are Dolby E encoded
streams.
Is there a way to tell ffplay to play it as Dolby E and decode it ? By default
it plays
33 matches
Mail list logo