Mit der letzten Woche erschienenen Version und dem Profil „MKV HEVC“ schlagen Konvertierungen nun mit dem Fehler fehl:
„Extrahieren der Untertitel fehlgeschlagen“
Diese Aufnahmen enthalten keine Untertitel. In früheren Versionen führte das Fehlen der Untertitel jedoch nicht zum Scheitern der Konvertierung. Mir ist bekannt, dass es in dieser Version Änderungen im Zusammenhang mit Untertiteln/Closed Captions gab. Ist es beabsichtigt, dass die Konvertierung fehlschlägt, wenn keine Untertitel vorhanden sind? Falls ja, kann ich ein Profil für Serien ohne Untertitel anlegen. Ich bin nur neugierig, ob das so gedacht ist oder ob es sich um einen Fehler handelt?
Based on recent changes in MCEBuddy (starting around version 2.6.2), the subtitle and closed caption engine was redesigned to be “simpler” and more automated.
In previous versions, the logic was often more permissive. However, recent updates changed how “Save subtitles” and “Embed subtitles” (formerly “Extract subtitles and closed captions” and “Add subtitles”) interact.
Is this a bug or intended design?
It appears to be a bug or a regression in how the engine handles files without caption streams. While the intended design is to automate extraction, it should not treat a missing stream as a fatal processing error if the source simply doesn’t contain one.
Potential Causes & Troubleshooting
CCExtractor Sensitivity: MCEBuddy uses CCExtractor for this process. If your profile is specifically calling for a caption extraction that returns a non-zero exit code (failure) because no stream is found, MCEBuddy may be interpreting that as a task failure.
Profile “Force” Settings: Check your MKV HEVC profile in profiles.conf. If there is a command line argument or a setting that mandates subtitle processing, it might be causing the hard stop.
Suggested Workarounds
Disable Subtitle Options: In your Conversion Task settings, try unchecking both “Save subtitles” and “Embed subtitles”. If the conversion then succeeds, it confirms the engine is failing because it expects a stream that isn’t there.
Custom Profile: As you mentioned, creating a specific profile for series known to lack captions is a valid workaround, but you can also try adding cc_stop_on_error=false (if available in your version’s expert settings) to the profiles.conf for that specific profile to see if it allows the process to continue.
Check Logs: To confirm exactly why it’s failing, look for the line in your conversion log just before the “Extracting closed captions failed” message. It will usually show the exact command line being run and the error code returned by the sub-process.
I recommend uploading a copy of your conversion log to this thread. The developers (like @Goose) usually look for those logs to see if a specific “check” needs to be made optional in the code.
Looking at your log for Elsbeth - S03E12, I can see exactly where the failure occurs:
2026-03-06T12:10:45 --> Extracting closed captions from C:\Users\SJL\AppData\Local\Temp\MCEBuddy\Working\elsbeth - s03e12 - All’s Hair.mp4
2026-03-06T12:10:46 --> CCExtractor failed to find any subtitles/closed captions in source file.
2026-03-06T12:10:46 ERROR> 2026-03-06T12:10:46 --> Extracting closed captions failed
Analysis
It appears your intuition was correct: this is a bug/regression in the recent subtitle engine redesign.
In the latest versions (starting with the 2.6.2 beta branches), MCEBuddy was updated to “simplify” subtitle handling by making extraction a default prerequisite when “Save subtitles” or “Embed subtitles” is checked. However, the logic currently treats a “No subtitles found” result from CCExtractor as a fatal error for the entire conversion task, rather than just skipping the subtitle step and moving on to the video encoding.
The Verdict
Is it intended? No. MCEBuddy is designed to be an automated “set and forget” tool;
Danke, dass Sie das gemeldet haben. Ja, es scheint ein Fehler im Zusammenhang mit Strict Processing zu sein, wenn keine Untertitel gefunden werden. Normalerweise setzt MCEBuddy die Konvertierung fort, wenn die Untertitel-Extraktion fehlschlägt. Wenn Strict Processing aktiviert ist, führt jede kleine Störung zum Abbruch der Konvertierung. Idealerweise sollte sie nicht fehlschlagen, wenn überhaupt keine Untertitel vorhanden sind.
Ich sehe in Ihren Logs, dass Sie Strict Processing aktiviert haben.
Strict Processing → True
Als vorläufige Lösung deaktivieren Sie bitte Conversion Task → Expert Settings → Strict Processing, bis wir eine Korrektur dafür veröffentlichen.