Can I do this with IFOEdit?

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Visor
    Junior Member
    Junior Member
    • Sep 2002
    • 5

    Can I do this with IFOEdit?

    Okay here's the deal...

    I have the Transformers DVD box sets and I'm sick and tired of all the interlace errors that cause my Sony DVD player to comb pretty bad, especially in scenes with lots of red (which are a huge portion, just look at Optimus Prime). I wish Rhino would give up the Transformers license and give it to a company who actually had MONEY to telecine these sets properly.

    Anyway, here's what I want to do. I am going to rip each episode, re-encode the IVTC and reduce the resolution to 352x480 on each episode with TMPGEnc, and replace the old VOBs with these new "fixed" ones. I still want to keep all the original menus, etc so that it looks like I'm still using the original discs. However, the trick is how to fool the .ifo files into thinking that the re-encoded VOBs are no different from the originals. Looking at the .ifo files with IFOEdit, I see they are expecting 720x480 files. I need to downconvert them to 352x480 so that I can fit them all onto one DVD-R layer without too many compression artifacts.

    Do I need to change all the 720x480 entries to 352x480? It's pretty daunting to guess just how many entries in each .ifo I'll need to change... and I don't want to accidentally screw up and change one of the menu screens to the wrong resolution. Or is there some automated rescan option in IFOEdit that I've missed?

    Also, does anybody know how to remove all the junk screens at the beginning of these discs? I've read a couple of guides on removing FBI Warnings, but these discs don't follow the standard (the Video_TS.ifo file doesn't request any VOB IDs in the menu section)

    Thanks!
    Visor
  • Evanesco
    Junior Member
    Junior Member
    • Aug 2003
    • 3

    #2
    Use DVDShrink to get rid of the junk you don't want. After that start edit the new ifos with Ifo edit.
    How to do the rescan, I simply don't know...

    By the way, what is IVTC?

    Comment

    • Visor
      Junior Member
      Junior Member
      • Sep 2002
      • 5

      #3
      IVTC stands for InVerse TeleCine. To explain what it is, I should first give you a basic background of film-to-video conversion. Film material plays back at 24fps, but in North America the NTSC video standard plays back at 60 interlaced fields per second. 2 interlaced fields are required to make up one frame of video. In order to play back film properly on NTSC, a system has been adopted in which the first film frame is played for 3 interlaced fields, then the second film frame is played for only 2 interlaced fields, and so on. The process is called 3:2 pulldown, and allows film to be played back at the proper speed (among other things) when watching on video. This gets to be very important when you're watching material with a progressive-scan TV (such as HDTV) as any defects with the 3:2 cadence will become very apparent. There is an excellent animated write-up about how it all works here. (Scroll part way down to the section with the blue background).

      Anyway, for the Transformers box set, 3:2 pulldown cadence wasn't done correctly. There are many frames that are 3:3 and 2:2, causing the TV's and/or DVD's decoder to get confused and spew out combing effects and other artifacts. What TMPGEnc's IVTC does is take that NTSC 60 interlaced-fields-per-second video and convert it back to 24 frames per second by stripping out unwanted (defective) fields. Now you have a clean 24 fps source, which you can convert back to NTSC 60 ifps using TMPGEnc's 3:2 Pulldown option. Because all the unwanted fields have been stripped out using IVTC, the conversion back to 60 ifps creates a video with perfect 3:2 pulldown cadence.

      Make sense? Probably not. Don't worry, if you don't have an HDTV or play many DVDs on your computer, this stuff won't matter to you (at least not for the time being). At any rate, DVDShrink isn't able to do any kind of IVTC, so I need to use TMPGEnc for this kind of process.

      If you're intrigued with this stuff, more details (with great visual examples) about all the progressive-scan errors can be found here.

      Regards,
      Visor

      Comment

      Working...