Print

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

[PARHull]

I've just upgraded to MC20.
Now, when updating tags, it seems that the filename is being updated with a new version number, so forming files like

03. Herr, lehre doch mich (4)

The tag update then ultimately fails complaining that cannot find files ?

It looks like as if a Windows Copy is taking place over the original version, leaving the updated version, deleting the original ?

Is this a bug, or some mistake on my part with configuration of MC20 (worked fine previously) ?

Thanks
Phil.

[Arindelle]

I'm not sure (or maybe I'm misunderstanding you -- happens about 30% of the time ) ... it almost sounds like you are reimporting your library and maybe in your autoimport configuration you have made some special rules or autmated something??  What do you mean by updating tags? There isn't any need to

Did you remove version 19 before upgrading?  If you didn't this should be seamless, no changes on physical files, just the library ported over to version 20. Actually you can run version 19 and 20 at the same time.

If you removed 19, did you take the backup from 19 and restore it into 20. If you didn't do a restore, maybe you should back track and start over with the upgrade. If there was a physical move (different paths or different computer etc.) you could try to repoint the database to a new (or in your case old) location.

But frankly, as long as you have backups of everything, including version 19 library backup, it would probably be faster, just to reinstall 20. rather than figure out what is going on. It shouldn't import anything or be looking for media really.

Post back if I am on the wrong track here if no one else chimes in first. ok?

[PARHull]

Thanks for some ideas. Sorry, should have explained more, nothing quite as complex as you suggested.
I have just updated to MC20, and afterwards uninstalled MC19. All music playing etc. works fine.

I am attempting to carry out a little housekeeping on some new flac files, just manually updating a few of the tags, composer etc. To do so I am using the Tag command from within the Action Window.
When I have changed the composer tag, then MC shows that it is updating tags.

After this, if attempting to change another tag in the same file, or to locate the original file on disk, then MC complains with an error, of the form "Media Centre encountered errors whilst tagging or moving files, check that files are not read only or open by another program"

Looking at the folder of flac files, it is apparent that the filename has been updated with a (n) - where n is the most recent number version of the file. Repeated attempts to update tags will result in (n) increasing !

I don't know how MC works, but it is almost as if MC holds the original file open, then tries to write the new file to the same filename, Windows7 doesn't allow, but updates the file number version. MC writes the file then closes/deletes the original, leaving only the filename with an incremented version in (). I'm sure this is not what is happening, just my explanation of a possibility !

The files are held on a Synology NAS. MC on a dedicated media pc, Windows7, MC20.0.17

Thanks

Phil.

[PARHull]

Just to update this little story.

It would seem that I have a selection of flac files, downloaded from B&W Society of Sound subscription (the very most recent three LSO recordings) (http://www.bowers-wilkins.co.uk/Society_of_Sound/Society_of_Sound/Music/Subscribe.html).

In each case, for these files (only ?), the tags do not update after a manual update of any of the tag fields and I am left with the updated version number of the files, as described earlier (the library is updated). Ironically this occurs for both the 16bit and 24bit versions of the files (a total of over 32 different flac files), which I downloaded again just to check.

No problems occur using MP3tag to update the tags, and MC correctly imports the files with the MP3tag updated tags.

No problems occur with those other flac files in my library that I have checked - so a strange peculiar behaviour with MC in my system for these particular flac files.

As a final check I will try importing the problem files to a fresh install of MC on a new PC. Clearly if this works ok, then is a problem in my existing system somewhere. If the problem remains then either an MC20 problem, or a problem with the flac files themselves !

If anyone else reading this is a subscriber to B&W Society of Sound, please try manually updating tags for either the 24bit or 16bit versions of the most recently released LSO recording of Brahms - Symphonies Nos 3 & 4

Thanks

[PARHull]

The final instalment

After installing most recent MC20 on new W8.1 machine, using local disk - not NAS, and importing the troublesome files - all works ok ! Which is good for MC, if not for me. So, the funny behaviour is somehow related to my Win7/MC system ! Oh well.

Phil.

[glynor]

This is almost certainly a filesystem permissions issue:
http://wiki.jriver.com/index.php/Troubleshooting_Disks#Filesystem_Permissions_Errors