Bug reports + FRs for Waldorf plugins (e.g. Largo, PPG Wave 3.V, Waldorf Edition, Lector)

[SLiC]

I posted on support that it largo 2 resizes to small when selecting another pre-set bank on windows.

[mi-os]

I have problems loading certain presets in the latest version of PPG 3.V (1.3.2 and v1.2.3). For example, when i open Ingo Weidners sound bank, i get tons of transient *not found* errors. Preset 001 reports its missing "T170 WO ACCORDEON", presets 002 and 003 don't produce any sound at all and so on. Can anyone confirm this?

[mi-os]

Please help. It looks like Waldorf support can't reproduce this issue on their end.

I have a dedicated audio PC which is very clean without any random crapware installed. I have no problems with all my other stuff. I'm running Windows 10 Pro and Cubase 11 Pro latest versions. I already reinstalled the plugin multiple times without any luck. Everything looks normal. The sound sources are there and soundbanks found by the plugin. But for some reason some presets work while others not.

So please read my comment above and try loading the mentioned sound bank/presets and report back. Thank you very much.

[chk071]

I have problems loading certain presets in the latest version of PPG 3.V (1.3.2 and v1.2.3). For example, when i open Ingo Weidners sound bank, i get tons of transient *not found* errors. Preset 001 reports its missing "T170 WO ACCORDEON", presets 002 and 003 don't produce any sound at all and so on. Can anyone confirm this?

I don't have PPG 3.0 installed at the moment, but, what happens when you load your DAW with administrative rights? Right-click on the desktop icon or Start menu entry, choose "Execute as administrator" (or something similar, don't know how it is phrased in English), and then check if the presets load now.

Background is that some sounds related to the presets, or the presets themselves reside in folders which require administrative rights to write to on your system. Kind of a classic issue.

[mi-os]

Yes, file rights or Windows Defender blocking files or something like this could be the culprit. I could try running it in SAVIhost and see what happens there. I don't see me changing the privilegs of my DAW because of a single plugin but also need to understand what is causing this first.

[chk071]

Running your DAW with admin rights just once won't hurt though, just to check if it has something to do with it.

[mi-os]

Ok, installed SAVIhost and got the same problem, but running it as admin solved the issue. So i think it's save to say there is a problem with the file/folder permissions or something related.

Even i'm more or less able to read/write code in a few simpler languages i'm rather bad at system admin things like file permissons/roles etc. One of the reasons i don't particularly like unix based systems. I just don't want to think about stuff like that. So i'm runnning my Windows machines as admin and never really have to think about that until something like this happens. I randomly looked at some related folders and file permissons and couldn't see what is wrong with what. So at the moment i've no idea how to trace the problem. Any ideas?

[mi-os]

How about recursively changing all contained files and folders in PPG library folder? Something like READ permissions for everything and everyone.

[chk071]

In which folder(s) do the PPG presets and sounds reside?

And, do you have a custom folder for your VST plugins, or do you just install them in the default path (something like C:\ProgramFiles\VSTplugins)?

[mi-os]

Path to sound library which contains banks/presets and sound sources:
C:\ProgramData\Waldorf\PPG Wave 3.V\PPG Wave 3.V Sounds

The VST3 itself is located in the standard VST3 folder:
C:\Program Files\Common Files\VST3

[chk071]

Ok. To be honest, I don't know much about changing folder or file permissions in Windows, but, there should be information about that online, for example here: https://answers.microsoft.com/en-us/win ... aac1415373 (under "Take ownership" in the first reply)

I don't know why the permissions changed in your case either, but, I also saw it happen a few times on my computers.

[mi-os]

The folders and files are owned by administators and have either 'full control' (for administrators) or at least 'read' permissions (for users). I assume when both groups have at least read permission that should be sufficient to read the sound sources. So even when i'm logged in as admin and only get limited rights because i don't run the app/host as admin i don't understand why the sound sources can't be read.

The strange thing is that some of the files, like patches, can be read, but others obviously not. The question is what is the difference between them. I hate wasting time with stuff like this.