Zum Hauptinhalt gehen

Problems upgrading catalog from 15.x to 16.3

Kommentare

57 Kommentare

  • Brian Jordan
    Moderator

    John, Capture One 16.3 builds preview images that are more efficient and about 40% smaller than previous versions. (Both metrics my own based on my experience.) As such, 16.3 will have to rebuild all previews for your catalog. Depending on your computer and catalog size, this can be kinda fast or not. Once previews are built, I find it to function faster than previous versions. But that first dance is a slow dance.

    0
  • John Friend
    Top Commenter

    Brian Jordan - Did you read what I wrote?  I set previews back to legacy.

    Also, there was no UI feedback at all that Capture One was intentionally carrying on any background processing.  No spinning starburst.  No progress window.

    Further more, the program was entirely locked up.  You couldn't select an image for viewing.  You couldn't even exit the program.  I let it sit for 4 hours and it was still locked up.

    Are you saying that this is EXPECTED behavior.  That it's doing something that takes hours and hours and hours and there's no UI feedback and the program is entirely locked up?

    I'm still in search of a way to use my existing catalog with 16.3.

    0
  • Brian Jordan
    Moderator

    John, I’m suggesting that you complete a fresh install and set that legacy catalog option before you open anything or you allow it to fully complete all activities before you change options mid-stream. I’ve worked with 3 people directly with what sounds like the same issue and this has solved the problem. Specifically, I did a clean install, set catalog options, then opened the catalog. I understood that you opened the catalog then changed it to legacy when you noticed slow response - which would have been during the preview rebuild process.

     

    Edit: All were on Mac. Shouldn’t make a difference but full disclosure. 

    Edit 2: I opened a fresh copy of their catalogs as some previews in the previously opened catalog were likely upgraded. Don’t know that for sure but just in case. 

    1
  • John Friend
    Top Commenter

    Brian Jordan

    How do I get it to stop what it's doing?  A clean install of C1 shouldn't be affecting anything - this is not a corruption of the C1 code.  This is a catalog-specific issue.  C1 16.3 does not have this issue on a brand new catalog. 

    Do you mean go back to my 15.x catalog backup and start over with that with legacy previews set BEFORE I open that 15.x catalog?

    If what you're theorizing it correct, then is a serious, serious flaw in how Capture One is handling existing catalogs with 16.3 and should at best be fixed and at worst should offer a progress dialog so that we can see what it is doing and how long it is likely to take and so we can be assured that it is actually making progress and not stuck forever.  This is creating a horrible user experience for existing users upgrading and opening their existing catalogs.  Bugs should be filed.  Developers should be fixing either the functionality or the user experience or both.

    FYI, I have an OK desktop computer (8 core 5GHz CPU, 32GB DRAM, a little older video card GeForce 1060) so whatever it's trying to do, it should be able to handle it on my computer.

    0
  • Brian Jordan
    Moderator

    No. It’s not a bug, imo. What I think I saw happen was people got impatient. While Capture One was rebuilding previews they said, “Nope. Don’t do that.” Kinda like deciding you don’t want to get wet after jumping off the diving board. In all cases and since I don’t know what all they did I just started clean. Fresh install. Set catalog options to legacy. Made a fresh copy of their old catalog. Opened that fresh copy. Opened the Activities window and didn’t do anything until everything completed. Maybe I got lucky each time but that worked.

    0
  • John Friend
    Top Commenter

    I already waited until the Activities Window was quiet.  Yet Capture One still continued using 50% of my CPU and unable to do anything else, not even exit.

    This is CLEARLY a bug.  A program shouldn't ever lock up completely and be unable to exit for over 4 hours and have no visible feedback for what it's doing.  I'm a retired software developer.  This IS a bug.  It's not acceptable behavior - go ask any product manager.  Now how often this occurs or exactly in what circumstances it occurs, I have no idea.  But it is happening to me.

    When I have a LOT of time to futz with this, I'll start over with a fresh backup copy of the catalog and perhaps examine logs if it gets stuck seemingly forever again.  But, experiences like this are NOT good for customer relations.  I don't know how you could possibly say the product is supposed to behave this way - that this is the expected or desired behavior.  Certainly, no product manager worth their salt would say this is an acceptable user experience to just appear to "hang" for over 4 hours and be unable to exit the program and unable to do anything in the program.

    1
  • Brian Jordan
    Moderator

    You can open a bug report here. https://support.captureone.com/hc/en-us/requests/new

    Just telling you what I’ve done to correct a problem that sounds like what you’re experiencing.

    0
  • Brian Jordan
    Moderator

    And John, I don’t care about customer relations. As I hope you know by now, I’m not an employee. Just a guy trying to help out.

    0
  • Walter Rowe
    Moderator
    Top Commenter

    John Friend – I agree this seems completely abnormal. A support case should be opened. If you are experiencing this and Brian Jordan has seen it elsewhere then it certainly is not a limited incident and should be address.

    2
  • John Friend
    Top Commenter

    Walter Rowe

    Thanks Walter.  I'll do some more debugging and then post a bug report with what I've discovered. 

    For now I'm playing with AI masking in a new catalog and frankly I'm underwhelmed with how it works for my landscapes.  It doesn't appear to handle a tree/sky boundary well at all, in fact not even as well as the magic brush can.  Hopefully I will discover things that it's good at.

    0
  • John Friend
    Top Commenter

    Brian Jordan

    When you classify a serious problem that hangs the product and renders it unusable as "not a bug", that gets a reaction out of lots of people as if the product is supposed to behave this way. 

    So, if you're not representing the company, then perhaps you should refrain from calling a serious problem "not a bug".  In fact, you don't have to even offer an opinion on what is or isn't a bug - just focus on the problem solving (which you are generally helpful with).

    0
  • Brian Jordan
    Moderator

    “IMO” is shorthand for in my opinion. Sorry if that didn’t come across. The people I worked with all admitted to getting impatient and killing processes, deleting files, all kinds of mayhem. That leads me to believe that in the 3 cases I helped with, there wasn’t a software bug as I don’t believe software can be made resilient to that kind of interference. I don’t know what you did or didn’t do nor am I implying anything, I simply passed along what worked on my end to get people up and running in as short a time as possible. Also, I see quite a lot of opinions floating around here. Not sure why I should be any less able to express mine. 

    0
  • Walter Rowe
    Moderator
    Top Commenter

    John Friend – I think the initial AI masking is tuned to better work with people and well defined objects. I've had good experience with sky selection when there was a well defined line between sky and trees or what ever is below the sky, but even then it isn't a tight mask. I still have to add to it with magic brush or refine mask. When the Subject and Background mask don't work the AI Mask seems to work in a lot of cases for me, but I also agree some times magic brush is superior.

    0
  • Brian Jordan
    Moderator

    Also, I find that doing a Refine Mask after AI can help quite a lot for skies and trees. Although, I do agree with Walter.

    0
  • Jerry C

    Brian and Walter,

    If you want to let 16.3 regenerate the previews, how long should it take per 10,000 images on an M2 Mac Studio Ultra with 128 GB RAM or whatever machine you have experience with? Would this be more than a little slower if the database is on an external Thunderbolt NVME SSD rather than the internal SSD?

    Presumably the regeneration of the previews is done in the background and you can edit images while it processes. How much are the editing and export process expected to slow down while the previews are being regenerated? I would expect this to vary with the CPU type and number of cores.  

    Is there supposed to be a progress bar for the regeneration process? 

    One suggestion that might have prevented John Friend's bad experience. Would it be reasonable to update 16.3 to ask the user if they want to regenerate the previews or retain the legacy previews before any previews are regenerated and perhaps even inform them of how the process works, warning about interruption and the time it might take if regeneration is selected? 

    0
  • Brian Jordan
    Moderator

    Jerry, minutes? Certainly not long. The Activities window shows progress on preview rebuild, any activity really but I believe that can be suppressed in preferences. Don’t quote me on that. In my experience it all works well even if you work on images while all this is taking place but everything will be a bit sluggish during. The people I worked with had older Macs than yours. M1 MBP and M1 Mac mini so slower but even on them it was in the 10s of minutes per 10k. They got impatient with the sluggishness and made things worse. Edit to add here, this is not unusual activity for them and not my first rodeo.

    One suggestion that might have prevented John Friend's bad experience. Would it be reasonable to update 16.3 to ask the user if they want to regenerate the previews or retain the legacy previews before any previews are regenerated and perhaps even inform them of how the process works, warning about interruption and the time it might take if regeneration is selected? 

    i think it would be a good idea in general if the install process asked if the user wanted to maintain catalog backwards compatibility then explained in detail the ramifications of each when selected. IMO, this shouldn’t be buried in settings. 

    0
  • Jerry C

    Brian, thanks for the clarification. Sounds that a catalog with my 65k+ images could be done in an hour or so on my machine. Not lightning fast, but not so long as to disrupt work if done in the hours away from the computer. Also, it would be nice if all lengthy process had a way to cancel without causing mayhem. 

    Question: If you configure the settings to keep the legacy previews and you later regenerate some previews, do they remain in legacy format, or are they updated to the new preview form?

    0
  • Brian Jordan
    Moderator

    Jerry, I can’t answer that. I assume that once you uncheck the box in settings and regenerate, previews are upgraded. But I base that assumption on nothing more than what I think logical. I’ll send a support ticket in and post back here when I get a response.

    0
  • Walter Rowe
    Moderator
    Top Commenter

    When I upgraded my 65K image catalog Capture One did NOT automatically start regenerating previews. The release notes explicitly say you must select the images and ask it to regenerate previews. I did exactly as the release notes instructed.

    It took 12 hours for 65K images to regenerate previews using the new high quality previews setting.

    • 2019 Intel MacBook Pro w/ 32GB of RAM connected to a Thunderbolt 4 SanDisk 4TB SSD
    • Catalog stored on internal SSD that references pictures stored on the external SSD

    I expect it would take more than "minutes" for 10K images to regenerate previews on an M2 Mac Studio.

    The catalog residing on any external storage impacts performance vs stored on internal SSD.

    0
  • John Friend
    Top Commenter

    I'm still having significant problems using my existing catalog with 16.3.

    Here's an update on my original problem here.

    • I configured 16.x to use Legacy previews
    • I retrieved a 15.x backup of my main catalog (as suggested by Brian)
    • I opened that in 15.x and confirmed that it is working fine in 15.x
    • I then opened that same catalog in 16.x.
    • It prompted me about upgrading the catalog and I gave it permission.
    • It then started to load and brought up two items in the activity window.  One about building previews for the folder I have displayed and the other about "Autoloading metadata for 47 of 271 images".  The previews took about 5 minutes.  The autoloading metadata took about 3 minutes. So, the activity window was empty and my selected photo was displayed.  While it was doing these two processes in the activity window, Capture One was unusable.  It would take 30 seconds to respond to selecting an image.
    • Once it finished the items in the activity window, I could then move around to select different photos as expected.  But, when making edits, some operations (like drawing a mask or moving sliders) were really sluggish.  I checked Task Manager and saw that Capture One was using around 40% of the CPU (I have an 8-core CPU so this is using more than 3 cores to do something), none of the GPU and there is regular disk activity on the SSD where my catalog is located, no disk activity on my hard drive where the RAW originals are located.  There's nothing in the activities Window.
    • So, it's not building previews with this phantom CPU activity because the RAW images are not being accessed.  When I look at the CPU usage details, there's one CPU core that is pretty much pegged at 100% (very occasional dip below that) and the other cores are up and down.
    • Update: At the 45 minute mark, it is no longer accessing the catalog drive.  So, it's not accessing the catalog SSD and not accessing the RAW files hard drive.  What in the heck is it doing with all that CPU?
    • Update: I noticed that some of the disk activity on the catalog SSD drive was being caused by Backblaze backing up the restored backup catalog I copied so it's not clear if C1 was ever using the catalog SSD drive in conjunction with this phantom CPU usage.
    • Update: There is regular activity being written to both Application.log and to ImgCore.log.

    I will leave it sit for awhile (with my computer temporary set to not go to sleep) and see if whatever it is doing completes at some point.  Right now, it's been going for 45 minutes with no change in the situation.

    Here's what the CPU usage looks like:

    Any further suggestions for what Capture One is doing with all that CPU?  When it will finish?  Will it ever finish?  How to make this usable?

    0
  • John Friend
    Top Commenter

    Continuing on with my previous post, here's the kind of stuff that is regularly being added to Application.log while I'm not using Capture One at all and nothing is showing in the activity window and it's using about 40% of my 8-core CPU:

    [2023-11-22 08:57:31.324][009][ID:051,           ]{PSIST} | PersistImagesInternal before commit

    [2023-11-22 08:57:31.337][012][ID:051,           ]{PSIST} | PersistImagesInternal SetImageIsPersistedToDb

    [2023-11-22 08:57:31.337][000][ID:051,           ]{PSIST} | PersistImagesInternal done

    [2023-11-22 08:58:44.986][649][ID:037, .NET Threa]{PFORM} | Memory Statistics: Virtual: 2420944MB    Private: 9968MB     Managed: 1150MB     TargetId count: 1   CalibrationCache: 0MB/0     RGBCache: 0MB/0     ColorProfileCache: 3MB/154      ThumbnailCache: 4MB/6   ProcessedThumbnailCache: 0MB/0      PreviewCache: 300MB/12      RAWCache: 1047MB/12     LCCCache: 0MB/1     FocusMaskCache: 0MB/0   TileCacheOpenCL: 297MB/9    MaskPrepareCache: 23MB/51   PyramidCache: 40MB/15

    [2023-11-22 08:59:03.044][057][ID:051,           ]{PSIST} | PersistImagesInternal before commit

    [2023-11-22 08:59:03.052][007][ID:051,           ]{PSIST} | PersistImagesInternal SetImageIsPersistedToDb

    [2023-11-22 08:59:03.052][000][ID:051,           ]{PSIST} | PersistImagesInternal done

    [2023-11-22 08:59:09.115][062][ID:065, [THD] Logg]{WAIT } | Info : WAIT [351] started

    [2023-11-22 08:59:09.935][819][ID:065, [THD] Logg]{WAIT } | Info : WAIT [351] finished : 2822 ms

    [2023-11-22 08:59:44.986][051][ID:076, .NET Threa]{APPL } | Autosaving documents...

    [2023-11-22 08:59:44.987][000][ID:003, .NET Threa]{SESPS} | Before persisting Document Keyword Library

    [2023-11-22 08:59:44.988][000][ID:003, .NET Threa]{SESPS} | After persisting Document Keyword Library, 0ms

    [2023-11-22 09:01:28.195][207][ID:051,           ]{PSIST} | Saving in E:\CaptureOne-Main-Catalog\Main-16\Adjustments\LAM\2022\8\2\68\Tetons-20220724-103712-JLF_4565.NEF.comask uuids:

                                                            **| 536d4872-2e0b-48f8-95e0-3b5173609be3 Size: 315

    [2023-11-22 09:01:28.204][008][ID:051,           ]{PSIST} | PersistImagesInternal before commit

    [2023-11-22 09:01:28.211][006][ID:051,           ]{PSIST} | PersistImagesInternal SetImageIsPersistedToDb

    [2023-11-22 09:01:28.211][000][ID:051,           ]{PSIST} | PersistImagesInternal done

    [2023-11-22 09:01:44.990][778][ID:072, .NET Threa]{PFORM} | Memory Statistics: Virtual: 2421010MB    Private: 10616MB    Managed: 1341MB     TargetId count: 1   CalibrationCache: 0MB/0     RGBCache: 0MB/0     ColorProfileCache: 2MB/488      ThumbnailCache: 4MB/6   ProcessedThumbnailCache: 0MB/0      PreviewCache: 300MB/12      RAWCache: 1047MB/12     LCCCache: 0MB/1     FocusMaskCache: 0MB/0   TileCacheOpenCL: 342MB/24   MaskPrepareCache: 32MB/71   PyramidCache: 40MB/15

    [2023-11-22 09:01:50.555][564][ID:065, [THD] Logg]{WAIT } | Info : WAIT [507] started

    [2023-11-22 09:01:50.802][247][ID:065, [THD] Logg]{WAIT } | Info : WAIT [507] finished : 2248 ms

    [2023-11-22 09:03:51.878][075][ID:001,       Main]{APPL } | GetLastCoordinates failed: 5

    [2023-11-22 09:03:51.953][074][ID:051,           ]{PSIST} | Saving in E:\CaptureOne-Main-Catalog\Main-16\Adjustments\LAM\2022\8\2\68\Tetons-20220724-103712-JLF_4565.NEF.comask uuids:

                                                            **| 536d4872-2e0b-48f8-95e0-3b5173609be3 Size: 2471680

    [2023-11-22 09:03:51.959][006][ID:051,           ]{PSIST} | PersistImagesInternal before commit

    [2023-11-22 09:03:51.966][006][ID:051,           ]{PSIST} | PersistImagesInternal SetImageIsPersistedToDb

    [2023-11-22 09:03:51.966][000][ID:051,           ]{PSIST} | PersistImagesInternal done

    [2023-11-22 09:04:19.603][637][ID:001,       Main]{APPL } | Screens: 2560x1600px

    [2023-11-22 09:04:44.985][382][ID:080, .NET Threa]{APPL } | Autosaving documents...

    [2023-11-22 09:04:44.985][000][ID:138, .NET Threa]{SESPS} | Before persisting Document Keyword Library

    [2023-11-22 09:04:44.986][000][ID:138, .NET Threa]{SESPS} | After persisting Document Keyword Library, 0ms

    [2023-11-22 09:04:45.005][019][ID:137, .NET Threa]{PFORM} | Memory Statistics: Virtual: 2422649MB    Private: 12275MB    Managed: 1841MB     TargetId count: 1   CalibrationCache: 0MB/0     RGBCache: 0MB/0     ColorProfileCache: 2MB/488      ThumbnailCache: 4MB/6   ProcessedThumbnailCache: 0MB/0      PreviewCache: 300MB/12      RAWCache: 1047MB/12     LCCCache: 0MB/1     FocusMaskCache: 0MB/0   TileCacheOpenCL: 400MB/25   MaskPrepareCache: 99MB/127      PyramidCache: 73MB/16

    [2023-11-22 09:05:55.323][317][ID:001,       Main]{APPL } | GetLastCoordinates failed: 5

    [2023-11-22 09:07:44.987][664][ID:003, .NET Threa]{PFORM} | Memory Statistics: Virtual: 2422655MB    Private: 12835MB    Managed: 2143MB     TargetId count: 1   CalibrationCache: 0MB/0     RGBCache: 0MB/0     ColorProfileCache: 2MB/488      ThumbnailCache: 4MB/6   ProcessedThumbnailCache: 0MB/0      PreviewCache: 300MB/12      RAWCache: 1047MB/12     LCCCache: 0MB/1     FocusMaskCache: 0MB/0   TileCacheOpenCL: 400MB/25   MaskPrepareCache: 99MB/127      PyramidCache: 73MB/16

    [2023-11-22 09:09:44.989][001][ID:003, .NET Threa]{APPL } | Autosaving documents...

    [2023-11-22 09:09:44.989][000][ID:080, .NET Threa]{SESPS} | Before persisting Document Keyword Library

    [2023-11-22 09:09:44.990][001][ID:080, .NET Threa]{SESPS} | After persisting Document Keyword Library, 1ms

    [2023-11-22 09:10:44.988][997][ID:080, .NET Threa]{PFORM} | Memory Statistics: Virtual: 2422660MB    Private: 13402MB    Managed: 2312MB     TargetId count: 1   CalibrationCache: 0MB/0     RGBCache: 0MB/0     ColorProfileCache: 2MB/488      ThumbnailCache: 4MB/6   ProcessedThumbnailCache: 0MB/0      PreviewCache: 300MB/12      RAWCache: 1047MB/12     LCCCache: 0MB/1     FocusMaskCache: 0MB/0   TileCacheOpenCL: 400MB/25   MaskPrepareCache: 99MB/127      PyramidCache: 73MB/16

    [2023-11-22 09:11:18.349][361][ID:051,           ]{PSIST} | PersistImagesInternal before commit

    [2023-11-22 09:11:18.356][007][ID:051,           ]{PSIST} | PersistImagesInternal SetImageIsPersistedToDb

    [2023-11-22 09:11:18.356][000][ID:051,           ]{PSIST} | PersistImagesInternal done

    [2023-11-22 09:13:37.025][669][ID:065, [THD] Logg]{WAIT } | Info : WAIT [1203] started

    [2023-11-22 09:13:39.057][031][ID:065, [THD] Logg]{WAIT } | Info : WAIT [1203] finished : 4042 ms

    [2023-11-22 09:13:44.988][930][ID:137, .NET Threa]{PFORM} | Memory Statistics: Virtual: 2422662MB    Private: 14039MB    Managed: 2530MB     TargetId count: 1   CalibrationCache: 0MB/0     RGBCache: 0MB/0     ColorProfileCache: 2MB/488      ThumbnailCache: 4MB/6   ProcessedThumbnailCache: 0MB/0      PreviewCache: 300MB/12      RAWCache: 1047MB/12     LCCCache: 0MB/1     FocusMaskCache: 0MB/0   TileCacheOpenCL: 400MB/25   MaskPrepareCache: 99MB/127      PyramidCache: 73MB/16

    [2023-11-22 09:14:36.921][933][ID:065, [THD] Logg]{WAIT } | Info : WAIT [1258] started

    [2023-11-22 09:14:38.847][925][ID:065, [THD] Logg]{WAIT } | Info : WAIT [1258] finished : 3947 ms

    [2023-11-22 09:14:44.989][142][ID:072, .NET Threa]{APPL } | Autosaving documents...

    [2023-11-22 09:14:44.990][000][ID:136, .NET Threa]{SESPS} | Before persisting Document Keyword Library

    [2023-11-22 09:14:44.991][000][ID:136, .NET Threa]{SESPS} | After persisting Document Keyword Library, 0ms

    [2023-11-22 09:16:44.986][995][ID:134, .NET Threa]{PFORM} | Memory Statistics: Virtual: 2422657MB    Private: 15129MB    Managed: 3408MB     TargetId count: 1   CalibrationCache: 0MB/0     RGBCache: 0MB/0     ColorProfileCache: 2MB/488      ThumbnailCache: 4MB/6   ProcessedThumbnailCache: 0MB/0      PreviewCache: 300MB/12      RAWCache: 1047MB/12     LCCCache: 0MB/1     FocusMaskCache: 0MB/0   TileCacheOpenCL: 400MB/25   MaskPrepareCache: 99MB/127      PyramidCache: 73MB/16

    [2023-11-22 09:19:44.981][994][ID:134, .NET Threa]{APPL } | Autosaving documents...

    [2023-11-22 09:19:44.981][000][ID:003, .NET Threa]{SESPS} | Before persisting Document Keyword Library

    [2023-11-22 09:19:44.985][004][ID:080, .NET Threa]{PFORM} | Memory Statistics: Virtual: 2422659MB    Private: 15748MB    Managed: 3674MB     TargetId count: 1   CalibrationCache: 0MB/0     RGBCache: 0MB/0     ColorProfileCache: 2MB/488      ThumbnailCache: 4MB/6   ProcessedThumbnailCache: 0MB/0      PreviewCache: 300MB/12      RAWCache: 1047MB/12     LCCCache: 0MB/1     FocusMaskCache: 0MB/0   TileCacheOpenCL: 400MB/25   MaskPrepareCache: 99MB/127      PyramidCache: 73MB/16

    [2023-11-22 09:19:44.987][001][ID:003, .NET Threa]{SESPS} | After persisting Document Keyword Library, 6ms

    [2023-11-22 09:22:44.995][007][ID:093, .NET Threa]{PFORM} | Memory Statistics: Virtual: 2422663MB    Private: 16272MB    Managed: 3894MB     TargetId count: 1   CalibrationCache: 0MB/0     RGBCache: 0MB/0     ColorProfileCache: 2MB/488      ThumbnailCache: 4MB/6   ProcessedThumbnailCache: 0MB/0      PreviewCache: 300MB/12      RAWCache: 1047MB/12     LCCCache: 0MB/1     FocusMaskCache: 0MB/0   TileCacheOpenCL: 400MB/25   MaskPrepareCache: 99MB/127      PyramidCache: 73MB/16

    [2023-11-22 09:24:27.062][067][ID:065, [THD] Logg]{WAIT } | Info : WAIT [1833] started

    [2023-11-22 09:24:27.346][283][ID:065, [THD] Logg]{WAIT } | Info : WAIT [1833] finished : 2294 ms

    [2023-11-22 09:24:44.977][631][ID:080, .NET Threa]{APPL } | Autosaving documents...

    [2023-11-22 09:24:44.978][000][ID:080, .NET Threa]{SESPS} | Before persisting Document Keyword Library

    [2023-11-22 09:24:44.984][006][ID:080, .NET Threa]{SESPS} | After persisting Document Keyword Library, 6ms

    [2023-11-22 09:25:44.986][002][ID:134, .NET Threa]{PFORM} | Memory Statistics: Virtual: 2422665MB    Private: 16889MB    Managed: 4408MB     TargetId count: 1   CalibrationCache: 0MB/0     RGBCache: 0MB/0     ColorProfileCache: 2MB/488      ThumbnailCache: 4MB/6   ProcessedThumbnailCache: 0MB/0      PreviewCache: 300MB/12      RAWCache: 1047MB/12     LCCCache: 0MB/1     FocusMaskCache: 0MB/0   TileCacheOpenCL: 400MB/25   MaskPrepareCache: 99MB/127      PyramidCache: 73MB/16

    [2023-11-22 09:28:44.998][011][ID:134, .NET Threa]{PFORM} | Memory Statistics: Virtual: 2422667MB    Private: 17437MB    Managed: 4311MB     TargetId count: 1   CalibrationCache: 0MB/0     RGBCache: 0MB/0     ColorProfileCache: 2MB/488      ThumbnailCache: 4MB/6   ProcessedThumbnailCache: 0MB/0      PreviewCache: 300MB/12      RAWCache: 1047MB/12     LCCCache: 0MB/1     FocusMaskCache: 0MB/0   TileCacheOpenCL: 400MB/25   MaskPrepareCache: 99MB/127      PyramidCache: 73MB/16

    [2023-11-22 09:29:44.982][983][ID:072, .NET Threa]{APPL } | Autosaving documents...

    [2023-11-22 09:29:44.982][000][ID:080, .NET Threa]{SESPS} | Before persisting Document Keyword Library

    [2023-11-22 09:29:44.988][006][ID:080, .NET Threa]{SESPS} | After persisting Document Keyword Library, 6ms

    [2023-11-22 09:31:44.986][997][ID:043, .NET Threa]{PFORM} | Memory Statistics: Virtual: 2422662MB    Private: 17954MB    Managed: 4537MB     TargetId count: 1   CalibrationCache: 0MB/0     RGBCache: 0MB/0     ColorProfileCache: 2MB/488      ThumbnailCache: 4MB/6   ProcessedThumbnailCache: 0MB/0      PreviewCache: 300MB/12      RAWCache: 1047MB/12     LCCCache: 0MB/1     FocusMaskCache: 0MB/0   TileCacheOpenCL: 400MB/25   MaskPrepareCache: 99MB/127      PyramidCache: 73MB/16

    [2023-11-22 09:34:44.984][998][ID:093, .NET Threa]{APPL } | Autosaving documents...

    [2023-11-22 09:34:44.984][000][ID:003, .NET Threa]{SESPS} | Before persisting Document Keyword Library

    [2023-11-22 09:34:44.988][004][ID:134, .NET Threa]{PFORM} | Memory Statistics: Virtual: 2422661MB    Private: 18442MB    Managed: 4754MB     TargetId count: 1   CalibrationCache: 0MB/0     RGBCache: 0MB/0     ColorProfileCache: 2MB/488      ThumbnailCache: 4MB/6   ProcessedThumbnailCache: 0MB/0      PreviewCache: 300MB/12      RAWCache: 1047MB/12     LCCCache: 0MB/1     FocusMaskCache: 0MB/0   TileCacheOpenCL: 400MB/25   MaskPrepareCache: 99MB/127      PyramidCache: 73MB/16

    [2023-11-22 09:34:44.991][002][ID:003, .NET Threa]{SESPS} | After persisting Document Keyword Library, 6ms

    [2023-11-22 09:37:44.991][000][ID:134, .NET Threa]{PFORM} | Memory Statistics: Virtual: 2422662MB    Private: 18960MB    Managed: 4983MB     TargetId count: 1   CalibrationCache: 0MB/0     RGBCache: 0MB/0     ColorProfileCache: 2MB/488      ThumbnailCache: 4MB/6   ProcessedThumbnailCache: 0MB/0      PreviewCache: 300MB/12      RAWCache: 1047MB/12     LCCCache: 0MB/1     FocusMaskCache: 0MB/0   TileCacheOpenCL: 400MB/25   MaskPrepareCache: 99MB/127      PyramidCache: 73MB/16

    [2023-11-22 09:38:50.710][719][ID:065, [THD] Logg]{WAIT } | Info : WAIT [2686] started

    [2023-11-22 09:38:54.853][142][ID:065, [THD] Logg]{WAIT } | Info : WAIT [2686] finished : 6161 ms

    [2023-11-22 09:39:05.001][147][ID:065, [THD] Logg]{WAIT } | Info : WAIT [2694] started

    [2023-11-22 09:39:06.583][582][ID:065, [THD] Logg]{WAIT } | Info : WAIT [2694] finished : 3709 ms

    [2023-11-22 09:39:44.988][404][ID:134, .NET Threa]{APPL } | Autosaving documents...

    [2023-11-22 09:39:44.988][000][ID:093, .NET Threa]{SESPS} | Before persisting Document Keyword Library

    [2023-11-22 09:39:44.994][006][ID:093, .NET Threa]{SESPS} | After persisting Document Keyword Library, 6ms

    [2023-11-22 09:39:57.903][908][ID:065, [THD] Logg]{WAIT } | Info : WAIT [2743] started

    [2023-11-22 09:40:01.518][615][ID:065, [THD] Logg]{WAIT } | Info : WAIT [2743] finished : 5621 ms

    [2023-11-22 09:40:45.080][561][ID:134, .NET Threa]{PFORM} | Memory Statistics: Virtual: 2422661MB    Private: 20751MB    Managed: 6559MB     TargetId count: 1   CalibrationCache: 0MB/0     RGBCache: 0MB/0     ColorProfileCache: 2MB/488      ThumbnailCache: 4MB/6   ProcessedThumbnailCache: 0MB/0      PreviewCache: 300MB/12      RAWCache: 1047MB/12     LCCCache: 0MB/1     FocusMaskCache: 0MB/0   TileCacheOpenCL: 400MB/25   MaskPrepareCache: 99MB/127      PyramidCache: 73MB/16

    [2023-11-22 09:41:04.894][814][ID:065, [THD] Logg]{WAIT } | Info : WAIT [2804] started

    [2023-11-22 09:41:06.981][086][ID:065, [THD] Logg]{WAIT } | Info : WAIT [2804] finished : 4107 ms

    [2023-11-22 09:42:17.295][314][ID:065, [THD] Logg]{WAIT } | Info : WAIT [2872] started

    [2023-11-22 09:42:18.871][576][ID:065, [THD] Logg]{WAIT } | Info : WAIT [2872] finished : 3597 ms

    [2023-11-22 09:42:42.006][134][ID:065, [THD] Logg]{WAIT } | Info : WAIT [2893] started

    [2023-11-22 09:42:44.091][084][ID:065, [THD] Logg]{WAIT } | Info : WAIT [2893] finished : 4094 ms

    [2023-11-22 09:43:20.820][729][ID:065, [THD] Logg]{WAIT } | Info : WAIT [2927] started

    [2023-11-22 09:43:21.480][660][ID:065, [THD] Logg]{WAIT } | Info : WAIT [2927] finished : 2676 ms

    [2023-11-22 09:43:44.995][514][ID:076, .NET Threa]{PFORM} | Memory Statistics: Virtual: 2422661MB    Private: 21508MB    Managed: 6770MB     TargetId count: 1   CalibrationCache: 0MB/0     RGBCache: 0MB/0     ColorProfileCache: 2MB/488      ThumbnailCache: 4MB/6   ProcessedThumbnailCache: 0MB/0      PreviewCache: 300MB/12      RAWCache: 1047MB/12     LCCCache: 0MB/1     FocusMaskCache: 0MB/0   TileCacheOpenCL: 400MB/25   MaskPrepareCache: 99MB/127      PyramidCache: 73MB/16

    [2023-11-22 09:44:36.972][976][ID:065, [THD] Logg]{WAIT } | Info : WAIT [3000] started

    [2023-11-22 09:44:41.090][118][ID:065, [THD] Logg]{WAIT } | Info : WAIT [3000] finished : 6142 ms

    [2023-11-22 09:44:44.984][894][ID:093, .NET Threa]{APPL } | Autosaving documents...

    [2023-11-22 09:44:44.984][000][ID:072, .NET Threa]{SESPS} | Before persisting Document Keyword Library

    [2023-11-22 09:44:44.990][006][ID:072, .NET Threa]{SESPS} | After persisting Document Keyword Library, 6ms

    [2023-11-22 09:45:53.104][113][ID:065, [THD] Logg]{WAIT } | Info : WAIT [3069] started

    [2023-11-22 09:45:55.291][187][ID:065, [THD] Logg]{WAIT } | Info : WAIT [3069] finished : 4208 ms

    [2023-11-22 09:46:42.766][474][ID:065, [THD] Logg]{WAIT } | Info : WAIT [3114] started

    [2023-11-22 09:46:44.994][227][ID:072, .NET Threa]{PFORM} | Memory Statistics: Virtual: 2422660MB    Private: 22272MB    Managed: 7042MB     TargetId count: 1   CalibrationCache: 0MB/0     RGBCache: 0MB/0     ColorProfileCache: 2MB/488      ThumbnailCache: 4MB/6   ProcessedThumbnailCache: 0MB/0      PreviewCache: 300MB/12      RAWCache: 1047MB/12     LCCCache: 0MB/1     FocusMaskCache: 0MB/0   TileCacheOpenCL: 400MB/25   MaskPrepareCache: 99MB/127      PyramidCache: 73MB/16

    [2023-11-22 09:46:45.996][002][ID:065, [THD] Logg]{WAIT } | Info : WAIT [3114] finished : 5246 ms

    [2023-11-22 09:48:01.837][841][ID:065, [THD] Logg]{WAIT } | Info : WAIT [3187] started

    [2023-11-22 09:48:04.671][833][ID:065, [THD] Logg]{WAIT } | Info : WAIT [3187] finished : 4853 ms

    [2023-11-22 09:48:31.614][942][ID:065, [THD] Logg]{WAIT } | Info : WAIT [3211] started

    [2023-11-22 09:48:35.540][926][ID:065, [THD] Logg]{WAIT } | Info : WAIT [3211] finished : 5939 ms

    [2023-11-22 09:48:47.611][071][ID:065, [THD] Logg]{WAIT } | Info : WAIT [3221] started

    [2023-11-22 09:48:50.014][402][ID:065, [THD] Logg]{WAIT } | Info : WAIT [3221] finished : 4406 ms

    [2023-11-22 09:48:53.040][025][ID:065, [THD] Logg]{WAIT } | Info : WAIT [3222] started

    [2023-11-22 09:48:57.644][604][ID:065, [THD] Logg]{WAIT } | Info : WAIT [3222] finished : 6623 ms

    [2023-11-22 09:49:44.984][339][ID:077, .NET Threa]{APPL } | Autosaving documents...

    [2023-11-22 09:49:44.984][000][ID:072, .NET Threa]{SESPS} | Before persisting Document Keyword Library

    [2023-11-22 09:49:44.989][005][ID:076, .NET Threa]{PFORM} | Memory Statistics: Virtual: 2422659MB    Private: 23145MB    Managed: 7080MB     TargetId count: 1   CalibrationCache: 0MB/0     RGBCache: 0MB/0     ColorProfileCache: 2MB/488      ThumbnailCache: 4MB/6   ProcessedThumbnailCache: 0MB/0      PreviewCache: 300MB/12      RAWCache: 1047MB/12     LCCCache: 0MB/1     FocusMaskCache: 0MB/0   TileCacheOpenCL: 400MB/25   MaskPrepareCache: 99MB/127      PyramidCache: 73MB/16

    [2023-11-22 09:49:44.990][000][ID:072, .NET Threa]{SESPS} | After persisting Document Keyword Library, 6ms
    0
  • John Friend
    Top Commenter

    Continuing on with my previous post, here's the kind of stuff that is regularly being added to ImgCore.log while I'm not using Capture One at all and nothing is showing in the activity window and it's using about 40% of my 8-core CPU:

    2023-11-22 09:25:44.978> MaskPrepare Cache on CreateProxies1 : 0 mb (0)
    2023-11-22 09:25:44.978> MaskPrepare Cache on PackageBitmapCPUProcessor0 : 3 mb (68)
    2023-11-22 09:25:44.978> MaskPrepare Cache on PackageBitmapGPUProcessor0 : 79 mb (33)
    2023-11-22 09:25:44.978> MaskPrepare Cache on PackageSamplerProcessor0 : 2 mb (5)
    2023-11-22 09:25:44.978> MaskPrepare Cache on PYRAMID_PackageBitmapCPUProcessor0 : 13 mb (21)
    2023-11-22 09:25:44.978> MaskPrepare Cache on PYRAMID_PackageSamplerProcessor0 : 0 mb (0)
    2023-11-22 09:25:44.978> MaskPrepare Cache on PYRAMID_PackageBitmapGPUProcessor0 : 0 mb (0)
    2023-11-22 09:25:44.978> MaskPrepare Cache on VariantProcessHelper : 0 mb (0)
    2023-11-22 09:25:44.978> MaskPrepare Cache on Automask processor : 0 mb (0)
    2023-11-22 09:25:44.978> MaskPrepare Cache on PYRAMID_Automask processor : 0 mb (0)
    2023-11-22 09:25:44.978> MaskPrepare Cache on AiMasking : 0 mb (0)
    2023-11-22 09:25:44.978> MaskPrepare Cache on PYRAMID_AiMasking : 0 mb (0)
    2023-11-22 09:28:44.993> Tile Caching on PackageBitmapCPUProcessor0 (targetID 3)  : 0 bytes (0)
    2023-11-22 09:28:44.993> (Message delayed 180.011s to prevent duplicates.)
    2023-11-22 09:28:44.993> Tile Caching on AiMasking (targetID 0)  : 0 bytes (0)
    2023-11-22 09:28:44.993> (Message delayed 180.011s to prevent duplicates.)
    2023-11-22 09:28:44.993> Tile Caching on PackageBitmapCPUProcessor0 (targetID 3)  : 0 bytes (0)
    2023-11-22 09:28:44.993> Tile Caching on PackageBitmapGPUProcessor0 (targetID 3)  : 15368320 bytes (2)
    2023-11-22 09:28:44.993> Tile Caching on PackageBitmapGPUProcessor0 (targetID 3)  : 95117216 bytes (2)
    2023-11-22 09:28:44.993> Tile Caching on PackageBitmapGPUProcessor0 (targetID 3)  : 160919040 bytes (16)
    2023-11-22 09:28:44.993> Tile Caching on PackageBitmapGPUProcessor0 (targetID 3)  : 13096512 bytes (1)
    2023-11-22 09:28:44.993> Tile Caching on PackageBitmapGPUProcessor0 (targetID 3)  : 57212928 bytes (1)
    2023-11-22 09:28:44.993> Tile Caching on PackageBitmapGPUProcessor0 (targetID 3)  : 74067488 bytes (2)
    2023-11-22 09:28:44.993> Tile Caching on PackageBitmapGPUProcessor0 (targetID 0)  : 4595200 bytes (1)
    2023-11-22 09:28:44.993> Tile Caching on PackageSamplerProcessor0 (targetID 0)  : 0 bytes (0)
    2023-11-22 09:28:44.993> Tile Caching on AiMasking (targetID 0)  : 0 bytes (0)
    2023-11-22 09:28:44.993> MaskPrepare Cache on CreateProxies1 : 0 mb (0)
    2023-11-22 09:28:44.993> MaskPrepare Cache on PackageBitmapCPUProcessor0 : 3 mb (68)
    2023-11-22 09:28:44.993> MaskPrepare Cache on PackageBitmapGPUProcessor0 : 79 mb (33)
    2023-11-22 09:28:44.993> MaskPrepare Cache on PackageSamplerProcessor0 : 2 mb (5)
    2023-11-22 09:28:44.993> MaskPrepare Cache on PYRAMID_PackageBitmapCPUProcessor0 : 13 mb (21)
    2023-11-22 09:28:44.993> MaskPrepare Cache on PYRAMID_PackageSamplerProcessor0 : 0 mb (0)
    2023-11-22 09:28:44.993> MaskPrepare Cache on PYRAMID_PackageBitmapGPUProcessor0 : 0 mb (0)
    2023-11-22 09:28:44.993> MaskPrepare Cache on VariantProcessHelper : 0 mb (0)
    2023-11-22 09:28:44.993> MaskPrepare Cache on Automask processor : 0 mb (0)
    2023-11-22 09:28:44.993> MaskPrepare Cache on PYRAMID_Automask processor : 0 mb (0)
    2023-11-22 09:28:44.993> MaskPrepare Cache on AiMasking : 0 mb (0)
    2023-11-22 09:28:44.993> MaskPrepare Cache on PYRAMID_AiMasking : 0 mb (0)
    2023-11-22 09:31:44.985> Tile Caching on PackageBitmapCPUProcessor0 (targetID 3)  : 0 bytes (0)
    2023-11-22 09:31:44.985> (Message delayed 179.988s to prevent duplicates.)
    2023-11-22 09:31:44.985> Tile Caching on AiMasking (targetID 0)  : 0 bytes (0)
    2023-11-22 09:31:44.985> (Message delayed 179.988s to prevent duplicates.)
    2023-11-22 09:31:44.985> Tile Caching on PackageBitmapCPUProcessor0 (targetID 3)  : 0 bytes (0)
    2023-11-22 09:31:44.985> Tile Caching on PackageBitmapGPUProcessor0 (targetID 3)  : 15368320 bytes (2)
    2023-11-22 09:31:44.985> Tile Caching on PackageBitmapGPUProcessor0 (targetID 3)  : 95117216 bytes (2)
    2023-11-22 09:31:44.985> Tile Caching on PackageBitmapGPUProcessor0 (targetID 3)  : 160919040 bytes (16)
    2023-11-22 09:31:44.985> Tile Caching on PackageBitmapGPUProcessor0 (targetID 3)  : 13096512 bytes (1)
    2023-11-22 09:31:44.985> Tile Caching on PackageBitmapGPUProcessor0 (targetID 3)  : 57212928 bytes (1)
    2023-11-22 09:31:44.985> Tile Caching on PackageBitmapGPUProcessor0 (targetID 3)  : 74067488 bytes (2)
    2023-11-22 09:31:44.985> Tile Caching on PackageBitmapGPUProcessor0 (targetID 0)  : 4595200 bytes (1)
    2023-11-22 09:31:44.985> Tile Caching on PackageSamplerProcessor0 (targetID 0)  : 0 bytes (0)
    2023-11-22 09:31:44.985> Tile Caching on AiMasking (targetID 0)  : 0 bytes (0)
    2023-11-22 09:31:44.985> MaskPrepare Cache on CreateProxies1 : 0 mb (0)
    2023-11-22 09:31:44.985> MaskPrepare Cache on PackageBitmapCPUProcessor0 : 3 mb (68)
    2023-11-22 09:31:44.985> MaskPrepare Cache on PackageBitmapGPUProcessor0 : 79 mb (33)
    2023-11-22 09:31:44.985> MaskPrepare Cache on PackageSamplerProcessor0 : 2 mb (5)
    2023-11-22 09:31:44.985> MaskPrepare Cache on PYRAMID_PackageBitmapCPUProcessor0 : 13 mb (21)
    2023-11-22 09:31:44.985> MaskPrepare Cache on PYRAMID_PackageSamplerProcessor0 : 0 mb (0)
    2023-11-22 09:31:44.985> MaskPrepare Cache on PYRAMID_PackageBitmapGPUProcessor0 : 0 mb (0)
    2023-11-22 09:31:44.985> MaskPrepare Cache on VariantProcessHelper : 0 mb (0)
    2023-11-22 09:31:44.985> MaskPrepare Cache on Automask processor : 0 mb (0)
    2023-11-22 09:31:44.985> MaskPrepare Cache on PYRAMID_Automask processor : 0 mb (0)
    2023-11-22 09:31:44.985> MaskPrepare Cache on AiMasking : 0 mb (0)
    2023-11-22 09:31:44.985> MaskPrepare Cache on PYRAMID_AiMasking : 0 mb (0)
    2023-11-22 09:34:44.984> Tile Caching on PackageBitmapCPUProcessor0 (targetID 3)  : 0 bytes (0)
    2023-11-22 09:34:44.984> (Message delayed 180.003s to prevent duplicates.)
    2023-11-22 09:34:44.984> Tile Caching on AiMasking (targetID 0)  : 0 bytes (0)
    2023-11-22 09:34:44.984> (Message delayed 180.003s to prevent duplicates.)
    2023-11-22 09:34:44.984> Tile Caching on PackageBitmapCPUProcessor0 (targetID 3)  : 0 bytes (0)
    2023-11-22 09:34:44.984> Tile Caching on PackageBitmapGPUProcessor0 (targetID 3)  : 15368320 bytes (2)
    2023-11-22 09:34:44.984> Tile Caching on PackageBitmapGPUProcessor0 (targetID 3)  : 95117216 bytes (2)
    2023-11-22 09:34:44.984> Tile Caching on PackageBitmapGPUProcessor0 (targetID 3)  : 160919040 bytes (16)
    2023-11-22 09:34:44.984> Tile Caching on PackageBitmapGPUProcessor0 (targetID 3)  : 13096512 bytes (1)
    2023-11-22 09:34:44.984> Tile Caching on PackageBitmapGPUProcessor0 (targetID 3)  : 57212928 bytes (1)
    2023-11-22 09:34:44.984> Tile Caching on PackageBitmapGPUProcessor0 (targetID 3)  : 74067488 bytes (2)
    2023-11-22 09:34:44.984> Tile Caching on PackageBitmapGPUProcessor0 (targetID 0)  : 4595200 bytes (1)
    2023-11-22 09:34:44.984> Tile Caching on PackageSamplerProcessor0 (targetID 0)  : 0 bytes (0)
    2023-11-22 09:34:44.984> Tile Caching on AiMasking (targetID 0)  : 0 bytes (0)
    2023-11-22 09:34:44.984> MaskPrepare Cache on CreateProxies1 : 0 mb (0)
    2023-11-22 09:34:44.984> MaskPrepare Cache on PackageBitmapCPUProcessor0 : 3 mb (68)
    2023-11-22 09:34:44.984> MaskPrepare Cache on PackageBitmapGPUProcessor0 : 79 mb (33)
    2023-11-22 09:34:44.984> MaskPrepare Cache on PackageSamplerProcessor0 : 2 mb (5)
    2023-11-22 09:34:44.984> MaskPrepare Cache on PYRAMID_PackageBitmapCPUProcessor0 : 13 mb (21)
    2023-11-22 09:34:44.984> MaskPrepare Cache on PYRAMID_PackageSamplerProcessor0 : 0 mb (0)
    2023-11-22 09:34:44.984> MaskPrepare Cache on PYRAMID_PackageBitmapGPUProcessor0 : 0 mb (0)
    2023-11-22 09:34:44.984> MaskPrepare Cache on VariantProcessHelper : 0 mb (0)
    2023-11-22 09:34:44.984> MaskPrepare Cache on Automask processor : 0 mb (0)
    2023-11-22 09:34:44.984> MaskPrepare Cache on PYRAMID_Automask processor : 0 mb (0)
    2023-11-22 09:34:44.984> MaskPrepare Cache on AiMasking : 0 mb (0)
    2023-11-22 09:34:44.984> MaskPrepare Cache on PYRAMID_AiMasking : 0 mb (0)
    2023-11-22 09:37:44.987> Tile Caching on PackageBitmapCPUProcessor0 (targetID 3)  : 0 bytes (0)
    2023-11-22 09:37:44.987> (Message delayed 180.002s to prevent duplicates.)
    2023-11-22 09:37:44.987> Tile Caching on AiMasking (targetID 0)  : 0 bytes (0)
    2023-11-22 09:37:44.987> (Message delayed 180.002s to prevent duplicates.)
    2023-11-22 09:37:44.987> Tile Caching on PackageBitmapCPUProcessor0 (targetID 3)  : 0 bytes (0)
    2023-11-22 09:37:44.987> Tile Caching on PackageBitmapGPUProcessor0 (targetID 3)  : 15368320 bytes (2)
    2023-11-22 09:37:44.987> Tile Caching on PackageBitmapGPUProcessor0 (targetID 3)  : 95117216 bytes (2)
    2023-11-22 09:37:44.987> Tile Caching on PackageBitmapGPUProcessor0 (targetID 3)  : 160919040 bytes (16)
    2023-11-22 09:37:44.987> Tile Caching on PackageBitmapGPUProcessor0 (targetID 3)  : 13096512 bytes (1)
    2023-11-22 09:37:44.987> Tile Caching on PackageBitmapGPUProcessor0 (targetID 3)  : 57212928 bytes (1)
    2023-11-22 09:37:44.987> Tile Caching on PackageBitmapGPUProcessor0 (targetID 3)  : 74067488 bytes (2)
    2023-11-22 09:37:44.987> Tile Caching on PackageBitmapGPUProcessor0 (targetID 0)  : 4595200 bytes (1)
    2023-11-22 09:37:44.987> Tile Caching on PackageSamplerProcessor0 (targetID 0)  : 0 bytes (0)
    2023-11-22 09:37:44.987> Tile Caching on AiMasking (targetID 0)  : 0 bytes (0)
    2023-11-22 09:37:44.987> MaskPrepare Cache on CreateProxies1 : 0 mb (0)
    2023-11-22 09:37:44.987> MaskPrepare Cache on PackageBitmapCPUProcessor0 : 3 mb (68)
    2023-11-22 09:37:44.987> MaskPrepare Cache on PackageBitmapGPUProcessor0 : 79 mb (33)
    2023-11-22 09:37:44.987> MaskPrepare Cache on PackageSamplerProcessor0 : 2 mb (5)
    2023-11-22 09:37:44.987> MaskPrepare Cache on PYRAMID_PackageBitmapCPUProcessor0 : 13 mb (21)
    2023-11-22 09:37:44.987> MaskPrepare Cache on PYRAMID_PackageSamplerProcessor0 : 0 mb (0)
    2023-11-22 09:37:44.987> MaskPrepare Cache on PYRAMID_PackageBitmapGPUProcessor0 : 0 mb (0)
    2023-11-22 09:37:44.987> MaskPrepare Cache on VariantProcessHelper : 0 mb (0)
    2023-11-22 09:37:44.987> MaskPrepare Cache on Automask processor : 0 mb (0)
    2023-11-22 09:37:44.987> MaskPrepare Cache on PYRAMID_Automask processor : 0 mb (0)
    2023-11-22 09:37:44.987> MaskPrepare Cache on AiMasking : 0 mb (0)
    2023-11-22 09:37:44.987> MaskPrepare Cache on PYRAMID_AiMasking : 0 mb (0)
    2023-11-22 09:40:45.077> Tile Caching on PackageBitmapCPUProcessor0 (targetID 3)  : 0 bytes (0)
    2023-11-22 09:40:45.077> (Message delayed 180.089s to prevent duplicates.)
    2023-11-22 09:40:45.077> Tile Caching on AiMasking (targetID 0)  : 0 bytes (0)
    2023-11-22 09:40:45.077> (Message delayed 180.088s to prevent duplicates.)
    2023-11-22 09:40:45.077> Tile Caching on PackageBitmapCPUProcessor0 (targetID 3)  : 0 bytes (0)
    2023-11-22 09:40:45.077> Tile Caching on PackageBitmapGPUProcessor0 (targetID 3)  : 15368320 bytes (2)
    2023-11-22 09:40:45.077> Tile Caching on PackageBitmapGPUProcessor0 (targetID 3)  : 95117216 bytes (2)
    2023-11-22 09:40:45.077> Tile Caching on PackageBitmapGPUProcessor0 (targetID 3)  : 160919040 bytes (16)
    2023-11-22 09:40:45.077> Tile Caching on PackageBitmapGPUProcessor0 (targetID 3)  : 13096512 bytes (1)
    2023-11-22 09:40:45.077> Tile Caching on PackageBitmapGPUProcessor0 (targetID 3)  : 57212928 bytes (1)
    2023-11-22 09:40:45.077> Tile Caching on PackageBitmapGPUProcessor0 (targetID 3)  : 74067488 bytes (2)
    2023-11-22 09:40:45.077> Tile Caching on PackageBitmapGPUProcessor0 (targetID 0)  : 4595200 bytes (1)
    2023-11-22 09:40:45.077> Tile Caching on PackageSamplerProcessor0 (targetID 0)  : 0 bytes (0)
    2023-11-22 09:40:45.077> Tile Caching on AiMasking (targetID 0)  : 0 bytes (0)
    2023-11-22 09:40:45.077> MaskPrepare Cache on CreateProxies1 : 0 mb (0)
    2023-11-22 09:40:45.077> MaskPrepare Cache on PackageBitmapCPUProcessor0 : 3 mb (68)
    2023-11-22 09:40:45.077> MaskPrepare Cache on PackageBitmapGPUProcessor0 : 79 mb (33)
    2023-11-22 09:40:45.077> MaskPrepare Cache on PackageSamplerProcessor0 : 2 mb (5)
    2023-11-22 09:40:45.077> MaskPrepare Cache on PYRAMID_PackageBitmapCPUProcessor0 : 13 mb (21)
    2023-11-22 09:40:45.077> MaskPrepare Cache on PYRAMID_PackageSamplerProcessor0 : 0 mb (0)
    2023-11-22 09:40:45.077> MaskPrepare Cache on PYRAMID_PackageBitmapGPUProcessor0 : 0 mb (0)
    2023-11-22 09:40:45.077> MaskPrepare Cache on VariantProcessHelper : 0 mb (0)
    2023-11-22 09:40:45.077> MaskPrepare Cache on Automask processor : 0 mb (0)
    2023-11-22 09:40:45.077> MaskPrepare Cache on PYRAMID_Automask processor : 0 mb (0)
    2023-11-22 09:40:45.077> MaskPrepare Cache on AiMasking : 0 mb (0)
    2023-11-22 09:40:45.077> MaskPrepare Cache on PYRAMID_AiMasking : 0 mb (0)
    2023-11-22 09:43:44.994> Tile Caching on PackageBitmapCPUProcessor0 (targetID 3)  : 0 bytes (0)
    2023-11-22 09:43:44.994> (Message delayed 179.915s to prevent duplicates.)
    2023-11-22 09:43:44.994> Tile Caching on AiMasking (targetID 0)  : 0 bytes (0)
    2023-11-22 09:43:44.994> (Message delayed 179.915s to prevent duplicates.)
    2023-11-22 09:43:44.994> Tile Caching on PackageBitmapCPUProcessor0 (targetID 3)  : 0 bytes (0)
    2023-11-22 09:43:44.994> Tile Caching on PackageBitmapGPUProcessor0 (targetID 3)  : 15368320 bytes (2)
    2023-11-22 09:43:44.994> Tile Caching on PackageBitmapGPUProcessor0 (targetID 3)  : 95117216 bytes (2)
    2023-11-22 09:43:44.994> Tile Caching on PackageBitmapGPUProcessor0 (targetID 3)  : 160919040 bytes (16)
    2023-11-22 09:43:44.994> Tile Caching on PackageBitmapGPUProcessor0 (targetID 3)  : 13096512 bytes (1)
    2023-11-22 09:43:44.994> Tile Caching on PackageBitmapGPUProcessor0 (targetID 3)  : 57212928 bytes (1)
    2023-11-22 09:43:44.994> Tile Caching on PackageBitmapGPUProcessor0 (targetID 3)  : 74067488 bytes (2)
    2023-11-22 09:43:44.994> Tile Caching on PackageBitmapGPUProcessor0 (targetID 0)  : 4595200 bytes (1)
    2023-11-22 09:43:44.994> Tile Caching on PackageSamplerProcessor0 (targetID 0)  : 0 bytes (0)
    2023-11-22 09:43:44.994> Tile Caching on AiMasking (targetID 0)  : 0 bytes (0)
    2023-11-22 09:43:44.994> MaskPrepare Cache on CreateProxies1 : 0 mb (0)
    2023-11-22 09:43:44.994> MaskPrepare Cache on PackageBitmapCPUProcessor0 : 3 mb (68)
    2023-11-22 09:43:44.994> MaskPrepare Cache on PackageBitmapGPUProcessor0 : 79 mb (33)
    2023-11-22 09:43:44.994> MaskPrepare Cache on PackageSamplerProcessor0 : 2 mb (5)
    2023-11-22 09:43:44.994> MaskPrepare Cache on PYRAMID_PackageBitmapCPUProcessor0 : 13 mb (21)
    2023-11-22 09:43:44.994> MaskPrepare Cache on PYRAMID_PackageSamplerProcessor0 : 0 mb (0)
    2023-11-22 09:43:44.994> MaskPrepare Cache on PYRAMID_PackageBitmapGPUProcessor0 : 0 mb (0)
    2023-11-22 09:43:44.995> MaskPrepare Cache on VariantProcessHelper : 0 mb (0)
    2023-11-22 09:43:44.995> MaskPrepare Cache on Automask processor : 0 mb (0)
    2023-11-22 09:43:44.995> MaskPrepare Cache on PYRAMID_Automask processor : 0 mb (0)
    2023-11-22 09:43:44.995> MaskPrepare Cache on AiMasking : 0 mb (0)
    2023-11-22 09:43:44.995> MaskPrepare Cache on PYRAMID_AiMasking : 0 mb (0)
    2023-11-22 09:46:44.987> Tile Caching on PackageBitmapCPUProcessor0 (targetID 3)  : 0 bytes (0)
    2023-11-22 09:46:44.987> (Message delayed 179.993s to prevent duplicates.)
    2023-11-22 09:46:44.987> Tile Caching on AiMasking (targetID 0)  : 0 bytes (0)
    2023-11-22 09:46:44.987> (Message delayed 179.993s to prevent duplicates.)
    2023-11-22 09:46:44.987> Tile Caching on PackageBitmapCPUProcessor0 (targetID 3)  : 0 bytes (0)
    2023-11-22 09:46:44.987> Tile Caching on PackageBitmapGPUProcessor0 (targetID 3)  : 15368320 bytes (2)
    2023-11-22 09:46:44.987> Tile Caching on PackageBitmapGPUProcessor0 (targetID 3)  : 95117216 bytes (2)
    2023-11-22 09:46:44.987> Tile Caching on PackageBitmapGPUProcessor0 (targetID 3)  : 160919040 bytes (16)
    2023-11-22 09:46:44.987> Tile Caching on PackageBitmapGPUProcessor0 (targetID 3)  : 13096512 bytes (1)
    2023-11-22 09:46:44.987> Tile Caching on PackageBitmapGPUProcessor0 (targetID 3)  : 57212928 bytes (1)
    2023-11-22 09:46:44.987> Tile Caching on PackageBitmapGPUProcessor0 (targetID 3)  : 74067488 bytes (2)
    2023-11-22 09:46:44.987> Tile Caching on PackageBitmapGPUProcessor0 (targetID 0)  : 4595200 bytes (1)
    2023-11-22 09:46:44.987> Tile Caching on PackageSamplerProcessor0 (targetID 0)  : 0 bytes (0)
    2023-11-22 09:46:44.987> Tile Caching on AiMasking (targetID 0)  : 0 bytes (0)
    2023-11-22 09:46:44.993> MaskPrepare Cache on CreateProxies1 : 0 mb (0)
    2023-11-22 09:46:44.993> MaskPrepare Cache on PackageBitmapCPUProcessor0 : 3 mb (68)
    2023-11-22 09:46:44.993> MaskPrepare Cache on PackageBitmapGPUProcessor0 : 79 mb (33)
    2023-11-22 09:46:44.993> MaskPrepare Cache on PackageSamplerProcessor0 : 2 mb (5)
    2023-11-22 09:46:44.993> MaskPrepare Cache on PYRAMID_PackageBitmapCPUProcessor0 : 13 mb (21)
    2023-11-22 09:46:44.993> MaskPrepare Cache on PYRAMID_PackageSamplerProcessor0 : 0 mb (0)
    2023-11-22 09:46:44.993> MaskPrepare Cache on PYRAMID_PackageBitmapGPUProcessor0 : 0 mb (0)
    2023-11-22 09:46:44.993> MaskPrepare Cache on VariantProcessHelper : 0 mb (0)
    2023-11-22 09:46:44.993> MaskPrepare Cache on Automask processor : 0 mb (0)
    2023-11-22 09:46:44.993> MaskPrepare Cache on PYRAMID_Automask processor : 0 mb (0)
    2023-11-22 09:46:44.993> MaskPrepare Cache on AiMasking : 0 mb (0)
    2023-11-22 09:46:44.993> MaskPrepare Cache on PYRAMID_AiMasking : 0 mb (0)
    2023-11-22 09:49:44.984> Tile Caching on PackageBitmapCPUProcessor0 (targetID 3)  : 0 bytes (0)
    2023-11-22 09:49:44.984> (Message delayed 180.002s to prevent duplicates.)
    2023-11-22 09:49:44.984> Tile Caching on AiMasking (targetID 0)  : 0 bytes (0)
    2023-11-22 09:49:44.984> (Message delayed 180.002s to prevent duplicates.)
    2023-11-22 09:49:44.984> Tile Caching on PackageBitmapCPUProcessor0 (targetID 3)  : 0 bytes (0)
    2023-11-22 09:49:44.984> Tile Caching on PackageBitmapGPUProcessor0 (targetID 3)  : 15368320 bytes (2)
    2023-11-22 09:49:44.984> Tile Caching on PackageBitmapGPUProcessor0 (targetID 3)  : 95117216 bytes (2)
    2023-11-22 09:49:44.984> Tile Caching on PackageBitmapGPUProcessor0 (targetID 3)  : 160919040 bytes (16)
    2023-11-22 09:49:44.984> Tile Caching on PackageBitmapGPUProcessor0 (targetID 3)  : 13096512 bytes (1)
    2023-11-22 09:49:44.984> Tile Caching on PackageBitmapGPUProcessor0 (targetID 3)  : 57212928 bytes (1)
    2023-11-22 09:49:44.984> Tile Caching on PackageBitmapGPUProcessor0 (targetID 3)  : 74067488 bytes (2)
    2023-11-22 09:49:44.984> Tile Caching on PackageBitmapGPUProcessor0 (targetID 0)  : 4595200 bytes (1)
    2023-11-22 09:49:44.984> Tile Caching on PackageSamplerProcessor0 (targetID 0)  : 0 bytes (0)
    2023-11-22 09:49:44.984> Tile Caching on AiMasking (targetID 0)  : 0 bytes (0)
    2023-11-22 09:49:44.984> MaskPrepare Cache on CreateProxies1 : 0 mb (0)
    2023-11-22 09:49:44.984> MaskPrepare Cache on PackageBitmapCPUProcessor0 : 3 mb (68)
    2023-11-22 09:49:44.984> MaskPrepare Cache on PackageBitmapGPUProcessor0 : 79 mb (33)
    2023-11-22 09:49:44.984> MaskPrepare Cache on PackageSamplerProcessor0 : 2 mb (5)
    2023-11-22 09:49:44.984> MaskPrepare Cache on PYRAMID_PackageBitmapCPUProcessor0 : 13 mb (21)
    2023-11-22 09:49:44.984> MaskPrepare Cache on PYRAMID_PackageSamplerProcessor0 : 0 mb (0)
    2023-11-22 09:49:44.984> MaskPrepare Cache on PYRAMID_PackageBitmapGPUProcessor0 : 0 mb (0)
    2023-11-22 09:49:44.984> MaskPrepare Cache on VariantProcessHelper : 0 mb (0)
    2023-11-22 09:49:44.984> MaskPrepare Cache on Automask processor : 0 mb (0)
    2023-11-22 09:49:44.984> MaskPrepare Cache on PYRAMID_Automask processor : 0 mb (0)
    2023-11-22 09:49:44.984> MaskPrepare Cache on AiMasking : 0 mb (0)
    2023-11-22 09:49:44.984> MaskPrepare Cache on PYRAMID_AiMasking : 0 mb (0)
    2023-11-22 09:52:44.988> Tile Caching on PackageBitmapCPUProcessor0 (targetID 3)  : 0 bytes (0)
    2023-11-22 09:52:44.988> (Message delayed 180.003s to prevent duplicates.)
    2023-11-22 09:52:44.988> Tile Caching on AiMasking (targetID 0)  : 0 bytes (0)
    2023-11-22 09:52:44.988> (Message delayed 180.003s to prevent duplicates.)
    2023-11-22 09:52:44.988> Tile Caching on PackageBitmapCPUProcessor0 (targetID 3)  : 0 bytes (0)
    2023-11-22 09:52:44.988> Tile Caching on PackageBitmapGPUProcessor0 (targetID 3)  : 15368320 bytes (2)
    2023-11-22 09:52:44.988> Tile Caching on PackageBitmapGPUProcessor0 (targetID 3)  : 95117216 bytes (2)
    2023-11-22 09:52:44.988> Tile Caching on PackageBitmapGPUProcessor0 (targetID 3)  : 160919040 bytes (16)
    2023-11-22 09:52:44.988> Tile Caching on PackageBitmapGPUProcessor0 (targetID 3)  : 13096512 bytes (1)
    2023-11-22 09:52:44.988> Tile Caching on PackageBitmapGPUProcessor0 (targetID 3)  : 57212928 bytes (1)
    2023-11-22 09:52:44.988> Tile Caching on PackageBitmapGPUProcessor0 (targetID 3)  : 74067488 bytes (2)
    2023-11-22 09:52:44.988> Tile Caching on PackageBitmapGPUProcessor0 (targetID 0)  : 4595200 bytes (1)
    2023-11-22 09:52:44.988> Tile Caching on PackageSamplerProcessor0 (targetID 0)  : 0 bytes (0)
    2023-11-22 09:52:44.988> Tile Caching on AiMasking (targetID 0)  : 0 bytes (0)
    2023-11-22 09:52:44.988> MaskPrepare Cache on CreateProxies1 : 0 mb (0)
    2023-11-22 09:52:44.988> MaskPrepare Cache on PackageBitmapCPUProcessor0 : 3 mb (68)
    2023-11-22 09:52:44.988> MaskPrepare Cache on PackageBitmapGPUProcessor0 : 79 mb (33)
    2023-11-22 09:52:44.988> MaskPrepare Cache on PackageSamplerProcessor0 : 2 mb (5)
    2023-11-22 09:52:44.988> MaskPrepare Cache on PYRAMID_PackageBitmapCPUProcessor0 : 13 mb (21)
    2023-11-22 09:52:44.988> MaskPrepare Cache on PYRAMID_PackageSamplerProcessor0 : 0 mb (0)
    2023-11-22 09:52:44.988> MaskPrepare Cache on PYRAMID_PackageBitmapGPUProcessor0 : 0 mb (0)
    2023-11-22 09:52:44.988> MaskPrepare Cache on VariantProcessHelper : 0 mb (0)
    2023-11-22 09:52:44.988> MaskPrepare Cache on Automask processor : 0 mb (0)
    2023-11-22 09:52:44.988> MaskPrepare Cache on PYRAMID_Automask processor : 0 mb (0)
    2023-11-22 09:52:44.988> MaskPrepare Cache on AiMasking : 0 mb (0)
    2023-11-22 09:52:44.988> MaskPrepare Cache on PYRAMID_AiMasking : 0 mb (0)
    0
  • Brian Jordan
    Moderator

    Jerry C Walter Rowe

    After Walter's post I looked for a way to go back and test for exact numbers.  It was difficult as I've upgraded everything here and don't have anything like a test environment.  I did find a catalog containing 1811 photos on a LaCie (2TB, HDD - not SSD).  Images dated to a trip last year so 16.2, maybe 16.1.  40 MPx images from a Fuji with a handful of exported JPEGs thrown in.  No external XMP files.  No ratings, color tags, keywords, etc.  Just a straight backup of images made on a trip.

    I imported the catalog into 16.3 with Use Legacy Photos checked and the catalog took a negligible amount of time to open.  Minutes(?).  I didn't time it.  My intention was to test the time to rebuild previews when changing that setting in Settings.

    Note, there is a popup when opening the catalog asking if I wanted to UPGRADE (the catalog) or cancel.  As I hadn't changed the settings yet, I clicked cancel which ended the open.  I then changed the field in Settings, opened the catalog again and clicked UPGRADE.

    I'll also note that the Activities window did not open automatically.  I had to open it via Windows > Activities.

    After open, I unchecked the Use Legacy Preview Format option and regenerated previews.  14 minutes and some seconds.

    • 2021 MacBook Pro M1
    • 16 GB RAM
    • LaCie Rugged 2TB USB 3.0 external Hard Drive connected via an Aukey USB 3.0 acapter

    Settings > Prefer Sidecar XMP over Embedded Metadata is selected (don't know if this makes any difference but maybe)

    I assumed that moving to a M2 with (what?) 128 GB RAM and fast external drives would be significantly faster but 1) I've never used an M2, and 2) should not have made that assumption.  I tried to take my memory of the size of each of their catalogs and my memory of how long it took to complete and do some quick math to adjust that to time per 10K.  That was a bridge too far and I should not have gone there.

    0
  • John Friend
    Top Commenter

    After heating up my office due to all the Watts that Capture One is burning with it's non-stop CPU usage, I'm trying to exit the program and it won't exit.  I'm going to have to kill it from the Task Manager.  Things are completely busted when trying to use my existing catalog. 

    I've burned far, far too much time on this trying to make this new version work with my existing catalog.  Perhaps I'll just ask for a refund.  The frustration of dealing with a support ticket does not sound fun and the confidence that anything will even get fixed via support is even lower.

    0
  • John Friend
    Top Commenter

    Official support request filed as the problem does not seem to go away and editing my existing catalog in 16.x is so laggy due to all the background CPU consumption that its not practical and the program won't even properly exit when I try to shut it down.  Log files show Capture One doing something over and over again, even when it's minimized and not visible.  It's not building previews because neither drive containing the RAW files or the previews are being accessed by anyone during this CPU usage loop.

    0
  • Walter Rowe
    Moderator
    Top Commenter

    Have you shut down cold and rebooted? I wonder if there is some process(es) hung in the background that needs to be shut down for things to run smoothly.

    0
  • John Friend
    Top Commenter

    Walter Rowe

    That was a good thing to try, but it did not make any difference.  Still the same problem after a complete reboot.

    0
  • Jerry C

    I am on version 16.2 contemplating an upgrade to 16.3. I regenerated previews on 1636 images at the 5K resolution recommended for my 5K display. My images are heavily edited. It took 17 min which extrapolates to a bit over 11 hrs for my 65,000 image catalog, very similar to Walter Rowe's experience. I am using an M2 Mac Studio with 128 GB RAM and an external OWC NVME SSD with the catalog and referenced files. 

    During the regeneration process, I noticed a trivial reduction in the otherwise absolutely smooth display of slider adjustments. I did not try exporting and cannot comment on that. So my big concern is not the effect of regeneration running in the background if it does so in the same way when upgrading to 16.3.

    Regeneration of previews is not designed to be an interruptible process. My concerns is what might happen if the process were interrupted, e.g., by a power interruption that exceeds my backup power supply capacity. If the process is interrupted by a power failure or a pinwheel of death scenario, this would seem to be the equivalent of a force quit and could produce a problem like Brian Jordan reported and John Friend experienced. 

    So, I have questions that really should be part of the installation instructions. I do not want to assume just because warnings were absent, there are no problems. So,

    • What will happen with a power failure? Will the catalog likely be rendered unusable?
    • Has part of the pre-release testing process tested what a power failure or manual force quit would do? If so, what were the results.
    • Must users who upgrade the catalog make a copy of the catalog, first? This is probably always a good idea.
    • Assuming the catalog is completely undamaged after a power failure or force quit, will the regeneration process resume either where it left off or skip all ready regenerated previews? If not, should regenerating previews be done in batches that take no more time that one would want to waste to redo that batch?
    • Could Capture One include advice in the installation instructions regarding best practices for upgrading a catalog and how to mitigate these issues?

     

    0
  • Walter Rowe
    Moderator
    Top Commenter

    Previews are stored as separate files outside the catalog database but within the catalog folder package in a subfolder called Cache. It contains previews (proxies) and thumbnails. That can be interrupted without issue. I've even force quit that process before and it picked up where it left off later. I think there is little updating to the catalog database during preview generation.

    0
  • BeO
    Top Commenter

    Hi John Friend

    I can somehow reproduce the high CPU usage between 20+ and 40+ %.

    I have a session (<300images), not a catalog, which I upgraded from 15.2 to 16.3.1. The high CPU usage occurs for some NEF images, not for others. What I mean is that it only occurs when I have one of the concerned images in the viewer, it does never occur when the viewer is hidden and only the browser is shown, and it does not occur either when both the viewer and the browser are shown. Can you confirm this?

    I first thought it has to do with the previews, old or new (regenerated for selective images (F5) vs. old preview .cop files), setting of old format in the preferences or quality vs. speed previews.

    But I could not find a common denominator.

    It think it has also to do with the caching of previews in main memory, because some images which are not concerned can be concerend when I load them via the "next" button.

    If I have a concerned image I can always stop the CPU from heating my room by bringing the browser (alt+b) in addition to the viewer, or toggle to the full browser (G). If I toggle back to the full viewer, sometimes CPU starts again for some images, but not so for those which are rarely concerned. But loading the previous image into the viewer (from the full browser by double-click) and then select "next" image can start the CPU for a less often concerned image again.

    So, in my case it seems to be a combination of the full viewer (without browser, but tool bar was always open), and how I "approached" an image. And it was always in a "system folder" in the lib tool (called "Capture" but from a different session, don't know if that matters).

    On a copy of some of the images in a new folder (no old previews, thumbnails and stuff) I did not observe the CPU going crazy.

    My log files didn't show relevant information imo.

    Hardly a test which would suffice to create a bug report, hard to reproduce, not sure I listed all preconditions, but my gutt feeling is I need at least to generate a preview of an old image before it can become an image which is powering the CPU if in viewer only mode.

    If my post is confusing that's because my brain is confused right now too.

     

    0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.