Before i start, i know I’ll get loads of posts about it being rock solid. It has been for me until tonight.
Im on a MacBook Pro M1 and everything is up to date (other than JP-8 V ironically, that was one update behind the current one).
I was using the knobs and sliders on my Keystep MKII, in Arturia mode, nothing else in the Rackspace other than a Midi in and my interface.
This has never happened to me before. With any Arturia pluggins, but im now very nervious.
If someone can guide me as to how to find and upload the crash log im happy to do this. If anyone has any idea what i can look at as to why this happened please let me know.
Thanks. I followed that and there was nothing showing.
EDIT: I think I did it wrong, I’ll have another look tonight. I looked just as I was leaving for work.
Is it ok to cut and paste it here or should I upload it as a zip file?
Nope. There is nothing there. I had a look on my Mac mini at work and i can see a couple of crash reports from other programs, so looked in the same place on my MBP which has GP on it but the list is empty.
I don’t normally use real time control on my sounds liek this This was just a manual filter sweep. Didnt happen all the time, but im nor going to risk it. I normally use Zenology for that sound and don’t have any issues, but i thought id try JP-8 as i found a more suitable tone.
There are no issues using the Plugin as stand alone so im not getting in to blame ping pong. Arturia will say if its not doing it in stand alone its not their software etc. I’ll go back to using Zenology Pro if i have to.
Im not aksing for help here, just wanted to flag this up for reference.
Standalone and plugin are 2 different piece of software.
Why not help Arturia to improve their software in sending them the crash report.
In the past they have been very responsive when they got a crash report.
Sigh - there’s no ping pong - we don’t play the blame game – if it was our fault, we would immediately own and address it - but it’s clear from the stack trace that it’s an Arturia issue.
We have a VERY good relationship with Arturia, they have our host for Q/A so if you let them know about this issue, they will look into it, possibly contacting us if ncessary.
Nonsense. That’s like arguing that if their plugin works in their standalone mode (which is basically just a very trivial plugin host, by the way) then if it breaks in any DAW it must be the DAW’s fault.
Ive got a workaround. Thats good enough for me for now. I don’t have the time or inclination to fault find this, especially when my knowledge of Macs is still very basic and i don’t wan to change anything as everything else is working.
In no way am i suggesting its GP thats at fault, but ive been palmed off with other software companies in the past and ended up giving up as each company said to contact the other.
Feel free to bring this up with Arturia if you want. If it happens again I’ll email them but for now im not bothering.
I have contracted them about a Minifuse1 not behaving itself and got told it’s normal, and yet its never happened to any of the other interfaces ive been using.
I told you it was a waste of time. not going to help at all.
This is what I got back.
"Thank you for reaching out and sorry for the inconvenience
We developed our instruments to be used with the following Platform specifications:
Windows
Win 10+ (64bit)
4 GB RAM
4 cores CPU, 3.4 GHz (4.0 GHz Turbo-boost)
32GB free hard disk space
OpenGL 2.0 compatible GPU
ARM processors not supported on Windows
Apple
Mac OS 10.13+
4 GB RAM
4 cores CPU, 3.4 GHz (4.0 GHz Turbo-boost) or Apple Silicon CPU
32GB free hard disk space
OpenGL 2.0 compatible GPU
===>>> For more information about the compatible DAWs, I invite you to take a look at the following link:
I’m really sorry, but there isn’t official compatibility with GigPerformer 5 and unfortunately, we cannot guarantee that our softwares will function smoothly in that environment.