Cubase doesn't recall VE Pro instances!! Please help!

[keyman_sam]

My primary's OS drive crashed and I've installed everything from scratch in a new drive. Needless to say I'm going through a lot of headaches trying to get back to where I was. Now I'm trying to open the project I last worked on.

One of the unwanted surprises was, my Cubase project opens up but doesn't recall ANY of the VE Pro patches. It doesn't even connect to VE Pro. It just opens the plugin in disconnected state. 

My slave is unaffected by my primary so technically I expected everything to work as usual (even though I have other unresolved plugins in that project). Please help!! 

[Paul]

Hello, 

Does that problem happen with all your Cubase projects? Did you try with a backup project?

Did you save your VE PRO instances or metaframes on the slave computer?

If a song is corrupted, this might also affect the saved VE PRO data. Are you using the same IP addresses that you used before the crash?

Did you try to click "Connect" in the VE PRO Server Interface plug-in and connect to VE PRO? This should send all stored VE PRO data to the newly opened instance. 

Best, 
Paul

[keyman_sam]

@Paul said:

Hello, 

Does that problem happen with all your Cubase projects? Did you try with a backup project?

Did you save your VE PRO instances or metaframes on the slave computer?

If a song is corrupted, this might also affect the saved VE PRO data. Are you using the same IP addresses that you used before the crash?

Did you try to click "Connect" in the VE PRO Server Interface plug-in and connect to VE PRO? This should send all stored VE PRO data to the newly opened instance. 

Best, 
Paul

 

Thanks for the suggestions. Thankfully I had saved the song locally (and totally forgotten about it) so it ended up loading fine!

No, the IP addresses are different. I haven't tried your last suggestion but I'll try it and get back. It would be great to know that there's a reliable backup option to load the data from the sequencer. However I still see duplicate connections to the slave after I installed the 2nd NIC on my primary. It would be nice to block that 2nd connection so that it doesn't clutter my connection options.

[Paul]

Hi again, 

The only safety routine to prevent corrupted projects is to keep backups of everything: 

- Your DAW Song
- your VE PRO projects (*.viframe)
- VE PRO metaframes (*.mframe)

VE PRO connects based on 2 parameters: 

- instance name ("preserved name"). 
- IP address.

Please send a screenshots that shows what you mean by "duplicate connections" to support@vsl.co.at, and please include the network settings of all components (also best with screenshots). 

Best, 
Paul

[keyman_sam]

@Paul said:

Hi again, 

The only safety routine to prevent corrupted projects is to keep backups of everything: 

- Your DAW Song
- your VE PRO projects (*.viframe)
- VE PRO metaframes (*.mframe)

VE PRO connects based on 2 parameters: 

- instance name ("preserved name"). 
- IP address.

Please send a screenshots that shows what you mean by "duplicate connections" to support@vsl.co.at, and please include the network settings of all components (also best with screenshots). 

Best, 
Paul

 

Thanks for the prompt response -  I was able to verify in one of my projects that indeed, when you connect manually it recalls the instances. So glad to have this facility. When I have some free time I'll follow up on the duplicate connections.