How long will an older version continue to work?

The place to discuss linux version of MakeMKV
Post Reply
Zirias
Posts: 22
Joined: Mon Apr 22, 2019 3:30 pm

How long will an older version continue to work?

Post by Zirias »

A few days ago, 1.15.1 refused to work, stating the version was too old. Today it worked again :?: Is this a random glitch?

In general, how long will a version continue to work after a new version is released? Would it be ok to keep 1.15.1 in a quarterly package repository until october?
Zirias
Posts: 22
Joined: Mon Apr 22, 2019 3:30 pm

Re: How long will an older version continue to work?

Post by Zirias »

I didn't ask about expiration of keys, but of program versions, that's a different topic.
Woodstock
Posts: 9912
Joined: Sun Jul 24, 2011 11:21 pm

Re: How long will an older version continue to work?

Post by Woodstock »

If you have a permanent key, the old version will run indefinitely.

That said, as copy protection schemes advance, the old version will fail to rip disks more and more. Version 1.14.0, for example, won't rip Bluray disks with AACS version 67 or later, and if you were to insert a v71 disk in your drive, the AACS will lock the drive out from being able to rip ANY BD.
MakeMKV Frequently Asked Questions
How to aid in finding the answer to your problem: Activating Debug Logging
Zirias
Posts: 22
Joined: Mon Apr 22, 2019 3:30 pm

Re: How long will an older version continue to work?

Post by Zirias »

I still think there's some confusion about what I'm asking. Regardless of the beta key expiry -- makemkvcon will tell you that it won't run any more and you have to upgrade the software.

What I want to know is the exact scheme when this error will be shown. It's a different error than the one about an expired key. Even if this doesn't happen with a paid key (yes, see edit below), my interest is as a packager, and there will probably be a lot of users using the free beta key. I want to know whether having a package of 1.15.1 until october would be fine or whether it will stop working for being too old :)

edit: Looking at the exact messages in makemkvcon, it seems that, indeed, with a paid key, you won't be forced to upgrade the application:

Code: Select all

This application version is too old.  Please download the latest version at %1 or enter a registration key to continue using the current version.
Still it doesn't help to decide whether a package of 1.15.1 will be fine, as there will be users using the free beta key, and they will be forced to upgrade, so my question stands: when exactly will that happen? :)
MetalDave
Posts: 31
Joined: Wed May 03, 2017 10:17 pm

Re: How long will an older version continue to work?

Post by MetalDave »

As Woodstock posted in his FAQ:
However, the beta key that is linked to above, DOES expire periodically, in part to make sure people remember to stay current with the beta, and in part to encourage you to buy your own permanent key, which won't expire.
Unfortunately, there is no set period of time before a beta key expires. While the License Purchase page indicates you have a 30-day trial period, I'd found the beta key expires at any given time. I believe it's tied to the availability of a new version of the app.

That said, the license you purchase is permanent and will not shutdown the use of the software regardless of the version you're using. If you use it on a regular basis, I would totally recommend the purchase. Permanent licenses are great to have in this day and age of subscription models, and I've more than gotten my value out of the software.
Support MakeMKV - Buy a license!
(Seriously, you use this thing enough; A lifetime license is well worth it.)

Thank you to all of my fellow supporters!
Woodstock
Posts: 9912
Joined: Sun Jul 24, 2011 11:21 pm

Re: How long will an older version continue to work?

Post by Woodstock »

Beta keys typically expire every 60 days or so, almost always at the end of the second month after a version is released. But yes, they can feel rather random. :)
MakeMKV Frequently Asked Questions
How to aid in finding the answer to your problem: Activating Debug Logging
Post Reply