All Projects → HaveAGitGat → Tdarr

HaveAGitGat / Tdarr

Licence: gpl-3.0
Tdarr - Distributed transcode automation using FFmpeg/HandBrake + Audio/Video library analytics + video health checking (Windows, macOS, Linux & Docker)

Programming Languages

javascript
184084 projects - #8 most used programming language

Projects that are alternatives of or similar to Tdarr

Ffmpeg Php
FFmpegPHP is a pure OO PHP port of ffmpeg-php library that was written in C. It adds an easy to use, object-oriented API for accessing and retrieving information from video and audio files. It has methods for returning frames from movie files as images that can be manipulated using PHP's image functions. This works well for automatically creating thumbnail images from movies. FFmpegPHP is also useful for reporting the duration and bitrate of audio files (mp3, wma...). FFmpegPHP can access many of the video formats supported by ffmpeg (mov, avi, mpg, wmv...)
Stars: ✭ 446 (-51.04%)
Mutual labels:  audio, ffmpeg
Green Recorder
A simple screen recorder for Linux desktop. Supports Wayland & Xorg
Stars: ✭ 594 (-34.8%)
Mutual labels:  audio, ffmpeg
Mediatoolkit
A .NET library to convert and process all your video & audio files.
Stars: ✭ 492 (-45.99%)
Mutual labels:  audio, ffmpeg
Mystiq
Qt5/C++ FFmpeg Media Converter
Stars: ✭ 393 (-56.86%)
Mutual labels:  audio, ffmpeg
Homebridge Camera Ffmpeg
Homebridge Plugin Providing FFmpeg-based Camera Support
Stars: ✭ 726 (-20.31%)
Mutual labels:  audio, ffmpeg
Awesome Video
A curated list of awesome streaming video tools, frameworks, libraries, and learning resources.
Stars: ✭ 397 (-56.42%)
Mutual labels:  audio, ffmpeg
Axiom
An FFmpeg GUI for Windows
Stars: ✭ 560 (-38.53%)
Mutual labels:  audio, ffmpeg
Itunes store transporter
Upload and manage your assets in the iTunes Store using the iTunes Store’s Transporter (iTMSTransporter).
Stars: ✭ 117 (-87.16%)
Mutual labels:  automation, audio
Ffmpeg
Mirror of https://git.ffmpeg.org/ffmpeg.git
Stars: ✭ 27,382 (+2905.71%)
Mutual labels:  audio, ffmpeg
Ffmpeg Normalize
Audio Normalization for Python/ffmpeg
Stars: ✭ 631 (-30.74%)
Mutual labels:  audio, ffmpeg
Mpc Hc
MPC-HC's main repository. For support use our Trac: https://trac.mpc-hc.org/
Stars: ✭ 3,567 (+291.55%)
Mutual labels:  audio, ffmpeg
Mlt
MLT Multimedia Framework
Stars: ✭ 836 (-8.23%)
Mutual labels:  audio, ffmpeg
Androidffmpeg
android 读取摄像头和麦克风,使用rtmp推流
Stars: ✭ 298 (-67.29%)
Mutual labels:  audio, ffmpeg
Ffmpegcore
A .NET FFMpeg/FFProbe wrapper for easily integrating media analysis and conversion into your C# applications
Stars: ✭ 429 (-52.91%)
Mutual labels:  audio, ffmpeg
Youtube Audio Stream
youtube audio stream
Stars: ✭ 276 (-69.7%)
Mutual labels:  audio, ffmpeg
Ffsubsync
Automagically synchronize subtitles with video.
Stars: ✭ 5,167 (+467.18%)
Mutual labels:  audio, ffmpeg
Fanplayer
A portable video player based on ffmpeg for windows and android platform.
Stars: ✭ 229 (-74.86%)
Mutual labels:  audio, ffmpeg
Swiftffmpeg
A Swift wrapper for the FFmpeg API
Stars: ✭ 243 (-73.33%)
Mutual labels:  audio, ffmpeg
Trinity
android video record editor muxer sdk
Stars: ✭ 609 (-33.15%)
Mutual labels:  audio, ffmpeg
Ffmediaelement
FFME: The Advanced WPF MediaElement (based on FFmpeg)
Stars: ✭ 733 (-19.54%)
Mutual labels:  audio, ffmpeg

Tdarr V2: Distributed Transcoding System

Audio/Video Library Analytics & Transcode/Remux Automation

  • FFmpeg/HandBrake + video health checking (Windows, macOS, Linux & Docker)

RedditDiscord paypal

patreon

Setup/Installation

About:

