you can set start and end dates and times by putting the data in the
filename as in
news-item2-YYYYMMDD-HHMMSS,YYYYMMDD-HHMMSS-pope.wav
then run rdimport in a shell script including a line like
startdate=$(cut -d- -f3
<<<"news-item2-YYYYMMDD-HHMMSS,YYYYMMDD-HHMMSS-pope.wav")
starttime=$(cut -d- -f4
<<<"news-item2-YYYYMMDD-HHMMSS,YYYYMMDD-HHMMSS-pope.wav")
enddate=$(cut -d- -f5
<<<"news-item2-YYYYMMDD-HHMMSS,YYYYMMDD-HHMMSS-pope.wav")
end time=$(cut -d- -f6
<<<"news-item2-YYYYMMDD-HHMMSS,YYYYMMDD-HHMMSS-pope.wav")
and using
--set-datetimes=$startdate$starttime$enddate$endtime
in an rdimport command line
bit of an effort to code but sets them as you want
start date and end date offset work similarly
mp3 tags go more or less where you might hope but don't put any faith in
them
cart chunk is an audacity request
ttr
regards
Robert
On 25/09/15 11:32, John Edstrom wrote:
According to the documents its rdimport can set cut start/end dates in
the arguments, but it also says:
... If the imported file does not reference a start date, create with
startdate/enddate offset ...
How does an input file "reference" start/end dates? The
metadata-pattern doesn't mention fields for this. Does rdimport read
ID3 tags or something?
JE
--
Robert Jeffares
Communication Consultants
The Wireless Station
Big Valley Radio
Radio Spice
_______________________________________________
Rivendell-dev mailing list
[email protected]
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
