|
|
Post by ssimon on Feb 23, 2022 9:37:01 GMT -5
I recently upgraded my firmware from 5.4 to 5.8 to 5.15. Since then, my XMC-1 has not been able to start up at the input it was last set to. When I start up the XMC, I get a no input detected on my LG OLED TV though the front panel shows input information.
I have to switch to another input, wait for it to finishing switching, then switch back to the first input source for that input to work (e.g. HDMI 1 to HDMI 2 back to HDMI 1). This is pretty frustrating. Been a Emotiva shop since 2009, first time having an issue. Anyone else have this issue and how to resolve? Thanks
|
|
|
|
Post by ttocs on Feb 23, 2022 10:00:59 GMT -5
I recently upgraded my firmware from 5.4 to 5.8 to 5.15. Since then, my XMC-1 has not been able to start up at the input it was last set to. When I start up the XMC, I get a no input detected on my LG OLED TV though the front panel shows input information. I have to switch to another input, wait for it to finishing switching, then switch back to the first input source for that input to work (e.g. HDMI 1 to HDMI 2 back to HDMI 1). This is pretty frustrating. Been a Emotiva shop since 2009, first time having an issue. Anyone else have this issue and how to resolve? Thanks Should've looked at this thread first, responded to the other one. Assuming all was well prior to the firmware update, then do the following. Unplug power for both the XMC-1 and tv for at least a few minutes. Turn on tv first and wait for it to fully boot. Turn on processor. If this doesn't work, then you'll need to do a Factory Reset of the XMC-1, and repeat the steps above. |
|
|
|
Post by AudioHTIT on Feb 23, 2022 11:13:08 GMT -5
I recently upgraded my firmware from 5.4 to 5.8 to 5.15. Since then, my XMC-1 has not been able to start up at the input it was last set to. When I start up the XMC, I get a no input detected on my LG OLED TV though the front panel shows input information. I have to switch to another input, wait for it to finishing switching, then switch back to the first input source for that input to work (e.g. HDMI 1 to HDMI 2 back to HDMI 1). This is pretty frustrating. Been a Emotiva shop since 2009, first time having an issue. Anyone else have this issue and how to resolve? Thanks Should've looked at this thread first, responded to the other one. Assuming all was well prior to the firmware update, then do the following. Unplug power for both the XMC-1 and tv for at least a few minutes. Turn on tv first and wait for it to fully boot. Turn on processor. If this doesn't work, then you'll need to do a Factory Reset of the XMC-1, and repeat the steps above. Could this be related to the bug we found in 2.3 where they added an additional video reset? As I remember it worked if you used a ‘button command’, but not if you use a ‘discrete command’, I realize this is slightly different, but maybe they put that same video reset in the XMC-1 code. Your recommendation, should narrow it down. Edit: I may also remember that when this ‘reset’ caused a problem, the video always ended up on HDMI 1. |
|
|
|
Post by ttocs on Feb 23, 2022 11:28:43 GMT -5
Should've looked at this thread first, responded to the other one. Assuming all was well prior to the firmware update, then do the following. Unplug power for both the XMC-1 and tv for at least a few minutes. Turn on tv first and wait for it to fully boot. Turn on processor. If this doesn't work, then you'll need to do a Factory Reset of the XMC-1, and repeat the steps above. Could this be related to the bug we found in 2.3 where they added an additional video reset? As I remember it worked if you used a ‘button command’, but not if you use a ‘discrete command’, I realize this is slightly different, but maybe they put that same video reset in the XMC-1 code. Your recommendation, should narrow it down. Edit: I may also remember that when this ‘reset’ caused a problem, the video always ended up on HDMI 1. Yes, I recall that now that you mention it. So an easy check would be to set the Turn On Input to something other than HDMI 1, correct? |
|
|
|
Post by AudioHTIT on Feb 23, 2022 11:40:24 GMT -5
Could this be related to the bug we found in 2.3 where they added an additional video reset? As I remember it worked if you used a ‘button command’, but not if you use a ‘discrete command’, I realize this is slightly different, but maybe they put that same video reset in the XMC-1 code. Your recommendation, should narrow it down. Edit: I may also remember that when this ‘reset’ caused a problem, the video always ended up on HDMI 1. Yes, I recall that now that you mention it. So an easy check would be to set the Turn On Input to something other than HDMI 1, correct? That seems reasonable, though if it’s set to ‘Last Used’, and regardless of which input is used ‘Last’ it always ends up on HDMI 1, that may also tell us this is the culprit. |
|
