Waldorf Largo + PPG Wave 3.V + Waldorf Edition: 64-bit/VST3/AAX updates

[Ingonator]

Surface Pro 3 is just a different shape of a laptop, so it's not really any different - the OS is exactly the same that might be on a laptop (Windows 8, that is).

I know, but there still could be problms related to the built-in hardware and using with certain music software.
At the end it is still slightly different to a "usual" notebook.

Anyway currently i am more interested if the member has remaining problems with Waldorf plugins and which problems those are exactly.

[EvilDragon]

It has a Realtek audio chip which is found built-in on a lot of regular desktop motherboards these days (and laptops!). There are no problems in using that chip along with WASAPI or ASIO4ALL drivers (WASAPI is usually a better call, though), really. And it runs regular desktop software just fine. So, don't think hardware's the issue.

[Ingonator]

edit

[rasmusklump]

Hi,

I have the original Waldorf edition. I don't know if i have it registered anywhere, but I have still the original disc.
How do I upgrade ?
Cheers
Alex

[Ingonator]

Hi,

I have the original Waldorf edition. I don't know if i have it registered anywhere, but I have still the original disc.
How do I upgrade ?
Cheers
Alex

Hi,

if you have the old Cd protected Waldorf Edition you have to contact Walodrf support ti receive a new serial that works with the latest versions.
AFAIK the first 64-bit versions with the new protection was relased back in beginnig 2012 while the download was not directly available at the website there as it is now.


Ingo

[Ingonator]

Unfortunately I'd have to agree that their support is bad. They make simple mistakes in their suggestions like telling me to reinstall windows when that has nothing to do with the issues, they are not always very polite, in some cases down right dismissive of the problem even when you provide them with screenshots, and it often takes days to get a response and sometimes multiple emails to get a response.

The frustrating thing is I like Attack and use it as my main drum synth. I just wish it came from a better run company. It sometimes amazes me they stay in business, you would think they learned something after the first time they went under but maybe not.

PM sent.

[Ingonator]

Unfortunately I'd have to agree that their support is bad. They make simple mistakes in their suggestions like telling me to reinstall windows when that has nothing to do with the issues, they are not always very polite, in some cases down right dismissive of the problem even when you provide them with screenshots, and it often takes days to get a response and sometimes multiple emails to get a response.

The frustrating thing is I like Attack and use it as my main drum synth. I just wish it came from a better run company. It sometimes amazes me they stay in business, you would think they learned something after the first time they went under but maybe not.

PM sent.

UPDATE:
Based on the PM i received indeed a Microsoft Surface Pro 3 tablet PC with Windows 8.1 and Cubase 8.0.5 was used.

There seemed to be a white/blank GUI withWalodrf Edition VST3 plugins (not with VST2) and based on the PM it is also possible this was fixed with a recent Windows update.

Could not confirm such problem here yet (same with the Beta of Waldorf Edition 2) and AFAIK this was also not reported by our testers yet.


Ingo

[Ingonator]

I upgraded from Cubase 7.5 to Cubase Pro 8.

So far i did not find problems that are specific to using Cubase Pro 8.0.5 on Windows 7 64-bit.

[relayer2001]

Waldorf just published a new Release Candidate 2 for the Waldorf Edition:

http://www.waldorf-music.info/downloads-we

Facebook: https://www.facebook.com/WaldorfMusic


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 spent the past 3 days trying to get WE VST3 plugins to read fxb files. Should have come here first. Pity that Waldorf makes no mention of this on their website of in the WE manual.

One question though. When you say "start your host/DAW without administrator rights", what do you mean exactly? I run my OS (Win 7 Pro 64-bit) in Administrator mode. Are you saying that I can only use the drag & drop feature in non-administrator mode?

I'm running Waldorf Edition v1.7.4 RC5 64-bit on Cubase Pro 8.0.5 (64-bit).

[Ingonator]

Waldorf just published a new Release Candidate 2 for the Waldorf Edition:

http://www.waldorf-music.info/downloads-we

Facebook: https://www.facebook.com/WaldorfMusic


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 spent the past 3 days trying to get WE VST3 plugins to read fxb files. Should have come here first. Pity that Waldorf makes no mention of this on their website of in the WE manual.

One question though. When you say "start your host/DAW without administrator rights", what do you mean exactly? I run my OS (Win 7 Pro 64-bit) in Administrator mode. Are you saying that I can only use the drag & drop feature in non-administrator mode?

I'm running Waldorf Edition v1.7.4 RC5 64-bit on Cubase Pro 8.0.5 (64-bit).

Administrator right means the setting for the specific software, not the whole Windows.

If you right-click on the desktop symbol or the EXE file of you host in Properties -> Copmpatibility you could check "start program with administrator rights" (this is a rough translation as i ue a german Windows 7 here...). This has to be unchecked to use the drag & drop feature.

Several months ago i posted a collection of the Waldorf Edition presets in multiple formats:
https://dl.dropboxusercontent.com/u/532 ... %20AAX.zip

Also with my free bank multiple formats are included (for PPG Wave 3.V this is not necessary as it has it's own browser but there are specific files for PPG 3.V that also include additional patches not done for PPG 2.V):
http://www.kvraudio.com/forum/viewtopic ... 7&t=418294

For exporting my own bank as multiple formats it was necessary to originally create the patches with the
VST2 plugin as the drag & drop feature in the VST3 and AAX plugins needs fxb/fxp files for the import.
Cubase with VST2 plugins does not support export of fxb/fxp but only import so i created the patches in Live 9.

[relayer2001]

Ingo

Thanks for the clarification. Got home tonight and converted some banks I had collected over the years.

One thing though, after converting about four banks I found that the keys of the on-screen keyboard tended to stick and not release. Only fixed after I closed down the plug-in and opened a new instance.

[Everglide]

Are these Waldorf updates working with Yosemite?

[Ingonator]

Are these Waldorf updates working with Yosemite?

There was already a specific fix for problems with the very first version of Yosemite (for Largo and PPG wave 3.V, Walodrf Edition was not necessary there). As i already mentioned here there seem to be new problems introduced by Yosemite version 10.10.2.
For example one problem could be that with the Lector installer the VST2 plugin is greyed out.
Waldorf is taking care abot this but it could take a little time as currently there are also Betatests for two new products (Nave plugin and Waldorf Edition 2).

There are also some details about OSX 10.10.2 mentioned here at the Waldorf Facebook page:
https://www.facebook.com/WaldorfMusic

Quote:

since Apple released the update to OSX 10.10.2, and Logic Pro X 10.1 we discovered some problems with the installation procedure of Largo, PPG 3.V and Lector, as well as activation procedure in Waldorf Edition. We are currently fixing it, but in the meantime we would highly recommend not to update to OSX 10.10.2

Similar problems do not seem to exist on previous versions of OSX Yosemite (e.g. OSX 10.10.1) and also not on Windows.

[Ingonator]

For Largo, PPG Wave 3.V and Lector also new update for OSX Yosemite 10.10.2 and Logic 10.1.1 were published:

http://www.waldorf-music.info/downloads-largo
http://www.waldorf-music.info/downloadsppg3
http://www.waldorf-music.info/lectordownloads

[lofty]

...