Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
28th March 2005, 16:40 | #1 | Link |
Moderator
Join Date: Oct 2001
Posts: 3,530
|
Highlight information files
This is in response to a post in this thread by D3s7
I'd be happy to work with you guys on a common format as well. As you may know the pioneer in this was Dimad and MenuEdit. I contacted him awhile ago about his file format and received the specs. He admits they are not complete, but they look more like .scp statements in that they are in text. I will have to work with .scp as well, so this is a consideration - just how many ways (and interpretters) to use for highlight information. Of course if it's a binary representation (like .sup) that makes life easy. |
28th March 2005, 17:35 | #2 | Link |
ScenAid
Join Date: Mar 2003
Posts: 1,623
|
To get the discussion rolling on this what I've currently established into vsrip (purely for selfish reasons ) is a .bdx / .bov file
The .bov file contains a raw dump of NAV packets w/ type 1 or type 2 highlights ("new" / "use previous except for commands") the .bdx contains the PTS and the timestamp of the matching subtitle (one entry per entry in the .bdx) The scenarist format for highlight info is IMO, awkward. But then again, everything in scenarist is awkward. I imagine that ultimately the preferred item would be to have the highlight info and sub info all in one location. |
28th March 2005, 17:53 | #3 | Link | ||||
Moderator
Join Date: Oct 2001
Posts: 3,530
|
Quote:
Quote:
Quote:
Quote:
Tagged records would be nice for this - each object starts with a header that tells the length and type of data it contains. This makes skipping unwanted data easy, and is extendable. The .sup format almost uses this, and maybe could be adapted. It has a 10/12 byte (depending on how you look at it) "header" for each spu with the signature "SP" in the first 2 bytes, relative pts in the next 4, 4 bytes of 0, and then the SPU which starts with a 2 byte length. Last edited by mpucoder; 28th March 2005 at 17:55. |
||||
28th March 2005, 18:37 | #4 | Link | ||
ScenAid
Join Date: Mar 2003
Posts: 1,623
|
Quote:
Yes it could be combined into a single file but it was easist at the time to follow the pattern of the .sub and .idx files. The "time code" that i put in the .bdx file relates to the PGC time of that (matching the subtitle in the .idx) not the PTS timestamp Quote:
I'll have to check into the .sup format - might be easy to adapt and create a sup2 format or something w/ the extended info |
||
Thread Tools | Search this Thread |
Display Modes | |
|
|