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

[Maskeeper]

For many years I’ve used the timecode selection function of pt by using the ‘/‘ key on the number pad.
Traditionally you could hit ‘/‘, type in a timecode. Hit ‘/‘ again type in the second timecode and hit enter and have a selection with those in/out points:

So previously I have been able to do:
"/"
01132212
"/"
01221213
"Enter"

And result in a selection from 01:13:22:12 to 01:22:12:13


However, currently when I try this: after typing in the first value and hitting the ‘/‘ to move on to the second value, the timecode I just typed as the START point is removed and the previous value is restored.

So if 01:22:01:07 is the current start point, I hit ‘/‘ and type in 01:00:00:00– I can see it in the start point counter but as soon as I hit ‘/‘ to go to the out point, the in point returns to 01:22:01:07.

The behavior has persisted through PT relaunch and System restart. I've tried Pref trashing. I discovered it while working in a 192 session so I tried a 48k session and the behavior was the same. I tried linking and unlinking the timeline/edit selection; no change.

I called a friend and confirm that this behavior was atypical (his worked fine, as I remembered it working) but he's running an earlier version. I confirmed with folks on a PT facebook group, work correctly, but again in different versions.

I'm just trying to figure out of 2020.5 is broken or I'm somehow in some terrible mode causing this.

[Maskeeper]

As a strange side note, if I open the transport and click directly on the Start timecode in the transport window instead (since the "/" doesn't work to take you into the transport window) and type it in the timecode, I can then hit "/" and move onto the End timecode in the transport window and it works CORRECTLY (it keeps the value I typed in as the start value instead of resetting).

So then I verified in the 'main' timecode window, if I CLICK to select the Start (instead of using the "/" key) it still DOESN'T work correctly, and when I hit "/" to move to the end timecode, it loses the value.

So this function is working ok in the floating transport window version (although I have to click to access it) but it DOES NOT work correctly in the main timecode window, whether I select the START field by clicking or by using the "/" quick key!

[SBP]

Hi-Yes this is a problem. PT Ultimate PT2020.05 MAC OS 10.14.06

I think what is happening is when second press of / the value we enter as 'start' and expect to be fixed as 'start position' is changing to whatever the value is at that moment in the main counter.

So a work around to try;
= 'your start time' enter [this will become the start selection time]
then / / 'your end time' enter

This is very annoying as it is more keystrokes.
Are you able to raise a support case?

Cheers

Bruno

[Maskeeper]

Originally Posted by SBP

So the only work around is to use;
= 'enter your start time' [this will become the start selection time]
then / / 'to enter your end time'

Yeah, although you have to hit ENTER after inputting the timecode into the main counter (just hitting "//" after inputting without ENTER did nothing for me).

Honestly if I hit "/" and then enter the TC, if i hit ENTER after that works too-- then I just have to hit "//" to get back into the end input. Same basic idea; was trying to avoid the extra strokes.

Anyway, good to confirm it is in fact broken, I'll see if I can file a ticket with Avid about it.

[Alden Manor]

I've submitted a bug report for this as well.
Didn't know if other people had the same issue.
First I'm hearing about it besides myself!

[Maskeeper]

Originally Posted by Alden Manor

I've submitted a bug report for this as well.

Is there another way to submit a bug report to Avid aside from opening a support case?

[AndrewAction]

Originally Posted by Maskeeper

Is there another way to submit a bug report to Avid aside from opening a support case?

Yes. I sent you a private message yesterday asking what OS you are on. I have those details from the other two posters showing both Mac and Windows see the problem.
With the info I had this morning I brought this thread to the attention of a relevant person higher up so they would look into it.

Andrew

[AndrewAction]

At present there are no cases in the Support system from this threads posters. Opening a support case ( avid.com/learn-and-support/contact-audio-and-music-support#Create-a-case ) is the best way to get things moving as it allows Avid to track the issue.

Andrew

[originalscottyg]

I can confirm this behavior.

MacBook Pro 2019 2.3GHz i9 32GB
macOS 10.14.6
PT Ultimate 2020.5
HD Native TB
Omni

[AndrewAction]

I was advised by my Pro Tools contact that with 3 (now 4) confirming the issue that Avid should look into the issue and that the best way to get that process underway was to open a support case.
Have any of you opened a support case??

Andrew