A suggestion for future releases: If it’s dual audio, set the English audio track and signs (if any) to default. People grabbing Dual audios are probably interested in the dub and get dual audio for completeness. People wanting the Japanese audio have probably already grabbed one of the many Japanese audio only versions already, which are usually also several episodes ahead. Also, thanks! Good work on this.

@Dex_Luther No, that is not how track flags are meant to work, and labeling signs as "default" absolutely breaks the flags. Please read up here: https://www.matroska.org/technical/notes.html Scroll down to Default Flag. Default flag doesn't mean "this is played by default". Default flag means "this is intended to be selectable by language preferences as the main track of that language. All audio is assumed to have default set to yes if there isn't a default set for that language. For example both English and Japanese audio should have the default flag set to yes. The forced flag is intended for signs as it literally tells your player this track is intended to supplement the matching language audio track. By setting it to default, you're telling the player that the signs track is a full subtitle track and thereby breaking all automation for track selection as intended. Any player that doesn't abide by matroska spec for language preference settings is garbage and the end user should update to something modern that actually works as intended. Namely mpv.

@Spoony >No, that is not how track flags are meant to work, and labeling signs as “default” absolutely breaks the flags. I change the flags all the time. It's never broken. Settings Signs as default breaks nothing except if it's one of those releases where your "full subtitles" happens to not have any of the songs or signs in it, but that's a completely different issue than "breaking flags". When only one track is set as Default, which is how it's used 99.999% of the time (including this release), that is the track that is played regardless of your language options, unless the player has an option to force its preferences, but then default flags would be ignored anyway since they wouldn't be important. > _[MKVMerge documentation:](https://mkvtoolnix.download/doc/mkvmerge.html#mkvmerge.description.default_track_flag)_ If the user does not explicitly select a track during playback, *the player should select _one of the tracks_ that has its "default track" flag set,* taking user preferences such as their preferred language into account. * If both (or more) tracks are set default, the player will pick one of the tracks based on your language preferences. * If only one track is set as default, which is almost always the case, then the player will pick it no matter what your language preferences are because there's nothing else to select from, even if it doesn't match your language preferences. (Like saying "Pick a card," but only pulling one card out of the deck for you to pick from.) Either set them both default, which would be on spec, or switch the default flag from the Japanese track to the English one, which is how people actually use it. Since that is the track that most of the people who are interested in a dual audio release would want. As I said earlier, people interested in the Japanese track would have already gotten one of the many Japanese Audio versions and already be 3-4 episodes ahead anyway.

Settings Signs with the default flag breaks things. Period. Again, read up on the documentation. Giving signs the default flag makes the players assume it's a full subs track. Not giving the full subs track default makes it assume it's not even a track for selection. By giving signs default, you've thereby fully broken automation as with improper tagging it no longer can correctly pick the tracks people actually want. Because now people who want English audio and Signs, get English audio and nothing (because it's looking for a non-default forced track matching the audio language and you don't even have a track with that tagging) and people who want Japanese audio and Full subs get Japanese audio and Signs (because it's looking for a default non-forced track matching the sub language preference and you've given that to the signs track). So neither dub nor sub watchers with track preference settings get what they want in this scenario without manual selection or remuxing the release to fix it. You're relying on outdated players to simply play what is "default" and that will only work for the those tracks and require manual selection for the tracks that aren't... Which there is no reason to intentionally break automation by doing things wrong. Doesn't matter if 99.9999% releases do it wrong, it's still wrong. As for your final point, that is moot when done correctly, because automation kicks in and gives people the tracks they want without any manual selection required. If you're doing things wrong as you've suggested to do, of course people aren't getting the tracks they want automatically. Again, proper flags is: Japanese and English audio both default. Full Subtitle default, Signs forced. The order of track listing generally should not really matter, though some non-modern players and some playback solutions may make additional preferences based on track order. There is another guide available here that explains things well enough: https://thewiki.moe/advanced/muxing/

> If only one track is set as default, which is almost always the case, then the player will pick it no matter what your language preferences are because there’s nothing else to select from, even if it doesn’t match your language preferences. This might be the case with some older video players, but it's outdated information and outright wrong on modern solutions like mpv that have been updated to follow spec. If you read the documentation you'd see that if no tracks of a given language are given the default flag then ALL tracks of that language are assumed to have the default flag even if they don't. Therefore whether you give both audio tracks default or not, mkv spec dictates that both tracks are assumed to have default set to yes anyways as a fallback because it assumes that most people can't read and tag things wrong. mpv does not play tracks based on the default flag. It uses the default flag exactly as written in the mkvtoolnix documentation. In that it in no way picks the track to play based on the default flag and instead picks the track based on your preferences. Preference settings in most modern players are a literal requirement for proper playback because otherwise they have no idea what to select because they do not know what you want and the default flag isn't intended to be a flag that says "pick me" if no preference is set. In my experience in these cases they literally just select the first track listed in the case of no preference set. I think some players will pull info as to what language your OS is and fallback on that for language, so I've seen it automatically give me English audio and no subs at all with no preference set in some modern playback solutions. And again, we should not be muxing things wrong, just to abide by outdated playback solutions and instead mux things to modern standards for modern playback and encourage those holdout users to upgrade to something that actually works.

