User’s Guide
Version v1.09 · Forensic Subtitle & Audio Track Intelligence

How to use every part of Sublutions+, and why each part works the way it does.

Table of Contents

About Sublutions+

Why Sublutions+ exists

Other tools give you functions to apply. Sublutions+ solves the specific pain points of running a home media server — automatically, with an override for every edge case.

Every feature in Sublutions+ started as a real problem in a real Plex library:

How it behaves, everywhere

1. What Sublutions+ Does

In one sentence

Sublutions+ takes the video files you download or rip and turns them into clean, correctly labeled files that play right on every device: the right subtitles in the right roles, audio that every device can play and every viewer can hear, and metadata without spam.

The tools

Everything happens in one window. The four tools are tiles in the dock along the bottom:

ToolWhat it's for
BuilderThe main tool. Plan every track of every file in a batch, then build clean output files.
Metadata OnlyFix tags, titles, flags and cover art in place. No re-encode, and in seconds for MKV.
External SubtitlesClean subtitle files on their own (no video): remove duplicates, make a dialogue-only track from SDH.
PreferencesSettings for this PC: output folder, hardware, audio language, track titles and more.

Every file planned on its own

No two files in a library are alike. One movie has Dolby Atmos and a commentary track, the next has a single stereo track and three SDH files. A single set of choices for a whole batch forces compromises. In Sublutions+ every file gets its own plan for every stream — video, each audio track, each subtitle — and you can copy one file's plan to others (a TV season, for example) in two clicks. See Copy and paste settings.

What happens to a file

When you add a video, Sublutions+:

  1. Reads it — duration, every stream, codecs, languages, titles and flags (a quick background read so a large batch stays usable in seconds).
  2. Analyzes it forensically when you open the file (or at Start for files you never opened) — reads the text of every subtitle track to decide which is Forced, dialogue-only or SDH (see How subtitles are identified), and checks for in-band ATSC closed captions (CEA-608) with a short sample.
  3. Builds a plan — what the output will contain, using Sublutions' defaults and your Preferences. You review and change it on the Builder.
  4. Processes it when you press Start — detects audio language if needed, cleans the subtitles, encodes or copies the streams, checks the output, and prepares MKV files for tagging apps.

Nothing is written until you press Start, and nothing you already have is lost along the way.

2. Before You Start

What's in the folder

Sublutions+ is a portable app: everything it needs is in its own folder. Copy the whole folder anywhere — another drive, another PC — and run Sublutions+.exe. Nothing is installed into Windows.

In the folderWhat it is
Sublutions+.exeThe app.
src\ffmpeg.exe, src\ffprobe.exeThe tools that read, encode and write video and audio.
src\Whisper\The speech model Sublutions+ uses to detect the spoken language of audio tracks.
src\mkvtoolnix\mkvmerge and mkvpropedit, used to edit MKV files in place and to prepare them for tagging apps (license in COPYING.txt).
src\wordlists\Word lists the blacklist uses to tell common words, real words and made-up release names apart (credits in Word list credits).
sublutions_blacklist.txtYour list of release-group spam words and phrases (see The blacklist).
Docs\This guide and the Change Log.
_internal\Parts of the app itself. Leave it alone.

Files the app creates

FileWhat it is
src\settings.jsonYour Preferences. Created on first launch. Delete it to start over with the Welcome page.
src\ui_state.jsonWindow size and position, theme, the last folder you worked in.
src\jobs\Temporary work folders while files are analyzed and processed. Cleared when you close the app.

Moving to another PC

Copy the whole folder. On the new PC:

3. First Launch

Welcome to Sublutions+

The first time you start Sublutions+ (or whenever src\settings.json is missing or unreadable), the app opens on a Welcome page inside the main window. It's made of the same cards you'll find later in Preferences, so it already looks and works like the rest of the app.

Why only a few choices: two decisions and you're working. Everything else starts with Sublutions' defaults, and every one of them can be changed later in Preferences.

  1. Output folder — click Browse and choose the folder where finished files should go. The path appears in the box as soon as you pick it (you do not have to wait for Start using Sublutions+). This is required. Each file can still be sent somewhere else later (see Per-file output folder).
  2. Hardware — Sublutions+ has already found the graphics card driving your display and shows it as "Detected: …". Leave the Encoder preset as it is unless you know you want something else (see Hardware).
  3. Windows integration (installed app only) — tick Show in Windows Open with menu if you'd like to right-click a video in File Explorer and send it to Sublutions+. Off by default.
  4. Click Start using Sublutions+ in the bottom-right tile.
The Welcome page: choose the output folder, check the encoder, then Start using Sublutions+
The Welcome page: choose the output folder, check the encoder, then Start using Sublutions+

If the output folder is missing you'll see "Choose a default output folder first."; if the folder you chose no longer exists, "The output folder doesn't exist: …". Once setup is saved, the Builder opens.

While the Welcome page is open, the other dock tiles are locked. Files you open during setup (for example with Open with) are added to the batch as soon as setup is finished.

Already running

If you start Sublutions+ while it's already open — or use Open with on a video while it's open — a window asks what to do:

Why: a second double-click is usually an accident, and two copies processing at once compete for the same graphics card. When you really want two, it's one click away.

Interrupted last run

If Sublutions+ was closed, or Windows shut down, restarted or signed you out, while files were processing, the next start shows a one-time notice. Leftover temporary files from that run are removed automatically; files that had already finished are kept.

Language Detection Required

Sublutions+ identifies subtitle languages by reading their text. If the language-detection data inside the app is missing or damaged, the app shows Language Detection Required and won't run. This should never happen with a complete copy of the folder; copy the folder again from the original.

Cleanup at start and close

Each time the app starts and closes it sweeps away leftover temporary encode files from the app folder, the output folder and the last folder you worked in, so an interrupted run never leaves gigabytes of half-written files behind.

4. A Tour of the Window

The layout

Sublutions+ is one window that never changes shape:

The Sublutions+ window: the batch on the left, the Builder in the middle, the dock along the bottom
The Sublutions+ window: the batch on the left, the Builder in the middle, the dock along the bottom

Why one screen: a tool you can't see is a tool you forget. Every job the app does is in view all the time and one click away, and the batch, the dock and the run button always stay where they are. There are no pop-up windows for tools, preferences or processing.

Day/night switch

The small switch at the top right flips between the dark and light appearance: a sun in a blue sky for light, a crescent moon in a starry sky for dark. Your choice is remembered. It's locked while files are processing.

The dock

Six tiles of the same size sit side by side along the bottom. The tool you're on is outlined.

The dock: the View switch, one tile per tool, and the run tile
The dock: the View switch, one tile per tool, and the run tile
TileWhat it does
ViewThe Current / Planned / Compare switch for the Builder (see Current, Planned and Compare). Greyed on the other tools.
Builder"Plan every track, build clean files" — see The Batch.
Metadata Only"Fix tags and titles. No re-encode." — see Metadata Only.
External Subtitles"Clean subtitles, make dialogue-only" — see External Subtitles.
Preferences"Output, hardware and title standards" — see Preferences.
Run tile (green, always last)Starts the job for the tool you're on, and says what it will do.

Why one dock: every tool is one click away and opens right in the workspace. There's no separate utilities window to find, no menu to dig through, and nothing to close before you get back to work. Your batch and every file's plan stay exactly as you left them while you use another tool, so you never lose your place.

The file comes with you. The file selected in the batch is the file the tools work on. Select a file in the Builder, click Metadata Only, and that same file is already open in the editor; click back to Builder and it's still selected. Fixing a file's tags in the middle of planning it is two clicks, with no file dialog in between (see Opening a file).

The run tile

The last tile always tells you what will happen when you click it:

You're onThe tile reads
Builder or PreferencesStart Processing · "4 files · planned settings" (greyed, "Add files to begin", when the batch is empty)
Metadata OnlyRun Metadata Only, Write N changes once you've edited a file, or Write changes to N files (orange) once you've edited more than one (see Writing the changes)
External SubtitlesRun External Subtitles · "Saved beside the subtitle files"
Welcome pageStart using Sublutions+ · "Saves these settings"
ProcessingAbort (red) · "Stop this run" (see Aborting)
FinishedRun complete · "Review the results, then Done"

While files are processing the other tiles and the day/night switch are locked and faded, so nothing can change under a running job.

Remembered between sessions

Sublutions+ remembers the theme, the window's size and position (and whether it was maximized), and the last folder you browsed to or dropped files from. + Add files and every Browse button share that folder, so they open where you last worked. A slot that already holds a file opens in that file's folder instead.

5. Your First File, Start to Finish

The short version

