I totally spaced on this comment and just re-read it, ok so I can write stuff in Max feed into Cubase as long as a keep it open kind of like when you use a standalone plugin to make use of RAM and incompatibilities etc? What’s the best way to get started? Just go through the tutorials I suppose? None of the routing will be a problem, the Mac has inbuilt midi looping and so does my focusrite for audio. Ok wicked, I’ll get cracking and give it a go
1 Like
Btw I’m not sure if using mentioned above or not but I did find a program called architect. It does exactly what I’m saying but much much more. Definitely worth checking out, it’s by loomer. There is a new version imminent which apartly contains huge additions
1 Like
Here’s a basic Max patch. It sends notes and CC data to a MIDI port. The port is specified in the [noteout] and [ctlout] objects. This could easily grow in complexity with automation and more.
In Cubase, you would need to specify the correct MIDI port as the input of a track.
The difficult part is synchronizing them.
I’ve never heard of architect. Looks amazing. Really solves some limits of Max.
Hi,
With the latest Max version, you can also export VST3 plug-ins from your Max patches.
1 Like
This looks almost exactly like how architect works, but I feel Architects is a little bit more in-depth as it is not just devices so to speak it’s almost a whole DAW itself - That’s a plug-in that you can put inside the DAW. In fact, you can put an instance of architect inside an instance of architect. If you do end up getting into it, let me know because I don’t know anyone else who uses it and I could do with some help with it often to be honest it’s not the kind of programming I’m used to
With the latest Max version, you can also export VST3 plug-ins from your Max patches.
Yes and only for audio. No MIDI processing. Specifically it’s a feature called RNBO which is an add-on with an additional cost.
This looks almost exactly like how architect works, but I feel Architects is a little bit more in-depth as it is not just devices so to speak it’s almost a whole DAW itself - That’s a plug-in that you can put inside the DAW. In fact, you can put an instance of architect inside an instance of architect.
Regarding Architect / Max comparisons, you can build DAW-like features in Max. They’re just not pre-packaged. Max is more of a “tabula rasa” compared to Architect, it seems.
What I find great about Architect however is that you can use it as a VST immediately out of the box. That’s something that Max does not currently offer without purchasing an audio-only add-on.
Here’s a video that demonstrates how to make a basic sequencer in Max
Hi,
It depends, in which direction do you want to go into the depth. Max can fully process also audio and video. You can process Audio files or real-time audio stream, same as video. It can also handle lots of input devices (not just MIDI, but also motion controls, light sensor, etc.). You can process data with JavaScript and Node, write Java libraries, process picture with Lua or even write own C/C++ objects.
I haven’t go too much in depth, but you can process MIDI data too. Then, you can export VSTi, which you can use as virtual MIDI In and Out.