VPS Avenger 2.4 [RELEASED - FAQ in OP]
-
- KVRian
- 906 posts since 25 Jan, 2014
I updated to 2.0.3 but V-Manager still says 1.8.6 and files in vst3, vst and AU folder still says 2.0.0. ....I guess 2.0.3 is installed but that should be corrected...
-
- KVRer
- 20 posts since 24 Sep, 2023
Fair question: M1 Max, 64GB, 4TB MBP / Monterey. I'm on the latest version of Avenger 1.8.6 arm64 (have 4 expansions currently), and it's pretty bad.noiseboyuk wrote: Thu Nov 30, 2023 9:19 am Anyone posting about CPU spikes - only worth posting if you not only say what your system is but also if you have tried 2.0.2, which has eliminated issues for some.
Haven't tried the update because I'm not giving them any more money until I am reasonably sure this has been solved.
-
- KVRAF
- 4720 posts since 25 Mar, 2016 from Seattle
That’s a good call! I should’ve done the same…remix68 wrote: Fri Dec 01, 2023 12:43 amFair question: M1 Max, 64GB, 4TB MBP / Monterey. I'm on the latest version of Avenger 1.8.6 arm64 (have 4 expansions currently), and it's pretty bad.noiseboyuk wrote: Thu Nov 30, 2023 9:19 am Anyone posting about CPU spikes - only worth posting if you not only say what your system is but also if you have tried 2.0.2, which has eliminated issues for some.
Haven't tried the update because I'm not giving them any more money until I am reasonably sure this has been solved.
The spikes on my 2023 Apple MacBook Pro, M3 Max running Sonoma, are really bad.
This needs fixing ASAP!
AVENGER 2.03
Last edited by simmo75 on Fri Dec 01, 2023 12:01 pm, edited 1 time in total.
-
- KVRAF
- 5057 posts since 27 Jul, 2004
He said thank you for the enormous effort and engagement for the updates and that we, the users of this amazing synth, appreciate this!enCiphered wrote: Thu Nov 30, 2023 10:58 pmDoes anyone know what He-Man wrote?Manuel, danke für die enorme Mühe und das Engagement für die Updates, wir, die Nutzer dieses großartigen Synthesizers, wissen das zu schätzen.
Germans among ourselves, you know!
-
- KVRAF
- Topic Starter
- 5913 posts since 25 Jan, 2007
But again - what Avenger version are you on?simmo75 wrote: Fri Dec 01, 2023 1:53 amThat’s a good call! I should’ve done the same…remix68 wrote: Fri Dec 01, 2023 12:43 amFair question: M1 Max, 64GB, 4TB MBP / Monterey. I'm on the latest version of Avenger 1.8.6 arm64 (have 4 expansions currently), and it's pretty bad.noiseboyuk wrote: Thu Nov 30, 2023 9:19 am Anyone posting about CPU spikes - only worth posting if you not only say what your system is but also if you have tried 2.0.2, which has eliminated issues for some.
Haven't tried the update because I'm not giving them any more money until I am reasonably sure this has been solved.
The spikes on my 2023 Apple MacBook Pro, M3 Max running Sonoma, are really bad.
This needs fixing ASAP!
http://www.guyrowland.co.uk
http://www.sound-on-screen.com
W11, Ryzen 7900, 64gb RAM, RME Babyface, 1050ti, PT 2024 Ultimate, Cubase Pro 14
Macbook Air M2 OSX 10.15
http://www.sound-on-screen.com
W11, Ryzen 7900, 64gb RAM, RME Babyface, 1050ti, PT 2024 Ultimate, Cubase Pro 14
Macbook Air M2 OSX 10.15
-
- KVRAF
- Topic Starter
- 5913 posts since 25 Jan, 2007
I'll add this to the FAQ as it is coming up 3 times on every page now, but you can check which version you are actually on by clicking the SYS tab in Avenger, and it's listed at the bottom.Jolaff wrote: Thu Nov 30, 2023 11:14 pm I updated to 2.0.3 but V-Manager still says 1.8.6 and files in vst3, vst and AU folder still says 2.0.0. ....I guess 2.0.3 is installed but that should be corrected...
http://www.guyrowland.co.uk
http://www.sound-on-screen.com
W11, Ryzen 7900, 64gb RAM, RME Babyface, 1050ti, PT 2024 Ultimate, Cubase Pro 14
Macbook Air M2 OSX 10.15
http://www.sound-on-screen.com
W11, Ryzen 7900, 64gb RAM, RME Babyface, 1050ti, PT 2024 Ultimate, Cubase Pro 14
Macbook Air M2 OSX 10.15
-
- KVRist
- 82 posts since 14 Dec, 2021
I am also on a 16 M1 Max MBP and also having cpu spikes and audio crackles, and I am not upgrading to Avenger 2 until there is a 100% confirmation these issues are fixed.remix68 wrote: Fri Dec 01, 2023 12:43 amFair question: M1 Max, 64GB, 4TB MBP / Monterey. I'm on the latest version of Avenger 1.8.6 arm64 (have 4 expansions currently), and it's pretty bad.noiseboyuk wrote: Thu Nov 30, 2023 9:19 am Anyone posting about CPU spikes - only worth posting if you not only say what your system is but also if you have tried 2.0.2, which has eliminated issues for some.
Haven't tried the update because I'm not giving them any more money until I am reasonably sure this has been solved.
Is the plugin now Native btw (so no Rosetta 2 layer)?
-
- KVRAF
- Topic Starter
- 5913 posts since 25 Jan, 2007
Yes
http://www.guyrowland.co.uk
http://www.sound-on-screen.com
W11, Ryzen 7900, 64gb RAM, RME Babyface, 1050ti, PT 2024 Ultimate, Cubase Pro 14
Macbook Air M2 OSX 10.15
http://www.sound-on-screen.com
W11, Ryzen 7900, 64gb RAM, RME Babyface, 1050ti, PT 2024 Ultimate, Cubase Pro 14
Macbook Air M2 OSX 10.15
-
- KVRist
- 82 posts since 14 Dec, 2021
Cool, that is good to hear.
Now I just need a confirmation that the CPU spikes and audio crackles are fixed on the M1 Max.
-
- KVRist
- 252 posts since 18 Jun, 2001 from UK and NY
Repeat post….Is there a way to use and edit factory/exp drum samples in an Osc module rather that a drum kit to allow deeper synthesis and editing. They don’t show up anywhere other than the drum editor. Thanks in advance and apologies if I missed something obvious.
-
- KVRAF
- Topic Starter
- 5913 posts since 25 Jan, 2007
No, pretty sure there's no way to do this (save of course rendering them out and re-importing them. There's a tonal drums section in the factory samples library, but that's about it otherwise.coldmachine wrote: Fri Dec 01, 2023 10:10 am Repeat post….Is there a way to use and edit factory/exp drum samples in an Osc module rather that a drum kit to allow deeper synthesis and editing. They don’t show up anywhere other than the drum editor. Thanks in advance and apologies if I missed something obvious.
http://www.guyrowland.co.uk
http://www.sound-on-screen.com
W11, Ryzen 7900, 64gb RAM, RME Babyface, 1050ti, PT 2024 Ultimate, Cubase Pro 14
Macbook Air M2 OSX 10.15
http://www.sound-on-screen.com
W11, Ryzen 7900, 64gb RAM, RME Babyface, 1050ti, PT 2024 Ultimate, Cubase Pro 14
Macbook Air M2 OSX 10.15
-
- KVRian
- 906 posts since 25 Jan, 2014
There is nothing about it on page 67 neither on page 66, can't tell for pages before but yeah ....that's a good idea to put it in the FAQ since this is the reason being of FAQ...noiseboyuk wrote: Fri Dec 01, 2023 8:21 amI'll add this to the FAQ as it is coming up 3 times on every page now, but you can check which version you are actually on by clicking the SYS tab in Avenger, and it's listed at the bottom.Jolaff wrote: Thu Nov 30, 2023 11:14 pm I updated to 2.0.3 but V-Manager still says 1.8.6 and files in vst3, vst and AU folder still says 2.0.0. ....I guess 2.0.3 is installed but that should be corrected...
- KVRist
- 145 posts since 6 May, 2005
You know you can mark any text in any language and with right click you can translate it to your default language?enCiphered wrote: Thu Nov 30, 2023 10:58 pmDoes anyone know what He-Man wrote?Manuel, danke für die enorme Mühe und das Engagement für die Updates, wir, die Nutzer dieses großartigen Synthesizers, wissen das zu schätzen.
- KVRist
- 145 posts since 6 May, 2005
maybe this will help you too, i had the problem that all my content was gone (incl third party and own presets):Jolaff wrote: Thu Nov 30, 2023 11:14 pm I updated to 2.0.3 but V-Manager still says 1.8.6 and files in vst3, vst and AU folder still says 2.0.0. ....I guess 2.0.3 is installed but that should be corrected...
chrisg wrote: Thu Nov 30, 2023 5:38 pm
I found the solution: the installation also created a new expansions folder in the VENGEANCE folder. But in this there is also still the V1 folder, ALSO with an expansion folder - in which all my expansions are. I copied those (for safety reasons "copy") into the new expansions folder - now everything is fine.
Check your vengeance folder if there are 2 expansions folders a new and an old one or if a second Vengeance folder was created. Could be that is the problem.
