Announcement

Collapse
No announcement yet.

New video drivers and YUV2 capture?

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

  • #16
    Gentlemen, just to satisfy my curiosity, did you have to apply my YUY2 patch to get it working, and did it work correctly on this new version?

    By the way, it's good to see Matrox is at last putting some time into the YUY2 codec. Maybe because it has become accessible to the audience (boasting not intended...), so it has become a quality issue?

    Another question; does the YUY2 codec now save its frames as keyframes? Until now, it didn't, which is a pain in the XXX if you try to edit the files (takes forever)... The latest version of avi_io has been modified to overcome this, by the way. Thanks Markus!
    Resistance is futile - Microborg will assimilate you.

    Comment


    • #17
      Yes, your patch works correctly also with this version of the Video Tools.(But "unfortunately" it isn't the cause of the problem)


      As i wrote in a precedent post, I've seen that the frame drops are not causal, and that exactly there are alternatively one frame captured and one dropped. (capturing YUY2 uncompressed, and with any resolution that I choose).

      I'm only a beginner, but this malfunction can't be associated to anything ? (fields, key frames, etc.)

      This problem is not related in any way to CPU or Disk power, because incredibly all works with Avi_io (also not enabling the "key frame" feature)

      Thanks for your help.

      T-rex / Raptor www.videomakers.net
      Italian Editing Video Forum

      Comment


      • #18
        Well, system specs... I seem to be on the wrong thread anyway, as I am using Win98... sorry about that.

        Anyway: Athlon500,MSI6167+256 MB PC 100 memory,G400+RR-G, ADS Pyro, AHA2940 UW, 18 G IBM SCSI HD, two IDE hard disks, ZIP-100... MX300 soundcard... I do not think there is too much common in our machines.

        M.
        year2000:Athlon500/MSI6167/256M/10GIBM/6GSamsung/18GSCSI IBM/CL2xDVD/RR-G/HPPSPrinter/G400DH32M/DeltaDC995/MX300/ADSPyro1394/AHA2940UW/3comXL100

        Comment


        • #19
          Phire: I'm still in the process of RMAing the card. I've got an RMA number already, but I need to get a temporary replacement to use in my macine while I send it in. I should be doing that this week. I'll let you know if it's all good once I get the new one in.

          -John

          Comment


          • #20
            I finally got the incorrect file reports using piped codecs. Some testing was in order....

            I did a series of captures using most of the common capture utilities and the 1.54 Video Tools. Where available I captured using the programs internal timer for consistancy. As mentioned by others the 1.52 Video Tools are unaffected.

            What was interesting was the difference in file sizes between affected AVI_IO captured files and those done by other programs. AVI_IO's captures were often half the size, mainly because they had half the number of frames of the captures done by the other programs.

            The 50% dropped frame reports seem to be an incorrect reporting of file stats because of incorrect actual frame rates relative to what is set. AVI_IO locks down its set frame rate, 30 or 29.970 fps for NTSC, as usual. The other programs are producing clips of 59-60 fps. Yup, you read it right.

            It's possible the fields are being saved as frames, doubling the frame rate and causing playback problems. It's possible that AVI_IO is, because of its tight frame rate conrol, clipping the rate to whatever is set. This allows for proper stats and fairly smooth playback relative to the other programs. Even so the AVI_IO files are not properly constructed.

            What's also interesting is that the DivX codec seems relatively unaffected even with the high frame rate and count relative to the duration.

            Dr. Mordrid


            [This message has been edited by DrMordrid (edited 23 May 2000).]

            Comment


            • #21
              So what's the consensus, then? Are these new drivers/videotools worthwhile?
              Resistance is futile - Microborg will assimilate you.

              Comment


              • #22
                Based on my tests it does appear that YUY2 is broken in this release. As such;

                For straight MJPeg captures VT-1.54 is fine.

                IF you plan on using YUY2 to capture to alternative codecs or plan on doing Ulead MSPro6 MPEG-1 or MPEG-2 captures I recommend sticking with VT-1.52.

                Dr. Mordrid

                Comment


                • #23
                  Doc, for straight MJPEG captures is there an advantage in 1.54 over 1.52? Or is it not worth the bother switching?

                  - Aryko

                  Comment


                  • #24
                    No advantage that I can perceive. If you have 1.52 installed and it works, don't fix it.

                    Dr. Mordrid

                    Comment


                    • #25
                      What would be good is if you could get skins to change the look of that boring gray remote. Now that would be good.



                      ------------------

                      Get paid to surf http://www.alladvantage.com/home.asp?refid=MAC649 it really works. Free Money.
                      Get paid to surf http://www.alladvantage.com/home.asp?refid=MAC649 it really works. Free Money.

                      Comment


                      • #26
                        You've been using WinAmp too much ;-))

                        Actually a nicer interface for PC-VCR would be nice, along with a few other mods. Time to start writing a list I guess ;-)

                        Dr. Mordrid


                        Comment

                        Working...
                        X