illustrate
Products            Buy            Support Forum            Registrations            Professional            About           
 

Dynamic Naming: [audio_quality]

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • square

    • Dec 2021
    • 13

    #1

    Dynamic Naming: [audio_quality]

    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.
    Last edited by square; June 11, 2025, 11:27 AM.
  • PeterP
    Super Moderator
    • Jul 2011
    • 1519

    #2
    Bug confirmed and being investigated, thanks for reporting.

    Comment

    • square

      • Dec 2021
      • 13

      #3
      Thank you for looking into it.

      Comment

      • PeterP
        Super Moderator
        • Jul 2011
        • 1519

        #4
        Various missing naming fields addressed in new beta build:

        Comment

        • square

          • Dec 2021
          • 13

          #5
          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.

          Comment

          Working...