djsoft said:This will be fixed soon.
djsoft said:Please post a screenshot of an event that does this, and also screenshot of player window - before and after an event is started. This is required to reproduce the problem here.
Also, to clarify when you say "Manual start" - does it mean that the event is started manually (the Run Now button), or that track in the playlist is started manually (using the play button)?
Update the bug was reproduced when the scheduled track is started manually from the playlist. It does not remove the track from the queue, therefore track plays second time. This will be fixed soon.
It's planned for RadioBOSS 5.6.1, in the second half of July I think.southernfm said:When is the fix for this expected to be released?
djsoft said:As a workaround, you can use the Next track button instead of Play to start the track - this will remove the queue mark from the started track.
Could be that security settings at your email provider changed. I suggest contact them about it, or read their user manual about how 3rd party apps can use their SMTP server - usually you'll need to enable 3rd party app access, or create separate login/password.nelson c said:Hello, what can be owed this error in the notifications? (previously it worked well)
This is because of low crossfade engine resolution, that allows crossfade times to drift +- 50 milliseconds (sometimes can be even more). The new audioengine will fix this, yes. But its development is a lot of work so I can't say when it's going to be finished.nelson c said:The new audio engine will improve the precision of sigue editor? It is much the difference between the previous listening and the mix that really is played. I guess for the disk access times.
The amount of error is not known, it can be different each time, even when the same tracks are played again.nelson c said:For example if it is known to take 50 ms to start the track compensate that time in the actual mix.
This is not a bug: in the report you don't have the "Title" column, but use the Filename column instead, and that will be empty for scheduled commands and many other log entries. Please see the image attached where (your report file is loaded there).nelson c said:Here's the attachment. Although it seems to be correct. In today's day is still happening in the log