Moth3r: I see in my Device Manager that I have two entries for my PDI Deluxe card (both with exactly the same wording). Digging into the "Details" of each of those two, going through the list ("Device Instance ID" "Matching Device ID", etc), I find that a what they say in the big white field does not always match from one to the other. (One's sting of stuff will end in "48" and that other in "49", things like that.) But I notice that in "General/Location" or their two properties pages, one entry reads "PCI bus 0, device 9, function 0" and the other reads "PCI bus 0, device 9, function 1". Is this just a complicated device that needs two Device Manager entries, or does this point to me having screwed up on installing the driver(s) somehow? This is particular area (deciphering device driver details) is not my area of expertise at all I freely admit. Is there a better place to look for that setting ("frames or fields") than here in the device manager?
And 29.970. Cool to finally have that setting nailed!
Arnie: (Putting very briefly) With NTSC, only some of the frames are interlaced, the others look progressive. So IVTC for NTSC does both some de-interlacing and frame dropping (plus the frame rate change) in the correct patterns.
The footage I will be transferring down the road (after I have adequate knowledge and experience) is indeed from sources that I will want to keep interlaced: Camcorder stuff, super-8 films footage transferred in ways that did not assure 24fps accuracy, would not be good candidates for doing ITVC. Hence, I wish to just leave most if not all of it interlaced. For my tests right now, I'm obviously not using (wearing out) those tapes; just more disposable stuff.
Actually, I've been doing my averaging without IVTC'ing so far -- yes, interlaced averaging -- and it works/looks fine (within one of the two aforementioned groupings).
I know that IVTC'ing will wipe away the 3:2, but I'd still need to shift one group up or down a line to make them match up. While I know that's not hard, I'd still like to see if I can find a way to just not have this difference happen with my captures in the first place (if that's even possible). Do you happen to know if what I'm experiencing is standard or if it's strange? Maybe it's unique to my set-up due to my having a bad setting somewhere and I can fix it. That's my hope I guess.
While I'm here.... Should I capture at 29.970 or 29.976 fps? I have yet to find a web page with the cases behind those spelled out (feel free to just give me a link).
Is there a way to turn off field capturing and switch to frame capturing?
Not than I can see. In VirtualDub there is "Swap fields" but in looking that up and trying it, that is not of any help (it really screws the captures up, a fix for something that's not broken with my particular capping set-up). I did more searching around the internet just now and still found no one else having talked about this particular bizarreness. At least my captures all look great and beautiful, and for that I am thankful. I could just discard ~half my caps, do only an averaging of the "shifted down one line" versions I guess, but the learning side of me would really like to know what is behind this weirdness rather than give up and do simply what works in a state of ignorance. (<-not to mention the time of having to do up to 10 or 11 captures instead of a straight 4 or 5 for everything I wanted to do averaging on!)
I did more tests to make sure I wasn't imagining things, and the same still holds. To risk being repititious (just hoping I'm doing helpful clarifying), doing a slew of caps of one scene will result in two "categories", the interlacing starting point (and flowing 3-2 style) at a different point between the two but consistent within each, and one of the two varients is lowered one scanline compared to the other (i.e., all of the captures that are in the "shifted down one frame" category will have an identical interlace pattern throughout the footage and are completely "average-able" barring an auto-inserted duplicate frame every few minutes).
Thanks again for the replies and trying to help me look into this Arnie.d.
Is that what you meant by "kicking in at either top or bottom field".
Yep, that's what I meant. I just assumed when I started all this that the capture card would decide at its starting to always do the (field) capturing one way, the "best" way -- or that at least I could click a setting somewhere to force it to start the capture only when the requested field passes through its clutches, the way your canopus appears to do (according to your edit text above). As you may know, the PDI Deluxe capture card is well regarded, 'twas used for the X0 project, so I can't imagine this 'problem' I'm having as being a real one. Did the X0 people really have to do multiple captures to get ones that "took" right and disgard the ones that were the wrong field first? Or is there another piece of this puzzle I don't know about? I'm just not finding that friggin' control/option select which I think must be there somewhere!
I know they could probably answer this at doom9.org (where I've read gobs of stuff over the years of course), but I feel I have already have too many memberships on bbs's going, and my signing on here has to do with more than my wanting to ask one technical question about video capturing -- but I'll keep that reason a secret for the moment I think. If after a while no one has an answer I'll go over there, but I'm not in a huge hurry on this project or anything.
I'm a filmmaker who has a pile of projects on NTSC VHS's that I want to preserve into big (interlace-kept) avi's in high quality. I've been reading on this and other forums for years about doing such things; have bought the equipment and been doing learning tests off and on for awhile now. Gosh, there are so many things to learn about and keep track of with this! Anyway, my first question that I haven't found an answer to in my knowledge-aquiring/trial-and-erroring/googling...
When I do multiple captures of the same scene, the field order seems to be random initiated (<- my guess anyway). To explain: in viewing the resulting supposed almost identical captures in VirtualDub, half of my captures of the scene will have cut x be a clean "progressive" style cut from one shot to the other while the other half of the captures of the same scene will have that same cut interlaced. (I also notice that one style is always a scanline lower than the other.) I basically understand what is happening I think. At each starting of the capturing, the capture card is kicking in on either the top field or the bottom at its start, resulting in two different looking types of captures in the end, right? But I ask... a) Is one of the two results more "correct" than the other? (I would assume that the one shifted down a scanline might be the "wrong" one if there is such a thing) b) Is there a way to have all the captures turn out the same in this regard, a setting in VDub or something? (I am wanting to do to multiple captures and carry out the "averaging" technique with Avisynth, but as it is I have to throw out half my captures because averaging both of these together will create a mess as I want to keep things interlaced).
Sorry if these turn out to be rather basic questions, but I promise I've been trying to seek the answers on my own and they've just eluded me so far. Thanks for listening.
Rough capturing approach specs: Hardware - AMD Athlon 2100+, PDI Deluxe card, JVC 9911U S-VHS Software - VirtualDub or IuVCR for capturing, HuffYUV codec, Avisynth 2.5 (for averaging after capturing)