selur.de

What is Hybrid?

Hybrid is a Qt-based front end for a collection of separate encoding, filtering and muxing tools. It is a desktop application that converts many input formats into common audio and video formats and containers, and it deliberately targets advanced users rather than beginners. The author states plainly that it is not meant for people who need a wizard-like interface or who are unfamiliar with containers and video formats.

In practice, you use it to drive encoders and muxers from one window instead of typing long command lines. It accepts raw VC-1, AVC, MPEG-2 and MPEG-4 ASP files, plus AVS scripts and almost anything MPlayer or FFmpeg can decode. It also supports tagging for AVI/MKV/MP4/MOV, chapters for MKV/MP4/Blu-ray, subtitles for the same three, separate audio, video, filter and combined profiles, and an integrated bitrate calculator.

What it can produce

Audio encoding can run through dcaenc, MEncoder, FFmpeg, Aften and several AAC encoders (qaac, FDK AAC, faac, fhg, neroaacenc). Filtering goes through VapourSynth, AviSynth on Windows only, and some basic FFmpeg filters. Work is organised as jobs in a queue, and single titles or chapters can be encoded on their own. Pass-through of audio and video means the same tool can be used purely for muxing, tagging and chapter editing, and there are automation options on top.

Who it suits

A good fit is someone converting a disc rip or camera file into a tagged MKV with chapters and a chosen codec, who wants to queue several jobs and walk away. A poor fit is someone who wants to drop in a file and click one button.

If you are unsure, try one small job first: load a short clip, pick an MP4 or MKV container, choose a video and audio codec, and check the bitrate calculator's output before committing a long queue. The official project page is Main.

How do I install Hybrid on my computer?

Hybrid is a Qt-based frontend that drives a collection of separate encoding, muxing and filtering tools, and it is explicitly aimed at advanced users rather than people who want a wizard-style interface. That shapes how you install it: you are not installing one self-contained app, you are setting up a graphical shell plus the underlying binaries it calls on.

What installation involves

• The Hybrid application itself — a Qt frontend. Because it is Qt-based, your system needs a working Qt runtime, which on most Linux distributions comes from your package manager and on Windows is normally bundled with the build.
• The external tools Hybrid delegates to — its own feature list names a wide set: FFmpeg, MEncoder, x264, x265, vpxenc, aomenc, rav1e, kvazaar, various NVENC/QSV/VCEEnc encoders, plus AAC encoders such as qaac, FDK AAC, faac, fhg and neroaacenc, and filtering through Vapoursynth or Avisynth (Windows only).
• Optional extras — Avisynth filtering is Windows-only, so that part of the chain is not available elsewhere. Some encoders (for example hardware NVENC/QSV paths) depend on your GPU and drivers rather than on Hybrid itself.

Because the tool set is broad and partly platform-specific, the practical route is to start from the download and setup information on the project's own site, Main, and follow its instructions for your operating system rather than assembling the pieces by guesswork. If a build is offered for your platform, that is the shortest path; otherwise you install the frontend and then point it at the external binaries you already have.

A realistic first-run check

Pick one simple job to confirm the chain works end to end: load a short clip, choose a container such as MKV or MP4, select one video encoder you know is installed, and run it through the job/queue system. If it fails, the missing piece is usually an external binary rather than Hybrid itself — the frontend can only call tools that exist on your machine.

Decision criterion

If you are comfortable naming containers, codecs and encoder backends, installing Hybrid and its dependencies is worthwhile. If you would rather not manage that, this is the wrong tool by its own description — a wizard-driven converter will get you to a finished file with far less setup.

Can Hybrid convert Blu-ray or AVCHD files to MP4 or MKV?

Yes. Hybrid is built to convert Blu-ray and AVCHD structures to MP4 or MKV, and to work with the streams inside them.

What it can do with Blu-ray/AVCHD

• Accept Blu-ray or AVCHD structures as input, plus raw VC-1, AVC, MPEG-2 and MPEG-4 ASP video streams.
• Output MP4/MOV/MKV/M2TS/WebM/AVI, or a Blu-ray/AVCHD structure.
• Encode or pass through audio and video: you can mux and tag without re-encoding, or re-encode to formats such as x264/x265, VP8/VP9, AV1, AAC, AC-3, DTS, FLAC or Opus.
• Handle chapters: automatic or manual creation, pass-through, and encoding a single title or individual chapters.
• Use a job/queue system, so a multi-title disc can be processed in batches.

Practical workflow For a Blu-ray disc, point Hybrid at the disc structure, let it detect the main title and playlists, choose MKV or MP4 as the container, then decide per stream whether to pass through or re-encode. Pass-through is faster and keeps original quality but leaves large files; re-encoding to H.264/H.265 shrinks them at the cost of time and some quality. MP4 is the safer choice for phones, TVs and editing apps; MKV is more flexible for multiple audio tracks, subtitles and chapters.

Who this is for The developer states Hybrid targets advanced users and is not a wizard-style tool for beginners. If you are comfortable with containers, codecs, bitrates and filters, it gives fine control. If not, a simpler GUI transcoder will be less frustrating. For a broader look at the project, see Hybrid.

Next step Try a short chapter or one title first: pass through video, convert audio to AAC, output MKV, and check sync and subtitle placement before queueing the whole disc.

What video and audio encoders does Hybrid support?

Hybrid is a front-end, not an encoder itself: it drives external encoder tools and muxers, so the list of supported codecs is effectively the list of tools it can call. Per its own feature list, it targets advanced users who already understand containers and formats, and it explicitly is not a wizard-style tool for beginners.

