Bidule VSTi and VST on Receptor

[CrownRoyal]

I tried installing those just for giggles last night and they didn't work. It reset the Receptor. I forgot to put the .bin keyfile in the same directory, though. Maybe it died because it couldn't find that. It would be nice if there was some kind of output from the Receptor for debugging. Perhaps there is and I don't know of it?

No biggie, though, I just thought it would be a fun exercise.

[DanTimis]

There is a system log file in the Reports folder. I forgot the exact name, but it's easy to figure out.

Chances are there will be little info about Bidule, but you never know.

[davidv@plogue]

There is a system log file in the Reports folder. I forgot the exact name, but it's easy to figure out.

Chances are there will be little info about Bidule, but you never know.

Hi.

First, it might be tricky as the key file (on PC) goes to
Documents and Settings\{username}\Application Data\Plogue\Bidule

Normally the Standalone version copies the key there for the plugin to find it. To what extent Receptor emulates the windows directory structures is beyond my current knowledge.

Secondly BiduleVST at the moment makes little sense without a GUI since there are no default FXP/FXB's that exibits the range of things it can do. We plan for this feature in 1.0.

[CrownRoyal]

There is a system log file in the Reports folder. I forgot the exact name, but it's easy to figure out.

Chances are there will be little info about Bidule, but you never know.

Hi.

First, it might be tricky as the key file (on PC) goes to
Documents and Settings\{username}\Application Data\Plogue\Bidule

Normally the Standalone version copies the key there for the plugin to find it. To what extent Receptor emulates the windows directory structures is beyond my current knowledge.

Secondly BiduleVST at the moment makes little sense without a GUI since there are no default FXP/FXB's that exibits the range of things it can do. We plan for this feature in 1.0.

Hi David,

I tried putting the keyfile and everything in the same directory but that didn't work, either. It resets the Receptor and just says it failed. I wish there was something that I could look at to see "why".

The routing, I/O, etc. of Bidule coupled with UniWire
would be very interesting. Just thinking about it makes my head hurt. There's no sense in hosting a VST inside Bidule on a Receptor but the other I/O features could be interesting.

I've come to appreciate Bidule a LOT more in the past couple months. I use it all the time.

[CrownRoyal]

There is a system log file in the Reports folder. I forgot the exact name, but it's easy to figure out.

Chances are there will be little info about Bidule, but you never know.

Thanks. I'll take a look for it when I get home.

[davidv@plogue]

I tried putting the keyfile and everything in the same directory but that didn't work, either. It resets the Receptor and just says it failed.

I forgot a few things, at the moment, the plugin really assumes the standalone is installed, for two other reasons, namely a registry key that points to two dlls required by it, namely libsndfile.dll and formulc.dll,
, skins, groups, presets, xsds and other things.