New Softube Central

[aMUSEd]

I have just installed a new plugin with it but unlike the old version it doesn't give any option as to activation, and instead of putting the licence on my iLok has put it on the hard drive. Does anyone know how to make it just put licenses on the iLok? - in the old version you had options.

[lfm]

And if you login to iLok account, does it not show up there?
- thinking you move license that way

Waves is using this kind of approach....

[aMUSEd]

Yeah I did that but it would be easier if the app still allowed the option, I don't know why they removed it.

[PAK]

I have just installed a new plugin with it but unlike the old version it doesn't give any option as to activation, and instead of putting the licence on my iLok has put it on the hard drive. Does anyone know how to make it just put licenses on the iLok? - in the old version you had options.

Green circle, top right, has two options. iLok Locations, which shows the locations it sees that it can install to, and Settings / Auto Activate (which defaults to enabled, and will install licenses on your HD even if you have them on a key.)

Due to some strangeness with the metal iLok 3 dongle on Mac OS (sometimes the key would actually get hot to the touch, whatever the hell it was doing) I gave in and just use the HD now.

BTW: All these web based bloatware updater apps (Softube’s is an electron based 700MB monstrosity + helper app + wastes an additional 200MB needlessly leaving the Softube Central zip on the drive), is starting to act as an advert against these companies for me. Almost 1GB for a freaking updater?

[Gamma-UT]

Due to some strangeness with the metal iLok 3 dongle on Mac OS (sometimes the key would actually get hot to the touch, whatever the hell it was doing) I gave in and just use the HD now.

This may be a fault in the hardware of that dongle. I've got the metal one and it's not overheating. It shouldn't make a difference, but in case it does, mine is plugged into a powered hub and not directly into the Mac.

[aMUSEd]

I have just installed a new plugin with it but unlike the old version it doesn't give any option as to activation, and instead of putting the licence on my iLok has put it on the hard drive. Does anyone know how to make it just put licenses on the iLok? - in the old version you had options.

Green circle, top right, has two options. iLok Locations, which shows the locations it sees that it can install to, and Settings / Auto Activate (which defaults to enabled, and will install licenses on your HD even if you have them on a key.)

Thanks so if I disable auto activate it will let me choose?

[Gamma-UT]

Thanks so if I disable auto activate it will let me choose?

It won't automatically put licences on the hard drive. You just use PACE's manager to handle the licences.

[PAK]

This may be a fault in the hardware of that dongle. I've got the metal one and it's not overheating. It shouldn't make a difference, but in case it does, mine is plugged into a powered hub and not directly into the Mac.

That’s a reasonable conclusion. However the problem did not occur with Windows 10. So the only different variable was either Mac OS or the Mac Studio’s ports. I did try it direct and via different hubs (via both Thunderbolt and A type ports), with the same result..

It wasn’t common. It happened infrequently after long (days to weeks) uptimes. But, after the 3rd or 4th time, it was enough for me not to trust it getting so hot. I did think about going with the USB-C version, to see if it made a difference, but figured I was fighting the tide. Plus it’s not like there’s a whole lot of hardware variables you can change to trigger revalidation on a Mac

[Gamma-UT]

I’d open a ticket at PACE. It sounds like it’s get stuck in a loop and keeps crunching numbers even without requests from the software, though I’d expect to get validation failures as well if it’s yer regular infinite loop problem. Or it’s simply requesting too much juice from the USB port: it gets to a point after a few days where it fails to request low power when idle. I believe the iLok has a bunch of anti-tamper circuitry inside, which is why they go funny on unpowered hubs: they seem to perceive intermittent low voltage as an attack and lock up.

Low-level sensor fault + small differences in software drivers between platforms = chaos.

There’s probably a clue in the logs but it’s a ball-ache sifting through them. But maybe PACE has seen it before.