How many instances of a are there in:
Im loading AviSynth scripts in VirtualDub to edit shots in DVD videos. Some shots in the resulting processed videos are beginning or ending on a different frame from what is shown in VirtualDub (before processing the video). So Im ending up with a frame from a shot I dont want to show sometimes showing. This is turning out to be a huge problem to correct, because each video takes me more than 5 hours to process. So I have to wait 5+ hours just to see if one shot is beginning or ending on the correct frame.
Is there a way I can see the actual frame Ill be cutting on before I process the video? Or what is the correct way to do this so I dont end up with videos that show frames from shots I dont want to show?
Edit: Im also using Srestore and QTGMC to improve video quality, if that matters. I should also mention that I havent noticed this problem with frames when adding a deblocker to the AVS script.
Arent you using AviSynths Crop filter to define the parts you want to keep? Then VDub will show you the parts youre keeping before you do the encode.
Make sure to crop before screwing with the framerate with QTGMC. What kind of video are you editing (DVD, you said?) and what source filter are you using (MPEG2Source, I hope)?
What youre saying about the Crop filter makes me think maybe Im not using the correct terminology. I havent been using the Crop filter because Im not trying to carve down the shape of the frame, Im trying to prevent a fame from appearing in its entirety. So when I was talking about cutting, I meant in terms of frame sequence, not size, shape, dimensions, etc.
Does what youre saying still apply? If so, I would actually prefer to do my cuts before using QTGMC because its faster, but for this particular video and script, Ive been cutting after QTGMC because cropping before QTGMC results in one of the overlay images Im using in a replacement shot to bounce up and down.
The video Im editing is DVD, and I am using MPEG2Source. The output file is AVI.
Does what youre saying still apply?
I apologize. Youre absolutely right. I meant to say Trim. Have you been using Trims to keep what you want? With MPEG2Source, using Trims should encode the way you want. You can even check your work to make sure you got the frame numbers correct before doing the encoding. Again, perform the Trims before doing any filtering that messes with the framecount, unless youre very careful about how you do it.
If already using Trims, maybe post a script that results in the wrong frames being encoded.
No problem. I have been using Trim to try and keep what I want. Is there a way to Trim before using filters that mess with frame count, and also prevent the problem overlay I mentioned (ovl5) from bouncing?
I assume here youre not talking about anything beyond simply viewing the frames and corresponding numbers as they appear in VirtualDub? Or is there some other trick? Ive noticed when doing this that the frame being shown does not always match its corresponding number. I think I remember someone here saying that was due to random seeks, if I recall correctly.
Ive noticed two issues. The first is that the original frame 4776 (before being covered with my overlay) shows where I tell 4777 to show. 4776 and 4777 in the source video are two different shots, so this is a problem.
The second issue is that the timing of ovl7 appears to start earlier in the processed video than it appears to in Vdub before processing, and as a result, it doesnt completely cover what its supposed to in the processed video even though it does cover the part of the shot I want it to in VDub before processing.
Open both VOBs at the same time in DGIndex and make a single D2V project file. When opening, either corral them both with the mouse or use the Add button to add the second one after opening the first.
Doing that will allow you to simplify your script greatly. And, yes, having all those Trims at the end of the script will make it about impossible to get the frame numbers correct.

user
In the text, there are 196 "a"s.
assistant