T3 Wusikstation Presets Now Pre-Receptorized

[Kermit Jagger]

Final remark on this.

The reason why it is great you can use BNK (full banks) is that if you open a bank of 96 presets in Wusik, your host can save the FXB version of that BNK. That means easy conversion to the midified Receptor format, and direct selection via MSB/LSB of the preset you want to use in your music.

It's a shame William discarded the BNK format to only keep presets.

[TotcProductions]

Final remark on this.

The reason why it is great you can use BNK (full banks) is that if you open a bank of 96 presets in Wusik, your host can save the FXB version of that BNK. That means easy conversion to the midified Receptor format, and direct selection via MSB/LSB of the preset you want to use in your music.

It's a shame William discarded the BNK format to only keep presets.

Yeah, this is true. Maybe he'll re-institute the bank format...Wusikstation has a hell of a future ahead of it...so who knows.

peace

[bernie9]

So if I install Wusik 1, even with the Malory generator, there might be a conflict if Wucik 3 in on the Receptor ?

I had better ask William for advice, also, it's getting way above me.

I appreciate you people helping me figure this out.
Bernie

[Hybernation]

So if I install Wusik 1, even with the Malory generator, there might be a conflict if Wucik 3 in on the Receptor ?

Indeed it will. I did this last night and today. You cannot have both, and if you have W3 now, it messes up when you un-install it and install W1. Ultimately, I had to delete W3 AND I had to use regedit on Receptor to get rid of ALL of the keys related to Wusikstation. Then I could install W1 with no issues.

I had previously purchased Vox'D and TSW....bitr also had "receptorized patches" that work with W1 and those add-on soundsets (in addition to T3's TSW banks).

Also, if you really want to keep W3 you can have the W1 version that came with Vox'D, TSW or Manystation and run them both at the same time. Since they are different DLL names, there is no comflict with W3 (but alas, those DLL's cannot load the receptorized banks that started this thread

[Kermit Jagger]

Yes, I was afraid W3 would overwrite W1 in the registry.

Nevermind, W1 is fine for now, until William fixes that registry conflict.

[WilliamK]

What registry conflict? Wusikstation V3 is an UPDATE, not a new product. So please, do tell me how I can help you guys. V3 doesn't work on Receptor? Tell me how I can improve things, and I will think on a solution.

Best Regards, WilliamK

[WilliamK]

I think I'm starting to understand the problem. One thing, if you create a directory called "MIDI Presets" and put up to 512 files there, load the FIRST preset, open CONFIGURATION and click SET DEFAULTS. Now, every time you open Wusikstaiton, it will load those 512 presets on the BANK, so Receptor "should" be able to see those presets, and you should be able to Receptorize those. Can you check if this works?

Wk

[Kermit Jagger]

To get a presets that can be called directly, it needs to be in FXP format. So that would mean using a host to convert the Wusik preset to a FXP first, if that's possible, which I don't know as I haven't installed W3 yet.

Wusikstation V3 is an UPDATE

Yes, it is an update, but you should be able to install it and test it before deciding to keep it, specially when you have a previous version installed that's already working.

But if you send me a second Receptor, I don't mind installing W3 and beta-test it

Since I only have one, you can understand why I'm reluctant to potentially screw things up.

[WilliamK]

To get a presets that can be called directly, it needs to be in FXP format. So that would mean using a host to convert the Wusik preset to a FXP first, if that's possible, which I don't know as I haven't installed W3 yet.

Yes, it IS possible. But it is limited to 512 presets per folder, and it works like this. The FXP file will have the current loaded preset, BUT, it will also have the preset path. So when you load it, it will also force Wusikstation to re-list all the current path presets into the host preset-list.

So, how should we handle this? We could create a FXP file for each directory. Load the very first preset from that directory, now save the FXP file using a host that supports it. I got Orion here that does, I could try this out. We would end with several FXP files, but that's the only way to do this.

So, Wusikstation V3 DOES work with Receptor, we just need to sort this problem out. I will see if I couldn't just create FXP files from Wusikstation GUI, adding this option to V3. Give me until next week, so I can do all this, as I need to finalize something else today and tomorrow.

