Page 2 of 7
Re: Atmos
Posted: 07 Mar 2019, 03:44
by jeremy1234
Question that I’m sure has been beaten to death but just for my own clarification, my receiver still is saying multi-in with Atmos movies. I really don’t care about the display on the receiver but are all channels being separated the same as bitstream would be doing? I don’t really want to buy a shield just for bitstream...
Thanks!
Re: Atmos
Posted: 07 Mar 2019, 04:38
by aureldelic
davilla wrote: 06 Mar 2019, 23:10
Got it

I'll have to put on the hipboots and wade into ffmpeg to see why eac3/atmos is not getting detected for this one.
Great! So its not just me

, thanks
Re: Atmos
Posted: 07 Mar 2019, 16:27
by livefeed
davilla wrote: 06 Mar 2019, 23:10
aureldelic wrote: 06 Mar 2019, 13:13
Aquaman.2018.IMAX.2160p.iT.WEB-DL.x265.10bit.HDR.DDP5.1.Atmos-MOMA
Got it

I'll have to put on the hipboots and wade into ffmpeg to see why eac3/atmos is not getting detected for this one.
@davilla Thank you for looking into this.
Re: Atmos
Posted: 08 Mar 2019, 14:41
by cosmoxl
davilla wrote: 06 Mar 2019, 23:10
aureldelic wrote: 06 Mar 2019, 13:13
Aquaman.2018.IMAX.2160p.iT.WEB-DL.x265.10bit.HDR.DDP5.1.Atmos-MOMA
Got it

I'll have to put on the hipboots and wade into ffmpeg to see why eac3/atmos is not getting detected for this one.
So isn't ffmpeg demuxing on Shield as well? Why does it work on that platform but not tvOS?

Re: Atmos
Posted: 08 Mar 2019, 17:30
by davilla
cosmoxl wrote: 08 Mar 2019, 14:41
davilla wrote: 06 Mar 2019, 23:10
aureldelic wrote: 06 Mar 2019, 13:13
Aquaman.2018.IMAX.2160p.iT.WEB-DL.x265.10bit.HDR.DDP5.1.Atmos-MOMA
Got it

I'll have to put on the hipboots and wade into ffmpeg to see why eac3/atmos is not getting detected for this one.
So isn't ffmpeg demuxing on Shield as well? Why does it work on that platform but not tvOS?
Because proper
passthrough is not supported under tvOS. With eac3/atmos, the atmos is transparent to the eac3 part and carried along. It magically gets to the a/v receiver. With tvOS, it's a different story.
Re: Atmos
Posted: 08 Mar 2019, 18:45
by cosmoxl
davilla wrote: 08 Mar 2019, 17:30
cosmoxl wrote: 08 Mar 2019, 14:41
davilla wrote: 06 Mar 2019, 23:10
Got it

I'll have to put on the hipboots and wade into ffmpeg to see why eac3/atmos is not getting detected for this one.
So isn't ffmpeg demuxing on Shield as well? Why does it work on that platform but not tvOS?
Because proper
passthrough is not supported under tvOS. With eac3/atmos, the atmos is transparent to the eac3 part and carried along. It magically gets to the a/v receiver. With tvOS, it's a different story.
Perhaps you know already but the example cited in this thread and some other files have dropped in the last few days that are from a "new" source. It starts with an i and ends with Tunes. DRM broken. That's why we're seeing different behavior in the Atmos handling I'd imagine.
Re: Atmos
Posted: 11 Mar 2019, 14:34
by Bjokam
Any update on why this file didnt work?
Re: Atmos
Posted: 11 Mar 2019, 15:07
by davilla
Bjokam wrote: 11 Mar 2019, 14:34
Any update on why this file didnt work?
Block size is different than the others. EAC3/Atmos handling is being refactored to be more robust.
Re: Atmos
Posted: 12 Mar 2019, 13:01
by BanRay
Good to hear
When the refactor is succesful, will we see it in 3.8.1 or so?
Re: Atmos
Posted: 12 Mar 2019, 15:41
by davilla
BanRay wrote: 12 Mar 2019, 13:01
Good to hear
When the refactor is succesful, will we see it in 3.8.1 or so?
Of course...