nightcore.sh

A Bash script that automates the process of creating "Nightcore" videos for songs.

Features

• Renders high-quality visual effects (a gliding background, text overlay, and audio visualizer) without need for user configuration
• Uses advanced pre-processing to automatically fix common issues (unnecessary audio silence, black bars in images, slight audio clipping, volume differences between songs) that would typically require manual editing
• Has a high-quality lossless media processing pipeline to preserve image and video quality whenever possible
• Offers 4k60 lossless, single-file (video+audio+thumbnail+subtitle) outputs at reasonable filesizes
• Comes with a suite of cli tools to manipulate output files (splitting into multiple files, compression, etc)

System requirements

Note: It may be possible to run the script on hardware that doesn't meet these requirements, but you will likely encounter issues.

• A Unix-based operating system.
• 6+ GB of available system RAM. More is better (especially with ESRGAN).
• A fairly powerful CPU, weak CPUs will be unable to play the rendered video in real-time. Faster is better.
• Enough available storage for storing all the dependencies and your rendered videos (expect ~1GB per video).

Dependencies

Required

• Bash
• Coreutils
• FFMPEG
• ImageMagick
• SoX

Optional (but highly recommended)

Version information

• Git

Subtitle processing

• Python3
• srt (pip install srt)

Ultra-high-quality ESRGAN upscaler

Note: This can take upwards of 30 minutes to upscale a single image on a fairly decent CPU. Uses the YandeRe ESRGAN model.

• Python3
• PyTorch
• NumPy (pip install numpy)
• OpenCV (pip install opencv-python)

High-quality upscaler

Delivers fairly meh quality. Much better than typical upscalers (such as Lanczos), but much worse than ESRGAN.

Roughly 10x faster than ESRGAN. If you care more about speed than quality, use this.

Note: If all the ESRGAN dependencies are installed, it will be preferred over this upscaler.

• waifu2x-converter-cpp

Installation

Once all dependencies are installed, open a terminal in the directory you wish to install the script into, and run the following commands:

git clone https://github.com/katattakd/nightcore.sh.git
git submodule update --init --recursive

Usage

Run bash nightcore.sh help_full for detailed usage information, or bash nightcore.sh for an overview of script usage (shown below):

Usage: bash nightcore.sh [mode] [input directory]

Available modes:

- render - use the files present in the directory to render a nightcore video
- split - split the script's output file into multiple files
- compress - create a compressed version of the script's output file for sharing
- expand - remove compressed version of output file
- combine - remove all files split from the output file
- clean - remove all files produced by nightcore.sh from the directory
- help - show this menu
- help_full - show a more detailed version of this menu

Use the help_full mode for more info.

Sharing output videos

The output file generated by the script's renders (output.mkv) is not suitable for sharing. It's huge (typically ~1GB), very high-resolution, only has a single keyframe (so seeking isn't possible), has an embedded high-resolution image, uses lossless codecs not supported by most video players (lossless sRGB H.264 video + FLAC audio), and uses a container format that isn't widely supported (Makroska).

As a result of this, you will have to re-encode the output file before you can share it (unless you're trying to share a lossless copy of the rendered video, or you're uploading to a streaming site, such as YouTube, which will re-encode the video for you). There are multiple ways to go about doing this.

The easiest way to do so is by using the script's built-in video compression tool. Simply run bash nightcore.sh compress [optional input directory], and it will make a compressed version of the output.mkv file called compressed.webm. This does everything right, and results in a high-quality video that you can share with most of your friends.

But, there are some caveats to this:

• It's slow. Expect it to take a slightly longer to compress than it took to render the video.
• You're stuck with specific codecs (yuv444p vp9 + opus + webvtt), a specific resolution (1080p60), and specific bitrates. If you need wider software support, a higher quality, or a smaller filesize, you'll have to do something else.

As a result of this, you'll likely need to manually compress the output video yourself at some point. Even if uploading to a streaming site / using the built-in tool works fine for now, you may run into a situation in the future when it doesn't.

Here's some guidelines, tips, and potential pitfalls to keep in mind (assuming you know some basic media encoding stuff):

• The renders are sRGB, and many tools (such as FFMPEG / anything FFMPEG based) mess up sRGB -> YUV conversion. Make sure that the compressed video is using the bt.709 colorspace.
  • The src/modes/compress.sh file may be a useful reference on how to perform sRGB -> YUV conversion correctly with FFMPEG.
• Make sure to strip out the attached image & metadata while re-encoding.
  • The src/modes/compress.sh file may be a useful reference on how to do this.
• If you're working with low bitrates (below 1mbit/s), give most of the bitrate to the audio stream. Bad quality audio is much more noticeable than bad quality video, especially when the audio is the main focus and the video is just eyecandy.
  • If you're working with very low bitrates, you may be better off sending an audio-only file. Decent audio + no video is far better than bad audio + terrible video.
• If you're uploading to a service which is going to be re-encoding the content (like a streaming site or social media), use lossless codecs if you can, and the highest bitrates possible if you can't.
• Use modern codecs if possible (especially when it comes to the audio), as they'll allow you to get much better quality at the same bitrate.
• Use yuv444p instead of yuv420p if possible. There may be a fairly noticeable difference in visual quality, especially at lower resoultions.
• Use 60fps if possible, even if it requires lowering the quality a bit more. The music visualizer benefits a lot from framerates >30fps.
• If filesize/bitrate isn't a huge concern, target a quantizer value (crf) instead of a bitrate. This will allow for more consistent quality between videos.
  • For audio: If lossless isn't an option, use a vbr setting.