If a timecode offset (in seconds or frames) is specified, an additional parameter should provide the ability to NOT apply this offset to the TCP field value as it may contain a wrong value (e.g. zero), leading to an aborted conversion (due to a resulting negative timecode).
spoeschel
commented
4 years ago
If a timecode offset (in seconds or frames) is specified, an additional parameter should provide the ability to NOT apply this offset to the
TCPfield value as it may contain a wrong value (e.g. zero), leading to an aborted conversion (due to a resulting negative timecode).