VSTi controllers
-
- KVRer
- Topic Starter
- 11 posts since 5 Feb, 2004
Firstly, everybody on this forum has been very helpful in getting me through my first real attempt at a programming project
I am trying to work out how to read in controller values for Cubase into my VSTi, for example volume or pitch bend controllers. Is this done as a Midi signal in? I am finding the (usually good) documentation a little confusing on the subject
Are there any examples or links to relevent articles people could post.
Thanks in advance
T*
I am trying to work out how to read in controller values for Cubase into my VSTi, for example volume or pitch bend controllers. Is this done as a Midi signal in? I am finding the (usually good) documentation a little confusing on the subject
Are there any examples or links to relevent articles people could post.
Thanks in advance
T*
-
- KVRAF
- 2086 posts since 11 Feb, 2003
Howdy,
I'm not sure how cubase works, but in FL Studio you just click "link to controller" and turn a knob on your controller and then you're twistin away.
Might want to consider FL as an alternative, it'll make your life a lot easier.
I'm not sure how cubase works, but in FL Studio you just click "link to controller" and turn a knob on your controller and then you're twistin away.
Might want to consider FL as an alternative, it'll make your life a lot easier.
- something special
- 8571 posts since 16 Mar, 2002 from Birmingham, Alabama
don't listen to him! you'd have to search and ask as many questions for FL as anything else.Mr.Me wrote:Howdy,
I'm not sure how cubase works, but in FL Studio you just click "link to controller" and turn a knob on your controller and then you're twistin away.
Might want to consider FL as an alternative, it'll make your life a lot easier.
I assume you're working in SX? I can't help you, I'm still at 5.1
(I'd give FL away, but my wife gave it to me for my birthday)
here's a link to a very elementary tutorial on sequencing in sx, it may have the info you're looking for.
http://www.cems.uwe.ac.uk/~lrlang/music ... l#sections
Last edited by bluedad on Thu Mar 25, 2004 10:44 am, edited 1 time in total.
-
- addled muppet weed
- 105853 posts since 26 Jan, 2003 from through the looking glass
bluedad wrote:don't listen to him! you'd have to search and ask as many questions for FL as anything else.Mr.Me wrote:Howdy,
I'm not sure how cubase works, but in FL Studio you just click "link to controller" and turn a knob on your controller and then you're twistin away.
Might want to consider FL as an alternative, it'll make your life a lot easier.
I assume you're working in SX? I can't help you, I'm still at 5.1
(I'd give FL away, but my wife gave it to me for my birthday)
well why not give pao away as part of the package
dont tell her i said that
-
- KVRAF
- 3723 posts since 17 Apr, 2002 from Scotland
First off, your vsti should respond equally in all hosts.
Thankfully, this is pimps (scottish word - means "very easy").
The pitch bend , volume controllers and CCs in general will be sent to your plugin as midi messages by the host. You should therefore deal with them in your event processing code - the same place you deal with note on/offs etc.
Thankfully, this is pimps (scottish word - means "very easy").
The pitch bend , volume controllers and CCs in general will be sent to your plugin as midi messages by the host. You should therefore deal with them in your event processing code - the same place you deal with note on/offs etc.
-
- KVRer
- Topic Starter
- 11 posts since 5 Feb, 2004
FL isn't that bad. Don't use it for anything major. I'm a Reason kid anyway
Not sure I've explained my problem properly tho. I'm actually coding the VSTi and I want to know how to get it to understand controllers sent from Cubase
Not sure I've explained my problem properly tho. I'm actually coding the VSTi and I want to know how to get it to understand controllers sent from Cubase
- something special
- 8571 posts since 16 Mar, 2002 from Birmingham, Alabama
oh, I suppose I should have looked at the forum name!i_dream_stars wrote:FL isn't that bad. Don't use it for anything major. I'm a Reason kid anyway
Not sure I've explained my problem properly tho. I'm actually coding the VSTi and I want to know how to get it to understand controllers sent from Cubase
-
- KVRAF
- 2086 posts since 11 Feb, 2003
-
- KVRer
- Topic Starter
- 11 posts since 5 Feb, 2004
Visual C++
-
- KVRist
- 38 posts since 16 Jul, 2001 from London UK
All continuos controller messages are midi messages.
To interpret these in your synth you will need to learn the midi specification. It is not long so it shouldn't take much time:
http://www.srm.com/qtma/davidsmidispec.html
Once you have learnt that then check the how the Synth example with the latest SDK handles midi messages, you should then get a bit of an idea what to do.
enjoy
Harry
To interpret these in your synth you will need to learn the midi specification. It is not long so it shouldn't take much time:
http://www.srm.com/qtma/davidsmidispec.html
Once you have learnt that then check the how the Synth example with the latest SDK handles midi messages, you should then get a bit of an idea what to do.
enjoy
Harry
-
- KVRian
- 922 posts since 26 Mar, 2003 from Guildford, England
You pick up midi events in a VST by providing an implementation for the virtual function, processEvents();
You'll get a structure which will tell you when particular events will occur in the next audio buffer that you process.
p.s. check the VST documentation for the correct prototype for the processEvents function!
You'll get a structure which will tell you when particular events will occur in the next audio buffer that you process.
p.s. check the VST documentation for the correct prototype for the processEvents function!