Rivendell would have to save the metadata in a chunk in the audio file
itself in the var/snd directory. 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

Reply via email to