Straylight Suddenly Using Way More CPU Than Before?

REMNANT.exe · 2022-10-07T00:05:00+00:00

There was an error rendering this rich post.

I got Straylight at the beginning of the year, and it ran beautifully in Logic Pro, even in large projects with 80+ tracks.

Now, something has changed in the last few months, and I'm not sure what it was. Every time I load Straylight, playing more than 2 or 3 notes immediately creates a CPU overload, making the instrument virtually unusable. This is pretty disappointing because I really enjoy this synth and would like to use it in more productions of mine.

I use a 2019 iMac with MacOS Monterey (although the problem existed on Big Sur already)

6-core i7 processor

16GB RAM

Another weird occurrence that may or may not be related: the background colors on my Komplete Kontrol keyboard on the right screen when an instrument is loaded default to black on several instruments when it should be a different color. Reinstalling fixes temporarily but then they revert to black after a while.

Anyone else experiencing similar issues?

Find more posts tagged with

Straylight

Komplete Kontrol Keyboards

Accepted answers

REMNANT.exe

https://community.native-instruments.com/discussion/comment/35193#Comment_35193

Apologies for the late reply! So weirdly enough the problem has resolved itself. I'm not sure how or why. I was working in a session, experiencing the UI glitch and poor CPU usage of Straylight, and after closing and reopening Logic everything is back where it's supposed to be, and Straylight is back to using a normal amount of CPU now.

Will report back if the problem occurs again, but for now it's fixed! I can't recall doing anything specific to trigger the fix.

All comments

Jojo123

Too many variables in the equation to say exactly why you're getting this, but in general, some presets on Straylight and Pharlight are known to *very* CPU intensive, others are fine. I have 19' 8core iMac 40GB Ram and I get the same. 2 notes held can almost cause a thread to top out if I choose a heavy preset.

Jeremy_NI

Check that Logic, Kontakt and Komplete Kontrol have Full Disk Access: How to Enable Full Disk Access on macOS Where is Straylight installed ? On your system's drive? On an external hard drive ? What format is that drive ?

About the issue with the Komplete Kontrol screens, could you post a photo of the issue? When you say "Reinstalling fixes temporarily" do you mean reinstalling the libraries or Komplete Kontrol ?

REMNANT.exe

https://community.native-instruments.com/discussion/comment/34822#Comment_34822

Thanks for the response! I read about this when researching the issue before posting, and the weird thing is there were specific presets I could use perfectly fine 4 months ago that now are totally unusable. Really strange.

REMNANT.exe

https://community.native-instruments.com/discussion/comment/34834#Comment_34834

Went ahead and enabled full disk access and have restarted the system, and nothing seems to have changed. Nothing is stored on an external drive, but I did just discover that all my NI stuff is stored outside of the things on my drive that are being backed up by my dropbox backup service. Maybe this could be part of the issue why the images are not showing up right? Still wouldn't explain the CPU stuff because this shows clearly the whole instrument is stored on my main drive.

Attached are a few images that show the problem.

IMG_4557.jpg

IMG_4558.jpg

IMG_4559.jpg

Screen Shot 2022-10-07 at 10.16.12 AM.png

Screen Shot 2022-10-07 at 10.15.55 AM.png

Screen Shot 2022-10-07 at 10.15.46 AM.png

Screen Shot 2022-10-07 at 10.15.37 AM.png

Jeremy_NI

@REMNANT.exe Actually, it's a good thing that none of NI files or programs are backed up in a cloud service such as Dropbox.

For Straylight, you could try to batch re-save the library, as explained here: How to Batch re-save a KONTAKT Library

Jeremy_NI

@REMNANT.exe Any luck with the Batch re-save?

REMNANT.exe

https://community.native-instruments.com/discussion/comment/35193#Comment_35193

Will report back if the problem occurs again, but for now it's fixed! I can't recall doing anything specific to trigger the fix.

Quick links

Unanswered questions