UVI Falcon - v4 = 2026 released - rumors, ads, praise, kindergarden, auto-sampling and off-topic inside!

[c_voltage]

I have never had problems with ilok licenses on Windows (win7 x64), although I have heard that some people have something to disappear (then appeared back) about licenses, but strange i never encountered this. In system installed dozens of ilok based plugins (including blackhole and relayer and falcon).

[padillac]

Can you remove the Falcon license and re-add it?

[TexLoco5]

I've found one guy that claims to have found a work around that involves deactivating the license ... rescanning ... and then reactivating the license ... but he is also getting a recurrence of the problem depending on how the rescan is done ... rescan all plugin's or rescan for new plugins only. I might get desperate and try it ... but for now I think I'll hang back and see what UVI has to say.

One question though ... when using the iLok License Manager ... when you deactivate a license ... and then reactivate it (on the same hardware) ... do you loose one of your total allowable activation's?

Thanks!

KenB

[tonedef71]

One question though ... when using the iLok License Manager ... when you deactivate a license ... and then reactivate it (on the same hardware) ... do you loose one of your total allowable activation's?

No you will not lose one of your activations by deactivating and reactivating on the same PC.

Sometimes a Windows update may cause your PC to no longer be recognized as the machine that you activated all of your iLok soft licenses with because iLok License Manager sees your PC with a new system ID code. Should that ever happen to you, you can try using Windows System Restore to go back to the state of your PC before the Windows update, go into iLok License Manager and deactivate every license, and finally undo the System Restore to return the PC back to the state it originally was after Windows update; you would then be able to reactivate all of your soft iLok licenses to your PC with its new system ID code. Hopefully, that problem never happens to you.

[Sampleconstruct]

This iLok issue is not UVI-related, it's happening across the board, e.g. with the new Zynaptiq release and other things too, so everyone hold back and do not install anything iLok-related until they fix this thing.

[lnikj]

I've started a new thread on the iLok problem warning people: viewtopic.php?p=6535293

[wasi]

It is the sacred duty of all iLok-free musicians to resist iLok.

No plugin is good enough that it's worth being randomly locked out of your work because of some glitch in their allegedly 'fool proof' system. Besides, a DRM-scheme that can't reliably handle the user patching OS vulnerabilities is itself a vulnerability.

iLok is the only DRM-scheme I've consistently had problems with every couple of weeks. This latest fits the pattern. I don't even give a shit at this point what hoops they want me to jump through to get this to work again this time.

f**k iLok. I can't believe I was so weak and caved.

[Ingonator]

@Simon

Nope ... updating the iLok software didn't work ...

I use the iLok License Manager for UVI Falcon, UVI Relayer and Eventide Blackhole

Previous iLok version was 3.0.2 ... Falcon quit working, Relayer was working, didn't check Blackhole.

I updated to iLok version 3.0.3 ... Falcon and Blackhole aren't working (same error message) but Relayer is.

Haven't used any of those programs for about a week ... only change to my system was a Windows 10 update. Wonder if something was broken as a result.

I am using Falcon v1.1.4 on Windows 10 64-bit and iLok version 3.0.1 (not udated this yet) and have no problems with UVI Falcon, UVI Thorus, Lexicon MXR Native and Pro Tools 12 so far. All licenses are on my iLok 2 key.
At the moment due to what was posted here i somehow hesitate to update iLok to v 3.0.3 but i do not know if this would cause problems if i do so.

It also does not seem to be sure if this is a general problem or only specific for certain Falcon/ilLok users.

[lnikj]

@Simon

Nope ... updating the iLok software didn't work ...

I use the iLok License Manager for UVI Falcon, UVI Relayer and Eventide Blackhole

Previous iLok version was 3.0.2 ... Falcon quit working, Relayer was working, didn't check Blackhole.

I updated to iLok version 3.0.3 ... Falcon and Blackhole aren't working (same error message) but Relayer is.

Haven't used any of those programs for about a week ... only change to my system was a Windows 10 update. Wonder if something was broken as a result.

I am using Falcon v1.1.4 on Windows 10 64-bit and iLok version 3.0.1 (not udated this yet) and have no problems with UVI Falcon, UVI Thorus, Lexicon MXR Native and Pro Tools 12 so far. All licenses are on my iLok 2 key.
At the moment due to what was posted here i somehow hesitate to update iLok to v 3.0.3 but i do not know if this would cause problems if i do so.

It also does not seem to be sure if this is a general problem or only specific for certain Falcon/ilLok users.

At the moment it looks possible that is only soft (HD) iLok users that are affected, and so far it has only been seen when a new iLok authorised software installation occurs.

[TexLoco5]

As far as I know this only is a problem with the software version of the iLok License Manager. I'm reading reports from people that use a dongle and they're sayin' they don't have a problem.

