RadioBOSS 7.1 [beta]

[TBN Radio]

It can be the mix point (Trigger mix at option) so you should process that also.

I am a bit confused about this option under the music library. What does it do? Is it the same as the crossfade option? I have already enabled Crossfade for the files. Should Mix Point be left at the default settings or adjusted? Does it affect the crossfade as well? Under Crossfade, I have enabled Mix Point, Trigger Mix at, Fade Out, and Start Fading Out on Mix for each file.

However, I was previously advised to turn off the processing of Trigger Mix Point and Gap Killer, as they do not calculate the exact track start and end time.

To make RadioBOSS calculate the Start Time precisely, the Trigger Mix At and the Gap Killer features can be turned off or tracks must be processed in advance.

D

Thread 'Precise Start Time and Duration calculation'

Jun 4, 2016

RadioBOSS calculates the estimated "Start Time" for each track in the playlist, but this time can be off by several seconds because of features that affect the track's playback time. This also affects the total playlist duration calculation.

Features that affect duration/start time:

1. Gap Killer removes silence at the beginning and end of the track. By default, this is evaluated when the track is started. Until then, RadioBOSS doesn't "know" how much silence the track contains, and therefore the exact track duration is unknown.

2. Trigger Mix At in the Crossfade settings...

• djsoft
• Replies: 0
• Forum: RadioBOSS Guides

• 

 

[xzsaimon16]

It is possible to add an option to set a color to a container?

 

[radiotelevision]

There is a problem in audio-video synchronization. When playing a video in the main player and an event is executed with the active options "Overlay Playback + Pause the playlist while event is playing", once the main video plays again, a desync is generated where the audio is ahead of the video. It has been tested with a computer with an nVidia 3060 video card and another with an integrated video card. The same thing happens in both.

What does it affect? In the case of a movie playing and an event, such as a commercial break, with "Pause the playlist", this problem will always be generated, very noticeable, since the desynchronization is more than 1 second
Best regards from Chile.

 

[nelson c]

Added scheduler command to turn Time Stretch on/off

Hi Dmitry, could you tell me what use command is?
I can't find it in the help?

 

[nelson c]

I am a bit confused about this option under the music library. What does it do? Is it the same as the crossfade option? I have already enabled Crossfade for the files. Should Mix Point be left at the default settings or adjusted? Does it affect the crossfade as well? Under Crossfade, I have enabled Mix Point, Trigger Mix at, Fade Out, and Start Fading Out on Mix for each file.

However, I was previously advised to turn off the processing of Trigger Mix Point and Gap Killer, as they do not calculate the exact track start and end time.

To make RadioBOSS calculate the Start Time precisely, the Trigger Mix At and the Gap Killer features can be turned off or tracks must be processed in advance.

D

Thread 'Precise Start Time and Duration calculation'

Jun 4, 2016

RadioBOSS calculates the estimated "Start Time" for each track in the playlist, but this time can be off by several seconds because of features that affect the track's playback time. This also affects the total playlist duration calculation.

Features that affect duration/start time:

1. Gap Killer removes silence at the beginning and end of the track. By default, this is evaluated when the track is started. Until then, RadioBOSS doesn't "know" how much silence the track contains, and therefore the exact track duration is unknown.

2. Trigger Mix At in the Crossfade settings...

• djsoft
• Replies: 0
• Forum: RadioBOSS Guides

• 

I don't have all my tracks processed yet, but in a test environment I'm seeing strange things.
With already processed songs, the track mixed 45 seconds before finishing (looking at the remaining time of the player), so the acceleration changed from +1.3 to +0.1
next track changed at -0.5
next track changed at +5.8
What is the reason for this?

 

[nelson c]

I don't have all my tracks processed yet, but in a test environment I'm seeing strange things.
With already processed songs, the track mixed 45 seconds before finishing (looking at the remaining time of the player), so the acceleration changed from +1.3 to +0.1
next track changed at -0.5
next track changed at +5.8
What is the reason for this?

View attachment 14774

Finally the playback apparently started on time, which is very good. But I wonder why the calculation has such extreme values at times. If the calculation were more exact I could adjust the time more evenly.

 

[djsoft]

Does it affect the crossfade as well? Under Crossfade, I have enabled Mix Point, Trigger Mix at, Fade Out, and Start Fading Out on Mix for each file.

If you have the Trigger Mix option enabled it means that Mix point will be detected automictically based on the level - in this case it can't calculate the correct Start Time. To make it happen, process the music tracks setting the Mix Point - it will do the same as Trigger Mix does, but the Mix point will be known in advance, allowing precise start time calculations.

 

[djsoft]

It is possible to add an option to set a color to a container?

You can create a file type with container= identifier and assign a color for it, this should work, starting with 7.1 this identifier is supported.