@spoony It's funny how you're talking about "Intended use" and specs, but you're not even following it yourself. According to the specs you keep referring to, you should have both audio tracks set as default or none. When you have only one audio track set as default, the "MODERN" player will use that. It has nothing else to "select from." It doesn't matter if that track matches your preferences or not. You can test this yourself. Take your dual audio release, change the language tag of the audio set as default to Chinese (or any other language tag), mux it, and then play it. I'm willing to bet that your player will play the one and only audio track set as default even if the language tag doesn't match any of your preferences because that's the way things work and has been used even if it's not the _"intended"_ use according to the specs. You also forget that most people are normies and don't have preferences set in their player, which is why 99.999% of all multi track releases of any media make the logical track choice for them by setting only one audio track as default. That's why I suggested if you've only going to set one audio track as default, then you should set the English audio track as default as that is the one most people will be interested in with a dual audio release (especially one that isn't a BD). The subtitle track flags work exactly the same as audio or even video ones. Signs & Songs lines should be included in "_Full_ Subtitle" tracks anyway. That way you don't have to rely on Forced subtitles. Many *MODERN* players (Jellyfin, VLC, maybe Plex (I haven't used Plex in a while) and probably others) don't play forced tracks at all, which is why most dual audio releases don't bother setting forced tracks. You should also probably tag your "Full Subtitles" track as JPN since it's _"meant"_ to be used with the Japanese Audio track. It makes the logic of matching via preferences logical (match JPN with JPN and EN with EN), and you don't have to rely on forced tracks at all.

Literally every thing I have released in the past couple seasons over at LostYears have followed the spec. Show me one I didn't. "you should have both audio tracks set as default or none." ... both set as default is exactly what I've said from the start. Setting none is absolutely wrong. If you set 'none' then it assumes you're an idiot and gives default to all. This fallback is why audio generally works despite not following spec. Again, doesn’t matter if 99.9999% releases do it wrong, it’s still wrong. You arguing otherwise is silly. It's illogical to intentionally keep doing things wrong simply because "it's what other people do". "MODERN players (Jellyfin, VLC, Plex) don’t play forced tracks at all".... Now you're just flat out lying. Literally all of these play forced flag tracks. There has never been a player that was unable to play them. It's simply a flag that tells the player this track supplements a matching language audio track. "You should tag your “Full Subtitles” as JPN since it’s “meant” to be used with the Japanese Audio."..... Absolutely no. This is wrong on all accounts and breaks things even worse than all your other incorrect suggestions. There is never a reason to lie about what the track is or contains. If you follow the spec, things work as intended. "most people are normies and don’t have preferences set in their player"... normies don't download videos to begin with, they stream them. Automation via preferences are a thing in all modern playback solutions. There's no reason to break that ability by doing things wrong. Before you had the option to say you were ignorant of how things work and accept that you've learned something today. Now that you're just spouting off lies, it comes across as nothing more than insincere trolling and it's clear you never bothered to read nor comprehend why you're wrong as you continue to push towards doing even more wronging instead of just accepting that things work as intended when you follow spec and there is no need to change that.

