Hi Cam,
I have been evaluating OSCulator now that Stereoscope has been shut down. Stereoscope had a great integration with Yamaha desks and I'm hoping to find the same functionality with OSCulator. There are two things that I'm struggling to find an answer to:
The deal breaker is the syncing of faders between the desk and TouchOSC. 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.
It's a great piece of software and I hope you can help answer my questions.
Kind regards,
Marcus
I have been evaluating OSCulator now that Stereoscope has been shut down. Stereoscope had a great integration with Yamaha desks and I'm hoping to find the same functionality with OSCulator. There are two things that I'm struggling to find an answer to:
- Stereoscope had the ability to 'recall' the current layout of the desk and update the TouchOSC states with one button. They used a /system/resync command which 'pulled' the state of the faders and mutes into TouchOSC. I can't seem to find any way to figuring this out with OSCulator. 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. In any case, Stereoscope enabled you to sync the settings of the desk without touching the desk itself. This was useful especially if you ran TouchOSC after you set the desk up.
- I'm not sure how best to control the Aux faders with OSCulator. Stereoscope used its own command: /input/1/toAux/2/level for example which in this example controls fader 1 levels for Aux 2. 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). The faders would respond to reflect the state on the desk.
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. I've created the template OK from the shortcut arrow in the i/o window. The sysex is 14 bytes. Byte 9 is the channel i think and 11 and 12 are the level information. I have tried creating substitute OSC arguments but I get random results (I don't really know what I am doing here!)
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.
The deal breaker is the syncing of faders between the desk and TouchOSC. 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.
It's a great piece of software and I hope you can help answer my questions.
Kind regards,
Marcus
Comment