title
Products            Buy            Support Forum            Professional            About            Codec Central
 

Bug: Audio Arrange not following Restricted Character rules on dMC-R17 Mac

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • brandonjp
    dBpoweramp Enthusiast
    • Mar 2003
    • 53

    Bug: Audio Arrange not following Restricted Character rules on dMC-R17 Mac

    Using dBpoweramp Music Converter R17 on Mac, when a tag contains a colon a file name comes out as expected when Converting a file, but when using "Arrange Audio" dMC doesn't follow it's own Restricted Character rules and puts a forward slash in place of a colon.

    Here are the resulting filenames, using the same dynamic naming and same restricted character rules for both "Convert to MP3" & "Arrange Audio"
    Click image for larger version

Name:	CleanShot 2020-05-23 at 14.51.34@2x.png
Views:	1
Size:	66.1 KB
ID:	297491

    Here are the rules (just using the defaults) found under dMC > Advanced Settings > Converter > Set Filename Restricted Characters:
    Click image for larger version

Name:	CleanShot 2020-05-23 at 14.56.39@2x.jpg
Views:	1
Size:	44.6 KB
ID:	297492
  • PeterP
    Super Moderator
    • Jul 2011
    • 1365

    #2
    Re: Bug: Audio Arrange not following Restricted Character rules on dMC-R17 Mac

    Thanks for reporting.

    Issue should be fixed in the latest beta-
    Current version: beta 15 https://www.dbpoweramp.com/beta/DMC-R171b15.dmg Changes since R17: Fixed launcher window not working correctly on Mac OS Yosemite. CD Ripper: Fixed de-emphasis not being correctly activated on CDs with pre-emphasis. CD Ripper: Added de-emphasis toggle. CD Ripper: More readable output codec list (re

    Comment

    • brandonjp
      dBpoweramp Enthusiast
      • Mar 2003
      • 53

      #3
      Re: Bug: Audio Arrange not following Restricted Character rules on dMC-R17 Mac

      Originally posted by PeterP
      Issue should be fixed in the latest beta- https://forum.dbpoweramp.com/showthr...-R17-1-for-Mac
      Fixed! Tested and it works for me. Thanks!

      Comment

      Working...

      ]]>