>Literally every thing I have released in the past couple seasons over at LostYears have followed the spec. Show me one I didn’t.  The specs you keep referencing says *both* audio tracks should be set as default. You keep referencing specs *AND YET YOU DIDN'T EVEN DO IT!* Instead; you do it like everybody else does and have only one audio track set as shown in the screenshot and then argue with me that I don't understand how default tags work. The way you've got your files set up doesn't even match what you're saying about the specs of the format you're talking about. *If there's only one audio track set as default, there's no reason to check your player's audio preferences.* In this case, as the documentation states and actual use confirms, the *ONE* audio track set as default will play regardless of what your player's preferences are set to (Unless your player has an option to ignore default tags and enforce your player's preferences no matter what), which is why I simply suggested that you set the English track to default instead of the Japanese audio track for future dual audio releases, but you argued that it's not how default flags worked. If you have *BOTH* audio tracks set as default, then it behaves the way the specs and you keep arguing. With both tracks set as default, the player looks to your preferences to choose which one to use. Also, If normies pirate games, and then post in the forums they got them from with all sort of issues simply installing the game, then they download all sorts of other things too. Including anime.

I see you're confused. Romux is not my release. I had zero involvement in this. I told you to go find something I worked on specifically over at LostYears, it helps if you can read that bit. So again, go find a release I worked on in the past season or two over at LostYears like I initially said, that didn't follow spec, I'm still waiting. The person behind Romux has stated they will be correctly tagging future releases to spec and likely re-releasing fixes for these episodes. Literally all the good dual-audio release groups follow this spec these days because it works as intended for everyone. If you're going to do something, there's no reason not to do it right. You're also still wrong about absolutely every bit of every thing else you said. With English default and Japanese not, it assumes you’re an idiot and gives default to the Japanese track as well. This fallback is why audio generally works despite not following spec. What part of this are you failing to comprehend? "If no tracks in a given language have the default flag set, then all tracks in that language are considered to have the default flag set." This is literally telling you that it's assuming the Japanese track will also have default since you have no Japanese track flagged as default because EVERY language you include requires having a default. Therefore, despite doing it wrong you end up with the same result as if you had given both default thanks to mkv spec assuming you're an idiot. You really have to learn to read the documentation cause you keep making me repeat what it says as you're failing to understand why you're wrong. At this point I'm just repeating the same facts from the first comment and you're just going in circles. It's moot, you're wrong and you seemingly can't accept that fact. There is zero gain from doing shit wrong. Arguing to do things wrong is dumb. What are you hoping to achieve by arguing to do things wrong instead of right?

>I see you’re confused. Romux is not my release. I had zero involvement in this. They also stated "ROMUX" wasn't actually their name. When I suggested simply setting the default audio language flag to the English track *instead* of setting the Japanese audio track as Default, you started arguing saying it wasn't possible because it's not how the default flag works. Since you're the one that interjected and the anonymous uploaded stated "ROMUX" wasn't their name, I assumed _YOU_ were the uploader. >A suggestion for future releases: > >If it’s dual audio, set the English audio track and signs (if any) to default. If you can set the Japanese Audio to default, which it currently is, then you can equally set the English Audio track to Default and remove it from the Japanese Audio Track obviously. This should have been obvious when I said this in the same post: >People grabbing Dual audios are probably interested in the dub and get dual audio for completeness. People wanting the Japanese audio have probably already grabbed one of the many Japanese audio only versions already, which are usually also several episodes ahead. You _CAN_ set multiple audio tracks to Default (recent LostYears release does this IIRC), and the player will use preference settings to choose which to use. This was *NEVER* what I was suggesting though. Basically, You're the one that has been confused. From the first post, what I was suggesting and arguing for was changing the command line or script (or whatever) used from this: ```Basic --track-name "1:Japanese 2.0" --default-track 1:Yes --track-name "2:English 2.0" --default-track 2:No ``` To this: ```VBA --track-name "1:Japanese 2.0" --default-track 1:No --track-name "2:English 2.0" --default-track 2:Yes ``` You're the one telling me that doing this was not "to spec" and was wrong, and that it didn't matter if other uploaders did it. Wrong is Wrong! You're the one that hasn't understood. Hope this clears up the confusion. I probably won't bother replying again.

You're still wrong, which is the point. You've said nothing correct from the beginning and yet you keep trying to convince yourself that you're not wrong rather than just taking the well deserved L and moving on. There is never a scenario where setting one audio language default and no others is correct. Because of everything stated above and below. It'll automatically assume they all have default, so why not just properly tag things? Matroska realizes 99.9999% of releasers are like you, who fail to comprehend how the flags are intended to work so they assume you got it wrong and have a fallback. There is no way to not tag a default track for each language and have it not assume all languages have a default, because the spec dictates that all language tracks are to have a default track set, period. Tagging English default and Japanese not, automatically assumes Japanese has default as well. The same as tagging Japanese default and English not, automatically assumes English has default too. So your suggestion continues to rely on the failsafe when you could instead just do it correctly. There is no upside to suggesting changes that do not correct what is actually wrong. You even went on to outright LIE about things such as players being incapable of playing forced tracks and then suggest muxers should lie about languages by tagging English subtitles as Japanese. Why do you keep advocating bad practices instead of just admitting that doing it right is the best method? For the umpteenth time: “If no tracks in a given language have the default flag set, then all tracks in that language are considered to have the default flag set.” This is literally telling you that EVERY language you include requires a default track. This does not mean one language gets default and another doesn't. Please finally acknowledge this fact and let it sink in. Take some time and try to comprehend this. It'll save you a lot of embarrassment in the future.

/me passes out popcorn...