Best Regards, WilliamK

[WilliamK]

Oooops, I made a mistake. I was thinking on BANKS, now I see that Receptor needs individual FXP files, one for each preset. Still, its possible. Question, when you load Wusikstation on Receptor and opens its GUI, is it possible to have the current Bank of presets saved into several FXP files? Or how else could this be done? Does anyone knows how the FXP format works? If you guys help me out, I can solve this problem pretty fast.

Best Regards, WilliamK

[Kermit Jagger]

Basically, Receptor needs one folder which is classed as a bank, and individual FXP inside the folder, representing the presets for that particular bank.

The problem as I see it is this :

With the old BNK format, you could save an FXB. Receptor takes the FXB, and automatically creates a folder containing midified FXP. So the next time you load Wusik as a sound source, you can simply place MSB/LSB and program change messages at the beginning of a track in your sequencer, and the proper Wusik patch will be selected, WITHOUT having to 1- open Wusik's GUI, 2- select the patch. This was working well because a Wusik bank was 96 presets, and Receptor can work with up to 128 FXP in one folder (midi 0 to 127).

With version 2 and 3, you cannot save an FXB containing the presets since the arrangement is using nested folders. The only thing you can do is to open a particular preset in your host, and save that preset as an FXP.

Considering the work of having to save individual presets as a bunch of FXP, one by one, you can imagine how long it would take to save all of Wusik presets in Receptor format compared with exporting one FXB and have Receptor do the rest. It is possible because if Wusik had a folder named Bass, containing 3 sub-folder for a total of 200 presets, you could create a folder Bass 01 with 128 FXP and Bass 02 with the remaining 72 FXP. But that would take many, many man hours.

[Kermit Jagger]

Of course, this is a moot point if you're not bothered about selecting presets from within Wusik's GUI.

But the other advantage to being able to select presets the Receptor way, is that if you don't have a monitor and mouse at the ready, you can still use midified presets just using Receptor's front panel. You won't if they haven't been receptorized.

[WilliamK]

Ok, I got it now. I will create a WusikPRST to FXP converter next week, and it will solve those problems.

BTW: Sorry that I hijaked this post...

Wk

[Hybernation]

Ok, I got it now. I will create a WusikPRST to FXP converter next week, and it will solve those problems.

BTW: Sorry that I hijaked this post...

Wk

Oh that would be GREAT, William! I reverted my Receptor version from V3Bxx back to V1 so I could take advantage of all the Receptorized presets coming along, but I will happily get back to tbe V3 bandwagon once this converter is available.

BTW: when I reverted, W1 seemed to have an issue with some of the registry entries. Upon launch it complained bittery about something to do with the "skin" or some "text" file. On the PC, same issue but I could click through all the errors the first time and then the problem was gone. On Receptor, it would lock up after the 4th click or so. So, I wiped the Wusikstation entries from the Receptor registry and reinstalled V1, and as was well. That was what I meant by the "registry conflict".

As a suggestion, since V3 is such a different beast from W1, COULD it be treated (upon final release perhaps) as a different DLL name and could it read for different registry entries? For instance Wusikstation3.dll reading "Wusikstation3" registry entries? Then, W1 and W3 could live happily side-by-side on most any platform. I noticed that Maxx took this approach with Toxic2 vs. ToxicIII and it does seem to make a lot of sense.

Regarding W3 on Receptor, you know I NEVER got W2 to run at all. Opening the GUI would crash Receptor every time. With W3, it DOES *occasionally* crash Receptor (the very soft quick reset kind of crash, which is pretty much a non-issue unless you are playing live). Seems like all of the crashes I have experienced happen when using the preset browser (another reason for using the Receptorzed presets, as several unsupported plugins will crash occasionally when selecting preset from the plugin's GUI vs. from Receptor). Anyway, it is GREAT that V3 does work on Receptor. There are some issues with the install, which I will document for the Receptor community once V3 final version is released.

Thanks for Wusikstation, William. I use it on a daily basis. The size and strength of the community of users and sound-developers is an amazing thing, and it is a testiment to the excellence of Wusikstation!

[Kermit Jagger]

A WUsikPRST to FXP converter !