Thanks for pointing that out @Torsten, it slipped by me and I thought my automation trick fixed it, but after trying out your explanation, it did indeed remember the preset and call it back up. Way less bloat this way and the original patches are preserved for recall at any time if you want to reset them!
Dave
Hi Torsten (AKA da man)
Iāve been trying to solve this for some time and was trying to get @dave_dore 's solution to work, but saw your solution, and it worked perfectly! I am now using my presets as states. Many thanks! Also many thanks to @dave_dore for the hard work in trying to solve this.
Regards
Corky
Yes, that works for me too @Torsten - thank-you for the clarification of what itās doing. As long as you totally ignore OP-Xās own bank/patch system, it works beautifully!
Itās interesting that this works - I didnāt realise Cantabile stored the pluginās current āedit bufferā, unless you enabled state behaviour on all the exported parameters.
Neil
These CantabileFxb files I made a while back might be useful
Just load the plugin, call up the gui and import the banks, the Catabile preset dropdowns sync with the OP-X original names.
Dave
You know, I think thereās still something wrong with the way OP-X Pro-II is working in Cantabile.
I followed @Torstenās steps above, and sure enough, the selected patches seem to get stored as Cantabile presets, so I can switch between them using the drop-down. But if I keep switching between these Cantabile presets (not touching the OP-X Pro-II GUI at all), eventually I find one of the Cantabile presets has been copied over one of the others, overwriting it, so instead of having patches A B C D, I now have something like A B C A. I seem to be able to provoke it by switching between Cantabile presets fairly quickly, although that might be a red herring.
Iād be really interested to hear from @brad on how this mechanism is working, and why it might be doing this. I still donāt trust OP-X Pro-II, unfortunately 
Neil
Oddly, tonight I was experiencing some strange effects selecting among Cantabile presets in NIās Replika XT delay. I wonder if something has broken during an update? (On 3267.) When Iād select a patch, the name wouldnāt change, but the sound would. When Iād select another, the name would change to the name of the one selected previously. Didnāt open it up to see if anything was being overwritten in the presets list.
Terry
Incidentally after working with the new method a bit I stored a Cantabile Bank file and found it has a different extension. Instead of .cantabileFxb itās now .CantabileBank ā¦ it may have been that way for a while, I donāt know when it changed for what itās worth.
Dave
I just went all the way back to build 3247 and found that both NIās Replika and Replika XT do that wonky thing with the Preset forward and backward buttons, selecting odd names for the patches even though it does perform the patch change. It seems only the names and numbers in the Presets window are messed up, but once they are messed up they stay messed up!
I wonder how one would reset those so it reads the patches in again straightening out the names and numbers?
I checked out build 3256 where the forward-backward buttons had been reported as being fixed, but the behavior persisted with these two NI plugins. Have not tested with other NI plugins as of yet.
Terry
I should know this, but how do I download the upgrade and enter my registration key so that the new software doesnāt stay in demo mode?
I canāt think of anything off hand that might changed to affect this so Iāll need to investigate but my gut feel is this is behaviour of the plugins (otherwise all plugins would behave weirdly).
@terrybritton - are you saying that Replikaās presets got messed up by a newer version of Cantabile and that it works fine in a fresh instance of Replika in an old version of Cantabile?
This format was introduced with the morph/randomize tools. It stores parameters + all morph/randomize settings and CantabileBank replaces CantabileFxb format (though both are still supported).
You should be able to just install the latest build and if your currently activated license doesnāt cover the build itāll prompt your to select the new one. Email me if any problems.
Iāve been doing some testing here with latest OPX Pro II 1.2.5 and it seems to be working albeit still with OPXās unusual preset management system - which I think explains the odd behaviour that @Neil_Durant is seeing.
Iāve been trying to figure out exactly what OPX does when it saves/loads to the host (or to/from fxb file which is exactly the same thing) but ended up so confused I gave up. It seems to always save and load the current preset name and the synth parameters, but it doesnāt save the selected internal bank index, it doesnāt save which bank you had loaded and on loading sometimes it updates the bank with the preset name and sometimes it doesnāt.
Combined with Cantabileās pseudo presets things get very out of hand very quicklyā¦
For the next build (3270+) Iām going to disable pseudo presets on new instances of this plugin.
That way at least it will behave the same as it does in other hosts. Although the same problem is still there, at least Cantabileās pseudo presets wonāt be making things even more confusing.
Brad
Bearing this new decision in mind, could you aid me in the removal of any shared files on the server I uploaded that use this current method? I donāt want to share anything funky. There were CantabileFxb Files.
Thanks,
Dave
Hey Daveā¦ they should still work I think. 3270 is up now - give it a test and let me know if any problems.
What should happen is you load a new instance of OPX, itāll be in non-pseudo preset mode. If you load something with pseudo presets (including those bank files you uploaded) it should switch to pseudo preset mode.
Ok, Thanks Brad
Dave
No, I tried older versions to see if it was a recent issue that came up (back to 3245) but the problem happened even back then and still does, apparently. This with both Replika and Replika XT. Is there a way to reset the auto-populated pseudo-preset patch names? The plugins own browser shows them correctly - they are simply ārenamingā themselves spontaneously in the pseudo-presets window, it would seem!
Doesnāt happen with LinPlugās Spectral synth, which Iāve recently been playing with a lot and would have noticed.
Terry
EDIT - Hmmm - I admit I did not try a fresh instance, exactly, but had my backed up racks from before the big update that I used when I tested 3245, and that version of the āReverbsā rack had Replika in it, not Replika XT. So, the two racks were made at different times with different versions of Cantabile.
Hey Brad,
I tried out the new build with OP-X 2.5 and the results are that it doesnāt recognize the old file extension of the Bank files I saved from before. The extension was ( .cantibileFxb ) so I canāt check the old versions. I had loaded the Factory presets bank (old version) a few days ago and then re-saved it after a small edit, it then had the new extension with the extension ( .CantabileBank ). This file loads and works correctly. The other problem I have with the new version is that it crashes on song changes in the set list. I have sent along the automatic crash report, it was repeatable.
Dave
I tried out OP-X Pro-II in build 3270, and had a few problems:
In fact the only way Iāve found to get it to work reliably is @dave_doreās method of enabling state behaviour on all of the pluginās parameters, and disabling Selected Program and Entire Bank state behaviour. That seems robust and doesnāt suffer from the problem above. Luckily, that method also provides the smoothest patch changes, as itās just doing a lot of quick knob twiddling, rather than cutting the sound and reloading a load of new parameter data.
So Iād recommend to anyone using OP-X Pro-II, to give it a good hammering on your setup to see if itās going to cause you problems like Iāve had, and if so, maybe switch to @dave_doreās automated parameter method.
Neil
OK, Iāve tried my luck with the new build - as I understand now with disabled pseudo states, there is no way to select OP-X presets from the menu directly in the routing view - which is a pityā¦
Instead of using āentire bankā, I tried using the built-in OPX bank system and program changes (or OP-Xā version of program changes), but that wonāt work, since OP-X doesnāt remember the loaded bank when saving the song - a major annoyance! Plus, it always overwrites the first patch in the loaded default bank with the edit buffer selected when saving, so even more nonsenseā¦
So I guess, Iāll give @dave_doreās method a try.
Thanx all!
Cheers,
Torsten
Hey Torsten,
I donāt know if this would prove handy but as stated in a post above I have a Factory Preset Cantibile Bank file that you can import and loading it will over ride the new limits Brad placed on the plugin with regards to the pseudo presets . It will revert the OP-X to the previous behavior and allow use of the Cantabile pseudo preset system but only if a file like this is loaded first. You could then export your edits made to this Bank in you own new Bank file.
Here it is, I had to zip it because the server doesnāt see the new extension.
SonicProjects OP-X Pro II Factory Presets.zip (344.5 KB)
Best
Dave
