Licensing....

Archive mAirList 4.x (English)
1

Just discovered something that may or may not become an issue for users once released.

I was VPN’d in to my work system as I was doing some server maintenance, which is like watching paint dry. So I ran mAirlist v4 to do some fiddling. After about 5 seconds, it complained that my “license was invalid, contact support”.

I assume it was one of two things.

a) It communicated to mAirlist server from a different IP address than before so it was refused.
b) It uses an different port number than 80 and so was blocked by my work firewall, and because it couldn’t communicated, was refused.

Is this just a Beta thing and will be different once released?

I ask because I can see some operational downsides if kept in.

a) If you have it on a laptop for remote work, could be an issue as it will be on a different IP everytime
b) Could be an issue if some installs are not exposed to Internet or ports are blocked. I know for my corporate firewall, getting odd ports inblocked becomes an inquisition.

I appreciate the protection of Intellectual property, and I suspect much of this is to ensure the beta is controlled, but I wanted to add my thoughts if some parts were being transferred to the release.

Thanks

2

The beta contacts my server to check if it’s still valid. This check does not happen on port 80.

It will be removed for the final release. There are not online activation checks in production releases of mAirList. Never.

3

[quote=“Torben, post:2, topic:7521”]The beta contacts my server to check if it’s still valid. This check does not happen on port 80.

It will be removed for the final release. There are not online activation checks in production releases of mAirList. Never.[/quote]

Thanks. :slight_smile: Then I shall shut-up as they say.

(I have actually had issues with some broadcast software at work that sits on an isolated VLAN, and would not activate. The vendor was insistent it had to have internet access. So, we rejected it and refused the invoice. Needless to say, next version had manual activation a la Microsoft, just less painful!!) 8)

4

I had to make a decision whether go hand out a public beta without personalized licenses, or issue a separate license for anyone who wanted to test the beta. I opted for the latter, but with an extra online check just to make sure that the beta will stop working on the designated date.

5

Makes total sense. Getting close to that date too :slight_smile:

I must download the full version and experiment with the regional encoders, hopefully one evening this week.

6

Let’s see how many release-critical bugs we still have. The website must also be updated.

I hope everything will be ready by the end of the week. If not, the beta period will just be extended by a few days.

7

Looking forward to this - Once a recording function is built into the Mix Editor I dare say I’ll be sending some people your way, Torben :slight_smile:

8

That’s on the list for v4.1, but I won’t start working on it until v4.0 is out, so one more reason to hurry up now :wink:

9

Are there news on how to get the official licence … I want to change asap :wink:

10

Those who are eligible for a free upgrade can already find it in their customer account.

I believe you bought your license shortly before the “magic date”. Perhaps you can contact me by e-mail, and I’ll see what I can do for you.

11

As an aside to this, I’ve licensed my v4 on my hardware running XP SP3. At some point I’ll upgrade to Windows 7 (32 or 64bit, haven’t decided yet). Will that need to be a deactivate/reactivate scenario or theoretically license should follow as hardware probably won’t change?

Cheers, Richard

12

The Windows product key and install date is part of the Hardware ID, so it will definitely change. Just contact be shortly before or after the upgrade, and I’ll reset your license.