So this has just happened again.  What I can report is that in some Logic files, decouple stops working

properly.  As I understand it, with decouple selected the VE Pro AU should not cause any loads to occur in the 

server.  Mostly, this works.  Sometimes however a Logic file will do what I describe:  it opens parallel default instances with 

an empty Vienna Instrument loaded in each case, and connects to them.  The only cure is to deselect the VE Pro AUs in Logic,

delete the dummy instances in the server, then reselect and reconnect the AUs.  A real PITA.

If it's me, please enlighten me!

Logic 9.01, 2008 8-core, OSX 10.6, 16 gig RAM.

Thanks Karel.

I open the 32 bit server.  I load a meta I have created with 8 instances of VE Pro, each hosting one instance of kontakt 3.5.

Each kontakt is loaded with 16 patches.

I open a pre-existing Logic file I have worked on already and previously saved.  The file has (among other things) 8 VE Pro multi AUs, each connected to its corresponding instance in the server, and all of them 'decoupled'. I am using the AU midi, as the IAC bus implementation does not seem to work well.

All is usually fine, but on occasion I find that the AUs cause 8 more 'dummy' instances to be created in the server:  so I see in the server window my 8 labeled instances, plus 8 new ones each hosting an empty Vienna Instrument.  Unfortunately, the AUs all connect to the new 'dummy' instances.Then I can't delete the unwanted instances because they are 'connected'.  I get that message even when I disconnect the AUs in Logic.   If I force quit the server, or exit (overriding the warning that it may cause Logic to crash...which it doesn't), then I am unable to re-open the server without getting the dreaded server is busy message, and I have to reboot.  The only cure is to deselect all the VE Pro AUs in Logic (at which point I CAN delete the unwanted instances in the server) and then reopen them.  

This could definately be user error.  Please let me know if I have misunderstood something.

Thanks!

Hi Karel,

they are created as new instances, no name.

So far hasn't happened today.

It certainly could be user error but I don't think so and it's happened enough times to frustrate me and

motivate the post!

Ok, just happened again.  What I think might be happening;  this problem (maybe) only occurs after Logic crashes.

When I reopen the file I was working on, I get AUs creating and connecting to dummy instances.  This in spite of the 

fact that all AUs are set to decouple.  As I understand it, when set to decouple, nothing should load in the server.

So maybe this is a bug that happens after Logic has crashed.

And contrary to what I reported above (sorry..it's all been a bit of a blur)...when I deselect the AUs, delete all the dummies,

and reselect the AUs, when I try to reconnect the AUs nothing is seen in the server.  Real bummer.

I now see exactly what is happening and apologize for my lack of clarity in earlier posts.

When Logic crashes all the instances in the server remain in a 'connected' state.

This causes a few problems:

1. Those instances can't be deleted from the server (because they are 'connected' even though in reality they

aren't connected to anything).  And when you exit or force quit the server, it can't be re-opened

without re-starting the computer ('can't find the server port...or whatever the error message says).

2.  When you re-open Logic after it crashes (but without restarting the comp), because all the instances in the server are "connected" already, the VE PRO AUs cause new instances to be created each hosting an empty Vienna Instrument.

So therefore when Logic crashes, one must restart the computer every time.

This is a huge time-waster.  It would be great if VE Pro would disconnect somehow when Logic crashes.

Thanks.

@rob morsberger said:

I now see exactly what is happening and apologize for my lack of clarity in earlier posts.

When Logic crashes all the instances in the server remain in a 'connected' state.

This causes a few problems:

1. Those instances can't be deleted from the server (because they are 'connected' even though in reality they

aren't connected to anything).  And when you exit or force quit the server, it can't be re-opened

without re-starting the computer ('can't find the server port...or whatever the error message says).

2.  When you re-open Logic after it crashes (but without restarting the comp), because all the instances in the server are "connected" already, the VE PRO AUs cause new instances to be created each hosting an empty Vienna Instrument.

So therefore when Logic crashes, one must restart the computer every time.

This is a huge time-waster.  It would be great if VE Pro would disconnect somehow when Logic crashes.

Thanks.

i think that your request has been noted for future releases already. However, what happens if you decouple VE Pro and then crash Logic? I'm not suggesting that this is a normal way to work, but it might mean that you could work with VE Pro decoupled and then just re-couple it before you shut down. Just a temporary workaround, assuming it works, of course.

DG

I've had this happen a few times to me in Protools. To answer DG's question - I run VE decoupled most of the time because of the save times, but I've still ended up with the problem on several occasions. The decoupling doesn't disconnect VE, so if you crash your DAW, VE slaves can still think they are connected. 

There have been other posts about this, the solution would be to have the ability to disconnect on the slave end as well. 

Re: the extra instances and the Logic Crash: I think I have a similar thing happening with DP (actually have a thread asking for the procedure to use when experiencing a DP crash)....thanks for your post it's useful to see you've discovered a pattern or some type of explanation.

To avoid a restart (after your sequencer crashed) you can also "force quit" VE Pro in activity monitor.

/Regards,

Rob I've been following your travails in another thread and I feel your pain.

Regarding this one, one helpful thing I found was that VE PRO seems to remain in a connected state

until a new sequencer file is open.  So that after a crash, if I opened an empty logic file with no VE Pros I could watch

all the instances in the server disconnect, then open the file I was working on safely.

That said, there were still anomalous occurances of this problem that didn't seem to conform to anything I thought I had

grasped about it.  

And force quitting never helped for me;  VE Pro would always give me a 'cant find a server port' or whatever...message. 

I had to restart every  time.