Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I think they have fixed it that when you played a video using homesharing the app shows the video as watched, previously it didn’t do this immediately.
 
It’s actually more that earc is kinda like hdmi-cec, everyone has their own slightly different flavor and as soon as you let ‘em talk it explodes.
Well, it had worked fine for everyone until 15.2. That update comes out and so many people ended up with the same problem.
 
Well, it had worked fine for everyone until 15.2. That update comes out and so many people ended up with the same problem.

Not doubting that, I just mean, the change could be to correctly implement eARC, and the actual is that it only worked with it “out of spec”. There’s lots of ways to break things.

Most of the issues related to eARC are caused by one of the devices not correctly reporting capabilities (sometimes of itself, others where it’s forwarding the device up/downstream).

For example if IMAX Enhanced was an audio flag (not sure if it is or not) and they added support for it and the player saw the flag from the receiver incorrectly so it sent “IMAX Enhanced” audio (I know it’s not a real thing, but imax enhanced itself isn’t really a thing, it’s more like a certification) but the receiver couldn’t play it or the tv can’t pass it correctly for whatever reason, then you could get issues.

Its totally possible they just broke arc, but it seems way more likely they did it by trying to add a new feature that is incorrectly implemented elsewhere and causing a break because the other devices don’t actually support the new feature. For example they could of enabled QMS, but if QMS isn’t implemented correctly everywhere, it would advertise the wrong supported formats upon switching inputs (since QMS is like a cached profile/session sort of thing so it should just reopen and have all the same settings).

I don’t doubt apple changed something, and it likely is “the cause” of the issue, but that doesn’t mean their change was wrong or they made a mistake.

Sadly in software and electrical engineering, there really are situations where two wrongs make a right, and it’s by fixing one of the two that you ultimately break it.
 
Doesn't explain why issues such as the audio clicks not working on the home screen no longer can be heard even when not hooked up to e-arc.
 
Not doubting that, I just mean, the change could be to correctly implement eARC, and the actual is that it only worked with it “out of spec”. There’s lots of ways to break things.

Most of the issues related to eARC are caused by one of the devices not correctly reporting capabilities (sometimes of itself, others where it’s forwarding the device up/downstream).

For example if IMAX Enhanced was an audio flag (not sure if it is or not) and they added support for it and the player saw the flag from the receiver incorrectly so it sent “IMAX Enhanced” audio (I know it’s not a real thing, but imax enhanced itself isn’t really a thing, it’s more like a certification) but the receiver couldn’t play it or the tv can’t pass it correctly for whatever reason, then you could get issues.

Its totally possible they just broke arc, but it seems way more likely they did it by trying to add a new feature that is incorrectly implemented elsewhere and causing a break because the other devices don’t actually support the new feature. For example they could of enabled QMS, but if QMS isn’t implemented correctly everywhere, it would advertise the wrong supported formats upon switching inputs (since QMS is like a cached profile/session sort of thing so it should just reopen and have all the same settings).

I don’t doubt apple changed something, and it likely is “the cause” of the issue, but that doesn’t mean their change was wrong or they made a mistake.

Sadly in software and electrical engineering, there really are situations where two wrongs make a right, and it’s by fixing one of the two that you ultimately break it.

Not doubting that, I just mean, the change could be to correctly implement eARC, and the actual is that it only worked with it “out of spec”. There’s lots of ways to break things.

Most of the issues related to eARC are caused by one of the devices not correctly reporting capabilities (sometimes of itself, others where it’s forwarding the device up/downstream).

For example if IMAX Enhanced was an audio flag (not sure if it is or not) and they added support for it and the player saw the flag from the receiver incorrectly so it sent “IMAX Enhanced” audio (I know it’s not a real thing, but imax enhanced itself isn’t really a thing, it’s more like a certification) but the receiver couldn’t play it or the tv can’t pass it correctly for whatever reason, then you could get issues.

Its totally possible they just broke arc, but it seems way more likely they did it by trying to add a new feature that is incorrectly implemented elsewhere and causing a break because the other devices don’t actually support the new feature. For example they could of enabled QMS, but if QMS isn’t implemented correctly everywhere, it would advertise the wrong supported formats upon switching inputs (since QMS is like a cached profile/session sort of thing so it should just reopen and have all the same settings).

I don’t doubt apple changed something, and it likely is “the cause” of the issue, but that doesn’t mean their change was wrong or they made a mistake.

Sadly in software and electrical engineering, there really are situations where two wrongs make a right, and it’s by fixing one of the two that you ultimately break it.
 
So maybe DTS will see the light…Disney may be the trigger launching IMAX Enhanced….Maybe Apple will follow suit….




 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.