![]() ![]() So when I repeated all the steps above with "omni" unselected" for the Viola, the fader would now get stuck on the viola, and not work on the violin anymore! So it was really frustrating and this is the crucial part of making this work. What caused so much trouble was that if you don't select "omni", the fader will be stuck to that specific instrument. For the next instruments you need to repeat this, but since we chose "Omni" you don't have to do #4 again. You will see that these knobs are now also moving as you move your faders.ĥ. Repeat for every controller (dynamics, expression, vibrato, etc). This window will now close by itself, and the fader is now controlling this. Now touch the fader you want to use for this CC. Make sure "Omni" is selected and "Remove conflicts" are unselected before doing anything else. Right click on the knobs again and choose "link to controller". The next you need to do is to link or learn to your midi control. In here, enter the name of the CC, then the CC number, and click "accept." Do this for as many CCs you want, like expression, vibrato, etc.ģ. In the "midi out" plugin right click on one of the knobs and select "configure" or just click on that small gear icon next to it. Make sure the midi and port channels corresponds with the midi channels in the VEP instance, as explained above.Ģ. I've renamed them to Violin, Viola, and Cello for the sake of this tutorial. Add "midi outs" as mentioned above for each instrument. This was also impossible to find information on online, but by trying every possible knob I figured it out.ġ. #Vienna ensemble pro demo how to#How to use a midi-controller with VEP in FL Studio: Much better than 9 per instance! And since you can only have 16 midi channels coming from one VEP instance with FL Studio, you will quickly need to have quite a few instances. So with the next instance, the CPU meter will show 4, then 6, then 8 and so on. So the next instance will be port number 2. The only thing you need to change is the port number. You can save this as a preset so you only have to do this once. "None" will still use quite a lot of CPU but could work for smaller projects. I use 1 buffer (low latency) but based on your resources you can choose 2-4. Go back and select "1 buffer" and you will now see that the CPU meter says 2, and there are no more distortion or freezing when you play. This is the crucial part of the CPU issue.Ħ. Select "Use fixed size buffers" (click "yes" if you get a warning) AND select "Process maximum size buffers" in the More dropdown menu. I just click "Auto map outputs" and all outputs are selected.ĥ. If you want more than one output (the same output numbers as in your VEP instance) select them here. Select the port for this specific instance (the same port number as you use for your VEP instance).Ĥ. If you don't do this first, FL Studio will most likely become unresponsive when doing the next step.ģ. VEP should now be ready to work but as you can see the CPU meter is at 9 already. (And of course, have the VEP Server opened on the computer or slave)Ģ. Open the Vienna Ensemble Pro (64Bit) plugin in FL Studio. But using 0 buffers won't work in the long run because of crazy CPU usage and how FL Studio handles latency.ġ. The problem was that the sound was either very distorted or FL totally unresponsive unless you changed the buffers to "none" inside the VEP wrapper window. So if you are like me, trying to figure this out, this post is for you. It has probably been there all the time, but no one has had a solution, at least not online, even not their staff, until now, thanks to Paul at VSL and the FL Studio guys who have been in touch. After one year of trying different ways to make this work, giving up and learning other daws, reading the same questions from the last 8 years by other people on forums about how to make VEP work with FL Studio, there is finally a solution! ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |