Why doesn't batch rename result in the names I expect?
iView MediaPro renames each file, one at a time, in turn. If a filename is already in use then iView MediaPro will try the next filename in the sequence until it finds a name which is not taken.
Quite often people have a numeric filename system and are using the batch rename on files in a folder where many of those files will already use some of the filenames they want to end up with.
An example is if I had files '00001.jpg' to '00100.jpg' in a folder. Then I add 'DSC0567.jpg' to the folder and batch rename them with a 5 figure incrementing number from 0. If 'DSC0567.jpg' is first in the list to be renamed iView MediaPro will try 00001.jpg, but that is used, it will continue to try until it finds a free increment. In this case 00101.jpg. The other filenames in the batch will continue up from there.
Hopefully if you understand how it works you can take it into account.
Firstly, always sort media items by filename before batch renaming, if a name clash could occur.
If all the files in the folder are in the catalog then you can use a temporary rename first. Use the batch rename once with the string 'temp' added. Then use the batch rename again with the filenames you want to end up with. This way no name clashes will occur.
What can I do if a catalog won't open? (error -54)
iView MediaPro uses a lock to prevent multiple users accessing editing a catalog simultaneously.
This lock is an invisible file with a similar name to the catalog. For instance the catalog 'catalog-1.ivc' would have a lock file called 'catalog-1.ivc_0'. The number at the end of the lock increases. iView MediaPro allows up to 10 computers to open a single catalog at any one time. In this case 10 lock files would exist, for example 'catalog-1.ivc_0', 'catalog-1.ivc_1','catalog-1.ivc_2', etc, up to and including 'catalog-1.ivc_9'. The eleventh connection is not allowed and will receive an error message including the code '-54'.
In some circumstances the lock file may not be removed when the catalog is closed, in this case the lock files may build up over time and a user may receive the above message even if they are the only user attempting to access that catalog.
If that is the case then renaming the catalog will break the link with the lock files and allow the user to access the catalog. If the user is sure no-one is accessing the catalog the lock files can be deleted, you will need to know how to see invisible files before they can be removed. This Answer will not cover viewing and deleting invisible files as it is something that should only be attempted by experienced users.
Inexperienced users will find it easier to move the catalog to a new folder or rename the catalog.
If you are experiencing this problem please make sure that when working on a catalog the catalog is Closed or iView MediaPro is Quit at the end of a session. Please also make sure you are using the latest available version of iView MediaPro.
What can I do if a catalog won't open? (not -54 error)
Any file (including an iView catalog) could become corrupt. iView always recommends backing up catalogs, and media files contained in them, as part of you regular backup stratergy. A typical example of a corruption might be an -39 error when attempting to open the catalog.
iView MediaPro does contain a method to attempt to recover a catalog that does not open due to corruption. Please note that not all corruptions can be repaired. Launch iView MediaPro, choose open from the file menu. Navigate to the catalog and hold down the alt key while pressing the 'open' button.
This method is available on Windows and Macintosh versions of iView MediaPro.
Why does MediaPro crash on import? (Windows)
There was a problem with Quicktime version 7.0.4 that would cause Windows MediaPro version 3 or 3.0.1 to crash on import. This is not a problem version 3.0.2 and later of MediaPro. Quicktime 7.0.4 is no longer the current version of Quicktime.
Please make sure you are using the current version of MediaPro.
