OP-X Pro II is out !!!

[miamigroove]

Hi Everyone,

I should mention a few things:

1.) when I installed Pro II, I ran a "refresh plugins" cycle on the receptor (this is run from the Setup page, under a tools menu I believe). This detected Pro/Pro II as the same plugin, and asked which version to use. I didn't try to keep both versions installed at the same time, I simply run Pro II as the only version now - so this is what I specified during the "refresh plugins".

2.) regarding authorizations - if you install the OPX Pro II commercial version (eg PC) on your receptor, it will try to use the PCs authorization scheme (and not your iLok auth, from the Receptorized versions). This shouldn't be a problem, simply enter the Auth code you were given for PC installation into the Auth dialog (Blue box over the interface when you first instantiate OPX pro).

3.) Previous Banks/Presets - as mentioned above, the new version *IS* the same plugin as the old one. Once you get the new plugin going, it will use exactly the same receptorized Banks/Patches that were previously stored for OPX Pro. Any custom banks will still appear (and load fine in OPX Pro II). As always, practice some caution and 'back up' custom banks/patches to be safe.

Hope this helps. Regards,
Kevin L

hmmm....im wondering if this may be an iLok issue. I have Pro I (Receptorized version) authorized via my iLok. Perhaps I should try and obtain an iLok license for Pro II?

[Meo]

ok....after 9 long hours i give up.

Like someone else said, did you refresh the plugins? That's pretty standard when installing something new on receptor!

I installed it without any problems, I really like the new presets! The effects give the instrument so much depth, it's incredible!

A valuable update, Good job Peter!

Unfortunately, I dont see any way to refresh the plugins

How do I do this?

Setup tab:
Run utility>Refresh plugins

When it stops at OP-X, select OP-X Pro 2.

Not sure if all OS are the same thought.

[Rick@MuseResearch]

I think you may be refering to rebuilding the plugin cache:
http://www.plugorama.com/kb.php?id=327

Refresh Plugins:
This is run from the Receptor SETUP Plugin Utility. This is used to find dlls.

[Meo]

You're prolly right!

I usually refresh plugins when installing something. Mostly unsupported. Perhaps just rebuilding the plugin cache is sufficiant? Not sure anymore, I have doubts now.

I did run the .exe installer thought.

[Peter999]

Btw, just found an old post made by Ben (KVR/Muse Research) regarding plugin IDs:

Receptor requires every plug-in to have a Unique ID but some plug-ins use the same ID for different versions, such as an instrument and an effect version (e.g.B4 and B4 FX).

Editing the XML file overrides the id for that plug-in so Receptor can use both plug-ins at the same time.

So this would mean that you theoretically could use OP-X PRO and OP-X PRO-II in the same Receptor by editing the XML file of one of both

I'm however not sure if this would stop Receptor to assign the right patches to the plugin. Theoretically it still *should* be possible to load patches since the ID is in the dll and the patches themselves. But maybe it messes up the internal structure, and Receptor does not see the patches and banks anymore.

Maybe someone knows it better

[PhilMuller]

OP-X PRO-II installs just fine on my Receptor 2 Pro Max using the standard install method as Kevin has documented. Wow, what a great synth! I haven't stopped playing it for 2 hours now.

Well, I just stopped playing and I converted all the OP-X PRO-II patches to Receptor patches and gave them to Peter at Sonic Projects. What a job, whew! Peter will probably post them on the Sonic Projects website for you all. Have fun.

[Peter999]

Thanks a lot Phil for sharing those!

The converted banks can be downloaded both on the Receptor support page and the sound reloads page with a brief installation guide:

Receptor support page (scroll down):
http://www.sonicprojects.ch/opxpro2/musereceptor.html

Sound reloads page:
http://www.sonicprojects.ch/opxpro2/userarea.html


It's a great download too for guys who generally want to have all sounds available as single patches

---

[looneytunes]

Btw, just found an old post made by Ben (KVR/Muse Research) regarding plugin IDs:

Receptor requires every plug-in to have a Unique ID but some plug-ins use the same ID for different versions, such as an instrument and an effect version (e.g.B4 and B4 FX).

Editing the XML file overrides the id for that plug-in so Receptor can use both plug-ins at the same time.

So this would mean that you theoretically could use OP-X PRO and OP-X PRO-II in the same Receptor by editing the XML file of one of both

I'm however not sure if this would stop Receptor to assign the right patches to the plugin. Theoretically it still *should* be possible to load patches since the ID is in the dll and the patches themselves. But maybe it messes up the internal structure, and Receptor does not see the patches and banks anymore.

Maybe someone knows it better

Hi Everyone,

I got to play around with this - here's what I observed:

You can change ID's on 2 different versions of the same plug (to install both plugins from the instruments menu). The moment you do this, Receptor treats the two plugins as 'different plugins' (not 2 versions of the same plugin). The issue is that if you have some .fxp or .fxb files that you wish to receptorize (eg change into receptor single presets or banks), you will only be able to associate these patch files with the the version whose ID you did not change.

Keep in mind, this doesn't mean you can't load them into either version. If the plug (like OPX-Pro) has .fxp/.fxb loading facilities, you can load them into the plug (avoiding Receptor's patch mechanism). Then you can iterate through each patch from the plug interface, and save each patch as a receptorized single. (With many 'unsupported installs' you need to do this anyway.)

A consideration:

Receptor's load mechanism often identifies and prevents plugs for which there are iLok protection. In this case, if you are trying to install a normal PC protected version of the same plug, Receptor may prevent you from loading this (unless you do change the ID). This is pretty hairy stuff, and you may only be able to get around this by other means (not the general unsupported install).

My general recommendation is *not* to try to change the IDs (in the .xml files). Specifically for OPX-Pro II on receptor, I think there is no need to do this - Pro-II loads the legacy files and receptorized patches just fine.

Hope this helps. Regards,
Kevin L

[Peter999]

Thanks Kevin - yes, that what I've supposed

Btw, has anyone already tried OP-X PRO-II on a Receptor 2 standard (the one with amd dual core)?

Is there a big performance difference between Receptor 2 Standard (AMD Athlon II SE 240E dual core 2,8 gHz) and the Receptor 2 Pro (Intel Core2duo E7200 2,53 gHz)?