Virtual instruments open with random settings

[jsbach]

Has anyone experienced an issue where you re-open a session and your virtual instruments have completely random settings or are even using completely different patches altogether?

Any thoughts on what could be causing something like this?

I unplugged all MIDI controllers / keyboards thinking this could be the issue, but no luck.

I tried trashing all preferences as well.

[Flyingrockstudios]

I have seen some VI’s like VPS Avenger where if I just make changes to a preset, but I don’t save the preset within Avenger, Pro Tools will just recall the original preset without the changes I made. I suppose Pro Tools doesn’t always save all the internal VI settings. I’ve also seen where the incorrect instrument assignment will be changed randomly on a VI track when I open the project.

[DonaldM]

I've had this happen with certain fx plugins, but not with VI's. Some of the Nomad Factory plugins sometimes revert to default when I reopen a saved session. But I don't recall having this issue with any VI's.

[jsbach]

Originally Posted by Flyingrockstudios

I have seen some VI’s like VPS Avenger where if I just make changes to a preset, but I don’t save the preset within Avenger, Pro Tools will just recall the original preset without the changes I made.

Yes, this is exactly what I was referring to. Did you ever find a solution?

It happens with many Arturia plugins. I was wondering if there is anything I can check on my end or if it's an issue on the developer end.

I though maybe it could be some type of permissions issue?

[musicman691]

Originally Posted by jsbach

Yes, this is exactly what I was referring to. Did you ever find a solution?

It happens with many Arturia plugins. I was wondering if there is anything I can check on my end or if it's an issue on the developer end.

I though maybe it could be some type of permissions issue?

Are you talking about Arturia's vi's or their fx? Daily user of their vi's and have never seen this. I rarely use their fx.

[jsbach]

Originally Posted by musicman691

Are you talking about Arturia's vi's or their fx? Daily user of their vi's and have never seen this. I rarely use their fx.

All of their VIs. I've seen several mentions of this issue with Pro Tools and Arturia going back years, but no solutions. Every time there is an update in Arturia Software Center, I hope for fix but not yet. That makes me thing there is something strange going on maybe permissions-wise specifically with certain setups.

[musicman691]

Originally Posted by jsbach

All of their VIs. I've seen several mentions of this issue with Pro Tools and Arturia going back years, but no solutions. Every time there is an update in Arturia Software Center, I hope for fix but not yet. That makes me thing there is something strange going on maybe permissions-wise specifically with certain setups.

Might be certain setups as I've never seen it across multiple versions of OSX going back to OSX 10.8.5 through OSX 10.13.6 except I never used El Crapitan. And every Arturia synth going to back to before there were VCollections. Are you running as admin? That's all I've ever run as. And are you allowing the installers to put things where it wants?

[Flyingrockstudios]

Originally Posted by jsbach

Yes, this is exactly what I was referring to. Did you ever find a solution?

It happens with many Arturia plugins. I was wondering if there is anything I can check on my end or if it's an issue on the developer end.

I though maybe it could be some type of permissions issue?

My solution is to save my changes to a new preset in the VI. Kind of a pain, but after you create and save as a new preset then you can just hit save when you make changes to the patch. Also beats trying to re-create your changes when re-opening the project!

[jsbach]

Originally Posted by musicman691

Might be certain setups as I've never seen it across multiple versions of OSX going back to OSX 10.8.5 through OSX 10.13.6 except I never used El Crapitan. And every Arturia synth going to back to before there were VCollections. Are you running as admin? That's all I've ever run as. And are you allowing the installers to put things where it wants?

Yes, I'm definitely running as an admin. I always install directly from Arturia Software Center. I never move or change anything that it's doing by default. I've also tried 'Clean Prefs' in ASC. I've uninstalled and reinstalled several times. It's just a complete mystery to me.

[jsbach]

Originally Posted by Flyingrockstudios

My solution is to save my changes to a new preset in the VI. Kind of a pain, but after you create and save as a new preset then you can just hit save when you make changes to the patch. Also beats trying to re-create your changes when re-opening the project!

That's exactly what I'm doing too. I also commit to audio just in case because sometimes the user presets don't even recall correctly.