Crazy Slow CO5 Performance
I find CO5 incredibly slow as a capture and editing program. Though editing is far more frustrating then capturing.
I am wondering what is the user base consensus on this, and what known tip or tricks are out there to alleviate some the pain?
My last capture session consists of about 1600 images. Captured with a Phase back using 5.0.2.
While editing, paging to the next page of images the thumbnail redraw takes as close to forever as I can stand. Some times over 5 minutes to redraw the new thumbnails. During that process CO5 is completely non-responsive.
It has taken me several hours to select 100 images from my list of 1600. This is not an acceptable workflow.
System info: Mac 8 core, 12 gig ram, 14T raid
Any feedback, tips, support would be really appreciated.
Thanks
Joseph
I am wondering what is the user base consensus on this, and what known tip or tricks are out there to alleviate some the pain?
My last capture session consists of about 1600 images. Captured with a Phase back using 5.0.2.
While editing, paging to the next page of images the thumbnail redraw takes as close to forever as I can stand. Some times over 5 minutes to redraw the new thumbnails. During that process CO5 is completely non-responsive.
It has taken me several hours to select 100 images from my list of 1600. This is not an acceptable workflow.
System info: Mac 8 core, 12 gig ram, 14T raid
Any feedback, tips, support would be really appreciated.
Thanks
Joseph
0
-
Joseph,
I am not the User Base so my response may not be what you are looking for. However as a tech for Phase One I can point out the likely reason for the lack of speed is the 1600 images in a folder. If you split that single folder into 6 or 7 smaller ones you should see an immediate adjustment in speed.
Having 1600 large files (>25MB/each) in a single folder means Capture One is accessing just shy of 40GB of data at once. No easy feat regardless of your hardware. Dial that number back and you will see speed improve in drastic ways.
Also, depending on your RAID setup you may actually be hindering Capture One's access. RAID setups, if done in unconventional ways, can impede speed rather than their intended effect.0 -
I have to second Drew's response to this...
by creating a sub folder for each of your 'looks' this will cut down dramatically on the overall amount of images C1 is accessing... thus increasing performance and speed...
I can't comment directly on the effect of the raid, but without a doubt shrinking down the amount of files that c1 is accessing will help.0 -
I too find c1 to be slow, slow to tab through a shoot, slow to render, slow to adjust. what you say makes sense in terms of the number of files per folder. my question is why then is that not a problem when using the same folder in another program like lets say photomechanic, or even better, adobe lightroom? those dont seem to suffer from any amount of images in a folder. 0 -
The software's may operate on the same basic principles and try to achieve the same end result but the bottom line is that they're different and that's that. So comparison in these terms is not at all equatable. 0 -
so,...be inspire by Photomechanic!!
This cheap product is working perfectly, never crash, never slows, so quick, but it's true, it's not a converter.
It's so true that for editing, I use photomechanic, time is money!, and you can check your pictures @ 100% without 1/100000 sec delay! And when I tag picture in PM, I can see the tag in C1!0 -
We have found several Sub Folders to be the exact opposite of what is recommended by Phase One, as seen above.
The Problem: Photographers who want to edit, find CP5 Painfully slow to use.
The Reason: The Proxie Cache now needs more time to render images the 1st time through the folder than CP3 did.
The Bottleneck: About 5-10 seconds after visiting a folder, CP5 begins to render the Proxies, as seen by the spinning circle in toolbar. In CP3, you could continue to work on the folder with a beefy machine while rendering happened in the background. This no longer seems to be the case. CP5 is using near 100% of system resources to render these proxies for the 1st time.
Testing: CP5 creates the Proxie Cache approximately twice the time it took CP3. Additionally, CP5 will only work on Caching one folder at a time. If you click to another folder, it stops working on that folder temporarily. It will continue the next time you click on the folder. It will pick up where it left off. No amount of changing options, sizes, different cameras or anything else we tried, made any difference to speed up the cache time.
Temporary Solution: Until Phase One realizes the problem I described above, and fixes the problem, the best option seems to be put all your images into one folder, wait 5 seconds until the spinning circle shows up in the toolbar, click on it to see what it's doing, and wait until it finishes. After that, you will be able to work at a normal speed. You can split the folder into sub folders after that. If you started with subfolders, rename the images so you can scan them all, then move them back where they came from. Otherwise, you need to babysit the folder caching one at a time, which may be more annoying than throwing them all into one folder and waiting 2 hours.
Permanent Solution: Phase One adds a Caching option to manually cache all selected folders. It would then have a visible display of items left to cache, and expected time remaining. Additionally, it would have a slider to adjust the amount of system resources used to cache folders. This would allow for us to cache the first folder with 100% resources to get it done, then slow it down to 25 or 50% for background processing.
It is less about how long it takes, and much more about not being able to use the computer until it finishes. Phase One documentation for all the details about how to use their amazing new software is barely existent. Things like changing the usage of the "Toggle Edit Primary and Edit Variants" option to be the exact OPPOSITE from version 5.02 to 5.1 and not mentioning it in the release notes was a terrible waste of our time. I want to use the software, not beta test it. 1 minute after loading 5.1 (seriously, 1 minute) I found that Moving Favorites around would crash the program. Not sure why I had to be among first people to discover such a basic feature was now broken.0 -
Does Capture One 5 take longer than Capture One 3? On the same machine it likely does as the Proxie is much more dynamic as it was in Capture One 3. Hence the ability to zoom into the preview and the more accurate preview quality.
By putting all of your 1600 images in one folder you are guaranteed slow performance. By breaking it up the wait is minimal, that is not really open to interpretation it is a straight forward fact. If your machine is a beefy machine then you should not have any real issues. I use a now out of date MacBook PRO and can use it in my day to day with P65+ files. The performance is not the best it could be but certainly workable.0 -
The slowness is beginning to cause issues with clients. When capturing to 8 core Mac Pros there should be no lag, but it is really horrible. The clients are asking why it is slower than previous softwares. I am running CP1 5.2 on a number of Mac Pros, so it is not just a machine issue. It seems to work just as fast on 27" iMacs, so it is not addressing what power is available. I keep the folders under 300 images, but each day can be from 1000 to 3000 images. As the day goes on, the speed in which the images pop up gets slower...It is basically unusable on new Mac Book Pros. The clients are getting frustrated and just walking away from the monitors. This reflects on all of our businesses, and we should ask that it is addressed sooner than later. 0 -
Ronn,
Which Phase One Back are you shooting with?0 -
I agree, and forgot to mention that in my previous post. Out Laptop takes just as long to process the proxies as our main workstation. This will again, stop you from getting anything else accomplished.
I would love to see how PhaseOne machines work so speedily, and the rest of us are suffering. If it was one machine, then that is one issue, but I have 2 machines here, and other posters with similar issues. Opening a ticket, they offered some interesting things to try, but nothing solved the main issue. Our pictures usually sit in a folder of under 200, and that caching is the bear for us. The thing is, since testing version 4, out images have never looked better. Now, with version 5, not only are locked into the software that supports our new camera, but speed that I can batch correct, and get wonderful results, leaves us in the situation where we can't NOT use it. If only there was some magic answer to make it faster.0 -
Bob,
Which Phase One Back are you shooting with?0 -
I have a P45+ and 2-P30+s. I just ordered a P40+ today... 0 -
Hmm, lets take a closer look with some details in a support case. 0 -
I have used Capture One software for over 8 years..... shooting into it almost every day.
Something very serious is happening with versions 4 and 5..... it is too slow to use.... rendering of files is so slow.... it is almost impossible to edit.... moving form frame to frame just takes too long..... and there are too many bugs that cause it to crash.
I now go back to version 3 to shoot into when it's important.
I shoot with a Phase P30+ and Canon 1DS MK11 and 5D MK11.
I now use Aperture with there cameras ... although they wont tether... just because it is so much faster to edit with.
Please fix whatever it is you changed in order for the files to render how they used to ....... otherwise you will see floods of customers leave to use other faster more reliable software manufactures.....0 -
[quote="oliver11" wrote:
I have used Capture One software for over 8 years..... shooting into it almost every day.
Something very serious is happening with versions 4 and 5..... it is too slow to use.... rendering of files is so slow.... it is almost impossible to edit.... moving form frame to frame just takes too long..... and there are too many bugs that cause it to crash.
I now go back to version 3 to shoot into when it's important.
I shoot with a Phase P30+ and Canon 1DS MK11 and 5D MK11.
I now use Aperture with there cameras ... although they wont tether... just because it is so much faster to edit with.
Please fix whatever it is you changed in order for the files to render how they used to ....... otherwise you will see floods of customers leave to use other faster more reliable software manufactures.....
You are no doubt a serious and experienced CO 3-4-5 user. However, with so little information about your setup, number of images in your folder etc. you do not give much to focus on for improvements.
Performance issues are equally as much related to personal setup and preferences as well to hardware and software setup. Even when CO4 or CO5 is the only program running slow on your system, it may run fast on another similar system. You tell me what is the culprit. You are invited to share more details or open a support case to give Phase One something to chew on to finally get what YOU want.0 -
My set up
iMac
Mac OSX 10.6.2
3.06 GHz Intel Core Duo
4GB Ram
also
Mac Book Pro
Intel Core 2 Duo
3.06 GHz
8GB Ram
Shooting tethered or importing via F/W 800 card reader
I start with a Phase P10 back.... the old days !
P30 about 5 years ago
P30+ for the last 3 years....
Used version 3 extensively for years and without any major issues....loved the ease of use and the ability to stick a client in front of it and they could understand and operate it for editing purposes.
Version 4 was a big leap backwards as i know you understand.
Version 5 ... i had major hopes for.... but it is so slow to render preview images.... even when this is done when you scroll down through it still seems to re-render on the fly.... something version 3 didn't do .... When shooting tethered there is considerable delay until you can view the render image. This occurs when i shoot in the capture folder with a lot of images or just a few. I have had my assistants set up separate folders for each shot or just dump the day in the capture folder.... either way is reacts the same........ i know many many photographers who feel the same. I have been a professional for over 28 years.... my web site www.oliverpearce.com
I was on location for the last month.... shooting every day..... i ended up shooting into version 3 due to to delay in rendering and crashes that occurred in version 5.01 then when back at my hotel we would transfer all images into version 5.01 and let them render.... approx 1000/day..... rendering in about an hour..... I would stay in version 3 if i hadn't upgraded to Snow Leopard that i found corrupts the jpg images when exported.
I am looking to upgrade my P30+ back but i have to admit i am very disappointed with the last version of Capture One. I should have to go back to version 3 in front of clients. I do think there are certain improvements but there does seems to be major issues as well...... and it does seem i am not alone. I have tried the usual steps..... reinstalling ..... different machines..... small capture folders..... etc etc..... but can you explain how Version 3 rendered so much quicker compared to version 5. I seems to remember there used to be a preview size setting in the version 3 ? When moving from image to image and trying to edit it is all about speed...... Aperture handles it by having a Preview mode then turning this off to make adjustments and export a high res..... also does Aperture not handle your Phase files when Lightroom and Photoshop does ?... is this an Adobe / Apple thing ?
Anyway thank you for your quick response..... it will be interesting to see if there is something that i am not seeing that will make a massive difference.
Many thanks for your help.0 -
Yes I agree that v5 is very slow. I have been watching a progress bar move across my screen for the last 2 minutes as I try to move 193 images from one folder to the other. Capture one 5 whilst being the first useable version of the post 3.7.9 C1 versions is slow to a: Import, b: scroll through when editing., c: move files around. v 3.7.9 really does seem like a greyhound in comparison. I prefer the way the files look in v5 (on the canon 1ds mk3 anyway) and it is the only way if you need to tether. I wish it could have the same nimble feelings as it used to have. My files have moved and I am off! 0 -
Hello @all, first post here!
I think there are two issues discussed here. I have a iMac 2,93/4GB and a MacPro 8x2,26/11&9GB. I had a discussion with Phase One in Europe about the setup of my MacPro. I had a Raid and 11GB. My Mac-technician told me to reduce RAM to 3x1GB plus 3x2GB. Helped a little bit. Syncing every evening my HDs instead of a Raid helped also a little bit. (Don't mention time killers like a complete reinstall of MacOS and C1...)
BUT: C1 5 is slower (on both machines) than 3, no doubt. So slow that is has sure impact on my time budget and I'm unable to meet tight deadlines now.
The second is: editing and organising is faster on my iMac than on my MacPro. C1 seems to have serious problems with that type of machines. This machine is much more powerful than my iMac an is in a very annoying way unresponsive (for minutes!) and crashes nearly once a hour.
I spent a lot of money for that machine for a absolutely unacceptable performance, thanks to C1.
I shot many PO backs, several DSLRs, all with CO1 since v3.6.1. I've got no time to get annoyed from a neglectful coded software which bothers my clients.
So, if there is a new cam this/next year which is not supported by CO 3.7.9 (and Phase One doesn't get the job done) it'll be Lightroom.0 -
[quote="christian20" wrote:
I'm on MacPro 8x2.26GHz & 12GB RAM as well. OSX 10.6.2. Too, my RAW files are located on a RAID (mirrored).
I have a iMac 2,93/4GB and a MacPro 8x2,26/11&9GB.
...
I spent a lot of money for that machine for a absolutely unacceptable performance, thanks to C1.
I have absolutely NO performance issues. The software is very responsive, redraw when editing is fast, processing is fast as hell. The sole thing that is a bit slower than V3 is scrolling through thumbnails in the browser as long as they are not fully cached. Actually I don't work in such big sessions/folders but for testing I assembled a folder with 500 P45 captures and C1 still goes quite fast and smooth.
What comes to my mind is you are possibly working in sessions created in a prior version of C1 and/or you've stored settings/presets from V4.
What may slow down C1 dramatically are preview caches from older software versions. Delete all *cop and all *.cof files from the drive your sessions are located. Too, the batch queue may cause performance issues (delete the history and the folder ~/library/application support/capture one/batch queue).
C1 caches favorite folders. So basically it will speed up things if you are working in different sessions containing just a few folders rather than working in one session with a lot of (favorite) folders. Ideally create a new session for each shooting rather than just adding a new folder to the session you are currently working in.
Too, LCCs are cached... so if you are working with a lot of captures form a tech camera and consequently are creating a lot of LCCs I'd suggest deleting the LCCs regularly (~/library/application support/capture one/LCC profiles). You can re-create them any time.
I experienced quite a few perfomance issues with many upgrades of C1. They were always related to older settings, preview cache, batch queue / history. If you start form scratch, C1 should go very smooth.0 -
Strange ....
i do create new sessions for each job..... very rarely work with older sessions created by previous versions of C1.
Try scrolling through the browser previews in C1 5.1 and it rebuilds the thumbnails as you scroll up and down.... even after they have all been fully cached. C1 3 never did this..... it built them once and then you could view in a totally smooth way. And there is also a small delay when you click on an image while it builds the full res preview. Very hard to edit properly when this happens..... you need a smooth transition between images..... especially when a previous version did this properly.
It may be that you have 12gb of ram.... not possible in a MacBook Pro..... so fine if you are in the studio but not so good if you are on location.
Done all the other things ... emptied batch queue cache (why does it need to keep this after they have been processed ?)
Always work with one session open..... no favorite folders...... i can't believe it is to do with this ..... i think there is a code issue with this software..... and the way it handles thumbnails.
Processing is very quick with version 5.1
Waiting for Phase to fix this...... please !!0 -
I agree with all comments by earlier posters about symptoms and the pain on getting through a job. Our computers are MacPro 6GB Ram 2x2.8mhz Quad Intel Xeon working off a FW800 (working on internal drive gave no speed increase for this problem). We also have MacBookPro 4GB Ram, but forget the processor speed right now, Intel.
Click on folder, wait for caching to finish. Click on image, wait 1 second for refresh of image. There is a lag in delete, rename, move and any other similar operation.
We are not using older cache files, versions, or whatever else you have suggested.
PLEASE find the problem. I know I have spent much time testing and troubleshooting with only minimal results. This is killing an otherwise wonderful program.0 -
Regarding the performance of moving files, you cannot really compare with the Finder for example (or even 3.7) because Capture One moves not pnly the RAW file but also all files associated with it (previews + adjustments) so at the minimum 3 files instead of 1 in the Finder. 0 -
You can see how fast it can be in CO if you tag a folder as "move to"-folder and press apple-J. Pretty fast. Do it by mouse and you wait seconds of seconds and drag it to the wrong folder and sort it out of this folder and try to get it into the right folder and so on.
That sort of things. Now i'm currently working with Adobe CS. Better choice.0 -
Because of the slow caching, redrawing and deleting process, the photographer now wants to leave CP5. After trying everything we have been told, I don't know what more I can do to make his laptop work any faster. Turning OFF the cache seems like a good option, because he doesn't need a cache at all. Especially not when it takes so long to generate them, over many folders, where he can not do anything but cache. 0 -
Bob,
Create a support case and give us more details.0 -
I have submitted a ticket, did what was suggested, nothing helped on multiple machines. 0 -
Bob,
I looked up your case and, although you've reported your times as slower than Capture One 3 I wouldn't classify them as "Crazy Slow". Waiting 8 seconds to load 52 images (analyzing 1.12 GB of information) and doing so off of an External Source seems in line with what we would expect from the software. Upgrading to an SSD machine drive and working on the Local boot would likely reduce that wait to about 3 seconds (rough estimate based on limited experience).0 -
With CO5 I often have the feeling my Computers(PowerMac 2x2.26 GHz Quad-Core,8GB and MAcBook 2.4GHz Intel Core 2) are filled with chewing-gum. It's not the conversion-speed, it's the reaction on mouseclicks building previews and so on. Never had this feeling with 3.x. seldom have more than 300 files per session.In addition I hate some workflow issues: Importing from Card and waiting for all the thumbnails to show before you can click on import all and then waiting again.
Wish you all a nice weekend and hope you don't have to edit images still on sunday 😉
Wilfried0 -
I have less of an issue on my PowerMac than i used to. Not because the speed is any faster, I have just learned how to adapt, and come certain expectations. I think out biggest problem these days seems to be the photographer, after a long day of shooting, trying to edit down images he took on his laptop.
The software wants to cache the files, when he wants to delete half of them. I think a huge solution to many peoples problems, would be the ability to turn on/off the automatic caching. In our case, the caching does not need to be done until 2 days later, after the bulk has been thrown out, and has moved to a faster machine.0 -
Drew, Bob is correct. The proxie performance is miserable.
First, automatic proxy generation should be optional. There needs to be a way to turn it off.
It's taking 15 minutes to generate 90 proxies. It's using 100% of the processor, and damn near all available RAM. It's pathetic. I can't edit or process anything while this is going.
The thumbnails come up quickly, which is great. But the proxies make me want to jump out of the window. Or just throw the computer.0
Post ist für Kommentare geschlossen.
Kommentare
61 Kommentare