Hi @Benjamin. Still having the same problem with this one station, just now and any time I try it, other stations are fine. Actually put in a new router after the problem started (UniFi Dream Machine), and machine running Roon core has been restarted multiple times.
Thanks for the follow-up! To confirm, is your core device running on a Mac device running Catalina? I see that you mention ‘Hackintosh’ on your community profile. If this is indeed still your core device, can you provide further information about it?
Please, if you haven’t yet, hardwire your core directly to your router, bypassing any network gear in between. Reboot your core and router, and let me know if your issue persists.
Does this issue happen when streaming audio to the system output of your core device? I would test out different endpoints to confirm if the issue persists.
I am also seeing a Macbook Air being used as a core device from your account info. If you could please recreate the issue and use the directions found here and send over a set of logs to our File Uploader, that would be helpful.
I just rebooted the Core machine and restarted the router. The Core machine does not have an audio output, when I enable System Output and play to that I can’t get anything to start. When I selected a KEF LSX endpoint it seemed like it played for more than a couple of seconds, but then I stopped the stream and now it only goes for a second or two with this radio station (all other radio stations, Tidal, and local music are fine). Same with all Meridian endpoints, and same with System Output enabled on my desktop.
My wife has a MacBook Air that she uses with the app, but she connects to the Core (Marshalls-iMac-2). Maybe I accidentally downloaded/ran the server on it once? I don’t see a MacBook Air core anywhere in our setup.
I stopped the Core, zipped the log files, and uploaded at your link, femanburch.zip.
Unrelated, how do you compose a reply that includes snippets of the post you are replying to?
@BrianW has the same problem I have with this station with the .m3u8 stream (the other streams he has to use VPN and so not Roon, I think). So if it is a hardware thing it is not only my hardware.
On a temporary core, I guess I can try to do that (shut down the existing core, figure out how to set up a new one, not sure if that will require moving license, etc.). But now I am realizing that I am running Core using the Roon application and not Roon Server, and given that the Core is on a dedicated machine in an equipment rack and is not an endpoint I guess it should really be running Roon Server and not Roon? To do this maybe I follow the instructions here, even though the “new” Core is going to sit on the same computer?
Hardware I am using for Roon Core is also getting a little old. Haswell i7 probably has enough horsepower, but 4TB mechanical (WD Black) has been powered on for almost 6 years, so probably a failure waiting to happen. I could put ROCK on a NUC i5-5250 I am using for Roon Bridge for multichannel, or get a new more highly configured NUC, or maybe a base configuration M2 Mac Mini, for those might like to run Core and also Remote for the multichannel.
Deleting and re-adding to the library does not fix the problem.
Yes, if you could reproduce the issue a few times and share the specific date and time in which the issue occurs, and share that information here, that would be helpful.
In this case, if you open your Macbook Air like you were using it as a remote, and head into Roon Settings>About you will be able to disconnect from your current core, and setup your Macbook Air as a temporary core. You’ll need to re-add the troublesome radio station, as it will load a fresh database once you swap your core. No need to restore a database in this case since we’re just testing things.