Add new comment

good catch.

the Clip/Take/Range... dialog indeed needs some input range sanitizing whenever not dealing the current clip selection (ie. "Selection" radio button option). meaning that all other options ("Loop", "Punch" or "Edit") *must* get their values constrained to the target clip extents, no matter what (and reflect that on the actual/effective range, as it should on "Custom"...

internally, the actual take range must be also capped. probably it doesn't, leading to some potential huge values (formerly unsigned converted from negative) making it all overwhelming lost, somehow :S

nice catch again.
holy thanks