![]() ![]() If it is just vanilla Control Changed, you can just receive the message in OSCulator and map it to a OSC message to TouchOSC. This is done in the MIDI Configuration panel of the console. You can choose to assign Aux-Sends to Control Changes or NRPN. I looked at the documentation for the Yamaha DM2000, and I believe the 03D is similar. Also, capturing a message is not enough as you found out, you have to tell OSCulator where are the area to "fill" with a OSC number value. Maybe you don't need to go into the trouble of creating a MIDI Template if the message is just a Control Change. This is the right way to go, but you have to get more information about these messages. It's a great piece of software and I hope you can help answer my questions. All the guys in the band are used to seeing the starting position of the faders in TouchOSC before they tweek their monitor mix - if they start with a flat fader view then it is unusable. The deal breaker is the syncing of faders between the desk and TouchOSC. If I can't translate the syses then my fallback would be to map controllers in the desk itself to unused slots - which would work fine if I had to. I have tried creating substitute OSC arguments but I get random results (I don't really know what I am doing here!) Byte 9 is the channel i think and 11 and 12 are the level information. I've created the template OK from the shortcut arrow in the i/o window. With OSCulator it seems I would need to create my own MIDI templates for the sysex that the aux channels transmit - however I really haven't a clue what to tell it to do with the bytes. The faders would respond to reflect the state on the desk. It also had a very neat way of switching between Aux channels with one set of faders using /stereoscope/system/state/selectedAux/changeTo/1 (1 being the Aux channel you required). Stereoscope used its own command: /input/1/toAux/2/level for example which in this example controls fader 1 levels for Aux 2. I'm not sure how best to control the Aux faders with OSCulator.This was useful especially if you ran TouchOSC after you set the desk up. In any case, Stereoscope enabled you to sync the settings of the desk without touching the desk itself. I have read in the forum about 'scene changes' and the fact that the desk should output the cc data - but I don't think it does. I can't seem to find any way to figuring this out with OSCulator. ![]() ![]() They used a /system/resync command which 'pulled' the state of the faders and mutes into TouchOSC. Stereoscope had the ability to 'recall' the current layout of the desk and update the TouchOSC states with one button.There are two things that I'm struggling to find an answer to: Stereoscope had a great integration with Yamaha desks and I'm hoping to find the same functionality with OSCulator. I have been evaluating OSCulator now that Stereoscope has been shut down. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |