Dynamic Naming: [audio_quality]

[square]

I'm trying to automatically sort my music files into separate subdirectories for lossy and lossless compression. I tried to make use of the [audio_quality] property that I can insert from the Edit Dynamic Naming dialog, but the property doesn't seem to do anything. Whatever the encoder, the Example always shows "Medium (Lossy)". When converting, the property seems to get ignoried completely. For example, when I use "[audio_quality] [track]" as filename, the resulting files are only named 01.flac, 02.flac etc.

Any ideas? I'm using dBpoweramp for Mac.

[PeterP]

Bug confirmed and being investigated, thanks for reporting.

[square]

Thank you for looking into it.

[PeterP]

Various missing naming fields addressed in new beta build:

https://www.dbpoweramp.com/beta/DMC-2025-06-12.dmg

[square]

Hi PeterP, thanks for the link! I can confirm that the problem with [audio_quality] seems to be gone in the new beta build, but not entirely. What does work now is that [audio_quality] can be used as a path or filename component. For example, with [audio_quality] [track], the resulting file now correctly gets named as e.g. Perfect (Lossless) 02.flac. But there are still some issues:

1. When editing dynamic naming, the Example still shows "Medium (Lossy)" in all cases, even with "Current Metadata" checked.
2. For the value of [audio_quality], dBpoweramp seems to use the audio quality of the source format, not the destination format. This is only partially suitable for my workflow. When converting from, say, flac to mp3, I would of course not want the resulting MP3 files to be sorted into a folder named "Perfect (Lossless)".
3. In some cases, there are typos in the value of [audio_quality], as in "Very High (Lossy)" – with a double space before the parenthesis.

[PeterP]

More fixes, made naming preview more consistent with what is actually used-

https://www.dbpoweramp.com/beta/DMC-2025-06-17.dmg

Typos and [audio_quality] of destination format are still being looked into.

[square]

PeterP Thank you for investigating this so thoroughly. Naming preview now seems to work correctly when "Current Metadata" is checked. I didn't try with multiple different quality levels, but during my quick test with lossless source files, everything went as expected

What I mean by typos is that e.g. if the value for [audio_quality] is "Very High (Lossy)" there's a double space before the parenthesis. I don't know if there are other values where this or something similar happens as well, but I've composed a screenshot and inserted formatting marks and an enlarged version of the Example text field so you can see what I mean.