the makmkv docker is complaining that it is too old and must be updated to be used?

2 hours ago, TexasUnraid said:

the makmkv docker is complaining that it is too old and must be updated to be used?

yeah there are some issues with ccextractor which was causing the build to fail, i have worked around it for now, not overly happy with it as it increases the image size, but hey for now i will go for the workaround.

5 minutes ago, binhex said:

yeah there are some issues with ccextractor which was causing the build to fail, i have worked around it for now, not overly happy with it as it increases the image size, but hey for now i will go for the workaround.

 

Cool, band-aids are perfectly acceptable. lol.

 

I tried updating the docker but it did not pull anything, guess you have not pushed the update yet?

Edited March 3, 20224 yr by TexasUnraid

22 minutes ago, TexasUnraid said:

 

Cool, band-aids are perfectly acceptable. lol.

 

I tried updating the docker but it did not pull anything, guess you have not pushed the update yet?

not yet, still doing my day job 🙂

1 minute ago, binhex said:

not yet, still doing my day job 🙂

 

Yeah no worries, sounded like you had it sorted so was not sure if it was an issue with it being pushed or just had not done it yet.

Any update to this docker? I am still getting the update error.

19 hours ago, strahd_zarovich said:

Any update to this docker? I am still getting the update error.

yep i have updated the image this morning.

 

@here the reason the image had not been updating is due to ccextractor build issues with ffmpeg v5, so for now ccextractor is not included in the latest image, if you do need ccextractor then please use an earlier tagged image.

On 6/3/2020 at 2:16 PM, Milldor said:

Setting MakeMKV to run as root user fixed the drive not being detected for me.

 

Use PGID and PUID as 0.

Thanks for this. I haven't used MakeMKV for a long time, and had removed the container. Today I realized my optical drive had a bad SATA cable, so I replaced it but still couldn't see the drive even though I could see it in unRAID and my BIOS menu.

Setting those two values to 0 worked! Cheers.

On 10/8/2019 at 1:02 PM, LFTech said:

--device /dev/sr0 --device /dev/sg6.

 

I have tried multiple different ways include --device=...

I have an LG Bluray DVD Drive and doing this worked for me! After I added "--device /dev/sr0 --device /dev/sg9" in the extra parameters. Thank you! the '0' and '9' could be a different number on each persons server so take that as a guideline.

dumb Question!  Is it possble to trigger the MakeMKV window to fullscreen if i start the Docker?

Edited April 3, 20233 yr by Snickers

How do I find out what/where my USB connected BluRay drive is called/connected?
This is shown to me in the dashboard -> ASUS BW-16D1HT 3.10 /dev/sr0 1.07GB

 

UPDATE:

Everything you need can be found here: https://github.com/jlesage/docker-makemkv#access-to-optical-drives

In my case I just had to start MakeMKV once and look in the log. At the beginning it states your detected optical drive which you can add in "Additional Requirements:"

Edited June 6, 20233 yr by AceBurn90

Hi there! Is there a way to add a variable or something to fix this message?

Using direct disc access mode
AACS directory not present, assuming unencrypted disc
This disc requires Java runtime (JRE), but none was found. Certain functions will fail, please install Java. See http://www.makemkv.com/bdjava/ for details.

Hi there! Is there a way to add a variable or something to fix this message?

Using direct disc access mode
AACS directory not present, assuming unencrypted disc
This disc requires Java runtime (JRE), but none was found. Certain functions will fail, please install Java. See http://www.makemkv.com/bdjava/ for details.

I have created a new test image with Java included can you please give it a try by appending :test to the name of the repository for the container and applying, let me know if it works so I can push to main

Sent from my 22021211RG using Tapatalk

11 hours ago, binhex said:

I have created a new test image with Java included can you please give it a try by appending :test to the name of the repository for the container and applying, let me know if it works so I can push to main

Sent from my 22021211RG using Tapatalk
 

That worked. Thanks so much!

That worked. Thanks so much!

This has now been pushed to main, please remove the tag :test

Sent from my 22021211RG using Tapatalk

On 4/8/2023 at 2:25 PM, AceBurn90 said:

How do I find out what/where my USB connected BluRay drive is called/connected?
This is shown to me in the dashboard -> ASUS BW-16D1HT 3.10 /dev/sr0 1.07GB

 

UPDATE:

Everything you need can be found here: https://github.com/jlesage/docker-makemkv#access-to-optical-drives