This walk-through takes one movie from download to a clean file in your library. Every step links to the full explanation.

  1. Add the file. Drag the video onto the window, or click + Add files on the Builder. It appears in the batch on the left with its duration, video codec and audio summary. See Adding files.
  2. Let it analyze. Click the file. Its line in the batch reads "Analyzing subtitle 3 of 12" with a small progress bar while Sublutions+ reads every subtitle track. A file with many tracks takes a few seconds. See Analysis progress.
  3. Review the plan. The workspace shows Planned: one card for the video, one for each audio track and one for each subtitle role Sublutions+ found. The defaults are usually right. See Video, Audio and Subtitles.
  4. Change what you want. Burn or Mux the forced subtitles, discard a commentary track, boost quiet dialogue, add a stereo track for the TV, drag tracks into the order you like.
  5. Check Compare. Click Compare in the View tile to see the source file and the planned output side by side, with every change in orange. See Compare.
  6. Start. Click Start Processing (bottom right). The screen shows each step, the time elapsed and remaining, and the speed. See Processing.
  7. Done. When the run finishes, review the results and click Done. The batch clears, and the output folder opens if you've asked for that in Preferences. See Results and Done.

What to look at first

For most files three things deserve a glance before you start:

6. The Batch

What the batch is

The left side of the Builder lists every video you're working on, headed "BATCH · N FILES". Each file keeps its own plan; Start Processing processes them all, one after another, each with its own settings.

Why a batch: add a whole season or a night's worth of downloads, plan them, press Start, and walk away.

Adding files

New files are added to the end of the batch. The left list stays still: from an empty batch the first file stays selected and loads in the Builder; appending more files keeps the file you already had selected and your scroll position while rows finish reading. Each row appears at once with Reading file… while the quick stream read runs in the background; the window stays responsive. When the read finishes, the row shows duration, codec and audio summary. In-video captions are checked later (when you open the file or at Start), not while adding the whole batch. Start Processing waits until those quick reads finish. Unreadable files stay in the queue with an error on the row until you remove them. Supported files: .mkv .mp4 .m4v .mov .avi .wmv .asf .ts .m2ts. The app confirms with "Added N files to the queue."

When the batch is empty the list reads "Drag video files here or click + Add files".

You can also send a file from File Explorer with right-click → Open with → Sublutions+, once that's turned on in Preferences → Windows integration.

Each file's line

Each file shows a short session label, not the full release filename. TV episodes use three lines — series name, S01E07 · Episode Title, then duration, video codec and an audio summary ("1 audio (5.1)" or "3 audio"). Plex-style movies show Title (Year) plus that same detail line. Hover the label for the full release filename. The batch list grows a little on a wide or fullscreen window so the labels stay readable.

The icon matches the media type: a TV for episodes, a film frame for movies, a camera for other video. Files that Sublutions+ boosted before are marked already boosted (see Boost).

Analysis progress

Every file is read as soon as it's added: duration, streams, codecs. The full forensic analysis — reading every subtitle track — runs when you first click the file. Files you never click are analyzed when you press Start Processing.

While a file is being analyzed its line reads "Analyzing subtitle 7 of 44" in the accent color, with a small progress bar, then returns to the normal details.

Why it takes a moment: to tell a forced track from a full dialogue track, Sublutions+ has to read them. Releases with 40 or more subtitle tracks take a few seconds, longer over a network. The line shows the app is working and how far along it is.

Selecting files

Several actions work on every selected file at once: Paste settings, Remove and, in Metadata Only, Apply Sublutions standards. Selecting is how you tell them which files.

ToDo this
Show one fileClick it. The file you click is the one shown in the workspace.
Add a file to the selection, or take it outCtrl-click it. The file on display stays shown and stays selected.
Select a run of filesClick the first, then Shift-click the last. Everything between is selected.
Add a run to what's already selectedCtrl+Shift-click.
Select every fileCtrl+A (click in the batch first), or right-click a file → Select all files.
Select a group with the mouseDrag from the space beside or between the files, as in Windows Explorer. A box follows the pointer and every file it reaches is selected; drag past the top or bottom of the list and it scrolls along. The file shown in the workspace stays shown.
Add a group, or take files outCtrl+drag. Files the box reaches switch: unselected ones are added, selected ones are taken out.
Keep just the file shownClick the empty space beside the files.
Copy or paste settings, re-analyze subtitles, remove filesRight-click a file.

Can't remember? Hover anywhere over the batch list: a tooltip lists every gesture.

The mouse wheel and arrow keys only scroll the list; they never change the selection. On a touchscreen, dragging a finger scrolls the list, and pressing and holding a file opens the right-click menu (with Select all files).

Removing files

Select one or more files and click Remove, or press Delete. Right-click offers Remove this file (or Remove N files) and Clear entire queue. The app confirms with "Removed N files from the queue." or "Queue cleared."

Removing a file from the batch never touches the file on disk. If a file you're removing has Metadata Only edits that haven't been written, the app asks first ("Remove and discard" or Cancel). Closing the app asks the same way.

Copy and paste settings

Why: the episodes of a TV season usually share one layout. Plan one episode, then give every other episode the same plan in two clicks.

  1. Right-click the file you've planned and choose Copy settings. The app says "Settings copied from NAME. Ctrl-click or Shift-click other files, then right-click → Paste settings."
  2. Select the files that should get the same plan (Ctrl-click, Shift-click or Ctrl+A).
  3. Right-click and choose Paste settings to N files.
Settings copied from episode_04; right-clicking episode_05 offers Paste settings to 1 file
Settings copied from episode_04; right-clicking episode_05 offers Paste settings to 1 file

What pastes: the video card, container, subtitle choices and subtitle format always paste. Audio settings paste only to files whose audio streams match — the same number of streams, with the same channels and languages in the same order. Files that keep their own audio are named: "Audio not copied to … (different audio streams)."

Why audio is guarded: pasting "track 2 = commentary, discard" onto an episode whose track 2 is the main audio would silently ruin it. Pasting a 5.1 plan onto a stereo file, or an English-first order onto a Spanish-first file, would do the same. The app refuses and tells you which files it skipped.

If you choose Paste with nothing copied: "Nothing to paste. Right-click a file and choose Copy settings first."

Re-analyze subtitles

Why: forensic subtitle identification runs when you first open a file (or when processing starts on a file you never opened). If you change Preferences → Subtitle ordering after files are already in the batch, remove-and-re-add is not required — right-click the batch and choose Re-analyze selected file (or Re-analyze N selected files), or Re-analyze all files in batch to refresh every queued file. The app confirms with Re-analyzing N files… and shows Analyzing subtitle N of M on each row while it works, one file at a time. Re-analyze is not available during a processing run.

Files added while processing

You can keep adding files while a batch is processing. They're queued and processed after the current run.

7. Current, Planned and Compare

The View tile

The first tile in the dock switches the Builder's workspace between three views of the selected file:

ViewWhat it shows
CurrentWhat's in the source file now. Read-only.
PlannedYour choices for the processed file. This is where you make changes.
CompareThe two side by side, with every change highlighted. Read-only.

Why: an encode can take an hour. Seeing exactly what you'll get — every track, title, flag and order — before you press Start means no surprises after.

The title block

At the top of the workspace:

Current

Current shows the source file exactly as it is: the video stream; each audio stream's codec, channels, language and title; and each subtitle stream's format, language, flags and title.

After the analysis, each subtitle card adds a Forensic line with what Sublutions+ found inside the track, for example "Forced · 11 lines · ara". Comparing that line with the track's title is often the quickest way to see that a release is mislabeled.

External subtitle files you add appear only in Planned, because they aren't in the source file.

Current: the source file as it is today, read-only
Current: the source file as it is today, read-only

Compare

Compare is a read-only page with the Source file on the left and the Planned output on the right, row by row, grouped like the cards:

Compare: the source file on the left, the planned output on the right, with every change highlighted
Compare: the source file on the left, the planned output on the right, with every change highlighted

How to read it:

Compare follows the batch: click another file and Compare shows that one. Change something in Planned, switch back, and Compare shows the new plan.

Why you can trust it: Compare is built from the same forensic analysis and the same final plan that processing uses. What you see is what will be written, not an approximation.

While the file is still being analyzed Compare says "Analyzing the file… Compare appears here as soon as the analysis finishes." and fills in by itself. A file that can't be analyzed says so and why. During processing Compare reads "Compare is available again when processing finishes."

8. Video

The video card

The Video stream 1 card shows the source video (codec, resolution, frame rate and bit depth, 8-bit or 10-bit) and your choices for the output.

