Here is what came up after running the comand:
1fbda90a1c8316e87a9c019dd24440df9959a43146c6ee9c346ac51560beb594a5cf92a11f946bad0f94230d7892a2a638975a5e1b77690a5af8c825a14eba2b /Applications/GigPerformer4.app/Contents/MacOS/GigPerformer4
Here is what came up after running the comand:
1fbda90a1c8316e87a9c019dd24440df9959a43146c6ee9c346ac51560beb594a5cf92a11f946bad0f94230d7892a2a638975a5e1b77690a5af8c825a14eba2b /Applications/GigPerformer4.app/Contents/MacOS/GigPerformer4
ok - that’s the correct value - I wanted to make sure your executable wasn’t corrupted in some way.
We will continue to think about how to debug this issue and be in touch.
If you can find a way to reproduce the problem, that would be awesome.
Are you using scripting?
I can’t reproduce it because it seems to occur randomly.
I’ve been thinking about the fact that I share the same type of bug with Miguel and I wonder if a plugin we both use (in fact it was Miguel who recommended it to me) could be responsible for the problem.
The plugin in question is nvMeter2. I have it in Global Rackspace, controlled by widget in all individual rackspaces.
Could it be the culprit?
Yes, I use a simple script I found here in community, in some rackspaces, to force kontakt to play a mute note when that rackspace is activated.
Can you post that script please?
Sure.
The script is:
var MIN : MidiInBlock
on Activate
PlayNote(MIN, // Handle to the MidiInBlock connected to Kontakt
C3, // Played Note
1, // Velocity
1, // Midi Channel
0, // Delay in ms before note is played
10) // Duration of played note in ms
end
And the subject discussionn can be found here:
https://community.gigperformer.com/t/first-note-out-of-kontakt-is-delayed/1005/18
OK - that shouldn’t be causing any issues
It’s Intel on intel machine
I just had another crash, while rehearsing… not doing anything within the software… just playing
This is what my terminal command came up with
ac26dfe360b37e05312e37ad01ff2f124c3da06952661d683644589d43c60e6a668f7719727beae264565e7c3ed6f71c28e40bce413bb1dab57be7090c373e57 /Applications/GigPerformer4.app/Contents/MacOS/GigPerformer4
Did you enable WLAN on your machine?
Just now, so I can upload any information you may ask for
My question was if WLAN was enabled while the crash occurred?
Can you please upload the crash report that you got at the rehearsal?
NO WLAN active at any time… only now to contact GP community.
GigPerformer4-2024-03-19-144924.ips.zip (39.2 KB)
I think we’re going to have to prepare a special build for both of you to try and figure out what the heck is going on here. We appreciate your patience. It’s very strange.
Salomao and I have been in contact and have found that we share some plugins, other than nvMeter2
Korg M1
Korg Triton Extreme
Kontakt
Serum …
Has anybody else had any issues with any of these?
I’d be skeptical of the Korg stuff, I’ve seen issues with them - do you have the latest versions (and presumably properly licensed versions) ?
Not in the case of Triton EXTREME (sorry! Downloaded just for the sake of comparing it with the real keyboard and it ended up in my library permanently. Never had any issues until now though.)
Having the licensed version, would that be a possible solution to any issues here or are the legitimate version crafty, too?
I have no idea — I know there were some issues with older versions of that plugin but I don’t use those plugins myself.
Not sure I understand. Were you using an unlicensed or cracked version? If so, it wouldn’t surprise me if those plugins detected tampering and just killed the host.
TBH, it is a cracked version but I never had any issue with it until now … I only downloaded to compare but I ended up using it with MainStage and left the real thing at home.
May have to go back to lugging the real thing around.
Well… I’m going to start by looking for sounds to exchange with the triton ones I’m currently using.
The Triton collection is only $249 but if there’s no real guarantee that it’ll solve the issue (IF this is the culprit)
Thanks again
If a plugin has been cracked, there is absolutely no guarantee that it will work properly. All bets are off.
As I mentioned earlier, from the crash report we saw, it looked like something was killing the host and it may very well have been that plugin.