194,165 users have contributed to 42,912 threads and 257,926 posts.
In the past 24 hours, we have 1 new thread(s), 13 new post(s) and 85 new user(s).
Hi Martin,
One thing that I believe would be a benefit would be to have the ability to save channel strip configurations within VE PRO. Similar to Logic but unlike Logic, save not only the instrument and plug-in settings but also the pan, sends and color. This way if one has a template established, but wanted to swap out one instrument for another, complete setups of that instrument could be saved for an easy switch.
One thing that I believe would be a benefit would be to have the ability to save channel strip configurations within VE PRO. Similar to Logic but unlike Logic, save not only the instrument and plug-in settings but also the pan, sends and color. This way if one has a template established, but wanted to swap out one instrument for another, complete setups of that instrument could be saved for an easy switch.
That is in the todo list already.
Excellent. It would really be nice that ALL parameters are stored including bus sends and the amounts. I questioned this with Apple and Logic a couple of years ago and they were against storing the bus sends and the values of sends. For me, one that uses wet/dry ratio setups, one is not really saving an instrument/environment setup in a channel strip unless all the parameters are stored. Sounds like your team is on the right track with this one. Thanks for the reply.
About the meta files, I would like them to be fixed.
Saving/recalling the meta files from VE Pro server 64 bits works fine. But there is a bug with the 32 bits VE Pro server. When you doble click such a metafile that contains Kontakt instances, it gives you a loading error. This error happens only when you doble click the meta, because if you open the meta from the server ir opens fine all the kontakt instances.
I found out that such 32 bit server meta files, when you look in the file info, open with, it alows you only to be opened with the 64 bit VE Pro server. I think that is a bug and should be fixed with the new update.
txs
I think it is not really a bug - since the operating system can only automatically open a file with a specific extension with one application (unless some specific workarounds are done).
I'll change the format name so a file that has been saved with a 64-bit instance will be called ".mframe64". This will still be possible to load in a 32-bit instance, but then the loading has to happen happen manually, from the file menu.
This will not come with the new update, but rather with a following one - since the current update is frozen awaiting positive test results from our beloved beta team.
<You can place your favorite default metaframe in your startup folder (in OS X, it ́s the Login Items
defined in your accounts, see below), so that all samples and settings are loaded up when you come
back from your morning coffee! >
So if I understand it right, what you say in the VE-Pro manual is not posssibe at the moment if you want to load this way a 32 bit metaframe file, right?:
This will not come with the new update, but rather with a following one
Do you have an idea of how long we will have to wait for that
best
Q: So if I understand it right, what you say in the VE-Pro manual is not posssibe at the moment if you want to load this way a 32 bit metaframe file, right?
A: Correct.
Q: When can we expect the mframe32 / mframe64 feature that allows us to load the correct server on startup?
A: I actually already implemented this yesterday, but the version which will be released today does not contain this feature. There will be another maintenance release very soon.
When I reload a saved metaframe all instance windows will be opened. I don't know what other user think but for me it's circular to close all these windows again (16 windows, other user may use more). Maybe it's possible to remember in the saved metaframe which instance windows were opened on saving and only open these windows on reloading?
Best regard,
Peter