Wavosaur

[BruceA]

Using the 32-bit version 1.1.0.0 and REAPlugins. Tested with single VST saved, and also two VSTs saved as a bank file. Neither one opens when I try to "load". This will be an important feature to be able to recall saved VST configs, so I would appreciate any direction to solve this one.

Thanks!
Bruce in TN., USA.

[Rex]

hello,

can you give us the version of the REAplugins and what plugins were used ?

i've just made a test with reacomp + save as fxp, it works well when i reload the fxp file.

i don't understand this : "two VSTs saved as a bank file."
fxp / fxb are presets for only one VST at the time.

you can use "save chain" and "load chain" to save and recall a chain of VST

tell us if this helps

[BruceA]

The version is 2.1 on the REAplugins. Tested with REAcomp, as well as a few other REA plugins to make sure it wasn't just something with that one.

I understood "bank" file from a previous post here:
Posted: Sat Feb 07, 2009 6:35 am Post subject: Reply with quote
--------------------------------------------------------------------------------
hello,

fxp & fxb files are presets files for the vst plugins.
fxp for a single preset, fxb for a presets bank

you can save your preset as fxp then reload it later.
-------------------------------------------------------------------------------

I am using the 32-bit version of Wavosaur.

I hadn't tried the "load chain" before, BUT...it works for single or multiple VSTs to click "save chain", then clear the list, then "load chain", with no error. So...I can just use that method.

Still can't get the fxp or fxb to work without the "unable to open file" error coming up.

Thank you for your reply!

[AllNight]

Not sure if this ever got resolved, but I ran into it myself this morning.

Wavosaur seems to do something weird when writing FXP files. They should work, but, Wavosaur seems to be unable to load FXP files that come bundled with many plugins.


Here's a FXP saved from Wavosaur for a Soundtoys Plugin called Crystalizer:

http://tommycatkins.com/2014/wavosaur.fxp


Here's a FXP that is bundled with Crystallizer:

http://tommycatkins.com/2014/bundled.fxp


The above FXP does not load in Wavosaur; Wavosaur returns "unable to open file." However, the FXP loads fine in other programs like Reaper or even VST Plugin Analyser.

If you open the above FXP files in a hex editor you will see that they are very different. The Wavosaur one appears to be compressed or something. However, it does work when loading a new instance of the plugin in Wavosaur, then applying the Wavosaur saved FXP. (The correct settings *do* get restored.)

[Rex]

yes we have identified a problem, it happens too with the blueline VST plugins.

there's a problem with the fxp/fxb loading/saving