H265 encode time got worse but nothing changed

Discussion in 'General Software' started by 1031982, Jun 2, 2017.

  1. 1031982

    1031982 Just Started

    Anyone else encode video?
    I started using h265, and for a while one hour of video took about an hour and a half to encode.
    Now, an hour of video is taking a little over three hours to encode. This is with the same settings, and even pulling the original un-compressed video and using it for real results.
    Nothing has changed, if anything I have more space available and less programs running then before.
    This is of old VHS footage which was archived and I am just re-compressing it for so save space.

    In HandBrake, I am using h.265 at quality reference 19. If other settings are needed, I can provide them.
     
  2. zy

    zy zynine.com Staff Member

    Not too much, x265 is very taxing on the CPU.
    Have you checked your CPU temperature?
     
  3. 1031982

    1031982 Just Started

    My temp maxes out at 69C when encoding. When it's idle, the temp is about 43-45C.
     
    Last edited: Jun 2, 2017
  4. Chai

    Chai Administrator Staff Member

    Did you check the CPU usage? Did you disable Hyper Threading?
     
  5. 1031982

    1031982 Just Started

    CPU usage before encoding is between 1 and 5%, when encoding it jumps to 98-100% all cores maxed out.
    My CPU doesn't have Hyper Threading.

    I went as far as to disconnect from the net, and close every other program on my PC and that made no difference.
    I noticed when telling handbrake to make a 5 second preview file, it usually speeds through to about 50%, and then slows down.
    If I do a 10 second preview, it's quick to about 25%, then slower to about 50%, and then it starts crawling.

    If the encodes times were always this long, I wouldn't have thought anything of it.

    Also, if I have encodes queued, about four hours of video will take almost 20 hours to encode. The longer it runs, the slower it gets.
     
  6. zy

    zy zynine.com Staff Member

    Where is your source file and destination file located?
    RAM Usage?

    Defrag your primary hard disk?
     
  7. 1031982

    1031982 Just Started

    Without encoding, RAM usage is either around 40 or 50%. When encoding, RAM usage goers up at most 5%, usually only by only a couple hundred meg.
    Source file is on an internal drive, and destination is on a different physical internal drive. I tried placing the source on an external drive, and it made no difference.
    Originally, the source would be from either an external drive, or on the destination drive.

    And as I was writing this, I tried something and it seemed to have fixed it... I made a custom preset in HandBrake, and making a new one and using it seems to have corrected it. I have no idea why or how that would matter, especially as the settings are the exact same as the previous one.
    However switching between the two presets I made validated it. The old preset ran slow, and the new one ran properly.
     
  8. zy

    zy zynine.com Staff Member

    How about your OS drive? Try de-fraging it or use a SSD. HandBrake would be using your OS drive temp folder for caching/processing although your destination is some other drive.
     
  9. 1031982

    1031982 Just Started

    Ya, I have a few internal drives. What it comes down to is that all three drives are different.
     
  10. Chai

    Chai Administrator Staff Member

    Good point, maybe hard disk could be failing causing slow write speed. Hard disk scan perhaps?
     
  11. 1031982

    1031982 Just Started

    I got it fixed.
    Not sure why, but making a new preset with the same settings fixed it.
     

Share This Page