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

[jalcide]

My Largo Filter Cutoff responds to automation, but not so with its Res and Drive (1st filter unit in this case).

Am I missing some kind of setup, or is it a known issue?

UPDATE: Also, even the Cutoff appears to not remember its last value when reloading a project.

RC3, VST3 x64, Win 7, Cubase 7.5.20 x64

[ChristopherMoyse]

RC3 Largo 64-bit VST3 now responds to Channel Pressure in Sonar X3 - thanks!

[Ingonator]

UPDATE: Also, even the Cutoff appears to not remember its last value when reloading a project.

RC3, VST3 x64, Win 7, Cubase 7.5.20 x64

Could not confirm this with RC3 64.vit VST3 in Cubase 7.5.20 64-bit at Windows 7 64-bit.

Cutoff seems to be saved and loaded with the project properly.

[raymondwave]

I've had problems with PPG Wave 3v where certain patches reload with different values. Not all patches, just some. But this like many other problems couldn't be reproduced by Waldorf.

Just tried and the same bug is still there:
Studio One Mac 2.6.2
New Project
Load PPG Wave 3v (I was using 64bit VST3)
Load "025 PwmPad" from Till Kopper bank (found in Local Library/PPG Wave 2v Library/Till Kopper.fxp)
Close project
Reload project
The smooth pad has turned into a glitchy wavetable sweep, I'm guessing some values are not properly re-loaded

Maybe someone can try this out, Ingo?

[Ingonator]

I've had problems with PPG Wave 3v where certain patches reload with different values. Not all patches, just some. But this like many other problems couldn't be reproduced by Waldorf.

Just tried and the same bug is still there:
Studio One Mac 2.6.2
New Project
Load PPG Wave 3v (I was using 64bit VST3)
Load "025 PwmPad" from Till Kopper bank (found in Local Library/PPG Wave 2v Library/Till Kopper.fxp)
Close project
Reload project
The smooth pad has turned into a glitchy wavetable sweep, I'm guessing some values are not properly re-loaded

Maybe someone can try this out, Ingo?

Currently checking this.

[Examigan]

I've had problems with PPG Wave 3v where certain patches reload with different values. Not all patches, just some. But this like many other problems couldn't be reproduced by Waldorf.

Just tried and the same bug is still there:
Studio One Mac 2.6.2
New Project
Load PPG Wave 3v (I was using 64bit VST3)
Load "025 PwmPad" from Till Kopper bank (found in Local Library/PPG Wave 2v Library/Till Kopper.fxp)
Close project
Reload project
The smooth pad has turned into a glitchy wavetable sweep, I'm guessing some values are not properly re-loaded

Maybe someone can try this out, Ingo?

I can confirm that here, same issue. I am on 32-bit Windows 7 and have tried it with both VST2 and VST3 in Sonar X3, same thing happens.

[jalcide]

UPDATE: Also, even the Cutoff appears to not remember its last value when reloading a project.

RC3, VST3 x64, Win 7, Cubase 7.5.20 x64

Could not confirm this with RC3 64.vit VST3 in Cubase 7.5.20 64-bit at Windows 7 64-bit.

Cutoff seems to be saved and loaded with the project properly.

Thanks for checking. Hmm, I do have Cubase "Quick Controls" assigned to the Cutoff (my method of automation). I'll test without (and in a fresh project) and see if I can reproduce your positive result.

Also, I haven't written, nor am I reading, any automation (Quick Control or otherwise). So I'll also try writing / reading the values as a possible workaround.

[amundsen_scott]

I've had problems with PPG Wave 3v where certain patches reload with different values. Not all patches, just some. But this like many other problems couldn't be reproduced by Waldorf.

Just tried and the same bug is still there:
Studio One Mac 2.6.2
New Project
Load PPG Wave 3v (I was using 64bit VST3)
Load "025 PwmPad" from Till Kopper bank (found in Local Library/PPG Wave 2v Library/Till Kopper.fxp)
Close project
Reload project
The smooth pad has turned into a glitchy wavetable sweep, I'm guessing some values are not properly re-loaded

Hello, I've tested with the same patch(025 PwmPad) on the Logic Pro 9. Same issue happens here too.

And the FXP(not FXB) loading issue I've posted before has still not be fixed.

Let me give an example -

1. You save the "025 PwmPad(PPG Wave 2v Library/Till Kopper.fxb)" as single ".fxp" program.
2. Reload project, then sound is wrong (as you know).
3. Try to reload the relative fxp program. It NEVER return to the original sound.
4. Only solution as yet is you must save your own program as FXB bank file and reload it.



thank you.

[Ingonator]

I've had problems with PPG Wave 3v where certain patches reload with different values. Not all patches, just some. But this like many other problems couldn't be reproduced by Waldorf.

Just tried and the same bug is still there:
Studio One Mac 2.6.2
New Project
Load PPG Wave 3v (I was using 64bit VST3)
Load "025 PwmPad" from Till Kopper bank (found in Local Library/PPG Wave 2v Library/Till Kopper.fxp)
Close project
Reload project
The smooth pad has turned into a glitchy wavetable sweep, I'm guessing some values are not properly re-loaded

