-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing --decrypt option #139
Comments
Hi, there! It's a few months late, but I'd just like to add my two cents here. |
Bah, sadly my edits did not make it work |
This Sunday is the earliest I can look into fixing it. |
Thank you for looking into this but after doing a fresh git pull it is now at least walking the titles but it still isn't using the decrypt option. 2017-07-14 21:40:16 - Makemkv - ERROR - CellWalk algorithm failed (structure protection is too tough?), trying CellTrim algorithm I retested the command line to ensure that I can in fact rip a dvd with the makemkvcon command line utility. |
Could you share your command line args? The only place I haven't put in |
here is the command line i used. I realize doing all titles gets more than I need it was just expedient to test it. |
Any update on this @JasonMillward |
Not at this time, no. I've put in the decrypt option into both the |
For some reason I see that the makemkv.py rip class is missing the --decrypt option for makemkvcon.py. I've tried adding it into the class but for some reason it doesn't seem to help.
I get the following error when I run the autorippr.py script (version 1.7.0).
2017-05-12 22:10:45 - Makemkv - ERROR - CellWalk algorithm failed (structure protection is too tough?), trying CellTrim algorithm
This to me indicates that makemkvcon can't read the disk due to encryption. According to their documentation the default setting is not to decrypt.
When using the makemkv GUI it doesn't have a problem ripping the disk.
Additionally running the makemkvcon command from the command line to include the --decrypt options works fine.
Any word on this?
The text was updated successfully, but these errors were encountered: