Dude, you're rather naive if you think logging in or not to a plugin makes any difference in the tracking part. The dev has stated multiple times now that after "logging in" you are supposed to use it offline. That means, you're probably logging in to a remote server to generate a token/keyfile/whatever on the client to authorize it until that thing expires (maybe the dev can confirm the TTL). Staying "logged in" in this context does not mean there is an active server side session still alive, but merely that you didn't de-authorize your client application.TheMaestro wrote: Sat May 02, 2026 10:34 am User-tracking.
Relying on the other end being online.
Try "accidentally" logging out of the synth, offline, then use it. Then report back here.
Should I stop, or do you need to be spoon-fed even more?
You don't have even one valid point of why we should need to log in to a VST, and stay logged in.
It's really just semantics, most companies call it "online authorization" vs. ULTRAs "login". The real question is, if you start your DAW and load up ULTRA, do you need an active internet connection? From what the dev says the answer is no, and it really is quite easy to test.
You don't like online authorization? Fair enough - but don't pretend ULTRA is some kind of outlier here. There are really a lot of companies doing exactly the same, including Arturia, UAD, Waves, NI, IKM, D16, or even small ones like Cytomic... just to name a few. Many more if you include iLok, which also requires you to be online for the authorization process.
