Coming up next window issue

mbabb

Member
Each hour RB has a scheduled event to play a URL audio stream. The scheduled event appears to work just fine, but in the "Coming Up Next" window it says "[Buffering: 5%] Network Stream" and doesn't really change. Any idea of what is happening? I have attached a screenshot.

I also see in the "Log" that there are several instances of the URL printed when there should be only one. I have also attached a screenshot. At 8:00:00 AM the ID plays, then after that there are multiple instances of the URL. Any idea?

Running Windows 11 Home
RadioBoss Standard 6.2.1.0


mike
 

Attachments

  • ComingUPNext.png
    ComingUPNext.png
    14.2 KB · Views: 131
  • Log.png
    Log.png
    82.4 KB · Views: 131
Each hour RB has a scheduled event to play a URL audio stream. The scheduled event appears to work just fine, but in the "Coming Up Next" window it says "[Buffering: 5%] Network Stream" and doesn't really change. Any idea of what is happening? I have attached a screenshot.
Yes, there's room for improvement. I have scheduled it for the next update.

I also see in the "Log" that there are several instances of the URL printed when there should be only one. I have also attached a screenshot. At 8:00:00 AM the ID plays, then after that there are multiple instances of the URL. Any idea?
It adds an entry each time it starts playing it.
 
The stream started playing at 8:00 AM via scheduled events, and if it's already playing, why do I see and entry at 8:03:22 AM, 8:05:26 AM, 8:07:27 AM, 8:12:32 AM and so on....shouldn't there be just the one entry in the log at 8:00:00 AM when the event started? there are no other commands or events telling RB to "start" playing the stream.
 
The stream started playing at 8:00 AM via scheduled events, and if it's already playing, why do I see and entry at 8:03:22 AM, 8:05:26 AM, 8:07:27 AM, 8:12:32 AM and so on....shouldn't there be just the one entry in the log at 8:00:00 AM when the event started? there are no other commands or events telling RB to "start" playing the stream.
Yes, that's odd. Does the stream actually stop and restart when you see those log entries? Does it happen always?
 
Sorry for the delay. It appears that when the streams audio drops and then comes back, that it is printing an entry in the log each time it does that.
 
Sorry for the delay. It appears that when the streams audio drops and then comes back, that it is printing an entry in the log each time it does that.
I don't recall the exact details now, but I think it's how it's supposed to work.
 
This stream is supposed to begin at 8:00 AM via scheduled events, so there must be a reason for that. However, why do the log entries indicate that it started at 8:03:22 AM, 8:05:26 AM, 8:07:27 AM, 8:12:32 AM, and so on even after the stream has already started?
The RB was responding to no commands or events when it first began playing the stream at 8:00:00 AM, and despite the fact that I am not sure why there is only one entry in the log when the event first began at 8:00:00 AM, and I do not believe that the program was responding to any commands or events that instructed the program to start playing the stream at the time that the event first began.
 
Back
Top