|
Post by ttocs on Nov 23, 2019 17:28:09 GMT -5
Thanks for mentioning "at the Amp" … meaning "loaded". That 11.8 VDC was at the far end on the 3.5mm trigger cable (tip and ring) … unloaded (not plugged into the amp). I just went back and plugged in a 3.5mm splitter at the RMC-1 trigger input and got 4.1 VDC … loaded. Rechecked the unloaded tip and ring reading and it was at still at 11.8 VDC. So, I either return the RMC-1 to have the triggers repaired (not enough current) or buy the ET-3 for $40.00 … assuming the RMC-1 has enough current to drive the ET-3. Any more tests I should run? That's quite a voltage drop. I just want to understand some things so please bear with me. You are using a mono cable, correct? And that cable is not an audio cable with attenuation built-in, correct? These are very common, I found out the hard way. The splitter is not attenuated in any way, just parallel connections inside, correct? My first trigger cable was one I purchased at RadioShack, they sold several different models. I bought the one with a length I needed. I couldn't understand why one end was heating up!! Upon closer inspection I determined it was attenuated even though the package didn't mention this. I thoroughly searched and found ONLY ONE cable sold at RadioShack which was NOT attenuated. Just a thought. I tested my XMC-1 with a Krell amp. XMC-1 Trigger output voltage is 12.25V unloaded, and 10.86V loaded through a 6 foot long cable. The cable measures .1 Ohms through Tip or Ring. edit: I make my own cables now. Exact length and no issues with attenuation. edit 2: While the voltage drop on Trigger-1 into the Krell is as stated above and under load, a cable plugged into Trigger-2 has no voltage drop and remains at 12.25V. So I'm guessing the triggers are powered independently.
|
|
|
Post by TDifEQ on Nov 24, 2019 7:45:46 GMT -5
ttocs KeithL Just verified all amps work with Denon 4810ci using same trigger cables. So it's the RMC-1 ... triggers have never worked on this unit ... I always thought it was the older amps because it was a brand new audio processor ... but when I got this fourth brand new amp unit, I started spending time to figure out the issue. Maybe EMO can send me a trigger board (or something related) so I can install at home without sending the unit back? Thx. Love that Denon rcv'r, but $900 was too expensive to have the HDMI board replaced … so paid $5000 for an audio processor with 3D immersion instead. One can still use the amps in the Denon unit, even though HDMI board does not work ... do this via analog 7.1 rca inputs. lol.
|
|
|
Post by SOWK on Nov 24, 2019 8:29:18 GMT -5
Just wanted to let people know the PEQ on the sub channels is not working with the RMC-1 FW1.7
If there is a work around, can someone tell me how to fix please.
|
|
|
Post by Geronimo on Nov 24, 2019 13:36:00 GMT -5
Just wanted to let people know the PEQ on the sub channels is not working with the RMC-1 FW1.7 If there is a work around, can someone tell me how to fix please. Just curious. Did you try loading up REW filters? Also, are you in any "MODE" other than REFERENCE, or DIRECT?
|
|
|
Post by SOWK on Nov 24, 2019 14:09:57 GMT -5
Just wanted to let people know the PEQ on the sub channels is not working with the RMC-1 FW1.7 If there is a work around, can someone tell me how to fix please. Just curious. Did you try loading up REW filters? Also, are you in any "MODE" other than REFERENCE, or DIRECT? Yes, Tried manually entering data points and via REW In Auto mode. Using ASIO and 7.1 LPCM output via REW.
|
|
|
Post by Geronimo on Nov 24, 2019 15:34:58 GMT -5
Just curious. Did you try loading up REW filters? Also, are you in any "MODE" other than REFERENCE, or DIRECT? Yes, Tried manually entering data points and via REW In Auto mode. Using ASIO and 7.1 LPCM output via REW. I'll give it a shot when I get home. I DO know that I was able to get my 7 bed channels EQ'd via exporting REW filters. I HAVEN'T tried the subwoofer channel, as a Minidsp 2x4HD handles that. I'm using the Center Subwoofer as mono for reference.
|
|
|
Post by SOWK on Nov 24, 2019 18:56:42 GMT -5
Yes, Tried manually entering data points and via REW In Auto mode. Using ASIO and 7.1 LPCM output via REW. I'll give it a shot when I get home. I DO know that I was able to get my 7 bed channels EQ'd via exporting REW filters. I HAVEN'T tried the subwoofer channel, as a Minidsp 2x4HD handles that. I'm using the Center Subwoofer as mono for reference. My other 13 channels PEQ just fine.
|
|
|
Post by Geronimo on Nov 24, 2019 21:48:31 GMT -5
I'll give it a shot when I get home. I DO know that I was able to get my 7 bed channels EQ'd via exporting REW filters. I HAVEN'T tried the subwoofer channel, as a Minidsp 2x4HD handles that. I'm using the Center Subwoofer as mono for reference. My other 13 channels PEQ just fine. I just tried. I lost all my PEQ, and ability to PEQ my channels. They load up, but REW shows them not working. That goes for the subwoofer as well.....
|
|
|
Post by adaboy on Nov 24, 2019 21:57:45 GMT -5
My other 13 channels PEQ just fine. I just tried. I lost all my PEQ, and ability to PEQ my channels. They load up, but REW shows them not working. That goes for the subwoofer as well..... 😱 That sucks!
|
|
|
Post by SOWK on Nov 24, 2019 22:36:19 GMT -5
My other 13 channels PEQ just fine. I just tried. I lost all my PEQ, and ability to PEQ my channels. They load up, but REW shows them not working. That goes for the subwoofer as well..... The RMC-1 is ULTRA finicky with the PEQ. You basically want to wipe all previous PEQ Filters. Power down the unit fully Power back up Load the new PEQ filters Power down the unit fully Power back up That seems to be the only way I found for it to not self destruct.
|
|
|
Post by bblv on Nov 24, 2019 22:58:23 GMT -5
Is this firmware a joke after a 3 month development period? C'mon......
|
|
|
Post by SOWK on Nov 25, 2019 4:29:16 GMT -5
Is this firmware a joke after a 3 month development period? C'mon...... Cant tell you if my issue is new or not. I finally installed the RMC-1 into my system after having owned since last year. Lol. Im sure it was not working from the first firmware.
|
|
|
Post by hsamwel on Nov 25, 2019 6:25:16 GMT -5
I read on AVS where the Monoprice tech guy answered a couple of questions and had changed some specs of the HTP-1 just by reading what users wanted. PEQ 5 to 16 and dirac presets 3 to 6. This without anyone asking for it yet. I would like Emotiva to do the same. Read and make changes that users want instead of writing it can’t be done or we have other priorities. But then again, it seems they are busy with the basics still, just getting it to work properly.
|
|
|
Post by TDifEQ on Nov 25, 2019 6:38:16 GMT -5
Upon power up, got noise on all speakers on FW 1.5. Movie: 2K Chef, DD2.0, DD5.1 (trailers) and DTS MAHD 5.1/Neural:X (movie). I now have default spkr volume set at -60dB. I would of pick -70dB if there were a choice. Both 1.5 and 1.7 exhibit this issue.
|
|
|
Post by hsamwel on Nov 25, 2019 6:52:07 GMT -5
How about firmware 1.8? We need a fast bugfix for 2-3 of the biggest bugs.. Making the firmware usable atleast.
I thought I had another disc bug on me. While watching Star Wars 4 A New Hope with my kid I got the same strange display on the oled. I have it configured to show bitstream on the left side. When the disc got to the menu, it showed a normal sized Dolby logo followed by a smaller one with 5.1 after. The same I got when I tried the Fury Road bluray. But this disc had a DTS-HD MA 6.1 track and did not lock up and show PCM 5.1 when I started the movie. It just started fine.
|
|
|
Post by TDifEQ on Nov 25, 2019 7:04:10 GMT -5
Thanks for mentioning "at the Amp" … meaning "loaded". That 11.8 VDC was at the far end on the 3.5mm trigger cable (tip and ring) … unloaded (not plugged into the amp). I just went back and plugged in a 3.5mm splitter at the RMC-1 trigger input and got 4.1 VDC … loaded. Rechecked the unloaded tip and ring reading and it was at still at 11.8 VDC. So, I either return the RMC-1 to have the triggers repaired (not enough current) or buy the ET-3 for $40.00 … assuming the RMC-1 has enough current to drive the ET-3. Any more tests I should run? That's quite a voltage drop. I just want to understand some things so please bear with me. You are using a mono cable, correct? And that cable is not an audio cable with attenuation built-in, correct? These are very common, I found out the hard way. The splitter is not attenuated in any way, just parallel connections inside, correct? My first trigger cable was one I purchased at RadioShack, they sold several different models. I bought the one with a length I needed. I couldn't understand why one end was heating up!! Upon closer inspection I determined it was attenuated even though the package didn't mention this. I thoroughly searched and found ONLY ONE cable sold at RadioShack which was NOT attenuated. Just a thought. I tested my XMC-1 with a Krell amp. XMC-1 Trigger output voltage is 12.25V unloaded, and 10.86V loaded through a 6 foot long cable. The cable measures .1 Ohms through Tip or Ring. edit: I make my own cables now. Exact length and no issues with attenuation. edit 2: While the voltage drop on Trigger-1 into the Krell is as stated above and under load, a cable plugged into Trigger-2 has no voltage drop and remains at 12.25V. So I'm guessing the triggers are powered independently. Mono cbl, bought at amazon, gold contacts, it says it's an audio cable … whether it has attenuation built in, don't know. These cables work with Denon 4810ci rcv'r: www.amazon.com/dp/B000O7AXX8/ref=twister_B07BS27VDN?_encoding=UTF8&psc=1Trigger cable measured 0.4 ohms for 6ft. A 3ft cheap rca cable measured 8.0 ohms. Still, these trigger cables work with Denon 4810ci rcv'r. Just checked end to end ohm'age with the splitter connected to 2 mono 3.5mm 6ft cbls, it read .002 ohms. tip connects to tip and ring talks to ring (gnd). no cross talk btwn tip and ring. lol. I'm getting too much into the weeds. It would be soooo nice to have the amps turn on automatically.
|
|
novisnick
EmoPhile
CEO Secret Monoblock Society
Posts: 27,235
|
Post by novisnick on Nov 25, 2019 7:32:36 GMT -5
I just don’t see any sense in trying any new software updates untill I see reports of great stability! I’m getting exhausted, reading and waiting for a solid solution for the RMC-1.
|
|
|
Post by TDifEQ on Nov 25, 2019 8:10:30 GMT -5
It's getting exhausting for sure.
|
|
|
Post by deewan on Nov 25, 2019 8:57:43 GMT -5
How about firmware 1.8? We need a fast bugfix for 2-3 of the biggest bugs.. Making the firmware usable atleast. You're not going to like this answer, but if you are in serious need for a more stable firmware, it's called FW 1.5. You should know, especially with the upcoming American Thanksgiving holiday the next new firmware released from Emotiva won't be anytime soon. After reading the code changes they want to make for 1.8, that code re-write isn't going to be quick and the changes should have some serious regression testing that will weeks, not hours.
|
|
|
Post by AudioHTIT on Nov 25, 2019 10:29:17 GMT -5
How about firmware 1.8? We need a fast bugfix for 2-3 of the biggest bugs.. Making the firmware usable atleast. You're not going to like this answer, but if you are in serious need for a more stable firmware, it's called FW 1.5. You should know, especially with the upcoming American Thanksgiving holiday the next new firmware released from Emotiva won't be anytime soon. After reading the code changes they want to make for 1.8, that code re-write isn't going to be quick and the changes should have some serious regression testing that will weeks, not hours. This is where I believe the suggestion for less time between FW releases AND fewer, more focused fixes, has merit. For example, several people have rolled back from 1.7 to 1.5 because of the audio loss with Video on Standby. So release a 1.71 with just this issue fixed, maybe call it a ‘public beta’, or continue the ‘private betas’ only given to those who write in describing the problem that’s been fixed. The advantages are twofold, one the customer gets a feature they want fixed, two the development team gets users back on 1.7x where they need reports of success or failure resolving other issues. I realize there are many complexities in updating ‘the code’ and that fixing one problem may introduce or affect another, but when users are rolling back it has to be more difficult to move forward.
|
|