|
|
Post by ElectricKoolAid on Feb 22, 2021 12:10:17 GMT -5
I "liked" one the of the posts that was getting a lot of positive feedback a few pages back. Basically saying I would like to keep the OSD for Volume and Info but would like everything else to be through a web interface. But this point brings out something I hadn't considered. I leave the network cable unplugged from my XMC-2 because the unit was locking up constantly before I unplugged it. To the point it wasn't really unusable for more than 10 to 15 minutes before locking up completely again and having to do a hard reset. I haven't tried plugging back in the network cable to the unit since updating to v 2.2, but have little hope anything's changed since I have heard to updates related to that - or if there's even a consensus that this is an actual bug/issue. One thing I may try is disabling CEC when I plug the cable in next time. I've had issues with CEC being enabled and the unit locking up, but it's far less frequently than when I had the network cable plugged in. Maybe the two of them together were causing the issues much more frequently when combined? I have not idea honestly, just thinking out loud. I have my network cable always plugged in connected directly to my router. No issues with lock-up. This is likely a CEC issue. Thanks, I've heard some say they don't have issues with network cable plugged in and others that do. I seem to be in the camp that do. I will give it a try again this week and try and report back with my findings. |
|
|
|
Post by doc1963 on Feb 22, 2021 12:41:22 GMT -5
I have my network cable always plugged in connected directly to my router. No issues with lock-up. This is likely a CEC issue. Thanks, I've heard some say they don't have issues with network cable plugged in and others that do. I seem to be in the camp that do. I will give it a try again this week and try and report back with my findings. I have no issues with my network interface and can leave my cable plugged in without causing any residual problems. Do yourself a favor... If upon plugging in your network cable, you do not acquire an IP address please try the following... - Leave the network cable plugged in. - Make sure "Use DHCP" is enabled in the network settings. - Shut down your processor normally. - Turn off the rear panel power switch. - Press and hold in the front panel Standby button for 10 seconds. - Wait 5 minutes. - Turn the rear panel power switch back on. - Wait 1 minute. - Press the front panel Standby button and wait for a full system boot up. Now see if you acquire an IP address. |
|
|
|
Post by SticknStones on Feb 22, 2021 13:01:24 GMT -5
My RMC-1L is identical in speed to what you've shown here using the ATV4K. Thanks for posting...  So is mine (XMC-2)....thank you for taking the time. That is a good response time. It's not normal to need to change settings all the time. I cannot remember the last time I was in the XMC settings. |
|
|
|
Post by megash0n on Feb 22, 2021 13:06:02 GMT -5
Considering that HDMI handshaking and negotiation is such a challenge in the first place, I'm not sure this would do anything but cause more issues. A fully functional API, that is a bit more consumable for the masses, would make this " Web interface " concept far easier while satisfy many other consumer requests. And you think going to a whole new setup they haven't done before is going to have few issues? The same programmers you continue to beat on? Not in this lifetime. Not at all. Everything has a pro or a con or both. It seems like the code has been rewritten from the ground up a handful of times already. If we are to actually get DLBC, we may be looking at another rewrite. If you read into many things that are said here and there, you can see there are architectural issues with the code. Being a code writer is not the same is being a code architect. Sometimes you can be both. There are far brighter minds here on this topic than I. I'll let them educate us on that. Having a long-term vision of what the code needs to accomplish, how to interface with it, how to build structure and process around new code or function implementation (which includes mandatory API commands), a "no-shortcut" attitude, and on and on... would just be an overall benefit in my mind. When one jumps from fire to fire, one tends to not see the larger picture. And, I could very well be entirely wrong in my opinions. Lastly, anything I have ever said about the "programmers" has not been intended to be a personal attack on "the programmer". People can only do what they can do with what they are given. My issues have always been with the lack of ownership/leadership taken to remediate the trend. The path to greatness always starts with our leaders. The team is only carrying out the leader's mission. |
|
|
|
Post by dukesd on Feb 22, 2021 13:11:36 GMT -5
First attempt to upgrade to 2.2 and it hung on the Copying part of the firmware from the USB stick. I decided to power cycle on the rear switch and re-attempt, second try went normally.
|
|
|
|
Post by megash0n on Feb 22, 2021 13:12:31 GMT -5
I have my network cable always plugged in connected directly to my router. No issues with lock-up. This is likely a CEC issue. Thanks, I've heard some say they don't have issues with network cable plugged in and others that do. I seem to be in the camp that do. I will give it a try again this week and try and report back with my findings. Emotiva has been quoted many times stating there could be issues with the cable plugged in. We just all experience something different at times, and over time. My NIC issues are a prime example. I've had such a frustrating time with my NIC for the first 10ish months of ownership. It hasn't stopped working for me ... Well, y'all get the point. If I actually say it.. I'll go home and it will end up being down for some reason. No rhyme of reason as to why it has decided to function electrically better over the past couple months. I wish I could unplug it, but I have to use the API. Well, I guess I could technically use other options as well. Just trying to stay current with times I guess. |
|
cawgijoe
Emo VIPs 
"When you come to a fork in the road, take it." - Yogi Berra
Posts: 5,033
|
Post by cawgijoe on Feb 22, 2021 13:24:22 GMT -5
Thanks, I've heard some say they don't have issues with network cable plugged in and others that do. I seem to be in the camp that do. I will give it a try again this week and try and report back with my findings. Emotiva has been quoted many times stating there could be issues with the cable plugged in. We just all experience something different at times, and over time. My NIC issues are a prime example. I've had such a frustrating time with my NIC for the first 10ish months of ownership. It hasn't stopped working for me ... Well, y'all get the point. If I actually say it.. I'll go home and it will end up being down for some reason. No rhyme of reason as to why it has decided to function electrically better over the past couple months. I wish I could unplug it, but I have to use the API. Well, I guess I could technically use other options as well. Just trying to stay current with times I guess. I'm not a computer person, so I just don't understand why some would have a problem with a ethernet cable connected to the processor and their router and others doing the same, not. I have Verizon FIOS and originally used their supplied modem/router. No issues with the XMC-1. I then decided that since I will never get FIOS TV, I would switch the Verizon router out with a Netgear router purchased at Costco. I'm connected with the XMC-2 24/7 and it just works. I have FIOS Gig speed. I know you all have been over this many times, so rehashing is probably not wise at this point....and it's over my head anyway....it would be nice if there was a simple explanation. |
|
|
|
Post by ElectricKoolAid on Feb 22, 2021 13:39:59 GMT -5
Emotiva has been quoted many times stating there could be issues with the cable plugged in. We just all experience something different at times, and over time. My NIC issues are a prime example. I've had such a frustrating time with my NIC for the first 10ish months of ownership. It hasn't stopped working for me ... Well, y'all get the point. If I actually say it.. I'll go home and it will end up being down for some reason. No rhyme of reason as to why it has decided to function electrically better over the past couple months. I wish I could unplug it, but I have to use the API. Well, I guess I could technically use other options as well. Just trying to stay current with times I guess. I'm not a computer person, so I just don't understand why some would have a problem with a ethernet cable connected to the processor and their router and others doing the same, not. I have Verizon FIOS and originally used their supplied modem/router. No issues with the XMC-1. I then decided that since I will never get FIOS TV, I would switch the Verizon router out with a Netgear router purchased at Costco. I'm connected with the XMC-2 24/7 and it just works. I have FIOS Gig speed. I know you all have been over this many times, so rehashing is probably not wise at this point....and it's over my head anyway....it would be nice if there was a simple explanation. I would consider myself decently tech savvy as I work in IT but I'll be the first to admit there's still so much that I don't know or fully understand when it comes to computers and networking and all of that. If I remember correctly, someone was saying that the NIC could be getting bogged down by network traffic or something in a post a few weeks ago I think? What I took away from it is that it could be highly dependent on the persons home network setup, but again I could be misremembering/misunderstanding. I have a slightly more complicated network setup at home than the average user, but I wouldn't say it's anything too crazy. I have cable internet through Mediacom running at 200 mbps coming in to an Arris Surfboard modem, then to my Unifi UDM Pro router. I thin have the UDM pro connected to a Unifi 24 port second gen POE switch. Then from that switch, I have a network cable that runs to my AV rack which houses a Unifi Flex Mini switch. I have my XMC-2 connected to that Flex Mini switch along with my Nvidia Shield. Like I said, I'll have to do some more testing and follow up with my results. I have been planning on running a new cable from my networking rack to my AV rack so we'll see if maybe that has any effect as well. |
|
|
|
Post by ElectricKoolAid on Feb 22, 2021 13:42:30 GMT -5
Thanks, I've heard some say they don't have issues with network cable plugged in and others that do. I seem to be in the camp that do. I will give it a try again this week and try and report back with my findings. Emotiva has been quoted many times stating there could be issues with the cable plugged in. We just all experience something different at times, and over time. My NIC issues are a prime example. I've had such a frustrating time with my NIC for the first 10ish months of ownership. It hasn't stopped working for me ... Well, y'all get the point. If I actually say it.. I'll go home and it will end up being down for some reason. No rhyme of reason as to why it has decided to function electrically better over the past couple months. I wish I could unplug it, but I have to use the API. Well, I guess I could technically use other options as well. Just trying to stay current with times I guess. Just curious, what do you mean you have to use the API? Is there some way you can interface with the processor over the internet? Or am I completely misinterpreting your comment? Lol |
|
|
|
Post by megash0n on Feb 22, 2021 14:45:09 GMT -5
Emotiva has been quoted many times stating there could be issues with the cable plugged in. We just all experience something different at times, and over time. My NIC issues are a prime example. I've had such a frustrating time with my NIC for the first 10ish months of ownership. It hasn't stopped working for me ... Well, y'all get the point. If I actually say it.. I'll go home and it will end up being down for some reason. No rhyme of reason as to why it has decided to function electrically better over the past couple months. I wish I could unplug it, but I have to use the API. Well, I guess I could technically use other options as well. Just trying to stay current with times I guess. I'm not a computer person, so I just don't understand why some would have a problem with a ethernet cable connected to the processor and their router and others doing the same, not. I have Verizon FIOS and originally used their supplied modem/router. No issues with the XMC-1. I then decided that since I will never get FIOS TV, I would switch the Verizon router out with a Netgear router purchased at Costco. I'm connected with the XMC-2 24/7 and it just works. I have FIOS Gig speed. I know you all have been over this many times, so rehashing is probably not wise at this point....and it's over my head anyway....it would be nice if there was a simple explanation. With all due respect, you probably won't get the explanation because of why the issue is there in the first place. I'm some cases it is QC or just bad luck. Things break. Nothing is perfect. In most other cases, it is related to software or coding on the Emotiva side. They do what they do for whatever reason they do it. But, from an IT perspective, if a network interface is powered on, and non "administratively shut down", then when it senses electricity on specific pins, those tiny LEDs light up. We don't have to take the conversation any further than that. No other software or feature really matters. The challenge is, from the little I know, is that Emotiva decides, through some sort of logic, whether or not the network interface should be "up" or "active". Most any device you have will likely be active, from a basic electricity standpoint" within a second or two of turning it on. Emotiva builds in some predetermined amount of time before the kernel (underlying OS) allows the NIC to even attempt to start it's process of turning on. You'll get some reason for it, and in their mind, I'm sure it makes sense. It's just another entry in the 3 inch book of "How To Operate an Emotiva Processor". So, I can imagine that if one has some other issue that causes a problem during boot, during usage, etc... I could indirectly keep the NIC from starting back up on the next reboot... Or several reboots. It doesn't look like the kernel has been updated since 2018, so it doesn't appear that any effort has been put into resolution on this item. |
|
|
|
Post by megash0n on Feb 22, 2021 14:47:16 GMT -5
I'm not a computer person, so I just don't understand why some would have a problem with a ethernet cable connected to the processor and their router and others doing the same, not. I have Verizon FIOS and originally used their supplied modem/router. No issues with the XMC-1. I then decided that since I will never get FIOS TV, I would switch the Verizon router out with a Netgear router purchased at Costco. I'm connected with the XMC-2 24/7 and it just works. I have FIOS Gig speed. I know you all have been over this many times, so rehashing is probably not wise at this point....and it's over my head anyway....it would be nice if there was a simple explanation. I would consider myself decently tech savvy as I work in IT but I'll be the first to admit there's still so much that I don't know or fully understand when it comes to computers and networking and all of that. If I remember correctly, someone was saying that the NIC could be getting bogged down by network traffic or something in a post a few weeks ago I think? What I took away from it is that it could be highly dependent on the persons home network setup, but again I could be misremembering/misunderstanding. I have a slightly more complicated network setup at home than the average user, but I wouldn't say it's anything too crazy. I have cable internet through Mediacom running at 200 mbps coming in to an Arris Surfboard modem, then to my Unifi UDM Pro router. I thin have the UDM pro connected to a Unifi 24 port second gen POE switch. Then from that switch, I have a network cable that runs to my AV rack which houses a Unifi Flex Mini switch. I have my XMC-2 connected to that Flex Mini switch along with my Nvidia Shield. Like I said, I'll have to do some more testing and follow up with my results. I have been planning on running a new cable from my networking rack to my AV rack so we'll see if maybe that has any effect as well. love those flex switches. Dirt cheap and rock solid! I bought a 5 pack a while back and glad I did. |
|
|
|
Post by megash0n on Feb 22, 2021 14:51:25 GMT -5
Emotiva has been quoted many times stating there could be issues with the cable plugged in. We just all experience something different at times, and over time. My NIC issues are a prime example. I've had such a frustrating time with my NIC for the first 10ish months of ownership. It hasn't stopped working for me ... Well, y'all get the point. If I actually say it.. I'll go home and it will end up being down for some reason. No rhyme of reason as to why it has decided to function electrically better over the past couple months. I wish I could unplug it, but I have to use the API. Well, I guess I could technically use other options as well. Just trying to stay current with times I guess. Just curious, what do you mean you have to use the API? Is there some way you can interface with the processor over the internet? Or am I completely misinterpreting your comment? Lol I don't think you are. They have a network API that uses UDP. Most functions have a command associated, but not all. The response data is a bit cumbersome because it is in XML format. If I'm not mistaken, there's no good way to just probe for a simple setting, and get a simple response via API. You have to run it through a parser, etc etc etc. I had a plan to write some stuff to do this, and actually build a web frontend for everyone. But yeah.. Kinda hard to do that when you don't have access to all the functions. They prioritize fixes, and then later implement into the API if they think it is necessary. Edit: I'm using python for the control commands btw. I have a thread on here where I discussed it and provided an example of my code. Currently, it gets executed from EventGhost, but I'm planning to offload all the python to the Raspberry Pi or an ESP32 module I am working on to parse the XML data for my home automation system. (HASS) |
|
cawgijoe
Emo VIPs
"When you come to a fork in the road, take it." - Yogi Berra
Posts: 5,033
|
Post by cawgijoe on Feb 22, 2021 15:12:20 GMT -5
I'm not a computer person, so I just don't understand why some would have a problem with a ethernet cable connected to the processor and their router and others doing the same, not. I have Verizon FIOS and originally used their supplied modem/router. No issues with the XMC-1. I then decided that since I will never get FIOS TV, I would switch the Verizon router out with a Netgear router purchased at Costco. I'm connected with the XMC-2 24/7 and it just works. I have FIOS Gig speed. I know you all have been over this many times, so rehashing is probably not wise at this point....and it's over my head anyway....it would be nice if there was a simple explanation. With all due respect, you probably won't get the explanation because of why the issue is there in the first place. I'm some cases it is QC or just bad luck. Things break. Nothing is perfect. In most other cases, it is related to software or coding on the Emotiva side. They do what they do for whatever reason they do it. But, from an IT perspective, if a network interface is powered on, and non "administratively shut down", then when it senses electricity on specific pins, those tiny LEDs light up. We don't have to take the conversation any further than that. No other software or feature really matters. The challenge is, from the little I know, is that Emotiva decides, through some sort of logic, whether or not the network interface should be "up" or "active". Most any device you have will likely be active, from a basic electricity standpoint" within a second or two of turning it on. Emotiva builds in some predetermined amount of time before the kernel (underlying OS) allows the NIC to even attempt to start it's process of turning on. You'll get some reason for it, and in their mind, I'm sure it makes sense. It's just another entry in the 3 inch book of "How To Operate an Emotiva Processor". So, I can imagine that if one has some other issue that causes a problem during boot, during usage, etc... I could indirectly keep the NIC from starting back up on the next reboot... Or several reboots. It doesn't look like the kernel has been updated since 2018, so it doesn't appear that any effort has been put into resolution on this item. So, I guess what your are saying is that Emotiva has their own implementation that may or may not cause problems depending on your home network configuration....I think that's what I'm hearing, and since no update has been made since 2018, those with issues need to do work arounds....don't want to put words in our mouth....so my system "works" with their current implementation. |
|
|
|
Post by ElectricKoolAid on Feb 22, 2021 15:22:49 GMT -5
Just curious, what do you mean you have to use the API? Is there some way you can interface with the processor over the internet? Or am I completely misinterpreting your comment? Lol I don't think you are. They have a network API that uses UDP. Most functions have a command associated, but not all. The response data is a bit cumbersome because it is in XML format. If I'm not mistaken, there's no good way to just probe for a simple setting, and get a simple response via API. You have to run it through a parser, etc etc etc. I had a plan to write some stuff to do this, and actually build a web frontend for everyone. But yeah.. Kinda hard to do that when you don't have access to all the functions. They prioritize fixes, and then later implement into the API if they think it is necessary. Edit: I'm using python for the control commands btw. I have a thread on here where I discussed it and provided an example of my code. Currently, it gets executed from EventGhost, but I'm planning to offload all the python to the Raspberry Pi or an ESP32 module I am working on to parse the XML data for my home automation system. (HASS) That makes sense. That would be awesome to have a way to control/interact with the processor via web ui/ HASS. I currently run HASS as well, although I haven't fully set up everything yet so I've just been playing with it from time to time. Eventually I'd like to deploy it for our home automation. I'll have to check out your other post. |
|
|
|
Post by ElectricKoolAid on Feb 22, 2021 15:24:38 GMT -5
I would consider myself decently tech savvy as I work in IT but I'll be the first to admit there's still so much that I don't know or fully understand when it comes to computers and networking and all of that. If I remember correctly, someone was saying that the NIC could be getting bogged down by network traffic or something in a post a few weeks ago I think? What I took away from it is that it could be highly dependent on the persons home network setup, but again I could be misremembering/misunderstanding. I have a slightly more complicated network setup at home than the average user, but I wouldn't say it's anything too crazy. I have cable internet through Mediacom running at 200 mbps coming in to an Arris Surfboard modem, then to my Unifi UDM Pro router. I thin have the UDM pro connected to a Unifi 24 port second gen POE switch. Then from that switch, I have a network cable that runs to my AV rack which houses a Unifi Flex Mini switch. I have my XMC-2 connected to that Flex Mini switch along with my Nvidia Shield. Like I said, I'll have to do some more testing and follow up with my results. I have been planning on running a new cable from my networking rack to my AV rack so we'll see if maybe that has any effect as well. love those flex switches. Dirt cheap and rock solid! I bought a 5 pack a while back and glad I did. Yes they are awesome! I almost bought the 3 pack but only had a use for one at the moment. I'll probably pick up some more when I eventually run some network cable through the house (hopefully, haven't figured out how hard that will be yet with our new house). I'm loving the Unifi ecosystem. Being able to see all my devices and network settings all in one place has been great. Eventually I'll set up VLANS for everything, especially when getting more IOT devices set up. |
|
|
|
Post by megash0n on Feb 22, 2021 15:32:57 GMT -5
With all due respect, you probably won't get the explanation because of why the issue is there in the first place. I'm some cases it is QC or just bad luck. Things break. Nothing is perfect. In most other cases, it is related to software or coding on the Emotiva side. They do what they do for whatever reason they do it. But, from an IT perspective, if a network interface is powered on, and non "administratively shut down", then when it senses electricity on specific pins, those tiny LEDs light up. We don't have to take the conversation any further than that. No other software or feature really matters. The challenge is, from the little I know, is that Emotiva decides, through some sort of logic, whether or not the network interface should be "up" or "active". Most any device you have will likely be active, from a basic electricity standpoint" within a second or two of turning it on. Emotiva builds in some predetermined amount of time before the kernel (underlying OS) allows the NIC to even attempt to start it's process of turning on. You'll get some reason for it, and in their mind, I'm sure it makes sense. It's just another entry in the 3 inch book of "How To Operate an Emotiva Processor". So, I can imagine that if one has some other issue that causes a problem during boot, during usage, etc... I could indirectly keep the NIC from starting back up on the next reboot... Or several reboots. It doesn't look like the kernel has been updated since 2018, so it doesn't appear that any effort has been put into resolution on this item. So, I guess what your are saying is that Emotiva has their own implementation that may or may not cause problems depending on your home network configuration....I think that's what I'm hearing, and since no update has been made since 2018, those with issues need to do work arounds....don't want to put words in our mouth....so my system "works" with their current implementation. I suppose one could have the chicken and the egg conversation. I'm really not sure to be honest. We'd need an awful lot of data to even formulate a strong opinion. I'm only providing observations along with some assumptions based on things I've been told by a few there while mixing that with decades of hands on experience with networking gear. I don't know man. Some people have issues and some don't. The truth is likely somewhere in the middle. |
|
|
|
Post by megash0n on Feb 22, 2021 15:37:11 GMT -5
I don't think you are. They have a network API that uses UDP. Most functions have a command associated, but not all. The response data is a bit cumbersome because it is in XML format. If I'm not mistaken, there's no good way to just probe for a simple setting, and get a simple response via API. You have to run it through a parser, etc etc etc. I had a plan to write some stuff to do this, and actually build a web frontend for everyone. But yeah.. Kinda hard to do that when you don't have access to all the functions. They prioritize fixes, and then later implement into the API if they think it is necessary. Edit: I'm using python for the control commands btw. I have a thread on here where I discussed it and provided an example of my code. Currently, it gets executed from EventGhost, but I'm planning to offload all the python to the Raspberry Pi or an ESP32 module I am working on to parse the XML data for my home automation system. (HASS) That makes sense. That would be awesome to have a way to control/interact with the processor via web ui/ HASS. I currently run HASS as well, although I haven't fully set up   everything yet so I've just been playing with it from time to time. Eventually I'd like to deploy it for our home automation. I'll have to check out your other post. Here's a screen shot of one of my dashboards. Edit: not sure what happened there uploading from my phone, but you get the point. 🤪 Also, we are probably veering off thread here, so please feel free to post any questions on the thread I started regarding this. |
|
|
|
Post by jasonf on Feb 22, 2021 16:18:20 GMT -5
I don't think you are. They have a network API that uses UDP. Do you know where this network API is documented? I've searched around a bit and can't find it anywhere. Edit: I just found this - I guess it's the latest? emotivalounge.proboards.com/post/759343 |
|
|
|
Post by jasonf on Feb 22, 2021 16:28:52 GMT -5
Some new observations from me:
I've given up on ARC. I was running my PS5 directly into TV, so that I could have game specific settings on that input, and using ARC for video. My Samsung Q90R has a breakout box for the electronics, so it's ideal for me to just run everything into the TV and use ARC. Unfortunately I can't do this for the AppleTV, because LPCM and Atmos.
Anyways, on ARC:
- I'm still getting processor "slowdown" that requires a restart sometimes when switching to ARC. I haven't been able to get a consistent repro on this issue.
- I get a lot of audible popping, even just switching between screens in a game. I encountered one massive pop that was more like a 'bang' and seriously concerned me about my speakers.
- Something seems different about the gain or EQ on ARC, and I ran into a situation where my speakers had audible clipping while playing the game Control - also concerned me about my speakers.
|
|
|
|
Post by megash0n on Feb 22, 2021 18:21:17 GMT -5
|
|
