registering using makemkvcon

[edent]

How do I register with the beta key using `makemkvcon`?

I've compiled and installed the latest version, run:

Code: Select all

makemkvcon reg T-T2HdpRvyvJtxjVtKWRv1n92AcFFFlYyl3FX2mazk0obKPR3V1fgIDQ793QfUnT2opR

But I just get "Key not found or invalid".

I've tried writing it to a file and using `reg filename.txt` but I get the same error.

Is there a way to register using the command line?

Thanks!

[beandog]

In ~/.MakeMKV/settings.conf put app_Key = "product-key"

[rockiesmagicnumber]

I'm also experiencing this issue. I edited `settings.conf` and found that the beta key I'd entered via GUI was already in the conf. I restarted MakeMKV a couple of times. Haven't gone so far as to reboot the computer tho.

Code: Select all

PRGC:3402,0,"Decrypting"
PRGV:0,7363,65536
MSG:5055,0,0,"Evaluation period has expired, shareware functionality unavailable.","Evaluation period has expired, shareware functionality unavailable."
MSG:5052,516,0,"Evaluation period has expired. Please purchase an activation key if you've found this application useful. You may still use all free functionality without any restrictions.","Evaluation period has expired. Please purchase an activation key if you've found this application useful. You may still use all free functionality without any restrictions."
MSG:5010,0,0,"Failed to open disc","Failed to open disc"

[beandog]

Make sure you're using the right key, viewtopic.php?f=5&t=1053

Post settings.conf here if it's still not working

[rockiesmagicnumber]

I should add that this is running through ARM

Code: Select all

#
# MakeMKV settings file, written by MakeMKV v1.17.0 linux(x64-release)
#

app_Key = "T-T2HdpRvyvJtxjVtKWRv1n92AcFFFlYyl3FX2mazk0obKPR3V1fgIDQ793QfUnT2opR"
sdf_Stop = ""

[mike admin]

Double-check the date on your computer.

[rockiesmagicnumber]

Code: Select all

rockiesmagicnumber@pop-os>> date
Tue Jul 19 10:32:25 PM MDT 2022

[rockiesmagicnumber]

Did I miss something obvious here? The beta key is good until the end of July 2022 and it's clearly 2022-07-21 now, and it seems I've followed all of the steps correctly.

[beandog]

This is a shot in the dark, but what's the permissions on .MakeMKV directory and settings.conf (run stat)

[rockiesmagicnumber]

Code: Select all

 rockiesmagicnumber@pop-os >> ~ >> stat ~/.MakeMKV 
  File: /home/rockiesmagicnumber/.MakeMKV
  Size: 4096      	Blocks: 8          IO Block: 4096   directory
Device: fd01h/64769d	Inode: 6328437     Links: 2
Access: (0775/drwxrwxr-x)  Uid: ( 1000/rockiesmagicnumber)   Gid: ( 1000/rockiesmagicnumber)
Access: 2022-07-17 20:44:28.575420193 -0600
Modify: 2022-07-17 21:05:58.065408770 -0600
Change: 2022-07-17 21:05:58.065408770 -0600
 Birth: 2022-07-17 20:44:28.575420193 -0600
 
 
 rockiesmagicnumber@pop-os >> ~ >> stat ~/.MakeMKV/settings.conf 
  File: /home/rockiesmagicnumber/.MakeMKV/settings.conf
  Size: 172       	Blocks: 8          IO Block: 4096   regular file
Device: fd01h/64769d	Inode: 6302475     Links: 1
Access: (0666/-rw-rw-rw-)  Uid: ( 1000/rockiesmagicnumber)   Gid: ( 1000/rockiesmagicnumber)
Access: 2022-07-17 20:50:40.202193049 -0600
Modify: 2022-07-17 21:35:50.107501334 -0600
Change: 2022-07-17 21:35:50.107501334 -0600
 Birth: 2022-07-17 20:50:40.202193049 -0600

[mike admin]

