RadioBOSS 7.1 [beta]

When it detects two ads of the same type (one after another), but with a different priority, it will move ads (with the same priority) so that ads of the same type do not follow each other. This requires additional processing, that's why it can slow things a bit. But it results in better quality of the ad blocks.

Perhaps you could include a checkbox in the settings to decide whether or not to use this.
I want to try it to see if it's effective or not, and if I'm not convinced, I want to be able to stop using it because of the extra time it takes.
 
Perhaps you could include a checkbox in the settings to decide whether or not to use this.
I want to try it to see if it's effective or not, and if I'm not convinced, I want to be able to stop using it because of the extra time it takes.
How much slower did it become in your case?

Is it possible to see what percentage applies when it's valid? To see how it holds up track to track.
Yes, will be added in the next update.
 
Ads Scheduler: automatically resolves ads type conflicts where possible
This is a big deal for me. This way, we can avoid competitor ads running one after another.
Yes, I also noticed that the information load is a bit slower, but in my case, it's only about 3-4 seconds, which isn't a problem considering how much I need this new feature.
Of course, it has been in testing since yesterday, and so far, I haven't found any errors.
 
Just liket tomimatko said, it will take 3 or 4 seconds longer for each block selected.I also think it would be interesting to be able to enable or disable this feature.
Maybe I didn’t express myself clearly, but when I run the Ads scheduler, it takes about 3-4 seconds to display all the information in all the blocks, while opening an individual block still takes the same amount of time as before, meaning almost instantly. I have around 20 blocks in each day.

And a question: why are some ads in the right window in normal font and others in italics?
 
Maybe I didn’t express myself clearly, but when I run the Ads scheduler, it takes about 3-4 seconds to display all the information in all the blocks, while opening an individual block still takes the same amount of time as before, meaning almost instantly. I have around 20 blocks in each day.

And a question: why are some ads in the right window in normal font and others in italics?
The italics indicate Ads of the same type that are grouped together.
I have run several tests, and in some cases, Ads of the same type but with different priorities remain stuck together, even when there are other Ads that could be placed in between.
Additionally, it would be great to have a much larger selection window for the type, as the current one is very small.
Since we have several types, searching becomes difficult.
 
I'm testing with TimeStreach.
I've been following your work track by track.
I noticed something strange with file types (the time adjustment changed quite a bit), so I'll keep a close eye on this now.
The strangest thing was with the last track's time. I disabled the adjustment, and now the new track doesn't start on time.
This makes all the previous adjustments in vain (when there was room for more adjustments among all the tracks).
I think there are cases where the faders aren't being taken into account to ensure the start time is correct. (With processed tracks)

1742745570717.png
 
I'm testing with TimeStreach.
I've been following your work track by track.
I noticed something strange with file types (the time adjustment changed quite a bit), so I'll keep a close eye on this now.
The strangest thing was with the last track's time. I disabled the adjustment, and now the new track doesn't start on time.
This makes all the previous adjustments in vain (when there was room for more adjustments among all the tracks).
I think there are cases where the faders aren't being taken into account to ensure the start time is correct. (With processed tracks)

View attachment 14812

Finally the track started before the hour

1742745729238.png
 
Ads of the same type but with different priorities remain stuck together, even when there are other Ads that could be placed in between.
In my opinion, for a commercial radio station, one of the most important aspects is good ad organization because, in the end, that's what we live off. That's why it's very important to me. Since you've already started this topic in this version, it would be good to develop it fully.
When it comes to the changes in this version, this one is the best and most important to me. Thank you for introducing it already in this version.
 
Yes, I also noticed that the information load is a bit slower, but in my case, it's only about 3-4 seconds, which isn't a problem considering how much I need this new feature.
We'll try to optimize it to make it work faster.

Just liket tomimatko said, it will take 3 or 4 seconds longer for each block selected.I also think it would be interesting to be able to enable or disable this feature.
An option will be added to control this. And as mentioned above, optimizations too.

I have run several tests, and in some cases, Ads of the same type but with different priorities remain stuck together, even when there are other Ads that could be placed in between.
Currently it only rearranges the ads within one priority. This will be extended to also handle the case you describe.

Additionally, it would be great to have a much larger selection window for the type, as the current one is very small.
Since we have several types, searching becomes difficult.
The list will be extended.
 
