Search results

Probably there's a bug where tag editor decides to update tag where it should only update additional information. This will be addressed in the upcoming RadioBOSS 7.1.5 update.

It linearly depends on the number of music tracks you have and the number of rules. Processing is parallelized, where possible (e.g. priority rules, so the more cores you have the faster it'll be). Also, 32-bit version is about 30% faster that the 64-bit. If you use the latter, consider switching.

As it turned out, it indeed could become unresponsive (not freeze, as the task is performed in the background and eventually it'll finish), the next update will have this improved, with a proper progress bar window.

This is possible, but as practice had shown RadioBOSS Cloud approach is much more better in many ways. If you want desktop RadioBOSS you can rent a Windows VPS and install it there, this way you will have all control over it, and it doesn't require a lot of management.

There are playout reports that you can find in the Reports section. If you want a report of all uploaded music, there's no such report.

The time/day parting feature is planned for the future versions, but I think it will be implemented differently, maybe additional field(s) that determine when a track can be used. As proposed here, it violates some UI design principles that is in the Tag List editor you also decide when a track...

From what happens, stability (of the system itself or RadioBOSS) is not a problem the problem is that audio device stops (or connection to the audio device stops). From the log you posted, RadioBOSS did detect that the device has stopped and successfully restarted it, so I suppose playback...

For this, RadioBOSS Cloud exists. Providing access to a regular RadioBOSS software is a totally different topic, and this actually was our first try before creating RadioBOSS Cloud - it didn't really work out, for a number of reasons. Virtual PCs are generally not a problem, it depends on what...

OK, I added it to the list of the future improvements.

Yes, it could, but I'm not sure about how useful it would be for others.

RadioBOSS 7.1.5 is currently under development and this bug will be addressed there, the release will be in September.

This is the definition of the current Intro/Outro points in RadioBOSS, Intro is where the vocals start, and Outro is where it ends. This is how most tracks are already marked by the users. So the current Intro/Outro look like what you describe as Intro B/Outro B. At this point, I'm not sure if...

Do you refer to "Crossfade - Limit Mix to end before Intro" option? If so, enabling this by default doesn't seem a good solution, as in many cases it will lead voice tracks starting before playing track's Outro point. It can be moved out of the Advanced section though if many people want to...

There should be no slash in the server address field. Also, mount point is not specified.

Event if this check works, this does not solve the core issue (device/connection to the device stopping), I think you should check everything. Probably do not use RadioBOSS on a virtual machine.

Scheduled tracks are deleted by blocks - that is, when all tracks from a single event are played, they are deleted. Just in case, please also ensure that you use the most recent RadioBOSS version.

This sounds interesting, however I think we should wait and see what other users have to say about it. If there are two or more intro/outro points, what "intro countdown" will show, or should there be some sort of switch between A/B markers?

I'm not sure, this is probably overkill for such a minor feature :) Maybe a fixed option like "Start bed X seconds before End marker" will do.

Disabling it is needed to understand the reason why the playback stops. From what happens, it's very likely the sound card is causing it - it stops processing so the sound stream stops. In some (most) cases, RadioBOSS detects such cases, and re-inits the device, but here it seems a bit...

It's scheduled for one of the major updates, probably RadioBOSS 7.2.