pechnatunk

I'm an old Max user - very rusty now and I have a great idea!

Aside from getting back on track with Max/MSP :) my other great idea is for a mobile app.

The obvious thing for me is to start building and prototyping this in Max.

Can people please advise on the journey a patch would have to take to get to - IOS and Android?

I've read about gen~ exporting to xcode and read the gen code export tutorial, however these seem to relate to more low-level fft signal processing effects rather than a standalone - for lack of a better word.

Lets say for now, I want to make a very basic drum sequencer - initially, I would simply patch this with Max objects - metro for timing and buffer~s with preloaded sounds.

What workflow would be needed to get this to IOS/android?

Would it be easier down the track to create it using only msp objects? Does it make a difference? I know it would perform better.

It would also great if you could describe each step of the process - for example what steps can be; ported to another language/platform - hopefully by me.... and/or what steps need to completely re-coded - by smarter human :)

Also, are there any actions done in Max/MSP that would be particularly hard, or easier, to do in Xcode/swift/objective c? Such as loading a sound into a buffer, or creating additional instances of a patch for example? Anything that might affect the max patching early on.

I'd really appreciate some insight into this process.

Hi,
I'm an old Max user - very rusty now and I have a great idea!

Aside from getting back on track with Max/MSP  :) my other great idea is for a mobile app.
The obvious thing for me is to start building and prototyping this in Max.

I've read about gen~ exporting to xcode  and read the gen code export tutorial, however these seem to relate to more low-level fft signal processing  effects rather than a standalone - for lack of a better word.

Lets say for now,  I want to make a very basic drum sequencer - initially, I would simply patch this with Max objects - metro for timing and buffer~s   with preloaded sounds.
What workflow would be needed to get this to IOS/android?

Would it be easier down the track to create it using only msp objects?  Does it make a difference?  I know it would perform better.  

It would also great if you could describe each step of the process  - for example what steps can be; ported to another language/platform - hopefully by me.... and/or what steps need to completely re-coded - by smarter human :)

Also, are there any actions done in Max/MSP that would be particularly hard, or easier, to do in Xcode/swift/objective c?  Such as loading a sound into a buffer,  or creating additional instances of a patch for example? Anything that might affect the max patching early on. 

max-prototype-iosandroid-app-workflow

Generally speaking the max prototyping model is completely separated from any mobile implementation. It is probably worthwhile to prototype a relevant dsp process, and UI interactivity in max, but that would be just for "proof of concept" and possibly "useability'. There is no actual defined path between a max patch and an application on a mobile platform. To transpose it to another platform you would have to recode it all by hand, gen or no gen.

Generally speaking the max prototyping model is completely separated from any mobile implementation. It is probably worthwhile to prototype a relevant dsp process, and UI interactivity  in max, but that would be just for "proof of concept" and possibly "useability'. There is no actual defined path between a max patch and an application on a mobile platform. To transpose it to another platform you would have to recode it all by hand, gen or no gen.


i think the gen code export is supposed to help you port dsp code to mobile platform, but nothing on the UI front.

look into Relative Wave's (and acquired by Google) Form: 

it's for mac/ios. it has a similar patching environment as Max. all the patching happens on your computer and then you can view the prototype and UI on your device. There's also ways to bundle it up as a standalone app, which i have done where i needed untethered iPads for an installation. The only unfortunate aspect is it's not very actively developed. It's open source though so you're able to create your own objects if you're familiar enough with obj-c

Origami Studio (acquired by Facebook) should be coming out later this year which will be very similar to Form, but hopefully more actively developed.

look into Relative Wave's (and acquired by Google) Form: http://www.relativewave.com/form/

Hmmm - thanks. So it seems for what I want to do - Max/MSP is but a glorified Powerpoint presentation? :)

I've had a quick look at xcode and swift, and just discovered the audiokit.io I'll check out Relativewave also, but obviously I'd much rather stick to what I "know".

Lets say that my sequencer, is instead a generative, say, 4 part song/sequence/evolving sound, without any storage buffer storage (only using waves) and with no UI other than say - start DAC, tempo, and volume of each part - 3-6 inputs, and just audio output.

Could the "brains" of the app be patched in gen~ and ported, then someone with more knowledge of Swift be able to code around that? Would this make it any easier for them/me?

Maybe I'm not grasping it - but I imagine swift would just be assigning UI to gen~ parameters.

Hmmm - thanks. So it seems for what I want to do - Max/MSP  is but a glorified Powerpoint presentation?    :)

I've had a quick look at xcode and swift, and just discovered the audiokit.io  I'll check out Relativewave also, but obviously I'd much rather stick to what I "know".

But for argument's sake:
Lets say that my sequencer, is instead a generative, say, 4 part song/sequence/evolving sound, without any storage buffer storage  (only using waves) and with no UI other than say - start DAC, tempo, and volume of each part - 3-6 inputs, and just audio output.
Could the "brains" of the app be patched in gen~ and ported,  then someone  with more knowledge of Swift be able to code around that?  Would this make it  any easier for them/me?  

Gen code export will help you in your prototype.

I am very supportive of people like you. Your creativity will have many better apps on your phone so I can share them extensively to everyone on my Blog 

I am very supportive of people like you. Your creativity will have many better apps on your phone so I can share them extensively to everyone on my Blog modandroidapk.com 

Max Prototype -> IOS/Android app workflow