RadioBOSS 7.1 [beta]

I’ve sent the ads_export_log.txt file by email, but in any case, that file is only created during the export process.
Please try the latest 7.1.1.3 update. To create a log for the "Test all blocks" function, hold Shift key while pressing this button.
If it's still slow for you, please send all ads_* related logs.

The problem isn’t with the ad export process. The first issue occurs when the window with the different time blocks starts building.
I’m attaching a video that shows this.
The second issue happens when clicking “Test all blocks,” which takes a very long time.

As you can see in the video, there are only 151 ads in total!
Showing the number of ads takes less than a second here, event with your previous file with about 2000 ads in the list. I'm not sure why it's so slow in your case. We no longer able to reproduce the slowness issue here. With typical 40-100 active ads it works almost instantly for all operations.
Please send us the adsettings.ini file for further testing.
 
I still have the problem that some of my playlists, which I generate automatically via the scheduler to compile the news, are causing an error. I still assume that this is a bug in version 7.1 Beta — in my case, 7.1.2 Release Candidate. The reason for this assumption is that the playlist creation works without any issues on my second RadioBOSS instance, which is still running version 7.0.8.0.
Can you please specify what is the error message? Also logs from Playlist Generator will help a lot - please click Settings, Open Settings Folder, Log folder- playlistgenerator.log

For example, my news playlist is generated correctly, as is a playlist for a morning segment. However, the playlists for event tips and regional news are not generated, and an error message appears instead.
Does it always happen with the same presets, or it's working sometimes?

Secondly, it often happens that individual files scheduled as events do appear in the log — meaning the event is triggered — but the file itself does not appear in the playlist and is therefore not played.
Please check the insert position in the event, maybe the event's tracks are inserted at the end of the playlist or somewhere else where you didn't see them. If the event starts a playlist, check how many tracks were inserted.
 
Please try the latest 7.1.1.3 update. To create a log for the "Test all blocks" function, hold Shift key while pressing this button.
If it's still slow for you, please send all ads_* related logs.


Showing the number of ads takes less than a second here, event with your previous file with about 2000 ads in the list. I'm not sure why it's so slow in your case. We no longer able to reproduce the slowness issue here. With typical 40-100 active ads it works almost instantly for all operations.
Please send us the adsettings.ini file for further testing.

HI, I sent via email!
tkz!
 
Please try the latest 7.1.1.3 update. To create a log for the "Test all blocks" function, hold Shift key while pressing this button.
If it's still slow for you, please send all ads_* related logs.


Showing the number of ads takes less than a second here, event with your previous file with about 2000 ads in the list. I'm not sure why it's so slow in your case. We no longer able to reproduce the slowness issue here. With typical 40-100 active ads it works almost instantly for all operations.
Please send us the adsettings.ini file for further testing.

I suggest you install RB on another PC and try AdsScheduler there... without a doubt, it will behave differently!
 
HI, I sent via email!
tkz!
Thank you, from the log we can't single out an operation that slows things down, it looks like overall performance is low.

I suggest you install RB on another PC and try AdsScheduler there... without a doubt, it will behave differently!
The only difference we see is that RadioBOSS 32-bit is considerably faster than RadioBOSS 64-bit, so I suggest you to try the 32-bit version to see how it performs.
 
Thank you, from the log we can't single out an operation that slows things down, it looks like overall performance is low.


The only difference we see is that RadioBOSS 32-bit is considerably faster than RadioBOSS 64-bit, so I suggest you to try the 32-bit version to see how it performs.

Honestly, the speed with the x32 version has improved incredibly! Now it’s much faster. I don’t technically understand why, it should be the other way around!

