global restrictions within the next 32 days value
global restrictions within the next 32 days value
Hi bernd,
the value is stuck to 32, I can change the Add/minus value, I can change the number of tracked checked, but when I try to chnage the number of days, It's back to 32 as soon I get back to the restrictions..
the value is stuck to 32, I can change the Add/minus value, I can change the number of tracked checked, but when I try to chnage the number of days, It's back to 32 as soon I get back to the restrictions..
Re: global restrictions within the next 32 days value
What exact version are you using?
However I'll take a look over the weekend what this might be...
However I'll take a look over the weekend what this might be...
Bernd - radio42
ProppFrexx ONAIR - The Playout and Broadcast Automation Solution
ProppFrexx ONAIR - The Playout and Broadcast Automation Solution
Re: global restrictions within the next 32 days value
thanks, have a nice day
Re: global restrictions within the next 32 days value
Yes, I see the issue, it will be fixed in the next version!
Bernd - radio42
ProppFrexx ONAIR - The Playout and Broadcast Automation Solution
ProppFrexx ONAIR - The Playout and Broadcast Automation Solution
Re: global restrictions within the next 32 days value
It is fixed in the latest v4.0.3.37-beta - so "Check for Beta-Versions..." to install.
Bernd - radio42
ProppFrexx ONAIR - The Playout and Broadcast Automation Solution
ProppFrexx ONAIR - The Playout and Broadcast Automation Solution
Re: global restrictions within the next 32 days value
thanks just did the update.
I should post this in a different topic, but I just found a possible explanation of some of the unwanted high rotations I have in my playlists.
When I check the "Age last played" column in the directory explorer, some tracks are Last played "01/01/0001" and most of those are the ones that seems to be heavy played (seems logical, since I used the least recently played condition most of the time).
Any idea of what's wrong?
Thanks,
T.
I should post this in a different topic, but I just found a possible explanation of some of the unwanted high rotations I have in my playlists.
When I check the "Age last played" column in the directory explorer, some tracks are Last played "01/01/0001" and most of those are the ones that seems to be heavy played (seems logical, since I used the least recently played condition most of the time).
Any idea of what's wrong?
Thanks,
T.
Re: global restrictions within the next 32 days value
yes media library server, (update when value) is "Always" and I sent you demo file and screen cap in your mailbox.
Thanks,
Thomas.
Thanks,
Thomas.
Re: global restrictions within the next 32 days value
you're right, when you take manyually a track it's functionnal in the playlist window, but not when the playlist is generated from a script (see screen cap attached)
and the funny thing that it's not right for all tracks... There must be somthing wrong because some file are heavy played without any particular reason. I mean if a track is in the same folder than another one added the same day; using the same cript to genrate the playlist why some are more played thant others... (without any particular restrictions)Re: global restrictions within the next 32 days value
is there a way to get a stat fo single file with the number of plays/day?
to get a concrete vision of the rotations?
to get a concrete vision of the rotations?