IIRC, you can store a full complement of metadata in a WAV file and
there is a standard for it, it's just not commonly done. I must admit
that the one thing that has concerned me slightly is the fact that the
ingested files are completely unidentifiable - the idea of writing out
and maintaining the metadata in the ingested files in case of a need for
database reconstruction sounds like a neat idea on the face of it.
On Mon, 5 Nov 2018, Fred Gleason wrote:
...This was one of the fundamental design principles laid down at
the very inception of the project: the audio store contains *only* audio;
all other metadata goes in the SQL database.
What was the rationale behind this decision, incidentally? Given the
amount of thought that has gone into the project as a whole, I imagine
there is a very good reason for it.
-_R
On 06-Nov-18 16:50, Rob Landry wrote:
Of course, one consequence of this approach is that if you lose the
MySQL database, the audio files will be more or less useless.
If each audio file had headers carrying copies of the metadata, it
would be possible to reconstruct the database fromt hem in the event
of a disaster.
_______________________________________________
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
