Execute makemkv command line software#
Execute makemkv command line tv#

I use MM for the following reasons (again, this is all automated by my scripting tool):ġ. It runs a variety of tools, including MakeMkv (MM), to achieve its target results. I wanted to preserve this knowledge, so reprocessing discs in the future (e.g., errors, newer formats, change-of-mind, etc.) would be easy.įor me, reprocessing a disc is simply a matter of rerunning the script. I realized long ago that there is a lot of research that goes into processing discs (determining title numbers, tracks, forced subtitles, etc.). Most people seem interested in quickly and easily extracting or transcoding Blu-rays or DVDs into media files.

My automation goals seem different than most. I've written my own scripting language, specifically tailored to transcoding discs into mkv files.

Execute makemkv command line software#

Thanks for the great software and keep up the good work.

Happy to answer any additional questions if needed. Hope this gives you some good user base intel for the cli user base. Its not a big deal, but being able to log the data sent to stdout would allow additonal scripting functionality. So far my attempts at trying to capture this output have ended up in either unreadable files or empty files which captured nothing. My only requests at this time would be for a 'dry run' or 'scan' parameter and then the ability to output the operational data to a file v/s having it sent to stdout. The GUI requires more intervention and time, which ends up being a more significant mental break. I have found my 'magic' formula for both makemkv and handbrake so I can simply insert disc and run my scripted operations while I work with very little interruption. It seems to be much easier to automate pieces of the operation with makemkvcon v/s GUI. That said, I personally use linux with no GUI as I also rip on a headless system and have a huge collection of movies I am working to digitize. Love the software and as of ~1mo ago am a proud owner/sponser of the work. Let me get my thanks and appreciation out of the way first. Thanks for your time and your wonderful tool! What do you think? Is it a big ask for makemkvcon to be able to parse a title list and rip multiple titles without completely rescanning the structure every time? Running multiple times is what really becomes inconvenient, especially when the disc has certain types of copy protection schemes ('Complex multiplex encountered'). What I need to do now is either pass 'all' and rip a bunch of material I don't want or need, or run the command multiple times - once for each title I want. I'd really like to be able to pass something like '1-5,8'. Makemkvcon mkv dev:$DEVICE $TITLE /output_dirįor $TITLE, a single number is allowed, or the word 'all'. This is an excellent example of a use case that would benefit from what I'm about to request.Ĭurrently, the command-line syntax I use is something like this:

Execute makemkv command line tv#

Often when ripping TV series, a disc will have a title for each episode, AND a title that it all episodes together. I have a request, actually, and while I don't want to assume anything about how simple or complicated my request is, I don't think it's a huge thing. I run makemkvcon after connecting to the ripper via ssh, in a screen or tmux session that I can disconnect from while rips are ongoing. The box I rip on doesn't even have a keyboard/monitor connected to it normally.