Originally Posted by:

i searched the forum but so far i could only see a solution for windows users.

SOME of my waves plugins show up as VST versions (v12) but the V9 ones are not on the list. If i go to AU and insert studio rack than i see the v9 versions under studio rack but the interface gets after opening and closing the window all blank so you can neither see studio rack nor the plugin inside it.

any ideas?

Did the older versions get placed somewhere else? Are you on OSX? Can you find documentation where the plugins go installed and if they maybe were placed in an additional folder. The only other thought I have is maybe they are old enough that there could be a 32 v 64 bit problem and that is why they aren’t showing up. Can you check in the 32 bit versions of VEPro and see if they show up there? 

Originally Posted by: Adia

Hello, I will have a bigger Mac for my DAW and I want to work sometimes on this bigger Mac and sometimes on my current MacBookPro. I am investing in new computer so this is why I need to know what I can expect.

Is there any quick way to not have problems to switch between external VEP IPs for Logic so it can understand what I want to do:

1. Current scenario: I use my MBPro 255.255.1.6 and connect to the external Windows MAchine that has IP 255.255.1.7. All my projects since a few years open with this configuration

2. Scenario 2: I I want to work on my new DAW Machine with the IP 255,255,1,5. and still connect it to my 255.255.1.7 Windows Machine. There will be difference in DAW IP,  does it matter? Or my projects will open correctly in spite DAW IP has changed?

3. Scenario 3: I want to use the VEPServer on the same DAW Big Machine 255.255.1.5  What can I do so my old projects open and I can work the way I choose?

The IP of the VEP is somewhere encoded in the Logic file? Is there a way to have a control over it? I do not want to change IPs of current computers to not to have conflicts (there is a time machine backup etc)  but please focus on reply on my 1.2.3 scenarios. Thank you

Hey Adia,

Sorry no one got back to you sooner. And it would be a good idea to get in touch with official VSL support on this. But the way I understand your scenarios whatever your DAW machine’s IP is shouldn’t matter, just so long as you are on the same subnet, VEPro will find the instances that you previously connected to. Especially since it seems you have them setup as static which certainly helps. And switching which DAW machine you are using shouldn’t effect the connection. If it were the Slave machines that were changing IP then you might have an issue but I think VSL has done some work so that even if your Slaves have DHCP assigned addresses they are still “re-link-able” if they can be discovered (which would again require you to be on the same subnet).

In your third (3) scenario that is a bit more difficult to be precise about. Assuming you only have one Slave machine then that would actually be a relatively easy change to make, just open up the Slave VEPro project on your local DAW machine and connect to the local instance. You’ll need to delink your old project the first time you open them but after that they should remember the new instance locally on your DAW machine and not the remote Slave version. If not you’ll just need to re-link it properly as required. If you have more than one slave then you’ll need to combine the multiple projects wich will be tricky. I would suggest creating channel sets and importing the project that way as there is no good way I know of to do this. But maybe there is an import project functionality that i am not aware of. I did this when I was still in VEPro 6 so things could have changed or been updated since I last needed to do this. 

Hey Alan,

So while I haven’t experienced this exact issue I have experienced a similar one with crackling and popping while Google Chorme is running at the same time ProTools is. Especially when using VEPro inside my ProTools orchestration template. I found the culprit to be Google Chrome and so have stopped using it for the most part (completely stopped using it while running ProTools). I found Firefox to be a viable alternative that didn’t exhibit the same behavior. I’d be curious to know if you find the same thing to be true in your situation.

I wanted to drop in here and see if anyone has had a similar issue to me. I am running a rather large (at least for ProTools) template and ever since I started working with it back about a year ago I have been solving all of my issues slowly and resolving them. But one that has been hanging around since the beginning is a rather large delay in pressing start/stop and the ProTools GUI freezing then about 3-5s after starting the GUI catches up. Audio does playback during this but it also causes issues when recording midi information and it makes it hard to quickly reset and try a take again or just to simply start and stop playback quickly without interrupting workflow. Right now I have it narrowed down to a few instances in my template which makes me think its the VIs and not VEPro, but i was curious if anyone had any further suggestions. Here is a youtube video of what is going on. I have also tried stripping out all unnecessary tracks (leaving just the VEPro audio tracks) with the same results. So I feel fairly confident that ProTools is not the culprit here.

Thanks for your help.

What is your VEPro plugin in Logic set to for its buffer? I have had trouble when I set mine below 2 (i.e. crackling, and "distortion" in playback). I would suggest that the ideal settings are 256 buffer size for your host (Logic), and a 2 buffer for the VEPro plugin. 

First off I know, not the best DAW.

Is anyone else experienceing a sever amount of lag/unresponsivness when starting/stopping playback/record in ProTools Ult 2019.6? My template is in the neighbourhood of 600 midi tracks 200 audio tracks. Starting and stopping playback/recording is very delayed and always freezes teh GUI for a few seconds before it catches up, and sometimes ProTools will become unresponsive. 

