average bitrate and fps capture - PROBLEM!!

PH125 wrote on 6/5/2004, 10:31 PM
For some reason the average fps and bitrate of my video capture is vearying a lot. I have gotten anything from 25.5 to 30.5 fps as my average fps capture, and 2.86 M/sec-3.84 M/sec for capture rate. I also have a fast comp (3.2 GHz processor with a gig of ram, so tht's niot the problem.

Vegas also says there's no dropped frames. I'm really confused.

Any ideas?

I am capturing NTSC by the way.

Comments

farss wrote on 6/5/2004, 10:37 PM
Capturing what through what, DV25 is 25bits/sec period as far as I know. Sounds like you're trying to capture through something that does on the fly mpeg compression and not firewire.
PH125 wrote on 6/5/2004, 10:43 PM
I am capturing through firewire 400 from a dv cam, as AVI. My last capture said 26.20 fps average capture rate and 3.44 M/sec as the average bit rate. As i said, i have a fast computer too, so this doesn't make sense.
farss wrote on 6/6/2004, 2:47 AM
Must say I've never even noticed a bitrate and fps indication during capture, maybe, just maybe your worrying about nothing if Vegas isn't reporting any dropped frames.
Did the captured avi look OK on the timeline?
At the end of the day thats all that matters.
Chienworks wrote on 6/6/2004, 3:26 AM
PH125, what capture software are you using?
TheHappyFriar wrote on 6/6/2004, 5:16 AM
I was going to say the same thing. I use iuVCR to capture. It says an average FPs durring capture. however, sometimes the average isn't what oyu'd expect (29.97) because when you start capturing, for a fraction ofa second it's 0fps, so the average is NEVER 29.97, but it doesn't drop any frames (i think that was fixed in recent versions, don't remember)
PH125 wrote on 6/6/2004, 7:31 AM
I use vegas 5 for capturing, and the fps dialog box appears at the end of the capture in the "post capture report" box, which also tells you if there were dropped frames, etc.
farss wrote on 6/6/2004, 7:44 AM
Oh, right!
Never looked at the thing, so long as there's no dropped frames (and I've never had any) I ignore it. Maybe the calcs are wrong or maybe they're a bit like the time to complete calcs in just about every Windows app. Probably the data rate is derived by dividing the size of the file by how long it was capturing for which could get some odd answers. Probably does the same thing with fps.
Beyond that I'd have to defer to someone else. If the capture is fine I'd just ignore those numbers.