jb@bmbcon.demon.nl

I have a Mac standalone made with Max 8.2.0 which uses an audio input (actually from loopback) and an external USB camera (to trigger things).

It's working fine. But as it needs to run for a long time (months) in an installation, I would like to launch it automatically when the computer starts up (as a Login item). This works, but during the startup process, dialog boxes appear asking for permission for "... MSP to capture audio from the microphone." and to "Allow Jitter to capture video". Which need to be clicked on.

I thought that the computer (mac mini running 10.13.4) would learn that it's ok for the app to do this (it appears in and stays in the relevant lists in the Security control panel). but these dialogs appear EVERY TIME.

Launching the standalone app on my laptop (OS 12.1) displays the same behaviour, so I don't think it's just an OS thing.

I've done this kind of thing before and can't remember ever having this problem.

Hi there,
I have a Mac standalone made with Max 8.2.0 which uses an audio input (actually from loopback) and an external USB camera (to trigger things).

It's working fine. But as it needs to run for a long time (months) in an installation, I would like to launch it automatically when the computer starts up (as a Login item).  This works, but during the startup process, dialog boxes appear asking for permission for "... MSP to capture audio from the microphone." and to "Allow Jitter to capture video". Which need to be clicked on.

I thought that the computer (mac mini running 10.13.4) would learn that it's ok for the app to do this (it appears in and stays in the relevant lists in the Security control panel). but these dialogs appear EVERY TIME. 

I've done this kind of thing before and can't remember ever having this problem. 

Hi there,
I have a Mac standalone made with Max 8.2.0 which uses an audio input (actually from loopback) and an external USB camera (to trig

standalone-mac-permissions-launch-problem

Interested in resolving this permissions issue also.

Actually I'm talking to support about it now.

Going back to Max 8.1.11 and making the standalone with that version solves the problem, - i only have to give permission once, then the computer remembers the permissions. so it seems to be a bug in the newer version(s). I'll post here again when I have more news about it! J

Actually I'm talking to support about it now. 

Going back to Max 8.1.11 and making the standalone with that version solves the problem, - i only have to give permission once, then the computer remembers the permissions. so it seems to be a bug in the newer version(s). I'll post here again when I have more news about it! J



if I recall correctly you can bypass this with an apple developer ID.

Once you have one, you should codesign* the app with a script.

https://stackoverflow.com/questions/13204407/how-to-codesign-an-existing-mac-os-x-app-file-for-gatekeeper

if I recall correctly you can bypass this with an apple developer ID.
Once you have one, you should codesign* the app with a script. 

Check this thread:
https://stackoverflow.com/questions/13204407/how-to-codesign-an-existing-mac-os-x-app-file-for-gatekeeper 

Thanks for the link! I'll check it out. It all seems to work anyway by using Max 8.1.11. And hopefully the bug will be fixed in a future version of Max.

 ) using max 8.1.11. Did anyone reported this issue in the bug report form?

Same here. I'm forced to export my App (https://irin.carloscaires.com/ ) using max 8.1.11. Did anyone reported this issue in the bug report form?

Anybody have any news on this? I can't even find where to download Max 8.1.11 anymore! Seems the oldest avail on the website is 8.2 something...

Anybody have any news on this?   I can't even find where to download Max 8.1.11 anymore! Seems the oldest avail on the website is 8.2 something...

Max 8.1.11. is surelly still available for download, but link is not shown

in which case you could get rid of stupid apple

Max 8.1.11. is surelly still available for download,  but link is not shown
is this for your own needs?
in which case you could get rid of stupid apple
security restrictions.
if you think solution is to use 8.1.11
I could  digg  download link from  archives


https://akiaj5esl75o5wbdcv2a-maxmspjitter.s3.amazonaws.com/Max8111_210413.dmg

Same thing with my standalone... but i can't use the 8.1.11 because of some objects that have since been updated (ex : mc.resize).

I hope C74 solves this problem in the next release...

