@Bunford
S1 is a nice daw, unfortunately if you do lots of orchestra, like junkie xl, you may hit the wall pretty fast.
The only alternative is cubase and maybe reaper.

 

Hit a wall you say?



And this is with everything idle, though to be fair it tends to sit around 45% but spike up to 100% every few seconds. I can't work out why though. There are no plugins except VE Pro loaded into S1, no MIDI or audio data in there either, and all there is in the DAW is the instrument tracks linked to the VE Pro servers with an empty Kontakt instance in each VE Pro instance. This is essentially just sitting at idle doing nothing except having been routed to the right connections. And with a Core i7 4960X 6 core, 12 thread CPU with 64GB, my system is far from being a slouch!

 

your midi in is set to omni on that kontakt instance.

 

Your system can handle big projects, S1 cant.
Jump over to the dark side, cubendo can handle that

 

Yeah, i tried changing it to allsorts already and that makes no difference.

I have found the issue but not solved it. When i use the VST2 version of VE Pro I gat option to choose MIDI Channel numbers in S1. When I use the VST3 version I dont.

This is the nub of the problem and cant find a way to select MIDI channel numbers in the VST3 version.

 

Used to own Cubase up until version 7.5 or 8 but rarely used it due to using Ableton then so sold it. D'oh!

 

Last edited: May 21, 2017

Too bad, if you still have the e-licenser you can test it.

 

Literally about 5 days before purchasing Cubase again, Studio One 3.5 gets released that apparently has huge CPU optimisations. If 3.5 would have come out next week, i would have been mightily pissed

 

Heh. Funny indeed. Try it out and see if its optimized now.

 

Contrary to most folks’ opinions, I have found VEpro very helpful in a single machine setup. For example, Waves ABR Chambers and ABR Plates are HUGE CPU hogs. Since S1 doesn’t spread plugin demands across multiple cores very well, it has been very beneficial for me to host said plugins in VEP 6.x.

I have also found VEP very helpful when using Impact Soundworks “Straight Ahead Jazz Horns” since it too is pretty resource demanding. 8Dio’s humongous “Vintage Studio Organ” is hard on CPU as well — again, VEP has been super helpful.

I’m not using VEP to host large orchestral collections, but I can say with total confidence, based on frequent personal findings, that VEP does help even out CPU balancing quite nicely alongside Studio One.

Just my 2 pence . . .

 

** Sorry, double post **

 

In my experience Studio One can't handle large track counts whether it's Kontakt instances, disabled or not, or midi tracks. It starts falling apart past 100+ or so. I once built a 1000+ track template with all single instrument track, disabled instances of Kontakt and some synths like Zebra and Cubase handles it no problem. Save times are like 2 seconds. Just enable a track and go. Each shows up as a single stereo track in the mixer, easy to automate, you don't see anything else..

VEPro is an unnecessary complication unless you insist on having everything loaded and ready to go. Personally I need breaks from sitting and need to get some air, do some yoga stretches etc. throughout the day. What's 30 seconds when loading a new cue? One computer is enough, don't want to maintain more than that. Unfortunately I sold Cubase in a fit of insanity and am saving my pennies to get it back. Thought having multiple DAW's was a bad thing for some reason...