Announcement

Collapse
No announcement yet.

480x480 SVCD size YUY2/HuffYUV with the Marvel

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

  • 480x480 SVCD size YUY2/HuffYUV with the Marvel

    SVCD size captures on the Marvel;

    1. Get AVI_IO ver. C 03.13 or later.

    2. Install HuffYUV 2.1.1

    3. Set up the Marvel with the 1.52 video tools and Flying Dutchman's YUY2 patch.

    4. Set up a capture using YUY2, 704x480, 44.1 khz and HuffYUV as the compressor. Set up HuffYUV using "Predict Left".

    5. As the LAST setup before capturing enter the Capture Settings and check the "Custom Frame Size" box. Set the size to 480x480.

    6. Capture the clips you need. After stopping each capture sequence AVI_IO will take several seconds longer to terminate the capture than usual. All is well, it'll come back to life in less than a minute.

    7. Encode using TMPGEnc 12a to the SVCD template. Since no scaling is needed the render goes faster.

    8. Author and burn the CD. Nero5 accepts the files with no problems.

    The quality is great.

    Dr. Mordrid


    [This message has been edited by Dr Mordrid (edited 07 December 2000).]

  • #2
    Doc,
    I've been playing with that for a while, but lately I've had trouble resizing Huff to 480*480 during capture. I swear it used to work, maybe an older version of Huff. All I get is chaotic noise for video and nice clean audio. It will occasionally work, but it is so hit and miss right now, that it isn't really worth it. I have had success using AVI IO with MJPEG full screen and frame with "84" for quality. Edit in MSP 6.0. Open the file in VDub and frame server it using the resize filter at 480*480 and using uncompressed RGB with Full Processing mode. Load the ???.vdr into CinemaCraft and encode. It also works well with VBR. The quality is very impressive, especially considering how convenient MJPEG is for capture, editing, file size and speed. CinemaCraft creates seperate audio and video elementary streams, which I-Author likes. And it does it fast. Use the MUX app and load them into I-Author. I am still optimizing the whole process, but it looks really promising.
    WinXP Pro SP2 ABIT IC7 Intel P4 3.0E 1024M Corsair PC3200 DCDDR ATI AIW x800XT 2 Samsung SV1204H 120G HDs AudioTrak Prodigy 7.1 3Com NIC Cendyne DVR-105 DVD burner LG DVD/CD-RW burner Fortron FSP-300-60ATV PSU Cooled by Zalman Altec Lansing MX-5021

    Comment


    • #3
      I get noise if I try capturing at 352x480 with the 1.52 drivers, but 704x480 seems pretty stable except for the post-capture slowdown. Otherwise it's been working pretty good.

      I don't like using transitional DCT based compressions like MJPeg. I prefer to capture to YUY2/HuffYUV then encode directly to MPEG.

      Dr. Mordrid

      Comment


      • #4
        Doc,
        I am using the latest drivers with VT 1.52. I can't seem to figure out why I am having trouble with huff 2.1.1. I am using the YUY2 hack, Format size 704*480, AVI IO, set to 480*480, using a FT 66 for capture, PCM audio at 44.1 kHz (doesn't matter if I capture with or without audio). It has me stumped, I do notice that after a bad capture I get a shaking in the TV output. It's almost like it swapped fields. I tried all of the settings in Huff, thinking the "swap Fields on decompress" would help, but nothing. I agree with you, Huff does do better for recompression than an already compressed format. It also makes sense to convert the same size video, rather than resize. Saves processing time and anytime you convert something, I don't care what format, you are going to get degredation of signal.
        WinXP Pro SP2 ABIT IC7 Intel P4 3.0E 1024M Corsair PC3200 DCDDR ATI AIW x800XT 2 Samsung SV1204H 120G HDs AudioTrak Prodigy 7.1 3Com NIC Cendyne DVR-105 DVD burner LG DVD/CD-RW burner Fortron FSP-300-60ATV PSU Cooled by Zalman Altec Lansing MX-5021

        Comment


        • #5
          The problems we're getting seem different. When I try capturing and get a "bad one" it looks like the hsynch is bad. But this is rare....

          Dr. Mordrid

          Comment


          • #6
            Hmm that's pretty weird that you get noise in 352x480 with the 1.52 drivers, does anyone else get this? I wish Matrox would just fix it so the latest drivers had YUY2 support.

            Comment


            • #7
              Doc

              How does it go with scenes containing fast motion? I have tried to make VCD's (PAL 352 x 288) but anytime I have faster motion (eg. panning the camera from right to left quickly), it is jerky.

              When I capture with MJPEG at 704 x 576 it's OK, but when I encode to MPEG I have this problem.

              Rod

              Comment


              • #8
                That's an encoding issue, not a capture issue. What you want to do in TMPENc is to go to the "Configure" menu and turn the motion estimation all the way up to "Highest Quality (very slow)". Most other MPEG encoders have similar settings.

                Dr. Mordrid

                Comment

                Working...
                X