Somehow I did not find that... Had to re-install and then it was there. Anyway, thanks!

First off, rule of thumb: Whatever you may 'customize' on the fly by CC automation does not count when choosing your instruments that go inside VEP in your template. There you tweak everything so it would be a sensible starting point for any project, save it an leave it.

Most options you can get out of sampled instruments by CC automation. The more you use it the less you feel the need to go back into the instrument's GUI to tweak. It takes a bit of thought and setting up, but it is worth it.

Mostly only synths or specific sound design tools etc. would fall under the category of instruments that you'd like to load directly in the DAW.

The whole idea of a template is that you DON'T have to modify your template for the next project.

"Decoupled" is the mode that you'd want to run VEP in most of the time. In "coupled" mode changed from within the DAW get applied to VEP whereas in "decoupled" mode everything stays as you left it independently from whatever you do in the DAW. (E.g. you don't want to have to purge all sample data each time you close a project.) Also, "coupled" mode is a tighter connection to the DAW and naturally, you will feel it by the fact that everything would feel a bit more sluggish and not as snappy as with "decoupled".

Really?
Crickets?
I have to go corpse hunting in the library folders?

Is there an official un-installer for VEP and if yes, where can I find that?

Hi Paul,

Thanks for the reply.

Tracking down these crashes is tricky as the crash reports do not reveal enough detail. All I know it is Kontakt after sitting idle for two or three days. It appears that during that time eventually the CPU meter within Kontakt turns red and hits 100% (this must be the result of a CPU leak) and that causes Kontakt to freeze. Everything then has to be force quit and the usual crash report appears. Some months ago I already had an exchange with VSL support about that (I i sent in in crash reports). Since then I moved from a Mac Pro 2013 to a Mac Pro 2019, from Mojave to Catalina and the same issue happens on the new machine. Needless to say I keep Logic, Kontakt and VEP updated.

The "wishlist" makes me curious. Do items on this list have a realistic chance to become reality?

Sure, so far the theory. In practice however, there are plenty of times when after a crash all the instances have to be re-connected manually. And yes, my instances are always set to "preserved".

Then it would be nice to have a button that helps finding lost connections.

VEP crashes on my machine frequently.
Even with saving projects all the time both in coupled and de-coupled mode I end up in a situation where I have to manually re-connect instances from within Logic Pro to VEP. This is very tiring with over 30 VEP instances.

It would be nice if there was a feature that could scan for the broken connections and upon matching instance names/patch names it re-connects disconnected instances.

Would that be a possibility?

Another thought could be if it was possible to isolate instances containing hanging or crashing plugins and offer a chance to re-start/reload the offending instance without killing the entire VEP session?

Any ideas on this...?

I have the same problem. And in addition to that VE-Pro crashes about every 36-48 hours. The culprit seems to be Kontakt. Some instrument (probably in its scripting) has a CPU leak. Eventually it goes through the roof, the "!" symbol in Kontakt becomes red and the application is no longer responding. It then drags VE-Pro as well as Logic down to hell. Only force-quit helps.

Afterwards even previously saved projects (VE Pro instances, Kontakt Multis) are not always coming back as they are supposed to be. Often it opens older versions of an instance for example that factually does not exist anymore.

You need to use the AU3 plugin version.

Here is a nice post with instruction on how to do it. It works great:

https://www.logicprohelp.com/forum/viewtopic.php?t=143416

I have created a template and have saved the server project. I also have saved all individual instances as well as Kontakt Multis.

As soon as I start VE Pro 7 and load the latest saved project it appears to be a saved version 2 or 3 times behind the latest one. I then have to individually update the instances and reload respective Kontakt Multis.

Of course I re-save the updated instance and also the entire project. But every time - reproducable - when I load the last saved project again it reverts back to an earlier version (which, by itself I do not even officially have anymore). Is this a chaching issue?

Also, perhaps unrelated(?) - every time I select "save" from the menu to save an instance it acts like "save as" - even though the instance file does already exists and should be simply overwritten as "save" should do.

Can someone help/explain what's going on?

Well, the difference is that I now use Kontakt 6.2.
I have one PLAY instance, and a few Spitfire Labs instances. They used to get a long with each other. I know, there can be a million reasons.

I'll try sending a crash report next time.

Also, what is interesting. When idling VEPro says whatever e.g. 7% CPU load - someting that seems right - however, the activity monitor says more than 100% percent load. That is certainly strange.

Since upgrading to version 7 I have seen a lot more crashes and program freezes.

The frustrating thing is that I do not know where to begin troubleshooting - and I do not have days and days to engage in it either.

So far I am running only a local template, with 128GB RAM on Mojave (Logic Pro), 99% Kontakt (6.20) instances, maybe one with PLAY and one with Spitfire Labs.

It already starts by the fact that if the setup is left idling, after 24 hours it will have crashed miserably, ususally preceeded by a program freeze with unusually heightened CPU usage (and not triggered by any action).

Sometimes it also crashes immediately when adding/replacing a random Kontakt instrument patch.