Tell me, aside from the installation folder (I'm planning to install the x32 version in the same folder as the x64 one), what else changes? Any detail is helpful, since I do a lot of things using RB's folders.

Anyway, “Test all blocks” is now faster, but not instant
It takes 9 seconds for 151 ads. With the x64 version, it took 19 seconds.
 
Thank you, from the log we can't single out an operation that slows things down, it looks like overall performance is low.


The only difference we see is that RadioBOSS 32-bit is considerably faster than RadioBOSS 64-bit, so I suggest you to try the 32-bit version to see how it performs.

Ask ChatGPT why a 32-bit version of a program is faster than the 64-bit version, and you'll be surprised by the answer!
 
Honestly, the speed with the x32 version has improved incredibly! Now it’s much faster. I don’t technically understand why, it should be the other way around!
Actually, 32-bit version is supposed to be faster. Memory pointers are twice size in 64-bits, and Ads Scheduler uses lots of small memory blocks (that is, lots of memory pointers). Unless you have a specific reason to use 64-bit version, 32-bit version is recommended. Playlist Generator and other modules will also be faster there.

Tell me, aside from the installation folder (I'm planning to install the x32 version in the same folder as the x64 one), what else changes? Any detail is helpful, since I do a lot of things using RB's folders.
You can install 32-bit version to the same folder where you have 64-bit version now. If you didn't use any 64-bit plugins, nothing else needs to be done.

Anyway, “Test all blocks” is now faster, but not instant
It takes 9 seconds for 151 ads. With the x64 version, it took 19 seconds.
That's still a lot. On the slowest PC we have here (Ryzen 7 3700U) it takes less than two seconds. But this PC is doing nothing else - only testing RadioBOSS. Maybe in your case CPU is loaded with other tasks making Ads Scheduler slower.

Ask ChatGPT why a 32-bit version of a program is faster than the 64-bit version, and you'll be surprised by the answer!
I'm not sure what it has to say about it, but the core issue is memory pointer size as mentioned above, and also immature x64 compiler in Delphi. In one of the next updates we'll probably optimize Ads Schedule further to utilize more CPU cores.
 
RadioBOSS 7.1.1.4

Ads Scheduler
: Everything works

Blocks testing: less than a second. Whether for 10 blocks or 180 blocks in a profile.
FYI, almost all screens have warnings voluntarily during testing.

There is no longer an alert message when I switch from one profile to another.


Questions and comments about how Ads Scheduler works:​
In the Ad Properties of an ad, you can add one or more tracks. I notice that the same track is always selected during playback: the first one.​
What's the point of adding a second or several other tracks after the first?​
The instructions mention "main track" and "alternative track." How do I use these alternative tracks? I'm asking out of curiosity.​
In Block Setup => Event Properties => Overlay Playback
Everything works correctly.​
You should adjust the type of mix points for the tracks that are selected for the START block and the END block because, currently, the "Start" and "End" points of a track are taken into account.​
The music volume varies correctly, but based on these two points.​
This doesn't seem appropriate to me. Instead, "Mix Start" and "Mix" should be enabled to make the sequence more fluid.​
For example, the music level rises after an effect that should normally mix with the music like a wave.​
I don't use this feature, but during testing, I noticed this small aesthetic flaw in the sound.​



Playlist Generator Pro: Everything works

Created an identical playlist on Beta 7.1.1.4 and the current version 7.0.8.0. No major issues, but the processing time seems strangely longer on the Beta version:

Manual playlist creation using Playlist Generator Pro – RadioBOSS 7.1.1.4 (x86) (Intel Core i7-8850H CPU @ 2.60GHz – Windows 11): 43 seconds
Playlist creation using the event scheduler – RadioBOSS 7.1.1.4 (x86) (Intel Core i7-8850H CPU @ 2.60GHz – Windows 11): 39 seconds
Manual playlist creation using Playlist Generator Pro – RadioBOSS 7.0.8.0 (x64) (12th Gen Intel Core i7-12700H 2.30GHz – Windows 11): 25 seconds
Playlist creation using the event scheduler – RadioBOSS 7.0.8.0 (x64) (12th Gen Intel Core i7-12700H 2.30GHz – Windows 11): 24 seconds


My setup:​
The computer isn't the same. My installation of version 7.1.1.4 is 32-bit. Version 7.0.8.0 is 64-bit.​
I find that the creation time for this same playlist is longer on the Beta 7.1.1.4 version than on the current version 7.0.8.0.​
Furthermore, the computer running version 7.0.8.0 runs the audio processing and encoder at the same time.​

All my other playlists are created faster on version 7.0.8.0.​
The ratio is almost identical: Beta 7.1.1.4 is 1.63 times slower than version 7.0.8.0 (including the event planner).​
When I install the 64-bit version of RadioBOSS 7.1.1.4, the ratio is higher at 1.95.​
So, it's even longer, which is normal, according to the latest comments I read in this thread.​
Compared to the 64-bit version of RadioBOSS 7.0.8.0, it's twice as long.​


No errors in any of the playlists during creation.

Are the new features (constraints and "fast" random option that I do not use to date) slowing down playlist creation?
There may not be any problem, but I'm reporting what I've noticed. This time difference between two computers seems a bit much to me.



TimeStretch: OK. Nothing to report in the current operation.
 
Does this version solve the issue with the scheduler failing to launch some playlist generation events that some have raised?
We were not able to reproduce this. From one playlist generator log the issue was faulty repeat protection rules that prevented creating the playlist in time.

RadioBOSS 7.1.1.4
Thank you for the detailed message!

FYI, almost all screens have warnings voluntarily during testing.
Can you please provide more information about it?

In the Ad Properties of an ad, you can add one or more tracks. I notice that the same track is always selected during playback: the first one.What's the point of adding a second or several other tracks after the first?The instructions mention "main track" and "alternative track." How do I use these alternative tracks? I'm asking out of curiosity.
The alternative ads are used when creating playlists - it will select a random track from the list.

You should adjust the type of mix points for the tracks that are selected for the START block and the END block because, currently, the "Start" and "End" points of a track are taken into account.
The overlay ads events are mixed according to the crossfade rules in RadioBOSS - as any other tracks. Ad playlists are not treated any differently so when needed, necessary file types and crossfade settings can be created.

The computer isn't the same. My installation of version 7.1.1.4 is 32-bit. Version 7.0.8.0 is 64-bit.
There are too much differences to compare directly. Depending on the preset (what features it uses), it may be slower or faster I guess. In most tests here it became faster. Previously, here on the forum, playlist creation time went down from almost 5 hours (!) to 15 minutes: https://www.djsoft.net/community/threads/radioboss-7-1-beta.12390/post-53522
You can see in the log where does playlist generator spends most of the time.

Are the new features (constraints and "fast" random option that I do not use to date) slowing down playlist creation?
Constraints, if not enabled, do not affect the speed. The Random (fast) option will make playlist creation much faster if you have categories with lots of tracks (I'd say 10K+ tracks).
 
Can you please provide more information about it?
I intentionally created several dozen ads blocks with all sorts of overruns:
  • Exceeding the number of ads in a block
  • Exceeding the duration of an ad block
  • Identical ads types.
This was to verify that the warnings were displayed in all cases when I clicked "test all blocks." And also to verify that no warnings were displayed when everything was correct.
Nothing to report. Everything works fine (y)

The alternative ads are used when creating playlists - it will select a random track from the list.

The overlay ads events are mixed according to the crossfade rules in RadioBOSS - as any other tracks. Ad playlists are not treated any differently so when needed, necessary file types and crossfade settings can be created.

There are too much differences to compare directly. Depending on the preset (what features it uses), it may be slower or faster I guess. In most tests here it became faster.

Constraints, if not enabled, do not affect the speed. The Random (fast) option will make playlist creation much faster if you have categories with lots of tracks (I'd say 10K+ tracks).
Thank you for all these details.


For my part, this version has been working for about 16 hours without any issues.

I haven't fully verified the functionality of the new "constraints" tab in Playlist Generator Pro. But it works for the two constraints I've set: Tags & Year.

I like new features like "Coldown" (AutoIntro), language search, new playlist columns, and more.
 
After these explanations, I also switched to the 32‑bit version, and it’s definitely faster - nothing drastic, but still a bit faster. We’re still testing for now, but for example, the “Test all blocks” task in Ads Scheduler now takes just 1 second.
Since the Release Candidate, RB has been on the air, and so far we haven’t found any bugs in the latest version.
 
Nothing to report. Everything works fine (y)
That's good to know, thank you!

Since the Release Candidate, RB has been on the air, and so far we haven’t found any bugs in the latest version.
The release candidate has just been promoted to a release :)

Why is the cooldown in seconds? I think minutes are easier to understand - 30 minutes is more obvious than 1800 seconds.
Yes. Seconds allow for a more fine control though.

After these explanations, I also switched to the 32‑bit version, and it’s definitely faster - nothing drastic, but still a bit faster.
Depends on the configuration, in some specially crafted test cases here 64-bit version was 8x times slower. So the default and recommended version is RadioBOSS 32-bit.
 
Since I started using the beta version of Radioboss — and this hasn’t changed since version 7.1.0.9 — an error regularly occurs when playlists are generated automatically, as shown in the log. However, the error only happens when the playlist is created via an event, not when I generate it manually. I’ve also recreated the preset in the Playlist Generator Pro, but the error still occurs.
Even though I get a "PlGen Error: 1 (errors while creating a playlist)" Now having examined the log files, in my case the event successfully generates the playlist (it creates a temp file in the AppData folder) but does not load it automatically for it to play as it should. And this applies only to presents I created/modified with the previous update. The log file shows that all the songs were loaded. For older presets there is no problem. The newer presets can't be generated as a scheduled event. This looks like a bug. Could you please kindly give it another look?
 
Back
Top