|
|
Post by AudioHTIT on Dec 4, 2021 23:10:17 GMT -5
Since it’s unique, I thought I should point out that Netflix has two tiers for streaming, I’m not going to look up exactly what they’re called, but let’s use HD and UHD. The HD tier give you 1080p and 5.1, the UHD tier gives you 4K/UHD and Atmos. I upgraded to the UHD tier at one point, I got pretty decent pictures but had the ‘center channel bug’ where dialog would randomly jump to your surround or or height speakers (TV) — this is typically caused by having insufficient bandwidth and is very annoying — we went back to an HD subscription to get rid of this. Let’s make sure that anyone discussing issues with the Netflix app, also lists what subscription they’re paying for, HD or UHD..
|
|
ttocs
Global Moderator 
I always have a wonderful time, wherever I am, whomever I'm with. (Elwood P Dowd)
Posts: 8,161
|
Post by ttocs on Dec 5, 2021 1:04:29 GMT -5
Since it’s unique, I thought I should point out that Netflix has two tiers for streaming, I’m not going to look up exactly what they’re called, but let’s use HD and UHD. The HD tier give you 1080p and 5.1, the UHD tier gives you 4K/UHD and Atmos. I upgraded to the UHD tier at one point, I got pretty decent pictures but had the ‘center channel bug’ where dialog would randomly jump to your surround or or height speakers (TV) — this is typically caused by having insufficient bandwidth and is very annoying — we went back to an HD subscription to get rid of this. Let’s make sure that anyone discussing issues with the Netflix app, also lists what subscription they’re paying for, HD or UHD.. When I signed up today there were three tiers to choose from, Basic, Standard, and Premium. I chose Premium with "Ultra HD (4K) and HDR". If everything in the system is ATMOS capable, then an ATMOS movie title will show the audio as being ATMOS. This screenshot is from when I played Lost In Space on the TiVo EDGE NETFLIX app via HDMI connection to the XMC-2. It shows the incoming as Dolby Plus, and the outbound as Dolby ATMOS audio.  This screenshot is from Lost In Space but on the Sony XBR-85X950G NETFLIX app via HDMI ARC to the XMC-2. It shows the incoming as Dolby Plus 5.1, and the outbound as Dolby Surround audio.  The HDMI cables in my system are all the same type and haven't exhibited any problem with DV, ATMOS, etc. But I changed the HDMI cable connecting the XMC-2 and tv several times today and got the same results. My normal cable is 10 feet long because it runs up the wall, then I tried a 4.5 foot cable, and also a 3 foot cable, all with the same results. My tv has eARC. What I don't know is what happens when it encounters a processor with ARC? How is it setup to cope with the limitation? In theory, from everything I've been able to find today, ATMOS should be possible via DD+ compressed. I know everything in the chain must be capable of the same spec for it all to work, so which item is not cooperating? My guess is it's the Emotiva processor, but how to prove it? I even cut the channel count down to 5.1.2 just to save some bandwidth. |
|
|
|
Post by Stephen Park on Dec 5, 2021 4:46:00 GMT -5
Since only Netflix Atmos isn’t activated with Emotiva through ARC, I believe (and heard somewhere here, but I can’t recall or point out where) that Netflix Atmos follows something different than other apps which are uses Dolby MAT encoding. That is why Emotiva and Netflix app can’t handshake correctly, thus Atmos is not kick in by Netflix. I think it is nonsense that the Netflix app has unique way (somewhat not follow dolby standard for implement their version of atmos). If so, how other makers such as Marantz, Denon, Onkyo, and other varios Soundbar makers cope with this so-called non standard way of Atmos and succesfully encode Netflix protocol??
All I have tested Netflix is under UHD subscription, and ARC, and good quality HDMI cable. Anyway ARC and cable is not a question because all other TV Apps do their Atmos job correctly under same combination.
One more thing, since Emotiva is not eARC compatible, I enable eARC on TV and test all other apps except Netflix, still Atmos is working through eARC enabled TV. So I believe ARC nor eARC is not a trouble point.
|
|
ttocs
Global Moderator
I always have a wonderful time, wherever I am, whomever I'm with. (Elwood P Dowd)
Posts: 8,161
|
Post by ttocs on Dec 5, 2021 10:49:26 GMT -5
I also tested changing the eARC setting on Sony TV set to Auto or Off and came up with no difference. I found some really great info from Dolby about ARC. Here's a couple addresses for Part 2 & 3 that I found particularly of interest. developer.dolby.com/blog/dolby-audio-over-hdmi-part-2-signaling-and-carriage/
developer.dolby.com/blog/dolby-audio-over-hdmi-part-3-reality/
My TiVo EDGE is capable of ATMOS via Dolby Digital Plus from Netflix. I connected the TiVo to the Sony 950G tv, set the tv's input for Enhanced so it gets full bandwidth, then proceeded to find out if ATMOS can make its way through to the XMC-2. It doesn't. The tv reports DD+ with no limit on the channels (ie DD+ 5.1). The audio comes into the XMC-2 as DD+ 5.1 48kHz/20bits and goes out as DD Surround. The NETFLIX account however detects that the TiVo is ATMOS capable so tv shows and movies all claim ATMOS as the soundtrack, which makes the negotiation between the Sony tv and XMC-2. The XMC-2 is correctly seeing DD+, but the tv (I'm guessing here) doesn't see the XMC-2 as being capable of ATMOS so it only sends DD+ 5.1 instead. Being that the XMC-2 reports 48kHz, this is correct. But, Dolby says " The data pipe is 2 channels with 16 bits per channel, so when you multiply the pipe size and the clock rate, you correspondingly get 1.5 Mbps, 6 Mbps, and 24.5 Mbps." It's the 6Mbps that we're after here to get " Dolby Digital Plus (with or without Dolby Atmos)" quoting Dolby. The XMC-2 reports 20bits, is this indicating a problem? For kicks I inserted one of my Lindy CEC-Less adapters at the XMC-2 end of the HDMI cable, no difference in the audio. edit: There is a difference in audio bits between the Sony tv NETFLIX app and outputting the TiVo NETFLIX into the Sony. The Sony NETFLIX app runs into the XMC-2 with 20bits, and when the TiVo NETFLIX signal reaches the XMC-2 it's at 16bits. I first thought it was the Lindy making the difference but due to having to cycle the inputs to get video after swapping the Lindy in and out it just took a few times for me to grasp what was happening. Either way, ATMOS is unattainable via ARC at the moment. |
|
AntonP
Minor Hero
RMC-1
Posts: 75 
|
Post by AntonP on Dec 5, 2021 11:52:13 GMT -5
HDMI1 out goes to TV HDMI2 out goes to PJ It won’t output to TV unless the PJ is on, so I have to unplug HDMI2 out How do I get it to work so that I don’t have to unplug cables Have the same problem. RMC-1 FW 2.3 Sim2 Lumis projector and LG OLED C9. Cant get picture on projector while TV is connected.
When only one display device is connected - all is ok. How to fix?
|
|
|
|
Post by cwt on Dec 5, 2021 17:19:37 GMT -5
HDMI1 out goes to TV HDMI2 out goes to PJ It won’t output to TV unless the PJ is on, so I have to unplug HDMI2 out How do I get it to work so that I don’t have to unplug cables Have the same problem. RMC-1 FW 2.3 Sim2 Lumis projector and LG OLED C9. Cant get picture on projector while TV is connected.
When only one display device is connected - all is ok. How to fix?
A consequence of 2 different resolutions 1080p and 4k for the tv . Hdmi works on the lowest resolution the edid comms receives and you need a pre pro or avr that does matrix switching to avoid this ; the rmc 1 etc are straight pass through switchers . If you upgraded the Sim to a 4k device you wouldnt have this problem . the alternative is a hd fury hd doctor or similar to transmit a different edid for your Lumis  |
|
|
|
Post by Stephen Park on Dec 5, 2021 20:25:04 GMT -5
I also tested changing the eARC setting on Sony TV set to Auto or Off and came up with no difference. I found some really great info from Dolby about ARC. Here's a couple addresses for Part 2 & 3 that I found particularly of interest. developer.dolby.com/blog/dolby-audio-over-hdmi-part-2-signaling-and-carriage/
developer.dolby.com/blog/dolby-audio-over-hdmi-part-3-reality/
My TiVo EDGE is capable of ATMOS via Dolby Digital Plus from Netflix. I connected the TiVo to the Sony 950G tv, set the tv's input for Enhanced so it gets full bandwidth, then proceeded to find out if ATMOS can make its way through to the XMC-2. It doesn't. The tv reports DD+ with no limit on the channels (ie DD+ 5.1). The audio comes into the XMC-2 as DD+ 5.1 48kHz/20bits and goes out as DD Surround. The NETFLIX account however detects that the TiVo is ATMOS capable so tv shows and movies all claim ATMOS as the soundtrack, which makes the negotiation between the Sony tv and XMC-2. The XMC-2 is correctly seeing DD+, but the tv (I'm guessing here) doesn't see the XMC-2 as being capable of ATMOS so it only sends DD+ 5.1 instead. Being that the XMC-2 reports 48kHz, this is correct. But, Dolby says " The data pipe is 2 channels with 16 bits per channel, so when you multiply the pipe size and the clock rate, you correspondingly get 1.5 Mbps, 6 Mbps, and 24.5 Mbps." It's the 6Mbps that we're after here to get " Dolby Digital Plus (with or without Dolby Atmos)" quoting Dolby. The XMC-2 reports 20bits, is this indicating a problem? For kicks I inserted one of my Lindy CEC-Less adapters at the XMC-2 end of the HDMI cable, no difference in the audio. edit: There is a difference in audio bits between the Sony tv NETFLIX app and outputting the TiVo NETFLIX into the Sony. The Sony NETFLIX app runs into the XMC-2 with 20bits, and when the TiVo NETFLIX signal reaches the XMC-2 it's at 16bits. I first thought it was the Lindy making the difference but due to having to cycle the inputs to get video after swapping the Lindy in and out it just took a few times for me to grasp what was happening. Either way, ATMOS is unattainable via ARC at the moment. This is... headache  Anyway Dolby's recommendation is 16bit and 6MBps, while XMC/RMC is reporting 20bit and don't know bandwidth... Either way, Netflix app fail to negotiate with XMC/RMC for detect whether connected device is Atmos capable or not. If it is TV app's fault, then it will also fail with all other devices as well, but it success except Emotiva device... so which one has faulty code or incompatible with Netflix app, is obvious. Since Netflix become world No.1 streaming service, and most of people enjoy this app with their TV, Emotiva must pay attention what is wrong, not just ignore it. I will report this again today. Let's wait what answer will come.... |
|
|
|
Post by autocrat on Dec 5, 2021 23:47:50 GMT -5
Netflix from an Nvidia Shield sends UHD/HDR/Atmos(DD+). My Panasonic UHD player also has Netflix but it only sends UHD/HDR/DD+5.1. Point being that the Netflix apps behave differently on different platforms so don't necessarily read anything from this into the behaviour of the AV processor.
|
|
AntonP
Minor Hero
RMC-1
Posts: 75
|
Post by AntonP on Dec 6, 2021 0:19:46 GMT -5
A consequence of 2 different resolutions 1080p and 4k for the tv . Hdmi works on the lowest resolution the edid comms receives and you need a pre pro or avr that does matrix switching to avoid this ; the rmc 1 etc are straight pass through switchers . If you upgraded the Sim to a 4k device you wouldnt have this problem . the alternative is a hd fury hd doctor or similar to transmit a different edid for your Lumis
I understand that switch isnt matrix and lower resolution display device is primary. So if both devices are connected i should have 1080p resolution on both devices. But i get black sreen on projector when both connected ( PS i preordered hd fury vrroom 8k in september and still waiting for it...
|
|
|
|
Post by hsamwel on Dec 6, 2021 3:49:12 GMT -5
Netflix from an Nvidia Shield sends UHD/HDR/Atmos(DD+). My Panasonic UHD player also has Netflix but it only sends UHD/HDR/DD+5.1. Point being that the Netflix apps behave differently on different platforms so don't necessarily read anything from this into the behaviour of the AV processor. Yes, most know this.. However, the problem is that Netflix with Atmos on ARC works to other devices. So if you have a soundbar, Denon/Marantz AVR or whatever you’ll get Atmos. With Emotiva Netflix somehow does not detect Emotiva as a Atmos capable device. The most strange part is that other apps on the same TV output Atmos. edit: btw the Panasonic bluray player Netflix app I believe is not Atmos capable.. So this is not a valid comparison I would think. |
|
|
|
Post by cwt on Dec 6, 2021 3:49:50 GMT -5
I understand that switch isnt matrix and lower resolution display device is primary. So if both devices are connected i should have 1080p resolution on both devices. But i get black sreen on projector when both connected ( PS i preordered hd fury vrroom 8k in september and still waiting for it...
Depends on which edid has locked on 1st possibly . Have you tried a different start up procedure ? I take it you need a 4k downscaler and frame rate manipulation so went for the vroom ? I would have gotten a Dr hdmi to manage all your edids and send an always on programmed edid even with the projector off .. www.hdfury.com/product/dr-hdmi-8k/Hdmi just gets more complicated with these high bandwidths  |
|
|
|
Post by hsamwel on Dec 6, 2021 4:01:22 GMT -5
I understand that switch isnt matrix and lower resolution display device is primary. So if both devices are connected i should have 1080p resolution on both devices. But i get black sreen on projector when both connected ( PS i preordered hd fury vrroom 8k in september and still waiting for it...
Do you have them on the correct output? TV should be on the ARC output, HDMI 2 I believe. I have a 4k TV and a 1080p projector.. It worked for me last time I tested.. A long time ago. But if I view 4k content on the TV and start up the projector after I’m not sure the TV get scaled down resolution.. But processors should inform the HDMI chain that a lower resolution device is used and do a resync as soon as the projector kicks in.. |
|
|
|
Post by hsamwel on Dec 6, 2021 4:10:22 GMT -5
I understand that switch isnt matrix and lower resolution display device is primary. So if both devices are connected i should have 1080p resolution on both devices. But i get black sreen on projector when both connected ( PS i preordered hd fury vrroom 8k in september and still waiting for it...
Depends on which edid has locked on 1st possibly . Have you tried a different start up procedure ? I take it you need a 4k downscaler and frame rate manipulation so went for the vroom ? I would have gotten a Dr hdmi to manage all your edids and send an always on programmed edid even with the projector off .. www.hdfury.com/product/dr-hdmi-8k/Hdmi just gets more complicated with these high bandwidths As I wrote before.. Unless the processors get something wrong from any of the display devices it shouldn’t matter in which order they are turned on. The processor gets the displays ”specs” from the HDMI sync. As soon as a lower resolution display device is turned on the processors SHOULD resync and settle with the lowest resolution. If one of the devices report this wrong you’ll get a black screen. But you will get the same if Emotiva has done something wrong as well.. edit: the source needs to be in auto resolution of course. Otherwise it won’t change to the lower resolution. Even though the processor tells it to. It’s like starting a 4k bluray on a 1080p display.. You’ll get a black screen. |
|
|
|
Post by hsamwel on Dec 6, 2021 4:22:09 GMT -5
I also tested changing the eARC setting on Sony TV set to Auto or Off and came up with no difference. I found some really great info from Dolby about ARC. Here's a couple addresses for Part 2 & 3 that I found particularly of interest. developer.dolby.com/blog/dolby-audio-over-hdmi-part-2-signaling-and-carriage/
developer.dolby.com/blog/dolby-audio-over-hdmi-part-3-reality/
My TiVo EDGE is capable of ATMOS via Dolby Digital Plus from Netflix. I connected the TiVo to the Sony 950G tv, set the tv's input for Enhanced so it gets full bandwidth, then proceeded to find out if ATMOS can make its way through to the XMC-2. It doesn't. The tv reports DD+ with no limit on the channels (ie DD+ 5.1). The audio comes into the XMC-2 as DD+ 5.1 48kHz/20bits and goes out as DD Surround. The NETFLIX account however detects that the TiVo is ATMOS capable so tv shows and movies all claim ATMOS as the soundtrack, which makes the negotiation between the Sony tv and XMC-2. The XMC-2 is correctly seeing DD+, but the tv (I'm guessing here) doesn't see the XMC-2 as being capable of ATMOS so it only sends DD+ 5.1 instead. Being that the XMC-2 reports 48kHz, this is correct. But, Dolby says " The data pipe is 2 channels with 16 bits per channel, so when you multiply the pipe size and the clock rate, you correspondingly get 1.5 Mbps, 6 Mbps, and 24.5 Mbps." It's the 6Mbps that we're after here to get " Dolby Digital Plus (with or without Dolby Atmos)" quoting Dolby. The XMC-2 reports 20bits, is this indicating a problem? For kicks I inserted one of my Lindy CEC-Less adapters at the XMC-2 end of the HDMI cable, no difference in the audio. edit: There is a difference in audio bits between the Sony tv NETFLIX app and outputting the TiVo NETFLIX into the Sony. The Sony NETFLIX app runs into the XMC-2 with 20bits, and when the TiVo NETFLIX signal reaches the XMC-2 it's at 16bits. I first thought it was the Lindy making the difference but due to having to cycle the inputs to get video after swapping the Lindy in and out it just took a few times for me to grasp what was happening. Either way, ATMOS is unattainable via ARC at the moment. Netflix is encoded with Dolby Digital Plus at 20bits in the premium tier. I believe this is the streaming standard for most major services. Why you got 16bit from the TiVo is beyond me.. But it’s not bitstreaming if that’s the case. |
|
|
|
Post by Stephen Park on Dec 6, 2021 9:05:19 GMT -5
Netflix from an Nvidia Shield sends UHD/HDR/Atmos(DD+). My Panasonic UHD player also has Netflix but it only sends UHD/HDR/DD+5.1. Point being that the Netflix apps behave differently on different platforms so don't necessarily read anything from this into the behaviour of the AV processor. If app working correctly with 99% of devices and last 1% is yours, which worth 5K, you don't want claim it's mal behavior and just give up? Can just said each device has different so don't care? I simply can't do that. And I myself being software/firmware developer and engineer, if my device which made by my hand is work like that last 1%, I will do whatever I can for solve out without sleeping. I can't get my device being that 1%. For sure. |
|
|
|
Post by Stephen Park on Dec 6, 2021 9:17:03 GMT -5
Netflix from an Nvidia Shield sends UHD/HDR/Atmos(DD+). My Panasonic UHD player also has Netflix but it only sends UHD/HDR/DD+5.1. Point being that the Netflix apps behave differently on different platforms so don't necessarily read anything from this into the behaviour of the AV processor. Yes, most know this.. However, the problem is that Netflix with Atmos on ARC works to other devices. So if you have a soundbar, Denon/Marantz AVR or whatever you’ll get Atmos. With Emotiva Netflix somehow does not detect Emotiva as a Atmos capable device. The most strange part is that other apps on the same TV output Atmos. edit: btw the Panasonic bluray player Netflix app I believe is not Atmos capable.. So this is not a valid comparison I would think. Thanks for confirming that panasonic player is not atmos capable... I just try to find out that part from google. And yes, most strange part is that other apps on same TV output Atmos. Because of this, I strongly doubt that the Netflix app uses somewhat different negotiation-handshake routine and Emotiva does not interpret does codes and fail to answer correctly as "I can play Atmos, just send me in!" Instead, it said "Oh, I dunno what you want, huh??" So Netflix app thinks that this is not Atmos capable. If so, how on earth other brand devices can understand what same Netflix app asking for, and answer correctly? That is why I believe Emotiva has less comprehend capabilities, which came from bug. |
|
|
|
Post by doc1963 on Dec 6, 2021 9:21:25 GMT -5
ttocs, hsamwel is correct. Dolby Digital Plus is always 20bit and should report as such. Your XMC-2 is reporting that correctly. I also concur that your TiVo should not be reporting “16bit” if it is a true unadulterated DD+ bitstream. FWIW, when my RMC-1L was active in my system (just a month or two ago), I also could not receive Atmos via Netflix when streaming via ARC from my LG CX’s internal app. All other internal apps that support Atmos (Disney+, Prime, Movies Anywhere and Vudu for example) worked just fine. When viewing Netflix from my Nvidia Shield (set to bitstream the audio), Atmos worked properly and my RMC-1L reported receiving “DD+” and at the correct 20bits. That configuration was working correctly and exactly as expected. Since the ATV does not bitstream raw audio, I’ll leave it out of the discussion. However, now that I have my AV8805 back in my system (for other reasons), Netflix streamed from my LG now works exactly as it should. “Atmos” is displayed in the Netflix GUI and is being received by the 8805. The only change here was the processor. So, apparently there’s an issue with the EDID that is being published by the XMC/RMC that the internal Netflix app on these TVs does not like. It may have “something” to do with eARC, but since Dolby Digital Plus (with Atmos metadata) certainly can be carried over conventional ARC (and since all of the other apps send Atmos via ARC without issue) that theory wouldn’t make sense. But at the end of the day, Emotiva needs to consult with these parties, sort this out, and fix it. Don’t pull your hair out trying to figure it out yourself… you’ll just end up hairless… 😁
|
|
ttocs
Global Moderator
I always have a wonderful time, wherever I am, whomever I'm with. (Elwood P Dowd)
Posts: 8,161
|
Post by ttocs on Dec 6, 2021 11:22:10 GMT -5
ttocs , hsamwel is correct. Dolby Digital Plus is always 20bit and should report as such. Your XMC-2 is reporting that correctly. I also concur that your TiVo should not be reporting “16bit” if it is a true unadulterated DD+ bitstream. FWIW, when my RMC-1L was active in my system (just a month or two ago), I also could not receive Atmos via Netflix when streaming via ARC from my LG CX’s internal app. All other internal apps that support Atmos (Disney+, Prime, Movies Anywhere and Vudu for example) worked just fine. When viewing Netflix from my Nvidia Shield (set to bitstream the audio), Atmos works properly and my RMC-1L reports receiving “DD+” and at the correct 20bits. This configuration is working correctly and as expected. Since the ATV does not bitstream raw audio, I’ll leave it out of the discussion. However, now that I have my AV8805 back in my system (for other reasons), Netflix streamed from my LG now works exactly as it should and Atmos is displayed in the Netflix GUI and is being received by the 8805. The only change was the processor. So, there’s apparently an issue with the EDID that is being published by the XMC/RMC that the internal Netflix app on these TVs does not like. It may have “something” to do with eARC, but since Dolby Digital Plus (with Atmos metadata) can certainly be carried over conventional ARC (and since all of the other apps send Atmos via ARC without issue) that wouldn’t make sense. But at the end of the day, Emotiva needs to consult with these parties, sort this out, and fix it. Don’t pull your hair out trying to figure it out yourself… you’ll just end up hairless… 😁 I figured hsamwel was correct on the 20bits, he seems very knowledgable on this stuff. Just don't know why a 20bit source (TiVo) loses 4bits on its way into and out of a Sony tv. When the TiVo is plugged directly into the XMC-2 using HDMI 1 it shows 20bits as can be seen in the attached image.  So what I did was to connect the TiVo to HDMI-2 of the Sony tv and then use ARC for the audio, which then showed up in the XMC-2 as 16bits after having gone through the Sony tv. (same thing happens with TV4K but we don't need to discuss that here, just pointing that out.) So 4bits gets washed out of the stream somewhere. To recap, when the NETFLIX on Sony app travels via ARC to the XMC-2 the audio shows up as 20bits, and when the NETFLIX on TiVo app is connected to the XMC-2 the audio also shows up as 20bits, but when the NETFLIX on TiVo app is connected to the Sony tv and the audio travels via ARC to the XMC-2 the audio shows up as 16bits. After hsamwel and you both explained about the bits, I'm not concerning myself with that so much anymore, thank you both! But, I'd love to know where those 4bits went just for gettin' some learnin'. I am interested in learning more about this as it intrigues me at the very least, and it annoys me that this is so mysterious, which is what is driving my quest for knowledge about ARC - because I don't even use ARC!!! But I might be inclined to use is if only for some apps in my tv now that I know a little more about it. ARC had been tedious to get going on the G3P until I discovered how to "kick start" my XMC-2 so the tv sees it by initiating the CEC Loopback Test mode. The key has been to press the front power button for at least 15 seconds prior to switching on the rear power switch. I believe that this drains out some residual power so a proper reset of whatever is blocking ARC from operating can occur. No need to run the CEC Loopback Test, just getting the processor into test mode was all that was needed for the tv to instantly see the processor. |
|
|
|
Post by hsamwel on Dec 6, 2021 19:05:52 GMT -5
ttocs , hsamwel is correct. Dolby Digital Plus is always 20bit and should report as such. Your XMC-2 is reporting that correctly. I also concur that your TiVo should not be reporting “16bit” if it is a true unadulterated DD+ bitstream. FWIW, when my RMC-1L was active in my system (just a month or two ago), I also could not receive Atmos via Netflix when streaming via ARC from my LG CX’s internal app. All other internal apps that support Atmos (Disney+, Prime, Movies Anywhere and Vudu for example) worked just fine. When viewing Netflix from my Nvidia Shield (set to bitstream the audio), Atmos works properly and my RMC-1L reports receiving “DD+” and at the correct 20bits. This configuration is working correctly and as expected. Since the ATV does not bitstream raw audio, I’ll leave it out of the discussion. However, now that I have my AV8805 back in my system (for other reasons), Netflix streamed from my LG now works exactly as it should and Atmos is displayed in the Netflix GUI and is being received by the 8805. The only change was the processor. So, there’s apparently an issue with the EDID that is being published by the XMC/RMC that the internal Netflix app on these TVs does not like. It may have “something” to do with eARC, but since Dolby Digital Plus (with Atmos metadata) can certainly be carried over conventional ARC (and since all of the other apps send Atmos via ARC without issue) that wouldn’t make sense. But at the end of the day, Emotiva needs to consult with these parties, sort this out, and fix it. Don’t pull your hair out trying to figure it out yourself… you’ll just end up hairless… 😁 I figured hsamwel was correct on the 20bits, he seems very knowledgable on this stuff. Just don't know why a 20bit source (TiVo) loses 4bits on its way into and out of a Sony tv. When the TiVo is plugged directly into the XMC-2 using HDMI 1 it shows 20bits as can be seen in the attached image. <button disabled="" class="c-attachment-insert--linked o-btn--sm">Attachment Deleted</button> So what I did was to connect the TiVo to HDMI-2 of the Sony tv and then use ARC for the audio, which then showed up in the XMC-2 as 16bits after having gone through the Sony tv. (same thing happens with TV4K but we don't need to discuss that here, just pointing that out.) So 4bits gets washed out of the stream somewhere. To recap, when the NETFLIX on Sony app travels via ARC to the XMC-2 the audio shows up as 20bits, and when the NETFLIX on TiVo app is connected to the XMC-2 the audio also shows up as 20bits, but when the NETFLIX on TiVo app is connected to the Sony tv and the audio travels via ARC to the XMC-2 the audio shows up as 16bits. After hsamwel and you both explained about the bits, I'm not concerning myself with that so much anymore, thank you both! But, I'd love to know where those 4bits went just for gettin' some learnin'. I am interested in learning more about this as it intrigues me at the very least, and it annoys me that this is so mysterious, which is what is driving my quest for knowledge about ARC - because I don't even use ARC!!! But I might be inclined to use is if only for some apps in my tv now that I know a little more about it. ARC had been tedious to get going on the G3P until I discovered how to "kick start" my XMC-2 so the tv sees it by initiating the CEC Loopback Test mode. The key has been to press the front power button for at least 15 seconds prior to switching on the rear power switch. I believe that this drains out some residual power so a proper reset of whatever is blocking ARC from operating can occur. No need to run the CEC Loopback Test, just getting the processor into test mode was all that was needed for the tv to instantly see the processor. Is the TiVo 16bit stream from the TV a PCM, Dolby Digital or Dolby Digital Plus? If it is a legacy Dolby Digital stream then I would guess the TV reencodes the stream before sending it to your XMC-2. You could look at settings in the TV for handling digital audio output. Could be something there..Or not.. Could also be that the TV does not support bitstream audio passthrough. It simply decodes the audio then reencodes it when you use the ARC feature. |
|
ttocs
Global Moderator
I always have a wonderful time, wherever I am, whomever I'm with. (Elwood P Dowd)
Posts: 8,161
|
Post by ttocs on Dec 6, 2021 19:25:15 GMT -5
I figured hsamwel was correct on the 20bits, he seems very knowledgable on this stuff. Just don't know why a 20bit source (TiVo) loses 4bits on its way into and out of a Sony tv. When the TiVo is plugged directly into the XMC-2 using HDMI 1 it shows 20bits as can be seen in the attached image. <button disabled="" class="c-attachment-insert--linked o-btn--sm">Attachment Deleted</button> So what I did was to connect the TiVo to HDMI-2 of the Sony tv and then use ARC for the audio, which then showed up in the XMC-2 as 16bits after having gone through the Sony tv. (same thing happens with TV4K but we don't need to discuss that here, just pointing that out.) So 4bits gets washed out of the stream somewhere. To recap, when the NETFLIX on Sony app travels via ARC to the XMC-2 the audio shows up as 20bits, and when the NETFLIX on TiVo app is connected to the XMC-2 the audio also shows up as 20bits, but when the NETFLIX on TiVo app is connected to the Sony tv and the audio travels via ARC to the XMC-2 the audio shows up as 16bits. After hsamwel and you both explained about the bits, I'm not concerning myself with that so much anymore, thank you both! But, I'd love to know where those 4bits went just for gettin' some learnin'. I am interested in learning more about this as it intrigues me at the very least, and it annoys me that this is so mysterious, which is what is driving my quest for knowledge about ARC - because I don't even use ARC!!! But I might be inclined to use is if only for some apps in my tv now that I know a little more about it. ARC had been tedious to get going on the G3P until I discovered how to "kick start" my XMC-2 so the tv sees it by initiating the CEC Loopback Test mode. The key has been to press the front power button for at least 15 seconds prior to switching on the rear power switch. I believe that this drains out some residual power so a proper reset of whatever is blocking ARC from operating can occur. No need to run the CEC Loopback Test, just getting the processor into test mode was all that was needed for the tv to instantly see the processor. Is the TiVo 16bit stream from the TV a PCM, Dolby Digital or Dolby Digital Plus? If it is a legacy Dolby Digital stream then I would guess the TV reencodes the stream before sending it to your XMC-2. You could look at settings in the TV for handling digital audio output. Could be something there..Or not.. Could also be that the TV does not support bitstream audio passthrough. It simply decodes the audio then reencodes it when you use the ARC feature. Dolby Digital Plus |
|
