Editing Openai/6957d2e8-b738-8008-987a-09a5d9f29bc8 (section)

=== Assistant: Yep — the approach I gave still works fine with milliseconds. ===
Yep — the approach I gave still works fine with milliseconds. You just put decimals on the cut points.

===== You can do it either as seconds with decimals: =====
* start=62.137:end=133.904

or as HH:MM:SS.mmm (ffmpeg accepts this format too, but inside trim it’s simplest to use seconds).

===== Say you decide clip 2 should be 03:17.237 → 05:26.041. =====

03:17.237 = 197.237 seconds
05:26.041 = 326.041 seconds

<syntaxhighlight lang="bash">ffmpeg -i "NEA MADALIN E DRAG QUEEN ACUM [P9gZEDOz9eE].mkv" -filter_complex \
"[0:v]trim=start=197.237:end=326.041,setpts=PTS-STARTPTS[v]; \
 [0:a]atrim=start=197.237:end=326.041,asetpts=PTS-STARTPTS[a]" \
-map "[v]" -map "[a]" \
-c:v libx264 -preset veryslow -qp 0 -pix_fmt yuv420p -profile:v high -level 4.0 \
-color_range tv -colorspace bt709 -color_trc bt709 -color_primaries bt709 \
-c:a libopus -b:a 160k -ar 48000 -ac 2 \
clip_02_0317p237-0526p041.mkv

</syntaxhighlight>

===== Your video is 30 fps, so frames are spaced about 33.333 ms apart. =====
That means:
* You can type millisecond timestamps,
* but the actual video cut can only land on a frame boundary (≈33ms steps).
* Audio can be trimmed much more finely (sample-level).

If you want, paste the exact ms cut points you end up with (like 01:02.153–02:13.087) and I’ll rewrite all 4 commands with those exact values.