by GibsonXXI » Fri Mar 21, 2014 3:50 pm
With the current version of MM (4.10.1692) there is a serious bug with the Auto Organize functionality built into MM.
When doing a "Move" files to new path, The process will complete successfully for the first attempt. For the second attempt (i.e: differing album / files from first attempt, or indeed same files, but different move settings), the file list will be blank. Nothing in source or destination. It is nessecary to exit out of MM, and restart it to get it to correctly show the files source and destination.
If "OK" is selected, when nothing appears in the source / destination parts of the dialog box instead of "Cancel", MM will assume the files have been moved and DELETE the source files regardless, even though NO movement of those source files has taken place.
I have witnessed the above (first paragraph) multiple times on my own PC, and my friend who i've been introducing MM to was unfortunate enough to have at least one album deleted by this bug.
There's also an general stability issue with large libraries, where MM is hanging when clicking on an album after the re-scan / monitoring stage at start-up, but this may be down to a corrupted/problematic Db so will hold off on this issue for now.
With the current version of MM (4.10.1692) there is a serious bug with the Auto Organize functionality built into MM.
When doing a "Move" files to new path, The process will complete successfully for the first attempt. For the second attempt (i.e: differing album / files from first attempt, or indeed same files, but different move settings), the file list will be blank. Nothing in source or destination. It is nessecary to exit out of MM, and restart it to get it to correctly show the files source and destination.
If "OK" is selected, when nothing appears in the source / destination parts of the dialog box instead of "Cancel", MM will assume the files have been moved and DELETE the source files regardless, even though NO movement of those source files has taken place.
I have witnessed the above (first paragraph) multiple times on my own PC, and my friend who i've been introducing MM to was unfortunate enough to have at least one album deleted by this bug.
There's also an general stability issue with large libraries, where MM is hanging when clicking on an album after the re-scan / monitoring stage at start-up, but this may be down to a corrupted/problematic Db so will hold off on this issue for now.