メインコンテンツへスキップ

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

New user. How do I stop generating previews?

Permanently deleted user
I just converted from an Aperture referenced library (took almost 2 days to import 91,000 files) and now I get an Activity window that shows "Generated X out of Y previews - About Z time left." When I click on an album, the number of previews remaining increases, but the number of completed previews never goes up. Oh, and I can't do any editing while this is happening—clicking on an image will display that image (if a preview has been generated), but it will not render a full resolution image at all.

When I started importing the Aperture library, the number of completed previews went to 5 (yes, one digit) and never increased for the ~40 hours of the import. The number of remaining previews kept climbing to the point where it said there were over 300,000 hours remaining. Quitting the app doesn't help and, in fact, I need to Force Quit the app before being able to re-launch and get the same results with the preview generation. The only difference is the app will launch into the previously open folder/album and complete one or two previews before settling into a whole bunch of stagnation.

Is there any way of telling what's going on to cause this problem? Is there any way of forcing the app to stop generating previews during this process? It'd be really nice if I could use my new $300 software.

EDIT: By opening into the last-used folder/album, I was able to get the app to generate previews for the images within that folder and it worked. I have since opened additional folders with various file types and the app doesn't seem to be choking on any given file type in the library, so there must be some corrupt files that are causing the app to come to a grinding halt when it attempts to generate previews for those images. I'd still like to know if there is a way for me to stop the preview generation if/when I have this problem again as it's only a matter of time before I get to a folder that contains a bad file.

Anyway, I've been able to play with a few images and do some processing. Now I need to figure out the rest of the features. Right off the bat I can say that Aperture was much more intuitive, but Capture One is probably a lot more powerful.
0

コメント

10件のコメント

日付 投票
  • David Butterworth
    I'm also a new user and moved over from Aperture. In my case, the importation of the Aperture Library was straightforward and listed my Aperture Projects in the right order. On opening Capture One this evening, the Aperture import seems to have disappeared and Capture One is now generating previews and has been for the last hour or so. I have really struggled with the import of new images from e.g. an SD card and can't figure out how to get them into a catalogue that makes sense - ideally I would like to import the contents of an SD card to a catalogue named with the subject matter, e.g. "Womad festival" - I can't however understand how one can create a catalogue located on my Macbook Pro but have the images on a separate hard drive....and I agree Aperture is much more intuitive. If I discover the answer re "previews" I'll post on here.
    0
  • PhaseoneUser55657
    I don't think you are going to get away from the the generation of the previews. That is how CO works, it uses the previews for what you are working on, and only looks at the raw's when it needs to generate some output. So the previews should generate in the background, and if you click on a image that you want to work on, it will jump that preview to the top of the list and get you a correct rendering.

    YES generating previews are going to take a very long time. I am a little loss why people do not understand that, you take X number of years (thousands) of photos from Aperture, and bring them over to CO. CO is going to take time, just like if you were to import that many images back into Aperture in one GO.

    Ok, "David Butterworth" not sure what you want to do, do you want to create a whole new catalog or just add an new album to an existing one? Do you want them managed or referenced.

    If you want a Catalog with referenced files, use what ever tools you want to copy the images off the SDCard, onto the external hard drive, with what ever directory structure you want, and with what ever naming convention you want. Start CO, create a new catalog, then select import, in the dialog box navigate to where the files are. Then make sure you have "Import to " set to "Current Location". Click Import, and it will import and create the previews as it goes.

    Robert
    0
  • David Butterworth
    Thanks Robert - What I want to do is create a catalog for each shoot and place that catalogue on the Macbook which has a SSD and to have the images themselves located on a separate hard drive since there's not enough space on the SSD - since writing this, I think I've figured it out - will give it a try and see if it's OK in which case, thanks for your response....but if it doesn't work I'll make another post here...Dave
    0
  • SFA
    [quote="David Butterworth" wrote:
    Thanks Robert - What I want to do is create a catalog for each shoot and place that catalogue on the Macbook which has a SSD and to have the images themselves located on a separate hard drive since there's not enough space on the SSD - since writing this, I think I've figured it out - will give it a try and see if it's OK in which case, thanks for your response....but if it doesn't work I'll make another post here...Dave


    David,

    If you are keeping each shoot separate have you considered using Sessions instead of the catalog approach?

    The Session concept is something that works well for individual shoots.

    IMO.


    Grant
    0
  • PhaseoneUser55657
    I agree, if you are making catalogs for each "shoot", you are not using any features that catalogs are meant for, and like Grant said, sessions to me would be a better choice in your case.

    For you the only difference would be where the "Previews" and "modification Instructions" are kept. If you create a catalog on your SSD, the "Previews" and "instructions" would be on the SSD. With Sessions the information will be kept in a directory created where the images are stored, so on your external drive.

    So, with Catalogs, you are going to use more space on your SSD as that is where the previews are going to saved. Might save a little time during creation of the previews as the SSD should be faster, but not enough to care about.

    Robert
    0
  • SFA
    [quote="PhaseoneUser55657" wrote:


    For you the only difference would be where the "Previews" and "modification Instructions" are kept. If you create a catalog on your SSD, the "Previews" and "instructions" would be on the SSD. With Sessions the information will be kept in a directory created where the images are stored, so on your external drive.



    I find working (on a PC) with an external USB3 drive and using sessions is fine so long as the drive is kept busy enough to be spinning rather go into some sort of power saving state. Things get a little stuttery if it needs to be woken up as you might imagine.

    My machine allowed me the luxury of installing an mSata SSD in a spare slot so, the primary SSD being rather full more often than not, I now tend to use the second SSD for sessions that are still in progress or, sometimes, bringing a session back in from an external drive if tempted to re-work stuff by new functionality or client requests. If I'm just working with a few pre-identified files then I'll just open the session on the external drive.

    It's quite simple to copy entire Sessions from location to location in order to manage disk space and initial archiving.

    I sometime use another editor that is happy to sit alongside C1 using a session structure file system so any work performed with that application will also be retained, moved and backed up in the same activities.


    HTH.


    Grant
    0
  • Permanently deleted user
    I just want to reiterate my concerns. I did manage to import my entire Aperture library (minus several thousand "corrupted" files), but I'm still having trouble with preview creation. For some reason, Capture One has a lot of problems with TIFF files created with Silver Efex Pro. I have a few thousand images in TIFF format and I've created a Smart Album in CO populated with all files with "monotone" as a keyword (and almost all of these are Silver Efex TIFFs), only to have the app grind to a halt whenever it encounters a file it can't read. The app displays an Events window with a list of "proxy creation" failures. As soon as it shows this window, all background processes stop. I can highlight the failures to display the associated filenames and then move those files to the CO trash, but nothing gets me back on track until I Force Quit the app and re-launch. I can't continue to do this for every single defective file and this is especially maddening because ALL of these supposedly bad files are easily opened in Aperture or the Finder.

    Why is Capture One Pro unable to read files that are readable in other apps? It's not like these are some weird, esoteric file types.
    0
  • PhaseoneUser55657
    Capture One does not handle B&W files. (Tiff or Jpegs) They need to be RGB. So if Silver Effects wrote them out as 8/16 Bit B&W files, (i.e single channel), yes CO will not handle them.

    Now, should CO break when it comes across one, no that should be a BUG, and only way anything is going to fix it, is for you to enter a support case. (I know, even through PhaseOne, owns operates, and moderates these forums, they do not do anything with information that is released this way. YES I know it is stupid).

    Robert
    0
  • Permanently deleted user
    [quote="PhaseoneUser55657" wrote:
    Capture One does not handle B&W files. (Tiff or Jpegs) They need to be RGB. So if Silver Effects wrote them out as 8/16 Bit B&W files, (i.e single channel), yes CO will not handle them.

    Now, should CO break when it comes across one, no that should be a BUG, and only way anything is going to fix it, is for you to enter a support case. (I know, even through PhaseOne, owns operates, and moderates these forums, they do not do anything with information that is released this way. YES I know it is stupid).

    Robert


    First: Really? A $300 photography app that can't handle single-channel TIFFs? Ridiculous.

    Second: Silver Efex Pro files are merely B&W versions of whatever files it's fed through a round-trip from the host app; in this case, Aperture. Since I have Aperture set to send all round-trip files as 16-bit TIFF files (RGB), that's what comes right back to Aperture. Many of the files that CO is ingesting are the same format as the files it's choking on. I don't get it.
    0
  • Paul Steunebrink
    [quote="PDBreske" wrote:
    ...
    I don't get it.

    I can understand your confusion if you make the move from Aperture or Lightroom or similar application. These are more allround tools regarding handling file formats compared to Capture One.

    Capture One is primarily a raw conversion tool and I believe it excels in that area. It has gained a lot of additional features over the years and since it has a catalog it is competing in the Aperture/Lightroom league. However, some features are still missing while on the other hand it has some features which you won't find elsewhere.

    Confusing? Yes. It is a different animal.
    0

投稿コメントは受け付けていません。