The video card: an H.264 source planned as HEVC, with a moderate size reduction on the hardware encoder; Preserve existing tags and cover art at the top right
The video card: an H.264 source planned as HEVC, with a moderate size reduction on the hardware encoder; Preserve existing tags and cover art at the top right

Why it works this way: every re-encode costs time and some picture quality. Sublutions+ copies the video untouched unless something truly requires a re-encode, and when it must re-encode, you decide how much to trade quality for size.

Container

Sync with Source (default), MKV, MP4 or M4V.

See Containers and soft subtitles.

Output codec

Sync with Source (default), H.264 (AVC), HEVC (H.265), AV1, H.266 (VVC), VP9.

CodecWhen to choose it
Sync with SourceKeep what the file has. The usual choice.
H.264 (AVC)Plays on everything, including old devices. Larger files.
HEVC (H.265)About half the size of H.264 at the same quality. Plays on most current devices.
AV1Smaller still; newer devices only. MKV only.
H.266 (VVC)Placeholder — see below. MKV only.
VP9Mainly for web players. MKV only.

While functional, H.266 (VVC) produces a real file, but for a home library today it's basically pointless except curiosity. It sits in the list as a placeholder for when encode speed, consumer hardware and media-server Direct Play catch up; for now that stack mainly serves commercial streaming and broadcast, not a Plex-style library. Encoding is software-only — far slower than HEVC on the same PC (hours for a feature film, not minutes). Plex and similar servers will not Direct Play it: expect a full video transcode, or no play, on typical clients. Only a handful of players can play it at all, and some of those need extra or experimental add-ons. Prefer HEVC or AV1 when you want a modern, smaller encode.

Choosing a codec different from the source re-encodes the video. Switching the container to MP4 or M4V resets AV1, H.266 and VP9 to Sync with Source. Codecs your copy of FFmpeg can't encode aren't offered.

Resolution

Sync with Source (default), or a smaller tier: 2160p, 1080p, 720p or 480p — only tiers narrower than the source are offered. Each keeps the source's shape, for example "720p · 1280×534".

Why only smaller: upscaling adds file size, not detail. Downscaling is useful for devices with small screens or a slow connection to your server.

Choosing a resolution re-encodes the video. Burned-in subtitles keep their proportions.

Frame rate

Shown for reference; it can't be changed. Changing the frame rate causes stutter and audio sync problems.

Reduce file size

Shown only when the video will be re-encoded: None, Moderate, Large, Extreme. The default is Moderate on every file.

ChoiceWhat you get
NoneNear-lossless (quality 18). The picture is as close to the source as an encode can get; the file may even grow. Choose it when quality matters more than space.
ModerateA noticeably smaller file that looks the same as the source on almost all content.
LargeMuch smaller; fine detail and dark scenes may soften.
ExtremeSmallest; visible artifacts are likely on complex scenes.

Why no size is promised: each choice sets a picture quality, not a file size. How much smaller the file gets depends entirely on the file itself. The same choice can save 10% on one file and 80% on another. A generously encoded web download shrinks a lot; a file that is already tightly compressed barely shrinks at all. That's why Sublutions+ doesn't show percentages or a planned file size: any file size estimation would be highly unreliable.

Reduce file size never causes a re-encode by itself. When nothing else requires one, the video is copied untouched and this choice is hidden (see When the video is re-encoded).

Bit depth

Shown only when the source is 10-bit and the video will be re-encoded: 10-bit (the default) or 8-bit.

An 8-bit source never shows this choice: converting 8-bit up to 10-bit adds nothing. With H.264 output the box reads "8-bit (H.264 is always 8-bit)", because H.264 is 8-bit on graphics-card encoders and most players. When the video is copied untouched, it keeps the source's bit depth.

Hardware encoder (faster)

Shown only when the video will be re-encoded. On uses the encoder on your graphics card (NVIDIA, Intel or AMD), which is many times faster than encoding on the processor. Off uses software encoding, which is slower but works on every PC. The speed/quality balance of each comes from Preferences → Hardware.

When the video is re-encoded

The video is re-encoded only when one of these is true:

Otherwise it's copied bit for bit, which is fast and loses nothing. Compare's Video section shows which applies ("Burn-in (re-encode)", for example).

Preserve existing tags and cover art

The checkbox at the top right of the video card, off by default. Normally the processed file starts with no file tags and no cover art: most incoming files carry only release-group spam, and clearing it is the right default. Tick the box for a file you've already tagged (in MetaX, for example) and its tags and cover art are carried into the processed file.

Copy settings / Paste settings carries the checkbox, so a whole season can be set at once. When it's ticked, Compare shows Tags and cover art: Kept on the Planned side.

Preserve HDR

The checkbox directly under Preserve existing tags and cover art. It appears only when the file is HDR, and it is checked as soon as that file loads. A file without HDR does not show it.

Why: a re-encode that drops the file's HDR plays back flat, at the wrong brightness. Copying the video already keeps HDR, so Sync with Source never has to ask. The box is there for the encode that has to happen — a new codec, a smaller resolution, or a burned subtitle — and it gets out of the way when you want a choice HDR cannot survive.

9. Audio

The audio cards

The Audio section, headed "Audio · N source streams", has one Audio stream N card for each audio track in the source, plus a New card for each stereo track you ask Sublutions+ to create. Each card shows the source (codec, channels, language) and your choices for the output.

Why: clear titles make the right track easy to pick in the player's menu; correct language tags let players choose it automatically; a stereo companion lets every device play the file directly; and Boost fixes quiet dialogue without touching tracks that don't need it.

Order and Discard

Order sets each track's position in the output (1 is first, and usually the track players pick by default). Choose Discard to leave a track out — a commentary or a second-language dub you don't want, for example. The card disappears at once; to bring it back, remove the file from the batch and add it again.

The last remaining audio track can't be discarded. Discarding a surround track also removes the stereo track created from it.

Drag to reorder

Grab a card by its header or labels (not by a control) and drag it up or down. Neighbors move aside as you go, the Order numbers update, and the page scrolls when you reach the edge. The top card is Order 1.

Codec

Sync with Source is first and the default: the track is copied untouched. The other choices are the codecs that make sense for that source — for example AAC, AC3 (Dolby Digital) or E-AC3 (Dolby Digital Plus). Choosing one converts the track.

Why Sync is the default: copying is lossless and instant. Convert only when a device can't play the original.

Title

The title is what players show in their audio menu. Pick one of Sublutions' titles for that track — "Dolby Digital Plus (5.1 Surround)", "AAC (Stereo)", Atmos-aware where it applies — or type your own. The style of the suggested titles comes from Preferences → Track titles.

Boost

Raises the volume of that track, from 1.00 (no change) to 2.20, in steps of 0.05. A boosted track has to be re-encoded: in its own codec with Sync with Source, or in the codec you choose.

Not allowed with… Some tracks can't be re-encoded as the same kind of track. With the codec at Sync with Source, their Boost reads "Not allowed with Dolby Atmos" (or the track type below) instead of a number.

An Atmos track at Sync with Source: Boost reads "Not allowed with Dolby Atmos"; the stereo track below can still be boosted
An Atmos track at Sync with Source: Boost reads "Not allowed with Dolby Atmos"; the stereo track below can still be boosted

Excluded from Boost (with the codec at Sync with Source):

Track typeWhy it's excluded
Dolby Atmos (in Dolby Digital Plus or Dolby TrueHD)The encoder can't write Atmos. The boosted track would keep its 5.1 or 7.1 sound but lose the Atmos height information — while still being titled Atmos.
Dolby TrueHDLossless. The encoder can't write TrueHD, so the file would fail to process.
DTS-HD Master AudioLossless. The encoder can't write DTS-HD Master Audio, so the file would fail to process.
DTSThe encoder can't write DTS, so the file would fail to process.
OpusThe encoder can't write Opus as the same track, so the file would fail to process.
VorbisThe encoder can't write Vorbis, so the file would fail to process.

Every other format — AAC, Dolby Digital, Dolby Digital Plus without Atmos, FLAC, MP3 and PCM — can be boosted as itself.

To boost an excluded track, choose another Codec first (Dolby Digital Plus or AAC, for example): the track is then converted anyway, and Boost works again. A stereo track created from it follows its boost, as always (see Create AAC 2.0).

Why: a boost should make dialogue easier to hear, never quietly downgrade your best audio track or make a file fail hours into a batch.

Why: surround mixes often bury dialogue under music and effects. Boost the track you listen to and leave the rest alone. Around 1.50–1.70 is a good starting point for quiet dialogue.

Boost has no limiter. Very loud passages can clip at high settings. That's also why boosting twice is dangerous: 1.70 twice is about 2.9, and the clipping is permanent.

