|
|
Post by rbk123 on Sept 12, 2018 13:46:37 GMT -5
I agree with Mark, especially if the OP swapped channels and speaker wires (not at the same time) and the behavior didn't follow the swap.
|
|
KeithL
Administrator 
Posts: 10,261
|
Post by KeithL on Sept 12, 2018 15:33:06 GMT -5
Actually, it could... for a few reasons.
When detecting the location of the speakers, EmoQ basically sends a test tone out of each speaker, then "listens" for when that sound arrives at the microphone. However, because the distances involved are short, it's not as simple as "listening for when the sound starts"; it's more like looking for the actual shape of the arriving wavefront. (Imagine throwing a stone out into a lake, then watching for when the first ripple arrives at your position.)
If the wavefront is altered enough that EmoQ fails to recognize it properly, or to be able to see exactly where the leading edge is, then the speaker won't be detected properly. This is what sometimes happens with dipoles - and with rooms with odd acoustics - the wavefront is "distorted" enough in time that EmoQ "doesn't see it clearly".
Class-D amps sometimes introduce phase shift or time delay into the signal (among other things). This alteration is going to be added to any changes already there due to your room and your speakers... and, taken together, they could be enough to "throw things off". (I should reassure everyone that this doesn't USUALLY happen, but it does occasionally.)
I recall a specific instance where a customer had a multi-channel Class-D amp, with seemingly identical channels, and all identical speakers, and EmoQ on the processor would only recognize certain channels. It turned out that, at some point, he had added more channels to the amplifier, and the amplifier modules used for the added channels were slightly different. (EmoQ worked perfectly with all the newer channels, and not the older ones... or maybe it was the other way around... and, yes, they all sounded exactly the same.)
Things like this don't happen often... but they do happen. 
Depending on the actual firmware version involved, sometimes the MC-700 will not be willing to do a direct re-flash. Basically, if it sees that you're trying to install the same version as it already has, it may just skip the install. The firmware update on the MC-700 is pretty quick, and it doesn;t really tell you what's going on, so you have no way to know.
That's why sometimes you have to install a different version, then reinstall the original one, to re-flash it.)
I should also note that the NuForce Amp is a Class-D design... And we have occasionally seen cases where EmoQ had trouble with Class-D amplifiers. (Because of how they work, and especially the output reconstruction filters, some Class-D amps create unusual delays and phase shifts in the audio signal, a few of which seem to confuse EmoQ.)
Would it be likely that a class D amp would create an issue for 1 channel yet not another? I would think not. In any case, as a Emotiva rep, would you reco the user try a fresh re-flash of FW? Mark |
|
|
|
Post by reverbero on Sept 12, 2018 18:10:58 GMT -5
The problem was solved by installing the previous version, 2.9.2. Perhaps the new firmware and the amplifier, a Nuforce MCA-18, were incompatible. I doubt that. I would bet you just had a bad flash of the new FW. The calibration system and FW have no idea what amp you have, and I cannot imagine any "incompatibility" Mark I was guided only by intuition when I said there might be incompatibility between the new firmware and the amplifier. I probably did a bad installation of the firmware but it's that same intuition that tells me that if I reinstall version 2.9.3 the same problem would arise. |
|
|
|
Post by reverbero on Sept 12, 2018 18:26:57 GMT -5
Thanks to all of you who have been interested in this issue and helped me to resolve it, especially Keith and Mark.
|
|
klinemj
Emo VIPs 
Official Emofest Scribe
Posts: 15,086
|
Post by klinemj on Sept 12, 2018 20:03:31 GMT -5
I doubt that. I would bet you just had a bad flash of the new FW. The calibration system and FW have no idea what amp you have, and I cannot imagine any "incompatibility" Mark I was guided only by intuition when I said there might be incompatibility between the new firmware and the amplifier. I probably did a bad installation of the firmware but it's that same intuition that tells me that if I reinstall version 2.9.3 the same problem would arise. Personally, now that you've gone back to the old FW successfully, I would try re-flashing the new one (on a clean, newly reformatted USB stick) and see if you have better results. Per Keith's last note - it's possible there was a bad flash. And, if you switch from the old version back to the new - things might be fine. My intuition says it's worth trying. Good luck! Mark |
|
|
|
Post by Tarzan on Mar 24, 2019 2:33:03 GMT -5
Be great if I could get my mc700 working as it should, this unit could for-full all my needs. Quite frankly this is unacceptable. I'm sure I don't need to regurgitate all the issues from the MC700 thread. Really disappointed. Don't advertise what you can't deliver. I hope that one day ARC will work along with Apple4k TV.
|
|
