Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[HiFiTubes]

I'm not a lot of tagging errors across all file types. Looks like everything is read-only now.

Recently, a friend reported that since the April 13th Windows security patch, her copy of 64-bit Windows 7 is marking all folders as “read only” and she couldn’t find an easy way to fix it. She’s not alone. But this isn’t a problem that’s unique to either 64-bit Windows 7 or this particular set of patches. Instead, it seems to be an endemic problem with Windows 7 and Windows Vista.

http://itexpertvoice.com/home/fixing-the-windows-7-read-only-folder-blues/

Hope this helps.

[Arindelle]

Hey thanks for posting this !

I'm not having trouble with my tagging, but I couldn't remove a few of my directories (one was 282 gb^^), and this did the trick
after running cmd

attrib -r -s drive:\<path>\<foldername>

.

Might want to change your subject include something like adding "read/write or permission issues 64-bit Windows" - so this can be searched easier ?

Anyways, this should help a bunch of users, thanks again

[nickeaston]

I get this error often:

Tagging Error
"MC encountered errors while tagging or moving files.  Check that the files exist, are not read-only, and are not in use by other programs."

"File read-only:....tune....mp3"

[HiFiTubes]

I still have this issue, and I really suspect MC19 is involved.

I have affected files on (3) local drives and also affecting a Synology DS411 NAS. Never had any issues like this with MC18.

Tonight, I will test with MC18.

Other issues that could be related are my reports of duplicate files not being repaired/removed after import, and empty filenames after import.

Of note, about 1.5 years ago I upgraded to the highest version of Synology DSM 4.0, and it completely broke MC accessing files for playback even though filenames were correct.

Now I wonder with MC19 if something has been updated, and I should be on DSM 5.0 or higher....

but if it's affecting local disk files then I don't know....

[JimH]

I think the most common reason for duplicates is that NAS files can be imported from a network path or a mapped drive.  In other words, your NAS might be seen as \\NASDrive\Music or as Z:\Music (both being the same source).

This is unfortunate, but it is user error, not an MC problem.

[HiFiTubes]

I agree, but that's not the issue here, and the strange variants of this problem affect files all from a mapped drive, I always avoid using the network connection.

This is directly after import, Remove Missing Files = yes



These two issues:

not being repaired/removed after import

empty filenames after import

I will verify if just mapped drive NAS files are affected.

[MrC]

Two additional tests might be useful:

  1) select the two duplicate files, and see if Filename in the Tag Action Window says [Varies], or shows the single file name.
  2) Add an expression column with the expression function FileKey() and see if the two files share a value or there are two values.

[HiFiTubes]

Thanks. All Filename fields are not Varies...

but, the FileKey() is unique for each file.

Is FileKey() based on some kind of characteristic found during import?

[MrC]

The FileKey is the unique key per-file in MC.  It is generated on import, and remains for the life of the file.  There should never be two identical FileKeys nor Filename values.  So your results would indicate there is some corruption in the library, or even a remote chance of some rare bug.

[HiFiTubes]

The FileKey is the unique key per-file in MC.  It is generated on import, and remains for the life of the file.  There should never be two identical FileKeys nor Filename values.  So your results would indicate there is some corruption in the library, or even a remote chance of some rare bug.

Ok thanks. After the empty Filename bug (linked up thread) I think Matt suggested to rebuild the library. Ever since then I leave auto-import off. All my video files residue on NAS, I think it is just video files.