Announcement

Collapse
No announcement yet.

Speed Encoder

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

  • Speed Encoder

    Hey guys and gals, for the past few months I have been getting alot of crashes with Speed Encoder, when I do, it always happen at the same spot on the timeline, I try making an HQ avi and put it on top of the section where it crashes but no good, once it crash, it will always crash at the same spot, my only workarond is to use ProCoder or the new plugin to encode and they always work but at turtle speed, I'm starting to think that there might be something screw up with memory in my system since it does use alot. What do you think?
    I7-6900K, X99 Taichi, Geforce GTX 1070, Corsair RM850X, Corsair H100 IV2, Windows 10, Edius WG 9.30

  • #2
    Try setting up the project to render to a second before the crash occurs and see what happens, then cut a space in the timeline and remove a second or 2 then render from that point to the end and see if it works. Then if that works just put a black clip in that spot and have 2 clips instead of one. It is a work around but will be faster. The advantage you have is knowing when the crash occurs use that to start testing.
    Chris

    Comment


    • #3
      Yeah I try that, it would crash right away, if I try to render from after that point then sometime it would render all the way to the end but sometime not.
      So this tells me that something on the timeline screw up speed encoder but not Procoder or the new plugin, what I don't understand is even when I replace that section where it crash with a new HQ file, it would still crash right there.
      I7-6900K, X99 Taichi, Geforce GTX 1070, Corsair RM850X, Corsair H100 IV2, Windows 10, Edius WG 9.30

      Comment


      • #4
        Khoi,

        Are you running the latest Speed Encoder?
        I've had zero crashes lately.

        How much RAM on your system?
        I tried 3gb and that was a flaky disaster. Now I run 2gb.
        Rusty Rogers | Films
        >TYAN S7025 - 32GB RAM, 2 x Xeon X5690's, 4 x 10k video HD's, Win10 x64, BM DecklinkHD, nVidia TITAN, 12TB DroboPro w/iSCISI connection
        >RAZER BLADE - QHD+ - 16GB RAM, i7-6700HQ Quad, 512GB SSD, Win10 x64, GeForce GTX 1060 6GB

        An inglorious peace is better than a dishonorable war.
        Twain - "Glances at History" 1906

        Comment


        • #5
          I have 3GB but now I look again it only show 2.5GB, so I think that there is something I need to look at.
          Thanks.
          I7-6900K, X99 Taichi, Geforce GTX 1070, Corsair RM850X, Corsair H100 IV2, Windows 10, Edius WG 9.30

          Comment


          • #6
            Go down to 2GB... kinda wierd, but it worked for me.
            Rusty Rogers | Films
            >TYAN S7025 - 32GB RAM, 2 x Xeon X5690's, 4 x 10k video HD's, Win10 x64, BM DecklinkHD, nVidia TITAN, 12TB DroboPro w/iSCISI connection
            >RAZER BLADE - QHD+ - 16GB RAM, i7-6700HQ Quad, 512GB SSD, Win10 x64, GeForce GTX 1060 6GB

            An inglorious peace is better than a dishonorable war.
            Twain - "Glances at History" 1906

            Comment


            • #7
              Yeah I will try that.
              Thanks.
              I7-6900K, X99 Taichi, Geforce GTX 1070, Corsair RM850X, Corsair H100 IV2, Windows 10, Edius WG 9.30

              Comment


              • #8
                Windows only shows 1.99GB for me.

                Speed Encoder worked fine for a test I did last month. About 1.2GB is in use with all the cores fired up when using Speed Encoder.

                Comment


                • #9
                  I too have been experiencing crashing with speed encoder recently. Same spot on the timeline always triggers a crash. I looked at the footage carefully and there aren't any timecode breaks, no visual or audio cues as to what might cause my system to crash. I'm currently on 4.54. Before this update, I've never crashed encoder.

                  Comment


                  • #10
                    If a crash occurs at the same place it usually indicates that there is some type of corruption in the file. Try to replace the clip and see what happens

                    Comment

                    Working...
                    X