|
|
Post by lukewayne on Dec 20, 2019 0:05:13 GMT -5
We already have one or two of several different AppleTV models - including the 4k model... And, depending on the other components in the system, they either have problems... or work perfectly. And, when they do have problems, again depending on the other components in the system, there are often specific settings or option choices that enable them to work.
(We do plan to start publishing tips about how to get things to work properly with some specific common combinations of equipment; look for that shortly.)
We are also planning some significant changes that will improve the lock-on speed for audio signals. One of those changes will be an option to individually configure each input to either accept or not accept a DSD input signal. Each audio input must currently test whether the incoming signal is DSD or not - and doing so adds significant time and complexity to the process.
We hope to speed things up considerably by allowing you to set specific inputs, which are never used for DSD audio, to skip the process of checking for a DSD signal.
keith But still you guys have a AppleTV 4k that you can test with? I would even expect you to have all the most common devices? Most issues that have been reported seem to be easy for most to repeat. But of course some issues only happens with a special setup. To me it seems the code block that locks on to a audio stream and sets its output that is a bit glitchy. Not only hdmi sync. Why else would there be similar problems with analog and balaced as well? Especially at startup. edit: Will you rewrite all old XMC-1 code in the future? I would guess some of this old code can cause issues or sluggishness. Please add an Intel NUC to your test bench, it has been the most difficult item in my stack to get to play nice with the RMC-1. Often requiring a full reboot of RMC and a full shut down power cycle of the NUC to get a picture to lock. Settings they would make it would would be very much appreciated. |
|
|
|
Post by novisnick on Dec 20, 2019 0:07:05 GMT -5
Just watched Mandalorian which is aired in Atmos but my RMC-1 only reported 5.1 surround sound. Im running fw 1.5, this doesn’t seem right I’m streaming via ATV 4K with the latest updates. Anybody else having this issue? Thanks in advance for any reply! Really been enjoying Mandalorian! 👍 It’s actually an AppleTV issue on Mando I think. I’ve read that other people with Apple TV’s are also only getting 5.1 on different processors. I also only get 5.1 with my Apple TV and RMC-1 Thanks so much! |
|
|
|
Post by hsamwel on Dec 20, 2019 13:33:14 GMT -5
So now I got the AppleTV 4k - Netflix ”missing channels” bug. A series supposed to have 5.1 is reqognised as 2.0 and thus are
missing center, surround and LFE channel. Was this a RMC or AppleTV/Netflix bug?
|
|
|
|
Post by hsamwel on Dec 20, 2019 16:51:28 GMT -5
One thing to note about AppleTV 4k is that it behaves a little strange with video settings. It has no source direct. If you set a higher dynamic range and resolution in video and sound settings than the actual source, AppleTV will ALWAYS upscale. So setting it to 4k Dolby Vision will make ALL sources in 4k Dolby Vision. This is crap! So I set it to 4k SDR. This way I only get resolution upscale from 1080p sources but it keeps all colors correct. It has options to match content, dynamic range and frequency. Which is great. But this option only works up, not down. Too bad match resolution isn’t available and that it doesn’t ignore the video settings. Haven’t tried but I guess setting the resolution to 1080p looses 4k in all sources?! Alot of other oddities.. All audio outputs in 48khz no matter source. No bitstream. Source Direct mode on AppleTV is achieved by activating “Match Range”, the accompanying designation of HDR or SDR is for the menu system only. I leave mine on SDR Match Range. All content plays in its native format. I tried this again. Before all sources I watched was upscaled to Dolby Vision like match range was disabled although it was on. Now it works as it should. Nice! Although everything is still upscaled in resolution to 4k. I have AppleTV set to 4k 50hz Dolby Vision in video settings. Too bad they can’t/won’t add bitstream for audio and source direct for video. I would expect my TV to have better upscaling than AppleTV has. |
|
|
|
Post by thrillcat on Dec 20, 2019 17:12:04 GMT -5
Source Direct mode on AppleTV is achieved by activating “Match Range”, the accompanying designation of HDR or SDR is for the menu system only. I leave mine on SDR Match Range. All content plays in its native format. I tried this again. Before all sources I watched was upscaled to Dolby Vision like match range was disabled although it was on. Now it works as it should. Nice! Although everything is still upscaled in resolution to 4k. I have AppleTV set to 4k 50hz Dolby Vision in video settings. Too bad they can’t/won’t add bitstream for audio and source direct for video. I would expect my TV to have better upscaling than AppleTV has. I couldn’t agree more on bitstreaming audio, but their up scaling is the best out there. They’re doing that right. |
|
|
|
Post by Geronimo on Dec 20, 2019 17:20:31 GMT -5
So now I got the AppleTV 4k - Netflix ”missing channels” bug. A series supposed to have 5.1 is reqognised as 2.0 and thus are missing center, surround and LFE channel. Was this a RMC or AppleTV/Netflix bug? Might be an EMOTIVA bug. It's the same bug I get when pausing then restarting LOSSLESS 5.1 PCM from certain blu rays... |
|
|
|
Post by TDifEQ on Dec 21, 2019 14:39:25 GMT -5
... One of those changes will be an option to individually configure each input to either accept or not accept a DSD input signal. Each audio input must currently test whether the incoming signal is DSD or not - and doing so adds significant time and complexity to the process.
We hope to speed things up considerably by allowing you to set specific inputs, which are never used for DSD audio, to skip the process of checking for a DSD signal. ... I like to use the same OPPO203 player (via HDMI) for both 2k/4k movies and DSD/music_CDs. Right now, a 2 output mux is used to spit OPPO203 HDMI output to both Radiance Pro and RMC-1 inputs. This is because RMC-1 does not sync with Radiance Pro. Do I need a three HDMI output mux now to feed OPPO203 Main Video/Audio Out to the following three inputs: 1. Radiance Pro Input 2. RMC-1 Input without DSD 3. RMC-1 Input with DSD I still want the RMC-1 OSD. |
|
|
|
Post by tom9933 on Dec 21, 2019 20:25:28 GMT -5
I still feel like my Sony OLED has the best up scaling, but it did improve with the new shield, and the shield has always done a nice job with bit streaming when the app supports it  I tried this again. Before all sources I watched was upscaled to Dolby Vision like match range was disabled although it was on. Now it works as it should. Nice! Although everything is still upscaled in resolution to 4k. I have AppleTV set to 4k 50hz Dolby Vision in video settings. Too bad they can’t/won’t add bitstream for audio and source direct for video. I would expect my TV to have better upscaling than AppleTV has. I couldn’t agree more on bitstreaming audio, but their up scaling is the best out there. They’re doing that right. |
|
|
|
Post by cwt on Dec 21, 2019 23:39:47 GMT -5
... One of those changes will be an option to individually configure each input to either accept or not accept a DSD input signal. Each audio input must currently test whether the incoming signal is DSD or not - and doing so adds significant time and complexity to the process.
We hope to speed things up considerably by allowing you to set specific inputs, which are never used for DSD audio, to skip the process of checking for a DSD signal. ... I like to use the same OPPO203 player (via HDMI) for both 2k/4k movies and DSD/music_CDs. Right now, a 2 output mux is used to spit OPPO203 HDMI output to both Radiance Pro and RMC-1 inputs. I think it was described before as a switch between dsd and pcm per input ; rather than locking each input to one specific codec ; so hopefully your ok still |
|
|
|
Post by hsamwel on Dec 22, 2019 7:33:04 GMT -5
I like to use the same OPPO203 player (via HDMI) for both 2k/4k movies and DSD/music_CDs. Right now, a 2 output mux is used to spit OPPO203 HDMI output to both Radiance Pro and RMC-1 inputs. I think it was described before as a switch between dsd and pcm per input ; rather than locking each input to one specific codec ; so hopefully your ok still This is supposed to be programable with the input buttons. So no cable switching or separate inputs needed, just a button press on the remote. My bluray settings is optimal for this though. I have the main hdmi as a single connector with both video and audio for movies. The second hdmi output is used with pure audio mode, all video is off. This is actually the mode I use for multi channel SACD or digital CD. I also have a balanced out for 2ch.. |
|
|
|
Post by Casey Leedom on Dec 22, 2019 13:57:58 GMT -5
Out of curiosity, I do wonder what the issue is with detecting DSD format audio data on HDMI. I would have thought that the sending device should properly identify the audio stream format with AUDIO_CODING_TYPE_SACD or AUDIO_CODING_TYPE_DST ... Or is this an issue of trying to detect the DSD over PCM (DoP) format? I would have thought that most HDMI sources would send DSD with the correct coding format?
Casey
|
|
Lsc
Emo VIPs 
Posts: 3,424
|
Post by Lsc on Dec 22, 2019 15:53:28 GMT -5
Out of curiosity, I do wonder what the issue is with detecting DSD format audio data on HDMI. I would have thought that the sending device should properly identify the audio stream format with AUDIO_CODING_TYPE_SACD or AUDIO_CODING_TYPE_DST ... Or is this an issue of trying to detect the DSD over PCM (DoP) format? I would have thought that most HDMI sources would send DSD with the correct coding format? Casey As KeithL has said earlier, it’s slowing down the HDMI switching. So since I have 3 inputs I use - iMac for Tidal, ATV4K, Sony X800 blu-ray player 2 out of 3 won’t need to worry about DSD so it’ll switch faster. The HDMI switching doesn’t bother me today but if it switches faster I’ll take it. |
|
|
|
Post by Casey Leedom on Dec 22, 2019 16:50:16 GMT -5
Yes, remember KeithL saying that. I'm just curious what the issue is. Casey |
|
LCSeminole
Global Moderator 
Res firma mitescere nescit.
Posts: 20,811
Member is Online
|
Post by LCSeminole on Dec 22, 2019 17:08:25 GMT -5
Having the option per input to turn off DSD detection will work in my favor if in fact it is appreciably slowing down HDMI handshakes. I preferred PCM with Dirac to DSD with the XMC-1, so when the RMC-1/RMC-1L/XMC-2 get Dirac 2.0, I’m sure I’ll prefer this as well over DSD, with faster switching to boot.
|
|
richb
Sensei
Oppo Beta Group - Audioholics Reviewer
Posts: 889
|
Post by richb on Dec 22, 2019 17:31:19 GMT -5
Having the option per input to turn off DSD detection will work in my favor if in fact it is appreciably slowing down HDMI handshakes. I preferred PCM with Dirac to DSD with the XMC-1, so when the RMC-1/RMC-1L/XMC-2 get Dirac 2.0, I’m sure I’ll prefer this as well over DSD, with faster switching to boot. I think this a really good option also considering some of the upcoming 16-channel products are not supporting DSD over HDMI. While I do have DSD disks, the majority of my content comes from DSD files that will be delivered via USB so only that connection is of interest. Currently, the USB does not support DSD multi-channel so I would have to resort to disks for that but still that is only one connection. If this improves switching speed then obviously the default for HDMI DSD is OFF  - Rich |
|
|
|
Post by Casey Leedom on Dec 22, 2019 18:53:16 GMT -5
Of course none of this would be a problem is we just had an Ethernet Roon Endpoint ...
Casey
|
|
|
|
Post by elwicksto on Dec 22, 2019 20:12:26 GMT -5
i did find a way to resolve the audio drop-outs at the beginning of pcm streams, with some hacking/reverse engineering. i added a hifiberry digi+ i/o card to a raspberry pi (spdif input & output), and put together a small ALSA pass thru program so i could inspect incoming data (from sonos toslink) to figure out what triggers the drop outs. based upon my observations, it seems that when a number of consecutive zeros come into the spdif signal, the rmc drops out audio for a couple seconds, presumably to handle stream type changes..
anyway, by adding a very small filter that detects a few zeros in a row and replaces one of them with a pair of 1s (L & R channel), then the dropouts no longer happen and i'm getting solid audio streams. i’ve not observed cases where the group of zeros happens within real audio, so dont think it ever negatively impacts audio quality. i can provide more details if anyone has interest - it costs less than $100, and takes a few hours of time. for me this has been the primary issue with the product, and with this workaround, digital audio has gone from disappointing to amazing.
|
|
|
|
Post by Casey Leedom on Dec 23, 2019 2:17:05 GMT -5
You ought to forward this debugging information to Emotiva elwicksto. Casey |
|
|
|
Post by hsamwel on Dec 23, 2019 6:52:33 GMT -5
Yeah I agree! Please report this to Emotiva. Maybe they can add this filter to all?
|
|
|
|
Post by elwicksto on Dec 23, 2019 10:27:23 GMT -5
You ought to forward this debugging information to Emotiva elwicksto. Casey i certainly could be wrong, but i think this is how the current firmware is designed to work and why Keith is talking about adding the option to disallow DD+ on specific inputs. so, Emo would be aware of this. my assumption is that when a group of zeros comes into via the spdif channel, the processor needs to figure out what type if data is coming in, and it doesn't immediately know if it is PCM or some other type of encoded/compressed stream (DD or something).. if you make the wrong decision (e.g. interprete DD as PCM) then garbage sound will come out - so to avoid garbage the processor waits until enough data is come thru before producing sound. |
|
