Waldorf software - new licensing system

VST, AU, AAX, CLAP, etc. Plugin Virtual Instruments Discussion
Post Reply New Topic
RELATED
PRODUCTS

Post

There still seems to be a little confusion about the new protection. I just posted this in another thread:
Ingonator wrote:
chk071 wrote: Dunno if you read it, but, Waldorf switched from eLicenser to C/R copy protection recently for their soft synths.
This is not fully correct. The new protection from Waldorf is a simple serial number like in Waldorf Edition 2.
A while ago i already mentioned ín the dedicated thread that this is no C/R.
The restriction that you are allowed to use a license on 3 computers at once is a restrictin of the EULA, not a "technical" restriction. No developer in the EULA wil alow to use a product on an unlimited amount of computers.

Anyway products have to be registerted to a "MyWaldorf" account to get the serial and a download link for the product. The account also offers an "eLicenser conversion" to convert an eLicenser code (the origianl code, not a license stored on an USB eLicenser) to the new serial (and add the product to "My Software" at the account).
Another way to receive serials is as a "coupon code" that after using "Redeem coupon code" in the account also has the product registered. This is also what you should receive when buying a product now.
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

Post

Ig I got Largo from the NI sale, do I have to ask NI and waldorf if I want a license transfer?
dedication to flying

Post

rod_zero wrote:Ig I got Largo from the NI sale, do I have to ask NI and waldorf if I want a license transfer?
AFAIK you could not register Largo to your NI account so most likely you would have to ask the Waldorf support.
Between Friday this week and Monday next week there is Easter so last day to reach support this week should be tomorrow and then again starting at Tuesday next week.
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

Post

I bought Largo last weekend, wish I bought Serum instead cause I have yet to receive the serial and there is no response from Waldorf support. No wonder they went under before if this is how they treat their customers.
"People are stupid" Gegard Mousasi.

Post

shroom81 wrote:I bought Largo last weekend, wish I bought Serum instead cause I have yet to receive the serial and there is no response from Waldorf support. No wonder they went under before if this is how they treat their customers.
Musikmesse was last week- give them time. They're more than likely pretty far behind as that tends to be an all hands on deck affair.

ew
A spectral heretic...

Post

shroom81 wrote:I bought Largo last weekend, wish I bought Serum instead cause I have yet to receive the serial and there is no response from Waldorf support. No wonder they went under before if this is how they treat their customers.
Perhaps need was better buy it through jrr instead official Waldorf site, i bought Large too (a week ago) and got serial code from jrr after 3 hours after pay.

Post

Hi,

since a while from time to time i work for Waldorf as a "Beta Forum Manager" where besides doing tests myself i also receive bug reports from other Beta testers.
Concerning testing myself for the setup you could have a look at my signature.

In the near future we plan to do new updates for the Waldorf plugins so if you got bug reports you might also post them here even if Waldorf normally prefers that bugs are reported to the official support.

I am not responsible for questions about purchases, sales or licenses so about that pleae ask at the official support.

If you want to report bugs here please consider this:
- please use the latest installers with the new serial protection (the old eLicenser versions will not be updated)
- please be sure to do a "clean" installation, not just overwrite the old installation (especially if the eLicenser version was installed before). Also delete remaining files manually where necessary (except your user patches)
- Largo and PPG Wave 3.V have seperate deinstallers for all plugin fromats which are found at the "Waldorf" sub-folder in the Start menu at Windows 10 (and also Windows 7)
- please try to give informations about the plugin format, OS (with version especiallly for OSX) and host (with version)
- pleae try to give a short step by step procedure if possible (opposing to e.g. a very long video where only a small part is really related to the bug...)
- If possible also test in a differnt host and/or plugin format to see if you could confirm this there


Best wishes,
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

Post

Hey Ingo,

i reported the issue already once, to you, and also to Waldorf, but, there was no fix for it.

Reproducable as following:

- Install a Waldorf plugin, in my case Largo, on Windows (doesn't matter which version, from 7 upwards), with a normal user account. Largo needs administration rights to install. Once it is installed, it has installed a folder in the admin's user AppData/Roaming folder named "Waldorf", with another folder in it, named "Largo", which contains the manuals.
- Start your DAW with your normal user account, without admin rights. Largo crashes the DAW, because it expects the folder mentioned above in the user's AppData/Roaming folder.
- The solution is to manually copy said folder into the user's AppData/Roaming folder, or, to execute your DAW as the admin user, but, of course, copying said folder manually is the better solution, if you execute your DAW the "normal" way (with your normal user rights), in the typical case anyway.

I'd really, really recommend to forward that to Waldorf again, it is really a critical bug, which will affect all users, who are not logged into Windows with admin user rights, which maybe won't be the majority, but, surely a lot of people. I don't know why Waldorf didn't fix that, in several versions of Largo now. It's a really easy fix, surely. They just have to copy the files for all users, not just the installing user (which is always the admin user).

BTW, this issue occured to me on - Windows 7, Windows 8, and Windows 10, all 64-bit. So, doesn't really matter which version, it should be reproducable on all systems which use UAC (from Win 7/Vista upwards).

Post

Concerning administrator rights i recently found a possible problem that is related to the new serial based copy protection.
During the first time starting the new plugin version where you have to enter the serial you might have to start the host with administrator rights (which for Live 9 somehow i always did automatically). If not it could happen that the plugin will not keep the authorizaion and asks for it again when re-starting the host or re-loading a project.
If you use both the VST2 and VST3 plugins you might have to do the authorization process (= enter the username which is the e-maik and the serial) for both plugin formats.

One important thing after entering the username and serial (except maybe for Nave...) it seems to be to use the ENTER key at your computer keyboard for confirmation. Usually you have to re-start the plugin to remove the demo label at the GUI (e.g. by removing and re-inserting the plugin).

Using the hints mentioned above currently here at Windows 10 64-bit the VST2, VST3 and AAX plugins do work without being asked for entering the license again. This is true for all Waldorf plugins.
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

Post

Alright. Didn't happen here TBH. worked fine, when i executed the DAW with normal user rights. VST3 works fine too that way, i just checked.

Post

Ingo, pay attention to this Largo issue please (if did not noticed yet) http://www.kvraudio.com/forum/viewtopic ... 0#p6709481

Post

c_voltage wrote:Ingo, pay attention to this Largo issue please (if did not noticed yet) http://www.kvraudio.com/forum/viewtopic ... 0#p6709481
Yesterday i found this thread in the Bitwig sub-forum:
http://www.kvraudio.com/forum/viewtopic ... 9&t=482415

I will have a look ASAP.
I alraedy had Bitwig 1.3.16 and installed the demo of v2.0 yesterday which also seems to work when v1.3.16 is already installed. Hopefully next week i could finally also get the full version of v2.0.

c_voltage wrote:Ingo, pay attention to this Largo issue please (if did not noticed yet) http://www.kvraudio.com/forum/viewtopic ... 0#p6709481
Like the one mentioned above I'll have a look ASAP, maybe today.
Usually i try to check in differnt oplugin formats and hosts as some bugs are specific to a certain format and/or host or even a specific OS version.
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

Post

c_voltage wrote:Ingo, pay attention to this Largo issue please (if did not noticed yet) http://www.kvraudio.com/forum/viewtopic ... 0#p6709481
Everglide wrote:Thanks for the heads up, I'll try it out when I can!

Has anyone notice this small anomaly;

1. add Detune to your patch
2. set Detune back to 0 and adjust the Spread and Voices to taste
3. save the patch
4. open the project and the patch loses the Stereo Spread, its now forced Mono

Before you say you need to add at least 001 Detune to keep the width.
What if you don't want the Detune movement?
What if I'd like to keep the static voice spread for sound design?

Surely Waldorf could add an option like Stereo or Static button next the Mono.
I just checked this now and my first thought it is quite strange to use the Unison Spread without any Unison detune. Personally i never used it that way. For just having a stereo spread for played notes in Largo it is also possible to modulate the panning with e.g. with the "Voice" mod sources (for example "Voice %4").

Indpendent of this i am currently checking the Unison after re-oading a host project, also with higher detune amounts and in different hosts and plugin formats. Not finished with tests yet. If i find something i will ask responsible persons at Waldorf about it soon.
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

Post

chk071 wrote:The solution is to manually copy said folder into the user's AppData/Roaming folder

They just have to copy the files for all users, not just the installing user (which is always the admin user).
If you want the same set of application data to be accessible by all users of the PC then you would traditionally put it in C:\ProgramData. That way you dont have to make a duplicate copy of the data for every user working on the machine, plus you also ensure that every user is working with the same set.


Note: On XP and earlier this directory actually used to be in a location named 'All Users', namely

C:\Documents and Settings\All Users\Application Data

More info here, in case youre interested. (See 3rd item, 'commonappdata'.)

Post

Ingonator wrote:
c_voltage wrote:Ingo, pay attention to this Largo issue please (if did not noticed yet) http://www.kvraudio.com/forum/viewtopic ... 0#p6709481
Everglide wrote:Thanks for the heads up, I'll try it out when I can!

Has anyone notice this small anomaly;

1. add Detune to your patch
2. set Detune back to 0 and adjust the Spread and Voices to taste
3. save the patch
4. open the project and the patch loses the Stereo Spread, its now forced Mono

Before you say you need to add at least 001 Detune to keep the width.
What if you don't want the Detune movement?
What if I'd like to keep the static voice spread for sound design?

Surely Waldorf could add an option like Stereo or Static button next the Mono.
I just checked this now and my first thought it is quite strange to use the Unison Spread without any Unison detune. Personally i never used it that way.
Ingo, well, unison sounds a bit more "cold" (that desirable sometimes) with zero detune, and vice versa - a micro-movement\modulate begin noticeable with detune level even 001.

For secondly - pay attention that i already wrote in that topic - this issue reproduce only in saved daw project, and not reproduce (ie detune setting stay in zero properly) if you import your saved preset through internal Largo browser. Thus, the same action with such difference obviously an small bug. (Or by other words - not a some planned feature)

Post Reply

Return to “Instruments”