I thought tonedef71 was onto something regarding mismatched system ID's so I checked mine ... but they all match.

KenB

[the3ug3reeder]

something completely different...
i'm still struggling to get falcon to react properly to OSC.
basically, i can get it to work on the top level... for example:
"/uvi/Gain 1" (1 is a variable) works to control the gain of the default multi... i copied and pasted this path directly out of the falcon interface.

for some reason, i can't seem to get falcon reacting to OSC on anything lower than the top most level... for example:
"/uvi/Part 0/Gain 1" (1 is a variable) does NOT work to control the gain of the the first part in my multi... i copied and pasted this path directly out of the falcon interface.

i've tried all sorts of variations.

is this a BUG?

[TexLoco5]

I received a reply from iLok to my support ticket. They recommended the following ... this is for Windows:

1. Go to Services > Right click PACE License Services > choose Stop to turn the service off

2. Go to Program Data\PACE\Eden > delete or remove all .sbd files

3. Go to Services > Right click PACE License Services > choose Start to turn the service on

I did these 3 steps and then rebooted.

Next I clicked on an iLok protected item that was previously blocked and a window popped up that was titled Updating License Storage.

After that all of my iLok protected items were working.

None of my license uses were incremented as a result of the process.

BINGO!

KenB

[tonedef71]

I received a reply from iLok to my support ticket. They recommended the following ... this is for Windows:

1. Go to Services > Right click PACE License Services > choose Stop to turn the service off

2. Go to Program Data\PACE\Eden > delete or remove all .sbd files

3. Go to Services > Right click PACE License Services > choose Start to turn the service on

I did these 3 steps and then rebooted.

Next I clicked on an iLok protected item that was previously blocked and a window popped up that was titled Updating License Storage.

After that all of my iLok protected items were working.

None of my license uses were incremented as a result of the process.

BINGO!

KenB

This is the standard remedy that iLok Support will always walk you through when there is an iLok soft authorization problem in Windows: shut down the Pace service in Windows (to remove the lock on the Eden database); delete the "Eden" database files in the Program Data folder because any one of them may be corrupted; restart the Pace service which will then connect to the iLok Pace servers running in the cloud and force a rebuild of the "Eden" database.

I am glad to hear that the standard remedy corrects this latest issue. Unfortunately, there are other Pace soft authorization issues that happen on Windows that this standard remedy does not correct.

[TexLoco5]

@tonedef71

Well ... all I know is ... I'm selfishly up and running now ... no license problems ... and after several reboots everything is working fine. Fingers crossed though!

KenB

[mdsp]

something completely different...
i'm still struggling to get falcon to react properly to OSC.
basically, i can get it to work on the top level... for example:
"/uvi/Gain 1" (1 is a variable) works to control the gain of the default multi... i copied and pasted this path directly out of the falcon interface.

for some reason, i can't seem to get falcon reacting to OSC on anything lower than the top most level... for example:
"/uvi/Part 0/Gain 1" (1 is a variable) does NOT work to control the gain of the the first part in my multi... i copied and pasted this path directly out of the falcon interface.

i've tried all sorts of variations.

is this a BUG?

If you are using Max () make sure to quote the OSC String like that:

Code: Select all

"/uvi/Part 0/Gain" $1

to avoid Max thinking the address is '"/uvi/Part" followed by '0/Gain' and '1'

Here is a simple working patch that I juste tested:

Code: Select all

----------begin_max5_patcher----------
411.3ocqSsrSCCCD7bxWg0JNFnwIskJ9A3J2onJmjkViRrircJAg5+NwOBTf
BMBwEa4w6N6ryZ+ZbDTH6QMPtgbOIJ503nHGjEHJbNBZX8k0LsKL3wZonqAR
7W8nT0vL1KVFPZYlxcbw1MJrz3INK+5qRSHT5B61hT6ZV1UojGB4LPnryTiF
WIxBnMbAuYnTCP1TdWKifz2AaYJVCZP0FTvJpQWJg67DadoE8hAfDBTvDagi
KOWLVcZ.jW4ZWYwSWtXra0lW7jCfE3PbrcIYhNWCp0rs3HYFr24OvZXV2d9r
6XJCIc1sLtXMPtfBm2PmG70UmwQo+nWbZOH66dP9+iGHvmGX6aVPWUqFEUjZ
YIqdmTaHzr74KlfErh5ch4mwBRm3rl968oicnlK95mFmDs3et40xNU4naGdK
Q9PiUn1vELCWJNJl7OEyNdUEJNtGp3Z6qbmnSO4PXppIeBpg9GUi2pXss6Qk
NPoSHCuHdRprGuNI1+O2ezwHnv87w38HL0vz2LL56T9IR+x4fOUYEpDcb2vL
1V4Cwuwg7yQk
-----------end_max5_patcher-----------