One big problem with C1, otherwis great
I am trying out C1 on the advice of a colleague,who says C1 is an excellent converter that will produce superb images. It does, but my problem is that it takes forever to load and be ready to use. The splash screen comes on like lightning on my quadcore 9350 intel with 8 gigs ram running win 7 64 bit Ultimate. A few seconds later the gui appears, but is locked up. If I wait between 1 minute 50 seconds and two minutes, the program then becomes operative and everything works perfectly and very fast after that. Until that two minutes is up, it acts like a permanently locked up application.
Fast start up is critical for me. I intend to use C1 as a secondary editing application, sending images to it from other applications (which works just fine except that I have to wait two minutes each time I use it). Can't live with that.
Anybody have any thoughts on what is hanging start up of C1? It is the only application of many I use professionally that does that. If I can't find a workaround or fix this, Ci will be useless to me, which would be unfortunate because c1 has some excellent image development features.
Fast start up is critical for me. I intend to use C1 as a secondary editing application, sending images to it from other applications (which works just fine except that I have to wait two minutes each time I use it). Can't live with that.
Anybody have any thoughts on what is hanging start up of C1? It is the only application of many I use professionally that does that. If I can't find a workaround or fix this, Ci will be useless to me, which would be unfortunate because c1 has some excellent image development features.
0
-
Perhaps you have Capture One opening a folder with a lot or much more than a lot of images on startup? 0 -
Thanks Paul,
I set up a new session in the root of an internal drive with just one image in it. That reduced the time to one minute. I will experiment some more with differing numbers of images in the folder to see what difference that makes--but, that means that the time can only get longer. One minute is just too long for startup when I will have to do this operation 30-60 times a working day. I am also trying Bibble 5.1g, which takes 4 seconds to open when I send an image to it. Bibble also has some excellent develop features, by the way, but neither Bibble or Lightroom will match the results obtainable with C1, so I am hoping that I just have something configured wrong that retards the startup of C1.
Anyone have any other thoughts on this problem? What kind of startup times are you and others experiencing with C1 on an x64 win 7 system.0 -
I have CO 5.1.2 Pro started up in approx. 8 sec. from Win 7 x64, core i7 processor, SSD drives only. With a regular HDD it should be approx. 15 sec to 30 sec max for a machine like yours. I have very few applications installed (a clean, lean and mean machine).
I think there is another issue in your machine. One minute seems slow to me, but I do not have a clue yet.0 -
I'm on Win 7 Home Premium x64, with Cap One installed on a pretty ordinary 1tb HDD, the machine having an Intel Q8300 Quad core processor and 6 gb RAM, and I've just timed Cap One start-up here at 20 seconds, which is still a bit "leisurely" compared with the likes of Bibble 5 and Lr 3. 0 -
On my machine (Windows 7 64bit, i7, 12GB RAM, 1TB HDD 7200rpms) Capture One 5.1.2 open's in <15 seconds.
I put this machine through its paces everyday and don't have any issues with stalls or speed. Granted this machine is stripped down as I only use it for work, the only other real programs on there are various Photoshop versions, however I like to think of this machine as the "base" that everyone should be able to match with comparable hardware.
If the speed issue persists, create a support case and we can look into it a bit further. There are other files that Capture One tries to load when it first starts which, if one is corrupt, may contribute to slowdowns... corrupt ICC profiles for example?0 -
[quote="don s" wrote:
One minute is just too long for startup when I will have to do this operation 30-60 times a working day.
Assuming an eight hour work day, why would you bother closing out CO and restart it every 8 to 16 minutes? I leave it running for hours on my old XP system.
When I do exit, I will first "park" the program in an empty folder so it doesn't reopen photos that I am finished with. I usually just empty the Trash folder, then click on it to make it the active folder.0 -
[quote="Coach" wrote:
When I do exit, I will first "park" the program in an empty folder so it doesn't reopen photos that I am finished with.
Now that's a good idea, Coach!0 -
[quote="Keith Reeder" wrote:
[quote="Coach" wrote:
When I do exit, I will first "park" the program in an empty folder so it doesn't reopen photos that I am finished with.
Now that's a good idea, Coach!
Had the same thought 😉0 -
Of course, ideally C1 wouldn't start processing/proxy building in any folder unless/until we explicitly told it to. 0 -
I think it would be nice if CO had an option to either open to most recently used folder or to always open to a user specified folder (such as the root directory of one's most used image file drive) 0
Post ist für Kommentare geschlossen.
Kommentare
10 Kommentare