at their facebook page Waldorf music had announced the long awaited native 64-bit versions of Waldorf Largo and PPG Wave 3.V:
Gute Nachrichten für Largo- und PPG-User: Die 64-Bit-Versionen sind jetzt im Beta-Test und zur Musikmesse als final angekündigt
Good news for Largo- and PPG-users: The 64-bit versions are now at beta testing stage and announced as being final at the Musikmesse.
Currently testing those myself (Windows versions). I am not really sure if those will be at final stage until Musikmesse next week like mentioned there while theoretically it could be possible.
Those are two synths with multiple platforms each (e.g. Win VST, Mac VST, Mac AU) which is a "bit" of work.
Could not give additional informations at the moment (or better: not allowed to yet...).
The Release candidate of the Largo 64-bit update was published now:
The reported GUI bugs (Level/Mixer knobs + Delay Clock display), crashes while scanning the plugin, broken mousewheel support and FM-bug should be fixed now.
Additionally there was also a fix for hanging notes in the AAX plugin when using a MIDI-keyboard.
Waldorf has published the first Release Candidate (RC1) of Waldorf PPG Wave 3.V 64-bit:
This was also notd at their Facebook page:
Like with Largo no new features added with this update. The focus was on porting to 64-bit, VST3 and AAX.
Here is the link for the Waldorf Edition 64-bit Release Candifdate 1:
Again this was mentioned at the Facebook page:
Installers for the Waldorf Edition LE seem to be included too.
To sum it up Waldorf published Release Candidates for Largo, PPG Wave 3.V, Waldorf Edition and Wasldorf Edition LE now:
PPG Wave 3.V:
Waldorf Edition LE:
Waldorf has just published the Release Candidate 2 for Largo:
As always any bug reports are welcome. Having all those avilable to the public should give the opportunity to find remaining bugs.
Waldorf just published a new Release Candidate 2 for the Waldorf Edition:
This contains several fixes for e.g. aftertouch, GUI glitches, renaming patches in VST3 + AAX, loading fxb/fxp files to VST3/AAX by drag & drop from your file browser (e.g. Windows Explorer), a fix for licenses on OSX (does no longer have to be entered every time you opena plugin), etc.
Also problems with saving/loading patches in VST3/AAX format have been solved.
With the drag & drop feature you could load fxb/fxp files to the VST3 or AAX plugins by moving the files from e.g. the Windows Explorer to the GUI of the plugin. After that you could save the imported patches in e.g. VST3 or AAX specific formats. If you want to use the drag & drop feature yu have to start your host/DAW without administrator rights (you could add this back later if drag & drop is no longer needed).
I have alraedy done this for all presets and those are included in this ZIP file:
https://dl.dropboxusercontent.com/u/532 ... %20AAX.zip
- fxb/fxp files should be in C:\ProgramData\Waldorf in Windows and at Library/Audio/Presets/Waldorf for OSX
- VST 3 Presets should be at: C:\users\your name\Documents\VST3 Presets\Waldorf
- .Pro Tools Presets (for AAX plugins) should be at: C:\users\your name\Documents\Pro Tools\Plug-In Settings)
For VST3 and AAX you have to save a patch to create a new folder that is recognized by the host.
This will add folders like e.g. "Attack", PPG Wave 2_V", "D-Pole" etc. at the locations mentioned above.
Waldorf decided to not include a dedicated load/save feature in the current updates of the Waldorf Edition plugins.
One hint for everyone who wants to use his own patches in multiple formats is to first create them in the VST2 plugin and save the patches in the fxb/fxp format. This opens the opportunity to import the patches to VST3 and AAX by drag & drop (and saving in the corresponding formats then).
Waldorf just released new installers for Largo RC4 and PPG Wave 3.V RC3 at their website:
PPG Wave 3.V: http://www.waldorf-music.info/downloadsppg3