Quote:
Originally Posted by Stereodude
AFAIK, piping can't seek either. The workaround is a giant pain. I have to make a unique .avs for every segment the outputs the right frames using trim, and then I have to make a unique .chp for every segment/x265 call that's shifted by the correct amount.  |
Can you shed more light on what you are trying to accomplish?
Why would a chp file be affected by seeking support? Suppose it's a chapter file, and x265 does not take chapter files as input.
Talking about my experience, if I want to backup a movie, usually I want to encode it in multiple segments. I have scripts which can produce "import().trim()" type of AVS files, and I encode them in different batch, then concatenate them together, attach the chapter, and call it a day.