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.
 
Back
Top