cawgijoe
Emo VIPs
"We made too many of the wrong mistakes." - Yogi Berra
Posts: 4,907
|
Post by cawgijoe on Nov 19, 2019 9:12:52 GMT -5
Well gang, I have decided to go back to version 1.5 software. This version was working fine for me with no issues other than slow Input switching which I have become used too. I installed 1.7 several days ago and had nothing but problems with it when it comes to the Standby setting of Video Remains On. After installing 1.7, I went through the rigmarole of powering all the way down, unplugging the power cord, removing all source connections, and then rebooting. I then reconnected my source devices and at first everything seemed fine. I went the whole day with no apparent issues. Even turned the RMC off for several hours when I went out and when I came back, Video Remains On worked as it should. Watched some tv without turning on the RMC. That night everything was working fine when I went to bed and turned everything off normally. Next morning I tried to watch tv and no video. Audio but no picture. I tried to turn the RMC on but would not respond. To get it to work I completely powered down and then restarted. After the restart the unit worked fine the rest of the day. That night I turned everything off as normal and the next morning went through the same thing. Did this 3 mornings in a row and I finally had enough. Installed 1.5 yesterday, went to bed last night, and Video Remains On worked as it should this morning. I have no clue as to why the unit with 1.7 works fine during the day, but when turned off overnight, does not work the next morning without powering down and restarting from there. Just to be clear, when I say the RMC is turned off, I am using the remote's Standby button. Also, because of other family members, I did not check to see if setting the Standby mode to Lowest Power at night would have any effect the next morning. It very well could have resolved the issue, but since I need to have Video Remains On usable, I did not bother. If it was only me, then I might have put up with it. But why should I/we need to put up with something that for me anyway was working with version 1.5 but now, at least for me, does not work as it should in version 1.7? Sorry for the long-winded post, but wanted to explain as best I could what was going on with my system. Steve I just wanted to let everyone know that I had to go back to 1.5 from 1.7 in my XMC-2 for similar reasons. My video remains on with 1.7 gave me no audio. Just video. Worked fine powered up completely. I did talk to Emotiva tech support and was told that this was a problem with certain TV brands. I have a Samsung. Not sure if that is right, but that's what I was told. I was also told they will fix this in the next firmware release. Fingers crossed. Apologize for posting an XMC-2 issue here, but they are using the same firmware and this might help someone. Also....please report your issue to Emotiva.
|
|
|
Post by goozoo on Nov 19, 2019 9:29:42 GMT -5
[quote source="/post/1011257/thread". I don’t think the problem is that the output devices have different resolutions like I have read here in the fourum. But rather specific units making demands and asumes things like resolution in the hdmi chain. Emotiva probably follows the ”standard” to rigidly and thus have problems with devices, mostly older 1.3/1.4, that won’t play along with, mostly newer 2.0 devices. With the introduction of HDMI 2.0 (which supposedly is backwards compatible), HDCP 2.2 IS NOT! If you have two devices with different HDCP capabilities, you WILL NOT (should not) get a picture per the licensing agreement. While you can mix HDMI 2.0 with 1.4, you CANNOT mix HDCP 2.2 with 1.4! The chain has to be 1.4 or 2.2 all the way through to produce an image. In the above scenario, one of the devices needs the capability to switch between the different HDCP formats to maintain the continuity. Furthermore, the RMC1 is not a true HDMI matrix switcher and thus cannot be relied upon for predictable results. One can try a HDFURY Vertex to resolve the issue but that can be hit or miss as well we have found with our installs. The only solution for such scenarios that has worked consistently is the introduction of a Lumagen Pro into the video chain but at added cost. Alternatively one can purchase a true HDMI matrix switcher but cannot get around the need for HDCP continuity to overcome the copy protection.
|
|
|
Post by TDifEQ on Nov 19, 2019 9:32:00 GMT -5
I'm forced back to 1.5. Something fundamental has changed with this firmware ... pls tell us. Config is all 4k all HDCP 2.2. RMC-1 is not interacting with Vertex2 the way it used to. That I don't like.
|
|
|
Post by deewan on Nov 19, 2019 9:35:36 GMT -5
With the introduction of HDMI 2.0 (which supposedly is backwards compatible), HDCP 2.2 IS NOT! If you have two devices with different HDCP capabilities, you WILL NOT (should not) get a picture per the licensing agreement. While you can mix HDMI 2.0 with 1.4, you CANNOT mix HDCP 2.2 with 1.4! The chain has to be 1.4 or 2.2 all the way through to produce an image. In the above scenario, one of the devices needs the capability to switch between the different HDCP formats to maintain the continuity. Furthermore, the RMC1 is not a true HDMI matrix switcher and thus cannot be relied upon for predictable results. One can try a HDFURY Vertex to resolve the issue but that can be hit or miss as well we have found with our installs. The only solution for such scenarios that has worked consistently is the introduction of a Lumagen Pro into the video chain but at added cost. Alternatively one can purchase a true HDMI matrix switcher but cannot get around the need for HDCP continuity to overcome the copy protection. THANK YOU for the explanation. I know my secondary monitor is older so I'm sure it is not compliant with my newer projector. I was thinking of upgrading that monitor so perhaps this gives me reason to do so. BTW - this is an excellent piece of info. goozoo I hope you don't mind but I copied and pasted most of your explanation into the best practices section for the RMC. I don't think you had a copy-write on that info.
|
|
|
Post by AudioHTIT on Nov 19, 2019 10:31:51 GMT -5
BTW - this is an excellent piece of info. goozoo I hope you don't mind but I copied and pasted most of your explanation into the best practices section for the RMC. I don't think you had a copy-write on that info. Agreed, more good info from goozoo, but how did you defeat the copy-protection and accomplish the cut and paste ... never mind, probably confidential 🤓
|
|
LCSeminole
Global Moderator
Res firma mitescere nescit.
Posts: 20,495
|
Post by LCSeminole on Nov 19, 2019 11:13:10 GMT -5
[quote source="/post/1011257/thread". I don’t think the problem is that the output devices have different resolutions like I have read here in the fourum. But rather specific units making demands and asumes things like resolution in the hdmi chain. Emotiva probably follows the ”standard” to rigidly and thus have problems with devices, mostly older 1.3/1.4, that won’t play along with, mostly newer 2.0 devices. With the introduction of HDMI 2.0 (which supposedly is backwards compatible), HDCP 2.2 IS NOT! If you have two devices with different HDCP capabilities, you WILL NOT (should not) get a picture per the licensing agreement. While you can mix HDMI 2.0 with 1.4, you CANNOT mix HDCP 2.2 with 1.4! The chain has to be 1.4 or 2.2 all the way through to produce an image. In the above scenario, one of the devices needs the capability to switch between the different HDCP formats to maintain the continuity. Furthermore, the RMC1 is not a true HDMI matrix switcher and thus cannot be relied upon for predictable results. One can try a HDFURY Vertex to resolve the issue but that can be hit or miss as well we have found with our installs. The only solution for such scenarios that has worked consistently is the introduction of a Lumagen Pro into the video chain but at added cost. Alternatively one can purchase a true HDMI matrix switcher but cannot get around the need for HDCP continuity to overcome the copy protection. Your statements above are what I’ve understood as well, but I do know that Oppo had firmware updates for their HDCP2.0 compliant media players(BDP-83/93/95/103/105) to work with HDCP2.2 compliant processors/receivers.
|
|
|
Post by aswiss on Nov 19, 2019 12:36:56 GMT -5
I'm forced back to 1.5. Something fundamental has changed with this firmware ... pls tell us. Config is all 4k all HDCP 2.2. RMC-1 is not interacting with Vertex2 the way it used to. That I don't like. Me too, each time I zap around the TV Channels, it either freezes or blocks with PCM 0.0. 1.7 is a step back. Maybe change the chip and start from scratch is the easier way to go. 6 months waiting to get everything worse. Why could this happen?
|
|
cawgijoe
Emo VIPs
"We made too many of the wrong mistakes." - Yogi Berra
Posts: 4,907
|
Post by cawgijoe on Nov 19, 2019 13:56:05 GMT -5
I'm forced back to 1.5. Something fundamental has changed with this firmware ... pls tell us. Config is all 4k all HDCP 2.2. RMC-1 is not interacting with Vertex2 the way it used to. That I don't like. Me too, each time I zap around the TV Channels, it either freezes or blocks with PCM 0.0. 1.7 is a step back. Maybe change the chip and start from scratch is the easier way to go. 6 months waiting to get everything worse. Why could this happen? I don't think it's the chipset. Firmware needs to be looked at involving these audio problems. I think they can be fixed to satisfy a majority.
|
|
|
Post by MonsieurAl on Nov 19, 2019 14:31:48 GMT -5
Hi, I'm the first to go back to 1.5, and I find that everyone will come back to 1.5 it's sad! rmc-1 and Emotiva dropped in my esteem this time. With 1.8 what will happen? RMC-1 will catch fire? But it will be the fault of my TV of course! now I have lost hope for the development of RMC-1. If I had known it was going to be this way? I would have waited for exchange xmc-1 / xmc-2 it would have allowed me to save a lot of money. it's going to be 6 months that I fight with the RMC-1 and instead of advancing we regress ! (1.7) Hello ... Emotiva there is someone again
|
|
|
Post by aswiss on Nov 19, 2019 14:34:47 GMT -5
Hi, I'm the first to go back to 1.5, and I find that everyone will come back to 1.5 it's sad! rmc-1 and Emotiva dropped in my esteem this time. With 1.8 what will happen? RMC-1 will catch fire? But it will be the fault of my TV of course! now I have lost hope for the development of RMC-1. If I had known it was going to be this way? I would have waited for exchange xmc-1 / xmc-2 it would have allowed me to save a lot of money. it's going to be 6 months that I fight with the RMC-1 and instead of advancing we regress ! (1.7) Hello ... Emotiva there is someone again Did you report your problems to the support Team? I did, and waiting for an answer. For me 1.5 is ok, almost everything is working except the Known Issues. But I agree, it should work everywhere and with all standard devices.
|
|
|
Post by MonsieurAl on Nov 19, 2019 15:30:04 GMT -5
Hi, I'm the first to go back to 1.5, and I find that everyone will come back to 1.5 it's sad! rmc-1 and Emotiva dropped in my esteem this time. With 1.8 what will happen? RMC-1 will catch fire? But it will be the fault of my TV of course! now I have lost hope for the development of RMC-1. If I had known it was going to be this way? I would have waited for exchange xmc-1 / xmc-2 it would have allowed me to save a lot of money. it's going to be 6 months that I fight with the RMC-1 and instead of advancing we regress ! (1.7) Hello ... Emotiva there is someone again Did you report your problems to the support Team? I did, and waiting for an answer. For me 1.5 is ok, almost everything is working except the Known Issues. But I agree, it should work everywhere and with all standard devices. it tells me nothing to report my problems, I have the same problem as everyone and Emotiva is making firmware that create even more problems. I'm waiting for the next processor with 16 channels, Dirac, Auro 3 D with stable HDMI card so that I can finally watch my movie without taking my head. (Jbl synthesis)
|
|
|
Post by aswiss on Nov 19, 2019 15:38:34 GMT -5
Me too, each time I zap around the TV Channels, it either freezes or blocks with PCM 0.0. 1.7 is a step back. Maybe change the chip and start from scratch is the easier way to go. 6 months waiting to get everything worse. Why could this happen? I don't think it's the chipset. Firmware needs to be looked at involving these audio problems. I think they can be fixed to satisfy a majority. I'm not a technician - so I don't really care, which part of the RMC-1 is causing these new issues, and how they could be solved - thats Emo's business. But for sure it was not what I expected after more than 6 months of waiting to get existing Bugs fixed! I'm now back on 1.5 - so I can at least use it.
|
|
|
Post by MonsieurAl on Nov 19, 2019 15:45:52 GMT -5
If the rmc was a $ 400 device ok, it does not matter ... but it cost me $ 5900 in France + $ 600 of fiber optic HDMI cables + $ 400 HdFury Vertex² and all that money for 3 hours of battle with the RMC to just watch a movie because I came back to 1.5 is delirious it must stop!
|
|
|
Post by brutiarti on Nov 19, 2019 15:51:03 GMT -5
I’m sorry but I don’t understand why unsatisfied customers don’t return the problematic unit and move on...
|
|
|
Post by TDifEQ on Nov 19, 2019 16:13:32 GMT -5
That does not help
|
|
|
Post by TDifEQ on Nov 19, 2019 16:22:57 GMT -5
This is the first time RMC-1, RMC-L and XMC-2 are all on the same firmware release. Development is still shaking out their verification test workflow among all 3 processors and will respond to bugs. Be patient. Go back to 1.5 if workarounds are not immediately available. Feel better? I do. I'm on 1.5.
|
|
|
Post by TDifEQ on Nov 19, 2019 16:34:18 GMT -5
I've read all the posts on this thread. Usually the owners that complain the most have the most issues … and they are pretty darn articulate and accurate. Usually, non-owners that complain on this thread are normally seasoned veterans that see similar issues here to what they've experienced in the past. Silent readers should understand that owners feel pretty much ignored by development (development is ssslllooowww to react). This thread is great for owners and expert installers helping other owners. Nuf said.
|
|
|
Post by hsamwel on Nov 19, 2019 18:30:51 GMT -5
Still the same problem with my dish receiver. If I start the dish receiver and the TV while having RMC in standby I get picture but no sound. Turning on RMC I get sound instantly, turn it off and the sound shuts off.. No difference if I set the dish receiver to output Dolby Digital Plus or Stereo. This bug has been the same since firmware 1.3 and upto 1.7. Happens everytime.
I have reported this to Keith in a private message a while back.
|
|
|
Post by Bonzo on Nov 19, 2019 19:40:44 GMT -5
High Quality Balanced to Unbalanced Output Adapters are now available !!!
I don't know if anybody has mentioned this already or not...
But we now have adapters available for connecting the balanced outputs on your RMC-1, RMC-1L, or XMC-2 to unbalanced inputs on other gear. These are neat little adapters with an XLR connector on one end to plug into the unit... And a female RCA connector on the other where you can connect an appropriate RCA-to-RCA interconnect cable. - These are pigtail adapters, with a high quality connector on each end, and about eight inches of flexible wire between them - Both connectors have high quality metal shells with a tough black coating - They are wired correctly (the inverting balanced output is not shorted to ground like it is on adapters intended for use with microphones) - Because the pigtail is flexible, it doesn't stick straight out like a solid adapter, so you don't need a lot of extra clearance for it - We used special slim-line connectors that have plenty of clearance for the closely-spaces connectors on the back of the RMC-1, RMC-1L, and XMC-2
- They're only $8 each
You can find them in the accessory section of our website... here:
Okay, so I have a question that I think warrants some clarification. When the RMC-1 was first shown to only have XLR outputs, some people questioned this or didn't like it. To answer their question and squelch the issue, Dan promised that each RMC-1 would come with 16 XLR to RCA adapters shipped in the box. November 2018 the first units shipped and no adapters were included. To answer then what the deal was, someone from Emotiva (I forget who exactly, but it was probably near the beginning of this thread) said that the adapters were not ready yet, but would be soon, probably early 2019, and would be made available to RMC-1 owners who requested them. Now, 11 months later, the adapters are finally available, and in the RMC-1 thread you are saying they are $8 each. So, are they still free for RMC-1 owners as Dan said they would be, but for RMC-1L and XMC-2 owners they are $8 each? Or, have minds changed again at Emotiva and they are now $8 each regardless of which unit you own? I think the $8 each is a very fair price for what appears to be a nice solid adapter, something I might considering purchasing on my own sans Emotiva processor. But I think there may be some RMC-1 owners expecting their adapters to be free, as they were originally promised. So clarification would be appreciated. So KeithL, some time has passed now and you have yet to answer my question. 15 people have "liked" my post so there is interest in getting clarification. Can you please clarify with a definitive answer? Note: I do not agree with people saying this is a "just call Emotiva" question. There are many many occasions where that is true. This is not one of them. I have already answered why in a previous post. You are clarifying in great length over in the trade in thread, so I think this one should be much easier. Thanks - Bonzo
|
|
|
Post by Thunderduck on Nov 19, 2019 23:49:01 GMT -5
I advised Emotiva support about my issue with the Video On Standby setting. Was advised that they have received feedback from a number of owners and that Emotiva has been able to reproduce the problem. The Video On Standby is losing connection with some TVs, especially Sony and Vizio. They are working on a software fix.
Hope springs eternal …
Steve
|
|