Log in

View Full Version : Export Scenarist Script in IFOEdit??


iomagic
25th December 2002, 02:04
Hi all!
I'm the first time poster, and I did my best to read the guides, try all suggestions, read the forums - hope I don't come in as an idiot to your wonderful community! I did not pass the "Matrix certification" yet, but I don't consider myself a newbie either ;)

It seems to me that if only Derrow could add script exporting to the IFO Editor (well, along with asset extraction), then the whole DVD backup process would get to:
1. Open VIDEO_TS.IFO
2. Export script and extract all assets from all the VOBs
3. Load this script into the Scenarist, and voila! - you have the *complete* scenario, will all the assets, with navigation, with chapters, with subtitles.... the whole damn thing!

Now the fun part: just change there whatever the heck you want! Reencode the video - drop it back and reauthor. Remove unwanted streams. Change your first-play pgc pointer. Add your logo. Play with multiple PGCs and angles. Won't life become instantaneously simple and beautiful?!!

It appears to me that this is a very feasible idea, since Derrow obviously knows IFO files better than anybody else on Earth, and Scenarist script has pretty straightforward contents.

Am I a complete idiot for dreaming about this nice little feature?

Regards,
Iomagic

klona
27th December 2002, 10:30
I also found the idea magic.
But not sure it's so simple to do it.
If DVD have only one vts with a simple standard menu and no special things like multi angle, seamless branching etc. it would be probably OK.

BEvery dvd is unique, and we can see that latest ones are often more complex than before.

It would be great anyway if it could work with even 20% of the DVD, and magic if 80% can be achieved.

But now Derrow has a full job and this seems a huge project...

iomagic
27th December 2002, 19:58
As Gorbachev would say to the Soviet People repeatedly "No-one said it would be easy" ;)
My understanding is that Scenarist script is very straightforward - meaning, when you know what you want to describe, it would be relatively easy to describe. The main problem would be to interpret the IFO information, mostly navigation. All these darn cell pointers should become useless crap, because they will get regenerated during compilation. The main problems are creating proper VTS/Title/PGC structures; Chapter points; Navigation and menus - and all this information Derrow already parses and shows, so he knows all this information.

Derrow, if you read this, would you like to comment? I'd be happy to help with coding.