Woodstock,
Even though this is an incredibly late reply I wanted to let you know that your suggestion to use
--stop-at duration:55
worked great.
Thanks to everyone who pitched in to help me out.
Search found 3 matches
- Fri May 19, 2017 8:03 am
- Forum: Command Line Interface And Scripting
- Topic: Custom start-at and stop-at commands not working CLI
- Replies: 6
- Views: 5134
- Fri Apr 21, 2017 12:47 pm
- Forum: Command Line Interface And Scripting
- Topic: Custom start-at and stop-at commands not working CLI
- Replies: 6
- Views: 5134
Re: Custom start-at and stop-at commands not working CLI
Hey thanks for getting back with me you two. rollin_eng: Below is my log. I let HBCLI (nightly) encode around 2.5% of the 23 Min 13 Second test video then I killed it using Q in cmd.exe [08:30:51] hb_init: starting libhb thread [08:30:51] thread 1 started ("libhb") HandBrake 20170416095940...
- Fri Apr 21, 2017 7:58 am
- Forum: Command Line Interface And Scripting
- Topic: Custom start-at and stop-at commands not working CLI
- Replies: 6
- Views: 5134
Custom start-at and stop-at commands not working CLI
Please detail your question or problem in as much detail as possible: I can not get HBCLI to recognize these two commands. start-at=duration:750:stop-at=duration:805 Start at 750 seconds and end encoding at 805 seconds. CLI keeps trying to encode the whole thing. I'll post my command line below. As...