I'm on a Windows Machine with a 7920X, PTU 2019.6 and VEPro 7. My two slave machines are hardwired into my main gigabit network (I have tried running them on a seperate physical network with no change in behaviour) with Static IPs (both machines are windows machines, one a Threadripper, and one an intel 7820X, each with 64GB of RAM). 

Let me know if I can provide anymore information or if you have any ideas. 

Thanks,

- Walter

Hey everyone,

So I wanted to chime in here. In building my own template in ProTools I have found out many things and I ran into problems like this as well. First to respond to the OP Julian, since its working some of the time I would guess that this is CPU bound. And since you are running VEPro and PT on the same computer I would guess that your computer can't handle the load at reasonable buffer sizes. Also since you can disconnect/turn off plugins and it works would also indicate that your CPU isn't able to handle the whole template you are trying to use. To add to this you are running all of your samples off of one drive, which yes I can hear you furiously typing, is SSD but remember that the SATA interface on what I assume is a 2012 MacPro 5,1 is 3 Gb/s add to that (depending on the quality of your SSD) delays in the response times of the SSDs and you just add more stress to your CPU which is trying to do this with the "DAW-that-wins-the-award-for-not-playing-nicely-with-others". I do have a question for you though, you said you have a dual CPU Cheesegrater with 2 3.33GHz CPU's... I couldn't find that as a shipping system built by Apple from the 5,1 lineup. Did you put in "aftermarket" CPU's or is this a stock config? Are you sure that is your base clock or is that the turbo clock speed? I would also be slightly concerned about RAM speed, but I haven't really looked into what speed causes bottlenecks. But its low enough that I would look into it. And finally, I would try setting up your template at 48kHz, in fact I would guess this might solve half of your problem since at 96k you have half the time you would at 48k putting twice the strain on your CPU. The higher your sample rate the less time your CPU has to do the same amount of work, the less time your SSD has time to respond, the less time your RAM has to respond. // Oh and in regards to your follow up post. Were these channels virtual instruments? Reverbs? Any correlation to what you disabled? And what if you started using those VI's, plugins again? Did CPU usage increase? Maybe something in Kontakt is loading, and when you turn it off and then on again it isn't loading until its used? Or maybe its something to do with ProTools and Dynamic Plugin Processing? Do you have that enabled? Maybe try disabling it and seeing what happens?



Jan - I saw this same behavior (if not so extreme) when I was troubleshooting VEPro and PT. And I still do see this uneven core usage reported by PT today when everything is working. However when it didn't work it was because PT was unable to handle the Project I was trying to playback. But since you said that it doesn't matter what VEPro buffer you set I would guess that your slave machine is hitting above 80% CPU usage? Or maybe higher? Whenever this happen for me (i.e. I put a synthetic load on my slaves and run an active VEPro project) I hear dropouts of instruments, pop and clicks, or a playback error, combine with high CPU spikes reported by PT. And its always because my slave CPU usage is too high. Also if you are also running a 5,1 MacPro then I would guess in addition to high CPU usage slow 3Gb/s SATA interfaces, and a single SSD for samples as contributing factors to inoperablility. But a few questions for you as well, are you running 5,1 MacPros? What are their specs (especially CPU)? Dumb question, but are you running a gigabit network on all machines (built in NICS on 5,1 MacPros are Gigabit, just want to make sure you aren't running through a 100 Mbps switch or anything like that causing a bottle neck)? The lowest setting for VEPro I would set is project at 48kHz sample rate, VEPro at buffer 2, ProTools at buffer 256. Anything lower I have found to be unstable or unusable. And finally remember that AVID/ProTools doesn't play well with others, so maybe this is a PT glitch, have you tried the standard trouble shooting steps? Trashing Prefs, rebooting? Uninstall and reinstall? I'm having no problems here running 512 MIDI tracks and 250 voices on my system, so it does work... but it can be a pain to get it to work.

Sorry for the long post, hope it was helpful.

-Walter

Hello all, I have been working on building my template in ProTools (PT) and VEPro for a while now. It is currently functioning however I have more latency than I'd like for playing parts in real time. (2 buffers, at a hardware buffer size of 256 for PT). So my question for you all is does anyone have experience with PT and VEPro? And does the fact that PT isn't terribly stable and is giving me an error message about PT running out of CPU resources, mean throwing more cores into my computer would solve the problem? 

Session specs: 512 midi tracks, 256 audio tracks (or near enough). I konw I am at the max system specs for PT without cards... maybe this is part of the problem too?

Computer specs: DAW system - Trashcan Mac Pro Quad-Core Xeon 3.7 GHz 16GB ram. 

Let me know if I can provide any more information! And I appreciate your help!

-Walter

Hey Lior, did you ever figure out what was going on? I seem to be having a similar issue.

-Walter