
The validator of the timecode input box seems to be set wrong. When just tapping the timecode value for it to open, it prefills it with the proper syntax, like “00:00:00:00”. When I now change a value like this for example “00:00:00:10”, that will not work and still save all zeros. Instead the field seems to have been set to use a simple number validator, so typing in an Integer or a Float makes it accept the input.

hmm, I can reproduce that here; however entering times using the provided buttons for the format works (eg. 1h2m5f) - we’ll address this in the Prolight & Sound update (2.1.x)

This issue has slipped through and the underlaying fix is bigger then just a validator setting. I see this is an annoying issue and we’ll certainly fix it at some point.

