Vienna Symphonic Library Forum
Forum Statistics

199,061 users have contributed to 43,151 threads and 258,882 posts.

In the past 24 hours, we have 3 new thread(s), 10 new post(s) and 62 new user(s).

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. VEP 5 - annoying "bug" (issue) connecting to slaves

  • VEP 5 - annoying "bug" (issue) connecting to slaves

    S
    S

    Hi.

    In VEP 4, if a slave machine was offline and a project contained instances of VEP that used this slave, it obviously would just skip connecting to those, but I could still work in that project and save new revisions of it. And when I then powered on the slave machine and re-opened the project, VEP 4 would be able to connect to those instances no problem.

    With V5 this seems to have changed. If I save my project (in Logic in this case) while a slave is not turned on, the next time I open the project when the slave IS on, VEP 5 will create all new instances, and the only thing I can do is to disconnect all those instances and reconnect them all manually again - pretty annoying. Is this something that you could look into?

    Thanks:)
  • civilization 3C
    civilization 3C

    I noticed that, if I connect to the slave server and forget to decouple it at once that reconnecting to that server instance in the DAW project results in the instance reloading with the version last saved with the DAW project, the behavior of a coupled project. this was not true in VEP 4. This is I think the same change as you speak of. I think it is a *feature not a bug* type of thing but I don't love it either. It isn't a big deal as it forces me to decouple at once. I'm not seeing the advantage of the feature though.
  • K
    K
    last edited
    last edited

    @civilization 3 said:

    I noticed that, if I connect to the slave server and forget to decouple it at once that reconnecting to that server instance in the DAW project results in the instance reloading with the version last saved with the DAW project, the behavior of a coupled project. this was not true in VEP 4. This is I think the same change as you speak of. I think it is a *feature not a bug* type of thing but I don't love it either. It isn't a big deal as it forces me to decouple at once. I'm not seeing the advantage of the feature though.

    This should be the same in VE Pro 4, but I think you have the "Incoming project data behavior" setting in the VE Pro Server preferences set to "Always load".
  • civilization 3C
    civilization 3C

    actually I have 'ask'. I could be wrong about 4, it could be I never reconnected to a coupled instance as I don't want to couple them.

    I'm not certain I didn't at some point click 'always load' and updating the software reset the prefs to default?
  • S
    S

    I always decouple all my instances, so that is not the issue here. The problem is that if I save a project with instances that couldn't connect to some instances, the next time I load that project (after now having turned on the slave PC), it won't correctly connect to that slave - it will create new instances all over (12 of them in my case - quite a bit going through disconnecting/connecting) instead.