start-at stop-at parameters not working as expected

Discussion of the HandBrake command line interface (CLI)
Forum rules
An Activity Log is required for support requests. Please read How-to get an activity log? for details on how and why this should be provided.
Post Reply
AndyA
Posts: 12
Joined: Mon Apr 10, 2017 5:45 pm

start-at stop-at parameters not working as expected

Post by AndyA » Wed Jan 30, 2019 5:05 pm

Description of problem or question:

In the GUI if I select Range (seconds) 1000 - 1050 it gives me a 50 second output result as expected. I think I'm using the command line parameters correctly as documented by they don't give me a 50 second output as the GUI does.

CLI Help Documentation -

--start-at <string:number>
Start encoding at a given duration (in seconds),
frame, or pts (on a 90kHz clock)
(e.g. duration:10, frame:300, pts:900000)
--stop-at <string:number>
Stop encoding at a given duration (in seconds),
frame, or pts (on a 90kHz clock)
(e.g. duration:10, frame:300, pts:900000)

My Command -

--title 162 --input "/Volumes/D/Movies/MyMovie" --start-at duration:1000 --stop-at duration:1050 --output "/Volumes/D/Movies-MKV/Movies/MyMovie .mkv" --markers --format av_mkv --encoder x264 --quality 18 --encoder-tune film --encoder-preset slow --encoder-profile auto --encoder-level auto --vfr --aencoder copy --audio-copy-mask aac,ac3 --audio-fallback ca_aac --mixdown 5point1 --ab 768 --subtitle scan --native-language eng --subtitle-burned

Console Output -

[11:54:29] starting job
[11:54:29] job configuration:
[11:54:29] * source
[11:54:29] + /Volumes/D/Movies/MyMovie
[11:54:29] + title 162, start 00:16:40.00 stop 00:34:10.00


Steps to reproduce the problem (If Applicable):

See command line.

HandBrake version (e.g., 1.0.0):

1.2.0

Operating system and version (e.g., Ubuntu 16.04 LTS, macOS 10.13 High Sierra, Windows 10 Creators Update):

macOS Sierra 10.12.6

Woodstock
Veteran User
Posts: 3217
Joined: Tue Aug 27, 2013 6:39 am

Re: start-at stop-at parameters not working as expected

Post by Woodstock » Wed Jan 30, 2019 5:21 pm

If you want to end at 1050, the duration is 50, not 1050.

It can be confusing, but the --stop-at duration is the number of seconds after you start.

AndyA
Posts: 12
Joined: Mon Apr 10, 2017 5:45 pm

Re: start-at stop-at parameters not working as expected

Post by AndyA » Wed Jan 30, 2019 5:51 pm

Ah ha! Yea the documentation is very misleading on that especially since the GUI works differently.

Thanks Woodstock!

Post Reply