DB reset: I'd try modifying the SQL database. What I'm recommending seems
like it should work, but I haven't tried it, so make backups, wait for
someone else to vouch for it, etc.

Log in to mysql:
$ mysql -u rduser -p Rivendell
And enter your password. Then run:

update Rivendell.CUTS set LAST_PLAY_DATETIME = NULL;
exit

And unless I'm horribly misunderstanding something, that ought to remove
the last played data from every track in your system.


Thanks,

Max Goldstein
Operations Director
WMFO Medford


On Sun, Mar 9, 2014 at 10:24 AM, Pedro Picoto <[email protected]>wrote:

> Regarding the DB reset, yes just the logs. I want it to "forget" what was
> played before...
>
> Regarding the backtiming... If I need to create a commercial break to be
> played before TOH, I'm able to backtiming it, that is, end at
> the very top of the hour, ONLY If I know the exact break time and force it
> to play. Since breaks can vary in length, it is a time consuming task.
> Would be nice if RD could handle that automatically.
>
>
> On Sun, Mar 9, 2014 at 12:42 AM, Rick <[email protected]> wrote:
>
>>
>> Pedro Picoto schreef op 8-3-2014 21:40:
>>
>>   - When a cart or cut is deleted, is the audio file also purged? If
>> not, how to?
>>
>> you can check if the cut still exists on your HD in /var/snd after
>> deleting it, but it should be removed
>>
>>
>>   - I'm noticing that some days the scheduller picks the same artist to
>> play at the same (or near) hour of the previous day(s). Feature or
>> something to take some care in the feature?
>>
>>
>> you can set replay same artists or number to 32 hours , but there is no
>> nice clean way to program this exept using an external scheduler like
>> stationplaylistcreator
>>
>>    - How to reset the database regarding played logs, i.e. start from
>> scratch?
>>
>>
>> only logs?
>>
>>
>>  - Backtiming  dynamic breaks (TOH mainly): how or when?...
>>
>>    havn't got a clue what you mean by this, but probably this will be
>> managed by RDCatch, explain
>>
>>
>>
>> _______________________________________________
>> Rivendell-dev mailing 
>> [email protected]http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
>>
>>
>>
>> _______________________________________________
>> Rivendell-dev mailing list
>> [email protected]
>> http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
>>
>>
>
> _______________________________________________
> Rivendell-dev mailing list
> [email protected]
> http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
>
>
_______________________________________________
Rivendell-dev mailing list
[email protected]
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Reply via email to