Taking some steps backwards...

Between October 2017 until May 2018, I created the first prototype MaxForLive system that represented my research. During this time, I focused a lot on melodic content produced by the VST 'Serum'. I created a patch in Max/MSP that allowed the collection and transferring of instrument parameters from auditioning setup on my laptop to the performance system on my PC. I used the same patch on seven different Ableton tracks, which contained two seperate drop down menus: one to select what type of instrument was to be selected at random (Bass, Lead, Pad, FX etc.), and one to select a range of port numbers in multiples of 1000. I would link the Bass instrument with 1000 (so ports 1,000, 1,001, 1002, 1003 etc.), Lead with 2000 and so on. This meant that I could use the same patch to communicate hundreds of parameters within seven different Serum instruments between two computers. Sound cool right?

Well, it kind of was, but this method simply was not sustainable. Not only was I attempting to randomly choose seven CPU heavy VST presets across seven duplicate copies of the same patch, but I was assigning every single parameter it's own UDP port. The result? An unmanageable, highly volatile system that requires hours of work to get the smallest changes made. Some major changes to the system had to be made, and this was was going to require a complete redesign. Some of the core functions of the system worked great, and worked well at demonstrating some of the key aims of my research proposal - these could stay.

audition