Hi

Any logic users found out if there is any major advances in building large templates with VSL EP7? I see the track count is now up to 1000 which is a bit more sensible.

G

SOLVED

It was windows 10 real time virus protection., It keeps switching itself back on and with it on the load takes 30 mins. Without it, it takes around 5.

I'll definitely look the W10 version as soon as I'm back in the studio.

@Paul! If I do have to rebuild it would be great if there was a way of exporting a CSV of all the instruments, routing, location of sample files, midi channels etc. Would make optimising and rebuilding a template a whole lot easier!  

Hi

I run a large template - 1000+ tracks - in Cubase with VSL ep running on the same machine, I have two studios one windows 7 on a 14 core PC and the other windows 10 and an 18 core pc. The same template takes 5-10x longer to load on the windows 10 machine and I can't work out why. Its the same with the latest updates of VSL EP 6 and 7. To be honest I suspect the answer is fairly obviously  - "rebuild it". But I'm in denial as that's a day or two's work.

Any alternative ideas welcome!

Guy

I would look carefully a the PC network card.  Obviously change the ethernet cable to check. I dont imagine you are using an adaptor of any kind from the mac but if you are change that as well etc. Try running them through a hub or network switch. Use network monitoring software to look at whats happening. Do other network connections drop? Can you see both machines from each other? Very frustrating |I know but just few ideas. Good luck!  

Yes me too...so to speak. spinning blue circle in windows 10. 

Having updated to the latest version of VSL EP 16178 I had some very weird problems with East West software.  The instance containing play instruments crashed on loading and QL Spaces did this even more weird feedback loop thing where all the meters were maxed as soon as it was connected.  So after a lot of faffing about I updated all the EWQL software to the latest version and the problems have now gone away. I can't be sure this was a VSL vs EW issue and it wasn't some other corrupt installation but I thought I would post just in case anybody else bumps into the same issue

Great news though - Logic is back in the game (sort of!)

The announcement says that Logic 10.3.1 supports AU3 and multi port midi. has anybody got this working with VSL EP or does it need implementation from VSL as well?

New Features/Enhancements

• Logic now supports the Audio Unit v3 specification for virtual MIDI ports.

Hi

What is the connection between setting proferences for available audio inpits outputs and midi ports on the master andteh slave? If I change the setting on the master it doesn;t seem to affect the slave and that doesn;t seem to make sense.

So if I am setting up a new number of audio inputs or outputs or midi ports, where should I do it? Master slave or both?!

Yes me too. Just tried the latest version of 6 and a project which takes 8 minutes in VSL5 takes 20+ in VSL6 (windows 10 - 12 core all from ssds, 4 x instances, 120 channels, 40Gbs samples mix of mainly Kontakt and a few Play)

As VSL seems to have been largely re-coded I wondered what the current advice is on thread count and multiprocessing settings to get the best out of it?

It always does that I think. I just cut and paste the one track I need and then delete the rest.

Any news on whether VSL6 resolves the multi device problem in Logic or is that an Apple/AU3 problem?

So the controller issue. Could somebody just clarify for me if I am building a big template using Logic X and VSL, do I only use CC11 for volume or do I have to remap every single channel in some way? I've been speaking to a number of more experienced logic users who recommend using a single instance of VSL EP for each port because it doesn't hammer a single core of the DAW cpu because of all the Aux inputs you use for the multiple outputs, you get full CC control and no port problems but of course your VSL meta looks a bit of a mess!

Hi

Anyone else having trouble making event input work with Play? It connects fine to the first midi port but there's no midi or audio over any of the event input ports after installing the latest version of Play 4.2.2.  I've gone back and forth with Play 3 and Dp7 but just can't get it to work reliably. 

mac pro 12 core 10.9. DP 8.07

Slave PV windows 7 64bit VSL EP 5 latest version

Play 4.2.2

Hi

Have some big metaframes with a lot of aux busses (one for each of the 32 outputs) running reverbs on each output. So for no apparent reason every now and again the bus stops working. You can delete it ad reinsert it but unless you change the name it still doesn't work. Odd. I have 4 slaves and it happens sporadically on any one of them.

I'm running them on i7 6 core PCs with 64 gbs of ram, latest version of VSL, windows 7 ultimate. Most of the instruments are Kontakt 5 and the busses are hosting EWQL Spaces.    

I know its a bit of a weird setup but I thought I would flag it up :)

Thanks

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.

And the load times don't get ridiculously long with loads of ports? Or do you just live with it and go and make a cup of tea or something!

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

It works!

As an earlier poster said you turn off plugin delay compensation in DP (setup>configure audio system >configure studio settings and uncheck Automatic plug in delay compensation) 

Also you have to set the system to run all plugins in real time and turn off pregen in the preferences.

Then it works. You still get latency from the VSL EP system depending on the number of buffers. I'm getting 1200 samples with 2 buffers run on a macbook pro. But that's still a ton better than using external midi. Still working on the finer details of this but this is the first time I've got the thing up and running and I'm using 25 event input plugins, 250 midi tracks on a Macbook pro.

Actually this is all coming back to me now. I tried this when event input first came out and had the same problem with large numbers of event inputs. The only alternative is using midi over lan and external midi in VSL EP. The latency is horrible but you can insert a midi track plugin in DP called time shift and offset everything early by the same number of samples as the latency. Not perfect but it works. The logic environment layer solution apparently works really well and Cubase uses vst3 so doesn't have the problem so its just Pro Tools and us DP people out here!

We need VST3 support in DP then we'd be sorted. 

Just for the record I also have this. I'm building a new template with DP7.24 /8.01 and VL EP with 30 event inputs and I get loads of this. Only on the event input tracks when I have lots of them active. Midi over lan and external midi is a solution but the latency is horrible.

OK now I see exactly what you mean. Just building a new template and wondered where half the instruments had gone. Then looked at activity monitor and watching the memory useage very very very slowly creeping up. Most of my stuff is kontakt 5 so it maybe a K5 problem as well?

*bump*

Personally I would decouple all your slaves and run them as standalone VEP's. The convenience of having all the metadata saved with the sequence was eventually outweighed for me by the speed advantage of leaving them all separate. It also speeds up the save file proceedure in your DAW which emans you are more likely to do it more often! (I am Mac Pro + 4 VEP slaves)