"version mismatch" on loading an updated plugin

[iaoranaemaeva]

Hi,

Each time I replace a VST, say, Pianoteq.dll, with a new build (same file name), loading any session that uses it ends with an error message:
VST Plugin- Pianoteq - Failed to load preset - version mismatch

So, I need to reselect Pianoteq in the plugin list for each call to this plugin, which is very tedious since I have dozens of racks that use it and Pianoteq updatings are frequent!

Is there a way to force Cantabile Solo to automatically accept a new build (or version) of already used plugins (maybe with a warning message)?

Sorry if this question was already answered

[TiUser]

I think this is more a pianoteq issue when each new version tags it's vst presets with a new version number... and can't read it's older preset versions.

I understand the hassle you have but actually see no simpler solution than what you already did... reloading the vst with appropriate patches with new version numbers.

[iaoranaemaeva]

Thanks TiUser. I of course submitted the problem in Pianoteq forum too: I got some responses, including from one of the developpers - they are investigating the problem...

[TiUser]

Well, that's one thing I hate about modular software systems - the endless shifting of problems from one instance to another.

I really hope Pianoteq will address the issue asap.

But to be honest I am not really happy that Brad has vanished from here for over 2 month now too... just hinting he's working on a Cantabile VST.

[iaoranaemaeva]

CantabileSolo20.exe is flanked by a Compatibility.ini file that could be edited in order to solve the problem, I believe:

; This file can be used to specify behaviour of specific plugins
;
; PluginXXXXXXXX=<value>
;
; Where XXXXXXXX = the plugin's uniqueId in hex. If not known, this value can be
; found in VstCache.ini in the application data folder (..)
; Valid values:
; (..)
; 16 = Don't check the version number contained in fxb/fxp files

Now, I have to find Pianoteq uniqueId...

[iaoranaemaeva]

Now, I have to find Pianoteq uniqueId...

Thanks to Plugin Consultant, I found that Pianoteq 3 uniqueId is ASCII "Ptq3". So, I added this line to Compatibility.ini:

Plugin50743371=16 ; Pianoteq3 - don't check fxb/p version number

Now I can update Pianoteq 3 without having to correct rack data in Cantabile 2 Solo

[TiUser]

...as long as there is no real compatibility issue with earlier patches...

[iaoranaemaeva]

...as long as there is no real compatibility issue with earlier patches...

Of course, but in this case, Cantabile will select the default patch (#1), I presume...

[TiUser]

That's a good question... probably Brad can answer this detail.

I thought selecting just means "indexing" any entry in a plugins loaded bank - except the shared patches - displayed in brackets like this: [shared].

Of course this implies the question how banks are handled during session load.