Something seems to have changed about how DP and VEP work together for me. It used to be that when I connected to VEP on my slave computer and I switched to a new sequence ("chunk") in the DP file the old sequence "let go" of VEP and the new one could connect to it. Now I have to manually disconnect from the slave before switching to the new sequence and manually reconnect back to it once I have the new sequence loaded.
Basically I used to be able to set up VEP connections in every sequence and switch between them and VEP would take care of connecting and disconnecting automatically so I wouldn't have to think about it.
I'm probably missing something obvious...
Vienna Ensemble Pro question
Moderator: James Steele
Forum rules
This forum is for seeking solutions to technical problems involving Digital Performer and/or plug-ins on MacOS, as well as feature requests, criticisms, comparison to other DAWs.
This forum is for seeking solutions to technical problems involving Digital Performer and/or plug-ins on MacOS, as well as feature requests, criticisms, comparison to other DAWs.
-
bralston
- Posts: 586
- Joined: Fri Oct 15, 2004 10:01 pm
- Primary DAW OS: MacOS
- Location: Los Angeles, CA
- Contact:
Re: Vienna Ensemble Pro question
The best way to us VEPro in DP is to:
1. Put all VEPro instances in a V-Rack so if you change chunks, DP will not trigger a reload of VEPro.
2. Once you load everything from your sequence or template..."decouple" all the VEPro instances. This can be done in one click. Then opening and closing DP sequence files...and or changing chunks will not force any reloads on the VEPro side and it will just reconnect when the new sequence is loaded up. If that is not happening...not sure what is going on for you.
1. Put all VEPro instances in a V-Rack so if you change chunks, DP will not trigger a reload of VEPro.
2. Once you load everything from your sequence or template..."decouple" all the VEPro instances. This can be done in one click. Then opening and closing DP sequence files...and or changing chunks will not force any reloads on the VEPro side and it will just reconnect when the new sequence is loaded up. If that is not happening...not sure what is going on for you.
Regards,
Brian Ralston
___________________________________
- MacPro 7,1 3.2 GHz 16-core Intel Xeon W, 384GB 2933MHz DDR4 RAM, OS 10.15.7, 2TB SSD OS drive, 6TB Samsung Pro EVOPlus SSDs via Sonnet 4x4 M.2 PCIe card, Graphics card: AMD Radeon Pro Vega II 32GB, UAD-2 Quad, DP 10.13, DP 11.0,
- 15" MacBook Pro 2.3GHz 8‑core 9th‑generation Intel Core i9 processor, Turbo Boost to 4.8GHz, 32GB 2400MHz DDR4 mem, Radeon Pro Vega 20 w/4GB HBM2 mem, 2TB SSD storage, OS 10.15.7, 2TB SSD, DP 10.13
Brian Ralston
___________________________________
- MacPro 7,1 3.2 GHz 16-core Intel Xeon W, 384GB 2933MHz DDR4 RAM, OS 10.15.7, 2TB SSD OS drive, 6TB Samsung Pro EVOPlus SSDs via Sonnet 4x4 M.2 PCIe card, Graphics card: AMD Radeon Pro Vega II 32GB, UAD-2 Quad, DP 10.13, DP 11.0,
- 15" MacBook Pro 2.3GHz 8‑core 9th‑generation Intel Core i9 processor, Turbo Boost to 4.8GHz, 32GB 2400MHz DDR4 mem, Radeon Pro Vega 20 w/4GB HBM2 mem, 2TB SSD storage, OS 10.15.7, 2TB SSD, DP 10.13
-
dix
- Posts: 3098
- Joined: Fri Oct 15, 2004 10:01 pm
- Primary DAW OS: MacOS
- Location: San Francisco
- Contact:
Re: Vienna Ensemble Pro question
+1 for keeping VEP instances in a V-Rack. That's what I do. ...though I'm not sure you need to do 2 as long as the Chunks don't have any VEP instances in them.
14-inch MBP M1 Max (2021), 13.6.x, 64GB RAM, UAD Quad Tb Satellite, 4 displays ::: 2009 4,1 > 5,1 MacPro 12-core 3.33 ghz , 10.14.x, 96GB RAM, GeForce GTX 770 , NewerTech eSATA/USB3 PCIe Host Adapter, UAD-2 Quad, ::: 15-inch MBP (2015) 10.14.x, 16GB RAM ::: Lynx Aurora (n) USB ::: DP (latest version), Vienna Ensemble Pro danwool.com
Re: Vienna Ensemble Pro question
I tried putting VEP in a V-Rack today, that workflow works for me, thanks!