![]() ![]() And if it doesn't find the ISO language code in the file name, it searches also for the full name of the language (in English only), like in this example: subtitle_French.sup. For example, with this file name, it assumes French: ack_. And even in that case, BD3D2MK3D tries to find the language automatically with the file name. Therefore, the window should be displayed only for BD SUP conversions. Therefore, the window should not be opened.Īlso, BD3D2MK3D assumes that the language code present in a IDX or XML file is correct and doesn't ask you to confirm it. Normally, it is used only when the language is unknown, and when a BD is converted, the language is known, because it is retrieved from the MPLS by tsMuxeR. Can you confirm that you had that problem when doing a complete conversion of a BD to 3D (and not when converting a subtitle with the "Convert subtitle to 3D" tool) ? It is strange that you had that dialog when converting a BD. OK, I think I've fixed the bug of the language selection window behind the others. Sub #30 ("Let Sola have a hatchling.") is the one that gives a 0 from the tool but visual inspection suggests a 10 (or there-abouts) is more appropriate. To that end, I've uploaded the John Carter forced sub track and corresponding planes file. This would also fit in with most players given they don't even bother displaying a "soft" subtitle in the event you skip the first frame it's displayed, suggesting they don't give two hoots about what happens after that first frame. If you combine that with the behaviour of TotalMedia Theatre, which actually changes the depth while the sub is still displayed, I'm wondering if there's actually some kind of "rolling" depth - each subtitle is displayed at the depth last encountered before it goes up if a new depth wasn't set on the first frame. Setting the margin to 0 only affected Cars. The first two subtitles in Immortals are correctly set to 0, but Cars 2 has a 0 where a 14 should be and John Carter has a 0 where a 10 should be. Thing is that often seems to return a 0 output, where a 0 isn't necessarily correct when viewed from the original disc. Fairly obvious in function and the number following it indicates the number of frames the subtitle is visible for which don't have a defined depth. I've been running through the last of my movies with forced subs and occasionally I'll see a "UndefinedFrameDepths" in the XML. ![]() On a slightly different note, I've found another curiosity. It seems to be happier the second time around, though, and that includes simply hitting the "Convert subtitles to 3D." button again and dismissing the error. Basically it's not accepting any input aside from moving it around by dragging the title bar, and even while doing that it's behind the window for all the other settings. You might need to put up a bugfix for that one - when it comes up asking to select the language for the resulting generated 3D subtitles I'm having trouble interacting with the new little window. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |