Vengeance Producer Suite - AVENGER - 1.8.5 the main thread

[frz]

Tried not importing, but manually placing the license file where it should be residing? Download a new license, the name sound be AVGR_SYS_blabla.license, rename that file to simply AVGR.license and place it manually in the corresponding folder on the hard drive. Maybe this way you'll get over the nag screen.

Tried that way also but it doesn't work either

[e-musician]

Hi,
I'm having trouble getting my EDM1 expansion to work after installing the 1.2.3 update. Is there a separate key file for expansions?

If I follow the instructions that appear in the plugin GUI, only the plugin key file shows up and when I select it a dialog pops up telling me that the installation was successful, but this dialog does not close when I click ok, and the expansion remains locked.

Sorry if this has been explained before.

Morten


My system:
Win 10 Pro 64bit
Cubase 9 Pro

Somewhere on your computer there is a file named AVGR.license. I’m on mac, so I can’t point the location. Find it and delete it and import the fresh key again

I have the same problem and deleting avgr.license and reimporting the file didn't help. It is not possible to click "ok" on the popup that appears as if it was on another layer, in fact it is possible to click the buttons of the popup underneath. Very weird.

1.2.4 here.

Hi, this is what you must do:

Log in to your account at VPS, then REGISTER your EBM1 expansion (yes, it has got a serial number of its own, check the invoice you got when you bought it). After Registration, your expansion will be listed under "My products".

Enter your SYSTEM-ID, then download the KEY file again. Import this new KEY file into Avenger.

Now your expansion will be unlocked.

In case you don't know what your SYSTEM-ID is: Remove that old AVGR.license file before opening Avenger. On opening the synth will tell you that there is no license file AND give you the SYSTEM-ID to be entered at VPS.

[sircuit]

Hi,
I'm having trouble getting my EDM1 expansion to work after installing the 1.2.3 update. Is there a separate key file for expansions?

If I follow the instructions that appear in the plugin GUI, only the plugin key file shows up and when I select it a dialog pops up telling me that the installation was successful, but this dialog does not close when I click ok, and the expansion remains locked.

Sorry if this has been explained before.

Morten


My system:
Win 10 Pro 64bit
Cubase 9 Pro

Somewhere on your computer there is a file named AVGR.license. I’m on mac, so I can’t point the location. Find it and delete it and import the fresh key again

I have the same problem and deleting avgr.license and reimporting the file didn't help. It is not possible to click "ok" on the popup that appears as if it was on another layer, in fact it is possible to click the buttons of the popup underneath. Very weird.

1.2.4 here.

Hi, this is what you must do:

Log in to your account at VPS, then REGISTER your EBM1 expansion (yes, it has got a serial number of its own, check the invoice you got when you bought it). After Registration, your expansion will be listed under "My products".

THEN download the KEY file again Don't forget to enter your SYSTEM-ID before. Import this new KEY file into Avenger.

Now your expansion will be unlocked.

Expansion was previously working, also is on his hard drive so he clearly made these steps (also can't get a key without inputting the System ID...) ^

[e-musician]

I have just added something about the SYSTEM-ID to my post.

For previous yersions of Avenger it was not necessary to register expansions. Everything worked fine without registration. They have just introduced the feature of system-ID locked licenses with version 1.2.3. So he needs to go through the procedure described by me above. I am pretty sure that he has not registered his EBM1 XP so far.

I think Granular XP was the first expansion to make use of the new system.

[invisiblesun]

Turned out I hadn't registered the expansion to my account. So I did and went through the procedure again as you described. And now everything works fine!
Thanks for helping me out!

Morten

[KenjiDeVries]

With the newest update again some of my presets don't sound the same anymore. This happened once already with an earlier update where I then had to step through every preset and fix it. Also some of the patches randomly consume more cpu than u-he Diva in divine mode. This came with the latest update.

After getting confronted with its bugs nearly every update, the sudden change with the license system, the problems with user accounts on the web page and after reading many posts in this thread I really get the impression Avenger should not have been released that soon. Please please please try to focus on bug fixing first before adding new features and fancy expansions.

ps: Sorry for ranting but unfortunately sometimes it still feels like an open beta version. This is the first synth I've experienced these problems.

[msvs]

I do not know what you are talking about. Please send us a preset before and after the update and show me what exactly sounds different now. We would never do an update/new feature which makes presets sound slightly different on purpose btw.
the id-license system works fine so far, nearly all problems you read were people, who had not activated their expansions in their account yet.

[Caine123]

of course i write here also some stuff but guys learn to send support tickets..... otherwise devs/companies cannot work well sorted.

[godly]

I do not know what you are talking about. Please send us a preset before and after the update and show me what exactly sounds different now. We would never do an update/new feature which makes presets sound slightly different on purpose btw.
the id-license system works fine so far, nearly all problems you read were people, who had not activated their expansions in their account yet.

Well... the license id system isn't perfect yet
Last night I searched the whole evening because my Avenger plugin suddenly was gone in Reaper...
I reinstalled Reaper several ways, then it was back, then not,...
Got me going crazy after hours of swapping files and replacing installs.
Finally I found out !
Seems that there were some previous Avenger dll files on my server and my reaper also reads plugins from there !
Removing ALL of the plugins, so only 1 instance was active solved the problem.
Big relief... But a whole (precious) evening of searching and stress...
I don't know any other plugins who has this problem and mostly I have them on several places running (my computer and server with backup and library)
Do you guys issue the same in your daw? Or is it only reaper?

I've send Rene the issue.

[msvs]

well if I understood right, there are old Avenger.dll files on your computer which are of course incompatible with the new licensing system hence there is no other way than using only the new dll and not try to open the old files. We cant delete them from your computer

[Warehouseparty]

Of course you are running into trouble having multiple dll of a plugin if it switches type of protection.

Can't you tell Reaper at which locations it should look for plugins? Or are you running multiple versions of Avenger? In that case there shouldn't be any problems if you are using multiple patch libraries as well. Any other situation is no failure in design.

Edit: msvs was faster than me.

[godly]

well if I understood right, there are old Avenger.dll files on your computer which are of course incompatible with the new licensing system hence there is no other way than using only the new dll and not try to open the old files. We cant delete them from your computer

Yes correct, seems that the plugin crashes on the old versions that were located on my server and active in Reaper also Fixed and updated Rene.

Yes I can tell Reaper where to look, but it has to look on my PC and my NAS for backup and sync reasons.

[DigiPRO]

Not sure if this has been reported by others, by every time I download an Avenger update file - Panda Protection Antivirus marks it as a malicious file and puts it in the quarantine.

It doesn't work to manually exclude it as every new update file has file version in the name, so every update requires me to do manually exclude it. Sorry if this has already been addressed.

[msvs]

what can we do if they regognize a false positive?

[DigiPRO]

what can we do if they regognize a false positive?

Not sure, maybe contact the Panda Protection developers to find out which string is giving the false positive output?