www.makemkv.com

failed to execute external program 'ccextractor' is the error I am getting. I am unable to figure out how to fix this. I am unable to run commands in terminal either as it keeps asking for a pw when I use sudo but my admin pw on the machine isn't accepted.

This is on a new M1 Mac mini.

Any help would be appreciated.

Work around is to NOT select closed caption subtitles.

Or you can set the path to ccextractor to /bin/true which will cause it to be ignored.

I also have this problem and error. I am using an external DVD player on an M1 MacBook Air. I looked through the MakeMKV settings and did not see a place to get rid of the closed captions

You have to unselect the closed captions from the title, using the left-hand menu.

Changing names with Expert mode enabled shows how to access the selections.

In this case I have just decided to return the external drive I purchased. I use an old MacBook to rip the DVDs. I don't have BLueRay so I don't care enough to use this work around. thanks for the feedback

It's actually more of a problem on DVDs than BDs.

A lot of DVDs claim to have Closed Captioning, but do not, which will also cause ccextractor to take a LONG time to figure out, which has all the visual cues of a crashed program. Gone with the Wind 70th Anniversary DVD is where I first encountered it.

That's peculiar. On my Intel Mac on Mojave mmccextr comes packaged in the MakeMKV app.

If MakeMKV is in the default spot, you can check with this command: It is in the same spot in MakeMKV 1.15.4 on Big Sur 11.2.1 on an M1 mac. In MakeMKV Preferences, on the Advanced tab, the 'ccextractor executable location' is blank, which is the default I think.

I just updated my M1 Mac to MakeMKV 1.16.0 and mmccextr is there as I expect. Interestingly, the permissions on this file in this version are different. In 1.15.4 it is 775 (-rwxrwxr-x), in 1.16.0 it is 661 (-rw-rw-r--). I don't have an optical drive handy to plug into my MBA to see if that makes a difference.

Without the x permission, it won't be allowed to run, so that would account for "cannot find" errors.

Fixed in 1.16.1 along with "failed to initialize" bug some have seen...

awesome! thanks