Jump to content

Recommended Posts

Dear Forum,

 

Its with great pleasure I can inform you that Capture One Pro is now live at www.captureone.com

 

Support is included for the RX100M5 and A6500 of course.

 

Don’t get you can upgrade your existing licence, subscribe or buy a licence outright!

 

Capture One Express 10 (for Sony) is still completely free.  So make sure you download today.

 

Enjoy!

 

www.phaseone.com/download

 

David

 

Welcome, dear visitor! As registered member you'd see an image here…

Simply register for free here – We are always happy to welcome new members!

Link to post
Share on other sites

Thanks for the announcement.  Money spent.  Update downloaded.  

 

Now I need to go read the bugfix list to see if the memory leak on Win10 is plugged.  I also need to see if the AWR failed condition that halts a file save when using layers and "processing" an image has been corrected.

 

Other than these things (from CP1 v9), this is pretty good stuff.  I love the IQ through the raw converter.

Link to post
Share on other sites

David, can you give us a sense of how much faster the image rendering is on v10 vs v9.  For an example, on my 2016 MBP 15", C1 still lags when I am rotating an image for a7Rii.  The same image in 3yr old Aperture v3.6 rotates without hesitation.

 

Thanks in advance.

Link to post
Share on other sites

David, can you give us a sense of how much faster the image rendering is on v10 vs v9.  For an example, on my 2016 MBP 15", C1 still lags when I am rotating an image for a7Rii.  The same image in 3yr old Aperture v3.6 rotates without hesitation.

 

Thanks in advance.

 

 

You are better served by checking the user forums : http://forum.phaseone.com/En/viewtopic.php?f=68&t=24977

 

Generally, the problem is that C1 will often, but not always, recalculate the image. There is supposed to be a cache, to speed things up, but it seems to me that if you toggle quickly between images then the caching does not work. If I count "one potato two" between toggling between images, then sometimes the caching works.

 

Actually, the normal description of how Preview Caching works given by C1 support ... does not match the C1 documentation. So I think there is a general misunderstanding of what is going on, why changing preview size does not actually help.

 

You will get the usual Blah about preview size or video card type, but these are Macs ... my impression is that Capture One don't understand, its not rendering speed that is the problem, its that each time you select an image it is being recalculated/rendered. Even if you don't make any edits. 

 

Rendering speed does depend on the amount of data to process, I find it much faster when images are zoomed to 300%, but I'm not sure how useful that tip is    ;)

 

 

Just now, an import with 4 images, each with about 5 modifications. toggling through the images, one image was cached others were continually recalculated, then I did an export of one of the slower images, then more toggling through the images, now all 4 images a continually recalculated ... no caching no matter how many potatoes I count.

Link to post
Share on other sites

timde, thanks for that.  Your spot on about switching images from one to another.

 

It seems that C1 regenerates preview from raw each time something is touched, change of view, small adjustments or what have you.  

 

Regardless of how its done, clearly its a sw issue and not hw....

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...