Negative numbers mean that there will *always* be a change - ie. So for example, entering 4 means that a clip on that layer will be triggered every 4 beats.įinally, if you are using the "drunken" mode, you can specify the maximum size of the steps away from the current clip. Next, you specify how often you want clips to be triggered, in beats, using the "beat int" parameter.
#MAX MSP RUNTIME PATCH#
Moving along, you tell the patch how many clips you have in that layer, using the "# clips" parameter. There are four modes:Ģ) Sequence: each clip in the layer will be activated in sequenceģ) Drunken: clips will be activated using a "drunken walk", randomly moving away from the current clip (see "Step" value later)Ĥ) Random: clips will be activated randomly You can control up to 8 layers.įrom left to right, enter the # of the layer you want to control. You can change both of these - most useful if you run CoPilot on a separate computer to the one where you run Resolume.įinally, the heart of the patch is the layer control section. By default, it is set to 'localhost' (127.0.0.1) for when the patch and Resolume are on the same computer, and the port is set to 7000, the Resolume default. (Not sure how it will work with the runtime version.)įurther down, the OSC control section lets you specify the IP address and port to use for OpenSoundControl. If you save the patch from the file menu, then the saved states will be saved for the next time you use CoPilot. By default, saved state 1 is loaded when the patch opens. You can save and recall up to 4 states of the program. You should see the BPM change in Resolume.īelow that are the presets. You can test OSC communications by enabling "sync BPM", putting the mouse cursor in the BPM box and dragging up and down. If the "sync BPM" box is checked, then CoPilot will control the Resolume BPM as well. Here you can turn CoPilot on and off, and set a BPM. Starting from the top left, you find BPM control.
#MAX MSP RUNTIME PC#
PC version should still work as-is.ġ) Open Resolume Avenue, and make sure that OSC is enabled in preferences, the 'bundle' checkbox is on, and the port is 7000ģ) You should see the user interface, like so: Replaced the OpenSoundControl external with the correct version for Intel Macs.
#MAX MSP RUNTIME INSTALL#
Here are instructions for installation and use:ġ) Download the zip file attached to this post and unzip it.Ģ) If you don't already have Max/MSP, get and install the runtime from here:
If you don't know what this is about just use 0.7 for now. Make sure the corresponding switch in Resolume preferences is turned off as well. Switching bundles off should allow using Copilot in parallel with TouchOSC.
Uploaded experimental version 0.7.1, allows you to switch OSC bundles on and off. If it does not seem to be changing, wait a couple of seconds and then tap in the tempo, at least 3 taps. Important note: the tap tempo feature has a guard time built in to avoid unintended changes. Make sure to download most recent Max runtime to use. Uploaded version 0.7, has tap tempo support (mapped to Tab key) and OSCI settings are persistent. Delete the cop_presets.json file to reset, it will prompt you to save the preset file when you close the patch. Uploaded version 0.6, supports saving and loading presets even when using the runtime. I've made a little Max/MSP patch that implements a kind of chaos mode for Resolume Avenue, using OpenSoundControl.
0 kommentar(er)
