t3x3l
Minor Hero
Posts: 12
|
Post by t3x3l on Nov 20, 2022 14:27:36 GMT -5
Yes I am having the exact same issue with my VRROOM and my XMC2. I contacted Emotiva and they tried to blame the VRROOM which worked fine on 2.5 and still works fine on other devices. There is another user with a Lumagen getting the same issues. Supposedly Keith will get back to me and he is reporting it to Lonnie. IF they had called this a beta AND not immediately blamed the customer when issues are reported I wouldnt be upset. I spent 10 hrs working on this to have Keith slap me on the hand for his assumption when in the reality I had done as he asked and so much more without being prompted. The truth is the users know more about what isnt working than the manufacturer, scary. I'm still a Emo fan and plan on doing the upgrade but the taste in the mouth aint great RN. I cannot blame the Vrroom here. My two Tivos and my ATV working fine (leveraging the Audio Out of the Vrroom). The issue also raises it's ugly head with the direct connect between the BluRay player and the RMC-1L. Last night I could get the Vrroom connection to finally work so we could watch the movie. The Direct Connect is a lost cause. This morning, I could not get either connection to work. This is absolutely a 3.1 issue, it worked perfectly fine for the past year. Nothing else changed. Yeah all my issues came with 3.1. Interestingly direct connect works for me but I am using the VRROOM for the 120hz and prefer its switching honestly. Try this, which is what I'm doing for a workaround for now. Plug your audio out into a input on the Emo and select that input. Then run a cable from your TV ARC port to the ARC port on your emo and enable arc output on your TV. This seems to make my VRROOM magically work like it used to. Whats crazy is when I check the VRROOM just with the audio out plugged in it shows the Emo detected (but no sound...) as soon as I connect that ARC cable the VRROOM now sees my LG C1 connected to the audio out (it isnt, im plugged into a emo input...) it makes no sense to me and the input select is not the arc input but the numbered one on the Emo unit but it works. BY GOD IT WORKS. If I remove the arc cable sound stops lolololol Hopefully its something silly and we get a 3.11 soon. |
|
|
|
Post by rew452 on Nov 20, 2022 14:29:17 GMT -5
I think you are mixed up about HDMI input and output ports.
My TV is hooked up to HDMI output 2 which is the ARC port.
I did of course say HDMI 1, my mistake.
Thanks
|
|
|
|
Post by RichGuy on Nov 20, 2022 14:58:57 GMT -5
The update went well for me. I updated my RMC-1L yesterday everything went fine. I did need to restart it after step 5 completed before continuing to step 6 which wasn't mentioned and startled me at first as at first I thought it wasn't responding until I realized it had shut off, it was displaying HDMI 1 on the right side left side blank at that time. I have only seen the updating fonts the one time while the update was taking place, although I do normally use Video Remains On I tried both turning off Video Remains ON and even turning Off/On my RMC-1L from the back panel and I still have not had a repeat of updating fonts. I have had my RMC-1L for almost a year as I received last December 7th 2021. If your RMC-1L has “12.25 22/10/10” for the HDMI Version, then I’m betting you are one of the first to get the hardware changed, latest 4K HDMI board with “eARC”. Thus this was about the time KeithL mentioned the change of hardware due to pandemic/supply issues for certain parts. Yes, I just looked and I do have HDMI Version “12.25 22/10/10” so I guess I am one of the first to get the new HDMI board. I thought I may have been one of the last to get the old HDMI board as I thought I'd read the new boards did not start shipping until January 2022 and I received my RMC-1L 12/07/2021. That's good to know. |
|
|
|
Post by AudioHTIT on Nov 20, 2022 15:34:41 GMT -5
TL;DR Take the firmware update process seriously, follow a written procedure and do it the same way each time. Make sure the procedure you use includes specific steps to take the FW upgrade notes and requirements into account.
I am going to somewhat reluctantly post my rather lengthy procedure for doing firmware updates. It does not coincide with Emotiva’s process so this is not an official recommendation, but I have used it successfully for many years (and I may do more FW updates than the average user). This is written specifically for my system; my wife (who designs airspace and writes plans and procedures for the FAA, has followed it to do updates when I’m away skiing), so some steps (like turning off the Mac, or the Harmony), may not apply to you. I will bold the steps that I think make this, or any procedure more successful, and will comment more at the end.
RMC/XMC Firmware Update Procedure
1.Start Harmony activity (system on) from LPS & confirm normal operation
2. RMC-1 > Menu > Setup > Advanced
—- A. Select : Backup Settings ^ (confirm) < (begin)
—- B.. Insert Flash drive with new firmware only
—- C. Select : Backup Settings ^ (confirm) < (begin) — 2nd backup for archive
—- D. Select : Factory Reset ^ (confirm) < (begin)
—- E. Select : Standby, change to Lowest Power
—- F. Select : Firmware Update ^ (confirm) < (begin
3. When processor shuts down turn off other components
—- A. Shut down Mac mini (to prepare for step 4)
—- B. Harmony “All Off”
—- C. Remove Flash Drive
4. Bounce system power (in lieu of pulling HDMI)
—- A. Turn AV breaker off (Main Panel CB#9)
—- B. Wait at least three minutes
—- C. Turn AV breaker on
—- D. Wait until all devices boot, status lights are on & stable (standby)
5. Restore system
—- A. Start Harmony Activity — Watch TV
—- B. Watch for normal startup — Time?
—- C. Menu>Information for expected firmware version
—- D. Menu>Setup>Advanced
—- E. Restore Settings ^ (confirm) < (begin)
—- F. Exit menu
—- G. Shutdown all gear (Harmony all off)
6. Startup and Test or Use
—- A. Start Harmony Activity — Watch TV
—- B. Test basic functions and previously known issues
This all normally takes me 15 to 30 minutes depending on distractions, multitasking, or ‘state of mind’; writing your procedure down (and following it), allows you be interrupted and not miss an important step.
Starting from LPS, or a cold (power off) reboot, is important in order to have the processor in a freshly booted / clean state; I also like having the processor in LPS while upgrading for a clean ‘happy ending’. I too have the luxury of having ALL my equipment on a single, dedicated, 20A circuit breaker and can easily remove power from every device, simultaneously for however long is necessary; because of this I don’t unplug any cables — you need to do one or the other to properly clear the EDID tables from all devices.
A factory reset and restore (or reload settings from scratch) is becoming an SOP for a variety of devices (TVs also come to mind). Some here have nicely organized spreadsheets documenting all of the changes they make to each of their devices.
I’m posting this in hopes that it helps some come to a more successful conclusion. I have similar gear to many here (signature), and I use it daily without grief or the problems many describe. It won’t fix the ‘loading fonts bug’, I still have some ‘minor’ pops and clicks with TV and sometimes elsewhere, nothing I worry about damaging my equipment (but my wife notices). I’m not claiming any high ground, I have no magic, just experience and maybe patience. Other experienced users also have procedures similar to this.
The TL;DR explains my conclusion; read the release notes, take the process seriously, write it down, don’t do it if you’re in a hurry or don’t understand what your doing. Start with Emotiva’s procedure and use it, or modify it for your system or situation (I made mine up before such procedures existed). I haven’t mentioned that I also have a lucky flash drive that I always and only use for RMC firmware updates … it’s like a high tech rabbits foot.
You’re welcome to comment or question, but please don’t quote this whole post for others to scroll through (edit for pertinence).
|
|
xeno
Minor Hero
Posts: 50
|
Post by xeno on Nov 20, 2022 16:34:24 GMT -5
So aside from a bit faster input switching I'm not really seeing much difference in my problematic RMC-1L. Certainly not the update I was hoping for.
I guess I'll have to keep it in LPM and deal with the wait. I was excited to see it working for awhile in VRO mode but it didn't last long.
Bummer.. |
|
|
|
Post by PaulBe on Nov 20, 2022 16:46:29 GMT -5
TL;DR Take the firmware upgrade process seriously, ... 1. I have an AV breaker for the whole system. I use it to reset the whole system. Full power down. 2. I use the same memory stick for all FW upgrades. "A factory reset and restore (or reload settings from scratch) is becoming an SOP for a variety of devices". My next step is a reload from scratch. I've done it twice. It's just a PITA.  |
|
|
|
Post by panasonicst60 on Nov 20, 2022 20:25:06 GMT -5
Definitely Emotiva needs to improve their beta testing process. No idea how many beta testers were but obviously not enough. I think they have enough beta testers. Everyone that owns their preamps are. |
|
cawgijoe
Emo VIPs 
"When you come to a fork in the road, take it." - Yogi Berra
Posts: 5,035
|
Post by cawgijoe on Nov 20, 2022 23:04:20 GMT -5
So aside from a bit faster input switching I'm not really seeing much difference in my problematic RMC-1L. Certainly not the update I was hoping for.
I guess I'll have to keep it in LPM and deal with the wait. I was excited to see it working for awhile in VRO mode but it didn't last long.
Bummer.. I’m not having any issues in VRO, which I have always used. Switching is faster. No electronic noises with the Apple TV. My Oppo 203 works fine. I do get the loading fonts if I use the rear switch, but since I’m on VRO, that’s not an issue. I have the XMC-2 with old board. edit: You were having lock up issues in VRO….I assume that was not solved. I wonder how many others have this problem….. |
|
cawgijoe
Emo VIPs
"When you come to a fork in the road, take it." - Yogi Berra
Posts: 5,035
|
Post by cawgijoe on Nov 20, 2022 23:14:30 GMT -5
Definitely Emotiva needs to improve their beta testing process. No idea how many beta testers were but obviously not enough. I think they have enough beta testers. Everyone that owns their preamps are. I just want to comment that the beta testers here are working beyond the call of duty to test and sort out issues. They are all volunteers and are doing their best to check the firmware provided to them. I appreciate every one of them and don’t think they should be blamed if an issue arises that is unique or beyond their use and systems. Emotiva is throwing more resources at these issues. If it’s at all possible, they will sort it out. |
|
|
|
Post by jonstatt on Nov 21, 2022 1:02:02 GMT -5
I cannot blame the Vrroom here. My two Tivos and my ATV working fine (leveraging the Audio Out of the Vrroom). The issue also raises it's ugly head with the direct connect between the BluRay player and the RMC-1L. Last night I could get the Vrroom connection to finally work so we could watch the movie. The Direct Connect is a lost cause. This morning, I could not get either connection to work. This is absolutely a 3.1 issue, it worked perfectly fine for the past year. Nothing else changed. Yeah all my issues came with 3.1. Interestingly direct connect works for me but I am using the VRROOM for the 120hz and prefer its switching honestly. Try this, which is what I'm doing for a workaround for now. Plug your audio out into a input on the Emo and select that input. Then run a cable from your TV ARC port to the ARC port on your emo and enable arc output on your TV. This seems to make my VRROOM magically work like it used to. Whats crazy is when I check the VRROOM just with the audio out plugged in it shows the Emo detected (but no sound...) as soon as I connect that ARC cable the VRROOM now sees my LG C1 connected to the audio out (it isnt, im plugged into a emo input...) it makes no sense to me and the input select is not the arc input but the numbered one on the Emo unit but it works. BY GOD IT WORKS. If I remove the arc cable sound stops lolololol Hopefully its something silly and we get a 3.11 soon. I found that since 3.1, I have to physically select the HDMI port on my RMC1 that vrroom has its audio out connected to while my projector is on AND showing the video of it. You see blue stripes which is what vrroom sends on its audio only output. Then step away to another hdmi input. Then back to it and everything starts working normally from this point. |
|
|
|
Post by jjkessler on Nov 21, 2022 7:54:37 GMT -5
Waiting to upgrade until I get a feel for new issues. For those who have upgraded, is the current 3.1 version worth the upgrade?
|
|
|
|
Post by bitzerjdb on Nov 21, 2022 8:00:38 GMT -5
Yeah all my issues came with 3.1. Interestingly direct connect works for me but I am using the VRROOM for the 120hz and prefer its switching honestly. Try this, which is what I'm doing for a workaround for now. Plug your audio out into a input on the Emo and select that input. Then run a cable from your TV ARC port to the ARC port on your emo and enable arc output on your TV. This seems to make my VRROOM magically work like it used to. Whats crazy is when I check the VRROOM just with the audio out plugged in it shows the Emo detected (but no sound...) as soon as I connect that ARC cable the VRROOM now sees my LG C1 connected to the audio out (it isnt, im plugged into a emo input...) it makes no sense to me and the input select is not the arc input but the numbered one on the Emo unit but it works. BY GOD IT WORKS. If I remove the arc cable sound stops lolololol Hopefully its something silly and we get a 3.11 soon. I found that since 3.1, I have to physically select the HDMI port on my RMC1 that vrroom has its audio out connected to while my projector is on AND showing the video of it. You see blue stripes which is what vrroom sends on its audio only output. Then step away to another hdmi input. Then back to it and everything starts working normally from this point. I don't have any Video output from the RMC-1L. I simply have the Audio Out as one Input and the Direct Connect from the BluRay as a Second Input. This is why I get Video without an issue, and sound doesn't work. |
|
|
|
Post by bitzerjdb on Nov 21, 2022 8:08:44 GMT -5
I just want to comment that the beta testers here are working beyond the call of duty to test and sort out issues. They are all volunteers and are doing their best to check the firmware provided to them. I appreciate every one of them and don’t think they should be blamed if an issue arises that is unique or beyond their use and systems. Emotiva is throwing more resources at these issues. If it’s at all possible, they will sort it out. I don’t think anybody in their right mind will blame the beta testers. Emotiva in handling the program? Probably. I don't blame the the Beta Testers, I assume there is enough of them so that the errors we are seeing have been known and reported. The updating Fonts issues had to be well known. I don't "blame" Emotiva either... I DO question their decision to release the firmware knowing that problem existed. If you really really wanted to release it, it should have been called out as an issue. If you are going to tell me you didn't know, then I question the Beta Testing program. Decisions like this do nothing to build trust in the process. |
|
|
|
Post by jdmusante on Nov 21, 2022 8:28:15 GMT -5
So aside from a bit faster input switching I'm not really seeing much difference in my problematic RMC-1L. Certainly not the update I was hoping for.
I guess I'll have to keep it in LPM and deal with the wait. I was excited to see it working for awhile in VRO mode but it didn't last long.
Bummer.. I’m not having any issues in VRO, which I have always used. Switching is faster. No electronic noises with the Apple TV. My Oppo 203 works fine. I do get the loading fonts if I use the rear switch, but since I’m on VRO, that’s not an issue. I have the XMC-2 with old board. edit: You were having lock up issues in VRO….I assume that was not solved. I wonder how many others have this problem….. Are there any specific settings I should be looking at with regard to an Oppo? You’re saying your 203 works just fine. My 205 does work, it just has a hell of a time with the handshake. So much so that my TV loses its signal multiple times before latching on. Once connected, the Oppo works fine. Plays 4K blu rays without issue with good sound/surround sound. I don’t have this issue with my Apple TV. |
|
|
|
Post by PaulBe on Nov 21, 2022 8:39:41 GMT -5
Waiting to upgrade until I get a feel for new issues. For those who have upgraded, is the current 3.1 version worth the upgrade? It was not worth it for me. I now have more problems than with FW2.3. 1. Processor locks every day; lost video and/or audio in FF, RW, and chapter skip. it used to happen occasionally. 2. Lost Center Heights. 3. Update Fonts issue. These issues, and others, are not exclusive to me and should have been known by both EMO and beta testers. This FW update should have never left the bench. If this is the "new world", don't get on the boat; it's lost at sea. |
|
cawgijoe
Emo VIPs
"When you come to a fork in the road, take it." - Yogi Berra
Posts: 5,035
|
Post by cawgijoe on Nov 21, 2022 9:17:20 GMT -5
Waiting to upgrade until I get a feel for new issues. For those who have upgraded, is the current 3.1 version worth the upgrade? It was not worth it for me. I now have more problems than with FW2.3. 1. Processor locks every day; lost video and/or audio in FF, RW, and chapter skip. it used to happen occasionally. 2. Lost Center heights. 3. Update Fonts issue. These issues, and others, are not exclusive to me and should have been known by both EMO and beta testers. This FW update should have never left the bench. If this is the "new world", don't get on the boat. It's lost. It's incredibly interesting to me how one person can have problems like this yet others not. 1. Processor does not lock....has never locked. No loss of video or audio. Weird. 2. Can't comment here because I don't have Atmos yet. 3. Update Fonts issue is known and being worked. Does not apply to my case because I use VRO. |
|
cawgijoe
Emo VIPs
"When you come to a fork in the road, take it." - Yogi Berra
Posts: 5,035
|
Post by cawgijoe on Nov 21, 2022 9:20:03 GMT -5
I’m not having any issues in VRO, which I have always used. Switching is faster. No electronic noises with the Apple TV. My Oppo 203 works fine. I do get the loading fonts if I use the rear switch, but since I’m on VRO, that’s not an issue. I have the XMC-2 with old board. edit: You were having lock up issues in VRO….I assume that was not solved. I wonder how many others have this problem….. Are there any specific settings I should be looking at with regard to an Oppo? You’re saying your 203 works just fine. My 205 does work, it just has a hell of a time with the handshake. So much so that my TV loses its signal multiple times before latching on. Once connected, the Oppo works fine. Plays 4K blu rays without issue with good sound/surround sound. I don’t have this issue with my Apple TV. I can't answer the settings question. I haven't changed a thing on my 203 since initial setup. It just works. No handshake issues. I don not use ARC/CEC. That's all off and I also bought a couple Lindy CEC-Less adapters just in case, though I didn't need them. Insurance. |
|
|
|
Post by PaulBe on Nov 21, 2022 9:26:25 GMT -5
It was not worth it for me. I now have more problems than with FW2.3. 1. Processor locks every day; lost video and/or audio in FF, RW, and chapter skip. it used to happen occasionally. 2. Lost Center heights. 3. Update Fonts issue. These issues, and others, are not exclusive to me and should have been known by both EMO and beta testers. This FW update should have never left the bench. If this is the "new world", don't get on the boat. It's lost.
1. Processor does not lock....has never locked. No loss of video or audio. Weird. 2. Can't comment here because I don't have Atmos yet. 3. Update Fonts issue is known and being worked. Does not apply to my case because I use VRO. Ahem... Are my posts the only posts you read? "one person"? I'm happy for you that your processor is working at your standards and use. Using a little symbolism, saying the update fonts issue does not apply because you use VRO is like saying my car works great because I use chewing gum and duct tape to keep the bumper from falling off. |
|
cawgijoe
Emo VIPs
"When you come to a fork in the road, take it." - Yogi Berra
Posts: 5,035
|
Post by cawgijoe on Nov 21, 2022 9:29:47 GMT -5
I don’t think anybody in their right mind will blame the beta testers. Emotiva in handling the program? Probably. I don't blame the the Beta Testers, I assume there is enough of them so that the errors we are seeing have been known and reported. The updating Fonts issues had to be well known. I don't "blame" Emotiva either... I DO question their decision to release the firmware knowing that problem existed. If you really really wanted to release it, it should have been called out as an issue. If you are going to tell me you didn't know, then I question the Beta Testing program. Decisions like this do nothing to build trust in the process. I can't comment on anything the Beta group saw regarding the "Fonts" message. I highly doubt it was there prior to release of 3.1 or it would have been mentioned. The firmware was released because the pitchforks were raised due to the long time waiting for fixes. This was not a "complete" attempt at fixes. It was partial. That has been documented. Emotiva has hired an additional resource (expert) to work this through. I'm confident it will happen and get better for those remaining issues. If you have developed "new"issues due to 3.1, please reach out to Emotiva to make you voices heard. Emotiva is monitoring this board, but they are not always on it. |
|
|
|
Post by geebo on Nov 21, 2022 9:33:51 GMT -5
I’m not having any issues in VRO, which I have always used. Switching is faster. No electronic noises with the Apple TV. My Oppo 203 works fine. I do get the loading fonts if I use the rear switch, but since I’m on VRO, that’s not an issue. I have the XMC-2 with old board. edit: You were having lock up issues in VRO….I assume that was not solved. I wonder how many others have this problem….. Are there any specific settings I should be looking at with regard to an Oppo? You’re saying your 203 works just fine. My 205 does work, it just has a hell of a time with the handshake. So much so that my TV loses its signal multiple times before latching on. Once connected, the Oppo works fine. Plays 4K blu rays without issue with good sound/surround sound. I don’t have this issue with my Apple TV. I didn't change a thing and my 203 is working fine with my RMC-1L as it always has. If you haven't already I would check out the cables and their physical connections if for no other reason than to just rule them out. |
|
