cawgijoe
Emo VIPs
"When you come to a fork in the road, take it." - Yogi Berra
Posts: 5,035
|
Post by cawgijoe on Nov 21, 2022 9:36:03 GMT -5
It's incredibly interesting to me how one person can have problems like this yet others not.
1. Processor does not lock....has never locked. No loss of video or audio. Weird. 2. Can't comment here because I don't have Atmos yet. 3. Update Fonts issue is known and being worked. Does not apply to my case because I use VRO. Ahem... Are my posts the only posts you read? "one person"? I'm happy for you that your processor is working at your standards and use. As far as I can tell, you are the main one mentioning the locked issue. Others have mentioned the height speakers and of course the Fonts issue affects most everyone. I have not gone through to see how many have had the locked issue which to me would be the most serious of these issues....what is the common denominator?
|
|
|
Post by bitzerjdb on Nov 21, 2022 9:38:20 GMT -5
I don't blame the the Beta Testers, I assume there is enough of them so that the errors we are seeing have been known and reported. The updating Fonts issues had to be well known. I don't "blame" Emotiva either... I DO question their decision to release the firmware knowing that problem existed. If you really really wanted to release it, it should have been called out as an issue. If you are going to tell me you didn't know, then I question the Beta Testing program. Decisions like this do nothing to build trust in the process. I can't comment on anything the Beta group saw regarding the "Fonts" message. I highly doubt it was there prior to release of 3.1 or it would have been mentioned. The firmware was released because the pitchforks were raised due to the long time waiting for fixes. This was not a "complete" attempt at fixes. It was partial. That has been documented. Emotiva has hired an additional resource (expert) to work this through. I'm confident it will happen and get better for those remaining issues. If you have developed "new"issues due to 3.1, please reach out to Emotiva to make you voices heard. Emotiva is monitoring this board, but they are not always on it. Already have....
|
|
|
Post by geebo on Nov 21, 2022 9:38:43 GMT -5
Waiting to upgrade until I get a feel for new issues. For those who have upgraded, is the current 3.1 version worth the upgrade? It was for me. If you use Low Power Standby and you got your processor before December 2021 be aware you will have an extended boot time. If you use VRO then you won't. Some people are bothered by long boot times while others don't mind.
|
|
|
Post by bitzerjdb on Nov 21, 2022 9:41:58 GMT -5
Waiting to upgrade until I get a feel for new issues. For those who have upgraded, is the current 3.1 version worth the upgrade? Bluntly...HELL NO! I now have a non functioning BluRay player and a freaking "Updating Fonts" delay. It makes the Rethink High End message sting that much more :-(
|
|
|
Post by bitzerjdb on Nov 21, 2022 9:47:37 GMT -5
I don't blame the the Beta Testers, I assume there is enough of them so that the errors we are seeing have been known and reported. The updating Fonts issues had to be well known. I don't "blame" Emotiva either... I DO question their decision to release the firmware knowing that problem existed. If you really really wanted to release it, it should have been called out as an issue. If you are going to tell me you didn't know, then I question the Beta Testing program. Decisions like this do nothing to build trust in the process. I can't comment on anything the Beta group saw regarding the "Fonts" message. I highly doubt it was there prior to release of 3.1 or it would have been mentioned. The firmware was released because the pitchforks were raised due to the long time waiting for fixes. This was not a "complete" attempt at fixes. It was partial. That has been documented. Emotiva has hired an additional resource (expert) to work this through. I'm confident it will happen and get better for those remaining issues. If you have developed "new"issues due to 3.1, please reach out to Emotiva to make you voices heard. Emotiva is monitoring this board, but they are not always on it. You cannot comment on the Updating Fonts issue... OK, does anyone here not have it? No comment is necessary, this was a complete miss. There is not a single reason you release something with this bug that seems to impact everyone. There was a conscious decision to release the firmware with this issue.... without any regard to the user base. Yes I'm pissed.. Super pissed. But, on the bright side, the family pushing me to get rid of this damn thing and buy something new. I think I see a shiny new Christmas Present in my future!
|
|
|
Post by PaulBe on Nov 21, 2022 9:48:16 GMT -5
Ahem... Are my posts the only posts you read? "one person"? I'm happy for you that your processor is working at your standards and use. As far as I can tell, you are the main one mentioning the locked issue. Others have mentioned the height speakers and of course the Fonts issue affects most everyone. I have not gone through to see how many have had the locked issue which to me would be the most serious of these issues....what is the common denominator? At this point, I'm the last person who has mentioned the issue. My first mention of locking is this morning. I don't know what is the common denominator. Why would you draw conclusions about me when you haven't 'gone through' the post stream? Everyone who updated to FW3.1 is a beta tester. The difference between the Beta Test Team and us, is that we share our findings in public. I hope you are not having a problem with that.
|
|
|
Post by DellaDog on Nov 21, 2022 9:51:00 GMT -5
Ahem... Are my posts the only posts you read? "one person"? I'm happy for you that your processor is working at your standards and use. As far as I can tell, you are the main one mentioning the locked issue. Others have mentioned the height speakers and of course the Fonts issue affects most everyone. I have not gone through to see how many have had the locked issue which to me would be the most serious of these issues....what is the common denominator? Check back a few pages. Try messing with the network settings - for me it results in a frozen unit. Try scrolling through the inputs - for me it results in a frozen unit. Try randomly turning it on from standby - for me "Rethinking High End" never goes away - results in a frozen unit. There is no common denominator other than Emotiva and FW 3.1
|
|
ttocs
Global Moderator
I always have a wonderful time, wherever I am, whomever I'm with. (Elwood P Dowd)
Posts: 8,168
|
Post by ttocs on Nov 21, 2022 9:51:57 GMT -5
You cannot comment on the Updating Fonts issue... OK, does anyone here not have it? Yes.
|
|
|
Post by DellaDog on Nov 21, 2022 9:53:13 GMT -5
And that ticks me off as well - why do recent builds have an improved HDMI board while early adopters are now having 3 minute plus boot times.
|
|
cawgijoe
Emo VIPs
"When you come to a fork in the road, take it." - Yogi Berra
Posts: 5,035
|
Post by cawgijoe on Nov 21, 2022 9:55:13 GMT -5
As far as I can tell, you are the main one mentioning the locked issue. Others have mentioned the height speakers and of course the Fonts issue affects most everyone. I have not gone through to see how many have had the locked issue which to me would be the most serious of these issues....what is the common denominator? At this point, I'm the last person who has mentioned the issue. My first mention of locking is this morning. I don't know what is the common denominator. Why would you draw conclusions about me when you haven't 'gone through' the post stream? I'm not drawing any conclusions about you and don't want a confrontation. I just find it strange because it doesn't happen to me. I certainly would want to know why this is happening. If this is happening to others, I would want to compare notes.
|
|
|
Post by PaulBe on Nov 21, 2022 9:58:19 GMT -5
At this point, I'm the last person who has mentioned the issue. My first mention of locking is this morning. I don't know what is the common denominator. Why would you draw conclusions about me when you haven't 'gone through' the post stream? I'm not drawing any conclusions about you and don't want a confrontation. I just find it strange because it doesn't happen to me. I certainly would want to know why this is happening. If this is happening to others, I would want to compare notes.Great! Comparing notes is exactly what I'm doing here! We are now on the same page.
|
|
|
Post by PaulBe on Nov 21, 2022 10:00:31 GMT -5
You cannot comment on the Updating Fonts issue... OK, does anyone here not have it? Yes. Perhaps a worthy re-mention is that processors with the series 8 HDMI boards are the ones with the Update Fonts delay.
|
|
cawgijoe
Emo VIPs
"When you come to a fork in the road, take it." - Yogi Berra
Posts: 5,035
|
Post by cawgijoe on Nov 21, 2022 10:02:23 GMT -5
I'm not drawing any conclusions about you and don't want a confrontation. I just find it strange because it doesn't happen to me. I certainly would want to know why this is happening. If this is happening to others, I would want to compare notes.Great! Comparing notes is exactly what I'm doing here! We are now on the same page. So....is there a common denominator besides the 3.1 update between those with the lock up issue when you compare notes that can lead to what might be causing this? Or is it random? This would drive me nuts if it happened to me, so I hear you!
|
|
|
Post by jdmusante on Nov 21, 2022 10:09:29 GMT -5
Are there any specific settings I should be looking at with regard to an Oppo? You’re saying your 203 works just fine. My 205 does work, it just has a hell of a time with the handshake. So much so that my TV loses its signal multiple times before latching on. Once connected, the Oppo works fine. Plays 4K blu rays without issue with good sound/surround sound. I don’t have this issue with my Apple TV. I didn't change a thing and my 203 is working fine with my RMC-1L as it always has. If you haven't already I would check out the cables and their physical connections if for no other reason than to just rule them out. I will try try this when I get back on Wednesday but I’m pretty sure the cables are seated properly. I’m using Zeskit Maya 8k HDMI cables I bought off Amazon. IIRC I bought those because someone here was using them successfully. Are there any other HDMI cables that someone could recommend? I can order one and see if the cable makes a difference. Would be awesome if that was the problem.
|
|
cawgijoe
Emo VIPs
"When you come to a fork in the road, take it." - Yogi Berra
Posts: 5,035
|
Post by cawgijoe on Nov 21, 2022 10:09:53 GMT -5
And that ticks me off as well - why do recent builds have an improved HDMI board while early adopters are now having 3 minute plus boot times. Yeah...wish I had the new board too....I think, and I could be wrong, the new board will also be part of the "upgrade" when it happens. We will have to pay for the upgrade of course.
|
|
|
Post by PaulBe on Nov 21, 2022 10:11:00 GMT -5
Great! Comparing notes is exactly what I'm doing here! We are now on the same page. So....is there a common denominator besides the 3.1 update between those with the lock up issue when you compare notes that can lead to what might be causing this? Or is it random? This would drive me nuts if it happened to me, so I hear you! Before updating to FW 3.1, from FW 2.3, it was an occasional problem for me; maybe once every week or two. After updating to FW 3.1 it occurs everyday. I have no conclusions yet beyond the FW update. I need more data.
|
|
|
Post by bitzerjdb on Nov 21, 2022 10:14:24 GMT -5
Perhaps a worthy re-mention is that processors with the series 8 HDMI boards are the ones with the Update Fonts delay. Ok, so did anyone with those boards beta test the firmware? Could they have mentioned it was a known issue? On that note, I'm done here. I'm not going to comment anymore, I don't want to offend anyone with my newly found negativity. I reported my issues to Emotiva directly, and will wait for their reply. Thanks everyone for all the help in the past. I wish you all a great holiday!
|
|
cawgijoe
Emo VIPs
"When you come to a fork in the road, take it." - Yogi Berra
Posts: 5,035
|
Post by cawgijoe on Nov 21, 2022 10:15:16 GMT -5
So....is there a common denominator besides the 3.1 update between those with the lock up issue when you compare notes that can lead to what might be causing this? Or is it random? This would drive me nuts if it happened to me, so I hear you! Before updating to FW 3.1, from FW 2.3, it was an occasional problem for me; maybe once every week or two. After updating to FW 3.1 it occurs everyday. I have no conclusions yet beyond the FW update. I need more data. Paul...I'm sure you have listed the equipment you have....maybe not....that might help someone here to troubleshoot....including type and length of HDMI cables....just a suggestion....don't shoot me...
|
|
|
Post by geebo on Nov 21, 2022 10:19:15 GMT -5
I didn't change a thing and my 203 is working fine with my RMC-1L as it always has. If you haven't already I would check out the cables and their physical connections if for no other reason than to just rule them out. I will try try this when I get back on Wednesday but I’m pretty sure the cables are seated properly. I’m using Zeskit Maya 8k HDMI cables I bought off Amazon. IIRC I bought those because someone here was using them successfully. Are there any other HDMI cables that someone could recommend? I can order one and see if the cable makes a difference. Would be awesome if that was the problem. I'm using the Zeskit Maya cables and they've been working perfectly. The longest I have are 2 meters. I would try physically unplugging and reconnecting them just to be sure. And maybe swapping one of your others for the one connected to the Oppo. I would also unplug the Oppo's power connection along with the TV and turning off the rear switch on the XMC for a couple minutes then turn everything back on.
|
|
|
Post by PaulBe on Nov 21, 2022 10:39:47 GMT -5
Perhaps a worthy re-mention is that processors with the series 8 HDMI boards are the ones with the Update Fonts delay. Ok, so did anyone with those boards beta test the firmware? Could they have mentioned it was a known issue? On that note, I'm done here. I'm not going to comment anymore, I don't want to offend anyone with my newly found negativity. I reported my issues to Emotiva directly, and will wait for their reply. Thanks everyone for all the help in the past. I wish you all a great holiday! The current crop of common issues had to be known by all on the inside. "It's a new world"! Happy Thanksgiving!
|
|