Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

[Support] Djoss - MakeMKV

Featured Replies

Thanks, I'll give it a try!  Again, thanks for the help!

  • Replies 947
  • Views 197.5k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • Note that there is currently an issue with the automatic disc ripper for people using the beta key (MakeMKV version is expired). A Docker image update will be available soon to address this.

  • Same thing as an internal drive.  In my case, the device is /dev/sr0, so I just add --device /dev/sr0 in extra parameters.

  • So maybe one solution is to add support for simultaneous disc ripping within the same container

Posted Images

What did the fix end up being for luisv? I am getting the exact error code as him. I tried changing the version and got the same error as well. This is an old ghost rider movie, not a new movie at all so I wonder if its not disc related then. 

Capture.PNG

Edited by fmjets11
Picture

I think it's an Alpine Linux and Java related issue.

  • Author

So if I understand correctly, making sure libjli.so is found by java fixes the backup mode, but not the ripping?

That's how it's appearing. And seems that instead of copying, we could fix it by adding more PATH directories as well, though untested.

Edited by cybrnook

Any luck?

  • Author
23 hours ago, cybrnook said:

Any luck?

I'm sill trying to find a BluRay disc requiring Java so I can reproduce myself the issue...

Sicario: Day of the soldado

 

If you have a movie store near you that rents.

Sorry guys... I was able to backup the disc successfully, then used Handbrake to convert the backup to MKV.

Sure, but there is still a problem. This is a good disc to use to expose it.

I'm getting this error: 

 

715992005_ScreenShot2018-10-22at6_10_58PM.thumb.png.d65d459e7873710501771acc467e64ff.png

 

Even if I manually enter the new beta key (valid until November) and also force update the docker container. Any suggestions?

I bought a key and I'm still getting the same error.

  • Author
6 hours ago, FieldGenEJ said:

I bought a key and I'm still getting the same error.

Do you set the key via the environment variable?

You can also try to start with an empty appdata folder:

  • Stop the container.
  • Move the appdata folder by executing "mv /mnt/user/appdata/MakeMKV /mnt/user/appdata/MakeMKV.backup"
  • Start the container.

@Djoss still no luck on the java issue? Hope all is well on your end.

Edited by cybrnook

  • Author
7 hours ago, cybrnook said:

@Djoss still no luck on the java issue? Hope all is will on your end.

I tried a couple of BD+ BluRay discs that were all decrypted successfully using Java.  I guess that I don't have one with the proper protection.

Which protection has your disc exactly?  MakeMKV displays the protection on the main page, before starting the titles detection by clicking the big drive icon.

Oh no.... I don't have that disc anymore. If you want, I can get it again this weekend if you're available.

I’ve had two tonight that needed Java and both ripped fine. Fifty Shades of Freed and Atomic Blond.

  • Author
8 hours ago, cybrnook said:

Oh no.... I don't have that disc anymore. If you want, I can get it again this weekend if you're available.

If it's not too much trouble for you, having an idea of the exact protection that makes Java to crash could be useful.

9 hours ago, Taddeusz said:

I’ve had two tonight that needed Java and both ripped fine. Fifty Shades of Freed and Atomic Blond.

Can you share the protection they use?

19 minutes ago, cybrnook said:

Can you share the protection they use?

Fifty Shades shows AACS v63 while Atomic Blond shows AACS v58.

 

Both of them show main title and such. Not sure what else to do to determine if they are using BD+.

1 hour ago, Taddeusz said:

Fifty Shades shows AACS v63 while Atomic Blond shows AACS v58.

 

Both of them show main title and such. Not sure what else to do to determine if they are using BD+.

Thanks, hopefully that helps get @Djoss a head start.

2 hours ago, cybrnook said:

Thanks, hopefully that helps get @Djoss a head start.

At work now but I left Atomic Blond in my drive. I reloaded it and noticed that it briefly flashed something about BD+ in the header. Nothing in the logs other than it using Java. I even enabled debug logging and nothing in there about BD+.

  • Author
23 hours ago, Taddeusz said:

At work now but I left Atomic Blond in my drive. I reloaded it and noticed that it briefly flashed something about BD+ in the header. Nothing in the logs other than it using Java. I even enabled debug logging and nothing in there about BD+.

Java can be used for other purpose also.  So usage of Java doesn't indicate it's a BD+ disc.  From what I saw, there is a clear indication when the disc is BD+.

 

But if your discs ripped fine, knowing their protection is not really important.  I'm better interested with protections that produce a crash ;).

I will go to the movie store and get Sicario this weekend, as posted before. I know this triggers the crash, and was also the same movie that caused @luisv 's crash as well.

 

@Djoss if you have a movie rental store near you, you likely could reproduce the same, might be easier to collect logs. If not, let me know what i need to gather at the time it's happening, specifically.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.