Vienna Symphonic Library Forum
Forum Statistics

195,429 users have contributed to 42,986 threads and 258,252 posts.

In the past 24 hours, we have 5 new thread(s), 29 new post(s) and 47 new user(s).

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. Cannot reconnect to VE Pro 6 after Logic Crash

  • Cannot reconnect to VE Pro 6 after Logic Crash

    C
    C

    After Logic crashes, I reboot that same Logic session but those instances in that Logic session will not reconnect to VE Pro. Each instance says 'Instance Busy'. 

    Is this normal behavior? I have to restart the VE Pro server each time. 

    I am using Logic Pro 10.2.2 in Mac OS 10.9.5 and VE Pro 6.0.15864 on the same machine (Mac Pro).

    I would greatly appreciate any suggestions.

    Thx

    Felix
  • PaulP
    VSL Team
    PaulP

    Hi Felix, 

    If the network socket is not informed that there is no connection anymore, it counts as busy (so VE PRO was not informed that Logic crashed). 

    I know we have been trying to find a way around this, but it seems to be quite tricky. 

    Best,
    Paul

    Paul Kopf Product Manager VSL
  • C
    C

    Thanks for your reply Paul.

    Unfortunately, this makes VE Pro unusable for me at the moment. Is this something you will be able to fix in the future? 

    Does anyone else have this problem in VE Pro 6? or in VE Pro 5?

    Thx

    Felix
  • PaulP
    VSL Team
    PaulP

    Hi Felix, 

    Sorry to hear that. 

    How often does Logic crash, and why? 

    I hope that it can be fixed, but so far, we have not been successful. 

    Best,
    Paul

    Paul Kopf Product Manager VSL
  • S
    S

    I have the same issue.

     

    Funny thing is, with VEP 5 it used to work - I could do a "force disconnect" on VEP, reload Logic and continue working.

     

    Since VEP6 this has been impossible, since "force disconnect" doesn't make Logic able to reconnect to the instances again.

     

    Or maybe it's a Logic X issue. However, it was the same in Logic 9, that VEP didn't "see" that the crash had happened, so I had to force disconnect in VEP, so it points to VEP somehow.
  • C
    C
    last edited
    last edited

    @Simon Ravn said:

    I have the same issue.

    Funny thing is, with VEP 5 it used to work - I could do a "force disconnect" on VEP, reload Logic and continue working.

     Since VEP6 this has been impossible, since "force disconnect" doesn't make Logic able to reconnect to the instances again.

     Or maybe it's a Logic X issue. However, it was the same in Logic 9, that VEP didn't "see" that the crash had happened, so I had to force disconnect in VEP, so it points to VEP somehow.

    Thank you Simon for letting me know. That is really helpful! I may well revert to VE Pro 5 for the time being.

    I am testing without VE Pro running to see if that could be what is causing the crash. 

    Best regards

    Felix
  • C
    C
    last edited
    last edited

    I was just wondering if this issue has been resolved yet? 

    @Paul said:

    Hi Felix, 

    If the network socket is not informed that there is no connection anymore, it counts as busy (so VE PRO was not informed that Logic crashed). 

    I know we have been trying to find a way around this, but it seems to be quite tricky. 

    Best,
    Paul
  • PaulP
    VSL Team
    PaulP

    Hi, 

    I'm afraid all development power has been focused on our new products, so this is not resolved yet. 

    I know that there will be a VE PRO Sprint after the release of Synchron Player, and hope that this bug can be fixed then. 

    Best, 
    Paul

    Paul Kopf Product Manager VSL