Track played from rvt session and history...
Track played from rvt session and history...
Hi bernd, here's a zip with of a screen cap of today playlist and global history.
as you can see, a track from leo kalyan was played this morning at 09:13
As you can see the same track was playlisted a few hours later (it's not supposed to be this close) as you can see the first rotation this mornin is'nt logged (the playlist window says last played january 22nd).
Note that this morning playlist was a RVT session recorded at 6am, and the actual playlist is generated from a script till 12:00. why is this first rotation not "listed" in the playlist (I assume it's been played again for the same reason)?
as you can see, a track from leo kalyan was played this morning at 09:13
As you can see the same track was playlisted a few hours later (it's not supposed to be this close) as you can see the first rotation this mornin is'nt logged (the playlist window says last played january 22nd).
Note that this morning playlist was a RVT session recorded at 6am, and the actual playlist is generated from a script till 12:00. why is this first rotation not "listed" in the playlist (I assume it's been played again for the same reason)?
- Attachments
-
- Capture d’écran 2018-02-09 à 13.34.01.zip
- (514.03 KiB) Downloaded 294 times
Re: Track played from rvt session and history...
What are your exact history settings (size, settings etc.)?
And are both tracks actually the same physical track?
Looking at the screen, it looks, that one track is called "CENSORED up" and one is called " CENSORED up" - which might explain, why the statistics are not accurate, as they might relate to 2 different physical tracks - it still wouldn't explain why it is played to close to each other, but here we might find a different explanation. Maybe your history size is simply too small?
There is for sure a good explanation on why this happened, but it rather hard to find out on only the information given...but we can try of course!
And are both tracks actually the same physical track?
Looking at the screen, it looks, that one track is called "CENSORED up" and one is called " CENSORED up" - which might explain, why the statistics are not accurate, as they might relate to 2 different physical tracks - it still wouldn't explain why it is played to close to each other, but here we might find a different explanation. Maybe your history size is simply too small?
There is for sure a good explanation on why this happened, but it rather hard to find out on only the information given...but we can try of course!
Bernd - radio42
ProppFrexx ONAIR - The Playout and Broadcast Automation Solution
ProppFrexx ONAIR - The Playout and Broadcast Automation Solution
Re: Track played from rvt session and history...
As there are no news, I assume this was a plain history issue resp. related to having 2 tracks with 2 different meta data values.
Bernd - radio42
ProppFrexx ONAIR - The Playout and Broadcast Automation Solution
ProppFrexx ONAIR - The Playout and Broadcast Automation Solution
Re: Track played from rvt session and history...
sorry Wasn't able to check in the last days.. will try to make a complete capture of history stettings later today.