Announcement

Collapse
No announcement yet.

4gb limit and avi_io

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #16
    Anyone wanting to see just how effective AVI_IO can be for long captures should check this image of a capture report from it:



    I don't think further commentary is necessary ;-)

    Dr. Mordrid


    [This message has been edited by DrMordrid (edited 09-28-1999).]

    Comment


    • #17
      Obviously that isn't going to work. Ohwell. I'll try d/l'ing it from my other site later.

      In any case the report shows 0 drops in a 130,869 frame capture using AVI_IO. Not too shabby Markus.

      Dr. Mordrid

      Comment


      • #18
        Hello Markus,
        AVI_IO is very good program, but unfortunely it can't be used as TV control program for TV card (Rainbow Runner). It has too much missed features for control TV card.

        I wrote my own program based of WfW, and added some functions for channel switching, view as desktop, TV tuning...( . So I have a question:

        Did you think about to write a DLL, with AVI_IO functions (continuous capturing without drops), something as extension of WfW ? The DLL, which could be added to, for example, my program ?

        StE[a]LtH

        Comment


        • #19
          DrMordrid or Markus,

          Every time I do a capture with AVI_IO, I usually get a frame dropped every minute or so, regardless of the setting. I read in your notes, Markus, that this was because of the Audio spacing, that even though there wasn't a dropped frame it was interpreted by the program as such. Certainly the results lead me to believe that I'm not really dropping any frames.

          According to that Mordrid, how did you get 130,000 frames without a drop?

          - Aryko

          Comment


          • #20
            Hi Aryko,

            You wouldn't be capturing NTSC with your frame rate set to 30 fps, would you?

            A lot of people seem to insist on capturing NTSC at 30 fps, when in fact NTSC is only 29.97 fps. The result is that every so often (every 33.3333... seconds) the capture program has to insert an extra frame (reported as a dropped frame) to make up for that fact that it has only received 999 frames after 33.3333.. seconds, but it is trying to create a file which should contain 1000 frames after 33.3333... seconds.

            (Hopefully I did my math right...)

            Rick
            http://www.Hogans-Systems.com

            Comment

            Working...
            X