The intro column is very essential in remote voicetracking.
With this, the announcer knows how many seconds they have to speak.
Yes, it's on the list for the next update.

I think there are cases where the faders aren't being taken into account to ensure the start time is correct. (With processed tracks)
It tries its best to take into account anything. Currently, Auto Intro is not considered, also dynamic items with unknown duration like Teaser or Track List are not properly processed. But if there are regular tracks with no Auto Intro it should work properly.

Finally the track started before the hour
Did you do any manual adjustments?
 
But if there are regular tracks with no Auto Intro it should work properly.
Intro tracks need to be addressed at some point. But that's not the case in this example, since playback was fast-forwarded rather than delayed.
In other cases, it seems to be more accurate, which makes me think there are some cases that haven't yet been addressed when calculating the start time. (In addition to tracks with unknown duration)
 
I first tried the Render Playlist to a file command in the sheduler. Is there a specific way to provide parameters? I tried it like this:
renderplaylist E:\audio\#automatische Beitragserstellung\News\Playlist\news.m3u8 E:\audio\News\news.mp3
 
I'll write about a few things. When I open the item "Process Music Tracks" screen reader all beautifully reads. When you move on the taba at a time at a time, I get to the list where my screen reader reads all the items, moving up the arrows up below, which can be processed. For all these items, there are cards that can be easily activated. I didn't even think that the list serves. With the help of the video, I realized that the options that will be processed will be turned on and off. However Screen Reader does not announce whether the item is turned on or off. Is this possible to fix this?
Another thing I will write about is the Playlist Generator Pro. I have two categories. One has 86 thousand songs and the other 270 thousand songs. I have three priority rules in each of them to give priority to unused songs. These are the rules: "increase priority by 100% for tracks whereplaycount is less than 0", "increase priority by 100% for tracks where playcount is less than avg" and "DECREASE PRIORITY BY 100% FOR TRACK WHERE PLAYCOUNT IS GREATHER THAN AVG". For a long time, Radioboss needs a lot of time to create a playlist. Specifically, he now needs about 4 hours and 50 minutes to create a playlist. Today I concluded why he needed so much time. The problem is these rules in priorities. When I deleted them, the Playlist Generator Pro created a playlist in 22 minutes. What could be done here to fit in that limit of 9000 seconds to make playlists?
 
Last edited:
No, I didn't make a manual adjustment. I even disabled all events for tracking.
I see the effort to improve this, but I still think there's more to it. :)
The start time is critical for TimeStreach.
Time Stretch is based on Start Time so calculating it is critical, so at this point we'd need to improve Start Time which will in turn make Time Stretch better. Sometimes it doesn't take into account "Override previous track mix" point correctly, maybe this is the case?

I first tried the Render Playlist to a file command in the sheduler. Is there a specific way to provide parameters? I tried it like this:
renderplaylist E:\audio\#automatische Beitragserstellung\News\Playlist\news.m3u8 E:\audio\News\news.mp3
The command format is in the User Manual (menu Help, Contents):
renderplaylist Format|Samplerate|Channels|Bitrate|FILENAMERender playlist to a file.

Parameters
Format - mp3, ogg, aac, flac, opus
Samplerate - sample rate value (e.g. 44100)
Channels - 1 (mono) or 2 (stereo).
Bitrate - bitrate for encoding, kbps.
Filename - file name (full path)

Example:
renderplaylist mp3|44100|2|128|D:\myshow.mp3

For all these items, there are cards that can be easily activated. I didn't even think that the list serves. With the help of the video, I realized that the options that will be processed will be turned on and off. However Screen Reader does not announce whether the item is turned on or off. Is this possible to fix this?
Unfortunately, this is a limitation of the control that we use, it can't be fixed at this point. We'll consider redoing the UI to use standard checkboxes.

Specifically, he now needs about 4 hours and 50 minutes to create a playlist. Today I concluded why he needed so much time. The problem is these rules in priorities. When I deleted them, the Playlist Generator Pro created a playlist in 22 minutes. What could be done here to fit in that limit of 9000 seconds to make playlists?
4 hours is indeed a lot. We're working on optimizing the playlist generator, maybe those optimizations will be released in this beta.
 
4 hours is indeed a lot. We're working on optimizing the playlist generator, maybe those optimizations will be released in this beta.
Since the new Constraint rules, the time it takes to generate a playlist has increased exponentially.
Some optimization would be great.
 
Back
Top