OP-X Pro II now available for Mac and 64-bit PCs

[chk071]

The 64-bit version of Synthedit only outputs 64-bit VST3's, so it's got to be something else he used.

[braj]

On Windows if you hover over the .dll it gives some info on the compiler. I am away from the computer so someone else can check please.

[bluzkat]

You have to use a 64 bit host to use the 64 bit version.

Not necessarily, Reaper will bridge 64 bit plugins if you use Reaper 32 bit.

I'm not sure about other hosts or jbridge.

just sayin'...

[4damind]

He used a modified version of the VST3 example "ADelay" from the Steinberg VST3 SDK. Afaik this supports some kind of wrapper to be loaded as VST2. Maybe it's a workaround to run Synthedit 64Bit also as a VST2 64Bit plugin.

I had a hope he programmed this synth new from scratch without the needs of Synthedit. I remember also the very simple listview for presets and a missing preset browser and some other not very well designed stuff on the GUI.. If I see the pics on his website nothing has changed, it's the same synth only now using Synthedit 64Bit and a VST2 wrapper (on Windows, not idea about MacOS).

[Examigan]

You have to use a 64 bit host to use the 64 bit version.

Not necessarily, Reaper will bridge 64 bit plugins if you use Reaper 32 bit.

I'm not sure about other hosts or jbridge.

just sayin'...

Ok, but I'm not sure why you would even want to as there is a 32-bit version anyway.

[chk071]

Why is there even a 64-bit bridge? Seems pretty pointless to me...

[braj]

Here is from the installer download page:

What has changed in version 1.2?
Although OP-X PRO-II has an immensely complex engine we were able to port every single feature and function to 64bit, VST3 and AU, including effects, arpeggiator, relative and fetched controller processing, pedal hold and all other specialities of OP-X PRO-II. And probably most important for you, too the whole plentora of existing sounds (more than 2'500 so far!). During re-writing we also streamlined parts of the code, so the engine itself should be even more solid now than before. The patch manager had to be re-written from scratch (see infos below), so this one still may not be 100% mature at this time. Upon re-writing we however too in this one improved the one or other thing because it was possible to do at all using our own format, see below. Because we built OP-X PRO-II around the new VST3 SDK and because it uses a new preset format a few minor things have changed, which are:
1. For cross-platform and cross-plugin-format compatibility we needed to create a completely new self-contained and host-independent patch system using its own preset format (.opxpreset and .opxbank). That's why the synth can't load the former fxp/fxb format presets and banks. We however provide dedicated transfer-plugins (see above) which allow to transfer your own custom fxp/fxb presets and banks forth and back. The advantage of this new patch system is that it's completely host and platform independent, so you can use the same presets everywhere (mac/pc/au/vst2/vst3). Note we have converted ALL available banks (including all reloads from the download page) to the new format already, all of them already included in the "Presetbase" included in the installers (66 banks or about 2'500 sounds in total!), so you only need to transfer your own custom presets and banks. Apart from the new format and a new library location (*check pathes below) the patch system works exactly the same as before, except for:
2. When you edit a preset within a bank the edited state won't remain anymore after switching presets, except you click on the COPY button which will freeze it. So the COPY button has this new function now.
3. Since the synth is built around the VST3 SDK midi program changes don't work anymore since VST3 doesn't offer it. To compensate this we however implemented 4 ways to switch programs by Controllers. For details check page 85 ff in the new pdf manual.
4. ALL controls except for the small grey env / port trimpots can be learned now, including filter trimpots and effects section. There's no default mapping anymore. Single controls can be unlearned now. For details check page 83 ff in the new pdf manual.
5. CPU load: The maximum cpu load of one instance (maximum 12 voice polyphony, full playing) is a bit smaller than in version 1.1 32bit, but the idle cpu load is a bit higher (plugin loaded doing nothing), so not almost completely zero as in 1.1 32bit. So dependent on the type of usage (many instances loaded, but only a few engaged at the same time) the total cpu load can be higher using multiple instances. But it's still low enough to use many instances even using weak cpus.
6. Since the preset library and other needed files now reside in an unprotected place you don't need to deal with administrator rights anymore in windows. Furthermore the plugin now should start working immediatly after licensing without the need of being reloaded.
*The new preset library locations are:
PC:
C:\Users\Public\Documents\SonicProjects\OP-X PRO-II\Presetbase
Mac:
Finder->Go->Computer->Macintosh HD:
Users/Shared/SonicProjects/OP-X PRO-II/Presetbase
This library is common for all formats (VST2/VST3/AU)used on the same machine. So in windows banks saved with the VST2 x64 version can be opened with the VST3 x64 version and vice versa, and in Mac banks saved with the VST3 version can be opened with the AU version and vice versa. Finally you also can neatlessly exchange banks and presets between Mac and PC.
The version 1.1 VST2 32bit version for the moment will remain at the 1.1 engine using fxp and fxb since it has been stable and rock solid for years now and it has a near zero idle cpu load which can't be realized to this extent in the 1.2 engine. That's why we don't wanna change anything here for now. Furthermore this one offers direct midi program changes (only possible via controllers in 1.2) which may be needed by some, especially using it in a live environment. We may release a 32bit version 1.2 engine version later as alternative.

[Examigan]

Why is there even a 64-bit bridge? Seems pretty pointless to me...

Yeah... I mean I knew of 32-bit bridging of course, as I use that myself for some older plugins here and there. I guess a 64-bit bridge would be good on the rare occasion, for instance I think Sampletank 3 is 64-bit only, not 100% sure though.

[braj]

Why is there even a 64-bit bridge? Seems pretty pointless to me...

I think it is so you can run 64 bit memory-intensive plugins outside the constraints of a 32 bit host. Say you have a lot of 32 bit native plugs that you don't want to use a wrapper for, you could run, say, Omnisphere outside the memory limits of the 32 bit host without having to wrap as many plugins. Since wrappers add an extra layer of potential issues, you avoid having too many of these extra variables. I think that is why anyhow.

[braj]

He used a modified version of the VST3 example "ADelay" from the Steinberg VST3 SDK. Afaik this supports some kind of wrapper to be loaded as VST2. Maybe it's a workaround to run Synthedit 64Bit also as a VST2 64Bit plugin.

I had a hope he programmed this synth new from scratch without the needs of Synthedit. I remember also the very simple listview for presets and a missing preset browser and some other not very well designed stuff on the GUI.. If I see the pics on his website nothing has changed, it's the same synth only now using Synthedit 64Bit and a VST2 wrapper (on Windows, not idea about MacOS).

It does use a .sem file so you may just be right. I'd love a total rewrite, but this does nicely, the only real issue I had with the synth was lack of a 64 bit version, this is here and it works well for me.

[braj]

Making it a free upgrade was a wise move I think reducing the normal price for the 2015 market would be wise as well.

[Examigan]

Making it a free upgrade was a wise move I think reducing the normal price for the 2015 market would be wise as well.

Yes I agree about the upgrade.

It could be a little less expensive, but he does have sales now and then. Actually right now it is on sale for around $95, so it's not a bad price really.

[BushidoBroWWN]

Well this is a nice surprise. I was in the process of trying to recreate my op-x presets in diva with varying success because I was fed up with all the workarounds you had to do in order to get it working on Mac but now I don't have to do that.

[wagtunes]

Just downloaded the upgrade. Sounds great. Seems more stable.

Happy camper.

[mholloway]

Ugh, the audio dropout on the Demo is WAY TOO FREQUENT. Do they want us to be convinced to buy the thing, or just deeply irritated with the whole experience of testing it???


-M