In my case I just had to start MakeMKV once and look in the log. At the beginning it states your detected optical drive which you can add in "Additional Requirements:"

That's not the right docker image... I didn't see any of that in logs for the binhex container.

 

Has anyone figured out a way to get usb drives to reliably appear?  Only way I've found was to set puid and pgid to 0.

I've suddenly developed a problem with connecting to the webui via vnc. Every time I try and open MakeMKV (latest release), I get the following:

 

noVNC encountered an error:

 

Cannot read properties of null (reading 'addEventListener')

TypeError: Cannot read properties of null (reading 'addEventListener') at Object.addClipboardHandlers (http://10.0.30.145:6080/app/ui.js:329:13) at Object.start (http://10.0.30.145:6080/app/ui.js:101:12) at http://10.0.30.145:6080/app/ui.js:47:27

 

Other vnc dependent applications are working

13 hours ago, Moose_Flunky said:

I've suddenly developed a problem with connecting to the webui via vnc. Every time I try and open MakeMKV (latest release), I get the following:

 

noVNC encountered an error:

 

Cannot read properties of null (reading 'addEventListener')

TypeError: Cannot read properties of null (reading 'addEventListener') at Object.addClipboardHandlers (http://10.0.30.145:6080/app/ui.js:329:13) at Object.start (http://10.0.30.145:6080/app/ui.js:101:12) at http://10.0.30.145:6080/app/ui.js:47:27

 

Other vnc dependent applications are working

Yeah this is normally cache/cookie related, clear cache and cookies for this site and try again.

I'm having trouble getting MakeMKV to work with a  physical drive for the first time. I've used it many times for iso files and bdmv folders and the like.

 

My error is a timeout of some sort, which is odd as I know the drive works fine and the sata controller is good as I have used them both recently.

 

the errors I am getting are:

Error 'Scsi error - HARDWARE ERROR:TIMEOUT ON LOGICAL UNIT' occurred while reading 'BD-RE ASUS BW-16D1HT 3.02 KETI5GI0938' at offset '65536'

 

I get this regardless of the container I use so I'm worried something has somehow killed my drive.

 

I did get it to show the titles on a disk once using the the other container, but then it didn't start when I tried to rip, it just sat there and finally timed out.

 

 

EDIT: ok odd. I just went out to the rack and force ejected the disk then put it back in now everything works perfectly. Must have been jammed in a busy state of some kind.

Edited October 14, 20232 yr by Faceman

On 10/4/2023 at 12:56 AM, binhex said:

Yeah this is normally cache/cookie related, clear cache and cookies for this site and try again.

Yeah, that was it. Cleared out the cookies and cache and everything returned to normal

On 6/3/2020 at 10:16 PM, Milldor said:

Setting MakeMKV to run as root user fixed the drive not being detected for me.

 

Use PGID and PUID as 0.

Thanks thar worked for me.

 

One problem solves, one left. I creazes a share for the makv-files on my array. I set this up in the container config, but can't see this share within makemkv. What do I need to do, to see my share?

 

Edit: I just found out......in the container config I pointed to my share and there it says, Container Path: /media, so I need to select /media in makemkv as the path to store the files....

 

Sorry for the misunderstandig, I' completely new to unraid and docker.

 

Thanks for the tips in this thread.

Edited October 30, 20232 yr by Tebald

On 7/7/2022 at 9:51 AM, binhex said:

yep i have updated the image this morning.

 

@here the reason the image had not been updating is due to ccextractor build issues with ffmpeg v5, so for now ccextractor is not included in the latest image, if you do need ccextractor then please use an earlier tagged image.

I am getting the update error. Will this docker be updated with a new license? Is there a way I can update the license manually?

17 hours ago, rbrowning85 said:

I am getting the update error. Will this docker be updated with a new license? Is there a way I can update the license manually?

what 'update error'? this has a freeware licence for another 50 days yet:-

On 12/1/2023 at 9:32 AM, binhex said:

what 'update error'? this has a freeware licence for another 50 days yet:-

 

I show the same thing under the About menu. However, when I try to rip a blu-ray disk, I get the attached error.

Same here, did the force update, started and restarted, removed config file in appdata but still the "evaluation period expired" error returns. The About screen tells me I have 102 days left in my license?

 

Removing docker image, deleting appdata folder and reinstalling docker did the trick

Edited February 3, 20242 yr by Ignasz Wolke