Well, whose a clever boy!!! Crickey, very clever indeed.
I will give that a go...
Thanks,
Simon
How do I discover Midi CC Values in VSTi's?
-
- KVRer
- Topic Starter
- 17 posts since 17 May, 2004
-
- KVRian
- 995 posts since 4 Mar, 2004
Eh ...
Thank you Scott this has been very helpfull
like.. very helpfull ,
Just a quick question if anyone who might know sees this ,
Why can't some programs accept more than one midi controller at a time ? ie Fl studio, Reason, Minihost,
Thank you Scott this has been very helpfull
like.. very helpfull ,
Just a quick question if anyone who might know sees this ,
Why can't some programs accept more than one midi controller at a time ? ie Fl studio, Reason, Minihost,
-
- KVRAF
- 3364 posts since 16 Feb, 2004 from atop a katamari
how do you mean? as in, one physical midi controller device at a time?
i'm not sure... but you can always use MIDIOX and midi yoke to customise your midi routing internally... have, for instance, a midi keyboard and a midi CC controller both cabled into the same output port, which would then (via the yoke driver) become your 'input' port. i could, of course, be talking about something entirely different......
i'm not sure... but you can always use MIDIOX and midi yoke to customise your midi routing internally... have, for instance, a midi keyboard and a midi CC controller both cabled into the same output port, which would then (via the yoke driver) become your 'input' port. i could, of course, be talking about something entirely different......
Kick, punch, it's all in the mind.
-
- KVRAF
- 3220 posts since 23 Dec, 2002
Glad you like the tip 
I can't remember if midi uses 0-127 or 1 to 128 . You may have to offset the midi file by a bar if it is off to get the transport to read 1 for controller 1 or bar 53 for controller 53 etc.
It seems to me I was able to do use copy and paste in the cubase controller view to save time (instead of manually recording a sweep for each of the 128 potential knobs I recorded it for one knob and pasted the sweep into each controller slot in the controller.
Private message me and maybe we can do this together. I lost the midi file due to a hard drive crash. I have another suggestion using a free CC mapper and hubbis loopback to create a library of presets for the UC 16. Its very cool and you set the fader box to specific numbers and change to control specific vsit using it.(Very cool and once you create a map for the vsti you never have to reprogram the UC -16)
Scott
I can't remember if midi uses 0-127 or 1 to 128 . You may have to offset the midi file by a bar if it is off to get the transport to read 1 for controller 1 or bar 53 for controller 53 etc.It seems to me I was able to do use copy and paste in the cubase controller view to save time (instead of manually recording a sweep for each of the 128 potential knobs I recorded it for one knob and pasted the sweep into each controller slot in the controller.
Private message me and maybe we can do this together. I lost the midi file due to a hard drive crash. I have another suggestion using a free CC mapper and hubbis loopback to create a library of presets for the UC 16. Its very cool and you set the fader box to specific numbers and change to control specific vsit using it.(Very cool and once you create a map for the vsti you never have to reprogram the UC -16)
Scott
-
- KVRian
- 995 posts since 4 Mar, 2004
No dude you got it in one , I'm d/l'ing Midi ox and energyxt as I write ,haydxn wrote: i could, of course, be talking about something entirely different......
I've got a midi keyboard connected by midi , and a uc 16 conected by usb(midi) and a kaos2pad daisychained to a bcf2000 which is connected by usb/ midi , and in some programs sx for example once I'd selected all inputs under the midi in everything was cool , but in Reason the way you have to toggle the midi inputs just plain annoys the hell out of me sometimes and I just wonder Propellerhead dudes why?? ,I know I should use rewire anyway , actually mostly I do .
anyhow many thanks ,