selfhost.directory

The index of self-hostable projects — ranked, categorized and served with live updates.
Own your data and stop giving it to big tech.

automatic-ripping-machine logo

Self-host automatic-ripping-machine

2.24.4

Headless auto-ripper for Blu-rays, DVDs and audio CDs

ReleaseOpen SourceMIT
Updatedlast month
LanguagePython
Setup difficultyModerate
Stars
5 439
Port
8080 (ARM Flask web UI)
Requires
MakeMKV
Docker
automaticrippingmachine/automatic-ripping-machine
Install with Docker
automatic-ripping-machine screenshot 1automatic-ripping-machine screenshot 2automatic-ripping-machine screenshot 3automatic-ripping-machine screenshot 4

What is automatic-ripping-machine?

A.R.M. is a disc-ripping service for Linux home media libraries: a udev rule notices when an optical disc is pushed into a drive, decides whether it holds video, audio or files, and runs the matching rip with no further input. Blu-rays and DVDs are pulled off with MakeMKV and then transcoded by HandBrake, audio CDs are handled by abcde, and data discs are copied into an ISO image; titles plus the movie-versus-series decision come from OMDb so output folders are named the way Plex or Emby expect. Ripping and transcoding are decoupled, so the disc ejects as soon as raw files are on disk, and several drives can be worked in parallel. A Flask web UI guarded by a built-in admin account lists jobs and logs and lets you edit the arm.yaml settings in the browser, while finished rips can trigger notifications through Apprise or an Emby library refresh. Self-hosting needs real hardware: one or more optical drives, Linux, and plenty of fast storage for the raw, transcode and completed folders. Docker on Linux is the documented route, using the published image, an ARM_UID/ARM_GID pair matching the host arm user and a start script that binds the drives through; note that MakeMKV itself is trial-or-key software.

automatic-ripping-machine alternatives

Should you self-host automatic-ripping-machine?

automatic-ripping-machine scores 66/100 on selfhost.directory (how scoring works) and ranks #11 of 141 in Media Management. It has 5 439 GitHub stars, +148 in the last 30 days.

It shipped 16 stable releases in the past year. The latest, 2.24.4, came out on 3 October 2026. New versions land roughly every 6 days.

Setup is moderate: expect some configuration beyond a single command. An official Docker image is available. It is MIT-licensed and written mostly in Python.

Its closest alternative on selfhost.directory is Sonarr (80/100, 17 726 stars). It scores higher overall, so compare the two before you pick. See automatic-ripping-machine vs Sonarr side by side.

Features

  • Asynchronous batched transcoding
  • Automatic disc insertion detection
  • Automatic transcoding queue after rip
  • Blu-ray, DVD and CD ripping
  • Hardware-accelerated transcoding
  • Headless server operation
  • In-browser settings editing
  • ISO backup of data discs
  • Media title and type lookup
  • Movie vs TV show handling
  • Parallel multi-drive ripping
  • Push notifications on completion
  • Web UI for jobs and logs

automatic-ripping-machine README

Automatic Ripping Machine (ARM)

CI Publish Docker Image Docker

GitHub forks GitHub stars GitHub issues GitHub pull requests GitHub contributors GitHub last commit

GitHub license

GitHub release (latest by date) GitHub release Date Python Versions

How to install automatic-ripping-machine

Install automatic-ripping-machine with Docker

A system capable of running Docker containers
Environment variables
ARM_UID, ARM_GID, TZ
docker run -d \
   -p "8080:8080" \
   -e ARM_UID="1001" \
   -e ARM_GID="1001" \
   -v "/home/arm:/home/arm" \
   -v "/home/arm/Music:/home/arm/Music" \
   -v "/home/arm/logs:/home/arm/logs" \
   -v "/home/arm/media:/home/arm/media" \
   -v "/home/arm/config:/etc/arm/config" \
   --device=/dev/sr0:/dev/sr0 \
   --device=/dev/sr1:/dev/sr1 \
   --device=/dev/sr2:/dev/sr2 \
   --device=/dev/sr3:/dev/sr3 \
   --privileged \
   --restart "always" \
   --name "arm-rippers" \
   automaticrippingmachine/automatic-ripping-machine:latest

Pre-built image on Docker Hub; the wiki ships a start_arm_container.sh template you fill in with volumes, drives and CPU pinning. Not compatible with the snap version of docker.

How to configure automatic-ripping-machine

  • SKIP_TRANSCODEfalsearm.yaml switch to rip the whole feature to .mkv and leave HandBrake encoding out.

    values: true | false

  • OMDB_API_KEYarm.yaml parameter that enables OMDb title lookup and movie/TV identification.

    values: API key string

  • ARM_UIDDocker env var: host user ID of the arm user, needed when it is not 1000.

    values: numeric UID

  • ARM_GIDDocker env var: host group ID of the arm user, needed when it is not 1000.

    values: numeric GID

  • TZUTCDocker env var: timezone used by the container.

    values: e.g. New_York

automatic-ripping-machine releases & version history

@ Every self-hosted release, weekly

One Monday email with the week's stable releases across the directory.

FAQ

Where do I look when something else goes wrong?

Check the per-disc log files, by default under /home/arm/logs/, filtering them with grep for ARM entries. Raising the log level to DEBUG in arm.yaml gives more detail, and the wiki asks you to re-run a disc in DEBUG mode before posting a log to an issue.

I can't get AMD VCE to work

Check that vce_h264 / vce_h265 appear in the HandBrakeCLI encoder list, install the amdgpu-pro drivers, the amf-amdgpu-pro package and the Vulkan SDK, and use the single built-in H.264 VCE 1080p profile. VCE is not enabled by any distro by default, so HandBrake must be compiled from source with the --enable-vce flag.

I can't get Intel QuickSync to work

Run HandBrakeCLI --help and look for the qsv_265 / qsv_264 encoders; if they are missing you need the Intel Media SDK, the right graphics driver and possibly a HandBrake build from source. If they are present, make sure you pick one of the two built-in QSV profiles.

Why won't ARM eject the disc until transcoding finishes?

To let discs stack up, set RIPMETHOD to "mkv" so MakeMKV writes raw files to disk first and turn MAINFEATURE off so the whole disc is taken. These are not defaults because the mkv rip method can cause problems with Blu-rays.

Is there a way to disable HandBrake encoding and just keep the .mkv rip?

Yes, set SKIP_TRANSCODE from false to true in arm.yaml, either by editing the file or through the settings page in the web UI.

My arm won't start when I insert a disc?

Check that udev is really launching the wrapper: look for entries in empty.log in your configured log directory, verify the symlink to the automedia rules and reload udev rules, and confirm the arm user can write to the paths in arm.yaml. Also make sure scripts/arm_wrapper.sh is executable and watch tail -f /var/log/syslog while inserting a disc.

More in Media Management

Rate this project

Click to rate — no account needed.

0 comments

Posting as guest
Loading comments…