Tech support request from Sonic Projects
I recently upgraded to the 64 bit OP-X Pro-II from the 32 bit version wrapped in JBridge and noticed a few inconsistencies.
First issue, there seems to be some instability in the Octave settings. When I program a “Scene” just like the 32 bit version (relating to the same Octave) everything sounds the same. But upon “Update Scene” and “Save Rack”, and then closing Forte and then reloading the same scene, often times the scene plays an “Octave Lower” than what was originally programmed. I am running multiple instances of OP-X Pro-II
Second issue. When I select a Bank and then Particular Patch, and “Update Scene” and “Save Rack”, then close out Forte and restart Forte, the Bank and Patch is only Partially remembered…… Let me explain.
If I select “Camera Eye”, patch number #4 on the “Famous” Bank, and select “Update Scene” and “Save Rack”. And then go between scenes all is good. But when I close out Forte and Restart Forte. The “Camera Eye” patch is present, but it shows as “Patch #1” in what appear to be the Default Bank, Where “Camera Eye” replaces whatever is the #1 Patch in the Default Bank. This happens every time with any patch that is selected, where upon restart the selected patch is now #1 of the Default Bank. Not sure if this is a problem or not, just seems weird.
Sonic Projects Reply
Thanks for your report.
The octave issue may be something with the actave radio buttons not saving/recalling correctly. We're going to examinate it (we have Forte in Win 8.1). It may help when you tweak the octave switch once up and down again with the mouse before you save the session.
Regarding the second: This in fact is no issue, it's conceived to work like this. Unlike the "old" 32bit version the new x64 (and Mac) version uses a new "own" patch and bank format which is independent from the host. The base engine (which is VST3, also in the VST2 version) by itself doesn't support banks at all, so the former banks only could be kept by implementing them in a custom format which only can be managed by the patch manager of OP-X PRO-II. The plugin itself only connects to the host through the active preset slot. So upon recalling a session you will have the saved patch in the top slot replacing the first preset of the default bank. You can't save and recall whole banks with the host anymore. This formerly only was possible since banks were fxb-chunks. In the former 32bit version the plugin was using the same format as the host, and the patch browser actually only was "talking" to the host for patch manipulation. Now it manages it all by itself internally, while only connecting to the host through the active slot for total recall.
This in fact is the way all plugins using an own patch format handle it. The 32bit OP-X PRO-II in fact was sort of a in-between solution, so offering own controls to load/save/change banks and presets, but actually using the host's format.
I hope I was able to explain it somewhat understandable