There is a problem in audio-video synchronization. When playing a video in the main player and an event is executed with the active options "Overlay Playback + Pause the playlist while event is playing", once the main video plays again, a desync is generated where the audio is ahead of the video. It has been tested with a computer with an nVidia 3060 video card and another with an integrated video card. The same thing happens in both.

Thank you, we'll check if there's a bug.

Hi Dmitry, could you tell me what use command is?
I can't find it in the help?

It's the set command:
set timestretch on
set timestretch off

With already processed songs, the track mixed 45 seconds before finishing (looking at the remaining time of the player), so the acceleration changed from +1.3 to +0.1

Why did it mix 45 seconds before the end, do you have a mix point set there?

next track changed at -0.5
next track changed at +5.8
What is the reason for this?

Each time a new track starts, it calculated the Time Stretch based on the updated Start Time values. Maybe the problem is some tracks were not processed and when a track started, because of gap killer/mix point it became "shorter" so new calculations resulted in different values.
There's also a potential bug in that it may not properly take into account mixing for file types (the ones that are ignored for Time Stretch).

 

[TBN Radio]

If you have the Trigger Mix option enabled it means that Mix point will be detected automictically based on the level - in this case it can't calculate the correct Start Time. To make it happen, process the music tracks setting the Mix Point - it will do the same as Trigger Mix does, but the Mix point will be known in advance, allowing precise start time calculations.

I will try disabling the Trigger Mix Point in the Crossfade settings for files, enabling the feature, and processing the tracks in the Music Library.

Another issue I encountered is that the last track of an hour ends a few seconds earlier than expected when the stretch feature is enabled.

For example, if a track is scheduled to start precisely at 00:00:00, but the last track of the previous hour ends too early, the first track of the next hour starts before the scheduled time, effectively shifting it into the previous hour. Ideally, if the first track of the next hour begin exactly at 00:00:00, then the scheduled time check announces the top of the hour correctly.

Let me first try the above mentioned Trigger Mix Point changes to see if the last track ends up precisely Top of the hour.

 

[xzsaimon16]

You can create a file type with container= identifier and assign a color for it, this should work, starting with 7.1 this identifier is supported.

It works fine.
One small observation is that the FIRST FILE inside the container does not change color when it is playing, the rest of the elements do. That is, all
the elements should change color according to the type of file inside the container. But the first element does not.

In the video you can see that for a fraction of time it turns blue and then returns to yellow.

 

[nelson c]

Why did it mix 45 seconds before the end, do you have a mix point set there?

No, nothing has custom fades. The song that started the mix at that time was a processed one. (You can see the dots in the previous tracktool screenshot)
It's a test environment, in which I don't have any file types either.

I'm still looking closely to see if I can find what triggers this.
I found a track in the library that didn't process, but that wasn't the case with this playlist.

 

[nelson c]

The song that started the mix at that time was a processed one

MixStart is also processed and from what I see now this can cause this

 

[TBN Radio]

I will try disabling the Trigger Mix Point in the Crossfade settings for files, enabling the feature, and processing the tracks in the Music Library.

Another issue I encountered is that the last track of an hour ends a few seconds earlier than expected when the stretch feature is enabled.

For example, if a track is scheduled to start precisely at 00:00:00, but the last track of the previous hour ends too early, the first track of the next hour starts before the scheduled time, effectively shifting it into the previous hour. Ideally, if the first track of the next hour begin exactly at 00:00:00, then the scheduled time check announces the top of the hour correctly.

Let me first try the above mentioned Trigger Mix Point changes to see if the last track ends up precisely Top of the hour.

At the beginning of the hour, everything seems well adjusted, but as time progresses, the adjustments become inconsistent, and most tracks no longer apply the expected settings.

I am testing with a stretch range of -10% to +22% over a 7-hour period. For example, a track is playing at -3%, and the next two tracks are also adjusted to -3%. However, once the next track starts playing, the adjustments disappear for the remaining tracks.

Although the adjustment recalculates at the start of each track, given the configured -10% to +22% range, it should still apply correctly even mid-hour, as there are plenty of minutes remaining to gradually reach the end of the hour. However, this is not happening as expected.

After a few songs, the system does recalculate and apply the adjustment again, but towards the end of the hour, the adjustments often do not apply in many scenarios.

Current Settings:​

• Gap Killer: Disabled
• Trigger Mix: Disabled
• Normalize, Mix Point, and Track Trim Silence: Processed

Could you confirm if this behavior is expected, or if any additional configuration is required to ensure consistent stretch adjustments throughout the entire hour?

Thank you!

 

[lughsan]

RadioBOSS 7.1.0.4 beta

Changes

• Advanced option: hide intro countdown

