Forum

Welcome Guest 

Show/Hide Header

Welcome Guest, posting in this forum requires registration.





Pages: [1]
Author Topic: Artwork Write Time / Best Practices
micahmax
Newbie
Posts: 2
Permalink
Post Artwork Write Time / Best Practices
on: November 28, 2018, 18:53
Quote

(Apologies for a seemingly entry level question, but I feel like I may be missing something obvious)

In preparation for a full library move and restructure, I'm applying pre-saved 1000x1000 jpegs to the vast majority of my FLAC library. In doing so, I've felt a bit of a bottleneck when writing the artwork to each album's files. Manually loading albums and dragging/dropping album art to a single artist's discography of albums could sometimes take hours for a dozen or so albums.

What I'm looking for is the most time-efficient way to apply my artwork to the library, be it album by album, batch processing, etc. I don't mind the labor of going album by album, but if there is a faster/preferred way to write artwork to files, I'd love to learn.

I understand the answer could be 'it just takes awhile'...

Thanks!

2MR2
Administrator
Posts: 1113
Permalink
Post Re: Artwork Write Time / Best Practices
on: November 28, 2018, 19:50
Quote

The issue is not adding an image but rather that there is insufficient space to add the image without re-writing the entire file. Metadata in FLAC files is stored at the front of the file. While you might have some free space available after the tagging information, more than likely it is not sufficient to store a 1kx1k image. Where the files reside, can definitely make it worse. For example a NAS or external drive.

Here's the process:

- Yate loads the metadata when first reading the file. The large amount of data which comprises the audio is not read.
- You add an image
- You save the file.
- At this point, Yate realizes that it has insufficient file space to contain the image so it has to go out and read the audio data.
- It then has to rewrite the entire file. This is a worse case scenario.
- due to the fact that there may be a disparity between the data in the UI and how it gets stored it to the file, Yate always has to re-load the metadata after a Save. You might have manually create a lower case UDTI. When it gets written out to a FLAC file it has to be converted to upper case. If the application did not do a reload, you'd never know about inadvertent changes. There are lots of other cases such as this one.

Typically every step above is pretty quick except for the audio read and the full write.

So its access and volume. If you're leaving a small amount of free space such as the default of 2k, you're insulated against small changes. If you change a few small text based tags, the application fills the free space and does not have to read the audio or write the entire file.

Saving in the Batch Processor is slightly faster if you do not have a Save statement in your action but use the Batch Processor's Auto-Save option. When saving this way the last step of re-reading the metadata is not performed as there is no user interaction with the data. But, as I said that's typically not the 'time eater.

The answer is unfortunately "it just takes awhile". 🙁

micahmax
Newbie
Posts: 2
Permalink
Post Re: Artwork Write Time / Best Practices
on: November 28, 2018, 20:39
Quote

Thanks for the quick response! All of this matches up to what I've been noticing. And thank you for the amazing piece of software that makes this process not as bad as it could be. : )

Pages: [1]
Mingle Forum by cartpauj
Version: 1.0.34 ; Page loaded in: 0.053 seconds.