Video output formats

That spread matters in practice: you can pick a software encoder for quality and compatibility, or a hardware path (NVENC, QSV, VCE) when speed matters more than file size. Hybrid also accepts raw VC-1, AVC, MPEG-2 and MPEG-4 ASP input, plus AviSynth scripts and essentially anything MPlayer or FFmpeg can decode.

Audio output formats

DTS, AC-3, Ogg Vorbis, MP3, AAC, FLAC, PCM, Opus, and E-AC-3, with pass-through supported. AAC encoding can go through qaac, FDK AAC, faac, fhg or neroaacenc; other audio is handled via dcaenc, MEncoder, FFmpeg or Aften.

Containers and what they enable

Output containers are mov, mp4, mkv, m2ts, webm, avi, plus Blu-ray or AVCHD structures. Because audio and video pass-through is supported, Hybrid doubles as a muxing, tagging and chapter-editing tool — useful if you only want to remux a file into MKV with proper chapters rather than re-encode it.

A practical next step: decide your target playback device first, then work backwards. If it's a modern TV or phone, MP4 with H.264 or HEVC video and AAC audio is the safe combination; for archival on a PC, MKV with FLAC audio and a slower software encoder such as x265 will give you smaller files at the cost of much longer encoding time. More detail is on Main.

How do I use Hybrid's job queue for batch processing?

Hybrid's job queue is the core of its batch workflow: you configure one encoding job, add it to the queue, then repeat for each further file and start the queue once. Jobs run sequentially in the order listed, so you can set up a whole evening's conversions and walk away. This is a deliberate design choice for advanced users — the page states plainly that Hybrid is not aimed at people who want a wizard-style interface, so the queue assumes you already understand containers, codecs and profiles.

The practical routine

1. Load a source file and set your container, video encoder, audio encoder, filters and chapters.
2. Add the job to the queue rather than starting it immediately.
3. Change the source (or adjust settings) and add the next job.
4. Repeat until the queue covers everything you need.
5. Start the queue and let it process jobs one after another.

Why separate profiles matter here

Hybrid supports separated audio, video, filter and combined "a/v-combi" profiles, which is what makes batch work tolerable. Instead of re-entering the same x265 and Opus settings for every episode, you save a profile once and apply it to each job. For a TV-season conversion, that means one video profile, one audio profile, and only the source file changes between queue entries. Chapter creation can be manual or automatic and passed through, so episodic discs with existing chapters don't need re-authoring per file.

A concrete scenario

Suppose you have ten camera clips to standardise into MP4 with AAC audio and consistent chapters. Load clip one, choose MP4 as the container, pick an AVC encoder such as x264, select an AAC encoder, set the bitrate with the integrated calculator, save that as a profile, add to queue — then repeat for clips two through ten. Start the queue and check the first output before leaving it unattended, since a wrong pixel format or filter setting would otherwise repeat across all ten.

Trade-offs to weigh

• Sequential, not parallel: the queue processes jobs in order, so a long job blocks the rest. If you need throughput, consider running separate instances rather than expecting the queue to parallelise.
• Advanced-only controls: the same depth that enables precise batch encoding also means a misconfigured profile propagates across every job. Test on one short clip first.
• Toolchain dependency: Hybrid is a frontend for external encoders and tools (x264, x265, FFmpeg, AviSynth/VapourSynth and others), so missing binaries break jobs mid-queue.

For documentation and the full feature list, see Main. If you are new to containers and codecs, build familiarity with a single manual encode before relying on the queue for a large batch.

Is Hybrid suitable for beginners or do I need advanced video knowledge?

Hybrid is aimed squarely at advanced users, not beginners. The site itself is explicit: it is a Qt-based frontend for a collection of other tools, and it is "not intended to please amateurs who need a wizard-like interface." If you don't already understand containers and video formats, it says Hybrid is not meant for you.

What that means in practice

• You are expected to know the difference between a container (MKV, MP4, M2TS, WebM, AVI, Blu-ray/AVCHD structures) and the codecs inside it.
• You choose video encoders yourself (x264, x265, VP8/VP9, AV1 via aomenc or rav1e, ProRes, FFV1, and hardware variants) and audio encoders (AAC, MP3, AC-3, DTS, Vorbis, Opus, FLAC, PCM).
• Filtering is largely your responsibility, through Vapoursynth, Avisynth (Windows only), or basic FFmpeg filters.
• Work is organised as jobs in a queue, with separate audio, video, filter and combined profiles.

Who it suits

A good fit is someone converting or remuxing existing material who wants precise control: choosing chapters, tagging, pass-through of audio or video, encoding a single title or selected chapters, and automating repetitive jobs with profiles. A poor fit is someone who just wants to drop in a file and press one button.

A concrete scenario

Say you have a Blu-ray rip and want an MKV with x265 video, FLAC audio, preserved chapters and correct tags. Hybrid exposes exactly those choices. If instead you don't know whether you want MP4 or MKV, or what CRF means, you'll spend more time reading documentation than encoding.

Decision criterion

Ask yourself: can I name the container and codec I want, and explain why? If yes, Hybrid's control is an advantage. If no, start with a simpler GUI encoder and come back once the terminology is familiar.

Next step

Read the general feature list on Main and check whether the encoders and containers you need are covered. If several terms there are unfamiliar, that's your signal to learn the basics first.