Where does the option appear? I can't find it.

• Playlist: added "Pause" column to allow inserting timed pause

Thanks for adding this option. As a suggestion, it would be nice to be able to set a specific time, which will activate just by pressing it.
This way we avoid having to configure the pause duration every time.

 

[TBN Radio]

At the beginning of the hour, everything seems well adjusted, but as time progresses, the adjustments become inconsistent, and most tracks no longer apply the expected settings.

I am testing with a stretch range of -10% to +22% over a 7-hour period. For example, a track is playing at -3%, and the next two tracks are also adjusted to -3%. However, once the next track starts playing, the adjustments disappear for the remaining tracks.

Although the adjustment recalculates at the start of each track, given the configured -10% to +22% range, it should still apply correctly even mid-hour, as there are plenty of minutes remaining to gradually reach the end of the hour. However, this is not happening as expected.

After a few songs, the system does recalculate and apply the adjustment again, but towards the end of the hour, the adjustments often do not apply in many scenarios.

Current Settings:​

• Gap Killer: Disabled
• Trigger Mix: Disabled
• Normalize, Mix Point, and Track Trim Silence: Processed

Could you confirm if this behavior is expected, or if any additional configuration is required to ensure consistent stretch adjustments throughout the entire hour?

Thank you!

After testing the stretch feature over extended hours and performing several restarts and adjustments, it appears to be functioning now. Initially, there were irregularities in its behavior, leading me to wonder if a training period was necessary for it to learn the schedule. I will monitor its performance to determine if these improvements are permanent or if issues recur intermittently. I will provide updates should any problems arise. Thank you.

 

[madein80]

We were unable to reproduce this bug here. If this still happens in RadioBOSS 7.1.0.4, please make a video again with Ctrl+F4 debug window visible (it now has more information for the debugging).

Hi,
The problem is still present on 7.1.0.4. I uninstalled and reinstalled Radioboss it doesn't change anything.
I don't know where to look anymore.
here is a new video with the debug window activated

- YouTube

Enjoy the videos and music that you love, upload original content and share it all with friends, family and the world on YouTube.

youtu.be

Thanks

 

[TBN Radio]

After testing the stretch feature over extended hours and performing several restarts and adjustments, it appears to be functioning now. Initially, there were irregularities in its behavior, leading me to wonder if a training period was necessary for it to learn the schedule. I will monitor its performance to determine if these improvements are permanent or if issues recur intermittently. I will provide updates should any problems arise. Thank you.

At the end of the hour, although it shows that the first song of the next hour is scheduled to start at 00:00:00, it doesn’t actually start at that time, making the stretch feature unreliable. A restart temporarily fixes the issue, but after a few hours, the problem returns, causing instability in scheduling.

 

[radiotelevision]

I've been testing the command to get weather information and found a possible problem. By default, this setting is set so that weather information cannot be updated within the next 12 hours. It might be better to limit it to only 3 hours, or even 1 hour. This would help the temperature and humidity mentions to be as accurate as possible.

Best Regards from Chile.

 

[patrick.de-bruyn]

I've been testing the command to get weather information and found a possible problem. By default, this setting is set so that weather information cannot be updated within the next 12 hours. It might be better to limit it to only 3 hours, or even 1 hour. This would help the temperature and humidity mentions to be as accurate as possible.

Best Regards from Chile.

It would be even better to get your own key
The key from RadioBOSS is used by many users and quickly reaches its limits
I got my own key for Accuweather, it's free and you can use it up to 5 times per hour for weather updates
You just have to register and create an api

AccuWeather APIs | Packages

Core Weather Minutecast Review Order Core Weather

developer.accuweather.com

I update the weather data every hour using an event

Greetings from Germany

 

[djsoft]

For example, if a track is scheduled to start precisely at 00:00:00, but the last track of the previous hour ends too early, the first track of the next hour starts before the scheduled time, effectively shifting it into the previous hour. Ideally, if the first track of the next hour begin exactly at 00:00:00, then the scheduled time check announces the top of the hour correctly.

This is what Time Stretch tries to achieve, but if you have Trigger Mix enabled, and the tracks are not processed, Time Stretch would not "know" the exact mix point, and calculate based on the general Mix Point settings from the crossfades. If the actual mix point is then placed earlier, this will result in the track also ending earlier than expected.

One small observation is that the FIRST FILE inside the container does not change color when it is playing, the rest of the elements do. That is, all
the elements should change color according to the type of file inside the container. But the first element does not.

In the video you can see that for a fraction of time it turns blue and then returns to yellow.

The video doesn't open, can you please provide another link?

MixStart is also processed and from what I see now this can cause this

Yes, Mix Start will modify the preceding track's Mix point, which can result in what you experience (45 seconds mix point).