I think there is a small bug in the handling of preserved instances. Here is how to reproduce the behaviour:
- create a preserved instance in VE Pro (I'm using 64 bit on PC/Vista)
- create an instance in the sequencer (Cubase 32 bit in my case), connect it to the preserved instance
- now setup the instance with the desired instruments etc.
- save the project in the sequencer, close it
- delete the preserved instance and/or exit the server (or reboot the server, let's say next day)
- now start the server, but "forget" to create the preserved instance
- load the sequencer project. The preserved instance will automatically be created and loaded
Now the preserved instance is in a weird state. It is shown as preserved, but this is not completely true. If you close the sequencer project, then the instance will stay - as expected. However, loading another (or the same) project will automatically discard any changes made to the instance and reload it from the sequencer project, which I wouldn't expect for a preserved one.
So it looks to me as if the internal state of such an instance is inconsistent. I can solve this by explicitly unpreserving and preserving the instance once.
Unfortunately it is not very unlikely that this happens. It actually happens each day when opening a project for the first time, without creating all preserved instances manually first.
Is this an expected behaviour (feature), or is it a bug?
PS: Vista 64 PC, local connection (no separate server), 64 bit VE pro, 32 bit Cubase 5.1