What's new

VEPro 7 Slow loading time with Studio one 5

deemarcus

New Member
Hey community!

I have a question as I couldn't find it anywhere on the web. I made a template in Studio one, routed with VEPro 7, 120 instruments split in 5 instances, so not that much.
Anyway, I wanted to speed up loading time so i disabled every kontakt instance in Vienna on startup. When i open Vienna server, and open that template, it runs within a seconds.
Anyway, when i open project in Studio One and when Studio One starts to raise instances from Vienna, it takes forever, same time like everything is enabled in VEP.

So my question is, what's going on with Studio One, why loading time is so slow when every instrument is disabled ?

Just to mention, my config is perfectly fine, 64gb , i7 9th gen, so it's not about that.

Thanks!
 
Last edited:
OP
D

deemarcus

New Member
Thread starter
  • Thread Starter
  • Thread Starter
  • #3
I am doing it right now. Template is opened and It's unbelievable - still very slow, it says loading device: and it takes forever
Turning windows defender off is not resolving issue either
 
Last edited:

samphony

Senior Member
Make sure that a vep instance has maximum of 8 midi ports. Anything above 8 midi ports will make working with vep and S1 a pain.
 
OP
D

deemarcus

New Member
Thread starter
  • Thread Starter
  • Thread Starter
  • #5
Haha you were right. I raised it to 48 midi ports to be default as i wanted to build template with one kontakt per instance. Meanwhile, i loaded same template with 48 midi ports in Cubase 10 and it loaded like charm.
Being unable to raise template with more than 8 midi ports fastly could be reason moving to Cubase permanently now. Thanks!
Make sure that a vep instance has maximum of 8 midi ports. Anything above 8 midi ports will make working with vep and S1 a pain.
 
Last edited:

Franklin

Member
Make sure that a vep instance has maximum of 8 midi ports. Anything above 8 midi ports will make working with vep and S1 a pain.
Just a quick question to be sure: Does this limitation of 8 midi ports only occurs when using VE Pro 7 with Studio One 5 and has there been a solution in the meantime?
 
OP
D

deemarcus

New Member
Thread starter
  • Thread Starter
  • Thread Starter
  • #7
You are not actually limited. It's just dramatically slower if you go with more than 8 while loading template/project. VEP has best integration with Cubase, proven
 
Last edited:

Dirk Ehlert

Dirk Ehlert
I raised that with S1 support and it’s kind of a known “bug” . Very annoying as it’s kind of the last step for me to completely jump off off Cubase (besides working with picture) but given their history of listening to their client base (just look at the latest additions in 5 and 5.1) I hope and assume it won’t be long till that is fixed as well.
 

Synetos

Departed Member
I raised that with S1 support and it’s kind of a known “bug” . Very annoying as it’s kind of the last step for me to completely jump off off Cubase (besides working with picture) but given their history of listening to their client base (just look at the latest additions in 5 and 5.1) I hope and assume it won’t be long till that is fixed as well.
I was experiencing this until I upgraded Windows 10 to version 20H2. I did a clean insall of Windows 10 20H2 on my DAW machine, and then installed Studio One v5.1 and I do not experience the delay any longer.

In fact, Nuendo 11 is the one that sets all my VEP instances to 8x the actual sample rate. I run at 64 samples, and one buffer is 512 samples. So...Studio One is getting more of my attention now. :)
 
Last edited:

Synetos

Departed Member
Plus...Studio One can actually report the midi port sequence properly. I use to keep all instances to 9 ports since Cubase/Nuendo couldnt figure out how to sort them correctly. I love it now that I can go beyond 9 ports per instance and see things in the proper sequence.
 
Last edited:
OP
D

deemarcus

New Member
Thread starter
  • Thread Starter
  • Thread Starter
  • #12
I am not sure how you got that result, I used Studio one for 5 years and got better performance in Nuendo/Cubase for mentioned
I was experiencing this until I upgraded Windows 10 to version 20H2. I did a clean insall of Windows 10 20H2 on my DAW machine, and then installed Studio One v5.1 and I do not experience the delay any longer.

In fact, Nuendo 11 is the one that sets all my VEP instances to 8x the actual sample rate. I run at 64 samples, and one buffer is 512 samples. So...Studio One is getting all my attention now. :)
 

Synetos

Departed Member
I am not sure how you got that result, I used Studio one for 5 years and got better performance in Nuendo/Cubase for mentioned
I don't know either, but it is working...except Studio One will hang if I try to delete a track/instrument for VEP, so not flawless. I just dont have the performance delay loading...but I did, initially.

I just bought Studio One a few months ago. Longtime user of Cubase with VEP.
 

Synetos

Departed Member
Meh...first date bliss wore off. I am back to Nuendo with VEP.
Too many little things that I found annoying...like I saw no way to import key switch maps. I am not doing them all manually, when I can edit them in a text editor.
Really, the inability to delete a VEP track without crashing is a deal breaker by itself, not just an annoyance.
 

maestro2be

Senior Member
Meh...first date bliss wore off. I am back to Nuendo with VEP.
Too many little things that I found annoying...like I saw no way to import key switch maps. I am not doing them all manually, when I can edit them in a text editor.
Really, the inability to delete a VEP track without crashing is a deal breaker by itself, not just an annoyance.
That sucks. I have 200 instances of VE Pro and 1500+ tracks in my Studio One v5 template and it never crashes. These little things are maddening at times. Perhaps it's very specific to a plugin you have and use that I don't. I remember when SPATv3 would crash VE Pro every time I touched it. I figured out it was the issue, worked with VSL support and now it's flawless and crashless. Good luck getting it all sorted out!
 

Synetos

Departed Member
I have not totally given up on it. I really like Studio One V5 workflow. I fully intend to keep working out the issues, but I need to be productive, too.

I was also experimenting running VEP in standalone mode, but it became a mess trying to get the midi channels sorted out in S1 with ipMidi. At the eod, I do not see it as helping over just running VEP in server mode.

For simplicity, last night I rolled back to a single machine (7980XE). I think I became spoiled at how well VEP performed in local host mode on that machine.

Some issues I was experiencing could simply be Win10 v20H2, network/switch issues/nic drivers, etc. Most of those variables get removed from the lineup when I go to a single machine setup.

I still have not had the slow loading times return as the OP has been experiencing. I will install S1 back on my 18 core DAW and see if it comes back. Will report the result.

Edit:
RESULTS: Studio One v5.1 on my 18core has no issues with delayed loading of VEP, or deleting VEP instances that are running in local host mode (cant test across network since I deleted everything on my other computer. I know it was having the slow loading thingy on my 18core before upgrading the OS to 20H2. That was an in place upgrade, not a clean install. Maybe that is the solution for OP?
 
Last edited:

madfloyd

Active Member
I'm experiencing the slow loading times. I am new to VEPro so I thought there might be something I'm doing wrong but I have a large orchestral template that Studio One takes almost as long to load as VEPro does (except VEPro loads samples while Studio One does not).

I can't imagine trying to rework every instance to have a max of 8 midi ports. I thought the recommendation was to have as few instances as possible...
 

Lukas

Senior Member
I can't imagine trying to rework every instance to have a max of 8 midi ports. I thought the recommendation was to have as few instances as possible...
Yes - but it's a Studio One issue and PreSonus is already working on it. So it's likely to be fixed in the next update.
 
Top Bottom