Original Summary

I've used other automation projects in the past like ARM and HandyMKV, both are great. I recently nuked my home lab and lost all my docker configs and such. My new machine is just a windows one, where installing docker seemed cumbersome to me (sharing drives was a weird headache I was not expecting). So for whatever reason I thought let's see what 100 dollars of claude credits can do. Personally, I think it worked out pretty good! My goal is to continue working on this project here and there (I definitely have some pain points I'm not liking). It only really seems to work on movies right now. I haven't even installed any subprocess programs for music yet. It does use an offline imdb database to title movies automatically. It also uses the OS vision ocr program that's built into macOS and windows. The screenshot above will be using Apple's Vision framework. For linux (and any platform really), I'm hoping that if this program can find tesseract on your system, it'll use that as a subprocess fallback for reading PGS into srt files. The idea is basically you have a tasks page with your drives, queue, logs, recently completed, etc. You have a projects tab to handle things like remuxing, transcoding, OCR'ing subs, etc. And you have a blueprints tab to create plan templates for your projects. So you can have a drive automatically execute a plan based on a blueprint. While it's copying the original disc to the harddrive (via MakeMKV), you can make any changes on top of the blueprint that was used until the transcoding (via Handbrake) begins. I'm actually not sure if I told Claude to use handbrake or if it's just using ffmpeg, will have to double check that (maybe handbrake just uses ffmpeg on the backend, I really haven't looked into it too much). Arfabit basically owns a folder in your downloads (e.g. ~/Downloads/arfabit) which contains a folder for each disc. You can have multiple files in there using Plex's naming structure of {edition-foobar} . So you can have the original mkv from MakeMKV as the Original edition and you can have a transcoded one as Archive edition. Arfabit also has the ability to use only short clips of an original mkv to help you sort out what is requiring transcoding on your player or what preset speeds/quality numbers to use that you prefer. So I liked that it was an easy way for me to compare file sizes and quality on my TV and decide on my own handbrake/ffmpeg config numbers. Would definitely appreciate any feedback on how to better sort out the workflow in here. I think I have a good generic idea of automatic vs manual process using the "projects" and "blueprints" tabs. But even I can feel some friction/confusion between the two flows. Let me know what you think! If you're interested (also side posted to r/makemkv ) and want to try it out (have to compile it yourself using golang) it's open-source (MIT licensed) on github: https://github.com/ar

  • 情报分类：技术学习与提效
  • 分类依据：内容涉及技术、AI、软件工具或工程实践
  • 信息来源：Reddit · SideProject
  • 发布时间：2026/9/27 22:33:20