Capture One 20 Stability is bad
Hello!
I bought an new Thinkpad P-53 (32 GB RAM, 3 x 1 TB very fast SSD, and Intel i-9 processor) and upgraded from CO12 to CO20. Then I transferred my picture-files (ca 90.000) from an external HDD to an new QNAP TVS-472-T NAS.
I made a mistake and moved all picture-files (from external HDD to the NAS) within CO20 .
Result: It last 2 1/2 days, CO20 crashed and the CO20-catalog was destroyed.
Step 2: I rebuild the CO-catalog from an old backup, but lost my 2015-folder with some thousand picture files. Only in the catalog fortunately not on the disc. I used the "find folder and synchronise" in CO20 and had to do this for each subfolder (178). This took nearly one day.
After 2015-folder was in CO20 again suddenly CO20 couldn´t find the subfolders of my 2014-folder. Again I had to use the CO-finder for 2014-directory and had to "find and synchronise" each sub-folder (147 directories) - terrible work. Unfortunately CO found only the picture files an no CO-edit-files. What a pitty!
But my real problem is the stability of CO20. When I import a larger number of files (some hundreds) CO crashes. It crashes also when I try to rename an folder in CO-Catalog.
Question 1: Are there any general problems with CO20?
Question 2: What can I do to get a stable CO20. Should I deinstall CO20 and reinstall it again? But I fear that the problem with the "not finding some directories and files" will happen again.
CO support told me only "that picture files will never get lost in CO20". That´s true but to edit thousands of RAW-files again this an terrifying thought.
Greetings 😭
Andreas
I bought an new Thinkpad P-53 (32 GB RAM, 3 x 1 TB very fast SSD, and Intel i-9 processor) and upgraded from CO12 to CO20. Then I transferred my picture-files (ca 90.000) from an external HDD to an new QNAP TVS-472-T NAS.
I made a mistake and moved all picture-files (from external HDD to the NAS) within CO20 .
Result: It last 2 1/2 days, CO20 crashed and the CO20-catalog was destroyed.
Step 2: I rebuild the CO-catalog from an old backup, but lost my 2015-folder with some thousand picture files. Only in the catalog fortunately not on the disc. I used the "find folder and synchronise" in CO20 and had to do this for each subfolder (178). This took nearly one day.
After 2015-folder was in CO20 again suddenly CO20 couldn´t find the subfolders of my 2014-folder. Again I had to use the CO-finder for 2014-directory and had to "find and synchronise" each sub-folder (147 directories) - terrible work. Unfortunately CO found only the picture files an no CO-edit-files. What a pitty!
But my real problem is the stability of CO20. When I import a larger number of files (some hundreds) CO crashes. It crashes also when I try to rename an folder in CO-Catalog.
Question 1: Are there any general problems with CO20?
Question 2: What can I do to get a stable CO20. Should I deinstall CO20 and reinstall it again? But I fear that the problem with the "not finding some directories and files" will happen again.
CO support told me only "that picture files will never get lost in CO20". That´s true but to edit thousands of RAW-files again this an terrifying thought.
Greetings 😭
Andreas
1
-
Andreas,
In general my experience with a Synology NAS is that it has its own agenda for work and will sometimes go off to do it's own thing for a short time (possibly up to several minutes) rather than serve files to applications.
I use it mainly as a backup and for that this method of working is not too inconvenient.
I also mostly use Sessions and probably have not more than about 6000 to 7000 original images in a session. Hoever I do have some small test catalogs that seem to work ok if a little slowly compared to having them on an internal drive.
The only time I see a crash is when the NAS has gone into hibernation for a while and either does not seem to get a message to "wake up" or does appear to wake up (I have if next to me so can hear disk activity) but does not make itself available quickly enough or completely enough to satisfy the C1 response requirements.
If your cocatalog file(s) or on the NAS I would suggest moving them to the main system.
Source files on the NAS are probably OK most of the time but perhaps not fast - although I expect the speed may be a function of the NAS configuration in some part. The way I use mine (Wi-Fi network connection) means I do not really expect to use if as a full time primary data source when editing a new shoot. So for me further investigation does not seem like a good use of time.
I suspect a NAS is a great idea for an "archive" catalogue - even a very large one - but not so good for interactive use - especially for a large catalogue.
C1 V20 stability on my WIn 7 based 7 year old notebook using internal SSDs is fine. But as I said earlier I can only claim that for on the basis of experience with relatively small (total 50 to 60GB and maybe 40k-50K total files of which 5-6k are original images) sessions and a few small catalog test files on local drives.
HTH.
Grant0 -
Andreas,
Did you put the catalog on your computer's internal drive or on the NAS?0 -
Hello Paul,
the CO-Catalog is on the Notebook (ThinkPad P53) and the picture-files on the NAS both connected by LAN (both with permanent IP-address).
If I start CO20 it always shows folders and pictures as "offline". I have to start the WIN 10 Explorer and select the network drive where the picture files are located. After this step I change to CO20 and now folders and picture files are shown online.
At the moment I´m very disappointed, because it took so much time to get CO20 running and it will cost much more time (and nerves) to edit the 2014-pictures and some of 2015.
On my old Notebook (SAMSUNG NP940, 8 GB RAM, 250 GB SSD) the catalog has been on an external HDD (USB-3 connection) together with the picture files and all worked well, beside of the speed. Later I changed the internal SSD for al larger one (1 TB) and placed the CO12-Catalog on the internal SSD, the picture files still on the external HDD (USB-3). Speed was better and all worked stable. Under CO12 my catalog never crashed as often as it has been in the "new and better" CO20. I think it´s an CO20-bug, or CO20 isn´t suitable anymore for moving large amounts of pictures within its explorer (catalog structure). In this case Phase One should tell about this restriction.
As there is enough storage on my Thinkpad I consider to store the picture files of 2020 on the internal ThinkPad-SSD and transfer the whole 2020-directory to the NAS by end of the year. Hoping that the procedure will not show the same difficulties shown above.
At the moment CO20 works well but I´m not really convinced of CO20-stability.
Best regards
Andreas0 -
Linzer-1962 wrote:
Hello Paul,
the CO-Catalog is on the Notebook (ThinkPad P53) and the picture-files on the NAS both connected by LAN (both with permanent IP-address).
If I start CO20 it always shows folders and pictures as "offline". I have to start the WIN 10 Explorer and select the network drive where the picture files are located. After this step I change to CO20 and now folders and picture files are shown online.
At the moment I´m very disappointed, because it took so much time to get CO20 running and it will cost much more time (and nerves) to edit the 2014-pictures and some of 2015.
On my old Notebook (SAMSUNG NP940, 8 GB RAM, 250 GB SSD) the catalog has been on an external HDD (USB-3 connection) together with the picture files and all worked well, beside of the speed. Later I changed the internal SSD for al larger one (1 TB) and placed the CO12-Catalog on the internal SSD, the picture files still on the external HDD (USB-3). Speed was better and all worked stable. Under CO12 my catalog never crashed as often as it has been in the "new and better" CO20. I think it´s an CO20-bug, or CO20 isn´t suitable anymore for moving large amounts of pictures within its explorer (catalog structure). In this case Phase One should tell about this restriction.
As there is enough storage on my Thinkpad I consider to store the picture files of 2020 on the internal ThinkPad-SSD and transfer the whole 2020-directory to the NAS by end of the year. Hoping that the procedure will not show the same difficulties shown above.
At the moment CO20 works well but I´m not really convinced of CO20-stability.
Best regards
Andreas
A thought, have you allocated the picture folder on the NAS a drive letter, on my Synology NAS it is z:/. That said Windows does not always recognise it when booting up, I have got into the habit of opening windows explorer when I boot the machine and ensuring that the Z:/ drive is selected and available. After that I have no trouble with communication between CO and the NAS.
Dave0 -
Hello David,
yes, the NAS got its own drive letter R:/. In general the communication between Win10-Notebook and my NAS is perfect (on LAN and WLAN). Both got an static IP-adress, too.
Actually I do it in the same way as you do.
1st step: start Windows-Explorer selcting drive-letter R:/
2nd step: start CO20 and all directories and folders are shown as "online".
Beside of this I think CO / Phase One should look at this item because, in my opinion CO20 is a professional and costly SW. I expect a software which is nearly perfect for any user.
Best regards
Andreas0 -
As David wrote it, you will have no choice than to click the drive in Windows Explorer after every computer start to establish communication. Network drives with a red X are a well-known Windows problem since long. Linzer-1962 wrote:
Beside of this I think CO / Phase One should look at this item because, in my opinion CO20 is a professional and costly SW.
Here Phase One is the wrong addressee but Microsoft is challenged but they have not yet managed to solve this. If you search the net you'll find many ideas to automate this with startup scripts, that would be the only way to make it a bit more comfortable.0
Post is closed for comments.
Comments
6 comments