bg
2006-09-02 19:43:29
Mouse movements/clicks as Outgoing Action
Status: in beta for "Midi Translator Pro"
I see mouse movements/clicks is being worked on. I have a suggestion/request that may be different.
The VST plugin Kantos, for example, has on-screen controls which cannot be automated by MIDI. You have to click-and-drag the on-screen sliders with the mouse. I am imagining a feature in MT called something like "Define Drag Region..." where the user would be prompted to click-drag a region. Typically the region would be the travel of an on-screen slider or knob. Then the user would be prompted to enter a MIDI CC number. MT would then move the on-screen slider/knob in response to incoming MIDI CC.
In order for a feature like this to work properly, the "Drag Region" would obviously have to be relative to the window that's being addressed. In other words, once an on-screen control is defined, the user should be able to re-postion the window (e.g. the VST plugin) and maintain the same MIDI-to-screen relationship.
I hope this makes sense.
Status: in beta for "Midi Translator Pro"
I see mouse movements/clicks is being worked on. I have a suggestion/request that may be different.
The VST plugin Kantos, for example, has on-screen controls which cannot be automated by MIDI. You have to click-and-drag the on-screen sliders with the mouse. I am imagining a feature in MT called something like "Define Drag Region..." where the user would be prompted to click-drag a region. Typically the region would be the travel of an on-screen slider or knob. Then the user would be prompted to enter a MIDI CC number. MT would then move the on-screen slider/knob in response to incoming MIDI CC.
In order for a feature like this to work properly, the "Drag Region" would obviously have to be relative to the window that's being addressed. In other words, once an on-screen control is defined, the user should be able to re-postion the window (e.g. the VST plugin) and maintain the same MIDI-to-screen relationship.
I hope this makes sense.