Frozen GUI for effects (Raum,Choral, etc..)

System
System Posts: 44 admin
in Komplete Kontrol
This discussion was created from comments split from: KK 3.3.2 Interface very long lag when loading Kontakt instruments (KBDSW-7912).

Comments

  • Sc0ttkid
    Sc0ttkid Member Posts: 11 Newcomer

    Hi @Jeremy_NI

    Whilst the lastest update has fixed the instrument issue, it has now moved on to the effects and is causing them to freeze on the screen. As soon as I click away from the current effect and re-select it, it’s frozen.
    Raum, Phasis, Choral, Freak, Replika / XT , Bite, Dirt, Flair ….. etc are the problem effects at my end.

    Could you take a look please?
    Cheers

    Scott

  • Jeremy_NI
    Jeremy_NI Customer Care Posts: 12,284 mod

    I'm not sure this is the best way to share a vid but it does show the issue..

    IMG_4270.MOV.zip

    @Sc0ttkid I've created this new post out of where you posted. The issue seems to be different and we'd like to have a deeper look. what's your operating system? Is this happening within a DAW, in standalone? Both? What DAW is it?

  • Sc0ttkid
    Sc0ttkid Member Posts: 11 Newcomer

    Hi @Jeremy_NI ,

    Yes it's happening in both DAW ( Logic 11.0.1 ) and Standalone ( KK 3.3.3 ).

    Sonoma 14.7 M1 Max.

    Moving the window to another screen does temporarily fix it, as per the other issue but it soon returns.

    If I set up a chain of effects the ones stated above freeze as per the video, the other like RC, Driver, Solid etc are fine.

  • Jeremy_NI
    Jeremy_NI Customer Care Posts: 12,284 mod

    I still can't reproduce the issue on my side. What graphic card are you using? If you're using an external monitor, what model/brand is it? Is it a macbook, iMac? Are you able to check if this happens without external monitor?

  • Sc0ttkid
    Sc0ttkid Member Posts: 11 Newcomer

    I'm running a Mac Studio with 4 monitors. M1 Max

    Samsung S34CG50, HP 27QD, HP V22i G5, Yodoit cheap 15" Portable.

    It happens on all of them, but what is interesting is, although the graphics don't move it still changes the amount if i click and move the mouse over selected parameter.

    I'll assume i'll just have to live with it and it'll sort itself out at some point

    IMG_4280.MOV.zip

  • Jeremy_NI
    Jeremy_NI Customer Care Posts: 12,284 mod

    Can you check the graphic card? Just to see if anyone with a similar setup can reproduce the issue. You can find it on your mac's system report under Graphic/Displays.

  • Kymeia
    Kymeia NKS User Library Mod Posts: 4,724 mod

    Do Mx Macs have a dedicated graphics card? I thought graphics handling was built into the Mx chip GPUs?

  • Sc0ttkid
    Sc0ttkid Member Posts: 11 Newcomer

    it’s integrated graphics, system on chip.

  • Jeremy_NI
    Jeremy_NI Customer Care Posts: 12,284 mod

    Of course 🤦‍♂️ My bad!

  • Sc0ttkid
    Sc0ttkid Member Posts: 11 Newcomer

    Hi @Jeremy_NI

    I've had a little time to look into this and while I can't resolve it, it has opened a can of worms.

    When a NI Effects is added to an effects chain in Logic 11.01 the graphical interface only registers movement when the play head is moving, this is the same for midi and audio tracks. If you change track it reverts back to being frozen again. Using SSL 360 link with a NI effect produces the same results

    Given the fact that I can produce the same issue inside KK standalone and Logic either inside KK or standalone narrows it down to either my Mac or a glitch in the NI Software. I am unable to reproduce this out side of NI effects and given the issue relating to the instruments freezing I would hazard a guess at the latter.

    Do you have any recommendations for other avenues to try ?

    Thanks

    Scott

  • Sc0ttkid
    Sc0ttkid Member Posts: 11 Newcomer

    I've just rolled my KK back to 2.96 and everything works fine both in KK standalone and KK in Logic. zero interface freezing. The effect freezing on their own in Logic is still there unfortunately

    Could you send me a link to a previous version of KK please? maybe a couple back from 3.3.3.

    I suspect some where between 2.96 and 3.3.3 the issue was introduced

    Cheers

Back To Top

Categories