23.976 & 29.97 on the same DVD?

[jriker1]

I have two movies, one was recording in 23.976 and the other 29.97. I know according to DVD standards you can not have PAL and NTSC on the same DVD, however can you have two NTSC movies on the same DVD that have a different FPS?

If the quick answer is no, how about in two separate VTS?

Thanks.

JR

[Matthew]

23.976 pulldowned to 29.97 + 'real' 29.97 can be included in the one PGC. There's plenty of DVDs that are a mix of film and video (namely tv series).

[Mug Funky]

yep, the "23.976" part has special flags that tell the DVD player to repeat certain fields to achieve a 3:2 pulldown pattern in 29.97 fps. this also means the framerate for that section is stil 29.97 and can be muxed in with the native 29.97 stuff. you can pretty much mix them together on a frame by frame basis.

most encoders have a 3:2 detection option, which just compares fields together and if they're similar enough, ditches one and replaces it with a flag that says "repeat this field". big space saver, and also allows the average bitrate to go up to almost 13mbps without going out-of-spec. sadly this can't be done in PAL, but at least we get more lines to enjoy :)

btw, NTSC and PAL can be mixed on a DVD, but they shouldn't be :) for instance, DVDmaestro has a little loophole where if you rename some NTSC assets to the names of the PAL ones, then re-load the project that refers to them, it'll let you load it up just fine. it'll probably poop itself when it compiles though.

[Trahald]

First you mix PAL and NTSC.. and the next day its raining frogs! ;)

Mixing ntsc and pal is only something you do if your dvd player can handle it and you dont ever think you will be switching player. its definately way out of spec.

scenarist would be a little harder to fool since if the modification date on the .vif (an indexing file scenarist makes) is older than the date on the mpeg file then it rescans the mpeg file and will stop when it sees its ntsc when the project is pal or vice versa. bad thing too is even if you do fool it(by monkeying with the dates), scenarist uses the index file during mux and would create something unwatchable if rff flags are involved at all.