Max4Live Max/msp conflict issue when loading
Max4Live Max/msp conflict issue when loading
Not sure if anyone else experiences this. When i load any max patch the mandala v3 opens up and takes priority eg my patch opens but the the menu is for mandala v3 and no further interaction can happen with max patch. When i open a max standalone this does not occur. Happens in both high sierra and sequoia 15.4.
Re: Max4Live Max/msp conflict issue when loading
This is an OS file-association issue. What’s actually happening is that when you double-click a .maxpat, your operating system decides which application “owns” that file type.
Since you have a standalone Max application (the Mandala Virtual Brain) installed on your system, your OS may have:
• Incorrectly associated .maxpat files with that standalone app
• Or reused the association from when the standalone was last launched
• Or lost the association to the real Max.app during an update
So the OS says: “This file opens with that app” even though that app has no idea what to do with a Max patch. Max itself is never being reached.
How to fix it:
MacOS
• Right-click the .maxpat file
• Choose Get Info
• Under Open with: select Max.app
(usually in /Applications/Cycling '74/Max.app)
• Click Change All…
• Confirm
This restores the correct handler for all Max patch files.
Windows
• Right-click the .maxpat file
• Open with → Choose another app
• Select Max
• Check Always use this app
• OK
If Max doesn’t appear:
• Browse manually to C:\Program Files\Cycling '74\Max\Max.exe
The other thing you could do instead is always launch Max first and open your .maxpatch files through Max with File>Open because when Max is already running:
• It intercepts .maxpat open requests
• The OS doesn’t have to guess
• The patch opens correctly
That is why the problem only shows up when double-clicking from the file system.
Best practice:
• After installing a standalone, re-check file associations
• Do not rely on double-clicking patches
• Launch Max first, then open patches
Since you have a standalone Max application (the Mandala Virtual Brain) installed on your system, your OS may have:
• Incorrectly associated .maxpat files with that standalone app
• Or reused the association from when the standalone was last launched
• Or lost the association to the real Max.app during an update
So the OS says: “This file opens with that app” even though that app has no idea what to do with a Max patch. Max itself is never being reached.
How to fix it:
MacOS
• Right-click the .maxpat file
• Choose Get Info
• Under Open with: select Max.app
(usually in /Applications/Cycling '74/Max.app)
• Click Change All…
• Confirm
This restores the correct handler for all Max patch files.
Windows
• Right-click the .maxpat file
• Open with → Choose another app
• Select Max
• Check Always use this app
• OK
If Max doesn’t appear:
• Browse manually to C:\Program Files\Cycling '74\Max\Max.exe
The other thing you could do instead is always launch Max first and open your .maxpatch files through Max with File>Open because when Max is already running:
• It intercepts .maxpat open requests
• The OS doesn’t have to guess
• The patch opens correctly
That is why the problem only shows up when double-clicking from the file system.
Best practice:
• After installing a standalone, re-check file associations
• Do not rely on double-clicking patches
• Launch Max first, then open patches