Jump to content

bmrowe

c4Forums Member
  • Content Count

    25
  • Joined

  • Last visited

About bmrowe

  • Rank
    Control4 End User

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Interesting development today in this saga. I realized that the network switch is managed. It's a Netgear SafePro switch. Once I logged into it, it was super far behind in firmware updates and had IGMP snooping turned on. I updated the firmware and turned the setting off. Could be coincidental, but had a long string of uninterrupted playback tonight in testing. I did notice that the audio would occasionally skip for less than a second, but never cut out. I've never had it skip before, so I'm wondering if those skips would have been director restarts before this latest change. If anyone has any further suggestions, I'm all ears.
  2. Thanks! If I just plug in the digital coax, I won't need to have the dealer change anything? I can just start using a second stream in a different room? That'd be pretty slick.
  3. I'm actually only using 2 of the inputs on the matrix. If I'm streaming music to the ea3, how would it choose to send out analog or digital? Given the same source, is one going to allow for higher quality?
  4. I've spent quite a bit of time searching without much luck. I've got a ea-3 connected to a triad 8x8 over analog today. The 8x8 does have digital coax inputs. Curious what the best practice is here. Would I see any improved audio quality switching from analog to digital? Listening sources are primarily high-res Spotify and Tidal. Thanks!
  5. Nope - at least not a residential one as its a fiber setup with no modem.
  6. I must have had a streak of luck yesterday. The system is back to being unable to get through 1 entire song. Any troubleshooting help would be greatly appreciated.
  7. Still troubleshooting and wanted to update progress in case it either sheds light in what might be wrong, or help someone else dealing with the same issue. This morning, I unchecked 'enable DHCP snooping' on my ubiquiti usg. I was able to go from not being able to get through one high bitrate MQA song to it playing a couple hours of music without a break. However, about 2.5 hrs in it restarted again. As a next step, I've enabled 'make controller discoverable on L2 network'. At about 2 hours of playback without issue after this change.
  8. Also potentially interesting - in the digital media section the 'max quality' is greyed out at 48 / 24 and the active quality is higher. I have been having these issues while playing high bitrate stuff from tidal masters. Any correlation? Edit: I unchecked the MQA box in the tidal settings and was able to play ~10 songs in a row before it died and restarted. Not sure what that tells us.
  9. This is from the ioserver log, wondering if each line might be a restart - which would tie back to when I was listening to music today and the 10 day gap between this set of instances and prior.
  10. Bumping this back up. Issue is still occurring. This morning probably had 10-15 restarts. Will listen to Tidal or Spotify and in 1-2 songs the music will cut out. Right after that, Composer HE will lose connection with Director. 1-2 minutes later I can restart the music. Any ideas on logs to look at or how to even go about diagnosing this? It is definitely worse today than it has ever been. The only recent change I've made is to add an Amazon Echo to my network and enable voice control. At this point, music playback is essentially broken. I'm also wondering if the music is coincidental and the director is just restarting all the time. Is there any way to see that? This is all on version 3.1.3.574826-res
  11. I was. Thanks for the tip, just changed it. Have you seen using ISP DNS causing these types of issues?
  12. Using default 192.168.1.1 for DNS. Attached is a screenshot.
  13. Debugging a weird issue. On Director version 3.1.3.574826 (5/19/20). Sometimes when I'm playing Tidal, the music will stop, and it seems the director is restarting. I've attached a log and see a variety of network connectivity issues. Any insight in how to even start troubleshooting this? Network wise, I'm running a netgear unmanaged switch and a ubiquiti USG-3P. Thanks in advance for the help! director log.txt
  14. Thats what I had been assuming, but how could it possibly not reach localhost? The controller is also the 192.168.1.11
  15. Bumping this old thread since no resolution came up. I'm diagnosing random Director restarts. Seeing these same type of errors among others. See below. I'm confused where the IP addresses below are even coming from -- especially 255.255.255.255 and 127.0.0.1. Also FUBAR_1 is a terrifying error name. 2020-09-18 17:58:22.863 -0500 ea3-000FFF19B8B0 [3136] ERROR: handleConnect(): Error connecting [192.168.1.46:23]: Connection refused 2020-09-18 17:58:22.866 -0500 ea3-000FFF19B8B0 [3136] ERROR: Flash: Failed to retreive device info from 255.255.255.255 2020-09-18 17:58:27.864 -0500 ea3-000FFF19B8B0 [3136] ERROR: handleConnect(): Error connecting [192.168.1.46:23]: Connection refused 2020-09-18 17:58:35.484 -0500 ea3-000FFF19B8B0 [3136] ERROR: Flash: Failed to retreive device info from 239.255.255.250 2020-09-18 17:58:37.589 -0500 ea3-000FFF19B8B0 [3136] ERROR: Flash: Failed to retreive device info from 192.168.1.46 2020-09-18 17:58:39.694 -0500 ea3-000FFF19B8B0 [3136] ERROR: Flash: Failed to retreive device info from 192.168.1.210 2020-09-18 17:58:41.799 -0500 ea3-000FFF19B8B0 [3136] ERROR: Flash: Failed to retreive device info from 192.168.1.11 2020-09-18 17:58:43.907 -0500 ea3-000FFF19B8B0 [3136] ERROR: Flash: Failed to retreive device info from 192.168.1.10 2020-09-18 17:58:56.527 -0500 ea3-000FFF19B8B0 [3136] ERROR: Flash: Failed to retreive device info from 127.0.0.1 2020-09-18 18:03:57.134 -0500 ea3-000FFF19B8B0 [3136] ERROR: asyncSendTo(): The specified address is invalid: NOT_SET:8750: Invalid argument 2020-09-18 18:03:57.134 -0500 ea3-000FFF19B8B0 [3136] ERROR: Flash: Failed to send info request: Invalid argument 2020-09-18 18:03:57.135 -0500 ea3-000FFF19B8B0 [3136] ERROR: Flash: Failed to retrieve device info at NOT_SET: 2020-09-18 18:03:57.135 -0500 ea3-000FFF19B8B0 [3136] ERROR: Flash: FUBAR_1: reached impossible state 0
×
×
  • Create New...