I just did a test with RDcatch and I think I will switch over to using it instead. however it didn't seem to like the wildcard * at the end of the filename, but it does pull the current days file by using %D so I can have one cut that will be overwritten each day, making the end date issue an non issue because there will only ever be the one cut to play.
This will also get rid of the 20 rdimports constantly running on the system. > Not sure but I thought you said you were getting start and end dates. If you > dont have any start date offsets set, > then I am not sure where any dates are coming from (the WAV file has INFO > chunks - maybe the creation date is in there?). I was getting start and end dates, but the end date was 2 days later and the programs are played twice a day and I only want the one program to play so I need the start and end dates to be for a 1 day period, not a three day period. Ultimately RDCatch is going to work better, lesson learned. Thanks to all who replied Nathaniel C. Steele Assistant Chief Engineer/Technical Director WTRM-FM / TheCrossFM On 2/4/2013 2:47 PM, Todd Baker wrote: > Dear Nathan, > > Yeah, as I looked at the ROG I realized that I may have confused that with > something else, my apoligies. > > Not sure but I thought you said you were getting start and end dates. If you > dont have any start date offsets set, > then I am not sure where any dates are coming from (the WAV file has INFO > chunks - maybe the creation date is in there?). > > I worked on this a long time ago so I have forgotten exactly how the dates > are parsed, but I think its in the WAV file INFO chunk. Something like that. > I think someone else (like Fred) can easily answer this more quickly cuz I am > fuzzy on that detail. Or look up the associated metadata INFO in WAV format > files. And check if your files have INFO in them. > > As for using the offsets, the entries can be negative numbers, but the end > date number cannot end up being a lesser date than the start date. > > So, if the incoming CUTS have no start dates on them, then set those two > fields to zero (or leave them at zero since thats the default), and that is > effectively today. If you want more days then add to end offset. The end > should always be >= the start offset. I think the logic works with negative > numbers, atleast they work for me - although I dont see much need for > creating things that would never be valid which would happen if you used -6 > for start date and -3 for end date... > > Remember: Both the offsets are always in relation to either TODAY or Start > Date from input file. So the numeric value > for Start Date offset will always be less than or equal to End date offset. > > I entered an createoffset of -6 and -3 for start and end respectively and it > created a file with Air Date time Enabled, > Start Date 01/29/2013 00:00:00 and End Date 02/02/2013 23:59:59. > > Hope this helps, and hopefully someone else remembers where these Start and > End dates come from via Dropbox files... > > Todd > > > ----- Original Message ----- > From: "nathan steele" <nathan.ste...@thecrossfm.com> > To: "User discussion about the Rivendell Radio Automation System" > <rivendell-...@caspian.paravelsystems.com> > Sent: Monday, February 4, 2013 1:38:46 PM > Subject: Re: [RDD] Dropbox question, was amb-ux question. > > > Is there a metadata pattern for dates? > It didnt look like it to me from reading the rivendell operation guide. > > I tried the offset end date -2 but it wont take it complaining that the end > offset is greater than the start offset , even though it would make theo > start and end the same day... > > Sent from my HTC smartphone on the Now Network from Sprint! > > ----- Reply message ----- > From: "Todd Baker" <bak...@rfa.org> > To: "User discussion about the Rivendell Radio Automation System" > <rivendell-dev@lists.rivendellaudio.org> > Subject: [RDD] Dropbox question, was amb-ux question. > Date: Mon, Feb 4, 2013 12:16 pm > > > Hi Nathan, et al... > > Sorry to chime in so late here but wanted to let you know how that > functionality works in relation to this. > > The Dropbox GUI has a couple of choices for creating start dates. First one > is called offset start date/end date and the other is called Create start > date/ end date offset. They should work like this: > > The first group (offset start/end choice) uses the incoming carts start > date date and you can enter an offset > to set starting and ending dates from using what input entry had coming > in. > > The second group creates start and end dates when NO dates are present > (starting from today). That functionality will only > set (create) entries with start and end dates when there are none > present in the input. > > > That being said, If you are using the Metadata patterns to figure out the > start Dates, then I guess you could > remove those patterns and click the check box to create with start dates and > end dates of your choosing. If you already have start and end dates then the > first group should do what you want... > > Hope this helps, > > Regards, > > Todd Baker > > ----- Original Message ----- > From: "Nathan Steele" <nathan.ste...@thecrossfm.com> > To: "jeffares robert" <jeffares.rob...@gmail.com>, "User discussion about the > Rivendell Radio Automation System" <rivendell-...@caspian.paravelsystems.com> > Sent: Friday, February 1, 2013 3:02:28 PM > Subject: Re: [RDD] Dropbox question, was amb-ux question. > > I have been using the gui to do my dropboxes. If I set one up via > command line, will it show in the GUI? I would totally forget about it > if I didn't have a place to check. plus how do you change a dropbox > setup by command line? >> It is possible to put files in the dropbox and have them carted with a >> start date and end date based on 'today' the day you put them in the >> dropbox. The offset start date end date in the Dropbox options allows >> this. > This might work for me but I have to figure out how amb-ux is working as > to when and how many files are dumped at once. Initially I had setup > amb-ux and it dumped 5 days worth of each program. Does anyone use > amb-ux to transfer files from an AMR-100? based on my initial post that > answer is NO, as I got NO replies....oh well...there also NO > documentation on it..... > > Thanks. > > > Nathaniel C. Steele > Assistant Chief Engineer/Technical Director > WTRM-FM / TheCrossFM > > On 2/1/2013 2:49 PM, Robert wrote: >> It is possible to put files in the dropbox and have them carted with a >> start date and end date based on 'today' the day you put them in the >> dropbox. The offset start date end date in the Dropbox options allows >> this. >> >> RD will read cart chunk data from a wav file, [start date end date] but >> as yet there are no linux audio editors that write cart chunk data. It's >> on the request list for Audacity but low priority because so few >> requests.[hint hint] >> >> There is a patch which allows start date start time end date end time to >> be put in the filename in a manner similar to that you describe. I have >> it and plan to test it on a non critical box here. >> >> Ideally this patch can be included in the rdimport options. Command line >> will be fine... it can make it to the GUI later! >> >> It's not that this has never been considered, it has been, but hasn't >> made it to the top of the list yet. >> >> It would be interesting to know how many users are manually setting >> start dates / times for cuts in carts that are time critical and who >> would find it useful to just save the file with the details written in >> the filename. >> >> Robert Jeffares >> Big Valley Radio >> The Wireless Station >> >> >> >> On Fri, 2013-02-01 at 14:24 -0500, Nathan Steele wrote: >>> OK, so I set this up with dropboxes, but the files come in with a start >>> and end date that allows for three days to play, I need it to only play >>> on one day and that day should be the date in the filename, but looking >>> in the ROG it doesn't seem like there is a metadata pattern for the >>> start/end date. I looked at a file in Adobe audition and can't see that >>> range in any of the cart chunk or other data. where are these dates >>> coming from and how do I fix them? >>> >>> My dropbox path looks like this: /var/amb-ux/HCJB_BTC5*.MP2 >>> >>> The files are named like this HCJB_BTC5_01-30-13_01-01 and upon creation >>> of the dropbox. there were 5 days worth of files in there. >>> >>> Having looked at the wiki it seems to suggest using rdcatch instead. how >>> do I use rdcatch to get a file from a local directory? really seems like >>> dropbox would be the more appropriate tool? Did I miss the medata >>> pattern for start end date? >>> >>> Nathaniel C. Steele >>> Assistant Chief Engineer/Technical Director >>> WTRM-FM / TheCrossFM >>> >>> On 1/29/2013 5:15 PM, Nathan Steele wrote: >>>> Hello all, >>>> >>>> So I have amb-ux configured and running and all of my ambos recievers >>>> files are showing up in /var/amb-ux. Can someone recommend to me the >>>> best way to go about getting them into the appropriate carts? RDCATCH or >>>> Dropbox? Previously I was using a dropbox, which had the files put into >>>> it from a windows systemk running the ambos ui. Ambos UI would rename >>>> the files and put them into a directory that was used by another >>>> automation system for our other station. then we used an ftp program to >>>> log into the rivendell server and put the ones we needed into the >>>> dropbox, which would import them and overwrite the previous days cut. >>>> Now we are adding more programs that will not be used by the other >>>> station and personally I would like to take the windows box in the >>>> middle out of the equation. The nice thing was that the ambos UI would >>>> handle sending the correct days program, now I am faced with the task of >>>> getting the correct program out of a folder with several days worth of >>>> them in it, I know it can be done, just have to get there. any >>>> suggestions the files are named like this: >>>> >>>> "HCJB_BTC5_01_29_13_more numbers_maybe some version number_not sure" >>>> >>>> Thanks! >>>> >>> _______________________________________________ >>> Rivendell-dev mailing list >>> Rivendell-dev@lists.rivendellaudio.org >>> http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev >> _______________________________________________ >> Rivendell-dev mailing list >> Rivendell-dev@lists.rivendellaudio.org >> http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev >> >> >> > _______________________________________________ > Rivendell-dev mailing list > Rivendell-dev@lists.rivendellaudio.org > http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev > _______________________________________________ > Rivendell-dev mailing list > Rivendell-dev@lists.rivendellaudio.org > http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev > > > _______________________________________________ > Rivendell-dev mailing list > Rivendell-dev@lists.rivendellaudio.org > http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev > _______________________________________________ > Rivendell-dev mailing list > Rivendell-dev@lists.rivendellaudio.org > http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev _______________________________________________ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
