MrMC

tvOS 11.4 is out. Hope they fix the Problem. Waiting for the Change Log.

They didn’t.

TaZZi2k wrote: 30 May 2018, 07:25 tvOS 11.4 is out. Hope they fix the Problem. Waiting for the Change Log.

Nope. Davilla posted somewhere in this forum a link to a VLC bug report saying that VLC had received word from Apple that passthrough will not be "fixed".

Then I am very curious how they will ever support Atmos. AFAIK Atmos requires that the decoder knows the speaker config, unless they ignore whether someone e.g. has a 5.2.1 (two upfiring speakers) and just decode for 5.1 or 7.1 to PCM.

Hopefully next week more news, when they will say something about tvOS 12.0

loekf2 wrote: 30 May 2018, 20:28 Then I am very curious how they will ever support Atmos. AFAIK Atmos requires that the decoder knows the speaker config, unless they ignore whether someone e.g. has a 5.2.1 (two upfiring speakers) and just decode for 5.1 or 7.1 to PCM.

Hopefully next week more news, when they will say something about tvOS 12.0

They may not ever support Atmos. Perhaps they told a little white lie to get people to buy the box. That's what we're all wondering I think.

loekf2 wrote: 30 May 2018, 20:28 Then I am very curious how they will ever support Atmos. AFAIK Atmos requires that the decoder knows the speaker config, unless they ignore whether someone e.g. has a 5.2.1 (two upfiring speakers) and just decode for 5.1 or 7.1 to PCM.

Hopefully next week more news, when they will say something about tvOS 12.0

I think a lot of people are hopefully for Atmos next week, especially people like me since I have a 7.1.4 system (4 in the ceiling - still need a new receiver for the back 2 so I'm running 7.1.2 right now).

cosmoxl wrote: 30 May 2018, 21:20 They may not ever support Atmos. Perhaps they told a little white lie to get people to buy the box. That's what we're all wondering I think.

They actually didn't say anything about the Apple TV 4K supporting it specifically, they just said was that Atmos was on their roadmap for tvOS, but they didn't give a timeline or anything so it could realistically be 3 years away.

Well, Apple could implement Atmos yet not expose a public API for it. They already do that to some degree with eac3. Eac3 is a little funny, it can be either 48kHz or 192kHz but most content needs the 192 kHz sample rate. Yet the public API does not support 192 kHz, only up to 48kHz and I know it can internally do 192 kHz... There's a launch test that MrMC does a check for 192 kHz support and that never passes

hi guys,

any idea if this problem will be solved ? my set up is

from APTV4 HMDI ---> TV
from APTV4 optical audio ---> Bose soundsystem
Bose soundsystem ---> tv through HDMI

Unit settings

- tvos sound = DD
- Mr MC passthrough closed

still the same static noise that comes back every 5 or 10 sec.

I dont care about the quality lose but that static noise makes it unwatchable. I have this problem only with MrMC.
Youtube or Netflix works like a charm. I dont use infuse or plex.

Premux wrote: 16 Jun 2018, 22:25 hi guys,

any idea if this problem will be solved ? my set up is

from APTV4 HMDI ---> TV
from APTV4 optical audio ---> Bose soundsystem
Bose soundsystem ---> tv through HDMI

Unit settings

- tvos sound = DD
- Mr MC passthrough closed

still the same static noise that comes back every 5 or 10 sec.

I dont care about the quality lose but that static noise makes it unwatchable. I have this problem only with MrMC.
Youtube or Netflix works like a charm. I dont use infuse or plex.

Disable passthrough, Apple broke it. That's what this thread is all about. Apple broke it, only Apple can fix it.

A little more info from the "Infuse guy"

" astirling wrote:
"The guys behind MrMC claim that Apple has told them this isn’t coming back."

" James wrote:
They are likely referring to a note from the VLC devs in which they claim Apple told them passthrough wasn't supported. I've seen the original VLC email (and Apple's response) and can tell you with absolute certainty they were asking the wrong question, and as a result the Apple rep simply directed them to submit a feature request.
As of today, our bug report with Apple is still open. We've submitted full technical details about the issue, and Apple asked for additional info in a follow-up - which seems to indicate the issue was introduced inadvertently, and they have at least some interest in fixing it.
If/when Apple actually intends to fix this is unclear, but at this point there is no reason to believe this change was intentional. It's also possible this change is part of larger, more sweeping audio related changes coming in tvOS 12, so we'll have to see what Apple introduces in the betas coming later this summer."