The problem is just that there are no distinct ways to reproduce this. It just seems that there is a general instability to VE Pro that is new. Unless someone has an idea lightbulb coming on all I can say/ask is: Please turn your future efforts back to stability. VE Pro used to be one of the more stable components in whole music setup, now it is a fun-killer.

Originally Posted by: marnix

Hi Crescendo,

the /etc folder resides on root level, is by default invisible and will indeed not yield any results during a system wide search.

Have you tried to access it by selecting "Go to folder..." in the Finders "Go" Menu, typing in "/etc" and confirming?

Best, Marnix

The file was not in there. I don't use spotlight since it never finds anything (I ue Find Any File, way better). I did some research and I found the file in the location you mentioned - but only on my backup drive. A little while ago I made a clean re-install of the system and backed everything up. While doing that I moved from El Capitan to Sierra. The new system installation obviously did not produce a "sysctl.conf". It must therefore be specific to VE-Pro. Since it is in such a exotic location I would not have known that it belongs to VE-Pro and therefore did not know it needs to be copied along with all the other files in Application Support, Preferences etc...

Now, since "sysctl.conf" is back at its place I can open VE-Pro and the message about osascript has not appeared again so far.

Originally Posted by: marnix

Now please select "sysctl.conf" in this folder,

no such file... I did a system wide search (including protected system files) and it seems not to exist.

There is only a sysctl.conf.5 within usr/share/man/man5/ - I don't think it is what we are looking for.

I am getting this osascript message now too every time I start VE-Pro 6 (latest version).
This happened right after I made a fresh install with Mac OS Sierra (used El Capitan before).

I would appreciate some help how to get rid of it.

Sometimes, and these things just happen, there is a small glitch in the network and the connection between host and slave is being temporarily disturbed.

On the host, VE-Pro thinks the connection disconnected, on the slave it thinks it is still active.
 Just to get the connection window up on the host takes about 5 minutes... Then even after forcibly changing the instances on the slave to "disconnected" and trying to reconnect from the host results in an infinite spinning wheel of death.

The only way out of this is to force quit VE-Pro and Logic.

I would really wish to see this:

- A more intelligent re-connecting - and if that is not possible,
- VE-Pro to be more communicate: What is it trying to do that it can't do?
- A safety mechanism for connecting attempts to prevent being in a loop for too long. E.g. after x cycles or seconds of trying to do y, quit the process.

(Logic 10.1, VE-Pro, new Mac Pro + Mac Pro 2008, Mac OS 10.10.3)

I don't think it is a sound card issue (using MOTU Ultralite here). It must be something somewhere between MacOSX/Kontakt 5.3.1/VE-Pro/Orchestral Tools. For a possible solution they probably need to get together in some way and do the trouble shoot in a groupe effort... IMO...

Well, at least right now it works for me under Kontakt 5.3.0 while everything else is in its latest version. It just won't guarantee that it will work in future versions of Kontakt or even the other involved components...

Yes, I had the same problem. But interestingly Kontakt 5.3.1 only had the problem from inside VE-Pro.
If I loaded a Kontakt instance directly from within Logic there were no issues. I also ended up reverting to Kontakt 5.3.0

It seems to have rectified itself.

Still, I find it scary, and I would like to know what that error code "????" means and how to avoid such things in future...

Suddenly, when I restarted my machine today, no information from the eLicenser key was possible to be read. There was a non-sensical error message "????". I have downloaded and installed the latest version of the software.

Conveniently, the eLicenser web site does not list options to contact support.

Can anyone please help?

I am experiencing hanging notes again after it has been working fine for quite a while.

I am using the Multiport-Layer with Logic 9.1.8 on Mac OS 10.7.5 with the current version of VE-Pro 5 and Kontakt 5 (latest version).

The library producing the issues is LASS but with both VE-Pro and the Multiport Layer involved, maybe someone here has some ideas what to do about this?

i know about the issue with bouncing - I would just like to have some instruction on how to set up the IAC scenario in VE-Pro...

As long as that brings actually relief from the hanging notes I'd like to try this out.

It looks like I have it working - I duplicated the Multiport Layer File with anew name and imported it onto a new layer and then copied it from there into the mixer layer. Then I had to re-name each Multi-Instrument (VE 01 etc.) into something like VE2 01 etc. so I would not get confused when re-assigning the external MIDI tracks. This works so far without a crash.

But - I too have massive problems with hanging notes and I do not think that my system is on overload at this point.

I have worked with IAC on standalone PLAY instances before - but I don't know how that would work with VE-Pro? I also would like to have some more detailed information on this. I really need to get rid of the hanging notes as well.

How can I use the Multi-Port Layer on two instrument tracks? I would like to connect one of the tracks to an instance on the main computer and then another instrument track to an instance on a slave computer each utilizing multiple ports - or - split the multiple ports between them.

Can this be done and how?

When I select the items of the Multi-Port Layer, copy them and paste them again Logic crashes instantly!