-
60 fields -> 60 frames per second conversion
I can do this in vegas, and it work great. But the preview does not show every frame. So, bear with me while explain my process:
I create a 1440×1080 double NTSC 59.x project (though tried with regular 29.x project too..see below).
I import my 1440x1080i footage (from a sony CX7).
I add mike crash’s smart deinterlacer to the event timeline (it really should no be required in this process as what I need is a bob to fill in the fields but anyway.. it works)
I render this out to a suitable format. for example x264 720p60.
The result is a very nice smooth video where every field has been coverted to a frame (and resized/bobbed up, etc).
If I load the AVI into virtualdub I can step through every frame (60 a second) and see that each frame is a full frame, and that is is clear (i.e. no blending or ‘creation’ of fake frames has happened… just the filling out of the fields).
So this is doing exactly what I want… i.e. the same thing that would be achieved if I took the footage into virtualdub, and used the internal deinterlace filter to ‘split fields side by side’.
Now, as I say, having a project as 29.x doesn’t matter, so long as I render out to 59.x in the settings vegas overrides the project settings as you would expect.
great so far.
The only problem is, that with my project settings at 59.x I was hoping vegas would show the split and bobbed fields on the preview. However, it doesn’t 🙁
It just shows a regular smart deinterlaced frame, which stays the same for 2 frames. i.e. I have 30 frames, each duplicated:
F1 : F2 : F3 : F4 : … F59: F60
F1 = f2
F3 = F4
…
F59 = F60As I say, not a big deal, because it DOES do the correct thing on rendering, but it does mean that it is more difficult to work with the video in vegas for certain things as I cannot see _exactly_ what each frame will look like.
Anyone know how I can get vegas to show the field splitting on the preview panel ?
stu
-
3 Replies
-
It could be the H.264 reader that has the issue.
Have you tried rendering a short section to an intra-frame compressor codec (although as you did before, not one that is constrained to SD)?I’ve not come read that there is a flaw with 59.94/60p projects.
-
You mean instead of importing AVCHD/H264 m2t files into vegas, covert to cineform HD first, then import ?
OK, I’ll give that a try, but it isn’t a very convienient solution if it does work.
If you mean on the render out, the format specified there should have no affect on the project preview video window. And I’ve rendered out to huffuv, cineform, wmv9, mjpeg and all work fine.
I compared the frames in detail last night:
-on one monitor the rendered video (H264 720p60 in this case, but cineform, etc all behave the same way) in virtualdub.
-on the other monitor the vegas preview window.
I could then frame advance in both applications to compare the frames: this confirms my first post:
-the rendered output video is fine, each frame showing as a clearly defined frame (vegas has correctly created by bobbing up a single field)
-the vegas preview window just shows each ‘tween’ frame as a duplicate of the previous one.
Note: if I import the rendered output (the 60 FRAMES per second) video into vegas it previews each frame fine. So I agree that vegas does not have a problem handling 60fps video.
The point I’m making is that the preview window does not correctly split the fields into seperate frames like an output render does while ‘converting’ 60 FIELDS per second video to 60 FRAMES per second video on the timeline.
stu
-
It sounds like you’ve identified something quite lacking here.
I did mean that I supposed the problem arrived when you had a 60p print after this stage:
“I render this out to a suitable format. for example x264 720p60.”
However after reading the latter part of your reply to my post, I suspect there is a bug in Vegas. I’d assumed the lack of advancing was on the x264 reader having some dependency on the source being read at a 30 per second cadence. The result being in the Vegas case that the same field was presented twice, not that it should have been.
As you point out and clarify, rendering works fine, previewing doesn’t. Hence why Vegas seems to be off kilter.
I presume secondary monitor AND windowed preview both have this trouble? (ignoring the DV-firewire or BMD/AJA options you might have at your disposal).
Various distillations to 24p, 25p, 30p and 60p from the more dominant 1080i are only going to crop up more and more. So I’d recommend submitting this to Sony and hope that if someone there is aware of this thread, that they can add supportively and post here.
Reply to this Discussion! Login or Sign Up