Crash! đŸ’„ Please Help!

General discussion about Gig Performer
22

Reason Racks is crashing

23

I see that. Just wanting to know why.

24

Us too
.you’d have to ask Reason!

But it’s not a GP bug


Note that this exact issue has been reported here before

25

So again, brand new to this
.so I won’t use Reason anymore
.and another person said not to use multiple versions of Kontakt, and another said Korg was buggy. These are the main plug ins I use for making my original sounds. I can do without Reason in GP as I only used it for effects. But Kontakt and Korg are my main ones. This is beginning to worry me

26

I wonder if you’re confusing multiple “versions” with multiple “inserts”.

What I meant by multiple versions, you shouldn’t use version 7 and version 8 and/or you shouldn’t use multiple formats (e.g., both VST and AU). Pick one version and one format and then use them as needed.

Remember, we were just guessing at the possible issues given that you hadn’t provided us with a crash report. Kontakt is pretty solid. Reports have been posted about bugs in some Korg plugins but Korg is pretty good at fixing them. But at this point, the actual issue seems to be with Reason though I don’t know what “IndexingThread” error means. You’re not running out of RAM by any chance, are you?

27

No. I mean I only have 16g but it’s been plenty for other ram hungry DAW’s. I do monitor CPU usage and my racks don’t seem to be even close to maxing out CPU in any way

28

I wasn’t asking about CPU - I was asking specifically about RAM.

Not talking about the host - I’m talking about how RAM is being taken up by plugins. DAWs are different - for example, you can freeze tracks which stores the audio and so plugins temporarily not needed can be swapped out by the OS. You cannot do that with a real-time live performance host since you generally need to have access to all plugins at any time. If your system is not showing indications about being out of RAM, that’s good.

But again, I am just trying to cover all the possibilities. But a google search also suggested that an “IndexingCrash” can be due to a problem with Spotlight indexing. I don’t know if that’s true, nor why it would show up in the Reason plugin but I would certainly suggest disabling Spotlight. One really doesn’t want ANY unnecessary applications running when running a real-time live performance app.

Someone in another post found the following:

A crashed “IndexingThread” on macOS usually indicates a failure in the Spotlight metadata indexing process (“mds” or “mds_stores” processes), which often results in broken search functionality, high CPU usage, or system slowdowns. This is frequently caused by a corrupted index, a problematic file, or external drive issues.

29

How do I monitor RAM usage? And correct I have had no notifications of any kind having to do with RAM. Spotlight you speak of, how do I disable that?

30
31

OK - let’s not go so fast – you’ve removed Reason (and hopefully reported the issue to them) and you have presumably ensured that you are only using one version of Kontakt so please just do some more thorough testing to see how it goes.

32

Please report to the Reason support. You can send them this thread or just the log.
(Some plugin developers are relatively quick to fix bugs)

33

I’ve never had crashes with Kontakt or Korg plugins. Korg plugins (e.g. Triton and Triton Extreme) are CPU hungry so be careful if you layer them. I am using VST3 format for my plugins and rackspaces.

Yes, do not use multiple versions of Kontakt.