I do not have OSX myself here but in the past with such problems it helped to delete the PLIST preference files for the plugin that caused problems. AFAIK the new OSX updates published today should work properly.lofty wrote:"For Largo, PPG Wave 3.V...new update for OSX Yosemite 10.10.2 and Logic 10.1.1 were published:"
both PPG3 & Largo do not pass Logic X10.1.1 AU validation
VSTs do not pass for Live9.1.7 (32bit) AUs cause Live to crash
Both PPG3 & Largo unusable on OSX10.10.2 here
(this is after following the instructions on the Waldorf installers and downloading latest version of eLicencer and using the USB dongle before installation of PPG3/Largo)
Waldorf Largo + PPG Wave 3.V + Waldorf Edition: 64-bit/VST3/AAX updates
- KVRAF
- Topic Starter
- 12522 posts since 21 Mar, 2008 from Hannover, Germany
Ingo Weidner
Win 10 Home 64-bit / mobile i7-7700HQ 2.8 GHz / 16GB RAM //
Live 10 Suite / Cubase Pro 9.5 / Pro Tools Ultimate 2021 // NI Komplete Kontrol S61 Mk1
Win 10 Home 64-bit / mobile i7-7700HQ 2.8 GHz / 16GB RAM //
Live 10 Suite / Cubase Pro 9.5 / Pro Tools Ultimate 2021 // NI Komplete Kontrol S61 Mk1
- KVRAF
- 2627 posts since 16 May, 2004 from Soviet Union
Wanted to question: do whether can be coexist new waldorf edition plugins version together with past version ? (ie they will be show as separately in daw?) Just i would want keep both.
- KVRAF
- Topic Starter
- 12522 posts since 21 Mar, 2008 from Hannover, Germany
The plugin names in the V2 are the same so you'll have to rename the old ones to keep them.c_voltage wrote:Wanted to question: do whether can be coexist new waldorf edition plugins version together with past version ? (ie they will be show as separately in daw?) Just i would want keep both.
This seems to work properly in some hosts but maybe cause problems in others. You'll have to check taht at your system.
The serials for the old an new Waldorf Edition are different.
Ingo Weidner
Win 10 Home 64-bit / mobile i7-7700HQ 2.8 GHz / 16GB RAM //
Live 10 Suite / Cubase Pro 9.5 / Pro Tools Ultimate 2021 // NI Komplete Kontrol S61 Mk1
Win 10 Home 64-bit / mobile i7-7700HQ 2.8 GHz / 16GB RAM //
Live 10 Suite / Cubase Pro 9.5 / Pro Tools Ultimate 2021 // NI Komplete Kontrol S61 Mk1
- KVRAF
- 24402 posts since 7 Jan, 2009 from Croatia
Nothing changed sound-wise in the Waldorf Edition update. Apart from Attack being able to load samples, and a bit more flexibility with its effects. PPG V.2 and D-Pole stayed the same.
- KVRAF
- 2990 posts since 13 Apr, 2008 from Charleston, SC
Question- I upgraded from Waldorf Edition LE to Waldorf Edition V2. Where are all off the sounds? I only show 128 sounds in PPG and Basic in Attack. There are no fxp/fxb files, and no way to select a bank from the program from what I can tell. Help...heh.
Jon
Jon
- KVRian
- 507 posts since 8 Dec, 2004 from Belgrade
Hm, nice new skins, but I expected that controls for D-Pole will at least be more fine-grained, but they stayed the same, completely unprecise. All plugins work seamless after update, so that's a plus. But as this was more or less skins update, I wouldn't expect it to be less. Samples look nice, will try.
- KVRAF
- 2627 posts since 16 May, 2004 from Soviet Union
Hm, frankly i have not done this before, it is normal practice for plugins? ie rename will not cause problems in the plugins work themselves? (without taking into account the host reaction)Ingonator wrote: The plugin names in the V2 are the same so you'll have to rename the old ones to keep them.
- KVRAF
- Topic Starter
- 12522 posts since 21 Mar, 2008 from Hannover, Germany
I do not have a "guideline" for all hosts at the moment but from my own experoience it works in most cases.c_voltage wrote:Hm, frankly i have not done this before, it is normal practice for plugins? ie rename will not cause problems in the plugins work themselves? (without taking into account the host reaction)Ingonator wrote: The plugin names in the V2 are the same so you'll have to rename the old ones to keep them.
Sometimes i also used a 64-bit and 32-bit plugin in the same folder where i re-named one of them.
Anyway recently for the Beta of Waldorf Edition 2 i avoided to keep both versions to avoid conflicts that could appear like a bug in the new version.
Last edited by Ingonator on Fri Mar 13, 2015 1:58 pm, edited 1 time in total.
Ingo Weidner
Win 10 Home 64-bit / mobile i7-7700HQ 2.8 GHz / 16GB RAM //
Live 10 Suite / Cubase Pro 9.5 / Pro Tools Ultimate 2021 // NI Komplete Kontrol S61 Mk1
Win 10 Home 64-bit / mobile i7-7700HQ 2.8 GHz / 16GB RAM //
Live 10 Suite / Cubase Pro 9.5 / Pro Tools Ultimate 2021 // NI Komplete Kontrol S61 Mk1
-
- KVRist
- 203 posts since 16 Sep, 2005
I'm renaming plugin for years without any problem (I remove the x64 or number of outputs from the .dll).c_voltage wrote:Hm, frankly i have not done this before, it is normal practice for plugins? ie rename will not cause problems in the plugins work themselves? (without taking into account the host reaction)Ingonator wrote: The plugin names in the V2 are the same so you'll have to rename the old ones to keep them.
-
- KVRist
- 203 posts since 16 Sep, 2005
Keep in mind though that after you've run an update for a particular VST you once renamed, you might end up with 2 .dll files. The "old" one you renamed in the past. And the updated new version one.c_voltage wrote:Ingonator, cranium, ok thanks. (Just i heard ofcourse about this and before, but not did yet)
Even then I simply delete the "old" .dll version and rename the new .dll file the way I prefer it to show up in my host.
- KVRAF
- 2627 posts since 16 May, 2004 from Soviet Union
Yes, it of course.cranium wrote:Keep in mind though that after you've run an update for a particular VST you once renamed, you might end up with 2 .dll files. The "old" one you renamed in the past. And the updated new version one.c_voltage wrote:Ingonator, cranium, ok thanks. (Just i heard ofcourse about this and before, but not did yet)
-
- KVRist
- 261 posts since 2 May, 2014
I started compiling an album of my tunes and have ran into a serious issue with PPG Wave v3. The sounds do not recall correctly. Just opened a tune that relied on an arp I had made with PPG v3 and it recalls as a completely different sound that is a chord instead of an arp. I had v1.0.5 loaded first, upgraded to 1.0.7 which changed nothing..
I've had this issue before with different patches and if I remember correctly, ingonator was able to reproduce this.. now it's happening again.
Started to recreate the arp from scratch, after some tweaking Studio One went mute with a peaking snap that sent the master meters to maximum. Had to re-start program.
These plugins are a fckn nightmare.
I've had this issue before with different patches and if I remember correctly, ingonator was able to reproduce this.. now it's happening again.
Started to recreate the arp from scratch, after some tweaking Studio One went mute with a peaking snap that sent the master meters to maximum. Had to re-start program.
These plugins are a fckn nightmare.
