earthmonkey1

I've created a simple patch which sends midi data to ableton using ctlout. When I run it under Max I can select 'from MaxMSP 1' from the ctlout dropdown, and ableton picks up the data fine.

However when I export the patch as an app and run it under runtime, the port 'from MaxMSP 1' disappears from the ctlout list.

Any ideas? Is there something extra I need to include during the app build?

I've created a simple patch which sends midi data to ableton using ctlout. When I run it under Max I can select 'from MaxMSP 1' from the ctlout dropdown, and ableton picks up the data fine. 

ctlout-app-issues

In case anyone has a similar problem in the future, I solved the problem by sending the midi data via the IAC port instead - which remains in the list when you open the app under runtime.

Still don't know why 'from MaxMSP 1' (and 2) disappear tho! :S

In case anyone has a similar problem in the future, I solved the problem by sending the midi data via the IAC port instead - which remains in the list when you open the app under runtime. 

Still don't know why 'from MaxMSP 1' (and 2) disappear tho! :S


> when I export the patch as an app and run it under runtime

Is it a collective that you opened with runtime, or a standalone app?

Anyway, the 'from MaxMSP 1' is only available in MaxMSP itself. A collective opened with Runtime will show the option 'from MaxMSP Runtime 1' and iStandalone will show 'from iStandalone 1', doesn't it? Probably the standalone object is required to specifically include midi support.

Is it a collective that you opened with runtime, or a standalone app?
Anyway, the 'from MaxMSP 1' is only available in MaxMSP itself. A collective opened with Runtime will show the option 'from MaxMSP Runtime 1' and iStandalone will show 'from iStandalone 1', doesn't it? Probably the standalone object is required to specifically include midi support.


ctlout app issues