HandBrake

Ha! That's funny. I've been a software engineer for 30 years, and even today, wherever I work, the only shells I can reliably assume will be available are bash and tcsh. And I loathe tcsh for productivity and stability (not to start a holy war, but the list of problems with tcsh that compromise prod...

Quoting is sufficient to remove any special meaning of ":" in bash. No additional escaping is necessary. Bash man page makes this fairly clear (citation readily available); however, the more conclusive proof (to my thinking) is that the message from HandBrake itself shows the entire filena...

CONFIRMED. The COLON in the filename is the entire source of the problem with HandBrakeCLI. How does one submit a bug report? Or perhaps I should just take a peek at the code and submit a patch for this one-- seems like a very trivial bug...

I have a theory -- I think it might be the COLON in the filename! I just had the same failure encoding "Mission: Impossible II (2000).mkv". On a hunch, for MI 3, I tried changing the colon, so I used "Mission - Impossible III (2006).mkv" for the rip name. And THAT seems to be wor...

I'm running a script that I've used to rip+encode over 100 movies from my library -- most are DVDs, but there are about 2 dozen BluRays in the library that I've ripped so far. This is the first failure of this nature, so I'm pretty sure it doesn't have anything to do with the missing path -- the fil...

Description of problem or question: I used MakeMKV (command-line) to rip "Mission: Impossible (1993)" to an .mkv file, and then tried to use HandBrakeCLI to reencode the video to an .m4v file. HB failed with a "scan: unrecognized file type" error. However, when I re-tried with t...