This entry was posted in Uncategorized on Maby Mike O'Connor. Cranking up the “Smoothing” settings in the 1st instance of OSCulator fixed that. Signals coming into Live were quite jittery at first.So the control wouldn’t “pick up” the MIDI signal. It turned out that sometimes controls were set to a higher value than the maximum value coming to them from OSCulator. I found that controls sometimes wouldn’t work.I found it useful to turn all the devices off (untick the boxes in the left column) before starting the mapping. The mappings will appear in the box on the left (under “MIDI Mappings”) as they’re added. Turn on the MIDI Map Mode switch (blue, in the upper right corner, says “MIDI”), click on the control that should receive the MIDI signals and toggle the device on and off in OSCulator. Once OSCulator is producing MIDI, Ableton Live can be trained to apply those MIDI signals in the normal way. I picked those message numbers because they’re within a range (85-90) that’s generally not used by other devices. OSCulator has been configured to convert the OSC messages from Wekinator to MIDI CC messages in this example. Runs on: WinXP, Win7 x32, Win7 圆4, Windows 8, WinVista, WinVista 圆4. If Wekinator is running, OSCulator will pick up the Wekinator outputs and they should be displayed in the Messages column of OSCulator.Ģnd instance of OSCulator to Ableton Live Ableton With Little Snitch Ableton Little Snitch Ableton With Little Snitch. The second instance of OSCulator (instantiated through File/New) is set to listen on port 12000. The default Wekinator output port is 12000. Wekinator to OSCulator (this is the second instance of OSCulator) If Wekinator is running, locating and selecting these entries should be available through the drop down menus. If you are starting from an empty OSCulator file, here is what the Parameters page looks like in this first instance of OSCulator. I’ve included the mapping if you are building this from an empty OSCulator file. This first instance of OSCulator translates the motions of the WiiMote into OSC messages and pushes them to Wekinator on Wekinator’s default UDP port (6448). Here’s the way it looks when it’s working. Open the sliding panel on the right side of the main OSCulator page, turn on the WiiMote, click “Start Pairing”. Open OSCulator with the 3-input template linked above. WiiMote to OSCulator is a built in feature of OSCulator. oscd templates to simplify the connection from OSCulator to Wekinator. Here is a block diagram (clicking on it makes it bigger) Wekinator outputs are mapped to MIDI to drive Ableton Live through another instance of OSCulator. In this configuration a WiiMote (input device) is connected to Wekinator (real time interactive machine-learning software) through OSCulator (OSC bridging and routing software). This won’t work on a PC as some of the software is Mac-only. When I tweak the fader on DAW, it doesn't mess with M32.This is a scratchpad post to remind myself how to put together a machine-learning system on a Mac. I can send the fader signals to the channels on DAW, but not the other way around. I'm using the MIDAS M32 console to control Logic Pro. If that's a problem you could create a 2nd OSCulator document to receive the MIDI from LogicĪlso, I'd recommend the OSCulator forum - Camille, the developer, is v helpful Then you need to connect/cable the stream of MIDI messages you want to send from Logic to OSCulator, to that MIDI Instrument Object.īeware of MIDI feedback if you're sending MIDI between OSCulator and Logic using the same OSCulator port. Select it, and in the inspector panel on the left where it says Port,Ĭlick the dropdown menu and you should see your OSCulator destinations, with their port numbers in brackets 2 - if you want to send a MIDI signal from Logic to OSCulator, you wouldĬreate a MIDI Instrument Object in the Environment,
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |