I am inclined to agree.

2 years is patient. The amount of other libraries being released by your company, you clearly are paying the people to do that… can you not spend the resources on coders to finish this transition? The problem is that now your hold up is not just effecting your products, which if were just your products being run then you would swallow the extra overhead with rosetta as a “that sucks, but it is what it is”… but it isn’t just yours, it’s now an overhead which is forced onto any and all other software because you can’t run both rosetta and native at the same time.

2 years is a long time VSL. Genuinely. You are in a tiny tiny minority of music software developers and developers in general to have NOT upgraded, or not even delivered a beta yet?

I am, like so many others getting to the point where I can’t put off upgrading any more. True, music is one of the least taxing affairs amongst the creative workspace… but a lot of people don’t have the luxury of ONLY doing music, forcing upgrades in order to stay current with other software, or as hardware fails not wanting to spend a lot of money on completely outdated mac hardware that has less support life and is nowhere near as good bang for buck or investment. I myself have put off upgrading my hardware now since 2017! Originally planning for 2020, then postponing again until software moves over… You are the last on the list, by a good margin. My computer getting old, and I will have to upgrade soon, and to be honest the rosetta 2 tax on your software is MORE than the tax of not running your software and just loading each instance into logic. Whilst I would be unable to run a slave computer… the Apple silicon is so good that I might not need it. At that point, I would not bother with Vsl. Instead of my original plan, to grow my software with you and start transitioning to more of your libraries over East West and others.

People are getting put into a position now that they will be forced to choose between abandoning your software in order to stay with Apple, and as time goes on, that number will not get smaller, only bigger.

2 years is rather a long time for nothing more than a “we are working on it”.

So possibly a bit of a tricky question, but here goes.

I am using VEP5, Master Macbook and slave PC. I frequently work away from the slave, and as such, have bought an external SSD which has duplicates of all my samples hosted on my slave machine, in internall SSD's. 

So my question is this:

If I start a project on my Laptop, is it possible to have all my metaframe templates that are set up on my slave machine, work and see the external drive as a target drive? Put another way;

1. Start project on Macbook, load my 'master templates' in logic - which automatically loads instruments from external drive - write and compose

2. Save project! - Saving along with it the template setup, and any other instruments i have loaded in Logic through VEP5.

3. Plug Master machine into slave. Open up the same Project in Logic.

!!!4 - Slave can see that the external drive is no longer available (as I don't plug it in to the PC) - so instead loads the instruments from the internal drives.

5. Carry on working on project with master and slave.

!!!6. Unplug Master from slave, plug in external Sample drive, open VEP5 on master. Load the same Project in Logic.

7. VEP5 on master can see that the internal drives being used for the project on the slave machine are no longer available, loads from external drive instead.

8. I am happy and do a little dance.

 

Is this possible? I hace tried to get this working, but it just doesn't load the instruments. 

 

Thank you