181,930 users have contributed to 42,194 threads and 254,635 posts.
In the past 24 hours, we have 4 new thread(s), 13 new post(s) and 52 new user(s).
Hi
I run a Mac and 4 PC slaves and a large template of 600 midi tracks, 60 odd MIDI ports, currently in DP but looking at Cubase. I have heard that VST3 on large templates take a very very long time to load. So how do people do this?
A/ running literally dozens of instances of VSL EP
B/ Event input rather than VST3
C/ Hardware MIDI interfaces
In Cubase you won´t use Event input, instead you´ll use multiport VST access, remember: in just one VEP pro instance you have available 16 port*16 channel (no more AU 1port*16 channel limitation). In this way if you put in groups your instruments (Play, VSL etc..) to fill all ports in each VEPpro server instance, you´ll optimize CPU thread with fewest instances.@flashman said:
B/ Event input rather than VST3
are you speaking about how long will take to load the project in CUbase and if this time is delayed due to lot and lot of VEP midi ports instances? With respect to this question I have found that the same midi-VI template load a little more in Cubase 7 respect to DP 8. I explain this because DP is a cocoa native app and better optimized for mac than Cubase: I don´t think is due to excessive VEP midi ports. This load time is insignificant compared with the time that take to load all sample libraries into the VEP server instances@flashman said:
And the load times don't get ridiculously long with loads of ports?
Hi Chiming in here because I just installed Cubase 7.5 and my templates with about 1400 tracks are taking 2:35 to load now. in Cubase 7 they took 1:34 and I thought that was a reallyy long time. Not loving this issue.
I had an idea want to bounce around to serve this end.
Would it be possible to run a metaframe in the background of my composing machine that connects to the 3 PC's meta frames and would be there and ready.
For example if I boot up myy meta frames on my 3 PCs and the meta Frame on my Main composeing machine and they connect, then when I opened Cuase all those midi ports would show up like the midi connectins in audio midi setup or rtpMidi and all the audio channels that are coming in from the PC's would show up as hardware connections in cubase.
This would be fantastic and a major upgrade so that the plugs and the intrument instances would not have to be run inside your DAW.
OK 2:35 must seem like forever but its not a deal breaker. It always takes me about 10 minutes to get all 4 slaves up and running in the morning. 1400 tracks! I got given a hard time about 650 by some people. Go you!
The background ot this is we're running 3 or 4 studios on mac pros with dp and logic. I have some big issues with DP8 and can't run it yet. The new macpros are 3 x the price of the equivalent PC so the quesiton is why don't we go to Cubase on a PC? Take a while to learn but if it works for HZ and HGW and others....This load time issue was one potential problem but it looks like I could live with that.
Connection times from Mac to PC does take a long amount of time. However, Mac to Mac is quick. This is why my next slave may be a MINI instead of another PC.
Chris
1400?….my God!!!!!!! ..I just have 400@john_3224 said:
my templates with about 1400 tracks