RadioBOSS 7.2 [beta]

[sharleedb]

Hello. Suggestions: Remove the reference to DSP plugins if they are no longer used and correct the repetition of songs in shuffle mode. Thank you very much.

 

[djsoft]

Every time I have the mix start point set on items like jingles that start with FX sounds or songs that have a fade in/reverse transition... The mix points are not respected at all. This always troubled me... The music doesn't fade out and the mix start actually doesn't do what I think it should do. I set it the way I used to set the Mix In point in the likes of Zetta.

Mix Start affect the Mix point position of the next track. This is described here: https://manual.djsoft.net/radioboss/en/track_tool.htm

That's enough corrections for me to start using this version in the program...we'll figure out the rest as we go

Yes, but this is still an early beta, so there still may be lots of other bugs.

 

[djsoft]

At the moment, since start earlier is defined globally in Settings > Scheduler, it also affects manual actions. For example, if it’s set to 3 minutes and I click Run now on an event, the event does not start immediately but waits those 3 minutes.

The Run Now should not be affected by this - this will be corrected.

In practice, most playlists are generated almost instantly (especially hourly ones)

It also depends on how many tracks are in the categories, for 20K tracks loading a category can take about 10 seconds.

 

[djsoft]

I love these new features, but I am starting to see some serious regression in terms of accessibility.

I wouldn't call it a regression because only new features are affected while what existed is still accessible. Accessibility issues you mentioned will be fixed.

 

[djsoft]

Because of that, it might be better if the start earlier offset was configurable per scheduler event

I'm not sure about this, you can set some average value in the settings to cover most of the cases. It's only needed in case when you create very different playlists e.g. on some days it's 24-hour single playlist and on others 1-hour playlists - but this still may be handled, e.g. have shorter wait time and for long playlists have two events (create and start).

When a playlist is generated from the Scheduler, it might not be necessary to manually enter the start time and day in the Wizard. The Scheduler already knows the exact execution time, so dayparting filters could be applied automatically based on the current day and hour at generation time.

The event has a configured playlist start time and it's expected that the event will start as configured, not silently overriding the set start time. Also the playlist start time (when you use the Wizard) is written in the event's command. The Run Now simply executes the event command, not doing any modifications.