Unexpecte/confusing output when `subclip()` tries to clip beyond end of file about moviepy HOT 3 OPEN

Idea to fix problems like this:

ffmpeg_reader should be very forgiving for out of bounds reads.

• for video, reads before the start get the first frame, reads after the end get the last frame
• for audio, out-of-bounds reads get 0-samples

The enforcement of duration should be in subclip(). subclip() could take a parameter elasticity with the following values:

• elasticity=='infinite':
  ignores whether it's in bounds of the original duration.
  result: new_clip.duration == end_time - start_time

• elasticity=='strict':
  assert original_clip.duration >= end_time - start_time, plus a small epsilon to take floating-point error into account.
  result: new_clip.duration == end_time - start_time

• elasticity=='truncate':
  truncate the ends so it fits in the old clip.
  result: new_clip.duration <= end_time - start_time

• elasticity=='truncatewarn':
  same as truncate, but does a warn() if it truncates more than an epsilon.

The default should be truncatewarn

from moviepy.

Something along these lines would work well for my purposes.

Just one minor issue: in the truncate case, the new_clip.duration == min(original_clip.duration, end_time - start_time) comparison doesn't seem correct. If my [start_time, end_time] range overlaps the end of the data, then I'd expect new_clip.duration to be original_clip.duration - start_time which may be shorter than either of the arguments to min().

from moviepy.

Something along these lines would work well for my purposes.

Just one minor issue: in the truncate case, the new_clip.duration == min(original_clip.duration, end_time - start_time) comparison doesn't seem correct. If my [start_time, end_time] range overlaps the end of the data, then I'd expect new_clip.duration to be original_clip.duration - start_time which may be shorter than either of the arguments to min().

Thanks, my formulation was wrong. corrected

from moviepy.