I’m pretty sure the answer to this is “no” but I figured I’ll ask anyway…
Can you use album-level fields in a path format?
I have an album-level “rating” field that it would be nice to use to organize on the disk, but I don’t think I can do that. Paths can only use item-level fields, right?
Hello! That should actually work—templates (in
paths but not elsewhere) try the album first and fall back to item-level data if that’s empty. Here is where it happens in the code:
"""Add lookup for album-level fields.
Album-level fields take precedence if `for_path` is true.
def __init__(self, item, for_path=False):
super(FormattedItemMapping, self).__init__(item, for_path)
self.item = item
However, queries are a different story:
Hm. Well I have this on my config but it doesn’t work:
Maybe you can only use album fields in the actual path itself, and not in the query part?
Yes indeed, that’s exactly it. The PR above is a (very tricky!) attempt to solve that problem with queries.
I “solved” the problem by moving my album ratings into the item metadata. They’re duplicated across every track, but I set them using a script that can batch set them all at once, so it’s not a huge problem in the end.