This isn’t very hard to do assuming rd audio doesn’t choke with an extra chunk installed, and I am assuming the data isn’t already there in the “levl” segment in a form I can’t decipher. Rivendell would have to be changed to take the appropriate information from the chunk and place it where it needed to be in the DB. It seems not to have any provision for that. I could probably do this in a few days as an external script however. Create a format for the chunk. Have an export that read the proper fields from the DB and put them in the chunk and saved the file. And another script that reversed that process. It could be asily accomplished with PHP/MysQL running through a web page called up through the local Apache server, or by running the php/mysql script through a bash shell. PHP I don’t think is generally installed with Rivendell although it was one of the first things I added to ours on installation. Looking at the DB it appears that the pertinent info isn’t all in one table, for one issue. Another would be things like making sure the import put things in the correct group and respected cart number for the group as well as not overwriting existing cartnumbers. TC From: drew Roberts [mailto:[email protected]] Sent: Friday, June 27, 2014 12:28 PM To: Thomas Churchill Subject: Re: [RDD] Rivendell exchange file format On Fri, Jun 27, 2014 at 9:50 AM, Thomas Churchill <[email protected]> wrote: Rivendell would have to save the metadata in a chunk in the audio file itself in the var/snd directory. Not really and I had started working on an external system capable of doing this in the past. You may find the beginnings of code to do this here somewhere:
https://github.com/zotz/drradioutils Basically, my idea was an external system along the lines of rivexport. One of the features would be taking a wav file from /var/snd and wiriting it to an export folder while adding the metadata from the database into a chunk. I got as far as writing metadata to the wav file that another program could see. Perhaps audacity could see it? I could not get rivindell to see the metadata when trying to import such files though. I may have sent a file along to Fred to see if he could make rivendell see the data on import. I don't recall, and if I did, I don't recall getting a response back saying it was working. If anyone is interested in moving this forward, let me know and we can perhaps work on it together. So, to recap: Rivendell would not need to be modified at all. And if this ability was included in rdexport, or if an external system did the work, the files in /var/snd would not need to have the metadata in them. The metadata could be added on export and stripped on import to the other rivendell system. all the best, drew Right now that info appears to be only included in the database. Then there'd need to be a special import, or an addition to the import function that would try to read that metadata out of the rd audio file if it existed into the database. There are is a 610 byte long "bext" chunk directly after the header which is mostly blank except for 18 bytes in the middle with ascii text representing the import date and time(ex: "2014-06-2202:28:31"). There is also a 720 byte end chunk labeled "levl" filled with some data, perhaps its there but only the import date is visible in ascii if so. A normal wave file can include multiple extra data chunks. If a player doesn't understand them, it is supposed to just them. I do not know, and haven't check to see if an extra chunk is added to an rd audio file causes a problem for the playback. But that's where this information would have to go, if its not in that "levl" end chunk. Good idea though. Usually the data IS encoded in the audio file itself. TC -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Hoggins! Sent: Friday, June 27, 2014 9:25 AM To: [email protected] Subject: [RDD] Rivendell exchange file format Hey guys, Don't you think it would be super fantastic to be able to export a CART under a specific Rivendell format ? It would include everything (or selectable) that the CART already contains (sched codes, group, cuts and their markers), along with the actual audio. We could then import it, one by one, or by complete series, on another Rivendell system. If the two systems do not share the same group naming, scheduler codes, etc., and to prevent ID collision, we could be able to select what to import exactly. Just an idea. Sharing CARTS between different systems would be easy, and one could even imagine having overnight replication between two systems without hassle. Hoggins! _______________________________________________ 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 -- http://freemusicpush.blogspot.com/
_______________________________________________ Rivendell-dev mailing list [email protected] http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
