I did install Avenger update ver.1.8 over ver 1.7. I was using a dongle with codemeter protection and everything was fine until i installed version 1.8. Vst2 was blacklisted and Vst3 was not recognized in Cubase 11. After contacting support, Rene suggested to install/repair VC-redist. I did that, but still the same. Then version 1.8.2 came out and i tried again my luck but still nothing. So i did a complete uninstall and a new installation. No luck again. Version 1.8.2 Vst3 is recognized from Cubase and Vst2 is NOT blacklisted but when i try to load the plugin it says: "Cannot create plugin instance". I did format my drive and installed new Windows 10 and still the same. Everything is checked about plugins in folders and YES they are correct installed and in the correct place. Drivers updated etc
Do you guys think i have a hardware compatibility problem?
My system specs:
CPU: AMD phenom x4 955 Black edition
Graphic Card: AMD Radeon R7 250x
Windows 10 Pro 21H1 on SSD drive.

Please help anyone. Do i miss anything? Rene at the support is not fast enough

 

you do not have a hardware compatibility problem, because no special hardware is required to use Avenger. only the same hardware as any other normal VST/VST3 plugin. your dongle device works with other things also, right? I'd install it cracked anyway, but that's just me.

Keep in mind, the only thing about your setup/install which has changed is their program's protection scheme and a build number. Did you try downgrading back to ver 1.7?

did you read any of this thread? https://www.kvraudio.com/forum/viewtopic.php?t=467127&start=11805. . you know it is ugly when your customers beg for ilok.

 

Last edited: Dec 31, 2021

I did downgrade and it worked like before. The weird thing is: I kept the "VPS Avenger.plugin" file from version 1.7 and when i installed version 1.8.2 i replaced ONLY this file. Plugin in Cubase 11 is working as it should BUT it says that i have 8 days left with my licence. This means that the "VPS Avenger.plugin" from 1.8.2 version is not recognizing my new licence.
May i ask you in Windows where the licence file has to be? In my case when i download the keyfile within V-manager is in: C:\ProgramData\Vengeance\VPS Avenger. I tried to move the file eveywhere but it doesn't work.

 

I just uninstalled Codemeter, uninstalled avenger and installed 1.8 / 1.8.2 through v-manager as stated from vengeance. Opened the vst, logged into my account through the vst. Works like a charm. On Cubase 11 pro

 

I really wonder why they moved on from Codemeter tbh, given how mental and hysterical they have been about piracy. The reason they gave was something with compatibility of the framework, when that doesn't seem to be true (judging from other people's comments).

 

The reason for the change was the compatibility with Mac M1.

1.8.0 changelog
- Avenger is now working on Apple M1 native
- switched copy protection from Codemeter back to keyfile

 

Yeah that's what I meant. I remember reading a comment somewhere that claimed that Codemeter was compatible with Apple M1, so the reason they gave didn't make any sense to me.

 

Yes , codemeter is cracked, even though WIBU is still claiming they are uncrackable, and Vengeance moved to them just because that, they changed protection and imagine when, in vey same time Reason got released. So because of that, they didn't want to be loser in their own game, again... So they, did that move before R2R make remarks on their decisions about WIBU, and what not... It is a physical game here about... WIBU is smashed by R2R, now who will last longer R2R or Music devs using WIBU.... Someone has to drop their gloves, ant R2R seems to be very persistent in that game, to force devs not to use shitey codemeter for audio apps... MAAT was the first one dropped WIBU...

 

Update for my case:
Support did connect to my PC with TeamViewer and they found that my CPU is not anymore compatible. Avenger 1.8 and upwards needs CPU's SSE 4 and my CPU (AMD Phenom x4 955) is SSE 3 I think. Anyway they will try to find a solution. At this point I have to mention the support (Andre Keilwert) was super nice, friendly and with a lot patience to find out the problem. Thank you Andre!

 

i wanted to get avenger so i thought i should look whether the new version is compatible and since i have
AMD Ryzen 7 1800X Eight-Core Processor ,all AMD Ryzen Family series support SSE 4.1 and above