Hi all,
Same thing with my standalone... but i can't use the 8.1.11 because of some objects that have since been updated (ex : mc.resize).
I hope C74 solves this problem in the next release...

You simply need to codesign the standalone app bundle. 

You simply need to codesign the standalone app bundle. 
From a terminal:

I did that, but unfortunately it doesn't work. I get the following error message in the terminal :

" resource fork, Finder information, or similar detritus not allowed "

Thank you for your reply.
I did that, but unfortunately it doesn't work. I get the following error message in the terminal :
" resource fork, Finder information, or similar detritus not allowed "


I'm having the same issue now -- realizing that I need the functionality of some updates since 8.1.1.

I thought that you needed to register an Apple developer ID in order to co-design the app?

I'm having the same issue now -- realizing that I need the functionality of some updates since 8.1.1.   

you don't need a developer ID when you sign anonymously, which is what passing "-" to the "-s" flag does

And all is right now, without Apple developer ID.

@Rob Ramirez - interesting, I didn't know this-

"you don't need a developer ID when you sign anonymously, which is what passing "-" to the "-s" flag does"

@Rob Ramirez - interesting, I didn't know this-
"you don't need a developer ID when you sign anonymously, which is what passing "-" to the "-s" flag does"

Amazing! Going to give it a shot... thanks everyone!

Amazing!  Going to give it a shot... thanks everyone!

I have an issue, which might be related (or not, I don't know).

 externals. Everything works as expected until I export my patch as 

 application on Mac. In the exported stand-alone the mouse movement doesn't work anymore. My expectation is, I have to enable the application in the System Settings > Privacy & Security > Accessibility on macOS. But even if I do so, the mouse doesn't move.

Max is also enabled in the Accessibility and both the externals work within Max.

Do you have any idea, please? Do I have to setup something specific in the [standalone] object or on the export, so the system recognizes the new application correctly? Or any other idea, please?

I tried to use the Terminal tricks, you recommended, but it didn't help.

I tried to use mxj_autobot and/or 11clicks externals. Everything works as expected until I export my patch as stand-alone application on Mac. In the exported stand-alone the mouse movement doesn't work anymore. My expectation is, I have to enable the application in the System Settings > Privacy & Security > Accessibility on macOS. But even if I do so, the mouse doesn't move.

Is Cycling on top of this issue? I used the suggestions made above, xattr and codesign, I get no error or other warnings when I use these commands in the terminal, but the issues still persist. In my case it is the microphone that I have to allow to be used over and over again even when I switch to other tabs in the same application and back. It is particularly frustrating since I have an automatic kill switch for audio in other tabs (users often forgot about audio in other tabs) but this bug makes it almost impossible to use it.

Does the Standalone need to be in a specific location? 

I'm trying to open a Standalone I made - doesn't use Audio at all - just midi.

Worked fine with Mojave, but now I'm trying in Ventura on a different machine, but getting the error - 

The application “MyStandalone” can’t be opened.

I'm trying the above Terminal commands, however both are saying "no such file". Triple checked the name I'm using and tried removing ".app" tried while bundle was in Applications folder and when in Downloads folder.

I made it using - Max 8.0.6 (build c36dce5) apparently - as I found this in the info.plist file.

Thanks for this.
Does the Standalone need to be in a specific location?  

I'm trying to open a Standalone I made - doesn't use Audio at all - just midi.
Worked fine with Mojave, but now I'm trying in Ventura on a different machine,  but getting the error - The application “MyStandalone” can’t be opened.  

I'm trying the above Terminal commands, however both are saying "no such file".  Triple checked the name I'm using and tried removing ".app"  tried while bundle was in Applications folder and when in Downloads folder.

I made it using - Max 8.0.6 (build c36dce5) apparently - as I found this in the info.plist file.

For me (Mac 13.6.3), it worked better with an "--deep" option as follows:

Don't forget to write full path for your app file or do the command in the same directory.

Standalone Mac permissions launch problem