|
Post by Mikomill on Feb 14, 2020 18:27:58 GMT -5
Wow, blocked sound on ANALOG inputs too? I did have one case where the RMC1 under a much older FW would play nothing on the analog inputs until I did a hard reset... but a regular muting of analog seems like a new problem?
Yes, again, we get the "it's difficult [to do this]" speech, yet as we have said, other vendors using the same chipsets don't have the same problems. This is a round robin argument, eventually it should be understood that if it can be done by others without issue you have a talent or manpower deficiency, or there's simply no desire to get it right due to some belief that the problems are minor or isolated or... some other reason altogether. The definition of "done" varies, remember when Hyundai first starting make US cars, they were content to send cars out the factory with gaps in the windshield and A-pillar, whereas most other companies would never even think of that, no matter what the pricepoint. We'll obviously never understand, but one thing *I* can understand is that after over a year it's still not right and the needle is not trending in the right direction, the chances of success go down... but that's up to the individual person to decide obviously. ...And you've obviously made your decision a long time ago. Thanks for the very helpful post. Once again your comments added a lot to this thread.
|
|
|
Post by dgreenwade on Feb 14, 2020 18:43:08 GMT -5
Has anyone posted their experience in returning this unit to Emotiva yet? I have decided that I no longer want to participate in what seems like beta testing that has lasted for over a year now and I sent an e-mail to Emotiva requesting info on how to proceed with a return. I'm curious how they are going to respond in regards to shipping the item back and my upgrade card I used.
I keep track of this thread pretty regularly, but I haven't seen anyone post anything specific on this subject. Please reply or PM me with your experience.
|
|
|
Post by mikoz on Feb 14, 2020 19:09:14 GMT -5
Wow, blocked sound on ANALOG inputs too? I did have one case where the RMC1 under a much older FW would play nothing on the analog inputs until I did a hard reset... but a regular muting of analog seems like a new problem?
Yes, again, we get the "it's difficult [to do this]" speech, yet as we have said, other vendors using the same chipsets don't have the same problems. This is a round robin argument, eventually it should be understood that if it can be done by others without issue you have a talent or manpower deficiency, or there's simply no desire to get it right due to some belief that the problems are minor or isolated or... some other reason altogether. The definition of "done" varies, remember when Hyundai first starting make US cars, they were content to send cars out the factory with gaps in the windshield and A-pillar, whereas most other companies would never even think of that, no matter what the pricepoint. We'll obviously never understand, but one thing *I* can understand is that after over a year it's still not right and the needle is not trending in the right direction, the chances of success go down... but that's up to the individual person to decide obviously. ...And you've obviously made your decision a long time ago. Thanks for the very helpful post. Once again your comments added a lot to this thread.
You're welcome. First line was factual and sharing actual experience.
|
|
klinemj
Emo VIPs
Honorary Emofest Scribe
Posts: 14,762
|
Post by klinemj on Feb 14, 2020 19:11:44 GMT -5
Has anyone posted their experience in returning this unit to Emotiva yet? I have decided that I no longer want to participate in what seems like beta testing that has lasted for over a year now and I sent an e-mail to Emotiva requesting info on how to proceed with a return. I'm curious how they are going to respond in regards to shipping the item back and my upgrade card I used. I keep track of this thread pretty regularly, but I haven't seen anyone post anything specific on this subject. Please reply or PM me with your experience. Call them instead of e-mailing. The response is typically very quick with phone calls. Mark
|
|
|
Post by petew on Feb 14, 2020 19:30:06 GMT -5
Has anyone posted their experience in returning this unit to Emotiva yet? I have decided that I no longer want to participate in what seems like beta testing that has lasted for over a year now and I sent an e-mail to Emotiva requesting info on how to proceed with a return. I'm curious how they are going to respond in regards to shipping the item back and my upgrade card I used. I keep track of this thread pretty regularly, but I haven't seen anyone post anything specific on this subject. Please reply or PM me with your experience. You pay freight for the return trip. Your card is gone. Poof. Hope you didn't spend currency on it.
|
|
Lsc
Emo VIPs
Posts: 3,348
|
Post by Lsc on Feb 14, 2020 19:52:47 GMT -5
I’m guessing 1-2 weeks away atleast.. Then also a delay with Dirac.. 45 days is approaching fast.. But with the bugs still left in 1.7.6 I can’t see them meeting the goal of Dirac in middle of march.. I have issues with lockups at startup that I have never had before. Also still no sound a start of some inputs. HDMI, digital or analog makes no difference, can be any type of input. Although always a simple switch and back to get sound. What I have noticed though is that if I get no sound through analog for example I need to switch to a HDMI input and back. If there’s a problem with HDMI then mostly switch to a digital or analog and back. The strange thing is that sometimes it works just by pressing the same input once more. I have noticed the small, about 1 second or less, delay when starting a song when connected to coax or toslink. Never noticed any delays on analog or hdmi connections. No burst of loud sound in my setup yet.. Hopefully I’ll never experience it.. Wow, blocked sound on ANALOG inputs too? I did have one case where the RMC1 under a much older FW would play nothing on the analog inputs until I did a hard reset... but a regular muting of analog seems like a new problem?
Yes, again, we get the "it's difficult [to do this]" speech, yet as we have said, other vendors using the same chipsets don't have the same problems. This is a round robin argument, eventually it should be understood that if it can be done by others without issue you have a talent or manpower deficiency, or there's simply no desire to get it right due to some belief that the problems are minor or isolated or... some other reason altogether. The definition of "done" varies, remember when Hyundai first starting make US cars, they were content to send cars out the factory with gaps in the windshield and A-pillar, whereas most other companies would never even think of that, no matter what the pricepoint. We'll obviously never understand, but one thing *I* can understand is that after over a year it's still not right and the needle is not trending in the right direction, the chances of success go down... but that's up to the individual person to decide obviously.
With the Hyundai analogy, this is good news. So emotiva will be the most reliable brand in 25 years 😬.
|
|
|
Post by mgbpuff on Feb 15, 2020 10:28:34 GMT -5
Nobody, I repeat, nobody uses the exact same chipsets as Emotiva does in the RMC-1. Many other pre-pros are derivatives of each other due to common holding company ownership. Emotiva is probably the only 'go it alone' small company developing a complex pre-pro.
|
|
ccm
Minor Hero
Posts: 21
|
Post by ccm on Feb 15, 2020 15:05:26 GMT -5
I was having video lock up issues on 1.7 and went back to 1.5 a while ago (sometimes very difficult to get working again when video quit). The only issues I have on 1.5 is audio start delays. No lockups or loud buzzing ever. Volume level seems to be too low but it's not a huge deal. I know we need to move forward to get Dirac, etc. but 1.5 works much better for me than 1.7 did.
Chris...
|
|
|
Post by hsamwel on Feb 16, 2020 6:38:19 GMT -5
I’m guessing 1-2 weeks away atleast.. Then also a delay with Dirac.. 45 days is approaching fast.. But with the bugs still left in 1.7.6 I can’t see them meeting the goal of Dirac in middle of march.. I have issues with lockups at startup that I have never had before. Also still no sound a start of some inputs. HDMI, digital or analog makes no difference, can be any type of input. Although always a simple switch and back to get sound. What I have noticed though is that if I get no sound through analog for example I need to switch to a HDMI input and back. If there’s a problem with HDMI then mostly switch to a digital or analog and back. The strange thing is that sometimes it works just by pressing the same input once more. I have noticed the small, about 1 second or less, delay when starting a song when connected to coax or toslink. Never noticed any delays on analog or hdmi connections. No burst of loud sound in my setup yet.. Hopefully I’ll never experience it..
Wow, blocked sound on ANALOG inputs too? I did have one case where the RMC1 under a much older FW would play nothing on the analog inputs until I did a hard reset... but a regular muting of analog seems like a new problem?
Yes, again, we get the "it's difficult [to do this]" speech, yet as we have said, other vendors using the same chipsets don't have the same problems. This is a round robin argument, eventually it should be understood that if it can be done by others without issue you have a talent or manpower deficiency, or there's simply no desire to get it right due to some belief that the problems are minor or isolated or... some other reason altogether. The definition of "done" varies, remember when Hyundai first starting make US cars, they were content to send cars out the factory with gaps in the windshield and A-pillar, whereas most other companies would never even think of that, no matter what the pricepoint. We'll obviously never understand, but one thing *I* can understand is that after over a year it's still not right and the needle is not trending in the right direction, the chances of success go down... but that's up to the individual person to decide obviously.
Well no.. I have had ”blocked” sound from any input since I bought the RMC, firmware 1.3 until 1.7.6. Not often, but several times a week. Maybe 10-15% of the times starting RMC (maybe often for some?). Although less with firmware 1.7. But with 1.7.6 this increased again. In the beginning anyway. A little bit better the last week though. Can’t actually not remember a single time I got no audio. HDMI sync also seems much more robust with 1.7.6. Because this happens on any input I don’t always blame hdmi sync. I think Emotiva has other issues as well with connecting sound from inputs. This probably isn’t the same code as hdmi sync. It has always been an easy switch of inputs to fix this though. I have only once had to restart my RMC due to ”blocked” audio. Taking the XMC-1 code as base for RMC-1 I think was a mistake. They should have made a fresh start instead. Probably alot less issues could have been avoided. Also faster..
|
|
|
Post by aswiss on Feb 17, 2020 11:58:10 GMT -5
Another week gone by. How's the next firmware coming along?? I’m guessing 1-2 weeks away atleast.. Then also a delay with Dirac.. 45 days is approaching fast.. But with the bugs still left in 1.7.6 I can’t see them meeting the goal of Dirac in middle of march.. I have issues with lockups at startup that I have never had before. Also still no sound a start of some inputs. HDMI, digital or analog makes no difference, can be any type of input. Although always a simple switch and back to get sound. What I have noticed though is that if I get no sound through analog for example I need to switch to a HDMI input and back. If there’s a problem with HDMI then mostly switch to a digital or analog and back. The strange thing is that sometimes it works just by pressing the same input once more. I have noticed the small, about 1 second or less, delay when starting a song when connected to coax or toslink. Never noticed any delays on analog or hdmi connections. No burst of loud sound in my setup yet.. Hopefully I’ll never experience it.. I got a mail from the german distributor for Emo, where I addressed my concerns about the future of the RMC-1.
The statement was, that some of the bugs might be resolved with a new FW "in the next few weeks" (Emo official). Dirac will come "soon". (Emo official)
I had also some drops on XLR Balanced in - but not reproducable. (no sound for 1-2 secs). After a reboot it was gone.
Some errors just happen. very strange.
As I'm still on FW 1.5 (1.7 was not working for me) - I'm now 6 months on the same level.
|
|
|
Post by kahodges1721 on Feb 18, 2020 9:53:29 GMT -5
I may be in the minority here but with the delay of 1.8 I hope that emotiva will just hold off on the update until Dirac is ready. Following the forum it seems logical that emotiva really needs to get this right. I personally appreciate the delay. To me it says we don’t want to rush this one out. Instead we need to ensure it is fully functional and stable. I believe we are right around 2 weeks until the proposed Dirac launch. If that’s still true then don’t you agree it’s only logical to release them together?
|
|
|
Post by aswiss on Feb 18, 2020 10:01:08 GMT -5
I may be in the minority here but with the delay of 1.8 I hope that emotiva will just hold off on the update until Dirac is ready. Following the forum it seems logical that emotiva really needs to get this right. I personally appreciate the delay. To me it says we don’t want to rush this one out. Instead we need to ensure it is fully functional and stable. I believe we are right around 2 weeks until the proposed Dirac launch. If that’s still true then don’t you agree it’s only logical to release them together? Sorry to say so - but 6 or 12 months are nothing I would call "a rush".
I don't care about Dirac before the RMC-1 itself is stable and works as designed. FW to eliminate all the known Bugs - then give it some weeks to see if all the major bugs really are gone, and no new ones occure with the 1.8. Once this is done, Dirac might come - I don't expect Dirac to happen before Axpona.
|
|
|
Post by thxultra on Feb 18, 2020 10:06:16 GMT -5
I may be in the minority here but with the delay of 1.8 I hope that emotiva will just hold off on the update until Dirac is ready. Following the forum it seems logical that emotiva really needs to get this right. I personally appreciate the delay. To me it says we don’t want to rush this one out. Instead we need to ensure it is fully functional and stable. I believe we are right around 2 weeks until the proposed Dirac launch. If that’s still true then don’t you agree it’s only logical to release them together? Sorry to say so - but 6 or 12 months are nothing I would call "a rush".
I don't care about Dirac before the RMC-1 itself is stable and works as designed. FW to eliminate all the known Bugs - then give it some weeks to see if all the major bugs really are gone, and no new ones occure with the 1.8. Once this is done, Dirac might come - I don't expect Dirac to happen before Axpona.
I agree I expect to see Dirac close to being ready at Axpona and Emotiva will demo it there on the RMC-1. Really hoping they work out some of these bugs in 1.8 especially the loud buzz one.
|
|
|
Post by davidl81 on Feb 18, 2020 10:28:58 GMT -5
I may be in the minority here but with the delay of 1.8 I hope that emotiva will just hold off on the update until Dirac is ready. Following the forum it seems logical that emotiva really needs to get this right. I personally appreciate the delay. To me it says we don’t want to rush this one out. Instead we need to ensure it is fully functional and stable. I believe we are right around 2 weeks until the proposed Dirac launch. If that’s still true then don’t you agree it’s only logical to release them together? I personally am not a fan of having the big FW updates every 3 months or so. I don't understand why we don't get smaller updates more frequently. Seems like instead of trying to fix all problems in one FW update (which never works anyway) why not just do smaller updates (say 1.7.1 etc) that fixes specific problems. It seems like that is what most other companies do.
|
|
|
Post by TDifEQ on Feb 18, 2020 10:38:09 GMT -5
|
|
flo26
Minor Hero
Posts: 13
|
Post by flo26 on Feb 18, 2020 13:00:26 GMT -5
Hello to update the firmware which USB key should be used? usb 2 ? usb 3 ? How many GOs ?
Thank you for your answers
|
|
cawgijoe
Emo VIPs
"We made too many of the wrong mistakes." - Yogi Berra
Posts: 4,915
|
Post by cawgijoe on Feb 18, 2020 13:11:38 GMT -5
I may be in the minority here but with the delay of 1.8 I hope that emotiva will just hold off on the update until Dirac is ready. Following the forum it seems logical that emotiva really needs to get this right. I personally appreciate the delay. To me it says we don’t want to rush this one out. Instead we need to ensure it is fully functional and stable. I believe we are right around 2 weeks until the proposed Dirac launch. If that’s still true then don’t you agree it’s only logical to release them together? I personally am not a fan of having the big FW updates every 3 months or so. I don't understand why we don't get smaller updates more frequently. Seems like instead of trying to fix all problems in one FW update (which never works anyway) why not just do smaller updates (say 1.7.1 etc) that fixes specific problems. It seems like that is what most other companies do. I tend to agree with this, because I want my specific issue fixed, but I think what happens is that they fix one thing and that fix then disrupts something else or causes a new problem. I've seen that happen with Apple. Apple with it's huge resources can turn things around pretty quick, because they can. Hopefully 1.8 will be released soon without causing more issues....fingers crossed.
|
|
KeithL
Administrator
Posts: 9,966
|
Post by KeithL on Feb 18, 2020 14:49:41 GMT -5
Either USB 2 or USB 3 will work.... You can also use the smallest USB stick you can find (the firmware file is only around 20 mB).
The stick must be formatted as FAT32...
Notes: You may write the firmware file onto the stick using either a Windows or Apple computer. However, sticks formatted on an Apple computer won't work (because some of the format defaults are wrong). Any stick you buy in the store that says "for Windows or Apple computers" should work fine (don't reformat it).
Put the firmware file in the main folder on the stick. Make sure there is only one firmware file on the stick (the RMC-1 will NOT automatically pick out the newest one).
(It's safer if there are no other files in the main folder.)
Some sticks just plain don't work... and the easiest solution is to try a different stick.
If the stick doesn't work you will see "NO USB STICK". If the stick is OK, but the file is missing, or you forget to unZip it, you will see "NO UPDATE FILE"
Hello to update the firmware which USB key should be used? usb 2 ? usb 3 ? How many GOs ? Thank you for your answers
|
|
|
Post by rbk123 on Feb 18, 2020 14:51:23 GMT -5
I don't understand why we don't get smaller updates more frequently. Seems like instead of trying to fix all problems in one FW update (which never works anyway) why not just do smaller updates (say 1.7.1 etc) that fixes specific problems. It seems like that is what most other companies do. It's because they are, in terms of experience, very young at software development. There's a difference in being able to code, and coding best practices, and you can see their relative youth in this area as they continue to make all of the classic software dev mistakes made when one "reinvents the wheel" and tries to learn on their own, vs. having seasoned large-scale program vets who already know how to make the wheel. I would guess they can't afford hiring pros and are managing a group of, most likely offshore developers, themselves. Perfectly understandable when you have budget constraints which limit your viable options.
|
|
m4rc
Seeker Of Truth
Posts: 7
|
Post by m4rc on Feb 18, 2020 16:06:19 GMT -5
Either USB 2 or USB 3 will work.... You can also use the smallest USB stick you can find (the firmware file is only around 20 mB).
The stick must be formatted as FAT32... Notes: You may write the firmware file onto the stick using either a Windows or Apple computer. However, sticks formatted on an Apple computer won't work (because some of the format defaults are wrong). Any stick you buy in the store that says "for Windows or Apple computers" should work fine (don't reformat it). Put the firmware file in the main folder on the stick. Make sure there is only one firmware file on the stick (the RMC-1 will NOT automatically pick out the newest one).
(It's safer if there are no other files in the main folder.)
Some sticks just plain don't work... and the easiest solution is to try a different stick.
If the stick doesn't work you will see "NO USB STICK". If the stick is OK, but the file is missing, or you forget to unZip it, you will see "NO UPDATE FILE"
Hello to update the firmware which USB key should be used? usb 2 ? usb 3 ? How many GOs ? Thank you for your answers Formatting using a Apple computer worked for me. Next to selecting FAT32 the setting Master Boot Record needs to be selected. FAT32 with the GUID setting, which is the default, doesn't work. Glad if this spares someone the hassle of browsing their neighborhood for a Windows machine ;-)
|
|