|
|
Post by trevordj on Sept 14, 2015 13:49:16 GMT -5
Ok. I will try it and see what happens. It can't hurt!
|
|
|
|
Post by wizardofoz on Sept 15, 2015 0:47:58 GMT -5
as I said before plasma tvs are very IR noisy as are some compact fluro tubes and maybe even LED bulbs (especially when in dimmed modes) but that just narrows down the problem turning off the IR detection.
I had a Parasound P7 that did a similar thing with random noise coming from the RS232 port...and a bad/failing filter on a plasma tv that wreaked havoc on my UMC-1
all that said sounds more likely you are having a faulty front panel perhaps or some other board n the chain of command
|
|
|
|
Post by trevordj on Sept 15, 2015 0:55:45 GMT -5
When I talked to Emotiva customer support (Damon) I mentioned that some of you had implicated IR or RFI issues that could be contributing to this problem. He said that there were no reported cases that he knew of with the UMC-200 or XMC-1 where this was the case. That being said, I actually turned off the XMC-1 IR blaster in the system setup advanced settings and, so far, the issue has not repeated itself. It is still too early to tell but I will test it for another few days before I get too excited. You guys may be on to something here!
Emotiva customer support seemed to lock on to the fact that I am playing content from a HTPC to the XMC-1 through HDMI. They said there is a known issue where playing MP3s at varying bitrates to the XMC-1 can cause issues similar to what I am experiencing. I told him this didn't apply to my scenario as a) I very rarely play MP3s through my HTPC to the XMC-1 and, as far as I know, the unit has never frozen while playing music b) the issue happens even when playing content through my Tivo or Oppo 103D (doesn't seem to be related to one media type or device) and c) This issue happens even when the device is starting up after a period of inactivity, before any content is played. I am just including this information in case anyone else runs into this issue and wants to compare notes.
|
|
|
|
Post by geebo on Sept 15, 2015 7:42:58 GMT -5
When I talked to Emotiva customer support (Damon) I mentioned that some of you had implicated IR or RFI issues that could be contributing to this problem. He said that there were no reported cases that he knew of with the UMC-200 or XMC-1 where this was the case. That being said, I actually turned off the XMC-1 IR blaster in the system setup advanced settings and, so far, the issue has not repeated itself. It is still too early to tell but I will test it for another few days before I get too excited. You guys may be on to something here! Emotiva customer support seemed to lock on to the fact that I am playing content from a HTPC to the XMC-1 through HDMI. They said there is a known issue where playing MP3s at varying bitrates to the XMC-1 can cause issues similar to what I am experiencing. I told him this didn't apply to my scenario as a) I very rarely play MP3s through my HTPC to the XMC-1 and, as far as I know, the unit has never frozen while playing music b) the issue happens even when playing content through my Tivo or Oppo 103D (doesn't seem to be related to one media type or device) and c) This issue happens even when the device is starting up after a period of inactivity, before any content is played. I am just including this information in case anyone else runs into this issue and wants to compare notes. Just to be clear, you disabled the Front IR In, right? The front IR blaster shouldn't cause any problems with the XMC. |
|
|
|
Post by trevordj on Sept 15, 2015 10:26:59 GMT -5
No, I actually disabled the IR blaster. My thought process went like this: I already have an IR blaster present from my harmony hub so, since many of you were thinking this could be an IR related issue I was thinking there may be a slight delay between the IR signal coming from my harmony remote and the XMC-1. I checked it again this morning and so far it hasn't frozen since I disabled this last evening. Again, still too early to make any definitive conclusions but it remains promising.
|
|
|
|
Post by wizardofoz on Sept 15, 2015 13:19:53 GMT -5
Blaster is firing out from the xmc...I suggest you disable the receiver too. It might be possible that the blaster is repeating the received signal and getting stuck in a loop I guess
|
|
|
|
Post by trevordj on Sept 15, 2015 16:09:55 GMT -5
Blaster is firing out from the xmc...I suggest you disable the receiver too. It might be possible that the blaster is repeating the received signal and getting stuck in a loop I guess That's what I was thinking as well, receiver and blaster both active may be causing some sort of feedback loop causing the freezing. Since I am not using the IR input in the back (yet) I will see how it goes with just the IR blaster disabled. If that doesn't do the trick I will hardwire IR to the back and disable the IR receiver as well. If all that doesn't work I will send it in for the RMA I received yesterday. It would be nice if I didn't have to send it back though. None of this explains why this occurs even without remote control input however. It even happened when first unboxing the XMC-1 before I even had anything hooked up to it. Hard to say. |
|
|
|
Post by geebo on Sept 15, 2015 16:32:16 GMT -5
Blaster is firing out from the xmc...I suggest you disable the receiver too. It might be possible that the blaster is repeating the received signal and getting stuck in a loop I guess That's what I was thinking as well, receiver and blaster both active may be causing some sort of feedback loop causing the freezing. Since I am not using the IR input in the back (yet) I will see how it goes with just the IR blaster disabled. If that doesn't do the trick I will hardwire IR to the back and disable the IR receiver as well. If all that doesn't work I will send it in for the RMA I received yesterday. It would be nice if I didn't have to send it back though. None of this explains why this occurs even without remote control input however. It even happened when first unboxing the XMC-1 before I even had anything hooked up to it. Hard to say. If the IR receiver sees something it doesn't like or gets confused by then actual IR commands are not necessary. My UMC would do odd things with no one even touching a remote. It also sent out IR that made my Oppo do funny things. The Oppo was connected at it's rear port to the IR output of my UMC. The culprit was my plasma TV and when I covered the IR sensor on the front of my UMC and connected the wire from the Harmony hub directly to the back the problem went away forever. It drove me nuts for awhile and I even opened a ticket with Oppo concerning odd behavior that stopped when I covered that IR sensor. But one day I realized it never happened if the TV was off and It occurred more often the brighter the scene on the TV was. I turned off the IR sensor on my XMC the day I got it and never had the problem with it and the plasma. |
|
|
|
Post by trevordj on Sept 15, 2015 17:17:28 GMT -5
Cool, good to know. That still very well may be the issue. I don't know if I mentioned it, but my equipment is all behind closed cabinet doors (shielded from IR interference associated with the plasma) and the behavior doesn't seem to be affected by opening or closing the cabinet. It is still possible, and I will keep experimenting with it before I send it in.
|
|
|
|
Post by trevordj on Sept 15, 2015 23:09:34 GMT -5
Well damn, the XMC-1 was frozen when I got home for the day. I had to order a 2.5mm to 3.5mm adapter for the harmony hub. As soon as I get that I will hard wire the IR connection and turn off the IR sensor on the XMC-1. I am not holding out much hope. I am pretty sure I will need to use that RMA.
|
|
|
|
Post by trevordj on Sept 19, 2015 21:28:12 GMT -5
Ok, I got the converters from monoprice today. We will see how everything goes the rest of this weekend. If this doesn't fix the problem then its back to Emotiva for repair.
|
|
|
|
Post by trevordj on Sept 20, 2015 15:50:02 GMT -5
So farit has been almost an entire day without the unit freezing. I have been turning it on/off, cycling the menus/inputs to try and induce the behavior and it hasn't happened. Fingers crossed!
|
|
|
|
Post by trevordj on Sept 26, 2015 15:47:38 GMT -5
Well, despite disabling the front IR blaster and IR input this is still happening on (at least) a daily basis. it seems as if the frequency of this happening has dropped somewhat but it still drives me insane. Time to use that RMA  . |
|
|
|
Post by geebo on Sept 26, 2015 16:42:25 GMT -5
Well, despite disabling the front IR blaster and IR input this is still happening on (at least) a daily basis. it seems as if the frequency of this happening has dropped somewhat but it still drives me insane. Time to use that RMA . That bites. I thought you might have had it there. Let us know what Emotiva finds. |
|
|
|
Post by wizardofoz on Sept 27, 2015 3:30:01 GMT -5
Either way defeaturizing the xmc is only a troubleshooting process...ultimately there IS a n issue and RMA is your only option
|
|
|
|
Post by trevordj on Sept 30, 2015 1:17:51 GMT -5
Got it boxed up and shipped out. That is $75 I would have rather spent on something else! I included a detailed description of everything it does and everything I have tried. My biggest worry is sending it back only for them to conclude nothing is wrong. When I spoke to the returns dept they seemed to be pretty convinced that this was due to listening to different resolutions of digital audio files. I tried to explain that most music I listen to is Pandora streaming through my 103D and 99% of what I do is watch movies/TV shows streamed from my server to my htpc client running Kodi or watch tv on my TiVo DVR. This issue does not clearly happen with one source more than any other but has never happened with music (probably because I listen to music so infrequently).
Anyway, I hope they are able to get it figured out. If not then I will ask to return It and I will go with a Marantz processor.
|
|
|
|
Post by ÈlTwo on Sept 30, 2015 9:38:59 GMT -5
Good luck, I hope they figure it out for you.
|
|
|
|
Post by trevordj on Oct 7, 2015 16:37:14 GMT -5
The unit arrived at Emotiva today so we will see what they come up with. I hope they are able to figure it out!
|
|
|
|
Post by trevordj on Oct 9, 2015 12:12:25 GMT -5
Quick turnaround with the repair. They said it was a faulty ECC board. Whatever the heck that is. They are shipping it back to me today. Hopefully it works!
|
|
|
|
Post by trevordj on Oct 18, 2015 11:35:37 GMT -5
Got the unit back, updated the firmware to 3.1 and reset to factory default settings. After a few hours of use, the XMC-1 randomly is now shutting down completely. This happens either from video on standby or when the unit is on and in use. It isn't freezing like it was but is equally frustrating. It sounds like this is happening to a few others since the firmware update so it is hard to say whether this is the ECC issue or a firmare issue. This unit has been nothing but trouble for me unfortunately. I am going to call Emotiva tomorrow. I am contemplating simply trying to return this and going with a Marantz unit. I hate to say it because I had really great luck with my UMC-200. Pretty disappointed right now.
|
|
. 
