-
-
Notifications
You must be signed in to change notification settings - Fork 125
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Demux preferred languages but don't include them does not demux subs in 2.42.0 #1471
Comments
I'm not talking about the subs inside the container (menu), but the extracted subtitle files that had been inside the default temp folder before the change to 2.42.0. The reason for this is that I use a script to hardcode the demuxed subtitle files into the video, and this does not work anymore since there are no subtitle files in the temp folder when using "Demux preferred languages but don't include them". The files are being created when using "Demux preferred languages and include them", but I do not want to include them when hardcoding the subs into the video stream. I don't think the source file matters much since the options do not seem handle demuxing consistently, but for reference, the streams of the source file are as shown on the screenshot of a mkvmerge output: |
Okay, got you. I will check that.... |
|
Yep, everything now works as it should. Cheers! :) |
Describe the bug
Project Options -> Subtitles -> Demux preferred languages but don't include them
Expected behavior
Demuxing should work the same as in 2.41.x
How to reproduce the issue
Activate Project Options -> Subtitles -> Demux preferred languages but don't include them
Open a file that includes subtitles of the preferred languages
Provide information
The temp folder for the file does not include any subtitle files. First I thought this was related to some kind of bad import of settings (which I didn't actually do really), but I when I made sure and recreated all relevant settings from complete scracth with 2.42.0 the issue remained.
The text was updated successfully, but these errors were encountered: