Capture One Pro 10 is so slow that I have to give it up!!!
I am a Capture One Ambassedor myself and I have been having issues with Capture One 10. The most influential one being TOO SLOW. I can hardly browse through the photo in a session. FIX THIS QUICK!!!
0
-
I installed the update, and it is still slow. It depends on which register is opened: for example it the color register is opened, I can switch through the pictures quickly. But if the output register (for rendering pictures) is opened, it is really slow. 0 -
Same thing here 🤬 , got a Mac Book Pro 16 GB in RAM plus 8 in the video card a couple of months ago, so I thought "here we go!! no more memory issues with Capture One", but no!, it works so slow that I am writing about this. I have this problem since CO 9. Now of course I love it when it works but I wonder if all the time I have to wait is worth it. Will you please hire someone who solves this!?
When is this problem going to be taken seriously. CO is no longer an ONLY editing tool but is also a Photo DB program. I don't want to have to use Bridge Again, I don't want to have to have to "sync" manually all the folders that I have made in my HD. This is really annoying and I don't feel heard by the PhaseOne company, has any one heard back from CO reps via this forum?0 -
Also here, very slow. Especially the new sharpening tool and if I put movement in lens correction
it takes up to 30s to show 100% view. That's sad.
But LCC is a lot faster!
Mac Pro Quad Core Intel Xeon E5 3.7 GHZ, D500, 32 GB Ram0 -
I have to back pedal somewhat on my previous post.
If I click All Images it slows to a crawl for a couple of minutes which lots of spinning beachball.
I tried moving my catalog to an SSD but left the originals on a spinning platter HD, it made no real noticeable difference. You also can hear the hard drive working.
I really like the program but working with "All Files" is something I do when I am looking for certain Keywords. I will try a Smart Album when I want to search a keyword.
Other than this annoyingly slow process I have not had much trouble.
I regenerated all the previews and that helped a little, I think. I even tried making smaller previews but did not notice any real improvement.0 -
[quote="jakoblehner" wrote:
It is so disappointing. It seems the C1 catalogue is still not production ready.
...
The worst thing is that when I accidentally click on all images, then C1 freezes and even after waiting some minutes nothing happens I have to kill the process. When I do this the catalogue gets corrupted and I get this error message:
"The requested document type is not recognized.
The provided database is of an unknown type."
So I have to get the latest backup of my whole catalogue and every work I did since the last backup is lost. This does not sound like a program worth investing 500€ (over time with updates) since I'm using it. Don't get me wrong I'm a professional and pay for good stuff but right now I can't consider this mess as good stuff.
I thought it would be good to move to C1 v10 from Aperture and CNX2 before I get stuck too deep in the dead end.
Gosh did I regret not testing the C1 more before I bought it.
It looks so nice and works great when you dont have any photos in it. But if you add a couple of thousands and then tens of thousands it becomes totally impossible to work with.
Aperture performs like a greased lightning.
And trying to create one catalogue for each year by downsize the one containing many years, ended in a total hang and after a forced quit the database was currupt and C1 unable to repair it. :/
So now I have to begin from the top again.
The v10 is definetly not production ready.0 -
Yup, same experience here. And the bad thing is that there's not a peep from PhaseOne.
Yet, some people claim to have no issues, but no-one seems to know why. It's time they put some serious work in that, or kill the catalog and tell everyone to work with sessions or to move to Media Pro.
Cheers,
Peter.0 -
[quote="Christian Gruner" wrote:
Sorry guys, but You will have to be much more specific in your statements.
What is slow?
What kind of files are you working with ?
What are you doing when it is slow ?
We currently know of an issue with Tiff handling, which will be solved.
Contacting our Support will get You further than this user forum, as we 1) got a fighting chance to sit down and help You one on one, and 2) can register your issues for further tracking and prioritization.
Hello Christian
I have a support ticket 240213
in which I have specified some of my problems, specs, tests and what I believe might be one factor in this slowness.
It began with my totally new db went corrupt after I tried to downsize my catalogue in order to make it manageable as CO 10 have some problems. I then took a look at what happens when lanuching and opening a catalogue.
It seems that - beside it takes 25 seconds to open a 6000 photos catalogue, directly after opening CO begins to beach balling and locks up for another 25 seconds. This beach balling is due to a single threded Autosave action is "saving" the referenced catalogue although no disk access really occur.
My original photos are placed on a network volume which have not been mounted on my workstation. My Mac Mini quad i7 with 16GB and dual SSDs have one out of 8 cores/threads locked up 100% by the Autosave.
Why an Autosave need 24800ms to do something directly upon launch I dont know. I have not found any way of disabeling it either.
It make no difference if I have the share with originals mounted or not. I do not have anything else then .NEF and jpegs in the catalogue.
So I would believe that either disable the Autosave or multithread it. It quite obvious that a letting the whole app wait in line for a busy single thread utilizing 100% out of 800% available will cause some pretty long waiting times.
I really hope it can be solved because it's make a really nice CO 10 quite a bit neutered, so to speak. 😊0 -
I don't have Sierra on my Mac and installed 10 by accident. Now version 9 isn't recognizing my camera.
How can I get Version 9 to work again?
Running Version OS X 10.10.50 -
How did you get Yosemite to even recognize version 10's installer? I just tried it and there is a circle with a white line across it which cautions against even trying to drop it into the applications folder. So I didn't. You will have leftover hidden files which should be removed. Ask Support but you may need to remove all your preferences. 0 -
Just want to add my vote. Version 10 is really slow for me. Especially switching between pictures can take forever. Or selecting 5 pictures and showing in "Multi View" is very slow. I don't recall seeing in V9. 0 -
Hi, we're also experiencing HORRIBLE performance with CP10. We have two sets running everyday with clean sessions each morning on our Mac Pro's. With only a handful of RAW files in the session, it's painfully slow just switching between images in the browser. Once we have a few hundred images shot, it's basically unusable. This is unacceptable.
Our mac pros are :
24GB RAM
3.4GHz 6 core
AMD 3GB Fire Pro graphics0 -
Hi,
With this configuration, it should work like a lightning !! You might have something with your computer which prevents C1v10 to work right away. I work with a referenced catalog, 17,000 images. My config is just a MBP retina 15" 2.3 GHz and 16 Go RAM, GPU Nvidia GT750M 2 Go, and it works quite well, no lag time when switching from one image to an other. The only issue is when I want to make a query through a filter on all my images. Displaying my 17,000 images takes about 30 seconds.0 -
It helps Phase One (and our user community) if we provide measured hang intervals in trouble reports and our postings.
Here is my AppleScript that monitors Capture One and logs the hang duration in the Script Editor log. Notifications also show the hang duration, this is useful because the screen captures do NOT show the beachball.
This is considerably improved since my last posted version.
-- AppleScript to detect and time Capture One Pro 10 hangs for the purpose of screen capture and feedback to Phase One.
-- Eric Valk January 2017 Version 0.5.1
-- Run the script running using Script Editor, enable the log window first.
-- Has a loop that mimics the idle loop. The initialisation section is in the main part before the idle-mimic loop is called.
-- Hangs will be displayed as notifications (make sure you have notifications enabled) and the final duration is displayed as an Alert, and also logged
-- Logging occurs in the Script Editor log
global voiceonfinish
global debugNotLevel
global debuglevel
global theAppName
global FinalAlertDuration
global longIntervalTime
global shortIntervalTime
global shortWaitTime
global intervalScale
global dispTime
global dispCount
global dispRoundingFact
global detectedDispCtr
global nextDispCtr
global hang_Ctr
global isHung
global wasHung
global COPpid
global startTime
set voiceonfinish to true -- if true, a voice says finished when the hang ends
set debugNotLevel to 0 -- 0: Standard Level 1:On Initialisation 3:GetProcess Info
set debugLogLevel to 0 -- 0: Standard Level 1: On Initialisation & Counts 2: On Notifications 3: More 4: Even More
set theAppName to "Capture One 10"
if (debugNotLevel ≥ 1) then tell application "Script Editor" to display notification "COP Hang Detector Starting"
log "COP Hang Detector Starting"
set FinalAlertDuration to 15 -- time before the alert when COP disappears times out and disappears
set longIntervalTime to 10 -- the time to wait if Capture OnePro is not running
set scriptRunTime to 0.062 -- estimated time it takes the idle loop to run
set shortIntervalTime to 0.5 as real -- the interval time if Capture OnePro is running
set shortWaitTime to shortIntervalTime - scriptRunTime
set intervalScale to 1 / shortIntervalTime -- the divisor needed to scale the output
set dispTime to 3 as real -- the time between notifications
set dispCount to (round (dispTime / shortIntervalTime) rounding to nearest) -- the number of intervals between notifications
set dispRoundingFact to 10.0 -- sets the number of digits in the display notifications
set detectedDispCtr to 1 --The hang_Ctr value for the display notification that a hang is detected
set nextDispCtr to dispCount --The hang_Ctr value for the next display notification
set hang_Ctr to 0 as real -- counts the number of intervals COP is hung
set isHung to false -- state this interval
set wasHung to false -- state last interval
set COPpid to {} -- PID of the Capture One Pro 10 process
set startTime to get time of (get current date)
--set detectedDispCtr to round (nextDispCtr - (0.9 / shortIntervalTime)) rounding down
if (debugLogLevel ≥ 1) then
log "voiceonfinish " & voiceonfinish
log "debugNotLevel " & debugNotLevel
log "debugLogLevel " & debugLogLevel
log "theAppName " & theAppName
log "FinalAlertDuration " & FinalAlertDuration
log "longIntervalTime " & longIntervalTime
log "shortIntervalTime " & shortIntervalTime
log "shortWaitTime " & shortWaitTime
log "intervalScale " & intervalScale
log "dispTime " & dispTime
log "dispCount " & dispCount
log "dispRoundingFact " & dispRoundingFact
log "detectedDispCtr " & detectedDispCtr
log "nextDispCtr " & nextDispCtr
log "hang_Ctr " & hang_Ctr
log "isHung " & isHung
log "wasHung " & wasHung
log "COPpid " & COPpid
log "startTime " & startTime
end if
repeat while true
set delayTime to idlemimic()
delay delayTime
end repeat
on idlemimic()
global voiceonfinish
global debugNotLevel
global debugLogLevel
global theAppName
global FinalAlertDuration
global longIntervalTime
global shortIntervalTime
global shortWaitTime
global intervalScale
global dispTime
global dispCount
global dispRoundingFact
global detectedDispCtr
global nextDispCtr
global hang_Ctr
global isHung
global wasHung
global COPpid
global startTime
set wasHung to isHung
if COPpid = {} then set COPpid to getCOPprocess()
if COPpid = {} then return longIntervalTime -- Capture One Pro 10 is not active
try
tell current application to set {pcpu, state} to words 1 thru 2 of paragraph 2 of (do shell script "ps -o %cpu,state " & quoted form of COPpid & " ")
on error errText number errNum -- Capture One Pro 10 is no longer active, process has been terminated
if (debugNotLevel ≥ 3) then tell application "Script Editor" to display notification "COP Hang couldn't get state of " & V & ": PID: " & COPpid & " " & errText & " " & errNum
set COPpid to {}
tell application "Script Editor"
beep 2
display alert ¬
"Do you wish to continue with COP Hang Detector?" buttons {"Continue", "Quit"} as warning ¬
default button "Continue" cancel button "Quit" giving up after FinalAlertDuration
return longIntervalTime
end tell
end try
set pcpu to pcpu as real
if (state = "R") and (pcpu > 96) then -- COP 10 returns "R" and CPU > about 96 when it is hung
if not wasHung then
set startTime to get time of (get current date)
tell application "System Events"
if not (exists process "Script Editor") then activate application "Script Editor"
if visible of process theAppName then set frontmost of process theAppName to true
end tell
end if
set hang_Ctr to hang_Ctr + 1
set isHung to true
if (hang_Ctr = detectedDispCtr) then
tell application "Script Editor" to display notification "COP hang has started"
tell application "System Events" to if visible of process theAppName then set frontmost of process theAppName to true
if (debugLogLevel ≥ 2) then log "COP hang has started"
end if
if (debugLogLevel ≥ 4) then log "hang_Ctr " & hang_Ctr & " state " & state & " % CPU " & pcpu
if hang_Ctr ≥ nextDispCtr then
set nextDispCtr to hang_Ctr + dispCount
set disphungtime to (round (hang_Ctr / intervalScale * dispRoundingFact) rounding to nearest) / dispRoundingFact
tell application "Script Editor" to display notification "COP has hung for " & disphungtime & " seconds"
tell application "System Events" to if visible of process theAppName then set frontmost of process theAppName to true
if (debugLogLevel ≥ 3) then log "COP is hung for " & disphungtime & " seconds"
end if
else
if wasHung and ((hang_Ctr * shortIntervalTime) > 2.1) and (hang_Ctr > 1) then -- don't log junk measurements
set stopTime to get time of (get current date)
if stopTime < startTime then set startTime to startTime - 86400 -- the hang started yesterday and ended today
set disphungtime to stopTime - startTime
tell application "Script Editor" to display notification "COP was hung for " & disphungtime & " seconds" sound name "submarine"
tell application "System Events" to if visible of process theAppName then set frontmost of process theAppName to true
if voiceonfinish then say "Finished!"
log "COP was hung for " & disphungtime & " seconds " & (get current date)
if (debugLogLevel ≥ 1) then log "Counts: " & hang_Ctr & " On Interval " & shortIntervalTime & " seconds"
end if
if (debugLogLevel ≥ 4) and wasHung then log "Exit on: hang_Ctr " & hang_Ctr & " state " & state & " % CPU " & pcpu
set isHung to false
set hang_Ctr to 0
set nextDispCtr to dispCount -- so that the first full display occurs on an integer second
end if
return shortWaitTime
end idlemimic
on getCOPprocess()
global debugNotLevel
global debugLogLevel
global theAppName
try
tell application "System Events" to set COP10process to unix id of process theAppName
set COP10process to COP10process as Unicode text
if (debugLogLevel ≥ 4) then tell application "Script Editor" to log "COP Hang found COP Process " & COP10process
return COP10process
on error errText number errNum
if (debugLogLevel ≥ 4) then tell application "Script Editor" to log "COP Hang not finding COP Process " & errText & " " & errNum
return {}
end try
end getCOPprocess0 -
I'm also having performance issues since upgrading to C1 10.0.2. Image previews take 2-3 seconds and waiting for adjustments take time as well. Using a wacom is not as fun either. I created a new Catalog for 2017 and I only have 870 images so far so the catalog should fly this early in the year. I currently run a Mac Pro running Sierra 3.5 Ghz 6-core with 64 GB of RAM.
I hope this is addressed soon0 -
I just can't comprehend how C1P can be so frickin slow. It's like it's ignoring it's own preview files and generating a display image from RAW every time you pick an image in the browser. It's maddening. How difficult can it be to load a preview image in the viewer? I can literally click a photo on my drive and have Preview open and render it on my Mac faster than I can advance through images in C1Pro. FFS Phase One... do any of you guys actually do your RAW processing in this app?
And that's when you're using a single display. God forbid if you want to have your viewer and tools on one display and the browser on the 2nd display. I can literally count to 5 between each image when using the arrow keys to advance from one image to the next. It's astonishing on a modern computer (and I have both a loaded 2013 Mac Pro and a 2016 MacBook Pro) and C1P is horrible on both.
And v10 has to be the worst release in the last few years. Buggy and slower than any release that came before it. Heads need to roll at Phase One.0 -
[quote="NNN636111969638062477" wrote:
Hi, we're also experiencing HORRIBLE performance with CP10. We have two sets running everyday with clean sessions each morning on our Mac Pro's. With only a handful of RAW files in the session, it's painfully slow just switching between images in the browser. Once we have a few hundred images shot, it's basically unusable. This is unacceptable.
Our mac pros are :
24GB RAM
3.4GHz 6 core
AMD 3GB Fire Pro graphics
Found a fix for the laggy browsing. Support pointed me towards this process: https://www.phaseone.com/en/Search/Arti ... nguageid=1
Browsing is just as fast as 9.3 now.0 -
What do you mean ? Uninstall Capture One ? Because the link points to uninstallation ❓ 0 -
[quote="tenmangu81" wrote:
What do you mean ? Uninstall Capture One ? Because the link points to uninstallation ❓
yes, sorry. To clarify, do this complete uninstall/reinstall process. For whatever reason, CO10 wasn't playing nice with previous versions caches and preferences. It totally fixed our browsing issues.0 -
I had a similar suggestion from support, and indeed it does seem to have improved some issues (such as recurring OpenCL failures).
However, the "Select All Images" with a large catalogue hang persists. For me, this hang occurs once on first selecting the collection and the delay is roughly proportional to the number of images (about 30s with 10k images in the collection). I do not know if it affects all Macs, but I sent support a trace file that effectively showed that C010 was seemingly refreshing the entire UI display each time it touched something in (presumably) every single image in the collection.
The only work-around for this is to limit the number of photographs in any catalogue/collection. Support recommended a maximum of 400 images per. Forum rules prevent me from expressing exactly what I feel about this - but I updated my online review of CO10 to recommend that users do not upgrade until this issue is resolved.0 -
The all images but is known since beta testing and has been re-submitted within the first days of V10 release. According to feedback from support it did not have highest priority as there also have been bugs which messed up with the data bases and this bug is just slowing down (and thereby makes C1P unusable).
I recently received feedback from one of the manager that it is in the works but far from being easy to be solved. My conclusion is that by re-writing most of the TIFF-handling code as well as the speed on browsing from image to image PhaseOne has introduced a new severe issue with the data base as well as re-introduced bugs with both GPU memory and CPU memory release.
What bothers me is that the difference in speed between V9 and V10 which is close to a factor of 10 could easily be reduced to a factor of 3 just by getting rid of the idle times ("CaptureOne not responding" and no activity on network, memory, SSD,..).
Even worse is that support is not looking into new support cases or providing any answer at all.
Frank0 -
I have given up also. I also bought Media Pro. Its great, but the fact it can not keep up with the edits in C1 makes it of way less value to me. If I have to cook JPGS to see them in my DAM, then there are may products that can work this way. Its been almost 3 months and C1v10 not supported.
So this means C1 itself has to function as DAM and EDITOR if the PhaseOne ecosystem is to be of value. And we all know that C1 is not working as a DAM.
My 2 year struggle with a replacement for Aperature and my hopes for C1 to be that tool has come to an end. One has to know when to pull the trigger. I have lost so much time trying to work with C1 that it has caused me to re-evaluate some things.
1. Do I NEED the BEST editor out there (answer is not really - most are quite good)
2. Do I need to catalog - (Yes, just too many files to find them by folder structure alone)
3. Do I want the same tool to be the DAM & Editor (Yes, I have tried both ways now and I think this part Aperature got right)
4. Do I want the DAM to do some lifting for me (Yes, face rec and Location tagging and other AI's save time)
5. Do I need social integration (No, but nice if there)
6. Do I need OS integration (No, but I have to say with apple its VERY NICE if you have it)
7. Do I want the DAM to be FAST (Yes, and C1 is NOT THAT BY FAR)
8. Do I need Stable DAM not Corrupting itself when a butterfly goes by (YES, C1 has caused me issues - Seems others have it worse)
Armed with my NEEDS list, augmented with my experiences with many different packages and approaches and valuing my time I have decided to go back to Photos (its been improving) with 2 different extensions (actually both open into the full program and save back to Photos). At times for some images Photos is too dumbed down.
I have resigned to the fact that the BEST is not worth the amount of TIME I have to dedicate to achieve it. TIME is limited by my lifespan. Its finite. Organizing my DAM is not worthy of my life. Its necessary to do but I want as little time dedicated to it as required. Having a 10% better quality picture in C1 is not worth what I have to sacrifice to get it.
There is a time when BEST may not really be BEST. It depends on what value you place on your time.
If you can think of one thing you rather be doing than organizing your DAM then you will understand what im saying.
If I truly believed C1 would get to meeting my real needs I would stick it out, but I dont believe they "want to" and less convinced the "can".0 -
Hi,
According to your requirements, I think Lightroom could be a good compromise for you.
As far as I am concerned, I worked with Lightroom from the beginning of this software, the catalog and DAM are very good, the processing is correct.
I have given up with Lightroom only two years ago, because I needed a better processing and rendering. And the DAM and catalog, which are awful up to now, are nevertheless satisfactory for my needs.
Cheers,
Robert0 -
[quote="Mark BCN" wrote:
I had a similar suggestion from support, and indeed it does seem to have improved some issues (such as recurring OpenCL failures).
However, the "Select All Images" with a large catalogue hang persists. For me, this hang occurs once on first selecting the collection and the delay is roughly proportional to the number of images (about 30s with 10k images in the collection). I do not know if it affects all Macs, but I sent support a trace file that effectively showed that C010 was seemingly refreshing the entire UI display each time it touched something in (presumably) every single image in the collection.
The only work-around for this is to limit the number of photographs in any catalogue/collection. Support recommended a maximum of 400 images per. Forum rules prevent me from expressing exactly what I feel about this - but I updated my online review of CO10 to recommend that users do not upgrade until this issue is resolved.
Did you mistype?? Surely they didn't say a maximum of 400. Did you mean 4000?0 -
[quote="Mark BCN" wrote:
I....
However, the "Select All Images" with a large catalogue hang persists. For me, this hang occurs once on first selecting the collection and the delay is roughly proportional to the number of images (about 30s with 10k images in the collection). I do not know if it affects all Macs, but I sent support a trace file that effectively showed that C010 was seemingly refreshing the entire UI display each time it touched something in (presumably) every single image in the collection.
....
Hi Mark, I am curious in debugging ny similar issues.
What indications in the trace were highlighted as indicating refreshing of every single image in the UI? I get a visual indication of this, but I don't know how to connect it with the trace.0 -
It's amazing how effectively these single threaded beach balling freezes kills ones creative interest as soon as you sit down to work on some photos.
I launch it. Watch it. It spins. I watch it. It spins. I loose interest.
I work some. I save. I quit. I pray that the catalog didn't get corrupt again.
I hope this get sorted soon because I'm considering trashing this and give it away.
Yes I know it's late and I should get some sleep.0 -
[quote="atenolol" wrote:
It's amazing how effectively these single threaded beach balling freezes kills ones creative interest as soon as you sit down to work on some photos.
I launch it. Watch it. It spins. I watch it. It spins. I loose interest.
I work some. I save. I quit. I pray that the catalog didn't get corrupt again.
I hope this get sorted soon because I'm considering trashing this and give it away.
Yes I know it's late and I should get some sleep.
I took up drinking. It tends to smooth over the rough edges of a bad C1 session.
Once I see the beachball, I'll pour myself a little something. Then go to youtube and watch videos. Every now and then, I'll just check back and see how the ole catalog is doing. Once she's done having an emotional breakdown, i'll go back and edit.
Works for me.0 -
[quote="Jimmy D Uptain" wrote:
Did you mistype?? Surely they didn't say a maximum of 400. Did you mean 4000?
No, they said four hundred. It is difficult to know if this is genuine advice or simply someone reporting things from a crib sheet. Something has changed with CO support in the last year (outsourcing?!), and initial support requests for the Mac are now met with generic but PC specific answers (such references to the C: drive).[quote="Eric Nepean" wrote:
Hi Mark, I am curious in debugging ny similar issues.
What indications in the trace were highlighted as indicating refreshing of every single image in the UI? I get a visual indication of this, but I don't know how to connect it with the trace.
There are two ways to get a trace when software is busy on a Mac. If you open "Activity Monitor" (from /Applications/Utilities) then double-click on an application/process name you get a dialog with details of that process. There is also a "Sample" button, which if clicked will give an indication of what the application is doing (try it on Activity Monitor itself, for example).
And if you have Xcode installed, you can use Instruments to perform a whole range of diagnostics on application code. I sent a trace during a "All Images" hang that showed the UI being refreshed as quickly as possible over and over again, so much that it completely dominated the (single threaded) CPU time.
I understand that it is difficult and time-consuming to develop and debug performance issues with OpenCL, which inevitably means lots of very hardware specific problems. But generic database and UI issues like this are pretty inexcusable given the that the whole point of SQL should be the robustness and performance of database queries (and which is clearly demonstrated by competing software, such as Lightroom).
I would be a lot less frustrated and critical if performance had not been one of the few tangible benefits that was promised for an upgrade from CO9 - which was faster in practise with larger catalogues. Unfortunately, there is no easy way revert back to the CO9 catalogue format.0 -
Just to add not a lot to the discussion, I'm having the same issues as most of you.
New 2016 13" MacBook Pro (i7, 16gb RAM, blah blah, top spec).
C1v9. All is good and nice. Happy days.
C1v10. Previews load very slowly, even bring up a beachball. Cropping is even slower when applying, guaranteed beachball each time. Copying adjustments also creates a freeze.
Tried with new small sized catalogues and Sessions (max of 40 images) as a test. Makes no difference.
Also, I have to disable OpenCL. Having that enabled was like working in thick sludge. Everything was super slow. Processing to outputs was painful.
I want to love and use C1v10 I really do. I want to give them all the monies, but alas right now it's way too slow.0 -
Just to add to this in the hopes of helping to identify the issue, I have the top of the line mid 2014 MBP with SSD. Trying to simply move from one thumbnail to the next in the browser takes about 7 seconds before the image is ready in the viewer. The CPU fans go crazy.
Fingers crossed this will get fixed soon!0 -
[quote="NNN636228159387558615" wrote:
Just to add to this in the hopes of helping to identify the issue, I have the top of the line mid 2014 MBP with SSD. Trying to simply move from one thumbnail to the next in the browser takes about 7 seconds before the image is ready in the viewer. The CPU fans go crazy.
Fingers crossed this will get fixed soon!
They happily accepted our money - Now it's their time to make us happy.0
Post is closed for comments.
Comments
120 comments