I'm just wondering, but why have a subtitle track that's just the normal voice lines, and a seperate track that's just the TL signs but no voice lines? Why not just do one?
@vanquisher
Encoding can result in higher file sizes or even more artefacts than the source, which might or might not be worth it.
Disney+ is usually pretty watchable and for that show there probably isn't really much to filter.
mpv can handle anything that's related to light debanding and even anti-aliasing fine.
See: https://nyaa.iss.one/view/1763441#com-5
@WitchyMary I was just wondering because it defaults to JP audio, but it's set to force the Signs subtitle track instead of the normal one, so when you first open it, you get JP audio but no subtitles, so it's kinda missmatched.
@Yoder
The way this is tagged is correct and follows the modern matroska spec as shown here: https://www.matroska.org/technical/notes.html scroll down to Track Flags.
Signs track should be forced, all audio tracks should be default, and full subs should be default.
With any good player with proper configuration, it'll play as intended with your language preferences. If you're getting Japanese audio and English Signs, then your player configuration is completely busted.
Forced flag literally just means "this file is intended to play with matching audio track". It in no way "forces" the track to be played despite so many people believing this. So getting English forced track with Japanese audio would never even be a possibility unless something is broken on your end.
In mpv, since this file is tagged correctly, with 'alang=jpn' in your mpv.conf you'll automatically get full subs, while with 'alang=eng' you'll automatically get the signs track.
Comments - 24
usagiaddict
sorrow
SomaHeir
NodMan
vanquisher
Uchiah
zetsu_shoren
Yoder
eXmendiC
WitchyMary (uploader)
Yoder
ChaoXide
Clemons
Aryma
LastBreeze
Clemons
zetsu_shoren
Yoder
usagiaddict
iru
ghooul
zetsu_shoren
phantomshadow07
LastBreeze