Hi Roadkill,
More specifically (and accurately) , this Adapted Disc Type info in the VOB is located in a "DSI_GI" (Data Search Information General Information) which is just the "general info" for a larger Data Search Information (DSI) packet that resides at the Navigation Pack level of the VOB. The "Nav Pack" occurs on every VOBU (VOB unit) in the VOB; about once every half second. Here's what the info this DSI_GI describes (contains 32 bytes worth of data):
1) NV_PCK_SCR - System Clock Reference of Nav Pack
2) NV_PCK_LBN - Logical Block Address of Nav Pack
3) VOBU_EA - End address of VOB Unit
4) VOBU_1STREF_EA - End Address of the first Reference Picture in VOB Unit
5) VOBU_2STREF_EA - End Address of the second Reference Picture in VOB Unit
6) VOBU_3STREF_EA - End Address of the third Reference Picture in VOB Unit
7) VOBU_VOB_IDN - VOB ID number of the VOBU
*8) VOBU_ADP_ID - VOBU Adaption Identifier* <----- this is our guy
9) VOBU_C_IDN - Cell ID number of the VOBU
10) Cell_ELTM - Cell Elapsed Time
The whole DSI (Data Search information table) Packet includes (again, this occurs about twice a second - depends of number of frames in the GOP):
DSI_GI - DSI General information - 32 bytes - <---- contents listed above
SML_PBI - Seamless Playback Information - 148 bytes
SML_AGLI - Angle Information for seamless playback - 54 bytes
VOBU_SRI - VOB Unit Search Information - 168 bytes
SYNCI - Synchronous Information - 144 bytes
reserved - 471 bytes (big ole blank spot? :-)
Total DSI packet size - 1017 bytes
Each of the above headings have a whole bunch of data in them, just like I listed the DSI_GI's contents.
Then, along with this DSI Packet (DSI_PKT), which occurs twice a second in the VOB, remember; there's also a PCI packet (Presentation Control Information) occuring twice a second also, one for each Nav Pack. It has all kinds of goodies listed in there:
PCI_GI - Presentation Control Information general information - 60 bytes
NSML_AGLI - Angle Information for non-seamless playback - 36 bytes
HLI - Highlight Information - 694 bytes
RECI - Recording Information - 189 bytes
Total PCI packet size - 979 bytes
Each of these headings in the PCI are crammed with all kinds of data, including, interestingly, a flag which depends on the setting of the "adapted disc type" (VOBU_ADP_ID) over in the DSI: Macrovision can't be set for "on" if the adapted disc type is set for DVD Recordable.
Here's what we show for each Nav Pack in the VOB in TFDVDEdit. We have combined the data from the DSI and PCI for each Nav Pack to show to the user, what we've thought and has been requested and might be useful to be able to change (and copy and paste any changed settings into all the other Nav Packs of the particular VOB, by Cell boundary). We've got several things slated to be added here (what we're discussing, if the tests prove it worthwhile, right? :-), including the ability to attach specific audio streams to angles, so the remote angle key changes audio streams as well as the angle:
The Nav Pack has shown to be so important, that Ben Weinrach, Ian Shepherd, and Jake Russell formed the "Nav Pack" group at NAB! Here's what Ben Weinrach says about the Nav Pack group in the intro to his department (
http://www.tfdvdedit.com/public/department38.cfm) over at the TFDVDEdit support site:
"Way back at NAB 2004, a group of us casually formed a contingent we called “The Nav Pack”. Our objective: to push and abuse the DVD Spec in ways that can only be accomplished with TFDVDEdit. Unlike authoring applications, we now have direct access to the smallest unit of the DVD structure, the nav pack. There are numerous parameters to experiment with - many of which are directly related to the way overlays are displayed. At NAB, The Nav Pack tossed around some exciting ideas for ways to use this unique capability, and hopefully I’ll be able to share some of them here – once we know they work, of course… :)"
I think membership in the "Nav Pack" if free, btw :-)
So the point is, since this Adapted Disc Type data field is listed in among dozens (maybe hundreds) of parameters (that are read by the player twice a second) that ABSOLUTELY control what the player does in regards to the VOB it's playing back, and that this Adapted Disc Type setting is also located in the Video Manager, and must match the settings in the Nav Packs, this tells me that the setting is more than just window dressing. If so, then maybe, just maybe, we can help the player (surely there's some players that do something with the data?) playback our DVD recordables a little better, if these flags are properly set.
Thanks again,
Trai
PS. And thanks for the correction on the dual layer and DVD-R 1.0 data sizes. They're for sure not the exactly the same, like I said. I wasn't aware completely about their pit geometry. But a slightly wider pitch of the same length pits could definitely account for the data size total difference.
