Waldorf Largo + PPG Wave 3.V + Waldorf Edition: 64-bit/VST3/AAX updates
-
- KVRist
- 40 posts since 31 Aug, 2004
Hi Ingo!!!! My system is winxp sp3 32bit, same behaviour on all vsthosts, and dsnt matter vst2 or vst3 works as same aslo, all user arp patterns using the 1st part's setting (in the gui editable on all parts, but using the 1st's edits), the preset arps (1-15) and the arp pattern lenght setting works independently well on all parts.
And iwant to notice also at 48khz the plug is not the best sounding(high freq domain aliasing if using xtreme settings on the modulations etc.), from 88khz sounds like a dream, so a global setting to set internal oversampling rate is can be very usefull 4 all of us. and limiting the very high notes (limit oscillator bandwith) like on microQ also needed to avoid counting xtreme high notes but ican live with that....
And iwant to notice also at 48khz the plug is not the best sounding(high freq domain aliasing if using xtreme settings on the modulations etc.), from 88khz sounds like a dream, so a global setting to set internal oversampling rate is can be very usefull 4 all of us. and limiting the very high notes (limit oscillator bandwith) like on microQ also needed to avoid counting xtreme high notes but ican live with that....
- KVRAF
- Topic Starter
- 12522 posts since 21 Mar, 2008 from Hannover, Germany
Hi,Tuth wrote:Hi Ingo!!!! My system is winxp sp3 32bit, same behaviour on all vsthosts, and dsnt matter vst2 or vst3 works as same aslo, all user arp patterns using the 1st part's setting (in the gui editable on all parts, but using the 1st's edits), the preset arps (1-15) and the arp pattern lenght setting works independently well on all parts.
And iwant to notice also at 48khz the plug is not the best sounding(high freq domain aliasing if using xtreme settings on the modulations etc.), from 88khz sounds like a dream, so a global setting to set internal oversampling rate is can be very usefull 4 all of us. and limiting the very high notes (limit oscillator bandwith) like on microQ also needed to avoid counting xtreme high notes but ican live with that....
if i understood you problem properly you try to use different user Arp patterns with different layers in Largo and Parts 2-4 use the same pattern as Part 1. Is this right?
Will try to check this.
Ingo
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
- Topic Starter
- 12522 posts since 21 Mar, 2008 from Hannover, Germany
I guess i got it but currently try to find a procedure to replicate and/or notice this easily.Tuth wrote:yes! pls set to "user" all the arp patterns, because factory patterns works well. and try edit.
Indeed no probems with the factory/preset patterns.
Ingo
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
- 23101 posts since 7 Jan, 2009 from Croatia
I can confirm user patterns not working for parts 2-4 - whatever accent/length/timing and step selection you select, it doesn't work - it takes on from part 1 arp.
- KVRAF
- 23101 posts since 7 Jan, 2009 from Croatia
Also I think I can confirm this too:
http://www.waldorf-music.info/kunena-en ... tor-broken
Both in Blofeld v1.22 and Largo.
http://www.waldorf-music.info/kunena-en ... tor-broken
Both in Blofeld v1.22 and Largo.
-
ChristopherMoyse ChristopherMoyse https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=58343
- KVRer
- 2 posts since 18 Feb, 2005
Using Sonar X3 64 under Windows 8.1 64, neither 64-bit VST3 1.5.2 RC1 or RC2 Largo respond to Pressure (channel aftertouch). However, 32-bit VST2 1.5.1 Largo in the same project with the same preset loaded does respond to Pressure. Does anyone know if this is a configuration issue or a bug?
- KVRAF
- 35268 posts since 14 Sep, 2002 from In teh net
Can't confirm that on Mac - the VST64 is responding to aftertouch for me - have you tried in any other Win hosts?ChristopherMoyse wrote:Using Sonar X3 64 under Windows 8.1 64, neither 64-bit VST3 1.5.2 RC1 or RC2 Largo respond to Pressure (channel aftertouch). However, 32-bit VST2 1.5.1 Largo in the same project with the same preset loaded does respond to Pressure. Does anyone know if this is a configuration issue or a bug?
- KVRAF
- Topic Starter
- 12522 posts since 21 Mar, 2008 from Hannover, Germany
Aftertouch/Pressure seems to work properly with VST2 64-bit in Cubase 7.5.20 64-bit on Windows 7 64-bit. Same with Live 9.1.3 64-bit.aMUSEd wrote:Can't confirm that on Mac - the VST64 is responding to aftertouch for me - have you tried in any other Win hosts?ChristopherMoyse wrote:Using Sonar X3 64 under Windows 8.1 64, neither 64-bit VST3 1.5.2 RC1 or RC2 Largo respond to Pressure (channel aftertouch). However, 32-bit VST2 1.5.1 Largo in the same project with the same preset loaded does respond to Pressure. Does anyone know if this is a configuration issue or a bug?
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
- 35268 posts since 14 Sep, 2002 from In teh net
OK hang on - there is something up with the AT response for the VST3 in Studio One 2.6 too - so this may be a VST3 issue (this on Mac)Ingonator wrote:Aftertouch/Pressure seems to work properly with VST2 64-bit in Cubase 7.5.20 64-bit on Windows 7 64-bit. Same with Live 9.1.3 64-bit.aMUSEd wrote:Can't confirm that on Mac - the VST64 is responding to aftertouch for me - have you tried in any other Win hosts?ChristopherMoyse wrote:Using Sonar X3 64 under Windows 8.1 64, neither 64-bit VST3 1.5.2 RC1 or RC2 Largo respond to Pressure (channel aftertouch). However, 32-bit VST2 1.5.1 Largo in the same project with the same preset loaded does respond to Pressure. Does anyone know if this is a configuration issue or a bug?
Tested now with the AU too - AT not working in that either! So it is only working properly with the VST2
- KVRAF
- Topic Starter
- 12522 posts since 21 Mar, 2008 from Hannover, Germany
Confirmed with 64-bit VST3 in Cubase 7.5.20 64-bit on Windows 7 64-bit.aMUSEd wrote:OK hang on - there is something up with the AT response for the VST3 in Studio One 2.6 too - so this may be a VST3 issue (this on Mac)Ingonator wrote:Aftertouch/Pressure seems to work properly with VST2 64-bit in Cubase 7.5.20 64-bit on Windows 7 64-bit. Same with Live 9.1.3 64-bit.aMUSEd wrote:Can't confirm that on Mac - the VST64 is responding to aftertouch for me - have you tried in any other Win hosts?ChristopherMoyse wrote:Using Sonar X3 64 under Windows 8.1 64, neither 64-bit VST3 1.5.2 RC1 or RC2 Largo respond to Pressure (channel aftertouch). However, 32-bit VST2 1.5.1 Largo in the same project with the same preset loaded does respond to Pressure. Does anyone know if this is a configuration issue or a bug?
Tested now with the AU too - AT not working in that either! So it is only working properly with the VST2
So on Windows it seems to work with VST2 but not with VST3.
Ingo
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
- 8074 posts since 16 Oct, 2006
Here's a video I sent to the beta list long ago, Logic X 64bit Largo, I have a few saved but here's 2 of them now that it seems Waldorf beta test is now a public thing.
- Crashed within seconds
- Preset Saved but was greyed out when trying to reload
- Init program issue
- LFO 2 bug assign it to pitch LFO2 works until you select LFO*Pressure to the pitch
See video (reported ages ago) on mac
http://www.screencast.com/users/rob_lee ... 3426201913
That clock delay might be fixed I'm not sure but here:
http://www.screencast.com/users/rob_lee ... b9db47791c
I'll sort more out at some point when I have time, maybe some are fixed (I think the FX Delay values) were fixed.
I was testing on 64bit AU back in may 2014 when these were reported but have no idea whether were fixed or not.
- Crashed within seconds
- Preset Saved but was greyed out when trying to reload
- Init program issue
- LFO 2 bug assign it to pitch LFO2 works until you select LFO*Pressure to the pitch
See video (reported ages ago) on mac
http://www.screencast.com/users/rob_lee ... 3426201913
That clock delay might be fixed I'm not sure but here:
http://www.screencast.com/users/rob_lee ... b9db47791c
I'll sort more out at some point when I have time, maybe some are fixed (I think the FX Delay values) were fixed.
I was testing on 64bit AU back in may 2014 when these were reported but have no idea whether were fixed or not.
- KVRAF
- Topic Starter
- 12522 posts since 21 Mar, 2008 from Hannover, Germany
edit
Last edited by Ingonator on Mon Jul 21, 2014 9:23 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
- 261 posts since 2 May, 2014
This is from Facebook, changelog for RC2:
- Timing problem on Mac/OSX solved
Does this mean that the arp sync problem should be solved?
It's still there tho, nothing has changed for me.
How do I know for sure I'm running RC2 btw? I deleted the RC1 plugin files before install, but I'd like to make sure reading it from somewhere.
- Timing problem on Mac/OSX solved
Does this mean that the arp sync problem should be solved?
It's still there tho, nothing has changed for me.
How do I know for sure I'm running RC2 btw? I deleted the RC1 plugin files before install, but I'd like to make sure reading it from somewhere.