Capture One 11 keeps generating previews
First time I created a catalog and imported images, capture one generated previews for the images. I let it finish and everything is all good. After switching to another catalog and going back, it generated previews again. This has happened several several times after I switching between different catalogs. Please bear in mind that I have LET IT FINISH GENERATING previews for the whole catalog. Why does it keep generating previews even after it's already done so multiple times?
0
-
Best option here is to create a tech support case (via the link in my profile) and send us your log files, which can be generated via Scripts > File Packager. 0 -
[quote="NNN636514531318806334" wrote:
First time I created a catalog and imported images, capture one generated previews for the images. I let it finish and everything is all good. After switching to another catalog and going back, it generated previews again. This has happened several several times after I switching between different catalogs. Please bear in mind that I have LET IT FINISH GENERATING previews for the whole catalog. Why does it keep generating previews even after it's already done so multiple times?
To make sure, you're 100% NOT talking about thumbnails/loading up the image list; and it does indeed say "Generating x previews" with a progress bar, right?
I bring this up as there's a directory listing behaviour discussed at length in the Windows section that is often mistakenly associated with 'preview generation'.
In Windows again, there was a major preview generation and memory hole issue between versions 10.1 and 10.2.1 which, in my experience thus far, is not present in 11.x.x.0 -
I'm having the same issue with sessions using 11.1.1
Moving files between folders or renaming files is causing it to generate previews again.
Very strange.
Did you get any solutions from tech support?0 -
Me too. Its just happened to me after switching catalogs. In my case, it takes about 9 hours to complete. 0 -
Happening to me to (I posted another thread, hadn't seen this one).
Mac OS10.11.6; C1 11.1; session (NOT catalog); session on external HD attached via USB3.
I shoot lifestyle, so Capture folder can easily have 5K of image files, but I'm trying to pull one single file for post work. To say this is annoying / frustrating is an understatement.0 -
[quote="NNN634579324681874960" wrote:
Happening to me to (I posted another thread, hadn't seen this one).
Mac OS10.11.6; C1 11.1; session (NOT catalog); session on external HD attached via USB3.
I shoot lifestyle, so Capture folder can easily have 5K of image files, but I'm trying to pull one single file for post work. To say this is annoying / frustrating is an understatement.
It may be worth mentioning here that you can apply a filter activity while the session startup process is in progress.
Now if you have not had an opportunity to group or categorise the images somehow before seeking the one to work on that might be a problem BUT, presumably, if you can recognise which one you want you may have some information about it. The file name for example. Or some idea of when it was shot - an approximate time of day for example.
This you could specify the file if you know the name (or part of the name) for example. Or use the estimated time of the shot to get closer to the image you want faster.
HTH.
Grant0 -
There has to be abetter way than to essentially try to hack and fool the system. Plus, of course, C1 is what we use to look at to choose the images we need to work on. Something is going on and I can only think there's a better solution. 0 -
[quote="NNN634579324681874960" wrote:
There has to be abetter way than to essentially try to hack and fool the system. Plus, of course, C1 is what we use to look at to choose the images we need to work on. Something is going on and I can only think there's a better solution.
Why are you trying to hack and fool the system?
Just use the facilities available that help you while C1 does what it does to try and set things up for fast processing interactions in the background.
Grant0
Post is closed for comments.
Comments
8 comments