So I have a session on a slave with already loaded up VEP7 and when I boot a new logic session, logic automatically tells VEP to load the instruments of THAT session, thus creating a much larger session, sometimes doubling instruments, renaming them "1" and "2" at the end. Any one else experience this? Also, the RAM tends to get used up when popping back and forth between Logic Sessions.
-
VEP 7 loading instruments automatically.
-
@jason_22991 said:
So I have a session on a slave with already loaded up VEP7 and when I boot a new logic session, logic automatically tells VEP to load the instruments of THAT session, thus creating a much larger session, sometimes doubling instruments, renaming them "1" and "2" at the end. Any one else experience this? Also, the RAM tends to get used up when popping back and forth between Logic Sessions.
the instruments that are not decoupled will load from Logic to VEP. The decoupled ones stay in VEP .
If you click on the lock, it preserves them open and asks if you want to update with the information of the new session in Logic or not using an arrow
Before you start Logic, start VEP.
They need to heavily update this app, because it is not that smart still... The button should be “couple” and the explanation is “subordinate the instance data to the corresponding project file in the DAW” Or “make it independent from the project file of your DAW”...