Already-boosted protection: whenever Sublutions+ boosts a track, it marks the output file (the tag Boost=1 in its keywords). When you add a file with that mark, its batch line says already boosted and every Boost on it is locked at 1.00. There's no way around it, on purpose: if the original is gone, there's no clean copy to go back to. Compare's Volume boost row shows what will happen.

Only files processed by Sublutions (Multi-File Pro or Sublutions+) carry the mark. A file boosted by another tool, or whose keywords were removed, can't be recognized — check those yourself.

Language and Re-detect

Choose the track's language from the list or type its three-letter code (eng, spa, jpn…).

Re-detect listens to the file's audio tracks in the background with the built-in speech model and reports on each card, for example "Detected: English (eng) · 97.2% · two samples agree".

Why: one minute of dialogue analysis has resulted in multiple incorrect language identifications. The app now samples until it reaches consensus. If the same language isn't detected twice, a third analysis determines the language title. Your language stays as it was when the samples disagree or never become sure: the card says "samples disagreed, language not changed" or "low confidence, language not changed".

With the default Audio language mode, Always detect, untagged audio is detected automatically when processing starts, so Re-detect is for checking sooner, or for re-checking a track whose tag you don't trust.

Create AAC 2.0

Shown on 5.1 and 7.1 tracks. Tick it to add a New stereo AAC card, "Created from audio stream N", with its own Order and Title. Its boost follows the track it was made from. Only one track per file can have it.

Why: TV speakers, phones and many streaming sticks can't play 5.1 or 7.1 directly, so your server has to convert the audio on the fly, every time. A stereo track in the file lets those devices play it as-is, while the surround track stays for the home theater.

What Current shows

In Current view each audio card shows the source track's codec, channels, language and the title in the file's metadata — useful for spotting a mislabeled or untagged track before you plan.

10. Subtitles

How subtitles are identified

Subtitle titles and flags in downloaded files are often wrong. A track titled "English" may be SDH; a track titled "Standard" may hold only the eleven lines of foreign dialogue that make it a forced track. So Sublutions+ doesn't trust the labels. It reads every subtitle track and decides its role from what's inside:

From that, each English track gets one of three roles:

RoleWhat it is
ForcedOnly the lines viewers need when the movie switches language — foreign dialogue and on-screen signs.
Dialogue only (Standard)Everything that's said, and nothing else.
SDHSubtitles for the deaf and hard of hearing: dialogue plus sound descriptions and speaker names.

Why this matters: a mislabeled forced track means viewers miss the foreign dialogue; a mislabeled SDH track means "[DOOR SLAMS]" for viewers who didn't ask for it. Reading the tracks gets it right regardless of what the release group called them.

When a file has a short track next to SDH and no dialogue-only track, that short track is identified as Forced — not as a short dialogue track. The Forced flag in the file is used only when the text evidence is borderline; otherwise what's inside the track decides.

Picture-based subtitles (PGS, VobSub, DVB — common on Blu-ray and DVD rips) can't be read as text, so they never fill Forced / dialogue / SDH. They get their own Planned cards: Pass through (MKV stream copy) or Discard (default). Very short text tracks can't be identified reliably and are not used as heroes.

In-video closed captions (US broadcast CEA-608 carried inside the H.264 or HEVC picture) are different again: they are not a subtitle track at all. See In-video closed captions (CEA-608).

The subtitle cards

In Planned, each role Sublutions+ found gets a card — Forced subtitle, English — dialogue only, English — SDH — with a badge showing the role. Under Prioritize English, a foreign text track can fill an empty role; those cards name the language (for example Italian — dialogue only). The note line shows the evidence, for example "Forensic: 412 cues · 18% SDH".

Before the analysis finishes, or when a track can't be used, read-only cards say so: "Analyzing…", "Analysis failed: …", or "Not kept…" (no English text under Discard non-English, or no text cues at all under Prioritize English).

The subtitle cards: an added forced file to burn in, and the dialogue-only and SDH tracks from the source to mux
The subtitle cards: an added forced file to burn in, and the dialogue-only and SDH tracks from the source to mux

Inspect a subtitle

The source line on each card — "Stream 3 · SubRip · eng", or "External · name.srt" for a file you added — is a link. Click it to open that subtitle exactly as it is in your default subtitle program.

Why: a two-second look confirms a track really is what Sublutions+ says it is before you commit to an encode.

Output: Burn, Mux or Discard

Discard removes the card at once. A burned forced card is pinned first and can't be dragged.

Burn or Mux

This is one of the most important choices for a file with foreign-language dialogue.

Burn draws the forced lines into the picture itself.

Mux keeps the forced lines as a separate subtitle track with the Forced flag.

Why Burn is the default: forced text must never be missable. Mux is one click away when you know your players handle it. On an HDR file the default is Mux instead, because a burn is 8-bit and cannot keep HDR (see Preserve HDR).

Your situationChoose
Apple TV or other players that ignore the Forced flagBurn
Not sure what your viewers useBurn
Plex, Kodi or VLC clients that handle forced subtitles wellMux
Fastest job, no change to the pictureMux

Burn size

Shown when the forced card is set to Burn: Small, Medium (default) or Large. The size scales with the video's resolution. Medium is usually the closest match to normal subtitle size in common players.

Format

Shown for muxed tracks. In MKV: SRT (default for SubRip sources) or ASS. A track that is already ASS or SSA stays ASS — you cannot change it to SRT (that would strip fonts, positions and effects). In MP4 and M4V, subtitles are always mov_text.

Why SRT is the default for SubRip: styled ASS subtitles often force Plex clients to transcode the whole video just to draw them. SRT plays directly almost everywhere.

Title

Shown for muxed tracks: the role's standard title from Preferences → Track titles, or type your own.

Generate dialogue-only from SDH

Shown on the English SDH card when there is no kept dialogue-only track (none in the file, or you Discarded the dialogue card); on by default. Sublutions+ builds a clean dialogue track from the SDH by removing sound descriptions and speaker names.

While it's ticked, the Planned view shows the new track as an English — dialogue only card marked NEW, "Created from the SDH subtitle", just above the SDH card, where it goes in the file. Its format follows the container (SRT in MKV, mov_text in MP4), and you can change its title. Untick Generate to leave it out.

English SDH only. When the hero SDH is another language (Arabic, Italian, …), Generate is hidden and never runs. The cleanup that strips "[DOOR SLAMS]" and speaker labels is shaped for English; applying it to a foreign SDH does not make a good dialogue-only track.

