title
Products            Buy            Support Forum            Professional            About            Codec Central
 

issues with latest release - editing tags creates error message

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

    • Jan 2024
    • 3

    issues with latest release - editing tags creates error message

    I just updated to the latest version, but now when I try to edit tags, I get error messages. Is there a fix for this?? If not, how do I go back to a previously release that worked for me??

    THANK YOU!!

    Ricker
  • Spoon
    Administrator
    • Apr 2002
    • 44579

    #2
    Re: issues with latest release - editing tags creates error message

    What file type are you tagging? what error message is shown?

    Which program are you using?
    Spoon
    www.dbpoweramp.com

    Comment

    • Ricker

      • Jan 2024
      • 3

      #3
      Re: issues with latest release - editing tags creates error message

      I am tagging FLAC files on a MacBook Pro using Sonoma 14.3. I just paid for the upgrade ($24) to dbpoweramp and it STILL doesn't work....still get the same error messages. Click image for larger version

Name:	Screenshot 2024-01-27 at 1.49.43 PM.jpg
Views:	1
Size:	100.0 KB
ID:	294732Click image for larger version

Name:	Screenshot 2024-01-27 at 1.49.43 PM.jpg
Views:	1
Size:	100.0 KB
ID:	294732

      Comment

      • Ricker

        • Jan 2024
        • 3

        #4
        Re: issues with latest release - editing tags creates error message

        I have been using dbpoweramp for a number of years now and have never had this issue previously. I even downloaded an older version to see if it would work and it DID work for me, but this latest version keeps giving me the error message I sent previously. Please help me get this straightened out as soon as possible. THANK YOU!!

        Comment

        • PeterP
          Super Moderator
          • Jul 2011
          • 1471

          #5
          Re: issues with latest release - editing tags creates error message

          Thanks for reporting.

          Fixed in new beta version-

          Comment

          Working...

          ]]>