Hi. There’s a message that appears when loading either MIDI Guitar 3 (MG3) for the first time in a Gig Performer 5 (GP5) session or loading a .gig file containing MG3.
It’s truly a minor annoyance but there is a system level message requesting to allow GP5 to access data from other applications. In macOS settings I’ve allowed full disk access for GP5 and MG3 but I still get the message.
Simply clicking “Allow” solves the issue but it introduces another “uneccessary” step in launching a project and that’s undesirable.
This hasn’t happened with other plugins so it could be an MG3 issue and I’ll raise it with the Jam Origin dev. But, Ableton Live 12 doesn’t trigger the message under the same conditions so it may be a GP5 anomaly.
I’m just asking here to make sure I’m not missing some obvious setting. Any ideas? Thanks.
We can’t provide support for third party plugins unless we can establish that the problem is due to Gig Performer itself in which case we try to fix the issue ASAP.
That message you’re seeing is probably emanating from that plugin (the evidence being that no other plugin causes this issue) and since MG3 is still in beta we would refer you to Jam Origin for support. That said, this issue may have already been solved by them. Please see this recent discussion on our forum
I appreciate that, and I’ve already taken it up with Jam Origin as I am involved in their pre-beta release testing. But to add to/amplify the possibility that it might be a Gig performer issue, minutes ago I disallowed full disk acess for Ableton Live 12 and then Live also started exhibiting the same behaviour – requesting access. After I re-enbable full disk access the message disappeared. But when either allowing/disallowing full disk access for Gig Performer, the message appears in either state.
Yes, I’m assisting this same user on the Jam Origin forum regarding the MIDI PC issue and I think we’re close to a solution. But that is unrelated to the privacy/permissions issue.
There is no such issue with MG2. But I think we’re comparing apples and oranges, so to speak because there is no “allow” request issued when loading MG2 in any host/DAW. It’s not a thing.
I can solve the MG3 “allow” permission request issue in Bitwig 5, Max 8, Live 12 and Blue Cat Audio’s PatchWork simply by allowing full disk access in macOS. At this moment, Gig Performer 5 is the only environment that is not respecting the full disk access I’ve turned on in the macOS security settings.
Anyway, if you’re 100% convinced it’s not a GP5 thing, I’ll elevate my discussions with JO. But, just out of interest, are you aware of any other plugins that trigger this “allow” request? I have a sneaking suspicion that it might have something to do with the MIDI/audio networking implementation in MG3 but I’m not certain yet.
I have not seen this before and the fact that it does not happen with MG2 and Gig Performer yet it happens with MG3 and Gig Performer would clearly be indicative of an issue with MG3 since that’s the only thing that is different.
I have a thought. I remember having an issue a bit like this when testing an earlier beta version of GP, getting prompted multiple times for permission and this only happened after I “upgraded” (sigh) to Sequoia.
Turns out the reason I kept getting prompted was because, at the time, that beta was not code signed. Once I added code signing to the build, then problem went away.
I wonder if MG3 is not code signed? That might be the issue.
Thanks, I’ll raise that with JO but I thought that applications that are not code signed required some additional permissions to be activated manually when installed. I have not experienced that with MG3. But I’m using a pre-release version different to the public release so maybe it’s not code signed like the regular beta.
Still, this could be a good lead. But I would reiterate the point that allowing full disk access to GP5 does not negate the issue as it does with the other DAW/host applications that I mentioned.
Thanks again. I’ll report back if I discover any useful info.
Interesting. I never had an issue with this on my Macbook M1 Pro running the latest Sequoia. Full Disk Access was given from the start and it never popped up.
