|
|
Post by fiero429 on Nov 26, 2022 20:42:17 GMT -5
Have the new firmware installed install went fine. Never had a problem with old version when switching input with loosing sound. Now with this new version if switch inputs now than two times I losse sound then it lock up can't change anything or even cut unit off with remote,have use the main power switch on the back of unit .
The sound format switch is better as long as I stay on the same input.
So this update has made things worse me. Hope a new update will come soon
|
|
|
|
Post by jayce996 on Nov 27, 2022 11:05:15 GMT -5
Hello there,
I was having troubles to manage HDMI ARC with my PS5 quite some times but i was able to make it happen most of the time. at last a hard reboot resolved the connexion
Now with the 3.1 firmware, it does not work at all...
- hard reboot
- soft reboot
- full power off of the TV during the firmware upgrade (as required)
- deactivation / Activation of the ARC option on the TV (LG G1)
- XMC2 switched first or after
nothing works, please heeeeellllllppppppp
|
|
|
|
Post by Goodfella on Nov 27, 2022 12:40:23 GMT -5
Updated on release day. No issues updating. If fully powering down I get the updating fonts message. I just use the VRO and no issues. The A4K had Atmos issues initially but a reboot of the A4K fixed it. I get NO pops or clicks like before. It use to be really bad with Loudness on but now it works fine. So far I have found no issues with everything I have thrown at it but I am only using A4K and a 4K player. After running for about a week the clicks and pops came back. I can’t run with VRO without the processor getting buggy. I switched it back to low power mode so it does the full startup and shutdown each time. I get the Font issue upon startup which sucks and adds a lot more boot time. Other than the super slow boot up I have no issues with the functionality or sound. Hopefully they can fix the font issue quickly. Trying to stay positive but disappointed with this release. |
|
LCSeminole
Global Moderator 
Res firma mitescere nescit.
Posts: 20,867
|
Post by LCSeminole on Nov 27, 2022 13:06:12 GMT -5
Updated on release day. No issues updating. If fully powering down I get the updating fonts message. I just use the VRO and no issues. The A4K had Atmos issues initially but a reboot of the A4K fixed it. I get NO pops or clicks like before. It use to be really bad with Loudness on but now it works fine. So far I have found no issues with everything I have thrown at it but I am only using A4K and a 4K player. After running for about a week the clicks and pops came back. I can’t run with VRO without the processor getting buggy. I switched it back to low power mode so it does the full startup and shutdown each time. I get the Font issue upon startup which sucks and adds a lot more boot time. Other than the super slow boot up I have no issues with the functionality or sound. Hopefully they can fix the font issue quickly. Trying to stay positive but disappointed with this release. Interesting that your pops and clicks came back. I've only been getting the pops/clicks with my ATV4K as the source and interestingly enough, they lessened(not totally gone away) when iOS 16 was installed. Admittedly they don't bother me at all, especially since they only occur when navigating the ATV4K's UI, and I can't remember when they weren't a problem of sorts. Hopefully the new HDMI engineer cleaning up the code can do just that make them dissappear, as for the Font issue I'd bet that issue will be cleared up fairly soon in the next firmware update. Just to poke a little fun here and lighten the mood some, if your pops and clicks came back this week, maybe that was a precursor of the outcome in the Horseshoe yesterday afternoon! jk |
|
|
|
Post by jasonx on Nov 27, 2022 13:08:15 GMT -5
Hello all.. Upgraded to firmware 3.1 and I have tons of pops and clicks. If it matters all HDMIs are Rupio optical. I followed the instructions to the letter with some additional time as my unit didn't fully reboot after updating. Also For months I have had my processor in lowest power mode due to errors that came up when in "video remains on" mode. (Errors as in distorted audio) I know in the 3.1 instructions I saw that it was recommended to use "video remains on now" which I guess is fine but I had to try it on the lowest power mode and every time the unit boots now it has to spend minutes loading fonts. Is this right? Has anyone else encountered this? I turned it back to "video remains on" but the noise issues I have come back and I eventually have to turn it off at the rear switch or switch it back to lowest power mode.
It also doesn't appear that they have fixed the issues with zone 2 when using balanced inputs. - Volume increases on its own. I just avoid this buy using coax on zone 2. Not exactly what I want.
|
|
|
|
Post by foggy1956 on Nov 27, 2022 14:12:47 GMT -5
After running for about a week the clicks and pops came back. I can’t run with VRO without the processor getting buggy. I switched it back to low power mode so it does the full startup and shutdown each time. I get the Font issue upon startup which sucks and adds a lot more boot time. Other than the super slow boot up I have no issues with the functionality or sound. Hopefully they can fix the font issue quickly. Trying to stay positive but disappointed with this release. Interesting that your pops and clicks came back. I've only been getting the pops/clicks with my ATV4K as the source and interestingly enough, they lessened(not totally gone away) when iOS 16 was installed. Admittedly they don't bother me at all, especially since they only occur when navigating the ATV4K's UI, and I can't remember when they weren't a problem of sorts. Hopefully the new HDMI engineer cleaning up the code can do just that make them dissappear, as for the Font issue I'd bet that issue will be cleared up fairly soon in the next firmware update. Just to poke a little fun here and lighten the mood some, if your pops and clicks came back this week, maybe that was a precursor of the outcome in the Horseshoe yesterday afternoon! jk Nice to hear that you believe the next firmware update will come fairly soon.🙂 |
|
|
|
Post by Goodfella on Nov 27, 2022 17:13:39 GMT -5
Interesting that your pops and clicks came back. I've only been getting the pops/clicks with my ATV4K as the source and interestingly enough, they lessened(not totally gone away) when iOS 16 was installed. Admittedly they don't bother me at all, especially since they only occur when navigating the ATV4K's UI, and I can't remember when they weren't a problem of sorts. Hopefully the new HDMI engineer cleaning up the code can do just that make them dissappear, as for the Font issue I'd bet that issue will be cleared up fairly soon in the next firmware update. Just to poke a little fun here and lighten the mood some, if your pops and clicks came back this week, maybe that was a precursor of the outcome in the Horseshoe yesterday afternoon! jk Nice to hear that you believe the next firmware update will come fairly soon.🙂 The wounds haven’t healed yet from yesterday’s game yet. Definitely don’t want to talk about that one. I didn’t say I believed the next software version would come out soon, I said hoped the next firmware would be out soon. I know better than to say it would be out soon. |
|
cawgijoe
Emo VIPs 
"When you come to a fork in the road, take it." - Yogi Berra
Posts: 5,035
|
Post by cawgijoe on Nov 27, 2022 17:26:48 GMT -5
Nice to hear that you believe the next firmware update will come fairly soon.🙂 The wounds haven’t healed yet from yesterday’s game yet. Definitely don’t want to talk about that one. I didn’t say I believed the next software version would come out soon, I said hoped the next firmware would be out soon. I know better than to say it would be out soon. I have confidence in the new guy…..thinking positive! |
|
|
|
Post by geebo on Nov 27, 2022 17:30:29 GMT -5
Nice to hear that you believe the next firmware update will come fairly soon.🙂 The wounds haven’t healed yet from yesterday’s game yet. Definitely don’t want to talk about that one. I didn’t say I believed the next software version would come out soon, I said hoped the next firmware would be out soon. I know better than to say it would be out soon. I thought it was a GREAT game. Especially the 4th quarter.  |
|
|
|
Post by Goodfella on Nov 27, 2022 17:47:00 GMT -5
The wounds haven’t healed yet from yesterday’s game yet. Definitely don’t want to talk about that one. I didn’t say I believed the next software version would come out soon, I said hoped the next firmware would be out soon. I know better than to say it would be out soon. I thought it was a GREAT game. Especially the 4th quarter. Ouch! |
|
|
|
Post by foggy1956 on Nov 27, 2022 17:51:27 GMT -5
Nice to hear that you believe the next firmware update will come fairly soon.🙂 The wounds haven’t healed yet from yesterday’s game yet. Definitely don’t want to talk about that one. I didn’t say I believed the next software version would come out soon, I said hoped the next firmware would be out soon. I know better than to say it would be out soon. Apologies, I thought I was responding toLCSeminoles post about the relatively soon next update, especially considering his standing here.🙂 |
|
xeno
Minor Hero
Posts: 50
|
Post by xeno on Nov 28, 2022 4:49:59 GMT -5
I'm starting to wonder if, after updating I shouldn't have reinstalled my saved settings.
My RMC-1L is acting exactly as it did before the firmware update. Maybe I'll give it another go without saving my settings.
Worth a shot?
|
|
|
|
Post by PaulBe on Nov 28, 2022 6:59:54 GMT -5
I'm starting to wonder if, after updating I shouldn't have reinstalled my saved settings. My RMC-1L is acting exactly as it did before the firmware update. Maybe I'll give it another go without saving my settings. Worth a shot? One of the definitions of insanity is ‘doing the same things and expecting different results’. I think the insane thing with the FW updates is ‘doing the same operating things and constantly getting different results’. Humanizing this – the FW seems to have a mind of its own. Perhaps we who are having problems have hardware that is marginally stable, and not readily discoverable with normal troubleshooting techniques. Sometimes, it’s time for a board swap. I backed up and restored settings. I did a Factory Reset and manually entered my settings. Post FW 3.1, some problems are… less problematic. Some problems are new. Some come and go. Nothing definitive except for the loss of middle height channels, no matter what I have tried to do. Everyone wanted the RMC to respond faster. Now it responds faster, and seems more unstable for some people. Supposedly, 2000 owners updated the FW and are happy. I’m trying to make lemonade. Short answer – it’s hard to know what is worth a shot. Perhaps EMO should dwell on what is common with the problem units and fix or replace those units. New FW is not fixing all the problems. |
|
cawgijoe
Emo VIPs
"When you come to a fork in the road, take it." - Yogi Berra
Posts: 5,035
|
Post by cawgijoe on Nov 28, 2022 8:25:53 GMT -5
I'm starting to wonder if, after updating I shouldn't have reinstalled my saved settings. My RMC-1L is acting exactly as it did before the firmware update. Maybe I'll give it another go without saving my settings. Worth a shot? One of the definitions of insanity is ‘doing the same things and expecting different results’. I think the insane thing with the FW updates is ‘doing the same operating things and constantly getting different results’. Humanizing this – the FW seems to have a mind of its own. Perhaps we who are having problems have hardware that is marginally stable, and not readily discoverable with normal troubleshooting techniques. Sometimes, it’s time for a board swap. I backed up and restored settings. I did a Factory Reset and manually entered my settings. Post FW 3.1, some problems are… less problematic. Some problems are new. Some come and go. Nothing definitive except for the loss of middle height channels, no matter what I have tried to do. Everyone wanted the RMC to respond faster. Now it responds faster, and seems more unstable for some people. Supposedly, 2000 owners updated the FW and are happy. I’m trying to make lemonade. Short answer – it’s hard to know what is worth a shot. Perhaps EMO should dwell on what is common with the problem units and fix or replace those units. New FW is not fixing all the problems. It appears that a majority are either happy or have minor issues that are superceded by improvements. I am one of those that are 95% happy with the new firmware update. The only fix I need is the low sound volume from the TV speakers when using VRO and of course the long low power startup issue that we all have. Other than that, I can't complain with my simple 5.1 system. Not using ARC/CEC, so that is out of the loop. I agree that Emo should work to find common ground on the real problematic units and to focus on fixing their issues. If that involves a direct return and replacement, maybe thats the way to go and would certainly garnish high approval even though the cost may be significant for a small company. Edit: If you do have significant issues, please report to Emotive support via email or phone. They are asking for that. |
|
|
|
Post by vmbray on Nov 28, 2022 8:53:01 GMT -5
The ‘updating fonts’ step does not go away and keeps doing it at each cold boot. Is that supposed to be like this? It says complete each time as well. annoying, as it adds time to the cold boot Having exactly this after the update. Was on 2.3 prior to the update. Did all the steps, backup, reset factory, flashed, reset, restored. |
|
|
|
Post by PaulBe on Nov 28, 2022 9:00:48 GMT -5
One of the definitions of insanity is ‘doing the same things and expecting different results’. I think the insane thing with the FW updates is ‘doing the same operating things and constantly getting different results’. Humanizing this – the FW seems to have a mind of its own. Perhaps we who are having problems have hardware that is marginally stable, and not readily discoverable with normal troubleshooting techniques. Sometimes, it’s time for a board swap. I backed up and restored settings. I did a Factory Reset and manually entered my settings. Post FW 3.1, some problems are… less problematic. Some problems are new. Some come and go. Nothing definitive except for the loss of middle height channels, no matter what I have tried to do. Everyone wanted the RMC to respond faster. Now it responds faster, and seems more unstable for some people. Supposedly, 2000 owners updated the FW and are happy. I’m trying to make lemonade. Short answer – it’s hard to know what is worth a shot. Perhaps EMO should dwell on what is common with the problem units and fix or replace those units. New FW is not fixing all the problems. It appears that a majority are either happy or have minor issues that are superceded by improvements. I am one of those that are 95% happy with the new firmware update. The only fix I need is the low sound volume from the TV speakers when using VRO and of course the long low power startup issue that we all have. Other than that, I can't complain with my simple 5.1 system. Not using ARC/CEC, so that is out of the loop. I agree that Emo should work to find common ground on the real problematic units and to focus on fixing their issues. If that involves a direct return and replacement, maybe thats the way to go and would certainly garnish high approval even though the cost may be significant for a small company. Edit: If you do have significant issues, please report to Emotive support via email or phone. They are asking for that. I have the Update Fonts issue. I thought is was established that this is an issue for people with a series 8 HDMI board, and doesn't affect use. I don't use ARC/CEC. My system is also relatively simple, but with higher channel count. I do have a ticket with EMO. Lonnie was working diligently on my problem. We are communicating. I suggested he stop for Thanksgiving, and go home and enjoy his family.  My little processor problems can wait. |
|
|
|
Post by vmbray on Nov 28, 2022 9:33:38 GMT -5
Maybe it's just me but it seems like it would be good if the low power state could be a separate feature from the hdmi remains on. The processor here is on an atlona matrix with only other surround sound devices, I'll have to try it again with new firmware but on 2.3 when I turned off the xmc2 it would cause hdmi dropouts to randomly start happening on the other displays on the matrix. Turning off low power mode and booting the processor cured this issue, it would just be nice to be able to quick boot but also not have hdmi on.
The other issue I'm having is hdmi sync with apple tv 4k g3, (apple tv -> xmc2 -> jvc rs520) where i get a black screen on startup. Pulling hdmi off the atv and reconnecting it fixes it every time. Hdmi to pj is a ruipro fiber, also the atv to xmc hdmi is a zeskit, both certified cables known to work well. It seems like apple tv interaction with xmc2 but I'm not sure. I can start a ticket if that would help, just curious if other people were experiencing this.
|
|
|
|
Post by geebo on Nov 28, 2022 9:41:01 GMT -5
The ‘updating fonts’ step does not go away and keeps doing it at each cold boot. Is that supposed to be like this? It says complete each time as well. annoying, as it adds time to the cold boot Having exactly this after the update. Was on 2.3 prior to the update. Did all the steps, backup, reset factory, flashed, reset, restored. The updating of fonts on every low power boot is common on units with the original version of the HDMI board. Emotiva knows about it and is working on a fix. If you use VRO (Video Remains On) the fonts updating does not occur. It causes no problems other than the extended boot time. |
|
|
|
Post by jasonx on Nov 28, 2022 9:43:19 GMT -5
I am curious... For the other users of the Ruipro Optical HDMI cables are any of you using the power device that comes with the cable? I am not and I can not get audio to pass to the TV from source with "Video remains on"
|
|
KeithL
Administrator
Posts: 10,276
|
Post by KeithL on Nov 28, 2022 10:09:00 GMT -5
HDMI switches are active devices which consume power... (so there's no way to pass HDMI through the processor unless they are powered). And, in addition to that, when we pass audio in "video remains on" mode we also do some audio processing. Therefore it is not possible to continue to pass a signal to the TV while in "low power standby mode". (The way a device can consume such little power in low power standby mode is to only leave on the circuitry that "listens for the Turn On command".) I don't know anything about the Atlona Matrix device... However it is not uncommon for HDMI devices to repeatedly attempt to complete an "HDMI handshake" with other devices that are off. (And, when this occurs, it can cause the sorts of random dropouts you describe.) Maybe it's just me but it seems like it would be good if the low power state could be a separate feature from the hdmi remains on. The processor here is on an atlona matrix with only other surround sound devices, I'll have to try it again with new firmware but on 2.3 when I turned off the xmc2 it would cause hdmi dropouts to randomly start happening on the other displays on the matrix. Turning off low power mode and booting the processor cured this issue, it would just be nice to be able to quick boot but also not have hdmi on. The other issue I'm having is hdmi sync with apple tv 4k g3, (apple tv -> xmc2 -> jvc rs520) where i get a black screen on startup. Pulling hdmi off the atv and reconnecting it fixes it every time. Hdmi to pj is a ruipro fiber, also the atv to xmc hdmi is a zeskit, both certified cables known to work well. It seems like apple tv interaction with xmc2 but I'm not sure. I can start a ticket if that would help, just curious if other people were experiencing this. |
|
My little processor problems can wait.
