Just a tip regarding Novations Stepseq and the launchpad
Posted: Wed Aug 11, 2010 5:29 am
I'll make this short.
I've been quite annoyed by the fact that I've had to click edit on the Stepseq patch from Novation before my launchpad is discovered.
No more.
I edited Stepseq in Live and saved a custom version of the M4L.api.SelectControlSurface.maxpat called M4L.api.SelectControlSurface_launchpad.maxpat (in \Cycling '74\Max 5.0\patches\m4l-patches\LiveAPI resources), AFTER the lauchpad was already discovered by m4l. Then I merely pointed the bpatcher to this file in the inspector. Lastly I saved the Stepseq patch with a new filename.
Now, when I add the stepseq it discovers my launchpad fine every time
No need for the extra waiting and hassle!
Anyhow, I thought this might be of help to some.
Cheers,
Chris
I've been quite annoyed by the fact that I've had to click edit on the Stepseq patch from Novation before my launchpad is discovered.
No more.
I edited Stepseq in Live and saved a custom version of the M4L.api.SelectControlSurface.maxpat called M4L.api.SelectControlSurface_launchpad.maxpat (in \Cycling '74\Max 5.0\patches\m4l-patches\LiveAPI resources), AFTER the lauchpad was already discovered by m4l. Then I merely pointed the bpatcher to this file in the inspector. Lastly I saved the Stepseq patch with a new filename.
Now, when I add the stepseq it discovers my launchpad fine every time
Anyhow, I thought this might be of help to some.
Cheers,
Chris