{item_id} in folder name?

[dstarr5d]

I'd love it if we could add the qobuz item_id into the folder where albums are downloaded. Some artists on Qobuz have both explicit-lyric and censored-lyric versions of their music, and unless this is described in the album title, it will only download one version, then say the files already exist for the second version because by default, they would end up with the same file names. Being able to add {item_id} into the folder names would allow one to download both versions.

Some similar requests: I would love to be able to have {albumartist} in both the folder and file name, as well as {year} in the file name. These currently can't be done.

Thanks

[darkf3n1x]

This is in #294 as well and I think it would be better to just have the {ExplicitFlag} broke out so it can be used at the folder and track level.

[bgonz808]

Sorry if this comment on a similar issue is not exactly on topic, but I feel it's a symptom of a larger decision that would need to be made on uniqueness (?). Also, sorry if this was already considered and perhaps made difficult by how Qobuz itself handles uniqueness...I've seen artists with the same name all combined into one.

Related to @dstarr5d 's point, my issue below would be solved be including a {release_type} tag for uniqueness. However, I think there is a cleaner way, and maybe under the hood, qobuz-dl needs to care about the {item_id} from Qobuz service as a way of telling if a track, or release (album, ep, single, comp., etc) has already been downloaded.

Issue:
Let's say an Artist has a Single and an Album of the same name

Result:
Tracks for both albums will download successfully (i.e. qobuz-dl will not skip a release for being seen already) but with the tracks from all releases of same artist and release name in the same folder (under default naming)

Not sure the best course for a solution, but keeping qobuz-dl as a silent CLI might encourage appending something to make a folder or filename unique, which would be solved by the {item_id} approach, or specifically {track_id} and/or {release_id}.