Reply To: 1281 & compilation grouping

#5464
rpedde
Participant

@mbaker wrote:

What sort of black magic’s happened to make it run so fast?!? It canes the CPU a bit, but I can live with that for a 400sec full build on 13000 files when the files are on a network share.

Ha! Ya… fundamental misunderstanding on my part about how sqlite does transactions, I think. Lesson learned, though.

The “Various Artists” issue remains the same. To be more clear, I’m talking about the “Group Compilations” (concat_compilations) flag. I’ve got the flag set to 1 in the config file and but am not getting albums showing up under “Various Artists” as expected.

concat_compilations (under the [scanning] header, right?) changes the artist of any files marked as a compilation and changes it to “Various Artists”, and changes the title to “Real Artist – Title”.

So, say… track 4 of the “Pump Up the Volume” soundtrack is “Wave of Mutilation” by the Pixies. With concat_compdirs set to 1, it would show up on the soundbridge as the song title “The Pixies – Wave of Mutilation” by “Various Artists”.

Okay. Well and good, but the trick is marking that soundtrack as files in a compilation. If these are from iTunes, you can mark them as a compilation in iTunes and mt-daapd will recognize it. Or, if you have a tagger that will set compilation tags (they don’t seem to be very standard, but I’m honoring YTCP or TCMP tags in mp3 as compilation tags, as well as the “cpil” atom in aac files), then firefly will recognize those.

If you don’t have either of those, another way would be to do it by directory. I have all my non-iTunes organized files by artist, except soundtracks, which I have in a “Various” folder.

If I set a compdirs of “/Various/”, then anything with a fullpath with “/Various/” would get it. If you named your soundtrack and stuff consistently, you might be able to use a compdirs entry like “Soundtrack/”, or maybe ” OST”.

Once you’ve got those, you’ll have to do a full rescan, as those get doctored up in the database at the time they are initially inserted into the database.

I turned on D9 and had a look at the queries and they don’t seem to be trying to filter based on compilations at that point. Is the compilation processing done at build time so that the database entry “looks” different? I’ve just done a full rebuild for 1359 and that hasn’t made a difference.

Uh, yeah, see above.

I’ve checked the database and the information appears to be accurate (compilation=1 on the songs I expect it to be).

Should have read the whole post first, obviously. 🙂

The only thing I can think is that concat_compilations isn’t in the [scanning] section.

— Ron