|
|
Post by doc1963 on Feb 19, 2021 14:39:19 GMT -5
The only times I experience a Slow Bug is when a Dolby Bitstream device is Paused, or in the case of my Panasonic UB820 when I'm in its menu. And it's not when the device is paused the first time in a processor On session, it's only the second time and after. I just tried it for the first time since updating to FW-2.2. I paused TiVo once, no problem, started playing again and paused a second time, now the processor Menu is slow, resume play and Menu is ok again. that's interesting. So, it's getting bogged down in some logic error or loop that won't exit until playing resumes? I wonder if there are any code prioritizations built in to limit each functions overall utilization/consumption of processor and memory. Here's how it was explained to me... while paused, some (or maybe most) devices will send a "blip" every 500ms. When this occurs, the processor gets busy trying to lock on to audio and the OSD gets bogged down. So, yes, I do believe it's a "system priority" type of thing that will be a addressed in the next firmware release. But IMO, I don't believe that the OSD will ever be as responsive as it once was when it comes to now having to overlay on top of 4K video. This is likely why more and more manufacturers are moving away from a live OSD and instead opting for an app or browser based menu for setup and system control. Even Marantz comes out of live video for "Settings". Only "Volume" and "Info" is shown over live video. FWIW, I would welcome this change as long as "Info" and "Volume" were still available to us over live video. Anthem is the latest to have moved in this direction... |
|
|
|
Post by Thunderduck on Feb 19, 2021 15:06:11 GMT -5
You can do that also with the STANDBY button on the remote unit. Hold that button for 6 seconds or so and the unit will power down to the lowest power mode (sorry, forget the correct term). Anyway, the unit will not be in VRO mode so that when you power on again, it will go through the full boot-up process. This will save me the headache of pulling my cabinets apart just to get to the switch. Another question!! Where can I get 2.1 if I upload 2.2 and it doesn’t work for me? I believe so but am far from an expert on this question. It certainly would not hurt to try either the STANDBY button or the Emotiva button on the front to see if that does what you want. I use the STANDBY button procedure every once in a while to kind of shake the cobwebs out. Sorry I could not be more definitive on this but am sure someone with more knowledge will chime in. Take care. |
|
Lonnie
Emo Staff 
admin
Pay no attention to the man behind the curtain
Posts: 6,999
|
Post by Lonnie on Feb 19, 2021 15:10:39 GMT -5
You can do that also with the STANDBY button on the remote unit. Hold that button for 6 seconds or so and the unit will power down to the lowest power mode (sorry, forget the correct term). Anyway, the unit will not be in VRO mode so that when you power on again, it will go through the full boot-up process. Does this do the same function as toggling the on/off switch from the back? This will save me the headache of pulling my cabinets apart just to get to the switch. Another question!! Where can I get 2.1 if I upload 2.2 and it doesn’t work for me? Yes, if you hold the standby button for 6 seconds, the unit will do a hard shut down and kill all power to everything internal, so it acts the same as turning off the main power switch. Lonnie |
|
|
|
Post by jasonf on Feb 19, 2021 15:17:26 GMT -5
I tried the version 2.2 on my XMC-2 and had lots of issues with the Apple 4K. The video kept turning off and on like it was losing connection every time I would change screens. You're going to have to turn off CEC Input switching on the XMC-2 unfortunately. It seems that changes to VRO are causing the AppleTV to try and change inputs constantly. |
|
Lonnie
Emo Staff
admin
Pay no attention to the man behind the curtain
Posts: 6,999
|
Post by Lonnie on Feb 19, 2021 15:24:10 GMT -5
that's interesting. So, it's getting bogged down in some logic error or loop that won't exit until playing resumes? I wonder if there are any code prioritizations built in to limit each functions overall utilization/consumption of processor and memory. Here's how it was explained to me... while paused, some (or maybe most) devices will send a "blip" every 500ms. When this occurs, the processor gets busy trying to lock on to audio and the OSD gets bogged down. So, yes, I do believe it's a "system priority" type of thing that will be a addressed in the next firmware release. But IMO, I don't believe that the OSD will ever be as responsive as it once was when it comes to now having to overlay on top of 4K video. This is likely why more and more manufacturers are moving away from a live OSD and instead opting for an app or browser based menu for setup and system control. Even Marantz comes out of live video for "Settings". Only "Volume" and "Info" is shown over live video. FWIW, I would welcome this change as long as "Info" and "Volume" were still available to us over live video. Anthem is the latest to have moved in this direction... You are correct Doc. There are a few devices out there now that when in pause will send out a 2K "blip" which is actually is a series of binary numbers that look like something between PCM and Bitstream code. The DSP starts running through its hunt and lock routines trying to figure out what it is and lock onto it. But it jumps in and goes away, jumps in and goes away. This ties up the DSP as it is constantly reporting back to the main processor what it is seeing and thus the whole system slows down. Over a prolonged period of time the various reports and instructions start stacking up and eventually this can cause things to get out of sync and the whole system remains in this slowed up state until reset. Now we are not sure why this "Blip" has suddenly started showing up in some products. We've reviewed the latest HDMI specs and docs and this does not appear to be related to any new spec. So the current theory is it's just a byproduct of a particular HDMI transmitter that companies are starting to use. That being the case, it is something we have to deal with, which means being able to quickly identify it, isolate it and resume normal operation as soon as it goes away. This is what we are working on right now. I hope this helps to explain a little bit. Now as for OSD. On a personal level, I would be in favor of dumping it like everyone else. It's truly a pain in the backside to code for all the various resolutions and formats (SD, HD, HDR, DV.......), but that is just my personal opinion. Lonnie |
|
fpv
Seeker Of Truth
Posts: 8
|
Post by fpv on Feb 19, 2021 15:31:21 GMT -5
i just updated to version 2.2,
but it freezed at front panel update i waited for an hour and unplugged the power cord at the information menu fw ver 2.2 but the date is 21/02/08 and the front panel version is 2.1 should it be 2.2 ?
do i need to preform the update again?
edit : just checked the update log ( timeout waiting on FP, termination with error )
|
|
|
|
Post by bigbird on Feb 19, 2021 15:55:15 GMT -5
ok Firmware 2.2 went perfect on my RMC-1L ......But no so easy on my RMC-1. It is currently locked on the DSP1 step of the upgrade for 45 min.
I had previously been locked on HDMI part of the firmware update but with power off, restart and restart of upgrade from USB I blew through the HDMI part only to get hung on DSP1.
Thoughts? Ideas?
|
|
cawgijoe
Emo VIPs 
"When you come to a fork in the road, take it." - Yogi Berra
Posts: 5,033
|
Post by cawgijoe on Feb 19, 2021 16:08:39 GMT -5
ok Firmware 2.2 went perfect on my RMC-1L ......But no so easy on my RMC-1. It is currently locked on the DSP1 step of the upgrade for 45 min. I had previously been locked on HDMI part of the firmware update but with power off, restart and restart of upgrade from USB I blew through the HDMI part only to get hung on DSP1. Thoughts? Ideas? Hold the front panel button down for 6 seconds till it shuts down. Or use the Standby button on the remote to do the same thing. You can also use the rear switch to shut it down. Again....wait 60 seconds and power back on. You can then try again. Edit: Check LCSeminole's post and instructions on this. He goes into more detail. |
|
LCSeminole
Global Moderator
Res firma mitescere nescit.
Posts: 20,863
|
Post by LCSeminole on Feb 19, 2021 16:16:12 GMT -5
i just updated to version 2.2, but it freezed at front panel update i waited for an hour and unplugged the power cord at the information menu fw ver 2.2 but the date is 21/02/08 and the front panel version is 2.1 should it be 2.2 ? do i need to preform the update again? edit : just checked the update log ( timeout waiting on FP, termination with error ) No, you don't have to perform the update again. When this happens again, just turn your processor off with the rocker switch on the back of the box, pull the USB stick, turn the rocker switch back on and then turn the processor back on as you would normally do with the front power button or remote. |
|
fpv
Seeker Of Truth
Posts: 8
|
Post by fpv on Feb 19, 2021 16:28:49 GMT -5
i just updated to version 2.2, but it freezed at front panel update i waited for an hour and unplugged the power cord at the information menu fw ver 2.2 but the date is 21/02/08 and the front panel version is 2.1 should it be 2.2 ? do i need to preform the update again? edit : just checked the update log ( timeout waiting on FP, termination with error ) No, you don't have to perform the update again. When this happens again, just turn your processor off with the rocker switch on the back of the box, pull the USB stick, turn the rocker switch back on and then turn the processor back on as you would normally do with the front power button or remote. it worked fine after the hard reboot but am asking about the fp version it 2.1 not 2.2 and firmware version date is 21/02/08, should i preform the update again ? |
|
LCSeminole
Global Moderator
Res firma mitescere nescit.
Posts: 20,863
|
Post by LCSeminole on Feb 19, 2021 16:35:07 GMT -5
No, you don't have to perform the update again. When this happens again, just turn your processor off with the rocker switch on the back of the box, pull the USB stick, turn the rocker switch back on and then turn the processor back on as you would normally do with the front power button or remote. it worked fine after the hard reboot but am asking about the fp version it 2.1 not 2.2 and firmware version date is 21/02/08, should i preform the update again ? My "FP" version is : 2.10 20/05/01, if that's what you have then you are up to date. |
|
|
|
Post by hsamwel on Feb 19, 2021 16:41:21 GMT -5
What is the latest version fo Dirac which is playing nice with the gen 3 processor's? I believe someone has run 3.0.13 successfully....but I will let them respond. That depends on what you mean by successful. I have done a full calibration and it sounds fine, I think. But it crashed a lot while transfering to my RMC. Otherwise no issues for me on 3.0.13. |
|
|
|
Post by SticknStones on Feb 19, 2021 16:41:38 GMT -5
Well the Loudness seems to do more than loudness. It has changed the way the dialog sounds and adds to surround levels also more than the fronts. I here more of a center spread across the front stage. For the first time on an Emotiva processor, I like the effect of "loudness"... great for low volume listening... at super low volumes it's a little off-putting but moderate-low and up works well. Boom! I have been waiting for this feature to do my XMC-1 upgrade. My wife plays instrumental music all day while she works and the loudness is very helpful. Thanks for the feedback. |
|
|
|
Post by JKCashin on Feb 19, 2021 16:49:37 GMT -5
VRO is not working for me. I have to toggle the main switch in the back to get it to work again and that’s a pain in the a$$. I wish they would put a switch in the front for people who can’t get behind their cabinets easily. I wouldn’t complain if I had to do it like once or twice a year but it’s been like every week I have to toggle it to get the damn thing to work again. Sounds great when working right but a $3k processors that can’t even perform half the time. Emotiva needs to step up the game here and get some professional programmers here. This thing has been out way to long to have bugs like this. I wish I could get my hands on their code.... I'm an embedded software designer by trade. One of my specialties is performance tweaking and I've also done many memory leak fixes in embedded code from medical to banking to automotive. Sigh. |
|
cawgijoe
Emo VIPs
"When you come to a fork in the road, take it." - Yogi Berra
Posts: 5,033
|
Post by cawgijoe on Feb 19, 2021 16:51:03 GMT -5
VRO is not working for me. I have to toggle the main switch in the back to get it to work again and that’s a pain in the a$$. I wish they would put a switch in the front for people who can’t get behind their cabinets easily. I wouldn’t complain if I had to do it like once or twice a year but it’s been like every week I have to toggle it to get the damn thing to work again. Sounds great when working right but a $3k processors that can’t even perform half the time. Emotiva needs to step up the game here and get some professional programmers here. This thing has been out way to long to have bugs like this. I wish I could get my hands on their code.... I'm an embedded software designer by trade. One of my specialties is performance tweaking and I've also done many memory leak fixes in embedded code from medical to banking to automotive. Sigh. Maybe you need to send your resume to Emotiva? Relocate to Franklin, TN....it's a nice place! |
|
|
|
Post by megash0n on Feb 19, 2021 17:20:12 GMT -5
I wish I could get my hands on their code.... I'm an embedded software designer by trade. One of my specialties is performance tweaking and I've also done many memory leak fixes in embedded code from medical to banking to automotive. Sigh. Maybe you need to send your resume to Emotiva? Relocate to Franklin, TN....it's a nice place! Pretty sure most of that isn't going on in Franklin outside of a little Linux scripting. Besides, there are hundreds it not thousands of programmers and firms within a 35 mile radius. If they wanted these issues fixed, they would have been fixed years ago. |
|
|
|
Post by megash0n on Feb 19, 2021 17:24:17 GMT -5
that's interesting. So, it's getting bogged down in some logic error or loop that won't exit until playing resumes? I wonder if there are any code prioritizations built in to limit each functions overall utilization/consumption of processor and memory. Here's how it was explained to me... while paused, some (or maybe most) devices will send a "blip" every 500ms. When this occurs, the processor gets busy trying to lock on to audio and the OSD gets bogged down. So, yes, I do believe it's a "system priority" type of thing that will be a addressed in the next firmware release. But IMO, I don't believe that the OSD will ever be as responsive as it once was when it comes to now having to overlay on top of 4K video. This is likely why more and more manufacturers are moving away from a live OSD and instead opting for an app or browser based menu for setup and system control. Even Marantz comes out of live video for "Settings". Only "Volume" and "Info" is shown over live video. FWIW, I would welcome this change as long as "Info" and "Volume" were still available to us over live video. Anthem is the latest to have moved in this direction... Gotcha. I like being able to see the OSD, but if it were easier to poll the info I care about to display on a home automation system, or a functional mobile app, etc... I'd far rather have that. I'd personally accept a total loss of OSD if it meant all other issues were fixed. I'd be curious to know how many other issues are a direct or indirect result of keeping the OSD. |
|
|
|
Post by tngiloy on Feb 19, 2021 17:49:03 GMT -5
My $0.02
I recently sent my RMC-1L back to Emo for repair. Before sending it back I was offered the Beta version of 2.2 (2.17). IIRC, in the installation instructions I could swear it said to set the processor to 'standby- lowest power' before doing the fw upgrade.
I found the email with the link to the beta, but it had been removed, so I couldn't access the instructions. I'm wondering if Keith or Lonnie could verify if turning off VRO was part of the beta instructions. pretty sure it was, because it caught my eye as a new step.
I can confirm that when I did turn VRO off that the beta fw upgrade went better than any others I have done. Very smooth.
I would suggest if trying the fw upgrade to TURN OFF VRO first. And remove all HDMI inputs, either at the source or processor before updating.
It's easier (and looked upon by PETA as more socially acceptable) than sacrificing a live chicken to Jobu. But that option is available if all else fails.
|
|
|
|
Post by Goodfella on Feb 19, 2021 17:54:14 GMT -5
Is this an Apple 4k setting or XMC-2 setting? It’s the setting on the XMC2. Setup -> HDMI CEC-> Input change....need to disable this. Otherwise it’s darn near unusable watching ATV4K. I think Emotiva was working on improving the ARC / CEC experience but didn’t complete it on time. I don’t think this is a showstopper as this has never worked right. So I installed ver2.2 and disabled input change and that fixed my Apple 4k switching issue. I couldn’t get the bass increase under control so I ran Dirac again. Seems to be ok now. Fingers crossed. |
|
KeithL
Administrator
Posts: 10,273
|
Post by KeithL on Feb 19, 2021 17:59:46 GMT -5
We are not officially requiring that you set the Standby mode back to "lowest power"... However, doing so certainly won't hurt anything.  (We often suggest doing so simply as a way to "remove one more unknown from the equation".)
We also don't usually consider it necessary to disconnect your HDMI inputs...
In most cases the processor really doesn't care about that...
However, while our processors don't remember specific details about what's connected to them, many other devices do...
So, for example, you may find that your TV or projector acts oddly after an upgrade, until you fully power cycle it, so that it learns that something has changed.
In general, if things seem to be acting oddly, it's not a bad idea to power cycle all of your HDMI devices after any major change.
My $0.02 I recently sent my RMC-1L back to Emo for repair. Before sending it back I was offered the Beta version of 2.2 (2.17). IIRC, in the installation instructions I could swear it said to set the processor to 'standby- lowest power' before doing the fw upgrade. I found the email with the link to the beta, but it had been removed, so I couldn't access the instructions. I'm wondering if Keith or Lonnie could verify if turning off VRO was part of the beta instructions. pretty sure it was, because it caught my eye as a new step. I can confirm that when I did turn VRO off that the beta fw upgrade went better than any others I have done. Very smooth. I would suggest if trying the fw upgrade to TURN OFF VRO first. And remove all HDMI inputs, either at the source or processor before updating. It's easier (and looked upon by PETA as more socially acceptable) than sacrificing a live chicken to Jobu. But that option is available if all else fails. |
|
