Print

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

[MarkCoutinho]

I just discovered that all the files that I've been renaming and after that finalized with 'Rename files from properties' (Rename Files from Properties) have been removed from the library. I don't know why. I never had this problem in version 11 or before.
Is it a option I have to (un)check?
I just tried to reproduce the problem but that didn't succeed... The file remained where it should be. But it happened in the last few weeks with about 25 files.
I got them back by importing them one by one, luckily.
Hope anyone can help.

[prod]

I use this function almost daily and I've not seen your problem. When you say "finalized" what exactly do you mean? Which version of MC12 are you using, and can you explain the steps you are taking to rename your files?

[MarkCoutinho]

Hi 'Prod'.
Well, I've been using this function also daily for over a year now - some 500 files have been renamed in this way and that's why I don't understand what went wrong the last time.
I use version 12.301.
With finalizing I mean: I've renamed the file (artist and/or name of the title) in the library and then I choose Library Tools - 'Rename files from properties'. That's all.
Any suggestions?

[AoXoMoXoA]

I always use the "Rename Files from Properties" function as my method of placing the files onto the appropriate media drive. I have rarely seen a problem such as you describe, and certainly none in recent months.

Were the files in the proper location on the drive and simply dropped by the library?
Or were they mis-located?

[marko]

please post the strings you are using in the rename from properties fields.

base path
directories
filename

The only time I've seen this happen with the Rename Files from Properties tool is when I tried using an entry in "My Network Places" as the 'Base Path'. MC did not follow the shortcut and the files vanished. They were test files, so I wasn't overly concerned about learning where they had gone. I did use windows search tool to try and locate them, but they were not found. To this day, I've no idea what happened to them!!!

-marko.

[jgreen]

mark--

You're moving files from point A to point B within MC, and some of them disappear.  Did you try looking in point A?  The MC library expects them to be in point B after the renaming process is complete, even if there was an error in renaming.  One possibility is that your Rename Files from Properties setup is creating an illegally long filename at point B.  I've seen this happen with classical music that has some absurdly long descriptions, FWIW. 

BTW, I'm going to start using "Rename Files from Properties" to describe my favorite file move fuction within MC.  I love acronyms (FWIW)!  Er, IMO.

[MarkCoutinho]

Hold on: I'm not moving files - just renaming them.
Well, here we go:
Base path: R: (which is a mapped drive)
Directory: music\Top 40\A
Filename: Abba - I do, I do, I do (title renamed from I do I do I do)
or
Filename: Amen Corner - If paradise is half as nice (title renamed from (If paradise is) Half as nice

So maybe it's in the mapped drive where the cause may be found. But, as I stated, up 'till now I've been using Rename Files from Properties hundreds of times with no problems at all. Maybe it's since version 301? But, then again: reproduction of this problem is not possible.

[AoXoMoXoA]

I try to take care not to write to mapped drives and only use them to play music from. You never know when a network glitch will occur causing a potential problem.
If I need to work on a network drive I go to the PC where the drive is installed, either physically or remotely using VNC   

[prod]

Hold on: I'm not moving files - just renaming them.

I'm not sure if there's much difference between move and rename, in terms of what MC does. I expect MC calls the same OS-level function, and that deals with it as it sees fit.

Is auto-import on, and how is your fix broken links option set?

[MarkCoutinho]

Got it!
Thanks Prod, it was the auto-import function that was on. I should have mentioned that I use the same library on 2 computers. I renamed files on pc 1, backed the library up and restored it on pc 2. Then I started MC before I renamed the files that were already renamed on pc 1 (are you guys still with me? ;-)
That's where it went wrong because of the auto-import function, because in the meantime MC was busy auto-importing in the background before I renamed all those files.
So... now I've switched off auto-import.

Pfew!