Announcement

Collapse
No announcement yet.

Conversion problem

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

  • Conversion problem

    I updated to v4.6 and everything seemed Ok (apart from the occasional "Disk too slow error") but when I came to make a Mpeg from the timeline of the finished program the PC crashed, after about 5 mins of the conversion process.
    This was a big crash in that the PC actually switched off, its never done this before.
    I tried again, same thing happened. I tried using Pro Coder to make the Mpeg, same again.
    I tried a different format, wmv, same again. I looked at the wma that had been created and it played for around 4 mins, I then examined the video on the time line around that point for any problems and could find nothing, it was playing back just fine.
    I tried using the wma codec rather than through Pro Coder, same switch off after 5 mins.
    I'm puzzled, I have an identical spec machine (expect it has the HD Nx add on board) at home for editing and that machine gives no problems at all.
    Windows does not give the "your PC has recovered from a serious error" message upon re-boot but just boots as normal. Capture and editing are smooth and stable and the PC will run all day long, in fact I used to leave it rendering all night.
    PC spec is Asus canopus approved MoBo, Core 2 Quad CPU, Windows XP Pro, 2Gb ram, RAID 0 array for video, SATA system drive, EIDE DVD/CD-R, Nvidia 512Mb GT7300 graphics card.
    Any ideas? its driving me mad!
    System 1 - Win7 64/Edius 5.51/Asus P8/8Gb RAM/RAID0/i7 2600K OC/nVidia Quadra 600
    System 2 - Win XP/Edius v4.61/Asus P5 DH Deluxe/4Gb RAM/RAID0/Quad Core 2.4Ghz Q6600/nVidia 9800GT 512Mb/NXHD + other stuff

  • #2
    I've been experimenting further.
    I encoded the Edius timeline to a HQ avi file.
    I tried this on the Edius timeline and in Procoder and each time the PC switched off after 5-10 mins, it varied.
    I then used the free Prisim encoder to output a wma file.
    This was perfomed without a problem.
    From this the only conclusion I can come to is that it is Edius/Procoder related.
    System 1 - Win7 64/Edius 5.51/Asus P8/8Gb RAM/RAID0/i7 2600K OC/nVidia Quadra 600
    System 2 - Win XP/Edius v4.61/Asus P5 DH Deluxe/4Gb RAM/RAID0/Quad Core 2.4Ghz Q6600/nVidia 9800GT 512Mb/NXHD + other stuff

    Comment


    • #3
      Update to 4.61 and then try it.

      STeve
      Steve
      EDIUS Trainer, Grass Cutter Gold
      A proud EDIUS EDITOR
      For more information on the Grass Cutter program please visit: http://www.grass-cutters.net

      Comment


      • #4
        Originally posted by Stereodesign View Post
        the PC switched off after 5-10 mins, it varied.
        are your basic PC settings correct for editing performance

        1. hibernate = off
        2. screen saver = off
        3. power saving features = always on for all
        4. startup and recovery/automatically restart = off
        Anton Strauss
        Antons Video Productions - Sydney

        EDIUS X WG with BM Mini Monitor 4k and BM Mini Recorder, Gigabyte X299 UD4 Pro, Intel Core i9 9960X 16 Core, 32 Threads @ 4.3Ghz, Corsair Water Cooling, Gigabyte RTX-2070 Super 3X 8GB Video Card, Samsung 860 Pro 512GB SSD for System, 8TB Samsung Raid0 SSD for Video, 2 Pioneer BDR-209 Blu-ray/DVD burners, Hotswap Bay for 3.5" Sata and 2.5" SSD, Phanteks Enthoo Pro XL Tower, Corsair 32GB DDR4 Ram, Win10 Pro 21H2

        Comment


        • #5
          Updated to v4.61
          Still doing it.
          are your basic PC settings correct for editing performance
          Yes.
          System 1 - Win7 64/Edius 5.51/Asus P8/8Gb RAM/RAID0/i7 2600K OC/nVidia Quadra 600
          System 2 - Win XP/Edius v4.61/Asus P5 DH Deluxe/4Gb RAM/RAID0/Quad Core 2.4Ghz Q6600/nVidia 9800GT 512Mb/NXHD + other stuff

          Comment


          • #6
            Is the destination drive near its capacity?
            Steve
            EDIUS Trainer, Grass Cutter Gold
            A proud EDIUS EDITOR
            For more information on the Grass Cutter program please visit: http://www.grass-cutters.net

            Comment


            • #7
              300Gb free out of 500Gb total space.
              Surely that must be enough?
              System 1 - Win7 64/Edius 5.51/Asus P8/8Gb RAM/RAID0/i7 2600K OC/nVidia Quadra 600
              System 2 - Win XP/Edius v4.61/Asus P5 DH Deluxe/4Gb RAM/RAID0/Quad Core 2.4Ghz Q6600/nVidia 9800GT 512Mb/NXHD + other stuff

              Comment


              • #8
                Is your virus scan on or off?
                Steve
                EDIUS Trainer, Grass Cutter Gold
                A proud EDIUS EDITOR
                For more information on the Grass Cutter program please visit: http://www.grass-cutters.net

                Comment


                • #9
                  I had exactly the same problem a couple of years ago. Turned out to be the CPU temperature shutting the PC down. Replaced the fan and all was well again.

                  Seemed to only happen when Procoder was converting. My supplier suggested Procoder was very CPU intensive.

                  Just a thought.

                  Comment


                  • #10
                    Virus scan is off.

                    CPU temp is interesting, when I compared the two PC's (which are near identical) the problem PC does have a different CPU fan. Hmmm...?

                    I'll fiddle about with it tomorrow and report back.
                    System 1 - Win7 64/Edius 5.51/Asus P8/8Gb RAM/RAID0/i7 2600K OC/nVidia Quadra 600
                    System 2 - Win XP/Edius v4.61/Asus P5 DH Deluxe/4Gb RAM/RAID0/Quad Core 2.4Ghz Q6600/nVidia 9800GT 512Mb/NXHD + other stuff

                    Comment


                    • #11
                      Ok, this morning I turned off all the intelligent fan control in the BIOS so the CPU fan is running at a constant speed and left the side off the case.
                      I performed a conversion to wma in Procoder and monitored the CPU action in Task Manager.
                      CPU activity spent most of the time amount 50% peaking at 62% never dropping lower than 39%.
                      PC did not crash as before, so maybe the CPU temp was the problem?
                      I'm going to continue playing around all day to see what happens.
                      The CPU heatsink and fan is a Scythe Mugen (Infinity).

                      Thanks for all the help so far
                      System 1 - Win7 64/Edius 5.51/Asus P8/8Gb RAM/RAID0/i7 2600K OC/nVidia Quadra 600
                      System 2 - Win XP/Edius v4.61/Asus P5 DH Deluxe/4Gb RAM/RAID0/Quad Core 2.4Ghz Q6600/nVidia 9800GT 512Mb/NXHD + other stuff

                      Comment


                      • #12
                        Hope I've pointed you in the right direction.

                        I used HMonitor from http://www.hmonitor.net/ to see what was happening to the temperature. As soon as Procoder started temp rose until it shut down!

                        Comment


                        • #13
                          I've been doing some more encoding.
                          Today I attempted to encode another timeline into wmv. after 2 minutes the PC shut down again, no warning at all.
                          I then set the same avi encoding to wmv with Prism and opened Task Bar to monitor CPU activity.
                          Prism does bot shut the PC down and the CPU activity is identical to that shown when ProCoder is running.
                          I am now certain this is a Procoder/Edius problem, just poor code somewhere n the application.
                          System 1 - Win7 64/Edius 5.51/Asus P8/8Gb RAM/RAID0/i7 2600K OC/nVidia Quadra 600
                          System 2 - Win XP/Edius v4.61/Asus P5 DH Deluxe/4Gb RAM/RAID0/Quad Core 2.4Ghz Q6600/nVidia 9800GT 512Mb/NXHD + other stuff

                          Comment


                          • #14
                            Is it a complete shut down (and it stays powered off), or a reboot?

                            A reboot might be a BSOD if you have automatically restart enabled and aren't writing a full memory dump.

                            If it's shutting down and staying shut down, then it's more likely a hardware-issued shutdown, like a thermal trigger.

                            Comment


                            • #15
                              Its a complete shut down and stays switched off.
                              The Pc does not get very warm at all, it takes literally 2 minutes for the PC to shut down when encoding in Procoder, hardly much time to heat up.
                              Using Prisim it runs all day without a problems and gets much warmer to the touch as a result.
                              System 1 - Win7 64/Edius 5.51/Asus P8/8Gb RAM/RAID0/i7 2600K OC/nVidia Quadra 600
                              System 2 - Win XP/Edius v4.61/Asus P5 DH Deluxe/4Gb RAM/RAID0/Quad Core 2.4Ghz Q6600/nVidia 9800GT 512Mb/NXHD + other stuff

                              Comment

                              Working...
                              X