interlacing help?

pfista

pfista

Well-known member
I don't know if this is interlacing or not, but whatever it is I want to fix it. I shot in 24p captured through a sony trv22 into vegas and it's on a 24p timeline progressive no interpolating/blending of fields. Yet about every 4 frames it looks like the quality is cut in half. I think it might have to do with how I am capturing the footage. I used to capture on a windows pc I built, but now I'm capturing on windows 7 x64 in bootcamp on my mbp. I don't know if that has anything to do with it. Any help is appreciated!

image2p.png

image3qc.png


 
Last edited:
Does the trv22 shoot 24p in 30i ? It looks like vegas isn't doing the IVTC properly

Did this same procedure with the same settings work on the windows machine?

Are you are capturing with vegas ? or using some other program? It shouldn't make a difference for capturing, but you could try windv to capture
 
Well I shot the footage on my dvx, I only use the trv22 to capture to help make my dvx stay healthy. So the trv22 only shoots in 60i, but I don't think that should matter when capturing.

Yes, this same procedure worked on my other machine and I captured with vegas.
 
Yes, it's in best. The strange thing is at one point when I would stop playback it would sit on "best" but when I played it would go down to "preview". I doesn't do that anymore though... it stays on best now
 
Best. I just remembered that when I captured through vegas after capturing it said average frame rate: ~27.34 or something like that. I also looked at the captured .avi files and the framerate is different from what vegas says.

For some reason vegas thinks its a 24p framerate? but it's really not?
 
I thought you said you shot 24p and put it on a 24p timeline?

When 24p is wrapped in 30i , many programs "think" or misidentify the footage as 30i (or really 29.97 and your clip properties shows it as 29). This is why I asked you earlier if it shoots 24p in 30i

Vegas usually handles SONY products successfully, i.e. it is able to read the header flag from sony products such as your camera, and can do the pulldown removal properly. It doesn't do this properly for other manufacturers like Canon, or if the cadence isn't simple 2-3.

The screenshot you showed looks like it didn't do the IVTC/pulldown removal properly

If you made a mistake, and actually shot 30i , putting it on a 30i timeline should make things ok
 
Here is what I did:

I shot 24p with my dvx. Then I put the tape into the trv22 and captured through vegas. After capturing I got this info from vegas:

Then I set my timeline as NTSC DV 24p in vegas and thats where the problems were.

I don't know why it's showing up as 29 when I view the clip properties in windows explorer. Do you think my footage is getting wrapped in '30i' by the trv22 capture camera?
 
Sorry , for some reason I thought you shot with the trv22....

I'm not familiar with either of your cameras, or what they might or might not be doing

I don't use vegas to capture, but doesn't the average frame rate indicate the speed of capture, not the actual fps of the footage?

You have some frame drops, which can mess with the cadence, instead of regular 2-3, this can be contributing to what you are seeing
 
pfista said:
Here is what I did:

I shot 24p with my dvx. Then I put the tape into the trv22 and captured through vegas. After capturing I got this info from vegas:

Then I set my timeline as NTSC DV 24p in vegas and thats where the problems were.

I don't know why it's showing up as 29 when I view the clip properties in windows explorer. Do you think my footage is getting wrapped in '30i' by the trv22 capture camera?
Click to expand...

No. The files are being captured as 60i files. ("30i" simply doesn't exist; it's an archaic term for 60i.) Vegas removes pulldown on the 24p timeline, but would use them as 60i files in a 60i timeline. So, Windows Explorer is identifying it correctly.

You do have some dropped frames, though, which could account for the pulldown cadence being off -- and if it IS off, the pulldown removal wouldn't operate correctly. I'd suggest re-capture.
 
So if I can capture successfully without dropped frames then it should work fine?

This method is exactly what I did on my desktop and it never really gave me any trouble. I never had dropped frames though.
 
You must log in or register to reply here.
Back
Top