kimarnesen
Senior Member
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!
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. So if you are like me, trying to figure this out, this post is for you.
Issue:
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. But using 0 buffers won't work in the long run because of crazy CPU usage and how FL Studio handles latency.
Solution:
1. Open the Vienna Ensemble Pro (64Bit) plugin in FL Studio. (And of course, have the VEP Server opened on the computer or slave)
2. Set buffers to "none". VEP should now be ready to work but as you can see the CPU meter is at 9 already. If you don't do this first, FL Studio will most likely become unresponsive when doing the next step.
3. Open the wrapper settings. Select the port for this specific instance (the same port number as you use for your VEP instance).
4. Choose "Processing". If you want more than one output (the same output numbers as in your VEP instance) select them here. I just click "Auto map outputs" and all outputs are selected.
5. Select "Use fixed size buffers" (click "yes" if you get a warning) AND select "Process maximum size buffers" in the More dropdown menu. This is the crucial part of the CPU issue.
6. 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. I use 1 buffer (low latency) but based on your resources you can choose 2-4. "None" will still use quite a lot of CPU but could work for smaller projects.
You can save this as a preset so you only have to do this once. The only thing you need to change is the port number. So the next instance will be port number 2.
So with the next instance, the CPU meter will show 4, then 6, then 8 and so on. 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.
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. So if you are like me, trying to figure this out, this post is for you.
Issue:
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. But using 0 buffers won't work in the long run because of crazy CPU usage and how FL Studio handles latency.
Solution:
1. Open the Vienna Ensemble Pro (64Bit) plugin in FL Studio. (And of course, have the VEP Server opened on the computer or slave)
2. Set buffers to "none". VEP should now be ready to work but as you can see the CPU meter is at 9 already. If you don't do this first, FL Studio will most likely become unresponsive when doing the next step.
3. Open the wrapper settings. Select the port for this specific instance (the same port number as you use for your VEP instance).
4. Choose "Processing". If you want more than one output (the same output numbers as in your VEP instance) select them here. I just click "Auto map outputs" and all outputs are selected.
5. Select "Use fixed size buffers" (click "yes" if you get a warning) AND select "Process maximum size buffers" in the More dropdown menu. This is the crucial part of the CPU issue.
6. 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. I use 1 buffer (low latency) but based on your resources you can choose 2-4. "None" will still use quite a lot of CPU but could work for smaller projects.
You can save this as a preset so you only have to do this once. The only thing you need to change is the port number. So the next instance will be port number 2.
So with the next instance, the CPU meter will show 4, then 6, then 8 and so on. 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.
Last edited: