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

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

CO Slow to create proxies

Jim MSP
I cannot understand why the latest version (6.3) is so slow on "startup".
I just loaded 620 new shots from a Canon 60D into a new file folder.
I opened CO, and pointed it at the folder to open the shots so I could start my editing.

CO shows all the images in the filmstrip mode within a few seconds - reasonable.

However, it takes over 24 minutes for it to "generate" all the proxies. Given the relatively decent speed of my pc, this seems absurdly long.

As I have experienced crashes and hangups before with CO, I am very reluctant to ask CO to do anything to any file until all the proxies are generated.

So two questions
1. Is this time about what others see for an equal number of files?
2. If I start in on editing the first few files (keep or toss) will I run into issues if CO is still working on proxies?

Thanks,

Jim
0

コメント

10件のコメント

日付 投票
  • nggalai
    Hi Jim,

    I don’t see longish proxy generating, but exceedingly large amounts of “Loading Metadataâ€. Even if the contents of a folder aren’t changed, no new Proxies need to be generated or Metadata synced it takes a couple of minutes for this step alone, with 100 images inside a folder. I’ve had a folder with 2000 images block Capture One with this metadata thing for a good half-hour at one point – no Proxies were generated during that time.

    (MacBook Pro, i7 2.6GHz, 8GiB RAM, SSD work drive.)

    If this behaviour is typical for PCs, too, it’s possible part of this 24-minutes-wait you mention is due to metadata synching. Have you tried to disable all metadata sync settings in Capture One? Does this improve generation times?

    Cheers,
    -Sascha
    0
  • Keith Reeder
    I'm with you on this, Jim - similarly-specced machine, and proxy building takes an age, with no conversions being possible until Cap One is done.

    It's been like this for me since before 6.3, and it's a pain in the butt - often enough for me to to reach for another converter instead of Cap One.

    (Metadata synching not enabled, Sascha).

    I wonder if Phase One might take a leaf from Lightroom's book - it takes Lr a while to render lots of 1 to 1 previews (which is more or less analogous to Cap One's proxy building), but it will "multi thread" preview building and conversion processing.

    In other words Lr can do both at the same time, unlike Cap One.

    Big positive mark to Lr there...
    0
  • Permanently deleted user
    User response: speed of loading new files IS system dependent....a faster computer does this faster. Just timed 150 1DsMk3 files on my fastest computer, loaded on a local SSD...took 2.5 min, so extrapolating that to 10 minutes for 600 files...or twice as fast. Midrange 17, 24 gigs of Ram, Nvidia 480, SSDs....my PS machine.

    However, I typically work across a network on an older generation QuadCore CPU, 8gigs ram, Nvidia 240...loading the files on/from a NAS...so my typical times are very similar to yours. CONe has to read/write the COS/COP files...so this can take a while (compare to rendering a video on the front end of the process), so my workflow is to load the files and do something else while they process...COne is much better to work with once the loading process is done. Once loaded, the files open instantaneously on a local drive...or take a few seconds longer across the network...so this is a one-time hit.
    0
  • Keith Reeder
    [quote="John4" wrote:
    so this is a one-time hit.

    It is, and there are ways to manage it, like breaking a large folder into a few smaller ones.

    Nevertheless, I'd like to see proxy building and conversion processing being handled in parallel - surely that'd be doable on most machines these days without them bursting into flames...
    0
  • Jim MSP
    [quote="John4" wrote:
    User response: speed of loading new files IS system dependent....a faster computer does this faster. .......so this is a one-time hit.


    John - I understand this. However, I believe it is way too long. I was not asking CO to do anything during this time, no applied styles, etc. Just "get them ready" for processing and tagging.
    I have put up with this since v6.0 and for my shoots that only consisted of 100-200 shots or so. But this weekend, I spent the day shooting birds in flight (bif) and my hit rate is not super high, especially with hawks. Anyway, all I want to do to start with is tag and toss the poor ones (probably 300 of them).
    24 minutes is absurd imo for my machine.

    As a test tonight, I asked Lightroom to sync my main set of files. As I hadn't sync'ed LR for a few days, there were 1200 plus files that it needed to import. It took it all of 4 minutes. I can live with this.
    That means I am comparing performance of 2 min vs 24 min for 600 files.

    Previously, I used LR for the initial sort on a large number of files simply because of this time issue. I am trying to stick with CO (and Media Pro) but I hit the frustration point last night.


    Sasha - There is no auto loading or syncing of metadata holding me up. I keep the activity window open all the time.
    CO does get hung up at times showing "auto loading metadata" activity for the last file it has looked at, but this does not seem to effect performance. I can go to another set of files, and back again and the little wheel stops spinning, and the activity shows nothing is happening. I think they have a counter issue.
    0
  • Permanently deleted user
    [quote="Jim MSP" wrote:
    As a test tonight, I asked Lightroom to sync my main set of files. As I hadn't sync'ed LR for a few days, there were 1200 plus files that it needed to import. It took it all of 4 minutes. I can live with this.
    That means I am comparing performance of 2 min vs 24 min for 600....


    sorry, I was just confirming the time you were experiencing as normal. I KNOW LR is faster importing files. I use COne because it is profile aware and works in the manner it does....and I like the quality of the files. As I said, I simply allow files to load before working, although I can certainly start reviewing and rating before those are finished without crashing, it's not as responsive. It is just more pleasant to work once the process is done, so that's my choice.

    Yes, I'd like it to be faster...but not in the manner of LR and it's workflow.
    0
  • Jim MSP
    John,

    Thanks. I basically agree, which is why I stick with CO. I'd like to see some improvement in the speed, however.
    As an aside, I also find Media Pro too slow on rendering files, making the light table all but useless.

    Jim
    0
  • Permanently deleted user
    The sad part is that C1 3.x allowed you to work and build previews at the same time but versions since then don't allow it.
    0
  • Keith Reeder
    Yep, it's a weird and - literally - counter-productive step.
    0
  • Jim MSP
    [quote="dan122" wrote:
    The sad part is that C1 3.x allowed you to work and build previews at the same time but versions since then don't allow it.


    I agree. I could put up with the longer time if I could be assured that I could start viewing and tagging the files as CO worked on the subsequent ones -- without crashing.
    0

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