|
Post by doc1963 on Aug 8, 2020 1:33:40 GMT -5
That should not make sense... the firmware is checksummed... no matter how many times you apply it, if it succeeds it should be the same result *. Not I said, it should... so I am not saying you are wrong, but as a softweare developer who has written plenty of firmware patches and upgrades, this does not make sense to me. * Yes, there is a possibility of a startup memory corruption after F/W update... but I don't see the kind of reports that would suggest that is the case I agree, and we thought the same thing. No one could explain “why”, but it seemed to work... and for more than just one or two of us. Some of us just adopted the following routine with any firmware update for the XMC-1 with the V3 board... Update > Reset > Re-flash > Cold Reboot > Restore User Settings Prior to the XMC-1’s 2.0b HDMI board upgrade, you didn’t have to do this to get a firmware flash to stick.
|
|
|
Post by markc on Aug 8, 2020 5:20:02 GMT -5
So at least for now it's usable. That's a good thing. No lock up's with 1.10? Correct that is why I'm leaving it on 1.10 until the next firmware is released. Me too. I took the plunge and Upgraded (from 2.0) to firmware 1.10 this morning. The good news; the firmware actually installed correctly all the way to the end first time!!!! (More often than not, one part or other usually hangs or it doesn’t reboot at the end) The better news: My XMC-2 now functions as it should (mostly. Neural:X *cough*) and Dirac would not be worth losing that! The best news; no bricked unit (I held my breath for an awfully long time watching the update!)
|
|
|
Post by thxultra on Aug 10, 2020 9:05:33 GMT -5
Correct that is why I'm leaving it on 1.10 until the next firmware is released. Me too. I took the plunge and Upgraded (from 2.0) to firmware 1.10 this morning. The good news; the firmware actually installed correctly all the way to the end first time!!!! (More often than not, one part or other usually hangs or it doesn’t reboot at the end) The better news: My XMC-2 now functions as it should (mostly. Neural:X *cough*) and Dirac would not be worth losing that! The best news; no bricked unit (I held my breath for an awfully long time watching the update!) Did the same thing. I don't have my DIRAC box yet anyway and I would rather have a working processor without DIRAC then one that is completely unusable with version 2.0. I did just get a new TV so going to try 2.0 again with the new TV and see if it is stable, keeping my fingers crossed.
|
|
|
Post by markc on Aug 10, 2020 16:53:12 GMT -5
Erm, it is not the TV that has any role in what does (and does not) happen with 2.0 firmware. Just wait until you can either try firmware 2.1 or until you so desperately need Dirac room correction that you are willing to suffer the inconvenience of a broken Processor.
I’ve had a few days of fault free enjoyment of my XMC-2 version 1.10
One things strikes me: we don’t know who the beta testers are. I would also keep quiet if I were them as the beta fanboys falsely reassured Emotiva that they could release this firmware. Shame on them!
|
|
|
Post by JKCashin on Aug 10, 2020 18:13:47 GMT -5
Erm, it is not the TV that has any role in what does (and does not) happen with 2.0 firmware. Just wait until you can either try firmware 2.1 or until you so desperately need Dirac room correction that you are willing to suffer the inconvenience of a broken Processor. I disagree... sort of. I has mostly flawless XMC-2 performance, and then switched to a new TV with HDMI 2.0. I now get at least once a day lockups that NEVER happened with the 1.4HDMI TV. So, while it may not be the TV, it could be the HDMI 2.0. I was(and still am) getting several times a day audio lockups as well.. and that seemed to have worsened until I found some startup sequences that lessened the issue.
|
|
|
Post by megash0n on Aug 10, 2020 19:32:34 GMT -5
Erm, it is not the TV that has any role in what does (and does not) happen with 2.0 firmware. Just wait until you can either try firmware 2.1 or until you so desperately need Dirac room correction that you are willing to suffer the inconvenience of a broken Processor. I disagree... sort of. I has mostly flawless XMC-2 performance, and then switched to a new TV with HDMI 2.0. I now get at least once a day lockups that NEVER happened with the 1.4HDMI TV. So, while it may not be the TV, it could be the HDMI 2.0. I was(and still am) getting several times a day audio lockups as well.. and that seemed to have worsened until I found some startup sequences that lessened the issue. It seems like most of the issues, dating back to the xmc-1 days, are HDMI 2.0 issues. Whether proper implementation has been performed or not, clearly other companies are either buying more stable hardware, write code better, or write really good error handling.
|
|
|
Post by creimes on Aug 11, 2020 1:56:49 GMT -5
I disagree... sort of. I has mostly flawless XMC-2 performance, and then switched to a new TV with HDMI 2.0. I now get at least once a day lockups that NEVER happened with the 1.4HDMI TV. So, while it may not be the TV, it could be the HDMI 2.0. I was(and still am) getting several times a day audio lockups as well.. and that seemed to have worsened until I found some startup sequences that lessened the issue. It seems like most of the issues, dating back to the xmc-1 days, are HDMI 2.0 issues. Whether proper implementation has been performed or not, clearly other companies are either buying more stable hardware, write code better, or write really good error handling. Are you excited about 8K... yikes
|
|
|
Post by creimes on Aug 11, 2020 1:58:22 GMT -5
Erm, it is not the TV that has any role in what does (and does not) happen with 2.0 firmware. Just wait until you can either try firmware 2.1 or until you so desperately need Dirac room correction that you are willing to suffer the inconvenience of a broken Processor. I disagree... sort of. I has mostly flawless XMC-2 performance, and then switched to a new TV with HDMI 2.0. I now get at least once a day lockups that NEVER happened with the 1.4HDMI TV. So, while it may not be the TV, it could be the HDMI 2.0. I was(and still am) getting several times a day audio lockups as well.. and that seemed to have worsened until I found some startup sequences that lessened the issue. I'm still in the 1080p boat and will be for a long time, maybe that's why I have less issues than many here as I'm still stuck in the olden days of 2k hahaha but I'm totally fine with my 100" HD screen and the sound is really really great
|
|
|
Post by markc on Aug 11, 2020 5:30:59 GMT -5
Erm, it is not the TV that has any role in what does (and does not) happen with 2.0 firmware. Just wait until you can either try firmware 2.1 or until you so desperately need Dirac room correction that you are willing to suffer the inconvenience of a broken Processor. I disagree... sort of. I has mostly flawless XMC-2 performance, and then switched to a new TV with HDMI 2.0. I now get at least once a day lockups that NEVER happened with the 1.4HDMI TV. So, while it may not be the TV, it could be the HDMI 2.0. I was(and still am) getting several times a day audio lockups as well.. and that seemed to have worsened until I found some startup sequences that lessened the issue. I'll wager my own XMC-2 that you go to 1.10 firmware and that your HDMI 2.0 TV that broke your Firmware 2.0 XMC-2 now works. Ergo, it is the 2.0 firmware and not the HDMI 2.0 and not the TV. Fact: All of it works on 1.10 (peoples quibbles were about implementation more than function: Neural X, Bi-amp using fronts, aberrations of Top vs Height speaker configurations. No posts about a non functioning/breaking/locking up/Hard resets on the Processors with 1.10
|
|
|
Post by JKCashin on Aug 11, 2020 13:51:41 GMT -5
I disagree... sort of. I has mostly flawless XMC-2 performance, and then switched to a new TV with HDMI 2.0. I now get at least once a day lockups that NEVER happened with the 1.4HDMI TV. So, while it may not be the TV, it could be the HDMI 2.0. I was(and still am) getting several times a day audio lockups as well.. and that seemed to have worsened until I found some startup sequences that lessened the issue. I'll wager my own XMC-2 that you go to 1.10 firmware and that your HDMI 2.0 TV that broke your Firmware 2.0 XMC-2 now works. Ergo, it is the 2.0 firmware and not the HDMI 2.0 and not the TV. Fact: All of it works on 1.10 (peoples quibbles were about implementation more than function: Neural X, Bi-amp using fronts, aberrations of Top vs Height speaker configurations. No posts about a non functioning/breaking/locking up/Hard resets on the Processors with 1.10 I must have misread you the first time... yes I agree 100% with your premise.
|
|
|
Post by mikoz on Aug 12, 2020 20:14:05 GMT -5
Not very happy right now. Three times in two days have had to power down my unit because it lost audio and switching outputs didn't fix it. I use Video on in standby and have had no audio three times when powering up. I also had weird issues with one of my subwoofer channels failing to work when setting levels then it suddenly re-appeared. Haven't been this frustrated since ver. 1.0 . This doesn't bode well for Dirac. since right now I don't really even want to continue with this. I'm going to try re-installing 2.0, do the hokey pokey, plug unplug, turn the world off then on again and see where I stand. (and yes I followed the instructions for installing 2.0 to the letter the first time). ... and the menu's are way slower than 1.1 - almost like 1.0 go figure. And the network adapter is more finicky than ever - multiple starts/re-starts to get it to work. Yes, waiting and waiting each time 40-60 seconds and even using a static ip address. EDIT. After the re-install menu is more responsive. Will advise about future audio loss etc. must be your cables, both your network and hdmi cables should be replaced. Make sure your house voltage is exactly 120vac rms, if not, call the power company and complain. Check the voltage of the batteries of the remote control, sluggish performance is often attributed to low battery voltage. here is what you should buy for the network cable. The ultra low jitter design will ensure problem free rmc1 operation: www.cnet.com/news/denons-500-ethernet-cable/
|
|
|
Post by JKCashin on Aug 14, 2020 10:21:09 GMT -5
So I have an XMC-2 on 2.0 and I am having issues... like everyone else. I'm confident Emotiva is working on the issues, they have no choice... and I have found a "workflow" that works for me... a way to turn things on and certain orders to do things in that work... again, for me.
So since things "work" for me, I am thinking of putting my head in the sand for a while, but I have yet to do so... I am fearful i will miss the 2.1 update which will fix 10 things (and maybe break 2) Am I alone?
|
|
cawgijoe
Emo VIPs
"We made too many of the wrong mistakes." - Yogi Berra
Posts: 4,920
|
Post by cawgijoe on Aug 14, 2020 10:34:06 GMT -5
So I have an XMC-2 on 2.0 and I am having issues... like everyone else. I'm confident Emotiva is working on the issues, they have no choice... and I have found a "workflow" that works for me... a way to turn things on and certain orders to do things in that work... again, for me. So since things "work" for me, I am thinking of putting my head in the sand for a while, but I have yet to do so... I am fearful i will miss the 2.1 update which will fix 10 things (and maybe break 2) Am I alone? Yes, many if not most are having issues with 2.0, I have the "lost audio" problem....they are working on fixing 2.0. Hopefully a general release soon once the Beta testers are good with it.Fingers crossed it goes quickly.
|
|
|
Post by JKCashin on Aug 14, 2020 12:17:35 GMT -5
If it helps any, for some reason I can "fix" the lost audio problem 4/5 times by switching to the TV and playing content back through ARC. THen I reduce the volume pretty much to a whisper, and stop the content from the smart TV... then I go back to the original source that I lost audio on, and 4/5 of the time things. If the sound comes back through ARC, it will work. If the volume control stays in a fixed position when I try to change it, it's time for a reboot... that's the 1/5 of the time.
Reducing the volume has two purposes. First, if the volume stays stuck as mentioned, or won't respond, then there's no point in continuing, you're in for a reboot. Second, when you do switch sources, there is a loud "snap" sound... a single click like sound, but loud. Turning things down makes sure you don't cause damage.
This technique only seems to work by switching to an ARC source... switching to any other HDMI source won't work, and in fact makes things worse.
|
|
|
Post by superhelmi on Aug 17, 2020 1:53:13 GMT -5
Hi,
I also had the "lost of audio" three times with my XMC-2. I figured out, with lowest power standby ! , following helps: Disconnect the HDMI source, you are watching and caused the lost of audio. Switch the processor off (with remote, the front button was not working on my unit) switch it on again I switched to a another input, but it is not necessary, I think. connect the HDMI source again and switch to it The processor should work again !
Markus
|
|
|
Post by 5channels on Aug 17, 2020 7:58:00 GMT -5
For someone who has all of their equipment in a special closet in the basement under my media room, all of this resetting power, unplugging cables and spinning a rubber chicken in the air three times is entirely unacceptable. That being said, none of this should be required, no matter where your gear is located.
I am waiting on both my Dirac kit and the new firmware
Cheers J
|
|
cawgijoe
Emo VIPs
"We made too many of the wrong mistakes." - Yogi Berra
Posts: 4,920
|
Post by cawgijoe on Aug 17, 2020 8:17:47 GMT -5
For someone who has all of their equipment in a special closet in the basement under my media room, all of this resetting power, unplugging cables and spinning a rubber chicken in the air three times is entirely unacceptable. That being said, none of this should be required, no matter where your gear is located. I am waiting on both my Dirac kit and the new firmware Cheers J Hopefully you will be able to throw out the rubber chicken soon....
|
|
|
Post by foggy1956 on Aug 17, 2020 8:28:44 GMT -5
For someone who has all of their equipment in a special closet in the basement under my media room, all of this resetting power, unplugging cables and spinning a rubber chicken in the air three times is entirely unacceptable. That being said, none of this should be required, no matter where your gear is located. I am waiting on both my Dirac kit and the new firmware Cheers J Hopefully you will be able to throw out the rubber chicken soon.... If he doesn't have the kit or the firmware yet, how does he even know he'll need the chicken? I haven't.
|
|
|
Post by 5channels on Aug 17, 2020 9:13:03 GMT -5
Perhaps a rubber chicken should be included in each kit going forward
Cheers J
|
|
|
Post by markc on Aug 17, 2020 9:22:05 GMT -5
Hopefully you will be able to throw out the rubber chicken soon.... If he doesn't have the kit or the firmware yet, how does he even know he'll need the chicken? I haven't. The "rubber chicken" voodoo is used to compensate for the terrible effects of the 2.0 firmware that he mentioned which interrupt listening and usage of the Processors.. As far as I am aware from reading here, being able to run Dirac doesn't make any of the problems worse, but it certainly doesn't remove even one of them. Wacky hair-tearing out escapades to get back to actual watching and listening (rubber chicken or not) are required in spite of Dirac, not because of it. By the new firmware, I would hope that for his sanity, 5channels is referring to firmware 2.x where x>0
|
|