RadioBOSS 5.4 [beta]

Status
Not open for further replies.
djsoft said:
pety said:
Very important bugs unfixed.
This version cannot be used (right now) in our radio  :(
That's really odd... a quick test did not confirm a problem, it works fine in both active and any secondary playlists. Please give more information: is it a main playlist, how do you add a track to a playlist? A video would be great. Perhaps it will be possible to fix it this year :)
Dmitry, I made a video. It happened three times.Take your time and watch it from the beginning to the end.
Somewhere between tracks it is a space which is uncounted...
Please, fix it this year :)
https://www.youtube.com/watch?v=bQZYwPCxa9Y&feature=youtu.be
 
nelson c said:
Dmitry, I have the same problem with the play count. APEv2 are activated.
Granaas6 said:
Append APEv2 tag is checked. It updates the time and date played but not the play count.
It appears that Playcount is not updated in the playlist "Playcount" column, but it's updated in the tag, so it's saved actually. Playlist column update will be fixed in the next update.
 
djsoft said:
pety said:
Dmitry, I made a video. It happened three times.Take your time and watch it from the beginning to the end.
Somewhere between tracks it is a space which is uncounted...
Please, fix it this year :)
https://www.youtube.com/watch?v=bQZYwPCxa9Y&feature=youtu.be
Thanks for the video. Looks like it happens only occasionally, should be fixed soon.
It happens occasionally but not aleatory. That mean that it will happen everytime in the same conditions (when drag and drop the file somwhere between tracks).
 
Dmitry,
There is an error with the mix time to file types. (I think it is ignored)
I'm listening to the jingle mixing overlaps with the next track.
 
I just saw that the actual mixing time is 1 second. (the red bar on the air panel is positioned one second before the end of the mixture)

But I is set at 0.5 seconds.

In previous betas it worked well.
 

Attachments

  • 1.png
    1.png
    12.8 KB · Views: 443
nelson c said:
I just saw that the actual mixing time is 1 second. (the red bar on the air panel is positioned one second before the end of the mixture)

But I is set at 0.5 seconds.

In previous betas it worked well.
Update:
This only occurs on tracks inserted by an event.
 
nelson c said:
Silence detector in the latest version does not load the auxiliary list.
It does, but the settings have to be like this:


"Load auxiliary playlist"


silence.jpg
 
nelson c said:
I just saw that the actual mixing time is 1 second. (the red bar on the air panel is positioned one second before the end of the mixture)

But I is set at 0.5 seconds.

In previous betas it worked well.
Thanks for reporting, if it's a bug, will be fixed shortly.

nelson c said:
Silence detector in the latest version does not load the auxiliary list.
Are you sure that the playlist is empty? It only loads aux playlist if the playlist is empty.

pety said:
nelson c said:
Silence detector in the latest version does not load the auxiliary list.
It does, but the settings have to be like this:
"Load auxiliary playlist"
With this settings, it will always load the aux playlist. With nelson_c setup, it will only load it if the playlist window is empty (otherwise it will simply go to the next track).
 
djsoft said:
nelson c said:
I just saw that the actual mixing time is 1 second. (the red bar on the air panel is positioned one second before the end of the mixture)

But I is set at 0.5 seconds.

In previous betas it worked well.
Thanks for reporting, if it's a bug, will be fixed shortly.

nelson c said:
Silence detector in the latest version does not load the auxiliary list.
Are you sure that the playlist is empty? It only loads aux playlist if the playlist is empty.

If it was completely empty (emptied because he turned the "Delete tracks when played")
According I can see in the log detector silence not active.
It's strange but in another pc test (which has the same configuration in silent detector) detects silence and writes it to the log

What I can see is that the list is then finished a publicity event. Perhaps this is the problem. (attached screenshot of the log)

 

Attachments

  • bug.png
    bug.png
    35.8 KB · Views: 457
I just realized that the list is terminated sooner by a problem because PLGen Pro.

It should generate a playlist 18 hours and see which has generated a list of 12 Hs.
(The list is generated on a networked PC and is issued by another PC)
 

Attachments

  • PC Air.png
    PC Air.png
    53.4 KB · Views: 460
  • PC PLGen Pro.png
    PC PLGen Pro.png
    75 KB · Views: 465
Dmitriy, I am tired... I give up. This version (5.4.0.7) is for me a downgrade and still beta.
It happened again in this morning. I installed the new version and first thing I did was to test it feeding a playlist. Uffff...  :'( 

Ever never happened in older versions. Can you make a revision of code to see where is the problem? It is clear that something new was implemented in 5.4 version. This anything  new makes serious problems.

again.jpg


Dmitriy, another one, later today on my laptop:

another_one.jpg


So, the bug wasn't fixed. Please, fix it. I want to enjoy myself with 5.4
 
nelson c said:
If it was completely empty (emptied because he turned the "Delete tracks when played")
According I can see in the log detector silence not active.
It's strange but in another pc test (which has the same configuration in silent detector) detects silence and writes it to the log

What I can see is that the list is then finished a publicity event. Perhaps this is the problem. (attached screenshot of the log)
How long is silence detector period?

nelson c said:
I just realized that the list is terminated sooner by a problem because PLGen Pro.

It should generate a playlist 18 hours and see which has generated a list of 12 Hs.
(The list is generated on a networked PC and is issued by another PC)
It's a separate issue - you should check your playlist generator preset (perhaps the resulting playlist is shorted because of an error - try generating the playlist manually).
Silence Detector should detect the silence anyway... I've added it to the list of bugs.

pety said:
Ever never happened in older versions. Can you make a revision of code to see where is the problem? It is clear that something new was implemented in 5.4 version. This anything  new makes serious problems.
This is a result of delayed track information reading (new feature of 5.4). This was done to reduce delays when adding tracks (especially large amounts). As it seems, it's not perfect yet, although our internal tests here did not reveal the problem. In the next version the problem will be fixed. The old code worked just fine, but it was slower...
 
Status
Not open for further replies.
Back
Top