Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rdimport set enddate #618

Open
RudiOnTheAir opened this issue Sep 18, 2020 · 2 comments
Open

rdimport set enddate #618

RudiOnTheAir opened this issue Sep 18, 2020 · 2 comments

Comments

@RudiOnTheAir
Copy link

Hi,

i need an idea to solve a maybe simple problem.

In my setup (Rivendell 2.x (the last 2.x release) i use an rdimport shell script to import a
audiofile called 0715.wav (3 in an hour, 12h a day...the last is 1745.wav) in a cut to be played 5 min later.
That is running very nice. But if the presenter forgets to upload the file to our FTP i should not play on 7:15
the next day!

Is there a way to set the start and end date to the day the file was imported, so the cart/cut gets red
and skipped in the nextdays log.?
It is very important the the file name is only 0715.wav and the presenter must not put the date
and time in the filename...!

Thanks in advance...

@ermina
Copy link

ermina commented Oct 4, 2020

This question would be better asked on the rivendell users mailing list (http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev), but here is an answer anyway.
If i understood the question properly, you just need to "enable" the Air Date/Time property of each cut in rdlibrary.
By default, rdimport will change the start and end date/time to be valid only for the day on which the import is made.
You can use rdimport with the --create-enddate-offset=n option where n will be a number of days of validity after the day of import (useful for weekly shows which are aired multiple times a week).

@ElvishArtisan
Copy link
Owner

++

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants