Skip to content


Switch branches/tags


Failed to load latest commit information.
Latest commit message
Commit time

Vrecord Documentation

This documentation is up to date as of vrecord version 2020-02-10.

Table of Contents

  1. Summary
    1. Contributing to vrecord
    2. License
  2. Installation and Basic Use
    1. Installing vrecord
    2. Installing on Linux
    3. Using vrecord
      1. Setting Up vrecord for the First Time
      2. Basic Usage
      3. Ending a Capture
  3. The vrecord Window
  4. Passthrough
    1. Passthrough Mode
    2. Audio Passthrough Mode
  5. Editing Settings
    1. Options for Video Capture
    2. Video Capture Views
    3. Clearing the Configuration File
  6. DV Capture
  7. Audio Capture
  8. Analog Digitization Tips
  9. Help and Troubleshooting
    1. Testing Your Equipment
    2. Known Issues
      1. Timing of Recording
      2. FFmpeg Error Message
    3. Common Questions
    4. Other Issues


Vrecord is open-source software for capturing a video signal and turning it into a digital file. Its purpose is to make videotape digitization or transfer easier. Vrecord can capture analog and digital signals through a variety of inputs and can create digital video files in a variety of formats and codecs. Vrecord has been designed with needs of audiovisual archivists in mind.

Vrecord uses AMIA Open Source’s ffmpegdecklink to do its dirty work. Other dependencies are: cowsay, decklinksdk, gtkdialog, freetype, sdl and xmlstarlet. Optional dependencies are: deckcontrol, gnuplot, mediaconch, mkvtoolnix, mpv and qcli.

Currently vrecord supports macOS or Linux, and Blackmagic Design capture cards with the Blackmagic driver installed or AVFoundation for DV capture on macOS. Some notes on needed hardware are provided.

If you want to see a more detailed description about how to digitize analog videotape see our document on analog digitization.


We want vrecord to be a helpful tool for audiovisual archivists and others. Anyone can contribute to vrecord! If you experience any problems with vrecord you can open a new issue with our GitHub issue tracker. Try to see if you can replicate the issue yourself first and describe in detail what factors led to it. Please let us know if you were able to successfully replicate the issue.

For more tips on using GitHub and contributing directly to vrecord, please see our Contribution Guide, but feel free to contribute to vrecord by creating a fork and sending pull requests.


The vrecord Team


Creative Commons License
Vrecord is licensed under a Creative Commons Attribution 4.0 International License.