Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Aug 16, 2020 11:52:07 GMT -5
Is there a beta in testing that attempts to addresses the audio drop/lock issue? ...Those with inquiring minds want to know .
|
|
|
Post by megash0n on Aug 16, 2020 12:06:50 GMT -5
Is there a beta in testing that attempts to addresses the audio drop/lock issue? ...Those with inquiring minds want to know . Wouldn't it be swell to have a post from Emotiva, or page on their website, that lists known, and accepted bugs and that development is underway to correct said bugs?
|
|
|
Post by aliensoundtome on Aug 16, 2020 12:06:56 GMT -5
Not that I know of but I am currently testing to find the problem. It seems not to be a cause then effect problem. Hard to find when error occurs whenever it feels like it.
Oh sure hope your(brucelee) not using V1.0 but instead V1.10 or V2.0
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Aug 16, 2020 15:20:15 GMT -5
Not that I know of but I am currently testing to find the problem. It seems not to be a cause then effect problem. Hard to find when error occurs whenever it feels like it. Oh sure hope your(brucelee) not using V1.0 but instead V1.10 or V2.0 Rolled back to 1.10. With 1.10 when there's an audio dropout changing sources or input type usually fixes things (ie. going from DD 2.0 to DD 5.1)- this is NOT the case for 2.0. My guess is that they've changed something in the input checking timing. I wonder if checking for DSD isn't part of the problem (...what ever happened to giving us the option to disable DSD on HDMI to speed things up?)
|
|
richb
Sensei
Oppo Beta Group - Audioholics Reviewer
Posts: 859
|
Post by richb on Aug 16, 2020 15:26:07 GMT -5
Not that I know of but I am currently testing to find the problem. It seems not to be a cause then effect problem. Hard to find when error occurs whenever it feels like it. Oh sure hope your(brucelee) not using V1.0 but instead V1.10 or V2.0 Rolled back to 1.10. With 1.10 when there's an audio dropout changing sources or input type usually fixes things (ie. going from DD 2.0 to DD 5.1)- this is NOT the case for 2.0. My guess is that they've changed something in the input checking timing. I wonder if checking for DSD isn't part of the problem (...what ever happened to giving us the option to disable DSD on HDMI to speed things up?) I have a similar experience. Lost audio requires a hard boot (with front panel) or power cycle. I bought an Denon AVR-X3700H AVR and its switching speed is within a second of the RMC-1. All inputs have an option for Auto or HDMI 1.4, so backward compatibility is a problem for them as well. DSD is interesting but it makes two independent options DSD and HDMI 1.4. - Rich
|
|
|
Post by markc on Aug 16, 2020 17:16:43 GMT -5
I see others are reporting distorion issues with the July 2020 firmware. I have begun to notice this when listening to pure analog. I am listening to a Gold Note PH-10 phono preamp going into the XMC-2 XLR Analog inputs. I have the mode set to Reference Direct. Very audible distortion is occuring. I finally turned off the XMC-2 via the back AC switch (Cold boot). I then went straight to my phono input and there is no distortion. But, when I went to check my level settings in setup and then exited, the distortion returns? Again, I cold booted and when I return to my phono input there is no distortion. I have no idea how this may relate to Dirac issues since I have not implemented Dirac? I also noticed that when the distortion is introduced the gain on the XMC-2 is reduced about 10db? For example for the same listening level I am at 18 on the volume control with the distortion. When I reboot and there is no distortion, I am at 28 on the volume control? I think this may be a serious problem? Not everyone hears it, and not all the time. But it seems some people hear it incessantly. I heard it one time two weeks ago and only on one multichannel track. It went away after a reboot. Then yesterday after doing a Dirac calibration I heard it only on the center channel of music upmixed from 2-channel with the Dolby upmixer. Switched to stereo for a while and then back to upmix and it was gone. Then it happened again with a Netflix series in 5.1. It was fine, then we started a new episode of the series and the distortion was only on the center channel on the peaks of dialogue. Power cycled the XMC-2 (in VRO mode) and the distortion was gone. I have also seen wide volume swings with a given piece of music played at different times. Not sure if this is relevant, but the only times I heard the distortion were after having done a Dirac calibration and loaded new filters, without having cycled power between loading the filters and hearing the distortion. A few times I have had some high frequency warbling coming from the tweeters of various surround speakers - it sounds like a fly trapped in the speaker. I think it has been with PCM audio only and a reset was needed to clear it. Is this the sort of sound others are thinking of?
|
|
|
Post by AudioHTIT on Aug 16, 2020 20:25:51 GMT -5
Is there a beta in testing that attempts to addresses the audio drop/lock issue? ...Those with inquiring minds want to know . It was posted in your own thread over a week ago by Lonnie, there's not much more of a definitive source.
|
|
|
Post by markc on Aug 17, 2020 9:28:08 GMT -5
Is there a beta in testing that attempts to addresses the audio drop/lock issue? ...Those with inquiring minds want to know . I'm not sure I want to know the answer! Not unless the beta testers are a different batch than the ones who failed in beta testing 2.0 To be honest, may as well just pass any new firmware out to the masses rather than get it scrutinised with inscrutiny.
|
|
cawgijoe
Emo VIPs
"We made too many of the wrong mistakes." - Yogi Berra
Posts: 4,914
|
Post by cawgijoe on Aug 17, 2020 9:35:06 GMT -5
Is there a beta in testing that attempts to addresses the audio drop/lock issue? ...Those with inquiring minds want to know . I'm not sure I want to know the answer! Not unless the beta testers are a different batch than the ones who failed in beta testing 2.0 To be honest, may as well just pass any new firmware out to the masses rather than get it scrutinised with inscrutiny. The answer is yes....Lonnie mentioned it.
|
|
|
Post by megash0n on Aug 17, 2020 10:33:53 GMT -5
I'm not sure I want to know the answer! Not unless the beta testers are a different batch than the ones who failed in beta testing 2.0 To be honest, may as well just pass any new firmware out to the masses rather than get it scrutinised with inscrutiny. The answer is yes....Lonnie mentioned it. The underlying point here is that we forget or miss it when a small post is made among 500 pages of posts on a topic. The master list of known and fixed issues allows all of us to simply go to the thread, or website link, to see what's up and to log an unknown issue because we can't find our issue among the other known issues. We could appropriately track the number of people with the same or similar issue. It seems way easier to me for all involved and cuts down on a massive amount of off topic discussion.
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Aug 17, 2020 10:40:06 GMT -5
Is there a beta in testing that attempts to addresses the audio drop/lock issue? ...Those with inquiring minds want to know . It was posted in your own thread over a week ago by Lonnie, there's not much more of a definitive source. I re-read my thread and saw that on Aug 6 Lonnie posted "Yes, we are working on the audio drop..." I guess that means a beta is in testing? A "we're getting close" would be even more encouraging.
|
|
|
Post by bitzerjdb on Aug 17, 2020 10:45:50 GMT -5
The answer is yes....Lonnie mentioned it. The underlying point here is that we forget or miss it when a small post is made among 500 pages of posts on a topic. The master list of known and fixed issues allows all of us to simply go to the thread, or website link, to see what's up and to log an unknown issue because we can't find our issue among the other known issues. We could appropriately track the number of people with the same or similar issue. It seems way easier to me for all involved and cuts down on a massive amount of off topic discussion. Taking it one step further, how about letting people vote on the issues (who has it), and give it a severity or impact rating. This would be a simple way to prioritize the things that are impacting the most people. I was responsible for a large ITSM system at a Multi-National company, I had +80k users. Our issue tracker was a huge hit, it allowed us to know what we needed to be working on with a limited staff. In addition, we had a column that showed the status of the issue. In process, Under review, Fixed, etc. If you do it via a registered user approach, it also gives Emotiva a list of people to contact for the specific issues, or to test the fix. Targeted Beta's are always better than a broad brush approach.
|
|
|
Post by doc1963 on Aug 17, 2020 10:56:13 GMT -5
The underlying point here is that we forget or miss it when a small post is made among 500 pages of posts on a topic. The master list of known and fixed issues allows all of us to simply go to the thread, or website link, to see what's up and to log an unknown issue because we can't find our issue among the other known issues. We could appropriately track the number of people with the same or similar issue. It seems way easier to me for all involved and cuts down on a massive amount of off topic discussion. Taking it one step further, how about letting people vote on the issues (who has it), and give it a severity or impact rating. This would be a simple way to prioritize the things that are impacting the most people. I was responsible for a large ITSM system at a Multi-National company, I had +80k users. Our issue tracker was a huge hit, it allowed us to know what we needed to be working on with a limited staff. In addition, we had a column that showed the status of the issue. In process, Under review, Fixed, etc. If you do it via a registered user approach, it also gives Emotiva a list of people to contact for the specific issues, or to test the fix. Targeted Beta's are always better than a broad brush approach. + one million.... I couldn't agree with this more...!!!
|
|
|
Post by marcl on Aug 17, 2020 11:24:58 GMT -5
Not everyone hears it, and not all the time. But it seems some people hear it incessantly. I heard it one time two weeks ago and only on one multichannel track. It went away after a reboot. Then yesterday after doing a Dirac calibration I heard it only on the center channel of music upmixed from 2-channel with the Dolby upmixer. Switched to stereo for a while and then back to upmix and it was gone. Then it happened again with a Netflix series in 5.1. It was fine, then we started a new episode of the series and the distortion was only on the center channel on the peaks of dialogue. Power cycled the XMC-2 (in VRO mode) and the distortion was gone. I have also seen wide volume swings with a given piece of music played at different times. Not sure if this is relevant, but the only times I heard the distortion were after having done a Dirac calibration and loaded new filters, without having cycled power between loading the filters and hearing the distortion. A few times I have had some high frequency warbling coming from the tweeters of various surround speakers - it sounds like a fly trapped in the speaker. I think it has been with PCM audio only and a reset was needed to clear it. Is this the sort of sound others are thinking of? Yes. It's definitely a digital sounding distortion and related to peaks in amplitude, but it doesn't change character with amplitude. When I first heard it, it seemed to be on all channels but not with every file I played. second time it was only the center dialogue of 5.1.
|
|
cawgijoe
Emo VIPs
"We made too many of the wrong mistakes." - Yogi Berra
Posts: 4,914
|
Post by cawgijoe on Aug 17, 2020 11:38:59 GMT -5
It was posted in your own thread over a week ago by Lonnie, there's not much more of a definitive source. I re-read my thread and saw that on Aug 6 Lonnie posted "Yes, we are working on the audio drop..." I guess that means a beta is in testing? A "we're getting close" would be even more encouraging. There should be a Post that addresses what is being fixed, worked on, status, etc. Agree. Might be a good idea to send Lonnie and /or Keith that suggestion. That way, if it's kept up, people can see it and not constantly ask what's happening. In the meantime, it's being tested.
|
|
|
Post by megash0n on Aug 17, 2020 12:24:40 GMT -5
The underlying point here is that we forget or miss it when a small post is made among 500 pages of posts on a topic. The master list of known and fixed issues allows all of us to simply go to the thread, or website link, to see what's up and to log an unknown issue because we can't find our issue among the other known issues. We could appropriately track the number of people with the same or similar issue. It seems way easier to me for all involved and cuts down on a massive amount of off topic discussion. Taking it one step further, how about letting people vote on the issues (who has it), and give it a severity or impact rating. This would be a simple way to prioritize the things that are impacting the most people. I was responsible for a large ITSM system at a Multi-National company, I had +80k users. Our issue tracker was a huge hit, it allowed us to know what we needed to be working on with a limited staff. In addition, we had a column that showed the status of the issue. In process, Under review, Fixed, etc. If you do it via a registered user approach, it also gives Emotiva a list of people to contact for the specific issues, or to test the fix. Targeted Beta's are always better than a broad brush approach. I concur. This is all pretty basic and common stuff, but sure does work well. It also aids in tracking effort over time with different areas of problems so you can trend them. These trends tell you whether you are doing well or need to refresh the team performing the work. It allows you to hold people accountable.
|
|
cawgijoe
Emo VIPs
"We made too many of the wrong mistakes." - Yogi Berra
Posts: 4,914
|
Post by cawgijoe on Aug 17, 2020 12:28:10 GMT -5
Taking it one step further, how about letting people vote on the issues (who has it), and give it a severity or impact rating. This would be a simple way to prioritize the things that are impacting the most people. I was responsible for a large ITSM system at a Multi-National company, I had +80k users. Our issue tracker was a huge hit, it allowed us to know what we needed to be working on with a limited staff. In addition, we had a column that showed the status of the issue. In process, Under review, Fixed, etc. If you do it via a registered user approach, it also gives Emotiva a list of people to contact for the specific issues, or to test the fix. Targeted Beta's are always better than a broad brush approach. I concur. This is all pretty basic and common stuff, but sure does work well. It also aids in tracking effort over time with different areas of problems so you can trend them. These trends tell you whether you are doing well or need to refresh the team performing the work. It allows you to hold people accountable. I'm not worried about holding people accountable as much as it would be nice to have a place to go to see what the issues are, what is being worked, and what the status is. It's up to the company to hold their own accountable.
|
|
|
Post by megash0n on Aug 17, 2020 12:32:34 GMT -5
I concur. This is all pretty basic and common stuff, but sure does work well. It also aids in tracking effort over time with different areas of problems so you can trend them. These trends tell you whether you are doing well or need to refresh the team performing the work. It allows you to hold people accountable. I'm not worried about holding people accountable as much as it would be nice to have a place to go to see what the issues are, what is being worked, and what the status is. It's up to the company to hold their own accountable. that's exactly what I mean.
|
|
Lsc
Emo VIPs
Posts: 3,348
|
Post by Lsc on Aug 17, 2020 12:55:06 GMT -5
It was posted in your own thread over a week ago by Lonnie, there's not much more of a definitive source. I re-read my thread and saw that on Aug 6 Lonnie posted "Yes, we are working on the audio drop..." I guess that means a beta is in testing? A "we're getting close" would be even more encouraging. This means Lonnie’s developers are looking into the issue. Once they have identified the issue and made the necessary code changes to fix the problem, Emotiva will test it internally first. Then they will usually (but not always) release it to the beta team to take a look.
|
|
|
Post by bolle on Aug 18, 2020 11:05:44 GMT -5
The idea of a bug tracking tool for customers to report tools and also for Emotiva to transparently communicate what they are working on has come up several times in the last years. During the XMC-1 HDMI board V3 beta I also formulated a simple checklist / guideline as a help for filling out good bug reports. No interest in continuing this apparently.
I guess they just don´t have a responsible head of QM with enough weight in their organisational structure. Otherwise there should have been some noteable process improvements in the last years.
|
|