AMD processors that support SSE4.1 or higher

- "Bulldozer" family
- FX-4100 series
- FX-6100 series
- FX-8100 series
- Opteron 3200 series
- Opteron 4200 series
- Opteron 6200 series

- "Piledriver" Family
- FX-4300 series
- FX-6300 series
- FX-8300 series
- Opteron 3300 series
- Opteron 4300 series
- Opteron 6300 series

- "Steamroller" / "Excavator" Family
- all Althon X4 series

- "Ryzen" family
- all Ryzen series

AMD Processors that do not support SSE4.1 or higher

- "Sempron" family
- "Athlon II" family
- "Phenom II" family
- "Athlon" family
- "Phenom" family

original source
https://www.ubisoft.com/en-us/help/...le/amd-processors-and-sse4x-support/000064198

 

When i saw the non-standard methods employed during setup of early versions i wondered if this would be a problematic vsti.

Creativity at its most annoying

But looks like this is maybe just updating hardware for better features/performance.

What are those better features / performance?
Is it worth the update to change CPU / maybe motherboard?
Changelog should clear that up...

 

www.vengeance-sound.com/plugins/plChangelog.php?sub=Vengeance Producer Suite Avenger

 

Vengeance Producer Suite - Avenger / Changelog

1.8.2 changelog
- fixed VST3 error where Pitch-Bend did change after a preset was changed ( Cubase 11 )
- fixed tuning error when a chord-preset was selected in the OSC-voicing tab.
- fixed issue where a negative arp-pattern index was possible that may have caused a crash.
- fixed an issue in the chord voice replacement where a note might be assigned wrong to a voice


1.8.1 changelog
- added "Download Keyfile" popup when Avenger tries to load an expansion without the license in the keyfile to simplify the activation process.
- fixed error where an osc my play one note below its keyzone
- fixed issue on IntelMACs where the ImpulseFX was not working correct.
- possible fix for a rare crash on MACOS during load of Avenger
- changed codebase to be compatible with older-non-AVX processors. Minimum requirement changed to SSE4.1.
- WIN: added VisualC redistributeable package to installer.
- keyfile drag n drop should work correct now.
- fixed: switching LFO from Global to per-voice trigger did sometimes not work as expected


1.8.0 changelog
- Avenger is now working on Apple M1 native
- switched copy protection from Codemeter back to keyfile
- added: when preset search is visible, the prev/next button will cycle through the search results instead of loading the next preset from the "normal" expansion list
- added "FAVORITE" icon to preset search to toggle Fav's during search
- added detection for some specific chord ( min7-3, maj7-3 )
- added ARP triggered incremental mod source
- fixed: fx Phaser does not move when spread parameter is modulated
- fixed: arp chord detections hangs on last chord until a full chord is triggered again (happened on specific circumstances)
- FX impulse: fixed problem where textedit did not update the fx
- fixed: osc display did display the wrong start offset in specific circumstances
- fixed a crash: when changing the legato mode on the pitch tab may try to retrigger also inactive oscs that causes a crash on specific circumstances
- fixed a possible crash in pitch-module preset load
-fixed issue with loop playback in multi-loop module in specific circumstances
- fixed midi note hang in specific circumstances
- fixed: drumkit triggers modenvelope, even if osc-only mode is used as trigger for the mod-envelope
- fixed an OpenGL issue that deleted Textures from other application when closing Avenger's GUI
- fixed macOS: drag n drop onto Wavetable/Resampler sample display is now working as expected
- fixed a possible bug where the Avenger completely muted using sample stacker
- fixed a rare crash when loading presets while the ARP editor was visible

 

That's the reason, Codemeter won't support Apple Silicon

I would keep mailing, I am sure they will sort it out
[email protected]

 

Last edited: Jan 10, 2022

Rene is on holidays and he will come back on Monday. Andre told me we will find a solution. So there is nothing else left except waiting