RadioBOSS Cloud

Major problem this morning with stream retrieval of podcasts. Here's an example of what my log shows.
2025-05-09 9:00:12 AM
https://www.srnnews.com/feed/?post_type=audio-news&audio-category=hourly-news podcast
2025-05-09 9:00:53 AM
Stream connection lost/unstable: reconnecting
2025-05-09 9:01:35 AM
Stream connection lost/unstable: reconnecting

Each time it reconnects, it starts the podcast over, but not the time it is set to play for, so you get something that restarts multiple times, but does not play to completion. Not sure what should or could be done, but it has happened multiple times this morning.
 
Hello,
I could use a bit of help with setting up requests. I understand how to turn them on, and how to insert the code, but I need to find a way to have them be able to play just about any time, as long as that time is NOT within a few minutes of another scheduled event. I have a general music playlist scheduled hourly, but then an ads playlist (consisting of ad intro, ads, ad outro), another playlist consisting of a podcast followed by a station sweeper, etc. Goal is to not have requests pop up right in the middle of those specific playlists. Those playlists are set to start after currently playing track. So what I don't want to happen is, for example, requests to fall between ad intro and ads, or between my ads and ad outro. Or, between the podcast and the sweeper. Does this make sense? But, any other time in the hour is fair game. If I just insert the command at specified times, I run the risk of that happening. How would you go about this, and with as few scheduler items as possible? Ideally, at least 3 requests should be inserted per hour, if any exist at all. What would be absolutely amazing, is in the playlist builder, an option could be given to "replace track with request if one is available." Any way you could add that? Then, I could specify exactly which tracks are available to be replaced, exactly where requests should fall, and where they should not. You could add this option in the same set of options where you choose whether or not to ignore protection rules, whether or not track is sequential or random, etc. Please please consider adding this. That would enable requests in a much quicker way, and not clutter up the scheduler with tons of events. And, it would, I think, be easier to implement than heavy if then logic in the scheduler, but allow us to achieve the same result.

Also, on an unrelated note, I have a podcast that always seems to play quiet. Is it possible to create a filetype for that, and give it a boost of say +1 db?
Thanks in advance for your help.
 
If I just insert the command at specified times, I run the risk of that happening. How would you go about this, and with as few scheduler items as possible?
You can configure the "playrequestedsong" event to queue after the scheduled tracks, this way it will not interrupt other schedules. Currently, this is the only option.
 
Back
Top