KVR Audio

raymondwave · Post by **raymondwave** » Wed Jul 02, 2014 10:53 am

The Mac update seems to be withdrawn too. Can't see any installers downloadable now.

EvilDragon · Post by **EvilDragon** » Wed Jul 02, 2014 10:55 am

What I don't understand is - if they are going to pull downloads from the server, why don't they put the previously released version available for download? This is just bad form and way of working. Please tell them that, Ingo.

Ingonator · Post by **Ingonator** » Wed Jul 02, 2014 11:17 am

Everglide wrote:
Ingonator wrote:
Rommelaar wrote:New Waldorf Largo windows plugin available 1.5.2 release candidate.

http://www.waldorf-music.info/downloads ... in_RC1.zip
The link was published accidently and does not work anymore.

Anyway my own opinion is that those "accidently" published Links (two imes now) were very helpful (also see my last post above) and it would make sense to publish the current Installer as a "Public Beta". I just noted this in an email to Waldorf.

Ingo
+1

Ingo,

Command / Alt click the Largo keyboard = Hold Key Press

Have they fixed it?

Hi,

no does not seem to work with the 64-bit VST.

EvilDragon wrote:What I don't understand is - if they are going to pull downloads from the server, why don't they put the previously released version available for download? This is just bad form and way of working. Please tell them that, Ingo.

Looks like Waldorf plans to officially release the already accidently released Release Candiate (maybe with additional updates/fixes) soon.

Currently i am trying to care about the FM bug reported above. Just chekced the old 32-bit plugin and there seems to be a problem indeed.

Ingo

lalo · Post by **lalo** » Wed Jul 02, 2014 11:19 am

Ingonator wrote:
The link was published accidently and does not work anymore.

Anyway my own opinion is that those "accidently" published Links (two imes now) were very helpful (also see my last post above) and it would make sense to publish the current Installer as a "Public Beta". I just noted this in an email to Waldorf.

Ingo

+1

maybe a public beta would be quicker in solving so evident bugs

i mean they emerge really soon if trying to program a patch and maybe not if the testing is limited to preset surfing? so having a larger testing team can help i guess. just my humble opinion. Personally when i test something new first things i try are programming a patch and testing VST parameter automation in terms of accessible parameters ( ideally everything should be a VST parameter ) and parameter smoothing on critical parameters ( cutoff, pitch and the likes ). But i know this is determined by my style of music ( lot of live improvisation and lot of automation).

Ingonator · Post by **Ingonator** » Wed Jul 02, 2014 11:35 am

lalo wrote:
maybe a public beta would be quicker in solving so evident bugs

This is exactly what i just mentioned to Waldorf and hopefully the Release Candidate will be back soon.

Ingo

raymondwave · Post by **raymondwave** » Wed Jul 02, 2014 12:47 pm

Do you know if the Mac problems are being looked at, most importantly the maxed out meters and noise blast/peak?

I guess it's too much for now to hope that the arp and sync probs would be looked at.

Ingonator · Post by **Ingonator** » Wed Jul 02, 2014 12:58 pm

raymondwave wrote:Do you know if the Mac problems are being looked at, most importantly the maxed out meters and noise blast/peak?

I guess it's too much for now to hope that the arp and sync probs would be looked at.

Besides the fixes i am able to check myself and those already reported here i sent a text file with bugs reported here to Waldorf. If i find time i will maybe asked if all Mac bugs are fixed too but athe moment i got enough work with the Windows plugins. BTW i mentioned that bugs found in Windows should be also checked with the Mac.
If Waldorf really publishes the Release candidates soon maybe you could check yourself.

Ingo

Mike / Matrix Lab · Post by **Mike / Matrix Lab** » Wed Jul 02, 2014 2:54 pm

Is there a release date for the 64bit version of the PPG?

Mike

MFXxx · Post by **MFXxx** » Wed Jul 02, 2014 5:59 pm

I know Largo has historically had a lot of reported bugs/issues so priority I guess.

Any news on the PPG3 update?

Ingonator · Post by **Ingonator** » Wed Jul 02, 2014 6:42 pm

MFXxx wrote:I know Largo has historically had a lot of reported bugs/issues so priority I guess.

Any news on the PPG3 update?

Not at the moment. Everytime during the last week when i wanted to have another look on it i had to check/test Largo again (now with the FM issue)...
Anyway the last version of PPG Wave 3.V 64-bit seemed to be quite stable (which does not mean ther are no "hidden" bugs...).

Ingo

Ingonator · Post by **Ingonator** » Wed Jul 02, 2014 6:46 pm

Ingonator wrote:
lalo wrote:Hi, just downloaded the Win RC1 for Largo 1.5.2.
Installation went fine.
Level konbs works.
But seems there is definetly something strange in the FM modulation.
Try ti assign OSC2 to FM modulation for OSC1.
No FM at all.
Try to assign Noise and there's definetly something not working good.
The sound does not change immediatly and when it changes the FM level slider does not work very good.
The level of Noise to OSC1 FM suddenly goes from minimum ti maximum amount soundwise.
Can anyone confirm?
I'm on Win7 64bit, Reaper, RME ASIO

a.
Confirmed here. Will contact the developer concerning this problem.
Could not really remeber if i noticed such problem in a previous Beta version but i am quite sure it worked in the old 32-bit one.

UPDATE:
Currently investigating this. Will check the old Largo 32-bit again (v1.5.1) to see how it should work.

An update concerning the FM bug:

This now seems to be confirmed for the VST2 64-bit and AAX plugins (for Windows). With the new VST3 and VST2 32-bit plugins it seems to work normally (like in the old 32-bit plugin). This is strange as usually most bugs happened in all plugin versions.

Ingo

lalo · Post by **lalo** » Wed Jul 02, 2014 7:06 pm

i reinstalled the 32 bit version of 1.5.0 and everything works fine in the FM realm. Except that Largo crashes Reaper when closing its GUI. At least with my patch loaded.

maybe some problem of getting 1.5.0 and 1.5.2 installed together?

Ingonator · Post by **Ingonator** » Wed Jul 02, 2014 7:19 pm

lalo wrote:i reinstalled the 32 bit version of 1.5.0 and everything works fine in the FM realm. Except that Largo crashes Reaper when closing its GUI. At least with my patch loaded.

maybe some problem of getting 1.5.0 and 1.5.2 installed together?

As mentioned above the FM problem should not appear in the new VST2 32-bit plugin (v1.5.2).

For checking the old 32-bit plugin (v1.5.1) in the past i kept a copy of the DLL file so i just used that one without deinstalling anything.

lalo · Post by **lalo** » Wed Jul 02, 2014 7:40 pm

the official Waldorf version now downloadable when you buy Largo is 1.5.0. where can i find the 1.5.1 version?

thanks

Ingonator · Post by **Ingonator** » Wed Jul 02, 2014 8:09 pm

lalo wrote:the official Waldorf version now downloadable when you buy Largo is 1.5.0. where can i find the 1.5.1 version?

thanks

The 1.5.1 version does not seem to be available at the moment (at least not at the official website) but if you want to use a 32-bit plugin (like the old version) you could use the new v1.5.2 32-bit VST which does not seem to include the FM bug as already mentioned.
Anyway i hope there will be a fixed 64-bit VST soon (the VST3 also works properly like already mentioned).

It also seem to be planned to officially release a Release Candidte after doing a few additional bugfixes (including some fixes for AAX and the Mac plugins).

If you really need the 1.5.1 32-bit plugin you could contact Waldorf support. Not sure if i would be allowed to provide a link myself.

Ingo

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