I've built a fixed version, which works for me: Īctually I have just checked PAL-SUPs, so I can't tell if it works for NTSC-SUPs, too (BDSup2Sub defaults to 720x576). At this time, BDSup2Sub already decided to treat a SUP with that package header as "HD-DVD-SUP" and will throw an error. Unfortunately, HD-DVD-SUP and DVD-SUP use the same (outer) package structure so they can only be distinguished between during parsing of the command buffer. The reason is that BDSup2Sub can differ between BD-SUP and HD-DVD-SUP during import only because both format have different packet identifiers. Note that BDSup2Sub recognizes the extension "IFO" for SUP/IFO, but not "SUP". exported a file "english.sup" from a "VTS_02_1.VOB" and the according IFO is "VTS_02_0.IFO", then you need to copy the IFO and rename it to "english.ifo" to make BDSup2Sub accept it as input. BDSup2Sub needs a valid IFO file for each SUP file and both have to share the same file name (except the extension of course). Note that there are some limitations to this format though.įirstly, the palette and the screen size are stored inside an IFO file. regarding RLE encoding, palette definitions etc.) it's virtually the same as SUB/IDX. The SUP/IFO format as defined by IfoEdit/VobEdit is supported since version 3.9.0 due to public demand. It would have been more helpful is I said: RTFM, but there's no emoticon for that.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |