Thanks Graue. That makes sense. <br><br>Like I said - it's not causing a problem, I was just curious what it was doing.<br><br>-Brad<br><br><div><span class="gmail_quote">On 4/15/07, <b class="gmail_sendername">Graue
</b> <<a href="mailto:graue@oceanbase.org">graue@oceanbase.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">"Brad Leblanc" <
<a href="mailto:brad.leblanc@gmail.com">brad.leblanc@gmail.com</a>> wrote:<br><br>> While I'm playing around with it, I'd like to ask about something I've<br>> noticed.<br>><br>> Sometimes when I use metaflac to add tags, it performs it's operation
<br>> instantly in a split second. Other times the same command causes lot of HDD<br>> I/O's and I can see it create a "filename.flac.metadata_edit" temp file.<br>> For example - I just added tags to a 25MB file and it took 15 seconds to
<br>> process the command.<br><br>The tags are stored at the beginning of the file.<br>Since it's not possible to add new data into the<br>beginning or middle of a file, adding tags<br>normally means having to copy all the audio data
<br>that comes afterwards.<br><br>The reason this is sometimes fast is that FLAC<br>adds a padding block with unused space after the<br>tags. As long as your new tags fit in the padding<br>block, nothing has to be copied.
<br><br>If this is a frequent problem for you, look at the<br>documentation for FLAC's --padding option. Setting<br>a larger padding size might help.<br><br>Regards,<br>Graue<br></blockquote></div><br><br clear="all">
<br>-- <br>Brad