Sorting Files inside a Catalog
There seems to be a a problem with the sorting of file names within a catalog. I have a catalog that holds my images as referenced files. The files are stored on the hard-drive in folders that are named with the numeric of the year (i.e 2004, 2005, 2006 all the way up to 2012). Inside these folders are other folders titled with the date of the shoot in the format yymmdd and a title, such as 120714_Havana. Inside these foldera are the images with filenames based on the date, plus the file reference number from the camera, i.e. 120714_3425.nef. This means that all images are in strict date order.
I have imported all these files into a catalog as referenced files. Everything is fine until I close Capture One 7.02 and re-open it. Then the year files are re-sorted i.e. 2012, 2005, 2011, 2009, 2006, 2004, 2008, 2010, 2007. In addition, the folders inside the year folders are also re-sorted, i.e. 120730_Havana comes above 120317_Miami. If I right-click on the catalog name and choose "Sort by Name", then the catalog re-orders itself correctly, but when I close Capture One and re-open it, then the folders are once again out of date order.
Can someone give me some indication as to what the problem is. The files all sort themselves correctly in Lightroom, but I don't want to use the Lightroom processing engine.
I have imported all these files into a catalog as referenced files. Everything is fine until I close Capture One 7.02 and re-open it. Then the year files are re-sorted i.e. 2012, 2005, 2011, 2009, 2006, 2004, 2008, 2010, 2007. In addition, the folders inside the year folders are also re-sorted, i.e. 120730_Havana comes above 120317_Miami. If I right-click on the catalog name and choose "Sort by Name", then the catalog re-orders itself correctly, but when I close Capture One and re-open it, then the folders are once again out of date order.
Can someone give me some indication as to what the problem is. The files all sort themselves correctly in Lightroom, but I don't want to use the Lightroom processing engine.
0
-
Yes, the catalog don't work. But at least you get your images into a catalog. My catalog always crashes minutes before import ends (why doesn't it at least crash at the beginning, saves me hours of work?).
Even my small test catalog (the only one that I can actually use, as the big one crashes every time I try to build it) can't get the folders straight.
In the folder order I have the folder for Feb 13th, Feb 15th, then january 26th, then Feb 19th, then December 19th, and then, for a change, Feb 9th.
Too bad the 7.1 update wasn't really an update as it did nothing to address the broken catalog feature - which is so necessary as you need to get your images into a catalog in order to process them (no way I'm going to do sessions).
It's a bit like having a great car, but the wheels are square, not round, so it can't drive even though it's a Ferrari.
Let's hope for round wheels at the next update.0 -
One reason is the lack of free RAM, induced by misbehavior of Capture Core Server.
Capture Core Server still is a 32bit application, while COne itself is 64bit.
When it come to the end of free RAM on your system = Capture Core server allocates RAM but does not free it, it allocates and allocates and allocates until no free RAM is available, and, though, the system crashes, sometime with Kernel Panic. (See the Crash reports!)
I have never ever seen any Software in a mac, that starts the it's "Crash reporter" immediately prior to do anything with it's related software. (For sure, they seem to know why)
The workaround to often avoid this crash is:
1. Open Activity monitor and supervise the RAM usage. The blue indicator is the one of interest.
2. Open terminal
3. Open COne or MP,because behave the same, but seemingly with other triggers to let the application behave like this ...
4. When the blue indicator nearly arrives the RAM limits, go to the terminal window and type "purge" and enter the command. "purge" frees the "inactive" RAM. If you are lucky, the system returns to a stable condition that let's you continue working - at least it allows your save your current work.!
---
Not all "inactive" RAM, which usually should do no harm to a Mac system, following Apple, might be freed by purging, but it give you the opportunity to store your recent work, close the catalogue/session, and close COne.
For sure, this has nothing to do with proper development and/or the delivery of proper tested and QA approved software, but it saves your recent work!
---
Sometimes even a re-open does not indicate all added steps to your workflow - so you have do the "CO" (close and open) again.
saludos redondos -
tom0
Post is closed for comments.
Comments
2 comments