Le 27/06/2014 15:50, Thomas Churchill a écrit : > 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 Yes, and even if the final file is not usable by a classic player, that would not be an issue, as the file would only be intended to be used by RDImport. So one would imagine a file with a customized header with sufficient space to contain all the Rivendell metadata.
Hoggins! _______________________________________________ Rivendell-dev mailing list [email protected] http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
