On Nov 7, 2018, at 10:03, Rob Landry <41001...@interpring.com> wrote:
> A client of mine used to use AudioVault. I spent lots of hours examining AV
> .wav files to see how the metadata was stored, and was surprised to discover
> that each file stored its metadata twice: in an AV10 chunk, and
On Tue, 6 Nov 2018, Fred Gleason wrote:
Thus, in Rivendell, we make a strong separation: the audio store holds audio
and the database holds metadata. Audio in the audio store is *immutable*;
once it’s written, it can never be changed short of being *deleted*.
Information in the database OTOH
Well, the other side of the coin is that if you have two copies of the
metadata, one in a MySQL database and the other in the file headers, then
you need some mechanism to keep them synchronized. Otherwise you become
the proverbial man with two watches who can never be sure what time it is.
On Nov 6, 2018, at 15:42, Fred Gleason wrote:
> …
> They had an auxiliary program called the ‘SoundHound’ (derisively referred to
> as the ‘SoundPig’ by one of my co-workers) that would continually scan the
> set of audio files on the system, building and updating a searchable database
> of
On Nov 6, 2018, at 14:06, Richard Elen wrote:
> 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.
>
There are several public standards for such, as well as a whole slew of _ad
hoc_ private ones, invented by vendors
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
On Nov 6, 2018, at 11:50, Rob Landry <41001...@interpring.com> 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.
Yup. Better have a good backup plan in place!
> If each audio file had headers carrying
Of course,
if you have the storage space and the horsepower, you could always export
all the audio every so often... This puts a lot of the metadata into the
files exported. Does it put it all? You can export to flac as well...
all the best,
drew
On Tue, Nov 6, 2018 at 11:50 AM Rob Landry
On Mon, 5 Nov 2018, Fred Gleason wrote:
They don’t. 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.
Of course, one consequence of this approach is that if you
On Nov 5, 2018, at 17:44, John Edstrom wrote:
> Interesting. According to the doc the BWF V2 standard accomodates EBU
> R128 loudness metadata, which someone was asking about the other day.
> Am I correct in interpreting that to mean than its OK to include
> loudness metadata in the audio
Hi, Robert...
It's heading that way. I indeed picked up a used machine for the current
experiments and it should be fine for the application. Thankfully
storage is cheap too: I have a 2TB drive on its way. I'll let rdimport
ingest from the existing NTFS copy of the library and save its
Hi, Fred...
Many thanks for these helpful comments, much appreciated.
--Richard E
On 05-Nov-18 21:39, Fred Gleason wrote:
...the audio store contains *only* audio; all other metadata goes in
the SQL database.
...The European Broadcasting Union has codified the standard audio
storage
On Mon, 2018-11-05 at 16:39 -0500, Fred Gleason wrote:
> On Nov 5, 2018, at 16:17, Richard Elen wrote:
> ...
>
> It's a matter of standards-compliance. The European Broadcasting
> Union has codified the standard audio storage format for use in
> professional broadcast storage and play-out
Hi Richard,
I would heartily recommend you build a Rivendell system on a dedicated
computer.
You can source 2nd hand 64 bit machines relatively inexpensively and
they work quite well.
You may need to install a bigger drive for /var/snd depending on the
music library size, but you can run
On Nov 5, 2018, at 16:17, Richard Elen wrote:
> While the Windows system could no doubt play the WAV files produced by
> Rivendell, they may not contain any metadata, so it wouldn't know what they
> were.
They don’t. This was one of the fundamental design principles laid down at the
very
Observations based on your comments - for which thank you again!
On 05-Nov-18 20:58, drew Roberts wrote:
What does the windows system do with the audio that it cannot work
with the Riv files?
The Windows playout system reads the metadata from the audio files and
stores it in a database that
Richard,
glad to know the info was useful. A few clarifications...
On Mon, Nov 5, 2018 at 3:01 PM Richard Elen wrote:
> Hi, Drew...
>
> This is exceptionally useful information, and thank you.
>
> OK, so the current setup won't work. Not only that, my entire
> installation won't work - if the
Hi, Drew...
This is exceptionally useful information, and thank you.
OK, so the current setup won't work. Not only that, my entire
installation won't work - if the library needs to be stored in /var/snd/
then it DOES require its own partition - indeed, its own drive.
In addition, if I want
Richard,
On Mon, Nov 5, 2018 at 11:20 AM Richard G Elen wrote:
> Hi...
>
> I am just starting with Rivendell, so please pardon my total lack of
> knowledge at this point which may result in my asking meaningless or
> impossible questions.
>
We all start somewhere. Welcome.
> I had set up a
19 matches
Mail list logo
