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. ⚠️

Weird Interface Delay

meanwhile
Hi all,

Have a weird interface delay here in catalog mode. C1 9.1.1 (and earlier).
To try and narrow down the issue, I've removed all user collections, and smart albums.

Library Tab takes 7 secs to load.
Click on Colour tab.
Colour tab takes 7 secs to load.
Click back to Library tab.
Library tab takes 7 secs to load.

This is even without any images or directories in the catalog selected.

The Library tab only has the Library tool, nothing else.
The Color tab has only Base Characteristics, White Balance, and Color Editor.
The other tool tabs load quickly enough.

System is Mac Mini, 2.6GHz i7, 16GB RAM, all SSD drives. C1 only app running.

What's taking so long? What is being done in those 7 secs?

Thanks!
0

Kommentare

15 Kommentare

Datum Stimmen
  • SFA
    [quote="meanwhile" wrote:
    Hi all,

    Have a weird interface delay here in catalog mode. C1 9.1.1 (and earlier).
    To try and narrow down the issue, I've removed all user collections, and smart albums.

    Library Tab takes 7 secs to load.
    Click on Colour tab.
    Colour tab takes 7 secs to load.
    Click back to Library tab.
    Library tab takes 7 secs to load.

    This is even without any images or directories in the catalog selected.

    The Library tab only has the Library tool, nothing else.
    The Color tab has only Base Characteristics, White Balance, and Color Editor.
    The other tool tabs load quickly enough.

    System is Mac Mini, 2.6GHz i7, 16GB RAM, all SSD drives. C1 only app running.

    What's taking so long? What is being done in those 7 secs?

    Thanks!


    Have you had a look in the log files to see if any activity is being recorded?



    Grant
    0
  • meanwhile
    Good thinking. Nope, nothing being recorded in the logs. Does C1 have a verbose log mode?
    0
  • SFA
    [quote="meanwhile" wrote:
    Good thinking. Nope, nothing being recorded in the logs. Does C1 have a verbose log mode?


    Possibly - some of the perpetual log files for my Windows system are enormous! No idea if it is switchable though.

    Sounds odd.

    Any anti-virus or system admin stuff possibly kicking in?

    Have you already checked to see what happens if you reboot the system?

    I'm wondering whether you should consider a re-install but I'm not a Mac person at all. It just seems to be a common approach to problems on a Mac, presumably for good reasons. Windows seems to live with some deficiencies but doesn't necessarily let on that it is not performing at full health until it grinds to a complete halt.


    Grant
    0
  • meanwhile
    I'm wondering whether you should consider a re-install but I'm not a Mac person at all. It just seems to be a common approach to problems on a Mac, presumably for good reasons. Windows seems to live with some deficiencies but doesn't necessarily let on that it is not performing at full health until it grinds to a complete halt.


    It's unlikely that re-installing would do anything for this.

    presumably for good reasons


    Not really, most of the time. 😊
    0
  • Grant Hodgeon
    This happens to me sometimes on the mac, too. I've never had it happen often enough to try and debug the issue but typically an entire operating system restart solved it entirely. So it might be something akin to a memory leak. I wonder if there's more voices to add to the mix.
    0
  • meanwhile
    I've put in a support case on it.
    0
  • Mike Conley
    This happens consistently to me, ever since I updated to 9.1.1. It drives me nuts, and makes working in C1 a drag.

    I filed a support case on it, and have submitted timing samples as part of my submission. If you understand Xcode and its tools, I'd suggest you do the same, so that they have a clearer picture of how processor time is being spent.
    0
  • meanwhile
    I'll see if they ask me to send through anything else.

    I could kind of get why it might happen with the Library tab, not that I'd be happy with that happening every time like it does now, but the Color tab has me scratching my head.
    0
  • meanwhile
    Actually it's not just the Library and Color tab. It's whatever tab you move to after the Library tab. It seems to be doing a whole bunch of stuff on loading the Library tab, and on unloading the Library tab.

    Tried new user, reinstall, etc. Didn't help.
    0
  • MikeNYC
    Have you tried removing CAPTURE PILOT from the Camera tab? I've seen Capture Pilot tool's existence to cause "beachball" temporary lockups, even when not using Capture Pilot, when not connected to a network.
    0
  • HansB
    [quote="MikeNYC" wrote:
    Have you tried removing CAPTURE PILOT from the Camera tab? I've seen Capture Pilot tool's existence to cause "beachball" temporary lockups, even when not using Capture Pilot, when not connected to a network.


    If it is caused by the 'Capture Pilot' tab when not connected to a network, it may be solved just by 'Turn off Wi-Fi'. Worked for me, without removing the tool.


    Regards,
    Hans
    0
  • MikeNYC
    [quote="HansB" wrote:
    [quote="MikeNYC" wrote:
    Have you tried removing CAPTURE PILOT from the Camera tab? I've seen Capture Pilot tool's existence to cause "beachball" temporary lockups, even when not using Capture Pilot, when not connected to a network.


    If it is caused by the 'Capture Pilot' tab when not connected to a network, it may be solved just by 'Turn off Wi-Fi'. Worked for me, without removing the tool.


    Regards,
    Hans


    Hans - I've found that sometimes the Capture Pilot delay bug can be caused when the Mac is creating an ad-hoc network and has an iPad connected, in addition to when not connected to a network. Starting Capture Pilot then removing the tool works in that case...Capture Pilot keeps running, despite the controls being hidden, and the UI returns to its normal responsive state.
    0
  • dale11833
    This delay happens to me randomly in C1 8 as well. It's so annoying when I'm on-set, tethered, trying to navigate and there's a delay. WHY IS THIS HAPPENING PHASE ONE???
    0
  • HansB
    [quote="MikeNYC" wrote:
    [quote="HansB" wrote:
    [quote="MikeNYC" wrote:
    Have you tried removing CAPTURE PILOT from the Camera tab? I've seen Capture Pilot tool's existence to cause "beachball" temporary lockups, even when not using Capture Pilot, when not connected to a network.


    If it is caused by the 'Capture Pilot' tab when not connected to a network, it may be solved just by 'Turn off Wi-Fi'. Worked for me, without removing the tool.


    Regards,
    Hans


    Hans - I've found that sometimes the Capture Pilot delay bug can be caused when the Mac is creating an ad-hoc network and has an iPad connected, in addition to when not connected to a network. Starting Capture Pilot then removing the tool works in that case...Capture Pilot keeps running, despite the controls being hidden, and the UI returns to its normal responsive state.


    MikeNYC,


    I referred to 'not using Capture Pilot' in combination with 'not connected to a network'.

    I'll give it a try if I notice something like that. Until now, I never used Capture Pilot in an ad-hoc network. I am using a mobile router instead.


    Regards,
    Hans
    0
  • MikeNYC
    [quote="HansB" wrote:

    MikeNYC,


    I referred to 'not using Capture Pilot' in combination with 'not connected to a network'.

    I'll give it a try if I notice something like that. Until now, I never used Capture Pilot in an ad-hoc network. I am using a mobile router instead.


    Regards,
    Hans


    The mobile router surely is the way to go, and certainly a more stable solution than an ad-hoc network. Ad-hoc is ok in a pinch but has its limitations! I've started bringing a high powered access point (EnGenius EAP350) on set and had good success with that...just not battery powered.
    0

Post ist für Kommentare geschlossen.