Renaming bug and general renaming poor performance.
1. So here is a bug I can reproduce everytime. Say you have a folder files are named ok _001, _002, _003, etc. then something happens like C1 crashes and the import counter (during tethered shooting) doesn't start off at the right place when you finally get C1 back up again - you get _003 1, _004 1, etc. So now I want to rename the whole folder, the quickest workflow for me is to select all of the images and do a batch rename starting at _001. Since it already starts at _001 C1 will not rename the files because I am telling it to rename the first file to the same name. That has been annoying me for awhile in V4 and V5. Please fix that b/c renaming is one of C1's really big downgrades over 3.7.
2. Batch renaming in C1 is so slow, painfully slow it borders on unusable. I gave up importing and naming through the CF card importer b/c it takes ages compared to copying in Finder. I know C1 has to write the filename 4 times but it never was this bad in 3.7 at all.I think the problem is in C1 basic structure. If it needs 4 files to support one image, that isn't very efficient. How about adobe's xmp file? - just one reference file per raw file that can optionally sit right next to the raw file. I think C1 should think about moving in that direction, simplicity is better. We do not need more features just better shooting and editing performance. I've tried running shoots through bridge, renaming there and then going back to C1 but then the session gets weird and images have trouble staying in order b/c the filenames of the raw files is not matched to the settings and preview files. Anyway renaming in C1 needs to be looked at. Tethered shooting and editing (including renaming) were the strengths of C1 before V4 & V5.
All of these issues were on a brand new i7 macbook pro with 8GB Ram and I am going to open a support case now.
2. Batch renaming in C1 is so slow, painfully slow it borders on unusable. I gave up importing and naming through the CF card importer b/c it takes ages compared to copying in Finder. I know C1 has to write the filename 4 times but it never was this bad in 3.7 at all.I think the problem is in C1 basic structure. If it needs 4 files to support one image, that isn't very efficient. How about adobe's xmp file? - just one reference file per raw file that can optionally sit right next to the raw file. I think C1 should think about moving in that direction, simplicity is better. We do not need more features just better shooting and editing performance. I've tried running shoots through bridge, renaming there and then going back to C1 but then the session gets weird and images have trouble staying in order b/c the filenames of the raw files is not matched to the settings and preview files. Anyway renaming in C1 needs to be looked at. Tethered shooting and editing (including renaming) were the strengths of C1 before V4 & V5.
All of these issues were on a brand new i7 macbook pro with 8GB Ram and I am going to open a support case now.
0
-
I think it is great you opened a support case for this.
A small note re. your 1-versus-4 files-needed argument. Adobe's xmp file in camera raw compares to CO 4 or 5's .cos file. Preview files for Adobe camera raw and Bridge are stored elsewhere. The fact that you don't see them, does not mean they don't exist. You can look it up in Bridge in the Preferences and Camera Raw Preference. Look for Cache.0 -
Hi Paul
Yes, I know about camera raw cache but somehow it only takes bridge seconds to rename a few hundred images where C1 takes minutes. Not time that I have during a shoot.0 -
1) Can't say I can reproduce the error, perhaps I'm just following the example incorrectly? Can you create a support case and provide specifics?
2) Hmm, it's slow when renaming over a network (in my experience) but not so when working locally. Again, create a support case and we'll take a closer look.0 -
Hi Drew,
1) I made a support case and the tech confirms this renaming issue and has reported it to the engineers. I know its been there since v4 started, I thought I mentioned it earlier or maybe I forgot. Either way I hope it gets fixed.
2) Tech acknowledges that C1P renaming is poor abd they all know about it, says it relies on the operating system to complete the task and they are actively working on it. I always shoot a session to the computers main hard drive - the same one with C1P installed - never over a network. I really just wonder why C1P performance in renaming images is so poor compared to Adobe's products? Its just a filename.0
Post ist für Kommentare geschlossen.
Kommentare
4 Kommentare