Chewtobacca

SilverWook said: Someone is going to have to watch the ABC and ThisTv versions side by side to catch any other slight differences.

I'm willing to do this.  I know the film and the differences between cuts very well.

Here's the scene as it appears in the ABC TV cut.  If your friend's recording matches, then he has what we hope he has.

If we can get something on which we can perform a successful IVTC, it will be a big improvement on what we have currently.  PCM would indeed be preferable.  And as long as the alternate material is there, it doesn't matter what the rest of it is like because we have better sources for everything else.

^^ Who says a bad idea never strikes twice?

It would be a pity if no one were in a position to capture this.  It might be our last chance to have a rare treasure in half-decent quality.  Oh, to work for a television station!

Harmy said: It's technically the same as if he was giving bootlegs of the official BDs as a "free gift" with the LDs.

 That's a clever way to put it.  Let's hope it achieves something.

You're not missing anything.  You did the right thing.

Beber said:  So, I wondered if some resynchronizing job was done or if one of the two releases went out of sync from this point at around frame number 144053 or 144054.

Yeah.  I checked, and frame 144053 of Harmy's 2.5 is not present in the GOUT.   This frame looks very familiar:  I'm fairly sure it's in the PAL GOUT but missing from the NTSC.

Darth Mallwalker said:  But when I wrote "GOUTs" as plural I only meant 'both NTSC & PAL ESBs' are the ones which begin 688.

Ah, sorry.  I was thinking of the two films that now have 2.x releases (i.e. not Jedi) and misinterpreted your post.  My mistake!  Thanks for the clarification.

Stinky-Dinkins said:

So does this only affect Empire, or is SW 2.5 affected too?

The title card for SW appears at frame 689 too, so both are affected according to this post.

Harmy said:Won't that recode the audio?

 No.

Harmy said: And wouldn't it be easier to set the delay in MKV Merge/TS Muxer anyway?

That depends on one's definition of easy.  I like to add the delay to the audio with eac3to so that I am absolutely sure that it's been applied when I watch.  But people can please themselves.

One frame is not likely to be detected, which is why nobody said anything before Darth Mallwalker checked the title card (even when the audio was being discussed).  I can confirm that the title card appears on frame 689 though.

Those who wish to fix this can run the audio tracks that they want through eac3to.

eac3to input output +42ms

The source is 24fps, but what you gave Harmy has a frame-rate of 29.97fps.  All the original frames are there, but more than 24 of them are being shown every second.  To restore the original frame-rate, you have to slow the video down.

I don't know what you did with PG and PSB.  If I can find them, I'll have a look.

EDIT:  Sorry, Puggo.  I didn't see your second post.  The setting you used in your encoder probably explains why you didn't have to slow down PG and PSB

EDIT:  I found PSB.  Everything looks fine, so what you did obviously worked. :D

EDIT:  Harmy, that problematic clip looks just the same as the others to me, and the same script works.

The file-size is fine by me.  I'd be happy to have a look.

That's almost certainly because you have a video that contains 29.97 unique images per second, and you're telling AE to make it 23.976fps.  It can do this in three ways: by discarding frames, by blending fields/frames together, or by slowing the clip down.  So far, it seems that you haven't found a way of making it do the last of these.

But none of that really matters because you have a way to slow the video back down to 23.976fps.  If Puggo really wants the video to be at 29.97fps (and I don't see why he would), you can do your work in AE, render the result, and then speed the clips back up with AviSynth.

AviSource()

AssumeFPS(30000,1001)

EDIT:  Harmy, I typed all this before I saw the correction to your post above.  I don't know why you are seeing combing with your project set to 29.97fps, but the fact that the DV codec is involved might have something to do with it.  AE might be programmed to handle DV footage in a certain way.

Puggo - Jar Jar's Yoda said:  I don't need any of that altered - in fact I don't want any of it altered in any way.  Just the colors corrected.  DVD pulldown will take care of the speed later.

It won't.  I understand what you are saying about not wanting anything to be altered at this stage apart from the color, and that's fine, but you shouldn't apply RFF flags to 29.97fps video.  At some stage, you will have to slow it back down to 23.96fps and then encode with RFF flags i.e. apply pulldown.

^ But we're dealing with a movie.  Movies hardly ever involve true interlacing, so there's no need for QGTMC or Yadif.  They can, of course, be telecined, but I see no sign of that here.

I don't have much experience with DV, but if DV (as opposed to one of its later variants) does not support 23.976fps, then the video might have been sped up to avoid having to telecine it.

Puggo - Jar Jar's Yoda said:  You wouldn't want to change the speed because I intend to do the pulldown later by setting the DVD pulldown flag on the final DVD.

 But that's not the point.  The video is at 29.97fps, and each of those frames is (as far as I can see) a unique image i.e. there is no telecine.  It has to be slowed down to 23.976fps.

I don't see any combing at all, so I think the video is just sped up.  Try slowing it down to 23.976fps in AE.

AviSource won't open it because of the codec used.  Even installing the Panasonic DV codec did not help; however, VirtualDub was able to open the AVI, so I rendered it to Lagarith and then used AviSource().

EDIT:  I got AviSource() to work by installing CedoCida.

AviSource()

AssumeFPS(24000,1001)

Using DirectShowSource() on the original file seems to work too.

DirectSource()

AssumeFPS(24000,1001)

If you send me the file, I'll have a look and see if I can decode it and then find a solution in AviSynth.  If I find one, I'll send back either a script or the video with the problem fixed, whichever is easier.

I say roll with the settings too.  The new look, while cooler, is a great improvement.

_,,,^..^,,,_ said:

myinternalorganwhichyoucanlivewithoutbutyoustillprefertohaveitnevertheless.org

_,,,^..^,,,_ said: I'm going to download the last version of both AviSynth and x264...

Good!  Stick to the 32-bit versions.  Render a lossless AVI, check it for errors, and encode from that.  And check your RAM with Memtest.

I caught the allusion.  It seems that we misspent our youths in a similar fashion.

_,,,^..^,,,_ said: wish me luck, I'll need it (in particular with the toothpicks affaire)!

Good luck! :)