Timecode bug in v2020.5? Can you help me confirm?

[Maskeeper]

I did post a support case almost immediately after posting this discussion (previous instructions asked to confirm bug with other users on DUC before submitting). The case was logged 8/16 so not sure why they would say there isn't one in the system on 8/18!!

The response was it's been forwarded to engineering.

"This issue has been already logged as a bug (PT-263319) and is under investigation by our engineering and development team. We are now just waiting for a fix from them. For now, all we can do is wait for the fix. With that said, we'll close this case as a known bug. If you. Thanks and have a great day!"



Thanks.

[AndrewAction]

Originally Posted by Maskeeper

I did post a support case almost immediately after posting this discussion (previous instructions asked to confirm bug with other users on DUC before submitting). The case was logged 8/16 so not sure why they would say there isn't one in the system on 8/18!!

Sorry for the mistake! They had searched for a new case using DUC email addresses, your case was logged under a different email address.

For others users with this issue starting a support case referencing PT 263319 would be helpful.

Andrew

[Maskeeper]

And they fixed that timecode input bug in today's update
"The '/' key no longer cancels the previous value entry when moving between start/end/length fields in the transport cluster"