Javicle - a JSON Video Composition Language
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Jonathan Cobb ef10d2e07e update README 3 years ago
bin add support for -n/--no-exec for single-operation tools. allow handlebars context to use jsasset objects 3 years ago
docs improve handling of files with missing audio or video track 3 years ago
src improve handling of files with missing audio or video track 3 years ago
utils WIP. adding validation tests. refactoring 3 years ago
.gitignore ignore test script, adjust log output 3 years ago
.gitmodules add cobbzilla-parent submodule 3 years ago
LICENSE.txt add license 3 years ago
README.md update README 3 years ago
pom.xml rename jvcl -> jvc 3 years ago


Javicle - a JSON Video Composition Language

Javicle (JVC for short) is a JSON DSL for audio/video transformations.

Under the hood, it’s all shell commands: ffmpeg, mediainfo and so on.

JVC provides higher-level semantics for working with these lower level tools.


I infrequently find myself doing video editing, so I’ve never bothered to learn iMovie or any graphical video editor.

My editing needs are usually pretty simple, so I bust out ffmpeg and get the job done.

But it seems like every time, there is at least one wrinkle in the requirements that requires some deep research into ffmpeg filter arcana.

Hours later, before I know it, the day has gone by.

I created JVC to make it really easy to do the most common things people usually do to videos: splitting, concatenating, letterboxing, overlaying one video onto another, and so on.

A Quick Example

Suppose you have one video that is five minutes long, and you want to split it into five videos, each one minute long.

With ffmpeg and bash, you might do something like this:

    for ((i=0;i<300;i=(i+INCR))); do
      ffmpeg -i /tmp/my/source.mp4 -ss ${i} -t $((i+INCR)) /tmp/my/slice_${i}_$((i+INCR)).mp4

With JVC, you’d write this spec file and save it to a file (for example my-spec.jvc):

  "assets": [ {"name": "src", "path": "/tmp/my/source.mp4"} ],
  "operations": [{
      "operation": "split",
      "creates": "src_split_files",
      "source": "src",
      "interval": "60",
      "validate": [{
        "comment": "expect 5 output files",
        "test": "output.assets.length === 5"

and then run it like this:

jvc my-spec.jvc

Yes, the JVC is longer, but I think many would agree it is easier to read and maintain. It can also include validations (as shown above) to ensure the output assets are what you expect them to be.

As the number of media assets and operations grows, hand-crafted shell scripts with magical ffmpeg incantations become ever more inscrutable.

JVC is designed for readability and maintainability. JVC will continue to evolve towards greater coverage of the full capabilities of ffmpeg.

Who is JVC not for?

If you like GUIs, JVC is probably not for you.

JVC is not a replacement for Final Cut Pro or even iMovie.

Who is JVC for?

JVC is for people who like CLIs and automation.

JVC is for people with relatively simple video composition needs (for now), since the range of operations supported is limited.

JVC is for people who have used ffmpeg filters before and had flashbacks of editing Sendmail configs, debugging PostScript, or maintaining a legacy Perl system.

Caveat Emptor

Obligatory Disclaimer: JVC is still relatively new software and lots of stuff might not work right, ffmpeg could crap out on bad arguments, encodings, formats, filter syntax errors, or whatever.

In any case, JVC should never overwrite your source files, since all output goes to new files.

I’m also fairly confident that the underlying ffmpeg commands are far from optimized, and could use some scrutiny by eyes more expert than mine.


  • Java 11
  • Maven 3
  • ffmpeg (HEAD is required for overlay and merge-audio operations)
  • mediainfo

These programs should executable (given your PATH): javac, java, mvn, ffmpeg, and mediainfo

The first time you run jvc, it will automatically build the JVC jar file from sources, using maven and javac. This takes a little time but only needs to be done once.

Running JVC

Learn more about running jvc and other useful tools.

JVC Concepts

Learn about Assets and Operations, the core concepts of JVC.

Supported Operations

Today, JVC supports several basic operations.

For each operation listed below, the header links to an example from the JVC test suite.


Add a silent audio track to a video asset.


Speed up or slow down a video asset. Sound can be silenced, played at regular speed, or sped up/slowed down to match the video.


Concatenate audio/video assets together into one asset.


Transform a still image into video via a zoom-pan (aka Ken Burns) effect.


Resize a video, maintaining the aspect ratio and adding letterboxes on the sides or top/bottom.


Merge an audio asset into the audio track of a video asset.


Overlay one video onto another.


Remove a track from a video asset.


Scale a video asset from one size to another. Scaling can be proportional or anamorphic.


Split an audio/video asset into multiple assets of equal time lengths.


Trim audio/video; crop a section of an asset, becomes a new asset.

Complex Example

Here is a long, complex example that uses every operation.

JavaScript Expressions

Within a JVC spec file, operation parameters and validations can be JavaScript expressions, opening up some interesting capabilities.

What’s with the name?

A cross between a javelin and an icicle? JSON and a miracle? Something with positive connotations? I really don’t like naming things.