Tdarr V2 is a closed-source distributed transcoding system for automating media library transcode/remux management and making sure your files are exactly how you need them to be in terms of codecs/streams/containers and so on. Put your spare hardware to use with Tdarr Nodes for Windows, Linux (including Linux arm) and macOS. Code in this repository is for Tdarr V1, Tdarr V2 is not open-source.

Designed to work alongside applications like Sonarr/Radarr and built with the aim of modularisation, parallelisation and scalability, each library you add has its own transcode settings, filters and schedule. Workers can be fired up and closed down as necessary, and are split into 4 types - Transcode CPU/GPU and Health Check CPU/GPU. Worker limits can be managed by the scheduler as well as manually. For a desktop application with similar functionality please see HBBatchBeast.

  • Cross-platform Tdarr Nodes which work together with Tdarr Server to process your files
  • GPU and CPU workers
  • Use/create Tdarr Plugins for infinite control on how your files are processed: https://github.com/HaveAGitGat/Tdarr_Plugins
  • Audio and video library management
  • 7 day, 24 hour scheduler
  • Folder watcher
  • Worker stall detector
  • Load balancing between libraries/drives
  • Use HandBrake or FFmpeg
  • Tested on a 1,000,000 file dummy library
  • Search for files based on hundreds of properties
  • Library stats
  • Hardware transcoding container (install Nvidia plugin on unRAID/Nvidia runtime container on Ubuntu)


Transcode management

Screenshot

Stats

Screenshot

Search

Screenshot

Plugins

Screenshot

Tdarr is extremely modular/configurable and the main idea behind it is creating a plugin stack to clean up/standardise your files. For example, a typical plugin stack might look like this:

(1) Transcode non hevc files into hevc

(2) Remove subs

(3) Remove meta data (if title)

(4) Add aac stereo audio if none (eng preferred)

(5) Remove closed captions

In this example, plugins 1,2,3 and 5 are community plugins which are available for you to use immediately. Plugin 4 can be created in the plugin creator interface in Tdarr and will appear as a local plugin.

Each of the plugins are conditional, so are only used if needed. They are located in Tdarr/Documents and are written in JavaScript so if none of the plugins do what you want then you can modify/create new plugins if you have a bit of coding experience (or get the gist from having a look). Steps for doing so are in the README here:https://github.com/HaveAGitGat/Tdarr_Plugins . Ask for help in the Discord channel if need be.

Here is an illustration of how the plugin stack works:

https://i.imgur.com/483AakN.png

For the term 'streams', here is an example of how a file appears in Tdarr search results:

https://i.imgur.com/RaKnq2c.png

That file has 3 streams - a video, audio and subtitle stream. Subtitles and closed captions are very different. Where is the closed caption data in this example? It's embedded inside the h264 video stream.

Extra streams and closed captions which you don't need can cause problems with direct playing and syncing files, so you might as well remove them (I recommend using Bazarr for subtitles). Even when playing files in programs such as VLC or Kodi, subtitles/closed captions can cause playback delays and make things stuttery for a few seconds when jumping around the video.

Extra streams can also take up a lot of space. Don't be surprised to see some files in your library with 15+ audio/commentary/subtitle tracks in a bunch of different languages . These can take up an extra GB+ per file.

The plugin creator is split into 'Filters' and 'Actions'. Filters encapsulate the actions, so the actions will only be carried out if the filter conditions are met.

Current filters:

Filter by codec

Filter by medium

Filter by age

Filter by resolution

Filter by size

Current actions:

Transcode - HandBrake basic options

Transcode - HandBrake/FFmpeg custom arguments

Transcode - Standardise audio stream codecs

Transcode - Add audio stream

Transcode - Keep one audio stream

Remux container

Some actions/plugins have built-in filters (specified in the plugin creator). This means they'll automatically detect if a file needs to be processed or not (such as the remove subtitles community plugin). Additional filters can be added.

Some of the actions have become quite complicated so take a bit more time. For example, the 'Keep one audio stream' has 16 different outcomes as it tries to determine the best audio stream to keep based on the codec, language and channel count you specify.

If you have a request for a new filter/action, then try and think of it generically so I can implement it in way that other people can configure and apply it to their (slightly) different circumstances. Request on GitHub,Reddit or Discord.

I like to maximise the chance of direct play, so my plugin stack looks like this:

(1) If not in h264, transcode into h264 [h264 is a more universal video codec than others]

(2) If not in mp4, remux into mp4 [mp4 is the most universal container]

(3) Remove subs

(4) Remove closed captions

(5) Add aac stereo audio if none (eng preferred) [very universal audio codec/channel count]

(6) Remove meta-data if title meta detected [Stops annoying titles appearing in Plex]
Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].