Re: db error message: "Unable to write ID tags for..."
I am having this same error now - Trial Version with 2 days left. Planned on purchasing because really love the simplicity/flexibility of dBpoweramp.
[new HP laptop with WD8tb usb external drive, dedicated music server with no programs added except: dBpoweramp, HP tools, WD tools, McAfee LiveSafe]
We get this error when simply trying to manually edit tags (year & comment) for ALL songs in an album (we select check box at top of File Explorer which selects ALL of song files for album):
"Unable to write ID tags for:
[flac file location]
Check these files can be written to."
** We know that we have set full admin privileges in Win10 for this drive, and have been able to edit files until now. (trying to assess what might have changed on this platform to cause this issue)
Q: How can I check/change eset on Win10?
or
Q: Is there another discussion node for this issue that addresses this or similar issues?
We are thinking it might have to do with Windows ESET, or possibly McAfee LiveSafe... but just a hunch.
THANKS for any time and assistance anyone might offer,
RKK
(frustrated with MSoft - as usual)
I am having this same error now - Trial Version with 2 days left. Planned on purchasing because really love the simplicity/flexibility of dBpoweramp.
[new HP laptop with WD8tb usb external drive, dedicated music server with no programs added except: dBpoweramp, HP tools, WD tools, McAfee LiveSafe]
We get this error when simply trying to manually edit tags (year & comment) for ALL songs in an album (we select check box at top of File Explorer which selects ALL of song files for album):
"Unable to write ID tags for:
[flac file location]
Check these files can be written to."
** We know that we have set full admin privileges in Win10 for this drive, and have been able to edit files until now. (trying to assess what might have changed on this platform to cause this issue)
Q: How can I check/change eset on Win10?
or
Q: Is there another discussion node for this issue that addresses this or similar issues?
We are thinking it might have to do with Windows ESET, or possibly McAfee LiveSafe... but just a hunch.
THANKS for any time and assistance anyone might offer,
RKK
(frustrated with MSoft - as usual)
Comment