Hello, I've tested with the same patch(025 PwmPad) on the Logic Pro 9. Same issue happens here too.

And the FXP(not FXB) loading issue I've posted before has still not be fixed.

Let me give an example -

1. You save the "025 PwmPad(PPG Wave 2v Library/Till Kopper.fxb)" as single ".fxp" program.
2. Reload project, then sound is wrong (as you know).
3. Try to reload the relative fxp program. It NEVER return to the original sound.
4. Only solution as yet is you must save your own program as FXB bank file and reload it.



thank you.

Those banks in that folder are Banks made with PPG Wave 2.V and the problem seems to happen when import them into PPG Wave 3.V.
This does not happen with patches created with PPG Wave 3.V.

Actually they keytrack amounts seem to be imported wrongly or better those are wrong when re-saving the bank or savingg/loading a project file in the host.

This also seems to happen with the old 32-bit plugin (v1.0.2).

This is my current solution:
1.) Import the PPG 2.V bank into PPG Wave 3.V
2.) Change the True PPG mode in all presets to "2.V" mode (optional)
3.) save the bank file in PPG 3.V
4.) re-open the bank file in PPG 3.V
5.) correct the values for the KEYTRACk of the WAVES and the FILTER in the MODULATION menu of the PPG 3.V
6.) save the bank again.
7.) save single programs if needed.



Ingo

[raymondwave]

Thanks for testing the PwmPad thing everyone, seems to be quite easily reproducable. Strange that they couldn't reproduce this back in 2012 when I first reported this to Waldorf.

Do you think this is a bug or a feature, meaning is this something that could be fixed in the future versions?

[Ingonator]

Thanks for testing the PwmPad thing everyone, seems to be quite easily reproducable. Strange that they couldn't reproduce this back in 2012 when I first reported this to Waldorf.

Do you think this is a bug or a feature, meaning is this something that could be fixed in the future versions?

My guess is that this is not fixed easily. It is reported to Waldorf so let's see.

[MFXxx]

NEW ! Waldorf PPG Wave 3.V - VST VST3 AAX 32 & 64 Bit - Vers. 1.0.3 RC2 ( WIN )

Appears to be bombing out Cubase VST3, VST 2.4 not an issue.

Windows 8.1 x64
Cubase 7.5.2 x64
PPG3 Vst x64

Incidentally whilst setting up multi outs ie in the cubase rack and switching within the GUI to 16 outs. Each channel is deafulting to Stereo 1 out only...any tips appreciated

Thanks

[Ingonator]

NEW ! Waldorf PPG Wave 3.V - VST VST3 AAX 32 & 64 Bit - Vers. 1.0.3 RC2 ( WIN )

Appears to be bombing out Cubase VST3, VST 2.4 not an issue.

Windows 8.1 x64
Cubase 7.5.2 x64
PPG3 Vst x64

Mybe this helps?

There is also a new RC2 for PPG Wave 3.V:
http://www.waldorf-music.info/downloadsppg3

Not all bugs solved yet. Aftertouch is working properly now, also with VST3. Also a problem with using patches that use samples in the AAX plugin are solved.

One of oit testers mentioned that the VST3 of PPG Wave 3.V (on Windows) seemed to crash when you try to load it. I was able to confirm that in Cubase and Studio One.
Anyway i remebered a recent discussion with our developer where he mentioned somethimg about a certain folder.
I created a new folder (nothing else, just create that new folder): c:\test
This seems to solve that problem.

[MFXxx]

NEW ! Waldorf PPG Wave 3.V - VST VST3 AAX 32 & 64 Bit - Vers. 1.0.3 RC2 ( WIN )

Appears to be bombing out Cubase VST3, VST 2.4 not an issue.

Windows 8.1 x64
Cubase 7.5.2 x64
PPG3 Vst x64

Mybe this helps?

There is also a new RC2 for PPG Wave 3.V:
http://www.waldorf-music.info/downloadsppg3

Not all bugs solved yet. Aftertouch is working properly now, also with VST3. Also a problem with using patches that use samples in the AAX plugin are solved.

One of oit testers mentioned that the VST3 of PPG Wave 3.V (on Windows) seemed to crash when you try to load it. I was able to confirm that in Cubase and Studio One.
Anyway i remebered a recent discussion with our developer where he mentioned somethimg about a certain folder.
I created a new folder (nothing else, just create that new folder): c:\test
This seems to solve that problem.

Thanks resolves the vst3 crash. Actually remember reading this several threads back and forgot about it.
I am getting some spiking noise when playing. Asio load fairly load.

Still struggling with the multi outs.

[Ingonator]

Incidentally whilst setting up multi outs ie in the cubase rack and switching within the GUI to 16 outs. Each channel is deafulting to Stereo 1 out only...any tips appreciated

Audio outs seem to work but there is currently a bug with the VST3 that you could only use MIDI Channel 1.
Playing multiple parts at MIDI channel 1 and using different audio outs seems to work.
Same for the AAX plugin. Our developer is currently working on this.


Ingo