Plugin (Sequis) loading in a very strange graphics

lukasztab

Hi dear Community

i never had this problem before but the plugin (Sequis) is loading with a very strange graphics - see attached jpg. This happens both if I run this in Ableton via Kontakt as well as Komplete Instruments. It loads ok in standalone instances.

Doesn't happen to any other KI plugin. And I reinstalled the plugin already and it didn't work.

Any ideas or word of advice?

Thank you!

lukasztab

Thank you both for your responses and help!

Things seem to be working now -- I've done the steps above, but also my hypothesis is that Output Audio not being set/available was possibly causing the issue.

Thanks again, appreciated.

Uwe303

Hello,

can you check if both, stand alone and plugin are the same version, click on the floppy disk logo then help/about, must be 7.5.2.

lukasztab

Thanks @Uwe303 I'm afraid I dont see the help/about option when I click on the floppy disk... any other way to check the version of the plugin?

lukasztab

managed to check - yes both are 7.5.2...

Jeremy_NI

@lukasztab Open Kontakt in standalone and make sure to select a Core Audio sound card driver. Make sure to give full disk access to Kontakt, Komplete Kontrol and your DAW: How to Enable Full Disk Access on macOS

If that didn't solve the issue. Did you reinstall Kontakt or Sequis? I would recommend deleting the library folder and uninstall Sequis as explained here: How to Uninstall Native Instruments Software from a Mac Computer

Then install Sequis again.

Jojo123

Hello,

Sometimes, when Im just trying stuff out, I'll have a number of NI plugins loaded. Some of these I may disable (in Logic) to save resources. Some time down the track I may decide to save the project. When I load the project in again, anything that was disabled will have graphics like that. When I enable them all is well.

Sequis looks exactly like that if its disabled (in Logics track header). Hope that helps.

lukasztab

Thank you both for your responses and help!

Things seem to be working now -- I've done the steps above, but also my hypothesis is that Output Audio not being set/available was possibly causing the issue.

Thanks again, appreciated.