Re: DVD authoring,copy,edit questions + misc :)

Hello Hakan,

First thanks for all the information you gave me!

On Tuesday 23 July 2002 10:25, H}kan Hjort wrote:
[snip]
> > DVD-9 to two DVD-5:
> > Lets say that I just ignore all other titles sets on the DVD and I
> > just deal with the main feature film. Merging the VTS_XX_0.IFO with
>
> If you just want the 'main feature film' you could just concentrate
> on the Titel Track for that, that will mostlikely be just one singel
> PGC in one of the VTS (Video Title Sets).  Not much difference though.
>
> > some plain vanilla IFO or just edit the one I have. Anyways my
> > question is what to do when I encounter problems like the "tricky
> > part" above. This could very well be a part of the end of the main
> > feature referencing back to a cell in the very beginning.
>
> Well if you don't want to shuffle the video parts around to avoid
> recalcutalting lots if tables and sector offsets you'll have to keep
> all of the VTS_XX_[123456789].VOB files as they are.

Hmm easier said than done if e.g. the last cell is belonging to VTS_XX_1.VOB 
while "the rest of the end" is belonging to VTS_XX_9.VOB. Note: I taking 
about the cases where the main film is not fitting into one DVD-5.

> > As for a general question in splitting a title_set, I would like to
> > know if you guys and girls has some bright algos where it should be
> > done. E.g. is there a easy way to detect where the second layer
> > beginns.
>
> Well there is some info in one of the structs that can be gotten
> from the drive.  Can't rember which one rigt now, look in SFF-8090.
>
Do you know where I can find that doc?

[snip]
> > In order to get DVD-Video support integrated in mkisofs I had to
> > make a very cut down version of libdvdread. Joerg the maintainer of
> > cdrtools simply didn't want to depend on dvdread since it is not
> > portable in his view.
>
> Not much is (or perhaps better but, nothing not written by Jörg is ;-)
Lol :-)

> > Hence I stole and wrote some new code in order to subsitute
> > functions that I needed from libdvdread. I hope I haven't stepped on
> > anyones toes doing this.
>
> As long as it's GPL, it's fine.  There shouldn't be much code needed
> to get at the parts you need.  Though it would be better, in my mind,
> if libdvdread was patched to _be_ portable instead (or also).

It sure is GPL, and yes it would be better to make libdvdread more portable. 
Trust me if I had the time before Joergs deadline I would have. Although is 
main argument agains libdvdread was the use of dlopen and I don't think you 
would have sacrificed that one to please Joerg.

> > Maybe a positive side effect of this is that the bsswap.h macros now
> > have a new more portable implementation. It can be worth taking a
> > look at it.
>
> Ok, can you send us this?

The easiest is probably to download it from 
ftp://ftp.fokus.gmd.de/pub/unix/cdrecord/alpha/cdrtools-1.11a27.tar.gz 
and take a look at bswap.h in the mkisofs directory.

It can be worth noticing that Joerg has made macros for the different Uint16 
etc. types used my dvdread. According to him his way is more portable. This 
was one of those things that I thought be a good thing to use in dvdread if 
you could take a look at it I could actually do some patches for libdvdread.

(Hmm, yes been taking about patches. They will come sorry for the delay simply 
over worked doing the DVD-Video support and a DVD backup program.)

> > Ohh, Joerg can sound a bit harsh in his portability comments - but
> > he is actually quite nice to work with after the ice has metled. I
> > assume that he just want to make every one regardless of OS benefit
> > from improvements in mkisofs - hence he holds portability very
> > dearly.
>
> Is the SPOSIX standard ready yet?
I actually don't know if it is. 

Cheers Olaf