vangel76andClaude Sonnet 5.5 51501bbd21 #890: the Timeline time field reads its displayed timecode back as the same frame at 29.97/59.94 fps ...

Problem: the Timeline shows non-drop timecode, but time.set (the current-time field) parsed
typed text as drop-frame at 29.97/59.94 fps, so committing the displayed time, or typing a
time, landed on another frame from minute 1 on (frame 1800 "0:01:00:00" -> 1798).

Fix: typed text is read as drop-frame only when it uses ';' fields; ':' and '.' follow the
displayed non-drop style. Regression test round-trips the display at both rates.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

2026-10-11 19:00:25 +02:00

..

presets

M9.6: text animation depth (selectors, animator properties, per-char 3D, path text, presets)

2026-10-02 00:01:19 -04:00

scripts

M13.1: ScriptUI frontend (dialogs, palettes, dockable panels), script menus, example plug-in, docs

2026-10-03 04:24:01 -04:00

src

#890: the Timeline time field reads its displayed timecode back as the same frame at 29.97/59.94 fps

2026-10-11 19:00:25 +02:00

tests

Merge pull request #471 from sanyamsingh001/fix/parenting-3d-position

2026-10-10 12:49:17 +00:00

Cargo.toml

M13.35: Roto Brush trained model — swappable segment module, MobileSAM in pure Rust

2026-10-05 17:55:02 +07:00