Welcome Guest! To enable all features please Login or Register.



Forum Jump  
Go to last post
Posted on Sun, May 21 2023 09:42
by Oskar
Joined on Fri, Dec 13 2019, Posts 7


I started experiencing extremely slow loading times when opening projects in FLStudio a while ago. I think it happened after updating VEPro 7.

Every single Vienna Ensemble Pro VST3 plugin takes ages to load compared to before when it was instantaneous. I did a full clean reinstall and manually deleted all the ProgramData folders and anything I could find, since rolling back to a previous version did not fix the issue.. This worked for a little while, since the load times were fast again. However now that I want to actually do work inside the project like I'm used to I will have to increase the MIDI ports (per instance) to 48 to allow using all the instruments I have loaded inside VEPro server project.. Since clean reinstalling set them back to 8, which is the default, the load times were fast again. But now when I set it back to 48, the loading times are just insanely slow again.

I tried increasing multiprocessing threads from 2 to 24 with AMD Ryzen 9 5900X 12-Core Processor. That did not help.

Not sure what I need these for, but I tried lowering Audio inputs (per instance) from 32 to 2. That did not help either.

I pretty much need to have Audio outputs (per instance) set to 32 so I did not try change that.

Somehow the only thing that seems to bring back the good old fast loading times is decreasing the Audio inputs (per instance).

EDIT (typo): What I meant to say that decreasing MIDI ports (per instance) is the only way to make DAW projects load quickly.


Could you maybe look in to it and try to fix this bug or whatever is causing it, or help me find a solution please?

Posted on Mon, May 22 2023 16:03
by Andreas8420
Joined on Mon, Dec 02 2019, Vienna, Posts 344

Hi Oskar!

Could you please specify? At one point, you say lowering the MIDI (!) ports improves the situation. Later, you state that only reducing the number of audio (!) inputs makes a difference. Which statement is true?

Thank you!

Kind regards,

Technical Support - Vienna Symphonic Library
Posted on Mon, May 22 2023 20:49
by Oskar
Joined on Fri, Dec 13 2019, Posts 7

Hi Andreas,

Sorry about that mistype.. I edited it to specify that decreasing MIDI ports (per instance) is the only thing that helps with loading times.

I want to set it to 48 and have equally fast loading times inside DAW projects, like it was some time ago before a recent VEPro update.

Posted on Mon, May 29 2023 10:49
by Oskar
Joined on Fri, Dec 13 2019, Posts 7

Turns out i did not have Vienna Synchron Player and Vienna Synchron Pianos reinstalled. However it didn't change the loading times installing them again. Still very slow at 48 MIDI Ports (per instance).

I guess big part of the problem and why it's so slow, is having to have a separate instance for each MIDI Port, and a total of 48 instances setup.

I believe there's no way to have multiple MIDI Ports inside one VEPro instance for FLStudio setup (not one that works well anyway). I think for Cubase and maybe other DAWs that's possible. So basically every time I want to use one more MIDI Port, every instance takes forever to load all the 47 unused MIDI Ports.


Basically for my instrument set 1, I have a VEPro instance (eg. Strings1), and 16 articulations all routed to MIDI port 1.

For instrument set 2, a second instance, 16 articulations to MIDI port 2.



Maybe if somehow it didn't scan the unused ports per instance, it could be fast again? I don't know how it works under the hood, so it's just an idea that I have no idea how to achieve.

Posted on Tue, Aug 15 2023 23:13
by Oskar
Joined on Fri, Dec 13 2019, Posts 7


I don't know if you're still investigating the loading time issue or not,

in any case in my quest to still trying to get back to the good old loading speeds I did a few finds that might or might not be of any use if you might or might not be working on a fix for the loading time issue.


So loading my new template 16 MIDI ports (per instance) takes 1min 24sec

Loading the same template with 32 MIDI ports (per instance) takes 3min 19sec

Loading the same template with 48 MIDI ports (per instance) takes 6min 11sec


Well, as you can see the times are not increased linearly, so double the ports double the time isn't the case.

What I found with dividing total seconds with number of ports is that it takes increasingly longer to load a single port when MIDI ports are increased.

5,25 s/port

6,22 s/port

7,73 s/port

Small differences but it adds up when you count it 48 times, which is the number of VEPro VST3 plugins in my template, which takes the bulk of the loading time, while the rest of the template (samples, synths, effect slot plugins) load in 9 seconds.


The other point is I didn't even have a server project loaded in VEPro 7 Server.. So what at least I'm getting is that the issue isn't in the instances or whatever is loaded in the server project, but has something to do with the VST3 plugin.

Again, to point out that it was VERY fast with 48 MIDI ports (per instance) before an update. Might that update have even been some VST3 support or something? I thought it was supposed to be faster? Maybe I'm wrong, but to make it slower with an update this is really annoying for me.

Anyway hope you find a fix for this sometime in the future, and hope this helps narrowing it down

You cannot post new threads in this forum.
You cannot reply to threads in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.