Zum Hauptinhalt gehen

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

Speed up orange pie wheel loading in Catalog?

Kommentare

6 Kommentare

  • SFA
    Sessions would be perfect for what you describe.

    Why carry the processing burden of a whole catalogue for a 20 shot session?

    After processing in the session just import the completed session (or the parts of it you want) into the catalogue.

    How often do you open and close the catalogue?


    Grant
    0
  • IanS
    [quote="NNN636227271211111350" wrote:
    Seems like this is only a problem in the windows version which is unfortunate. When I load my catalog I get an orange pie Icon at the top that slowly loads, I think its finding all the photos in the catalog again, like its not indexed properly.

    My catalog is on an SSD, I have an i5-8600k, 16gb ram, Radeon 570 gpu with hardware acceleration enabled. Shouldnt be a PC spec issue.

    Super disappointing because the editing abilities of capture one blow Lightroom out of the water, but this might be a dealbreaker for me. I know I could use sessions but the way I shoot which could be sometimes only 20 shots a session, wouldn't work well with sessions.

    Would love any tips on how to speed this up!

    Thanks!


    Actually sessions sound perfect for a 20 shot shoot 😊

    Sessions can be later imported into an archive catalogue if you want.

    I used LR from V1 and naturally started with catalogues with C1Pro - how else can you work? 😊

    These days I work in sessions with an archive catalogue.

    Session work coming from LR can be initially confusing but they offer a lot of flexibility.

    Take a look at this thread on DPReview

    Session Organisation
    https://www.dpreview.com/forums/thread/4355557


    and the Phaseone Tutorial:

    Catalogs and Sessions | Webinar | Capture One 12
    https://www.youtube.com/watch?v=Voz5vX-YOaw

    Ian
    0
  • NNN636227271211111350
    [quote="IanS" wrote:
    [quote="NNN636227271211111350" wrote:
    Seems like this is only a problem in the windows version which is unfortunate. When I load my catalog I get an orange pie Icon at the top that slowly loads, I think its finding all the photos in the catalog again, like its not indexed properly.

    My catalog is on an SSD, I have an i5-8600k, 16gb ram, Radeon 570 gpu with hardware acceleration enabled. Shouldnt be a PC spec issue.

    Super disappointing because the editing abilities of capture one blow Lightroom out of the water, but this might be a dealbreaker for me. I know I could use sessions but the way I shoot which could be sometimes only 20 shots a session, wouldn't work well with sessions.

    Would love any tips on how to speed this up!

    Thanks!


    Actually sessions sound perfect for a 20 shot shoot 😊

    Sessions can be later imported into an archive catalogue if you want.

    I used LR from V1 and naturally started with catalogues with C1Pro - how else can you work? 😊

    These days I work in sessions with an archive catalogue.

    Session work coming from LR can be initially confusing but they offer a lot of flexibility.

    Take a look at this thread on DPReview

    Session Organisation
    https://www.dpreview.com/forums/thread/4355557


    and the Phaseone Tutorial:

    Catalogs and Sessions | Webinar | Capture One 12
    https://www.youtube.com/watch?v=Voz5vX-YOaw

    Ian


    Do you have any more information about an archive catalog? How can I add sessions to a catalog?

    Sounds like a good way to move forward
    0
  • Ian Wilson
    Moderator
    Top Commenter
    Do you have any more information about an archive catalog? How can I add sessions to a catalog?


    There is more than one way.

    (1) What I usually do is only add to my catalog the "keepers" in my session - generally the contents of the Selects folder. So you can use the Import function in the catalog, import from the Selects folder, and make sure you check the option to include existing adjustments. You have a choice of importing the images into the catalog database while leaving the files in their existing location, or actually putting them inside the catalog. (To my mind the second one is only a good idea for a fairly small catalog - otherwise you end up with a very large catalog file.)

    (2) Or you can use File>Import Session... That will add all the images in all the session folders (Capture, Selects, Output...) to the catalog. It doesn't offer the option to move the images into the catalog.

    (3) But you can import all the images in the session into the catalog itself another way: in the import dialog you can select the session folder as the source. It probably contains no images itself, but if you check the box to include subfolders, you get the contents of all the subfolders.

    In my view (1) is the most useful option.

    Ian
    0
  • xplatinum
    While sessions are best for him, this "bug" needs to be addressed once and for all.

    [The Capture One forum has migrated to a new platform, as a result all links to Capture One related postsstopped working and have been removed]
    [The Capture One forum has migrated to a new platform, as a result all links to Capture One related postsstopped working and have been removed]
    [The Capture One forum has migrated to a new platform, as a result all links to Capture One related postsstopped working and have been removed]
    0
  • SFA
    I think you will find it is pre-loading memory, presumably on the basis that whatever one has been doing since first opening the session or catalogue has required some re-allocation of memory to its needs and so has removed any initial load of the 6k+ images it started with.

    Now one could argue that pre-loading the entire set is unnecessary for one's purposes but for some things it might be exactly the right way to work to provide a fast work flow after a initial load so that moving from one image to another or applying edits to a large batch of images can progress quickly and the results, at any level of display, are rapidly available.

    In may experience (as a sessions user) on my(old) hardware the load speed is not an issue for my purposes. I also tend to keep 'live' sessions (i.e. the ones I am working on) open and the PC running rather than shutting it down frequently wherever possible. Hibernating is fine of course.

    The other option in terms of editing interface design choice is to load minimal data as quickly as possible up front and then read in the rest of the data, backgrounded where possible to give the impression of instant speed, on user demand. Smart use of such an approach can, for many users, make things look extremely fast. But is seems to depend on what one is doing.

    I think for any application at all it's not too difficult (especially if forums exist) to find people who will praise the speed of Product A compared to Product B on their machine and an equal number who observe the exact opposite for their installation.

    In some ways I suppose it would be nice to offer users the choice of approach so that they could set things up for their own preference but that would mean offering multiple and potentially options with multiple set of code routines to support. Probably not an ideal option for the developers and maybe not for a lot of possibly confused users either.

    Just my opinion based on my experiences and needs.

    I full appreciate that others may have different needs and so different experiences and opinions.


    Grant
    0

Post ist für Kommentare geschlossen.