Discard dialogue, then Generate. If a dialogue track is already in Standard and you want English dialogue-only from SDH instead, set that dialogue card to Discard. Generate appears on the English SDH card; processing leaves the discarded stream out and muxes the new dialogue-only track in its place (tagged with the SDH's language).

Prioritize English + foreign heroes. With Prioritize English, adding or assigning an English SDH should not erase the track that was in that slot. A displaced embedded SDH (Arabic, for example) moves to Other subtitles — still Mux. A non-English dialogue hero in Standard moves to Other too, so English stays first: Generate on fills Standard with English dialogue-only; Generate off leaves Standard empty so English SDH is the first subtitle stream (Italian/French/Arabic stay in Other after it). Unticking Generate does not put foreign dialogue back ahead of English. Undo the external English SDH and the displaced heroes return. With Discard non-English, foreign tracks were never kept as heroes, so this step does not apply.

Why: many English releases include only SDH. Viewers who don't need "[door slams]" and speaker labels get a clean dialogue track without hunting for one online. Under Prioritize English, bringing in an English SDH for that purpose should still let English own the Standard slot without throwing away the foreign dialogue your household may want.

The overlap scrub

When the forced track is burned in and a viewer also turns on regular subtitles, the same line would appear twice: once in the picture and once below it. Sublutions+ guarantees that no dialogue or SDH line is ever on screen at the same time as a burned-in line:

The log lists how many lines were removed, moved or shortened, and why. If the forced track and the SDH seem to be timed for different releases, a warning appears; check the result, because the cleanup depends on both matching the same video.

With Mux, the forced track stays a separate track, so the regular tracks aren't scrubbed against it.

The blacklist

The Forced, Standard and SDH tracks are also cleaned of lines matching your blacklist — release-group ads, site names, "Subtitles by…" credits. The list is sublutions_blacklist.txt in the app folder, one word or phrase per line; lines starting with # are comments. Lines that run past the end of the video are also trimmed.

The app sorts every entry on its own, so you never have to:

Kind of entryExamplesWhat happens
Common wordthe, that, you know, teamIgnored. It can't be spam, so it never removes anything. The log says so: Blacklist entry "that" ignored: a common grammar word.
Real wordelite, encoded, subtitlesRemoves a line only when it also looks like spam: a web address, credit wording ("Subtitles by…"), a release tag, decoration such as == … ==, two blacklist hits, the first or last 5 lines of the file, or right next to another removed spam line. A line that reads like dialogue, such as "Only the elite survive.", is kept.
Made-up nameyify, rarbg, galaxyrg, opensubtitlesAlways removes the line. Matched as a whole word, so "yify" does not catch "Sorry if you…".

Every removed line is logged with its reason, for example Removed (credit wording "encoded by"): Encoded by YIFY, and so is every line kept because it reads as dialogue.

Adding an entry: type the name as it appears in the spam ("elderman", "srt-team", "tvsubtitles.net"). Hyphens and dots are fine. New names are matched inside a single word only, so "honeybunny" catches "@HoneyBunny" but never "I love you, Honey Bunny."

Word list credits

Drag to reorder

Muxed subtitle cards can be dragged into the order you want, as with audio. A burned forced card stays first.

In-video closed captions (CEA-608)

Some TV captures, DVR files and broadcast rips carry US closed captions inside the video stream (CEA-608, packaged as ATSC A53 data in the H.264 or HEVC bitstream). Players such as VLC list them as Closed captions 1–4. They are not a separate MKV or MP4 subtitle track, so a track list that only counts container streams will look like the file has no captions at all — even while Plex still offers English (Closed Captions) after you remove every SRT and PGS track.

Why MediaInfo and mkvmerge are not enough. On a real example — a Chicago Med episode MKV with one English SRT dialogue track — a MediaInfo export shows Video, Audio and that one Subtitle stream only. mkvmerge's JSON identification lists the same four tracks. Nothing names CEA-608 or closed captions, because the captions live in the video elementary stream, not in Matroska's subtitle track list. VLC is honest about the extra layer; a container track report is not.

Sublutions+ probes for ATSC A53 when you open the file (or at Start for a file never opened), using a short sample of the start of the video — not while adding a whole batch. When captions are present, Planned Image subtitles gains a card for them — same layout as PGS/VobSub:

Discard on SDR: removes the embedded captions with a video stream copy and a bitstream filter (filter_units) — no picture re-encode, no quality loss. Discard on HDR: requires a video re-encode so captions are removed without damaging HDR signaling; the card explains when that applies.

Image subtitles section with the CEA-608 card, Discard, Strip in-video captions only, and Preserve metadata on the Video card
Image subtitles section with the CEA-608 card, Discard, Strip in-video captions only, and Preserve metadata on the Video card

Strip in-video captions only

On the CEA-608 card, Strip in-video captions only (default off) is for the job where you want only the in-video captions removed — not a full Sublutions subtitle pass.

When the checkbox is available (the rest of the Planned view still matches the defaults from analysis — no burn, no Create AAC 2.0, Generate dialogue-only from SDH off, no other subtitle/audio/video changes except Preserve metadata), processing:

A typical TV capture with only Strip in-video captions only and Preserve metadata can finish in under a minute.

Why: Plex and other servers can keep exposing "closed captions" from the video bitstream long after you thought you cleaned the file. This path removes that layer surgically without re-running dialogue scrub, SDH split or language detection when you did not ask for any of that.

If you need forensic cleanup and embedded CC removal, leave the checkbox off and run a normal Builder job with Discard on the CEA-608 card.

Other subtitles

With Preferences → Subtitles set to Prioritize English (keep others after), the other-language tracks Sublutions+ keeps appear in a section headed "Other subtitles · N tracks", after the Forced / dialogue / SDH cards.

Why: multilingual households want their languages kept, correctly identified and flagged, without dozens of tracks burying the three that matter. They are written after the English (or hero) tracks.

How a track gets here. Most Other cards are the foreign text tracks that were never chosen as Forced / dialogue / SDH heroes. Two special cases under Prioritize English: (1) an embedded SDH (or Forced / dialogue) displaced when an external file takes that hero role is moved here instead of dropped; (2) when English SDH is present, a foreign dialogue hero in Standard is moved here too so English stays first (Generate on or off — see Generate). Undo of the external English SDH restores displaced heroes; unticking Generate does not put foreign dialogue back ahead of English.

With Discard non-English (the default), other-language tracks aren't kept and this section doesn't appear.

11. Adding Your Own Subtitle Files

Why add files

Sometimes the subtitles you want aren't in the video: a better SDH from a subtitle site, or a forced track the release left out. Downloaded subtitle files are named inconsistently — "eng.srt", "English.HI.srt", "2_English.srt" — so their names can't be trusted either. Drop in as many as you like; each one is identified by reading it, exactly like the video's own tracks. An English SDH added under Prioritize English can also free Standard for Generate by moving a foreign dialogue hero to Other — see that section.

How to add them

While they're read: "Identifying N subtitle files…". Files that can't be used are listed in a card, "Some subtitle files weren't added", with the reason (for example "no subtitle cues found").

Roles

Each file becomes an External · name.srt card. Its role — Forced, Dialogue or SDH — comes from the forensic identification, and files added together never share a role. To change it, use the card's Role choice.

ASS files

.ass files are converted to SRT for processing (styling is dropped). Your .ass file itself is never changed.

12. Where Your Files Go

Output name and folder

The finished file keeps the source name, with the container's extension, in your default output folder: Movie (2024).mkv → Movie (2024).mkv. No suffixes, so Plex and other library apps match it exactly as before.

The Output line at the top of the workspace shows the full path before you start.

Per-file output folder

Tick Per File Save Output Folder Override at the top of the workspace, then Browse to send this one file somewhere other than the default output folder — a different library, for example. The path is greyed until the box is ticked.

When the output already exists

Set in Preferences → Output files:

Writing over the source itself (when the output folder is the source's folder): the new file is written beside it first, and the source is renamed _original only after the new file succeeds. A failed or cancelled run leaves the source exactly as it was.

Why: nothing you already have is ever lost to a failed or unwanted run. The old file is kept until you decide what to do with it.

Disk space check

Before anything starts, Sublutions+ estimates the space each file needs on each drive involved. If a drive is too full, you're told before the first file starts.

Why: running out of space three hours into an overnight batch wastes the night.

Expanding the MKV header

FFmpeg writes MKV files with a very compact header. Tagging apps such as MetaX need room in that header to add a cover or synopsis; without it they must rewrite the whole multi-gigabyte file, and some damage it. So, after each MKV is written, Sublutions+ rewrites it once more with mkvmerge, which leaves room in the header. Nothing is re-encoded; titles, languages, flags and chapters are kept.

The new copy is checked against the original — same streams in the same order, same chapters, same duration — before it replaces it. If anything doesn't match, or mkvmerge is missing, the original output is kept (it's a valid file) and the log says why.

It shows as its own step during processing: "Expanding header to accommodate tagging". Turn it off in Preferences → Output files if you never tag your files; MP4 and M4V files are never affected.

13. Processing

Starting

Click Start Processing in the bottom-right tile. Its tooltip says what will happen: "Process all N files in the batch with each file's planned settings".

Files you haven't clicked yet are analyzed first, then each file is processed in turn with its own plan.

What happens to each file

  1. Audio language — with Always detect, untagged audio is identified by listening to a sample (see Audio language).
  2. Subtitles — extracted, cleaned of blacklist lines, scrubbed against a burned-in forced track, and a dialogue-only track built from SDH if planned.
  3. Encode or copy — one pass when everything can be copied or encoded together; two passes when a forced track is burned in (or when surround audio is copied beside a re-encoded video), for example "Pass 1 of 2 — burn video encode" then "Pass 2 of 2 — mux audio/subtitles/chapters".
  4. Check — Sublutions+ waits until the file is completely written (important on network drives) and confirms its duration.
  5. Expand the header (MKV) — "Expanding header to accommodate tagging" (see Expanding the MKV header).

The processing screen

A batch running: the third file is encoding, the second failed, and the other tiles are locked until the run ends
A batch running: the third file is encoding, the second failed, and the other tiles are locked until the run ends

Telemetry

The log below fills with what the app is doing, step by step. Its detail level is set in Preferences → Telemetry:

Long lines, such as FFmpeg commands, wrap to the width of the window, so the log never scrolls sideways. While you are scrolled to the bottom, each new line stays in view through the end of the run (including Session complete after the results panel appears); scroll up to read earlier lines without the log fighting you. With Always detect audio language, a gold notice when that step starts explains it can take up to 90 seconds and how to turn it off in Preferences, followed by a plain Language detected: line when it finishes. MKV jobs that expand the header log [PROCESSOR] start and complete lines in the telemetry pane (the same step as the progress bar). Click Copy log to copy the whole log, for example to send with a question. Right-click for Copy selection, Copy entire log and Clear log.

Aborting

During processing the run tile turns red and reads Abort · "Stop this run".

Stopping removes the partial output. Files that already finished are kept.

While it runs

The tool tiles and the day/night switch are locked until the run finishes, so nothing can change under a running job. You can still add files; they're processed after this run.

14. Results and Done

The results panel

When the run ends, a results panel shows Successes, Failures, Cancelled / skipped and Total: "Review the results below. The telemetry log stays available until you click Done." The run tile reads Run complete · "Review the results, then Done".

The results panel after a batch with one failure, with Retry Failures, Recycle Processed and Done
The results panel after a batch with one failure, with Retry Failures, Recycle Processed and Done

Retry Failures

Shown when something failed. Runs only the failed files again, with the same plans. Read the log first: it says why each one failed.

Recycle Processed

Shown when at least one file succeeded. Sends the source files that processed successfully to the Recycle Bin: "Moved N processed source files to the Recycle Bin." Failed, cancelled and unprocessed sources are left alone, and so are _original files.

Why the Recycle Bin: you can still restore a source if you find a problem with its output later.

Done

Done clears the batch and returns to the tool that started the run. If Open output folder when processing finishes is on, it also opens the folder the files were written to. After External Subtitles it opens the folder the cleaned subtitles were saved in; after Metadata Only, the folder the written files are in.

Closing the app

Closing Sublutions+ clears the batch and removes its work files (extracted subtitles and analysis). Closing during a run stops it; the next start shows the interrupted-run notice.

15. Metadata Only

Why Metadata Only

Metadata is everything about a file except the picture and sound: its title, track titles, languages, flags, tags such as the synopsis and cast, chapters and cover art. Downloads are full of release-group spam in exactly those places — "GalaxyRG – …BluRay.x265" in the comment, junk in every track title — and the quick fix, stripping all metadata, throws away your real tags with it.

Metadata Only is a full editor that fixes the spam and leaves everything else exactly as it was:

Opening a file

Metadata Only follows the batch: the file selected in the batch on the left opens in the editor, and clicking another file opens that one instead. Why: the file you're looking at is the file you want to fix — no second trip through a file dialog.

Each file keeps its edits. Work through the batch the natural way: open a file, fix it, click the next one, fix that, and so on. Nothing is lost when you move between files; each edited file shows "N metadata changes to write" in orange under its name. One click on the run tile then writes them all — see Writing the changes.

Leaving with unwritten edits. Click another tool in the dock while edits are unwritten and the app warns: "You have unwritten changes that will be lost if you leave Metadata Only." It lists the files and offers:

Why: the Builder reads each file as it is on disk, so edits that were never written can't follow you there. Asking at the door means they're never left behind by accident.

The Video file card shows the name of the file you're editing as plain text: it's not a box to type in. To work on other files, add them to the batch (+ Add files, or drag them onto the window) and click them there; Remove takes them out. When no file is loaded, the card offers a slot to drag an MKV, MP4 or M4V onto, or Browse. Other kinds of file: "Couldn't read NAME: Metadata Only works on MKV, MP4 and M4V files."

The cards

Everything that is metadata is shown, and all of it is editable:

To delete a tag, clear its value. To add one, click Add tag, pick or type a name, click Add, then fill in the value (a new tag left empty isn't written).

Hidden encoder and statistics tags

Encoder and statistics tags (ENCODER, BPS, DURATION, NUMBER_OF_FRAMES, NUMBER_OF_BYTES, _STATISTICS_… and their language versions such as BPS-eng) are machine bookkeeping that nobody edits. They're hidden on every card unless you turn the view off. They stay in the file unchanged, and they're used behind the scenes to spot problems. On Metadata Only, Show all tags (encoder and statistics) under + Add files and Remove is on by default so you see them on every card (the same for every file in the batch; it does not change what gets written). Clear the checkbox for shorter cards.

Red flags and fix links

A box turns red when something doesn't add up. The reason is its tooltip and a line at the bottom of the card, and above the reason a fix link named for what it does. Clicking it stages the fix (nothing is written until Write) and the flag disappears.

Why: a red box that only says "wrong" leaves you to work out why. Sublutions+ explains the problem in plain words and offers the fix by name.

Release spam flagged in red: the title and comment name the release group, and "Use the movie name" fixes the title
Release spam flagged in red: the title and comment name the release group, and "Use the movie name" fixes the title
What's wrongExample reasonFix link
A subtitle titled Standard or SDH has very few lines"Titled Standard (dialog only), but only 8 lines over 109 minutes: looks like a forced track."Make it Forced
A subtitle titled or flagged Forced has as many lines as a full track"…looks like a full dialogue track."Make it Standard
The title says Forced but the Forced flag is off"Titled Forced, but the Forced flag is off."Tick Forced
The Forced flag is on but the title doesn't say Forced"The Forced flag is on, but the title doesn't say Forced."Retitle Forced (or Untick Forced)
An audio track is noticeably longer or shorter than the video"…cut short or out of sync?"none — metadata can't fix it
The file title contains a blacklist word"The title contains "galaxyrg" from the blacklist. The movie name from the file name is "28 Years Later"."Use the movie name
A track title contains a blacklist word"…release spam."Clear the title
A tag contains a blacklist word"COMMENT contains "bluray" from the blacklist: release spam."Clear this tag

Line counts are checked the same way the forensic identification checks them: a subtitle with 2 lines a minute or fewer, or with 20% or less of the lines of the biggest track in the same language, looks forced; one with more than half the lines of another track in the same language looks like full dialogue.

Descriptive tags — description, synopsis, cast and the like — are flagged "release spam, or real text?" but never cleared automatically, because blacklist words can appear in real prose. The link is your call.

Files without statistics (all MP4s and some MKVs) say on the File card: "No track statistics in this file, so line counts and lengths aren't checked."

A summary under the file name counts the flags as soon as the file loads: "27 flags in this file (red boxes below). Apply Sublutions standards should fix all of them." (or "…fix N of them.").

Apply Sublutions standards

One click to clean the whole file the way Sublutions would — but it only stages the changes, so you see each one and can undo any of them before you Write. A note says what it did, for example "Sublutions standards staged: 1 release tag cleared, 3 track titles / flags standardized, lone chapter removed.", or that "this file already meets them."

It:

Your own edits always win. If you changed a field by hand, Apply leaves it alone and the note adds "Your own edits to N fields were kept." Everything else you edited is kept too, and written along with the standards. Why: you changed it on purpose; a button shouldn't undo that.

A whole batch at once

Select two or more files in the batch (Ctrl-click, Shift-click or Ctrl+A) and the button becomes Apply Sublutions standards to N files. One click stages the standards on every selected file, one after another ("Applying Sublutions standards… file 2 of 5: NAME"), and the note sums up: "Sublutions standards staged on 5 of 5 files. Review each file, then Write." While it works, the fields are greyed out and can't be edited; they come back the moment staging finishes.

Leave a file out of the selection and it isn't touched. Hand edits win file by file: a title you typed in one file stays, while the same field in the other files gets the standard.

Why: a season of episodes usually needs the same cleanup. Fix the odd one out by hand, select the rest, and clean them all in one pass.

Cover art

The cover art itself appears on its card. Tags and tracks appear at once; the picture follows a few seconds later ("Loading the picture…"), because reading it means opening the movie, which is slower over a network. The window stays responsive meanwhile.

Why: Plex and other players show the cover in your library, so a wrong or missing poster is visible every time you browse. See what's there, keep a copy before you change it, and fix it in seconds.

Writing the changes

The run tile counts your edits:

Why orange: a click that writes several files deserves a second look. The color change is impossible to miss, so you always know whether you're writing one file or many.

The tile writes every file with edits, whether or not it's selected now, so the edit-each-file-then-click-once workflow just works. Each file gets its own line in the results.

After Done, the written files leave the batch and the files you didn't touch stay, ready for the next round. When every file was written, the batch is empty. If a Write fails, that file stays in the batch with its edits so you can try again. If Open output folder when processing finishes is on, Done also opens the folder the written files are in (each folder, if they came from more than one). Metadata Only always writes in place, so that's the files' own folder, not the output folder.

Safety: a rewritten file must contain exactly the expected tracks before it replaces the original. Otherwise the original is left unchanged and the log says why.

16. External Subtitles

Why External Subtitles

Sometimes the only problem is a subtitle file you downloaded. External Subtitles cleans subtitle files on their own — removing duplicates of a forced track, making a dialogue-only version of an SDH — without touching or re-processing any video.

The slots

Drag a .srt onto a slot or click Browse; Clear empties it. If you start with nothing loaded: "Add at least one subtitle file."

External Subtitles with a forced file and an SDH file loaded, ready to make a dialogue-only file and scrub the forced lines
External Subtitles with a forced file and an SDH file loaded, ready to make a dialogue-only file and scrub the forced lines

Use files timed for the same release of the same movie. The cleanup compares lines by their timing; a forced file from a different release can remove real dialogue.

Inspect a file

Click a loaded file's name to open it in your default subtitle program (tooltip: "Open this subtitle to inspect it", plus its full path).

Why: downloaded subtitle files are often vaguely named. A two-second look confirms the SDH file really has the [door slams] cues before you run anything.

What it does

Blacklist lines are removed from every file.

Where the results go

Results are saved next to the source files, not in the output folder. Each original is backed up once as name_original.srt before it's changed — the same _original the Builder uses — so running the same files again never overwrites your true original.

Done opens the folder the new subtitles were saved in (each folder, if the files came from more than one), unless Open output folder when processing finishes is off. Nothing opens after a failed run.

17. Preferences

How Preferences work

"Machine and app settings. These apply to every file." Changes take effect immediately; there's nothing to save or close. Settings for a single file — burn or mux, codecs, boost — are on that file's cards on the Builder, not here.

The whole Preferences page
The whole Preferences page

Output folder

Default output folder — where finished files go. Each file can override it on the Builder (see Per-file output folder).

Output files

Hardware

"Detected: …" shows the encoder Sublutions+ found on the graphics card driving your display — NVIDIA (NVENC), Intel (Quick Sync) or AMD (AMF) — or software encoding when there's none.

Encoder preset balances speed against quality and size when the video is re-encoded. The choices depend on the encoder:

EncoderPresetsDefault
NVIDIA NVENCp1 (fastest) to p7 (best quality)p4
Intel Quick Sync1 – veryfast to 7 – veryslow4 – medium
AMD AMFspeed, balanced, qualitybalanced
AnyNone (use software encoding)—

Faster presets finish sooner and make slightly larger files at the same quality.

Analyze Hardware detects the graphics card and its encoders again. Use it after a graphics card is removed, replaced or repaired, or after moving the app to another PC. The note says what it found, for example "Analyzed at 2:47 PM: no change." or "changed from …".

Why: hardware encoding is many times faster, but only if the app knows the current card. One click replaces deleting the settings file and setting the app up again.

Audio language

What happens to audio tracks with no language tag (or "und", undefined):

To check a file before processing, use Re-detect on its audio card.

Why there is a pause after Start Processing

With Always detect, the app does not trust language tags in the file. After subtitle scrub on each file, it listens to the audio (Whisper on the CPU — not your GPU encoder) until two independent samples agree on the language, and sometimes runs a third to break a tie. That step happens every time you press Start Processing, not only the first time you add the file.

What to expect: on a fast desktop, often about 10–40 seconds per movie before the FFmpeg plan appears; slower PCs, older NAS CPUs, or sources on a network share can take a minute or more. The Preferences Audio language card shows a short reminder in the same gold as the processing log when Always detect is selected so this does not come out of the blue.

Why it is worth it: a few extra seconds per file buys audio tracks that Plex and other servers label correctly without guessing from bad metadata — a small price for a clean library. If you already trust your sources or only process English, Default English or Prompt me skips the processing-time listen.

Subtitles

Non-English subtitle tracks:

Track titles

"Titles given to tracks when files are processed or standardized." A collapsed card — click Options ▾ to open it.

Files already in the batch follow a change wherever a title is still the standard one; titles you typed yourself are kept.

Why: every library has its own naming habits. Set yours once and every file follows them.

Audio codec names

A collapsed card — click Options ▾ to open it — with one box per audio format: AC3, E-AC3, E-AC3 with Atmos, TrueHD, TrueHD with Atmos, DTS, DTS-HD MA, AAC, FLAC and Opus. Each shows the Sublutions name greyed ("Dolby Digital", "Dolby Digital Plus", "DTS-HD Master Audio"…). Type your own — "DD+", for example — and titles become "DD+ (5.1 Surround)": the channels part is still added for you.

How audio titles work

Audio titles are what Plex and other players show in the audio menu. Two settings decide what they say, and they answer different questions:

  1. Audio titles (in Track titles) decides the shape: which pieces of information the title contains.
  2. Audio codec names decides the wording of the codec name inside the Sublutions shape. It changes nothing else.

The four shapes, for an E-AC3 5.1 English track, a TrueHD Atmos 7.1 English track and the stereo AAC track Sublutions+ creates:

Audio titles choiceE-AC3 5.1TrueHD Atmos 7.1Created AAC 2.0
Sublutions (default)Dolby Digital Plus (5.1 Surround)Dolby TrueHD with Dolby Atmos (7.1 Surround)AAC (Stereo)
ShortE-AC3 5.1TrueHD Atmos 7.1AAC Stereo
LanguageEnglish 5.1English 7.1English Stereo
Keep the file's own titlewhatever the file calls it (the Sublutions shape if it has no title)samesame

Each choice applies to every audio format. Untagged audio in the Language style falls back to Short.

With the Sublutions shape, E-AC3 named "DD+" and TrueHD with Atmos named "TrueHD Atmos":

E-AC3 5.1TrueHD Atmos 7.1Created AAC 2.0
Sublutions shape, your namesDD+ (5.1 Surround)TrueHD Atmos (7.1 Surround)AAC (Stereo)

Which to use: happy with Sublutions' names — change nothing. Want a different kind of title — pick it in Audio titles. Like the Sublutions kind but call a format something else — type it in Audio codec names.

Telemetry

Telemetry detail: Abbreviated (new installs) or Comprehensive. See Telemetry.

Windows integration

Show in Windows Open with menu (loads the selected file) — adds Sublutions+ to right-click → Open with for supported video files in File Explorer; choosing it adds the file to the batch. Off by default, and available in the installed app only. It's registered for your Windows account and for this folder: after moving the app, turn it off and on again.

Tool Tips

Turn off Tool Tips — when ticked, no tooltip appears anywhere in the app when you hover over something. Off by default.

18. Troubleshooting

A file takes a long time to analyze

Sublutions+ reads every subtitle track in the file, not just the English ones, and releases with dozens of tracks take longer — more so over a network. Watch the file's line in the batch: "Analyzing subtitle 23 of 44" means it's working, not stuck.

Compare says "Analyzing the file…"

Compare is built from the analysis, so it waits for it and fills in by itself. Click the file in the batch if its analysis hasn't started.

Progress sits at the end of a pass

After the last frame, FFmpeg may still be finishing the file — moving the index to the front of an MP4, or flushing a large file to a network drive — and Sublutions+ then waits for the file to stop growing before checking it. This is normal; network drives take longer.

A second step starts after an MKV finishes

That's "Expanding header to accommodate tagging" — see Expanding the MKV header. To skip it, turn it off in Preferences → Output files.

"mkvmerge not found"

The header step couldn't find mkvmerge. The output is still a valid MKV, but some tagging apps may damage it. Make sure src\mkvtoolnix\mkvmerge.exe is in the app folder (it ships with Sublutions+); copy the folder again if it's missing. Metadata Only also needs mkvpropedit.exe in the same place to edit MKV files.

My boost was skipped

The file is marked as already boosted by Sublutions, so every Boost is locked at 1.00 to prevent clipping (see Boost). This is deliberate and can't be overridden. If the file was never really boosted — someone copied the tag — remove Boost=1 from its keywords with a tagging app and add it again.

"Forced and … timing differs … may be timed for different releases"

The forced track and the dialogue or SDH track are consistently out of step (by more than half a second). The overlap scrub depends on both matching the same video, so check the output, or use subtitle files from the same release. In External Subtitles, also make sure both files are for the same movie.

A player doesn't show forced subtitles

The player is probably ignoring the Forced flag. Process the file again with the forced card set to Burn (see Burn or Mux).

Lines I don't want keep appearing

Add the release name or site to sublutions_blacklist.txt in the app folder, one per line (see The blacklist). If the log says your entry was ignored, it's too common a word to be spam; add the name next to it instead.

Hardware encoder errors

Click Analyze Hardware in Preferences → Hardware, especially after a graphics card or driver change. If errors continue, turn off Hardware encoder (faster) on the file's video card, or choose None (use software encoding) as the preset. The log in Comprehensive detail shows the encoder's own error.

Audio language wasn't detected

The speech model needs clear speech; music-heavy or very quiet samples can stay unsure. One minute of dialogue has also produced the wrong language, so detection samples until it reaches consensus, and a third analysis decides the language title when the same language isn't found twice. Click Re-detect on the audio card to run that check again, or choose the language yourself. If Re-detect reports an error, check that the src\Whisper\ folder is complete; copy the app folder again if not.

Some files in a batch failed

Read the log for the failed file's error, then use Retry Failures (see Results and Done). Files that succeeded aren't processed again.

Not enough disk space

Free space on the drive that's named, or choose another output folder for the batch (Preferences) or for one file (Per-file output folder).

The other tiles are locked

During processing, the tool tiles are locked until the run finishes and you click Done. On the Welcome page they're locked until you click Start using Sublutions+.

Start Processing is greyed out

The batch is empty. Add files on the Builder (the tile reads "Add files to begin").

Window size resets

The size and position are saved when you close the app. If your display scaling changed, resize the window once and it will be remembered.

19. Track Names and Order in Your Output

Stream order

Every output file is written in the same order, so players show a consistent track list:

  1. Video
  2. Audio, in your Order on the audio cards
  3. Subtitles: the English roles in your order (a burned forced track isn't a track at all), then other languages if you keep them

Subtitle titles

Unless you've set your own in Preferences → Track titles:

RoleTitle in the player
ForcedForced (foreign dialogue/non-Verbal)
Dialogue onlyStandard (dialogue only)
SDHSDH (for the hearing impaired)

Forced tracks are also written with the Forced and Default flags, so players that honor them show the track automatically.

Audio titles

Built from what the track actually is — codec, channels and Atmos — not from whatever the source file called it, in the style chosen in Preferences → Track titles. Examples in the default Sublutions style: AAC (Stereo), Dolby Digital Plus (5.1 Surround), Dolby TrueHD with Dolby Atmos (7.1 Surround), DTS-HD Master Audio (5.1 Surround). Mono tracks use the codec name alone.

20. Quick Reference: "What If I Choose…?"

Builder choices

I choose…What happens
Forced BurnForced lines drawn into the picture; video re-encoded; no dialogue or SDH line ever shares the screen with a burned-in line. Not available while Preserve HDR is locking HDR-safe choices
Forced MuxForced lines kept as a track with the Forced flag; video can be copied untouched
Forced DiscardNo forced lines in the output
Video codec, resolution and size all at Sync with Source, no BurnVideo copied bit for bit
A different codec, or a smaller resolutionVideo re-encoded
Output codec H.266 (VVC)Works, but software encode is very slow; Plex and similar won't Direct Play it (full transcode or no play); only a handful of players can play it today
Reduce file size None (while re-encoding)Near-lossless encode; file may grow
Reduce file size Moderate / Large / ExtremeSmaller file, increasing quality cost
Audio codec Sync with SourceTrack copied untouched
Audio Boost above 1.00Track re-encoded louder; output marked so it's never boosted twice
Boost on an Atmos, TrueHD, DTS, Opus or Vorbis track at Sync with SourceNot allowed; choose another codec to boost it
Any Boost on an already boosted fileLocked at 1.00
Create AAC 2.0Stereo AAC track added beside the surround track
Audio DiscardTrack left out (not on the last remaining track)
Generate dialogue-only from SDHClean English dialogue track built from English SDH; under Prioritize English, foreign Standard moves to Other automatically
Subtitle format SRTPlays directly almost everywhere
Subtitle format ASS (MKV)Styled subtitles; some Plex clients transcode to show them
Paste settingsVideo and subtitle plan copied; audio only to files with matching audio streams

Preferences

I choose…What happens
Keep clean name, archive old as _originalNew file takes the clean name; the old one is renamed _original
Prompt me to rename manuallySingle files ask for a name; batches still use clean names
Open output folder when processing finishesDone opens the output folder
Expand MKV header offMKV files left as FFmpeg wrote them; tagging apps may have to rewrite or may damage them
Audio language Always detectUntagged audio identified at processing by consensus. If the same language isn't detected twice, a third analysis decides the language title; otherwise it falls back to your choice
Preserve HDR checkedAn HDR re-encode keeps that file's HDR. H.264, 8-bit, and Burn cannot
Audio language Default EnglishUntagged audio tagged English; no listening
Audio language Prompt meAsked for a code when a file with untagged audio is opened
Subtitles Discard non-EnglishEnglish tracks only
Subtitles Prioritize EnglishOther languages kept after English, collapsed on the Builder
Encoder preset None (use software encoding)Every re-encode uses the processor: slower, works everywhere

Results

I click…What happens
Abort (one file)Stops now; partial output removed
Abort (batch)Stop after this file, stop all now, or keep processing
Retry FailuresOnly the failed files run again
Recycle ProcessedSuccessfully processed sources go to the Recycle Bin
DoneBatch cleared; output folder opened if you've asked for that

21. Containers, Subtitles and Glossary

Containers and soft subtitles

Sublutions+ can open the containers below. Output is always MKV, MP4 or M4V.

ContainerOpensWritesSoft subtitlesNotes
MKV✓✓Excellent — SRT, ASS, PGS, VobSub and moreThe best fit for multiple subtitle tracks
MP4✓✓Limited — mov_textPlays almost everywhere
M4V✓✓Same as MP4Apple's flavor of MP4
MOV✓—LimitedWritten as MKV with Sync with Source
AVI, WMV / ASF✓—RareWritten as MKV; add external .srt files for subtitles
TS / M2TS✓—Common on Blu-ray and broadcast, usually picture-basedWritten as MKV

Glossary

TermMeaning
Forced subtitlesOnly the lines a viewer needs when the movie switches language: foreign dialogue and on-screen signs.
Forced flagA marker on a subtitle track telling players to show it automatically. Not every player honors it.
SDHSubtitles for the deaf and hard of hearing: dialogue plus sound descriptions and speaker names.
Dialogue only (Standard)Subtitles with everything that's said and nothing else.
BurnDrawing subtitles into the picture itself. Always visible; requires a re-encode.
MuxPutting a stream into the file as its own track, which players can turn on and off.
Stream copyCopying a stream into the new file bit for bit. Fast and lossless.
Re-encodeCompressing a stream again. Takes time and costs some quality.
RemuxRewriting a file into a new container without re-encoding anything.
ContainerThe file format that holds the streams: MKV, MP4, M4V.
CodecHow a stream is compressed: H.264, HEVC, AAC, Dolby Digital Plus…
AtmosDolby's object-based surround format, carried inside Dolby Digital Plus or TrueHD tracks.
AAC 2.0A stereo AAC track: plays on virtually every device.
und"Undefined": the language tag on audio or subtitles that nobody labeled.
HeaderThe start of an MKV file, where its track list and tags live.
Forensic analysisSublutions' reading of every subtitle track to decide its real role, whatever its label says.
CEA-608 / in-video CCUS closed captions carried inside the H.264/HEVC bitstream (ATSC A53), not as a separate subtitle track.
ATSC A53The standard that packages closed-caption data in digital TV video; what Sublutions+ probes for when you open a file or at Start.
Overlap scrubRemoving or moving regular subtitle lines that would appear at the same time as burned-in forced lines.
BlacklistYour list of spam words and phrases removed from subtitles and flagged in metadata.
_originalThe name given to a file Sublutions+ set aside instead of overwriting it.

22. Coming from Multi-File Pro

What changed

Sublutions+ uses the same forensic subtitle identification, overlap scrub, SDH split, audio language detection and encoding engine as Multi-File Pro. What changed is how you work with it:

Multi-File ProSublutions+
One set of choices for the whole batchEvery file, and every stream in it, planned on its own; copy and paste plans between files
Settings screen behind a gear iconPreferences tile, changes apply immediately; per-file choices (Burn/Mux, compression, AAC 2.0, dialogue generation) moved to the file's cards
File Comparison windowCompare view, one click in the View tile
Audio Stream Configuration screen, turned on in SettingsAudio cards on every file, always: order, discard, codec, title, boost, language, AAC 2.0
Forced / Standard / SDH Browse slotsAny number of external subtitle files, each identified by reading it
Compression level in SettingsReduce file size on each file, with a near-lossless None; resolution downscaling
Check Audio Language buttonRe-detect on each file's audio cards
Metadata normalization only (a mode of the main run)Metadata Only, a full metadata editor
Subtitle-only modeExternal Subtitles tool; backups named _original instead of _bak
Progress barSteps, elapsed time, time remaining and speed for each file and the batch
Delete settings.json after a graphics card changeAnalyze Hardware
Separate first-run Settings screen and Open with questionOne Welcome page

What was dropped on purpose