-
Confused about why you'd use a single instance of VE Pro
I can see using VE Pro to distribute the workload across several machines. How is a single instance of VE Pro different from just using the DAW as the plugin host? Is there a special benefit if a mix of VI Pro and Synchron libraries are being used?
-
A few advantages you get to using one VePro server, even on the same machine as the DAW, include:
- you can have a single VePro server project that says loaded all the time while you switch between different DAW projects; without having to reload all the samples into the DAW project each time
- Having one common VePro project shared between multilple DAW projects can mean that certain mix decisions can also be shared. For example, if you use the VePro mixer to apply EQ, FX, level balancing, etc.. then you can reuse that balanced and mixed orchestr across several DAW projects and preserve the same mixed sound and not having to re-engineer the sound each time.
- If you are using VSL instruments, then VePro has some little built in features for managing VSL instruments and MirPro settings, that streamline workflow just a little bit compared to using VSL instruments and MirPro directly in the DAW.
- VePro7 now includes the Vienna Suite built in, with a bunch of EQ presets in particular that are already engineered and related to VSL orchestra instruments. Could be helpful.
- Some DAW's don't do a great job of freeing up memory when you disable tracks (ie, LogicPro). VePro does a much better job of that FWIW. So if you liike to use extremely large project templates, and enable/disable tracks as you go, with LogicPro, eventually you may run out of RAM because it will not properly free the memory when you disable tracks, but VePro does.
- VePro cpu handling is very efficient. Some DAW's are equally efficient, some are not. OSX Cubase for example is notorious for not being great on this point so using VePro may make it possible mix projects with Cubase that would not be possible without VePro. That situation with Cubase seems to change from version to version though, so... some of this could be urban legend.
- you can have a single VePro server project that says loaded all the time while you switch between different DAW projects; without having to reload all the samples into the DAW project each time
-
Some DAW's don't do a great job of freeing up memory when you disable tracks (ie, LogicPro). VePro does a much better job of that FWIW. So if you liike to use extremely large project templates, and enable/disable tracks as you go, with LogicPro, eventually you may run out of RAM because it will not properly free the memory when you disable tracks, but VePro does.
VePro cpu handling is very efficient. Some DAW's are equally efficient, some are not. OSX Cubase for example is notorious for not being great on this point so using VePro may make it possible mix projects with Cubase that would not be possible without VePro. That situation with Cubase seems to change from version to version though, so... some of this could be urban legend.Hi Dewdman42,
Totally agree with the above. I have almost the same setup as you and Cubase struggles to run modest size templates so more often than not, i'm having to run VEP on a mac mini i7 16gb RAM. However i'm having strange issues with VEP 6 in slave mode on the mac mini where Kontakt is always hitting 100% even though they're being streamed from the Mac Mini SSD. Could you offer any advice relating to the best set up options when using Kontakt in VEP in slave mode? One option that was suggested is to opt for a 10G ethernt upgrade instead of the standard gigabit. Not sure how that can work for the MM as it's not as upgradable as the Mac pro. Anyway, any suggestions would be very welcome.
Thanks in advance
-
I had to check what a Mac Mini was. The currently advertised ones list 10gbe Ethernet as available. There are also Thunderbolt 3 to 10gbe adapters on the market. Is your 48 GB machine not enough? My laptop with 48 GB RAM is my music machine. If I get into VSL will I need to get my server (Cisco C460, 40 cores, 128 GB RAM) into the game?
-
I doubt you need to to go to 10G networking. This probably has more to do with the CPU in your MacMini. What do you have the thread count parameter set to in VePro preferences? How many channels of instruments are you trying to run? How many VePro instances? what else is running on the MacMini? how many return audio channels are you streaming back over the network to your MacPro?
-
HI,
Thanks for the reply.
What do you have the thread count parameter set to in VePro preferences?
Currently thread (core) count per instance is 1 when using multiple instances but 2-3 when one instance is being used. As i understand it the general guidence is divide how many available cores by the amount of instances leaving at least one for the OS. Also should mention I set each VEP plugin in Cubase to 1 buffer as that is then a multiple of the buffer set in the I/O which is usually 256 samples for the FireFace 800. So 1 VEP plugin buffer = 256 samples of latency, 2 buffers = 512 etc.
How many channels of instruments are you trying to run?
No more than 3 Kontakts each playing 2-3 instruments (strings etc) usually in one instance
How many VePro instances?
Normally only one. Have tried to split instruments over multiple instances (strings one instance, brass one instance etc) but the result/performance is the same
what else is running on the MacMini?
Nothing other than the OS and synergy which enables me to use one keyboard/mouse for all connected macs. No BT or Wifi, all disconnected.
how many return audio channels are you streaming back over the network to your MacPro?
8 stereo tracks maximum with 8 midi channels per instance
So really this setup shouldn't be a heavy load for either Mac but i have the same issue if i use the other Mac Pro 1,1 with upgraded CPU (6 core 3.6ghz, 48gb ram & 3 SSD's) in the same setup. I end up using one mac as a FX & synth slave and the other to get as many Kontakt sample instruments as possible before having to print or freeze tracks, with the Mac pro 5,1 as the master running Cubase and any other low level bus processing. The Mac 5,1 and Mac Mini are running 10.13.6 and the upgraded Mac Pro 1,1 is running 10.11.
Theoritcally i should have enough CPU, RAM & SSD power to run a fairly heavy template but in reality, that's far from the case. Which is why i'm looking at the ethernet as a possible culprit but if the general feeling is, 10Gb won't or shouldn't make a difference then there must be something else going on?
Again any suggestions and or guidence would be appreciated.
Thanks,
MD
Forum Statistics
195,405 users have contributed to 42,984 threads and 258,234 posts.
In the past 24 hours, we have 6 new thread(s), 20 new post(s) and 56 new user(s).