![]() If you’re sending a custom OSC message, then the format is up to you to decide. This isn’t the BEST design, but it’s simple and should solve the problem in a way that’s pretty simple.Īre there any plans from the dev community for doing so? This would be a really awesome feature! These have some extraneous information - the things you’d be interested in are the part where \degree is specified - but you could extract that part, and reconstruct it into whatever format you wanted, and then send to P4 in your \schedBundleArray function. You get something like this: The bundle looks like: ], nil ] "The bundle looks like: %".format().postln | lag, offset, server, bundleArray, latency | ![]() I would try experimenting with this - for example: Pbind( This can be overridden by your Event or Pbind - so, you can re-use all of the existing setup logic for note events, and just fix-up and send the bundle to P5 in your custom version of this function. ![]() There might be a simpler way to override here - when a regular note Event is being assembled, the last thing it does is call ~schedBundleArray with the assembled OSC message - this is responsible for sending the bundle with e.g. There is no existing event type for sending OSC events - this would be a great feature, but it definitely doesn’t exist now. Now start Renoise OSC server, load a sample, and try some patternsĬtranspose: Pseq(,inf),īut what I couldn’t find there was a simple syntax for sending Note Events or Midi Events as OSC messages… Do I really need to re-implement the whole SC’s defaultParentEvent as new OSC Event to send it using regular pattern’s syntax? Some basic code you can try to get OSC communication between SC and Processing, you’ll have to install the oscP5 library first from Sketch > Import Library.įirst run this in SC: OSCdef(\processing, ) Is there a way of sendinh MIDI from SC to Processing with "any" range of values? Is it possible to use this same Pattern's template of sending MIDI to send OSC instead? degree is converted to midinote, not just frequency ![]() \midiout, mOut, // must provide the MIDI target here this line is optional b/c noteOn is the default Var mOut = MIDIOut.newByName("FastLane USB", "Port A").latency_() I was sending MIDI messages exactly in this way: // Pattern Guide Cookbook 04: Sending MIDI I tried to send PitchBend messages or SongPtr which could allow 16383, but the Processing library doesn’t recognized them. Secondly, I had some problem when trying to send MIDI from SC to Processing, because the processing library for that (The Midi Bus) lacks documentation and seems to be incomplete.įor instance, I was only able to send NoteOn, NoteOff, Pitch and tradicional Control messages, which means that everything was constrained to values between 0 and 127. I was trying to send data from SC to Processing and find some issues.įirstly, in terms of communication speed, does it really matter if I send MIDI or OSC? Is it all under UDP or TCP ?
0 Comments
Leave a Reply. |