Announcement

Collapse
No announcement yet.

VirtualDub/TMPG causing W2K reboots

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

  • VirtualDub/TMPG causing W2K reboots

    I'm trying to encode DV AVIs output from Media Studio Pro 6 into SVCD compatible MPEG2 files using the DVSoft codec under Windows 2000. I've heard that the resizing in TMPG isn't brilliant so I'm using VirtualDub to resize and then frameserve the result to TMPG. My problem is that 5-10% into encoding, say, a 3GB file my PC reboots. This happens every time but not always in the same place.

    If I try and encode a 3GB DV type-1 avi using TMPG directly then I either get a reboot or some sort of application memory error reported.

    It has been suggested by a friend that the reboot of W2K signifies a driver problem, rather than a software problem. Reinstalling W2K and not installing any driver updates, but relying on the native W2K drivers, doesn't help the problem, neither does W2K SP1.

    My config is:
    Abit BH6 rev 1.0, BIOS SS
    Matrox G200 Marvel (PAL)
    256Mb Ram
    Maxtor 10 + 30 GB disks
    SB Live value
    ADS Pyro 1394
    Plexwriter 8432

    Is it possible that the problems are being caused by my Marvel?

    thanks,

    Justin

  • #2
    How do you get VirtualDub to read DV type-1 files?

    When I try this under W98SE i get an error so I assumed VirtualDub couldn't read this file format.

    Comment


    • #3
      I don't believe VirtualDub will read type-1 files.

      You need to have the Adaptec DVSoft codec installed on your machine (can be downloaded from the Adaptec site) and then export from Media Studio Pro/Premiere/whatever using DVSoft compression. This will write a DV type 2 file which can be read by VirtualDub

      Comment


      • #4
        Excuse my ignorance but I'm not sure of the difference between a type-1 and type-2 DV file. Is there any recompression involved if I do this?

        An alternative route that I've tried is to use AVISynth which can read type-1 files and then feed them to VirtualDub. The trouble I'm having though is that VirtualDub sees the file size as 360 x 288 instead of 720 x 576. I have the same problem with Windows Media Player so I suspect that DirectShow is the culprit.

        If your method doesn't involve recompression then maybe this is a better route.

        BTW, my goal also is to make SVCD's from DV source.

        Comment


        • #5
          Hi,
          This might be typical behaviour of ... overheated CPU while you encode to mpeg.
          Most mpeg codecs that use mmx heat the CPU much. If heat is a problem, the ystem may reboot in 30-50 minutes after you start enconing.
          You can either download temp. monitoring program to see the CPU temperature, or (if your MB has no sensor) check the cooler manually.

          Grigory

          Comment


          • #6
            ScottV - as far as I know there is no recompression involved (if you're using MSP then make sure that you don't tick the "recompress" box). As far as the difference between type-1 and type-2 DV is concerned, my understanding is that type-1 uses DirectShow and type-2 uses Video for Windows.

            Grigory - Overheating is a possibilty. I'll check to see whether the temperature is rising during an encode.

            Justin

            Comment


            • #7
              Am I right in thinking that VFW only supports files up to 2 gigs. If this is the case I won't be able to convert my type-1 file as it is over 3 gigs.

              I think I see what the problem is with AVISynth. It uses the default settings for the MS DV Codec and the default is quarter size (360 x 576 PAL). Unfortunately, I can't see any way to change this in AVISynth.

              It is possible in Windows Media Player however. In version 6.4 you just go into advanced properties and select full size. In version 7 you go into properties and set the DV quality to full.

              Comment


              • #8
                ScottV - As I understand it VfW does only support files up to 2GB but using the DVsoft codec I can create DV AVI files over 2GB which VirtualDub can read. If you want to try for yourself then the installation package for the DVSoft codec can be found at:

                ftp://ftp.adaptec.digisle.net/1394/hotconnect_ultra_v20_win.exe

                If you have any problems then feel free to e-mail me directly.
                --
                Justin

                Comment


                • #9
                  Thanks Justin. I'll give the DVSoft Codec a go.

                  I'm also trying another approach. I've got the source code for AVISynth and I've found the MS documentation for DirectShow so I can now see what needs to be done to read type-1 DV at full resolution.

                  I've also got hold of DirectX Media 6.0 SDK so I'm going to change the AVISynth source and recompile it. When I get it working I can give you a copy of the new DLL if you like.

                  Wish me luck.

                  Comment


                  • #10
                    Good luck!

                    Comment

                    Working...
                    X