-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Metadata wirte to file tag fails sometimes in Win 10 #10620
Comments
Commented by: daschuer This is IMHO an important bug because if the metadata export does not always work, you cannot rely on it and the whole feature is kind of moot. I am not sure what is the best solution, and if we are ever able to fix it entirely because on windows we don't know when a virus scanner kicks in or such. For now I think we must not fail silently, leaving the inconsistent state. We may revert the edit and issue a pop up or such. Or make the dirty flag persistent to delay the metadata write across Mixxx restarts. |
Commented by: daschuer It seems to be a common issue that renaming a file after writing it fails because of indexer of virus scanner access. I think this https://stackoverflow.com/questions/11021639/overwriting-files-in-windows-by-renaming-randomly-fails post matches our issue. I am not sure if the ReplaceFileA Api function is able to work around it: Maybe it fixes the issue of multiple file handlers when accessing the Windows API via QFile. This will be at least a workaround for the birth time issue in https://bugs.launchpad.net/mixxx/+bug/1955314 |
Issue closed with status Fix Released. |
Reported by: daschuer
Date: 2021-12-19T11:23:30Z
Status: Fix Released
Importance: High
Launchpad Issue: lp1955331
The metadata export to file tag "sometimes" fails on WIN 10.
This was test on a virtual box Win 10 image.
There seems to be a file locking issue on windows that prevents to write the metadata at all testing wit plain 2.3.1:
My first Idea was that this this is because of a looking up the file properties in windows explorer? But this also happens when I do not touch the file at all with other applications than Mixxx. It also happens after a fresh restart of Windows.
It is a Windows 10 Runnning in a virtual Box.
Interestingly the renaming works after I have loaded the track into a deck and edit the metadata while paying.
The text was updated successfully, but these errors were encountered: