mheidt

Yes, I can't remember the actual error message. And my code is 3 years old. You don't seem to have the current version either. I would take the latest version...

@bigmalletman Could you please test the changes using testing branch for zynthian-ui? You need to install the binary again to make it happen.

That looks good, doesn't it? The next time you upload a binary, the activation key shouldn't be empty. Could you try that? (you have entered it already, I hope) For...

So you are telling me, that if you deleted all pref files, installed from scratch and applied the product key, Pianoteq would not start with activation because it requests the...

I don't know why it was done. But I wouldn't change it. Maybe to have the option to keep Trial and other versions in parallel. Could you test it again...

Ah damn, @jofemodo the LKEY only exists after activation or first start...chicken/egg problem.

@dcoredump Do you remember, why you coded the product (PRO, STAGE) into the pref file name?

Ok. @bigmalletman Could you test the code with just the line PIANOTEQ_CONFIG_FILENAME = "{}.prefs".format(PIANOTEQ_NAME) No "if" against version 6. Do you want to do a PR afterwards or should I...

@bigmalletman It's not going to be that easy. I tested it with my binary (STAGE). The issue seems to be, that pianoteq is creating the prefs file before the activation...

What I learned the last time is, that it's not on us to decide how to name the .prefs file. During the first run Pianoteq itself creates the file. We...