Did I miss something obvious here? The beta key is good until the end of July 2022 and it's clearly 2022-07-21 now, and it seems I've followed all of the steps correctly.

It Shouldn't be like that. Please enable "log debug messages" by adding to settings.conf

Code: Select all

app_ShowDebug = "1"

or running makemkvcon with --debug option , and post the log here.

[rockiesmagicnumber]

here's as far as it got

Code: Select all

Debug log started at Sun Jul 24 03:38:16 2022 , written by MakeMKV v1.17.1 linux(x64-release)
001005:0000 MakeMKV v1.17.1 linux(x64-release) started
001004:0000 Debug logging enabled, log will be saved as file:///home/rockiesmagicnumber/MakeMKV_log.txt
Using 262272KB for read cache.
Network access is ENABLED, CURL version 7.81.0/OpenSSL/3.0.2/1.43.0 (x86_64-pc-linux-gnu) , proxy server not set.
001003:0020 DEBUG: Code 0 at ^aoCY_?pF2N[RTPtazEj{e:29393631
SDF  v08d: HL-DT-ST_BD-RE__WH14NS40_1.05_212005061444_KLBKB180413
SDF  v08d: HL-DT-ST_BD-RE__WH14NS40_1.05_212005061444_KLBKB180413
DEBUG: Code 2317353419 at !=9+E{bmwIy>yl\?#:213132974
DEBUG: Code 0 at !=9+E{bmwIy>yl\?#:121264786
DEBUG: Code 2317353419 at !=9+E{bmwIy>yl\?#:213132974
DEBUG: Code 1 at !=9+E{bmwIy>yl\?#:121264786
DEBUG: Code 2317353419 at !=9+E{bmwIy>yl\?#:213132974
DEBUG: Code 2 at !=9+E{bmwIy>yl\?#:121264786
DEBUG: Code 2317353419 at !=9+E{bmwIy>yl\?#:213132974
DEBUG: Code 3 at !=9+E{bmwIy>yl\?#:121264786
DEBUG: Code 2317353419 at !=9+E{bmwIy>yl\?#:213132974
DEBUG: Code 4 at !=9+E{bmwIy>yl\?#:121264786
DEBUG: Code 2317353419 at !=9+E{bmwIy>yl\?#:213132974
DEBUG: Code 5 at !=9+E{bmwIy>yl\?#:121264786
DEBUG: Code 2317353419 at !=9+E{bmwIy>yl\?#:121264648
DEBUG: Code 0 at K['JmtPBo'/pq.(a:29401934
SDF  v08d: HL-DT-ST_BD-RE__WH14NS40_1.05_212005061444_KLBKB180413

[rockiesmagicnumber]

Checking back on this, the issue still exists with the Aug/Sept key. Here's the latest log:

Code: Select all

Debug log started at Wed Aug 10 03:38:56 2022 , written by MakeMKV v1.17.1 linux(x64-release)
001005:0000 MakeMKV v1.17.1 linux(x64-release) started
001004:0000 Debug logging enabled, log will be saved as file:///home/rockiesmagicnumber/MakeMKV_log.txt
Using 262272KB for read cache.
Network access is ENABLED, CURL version 7.81.0/OpenSSL/3.0.2/1.43.0 (x86_64-pc-linux-gnu) , proxy server not set.
001003:0020 DEBUG: Code 0 at ^aoCY_?pF2N[RTPtazEj{e:29393631
SDF  v08d: HL-DT-ST_BD-RE__WH14NS40_1.05_212005061444_KLBKB180413

[backuptime]

Also still having this problem on linux trying to run headless makemkv.

I ran strace and there's evidence that suggests that makemkvcon reg <key_here> is trying to parse the string as a path, not the actual key.

see attachment.

[backuptime]

Replying to myself... i tried using the file method, and makemkvcon still refuses to accept the key.

Running makemkvcon with --debug or the debug flag set in settings.conf results in a log file with 2 lines acknowledging the creation of the file, nothing more. Definitely seems like license activation on linux is bugged on 1.17.2