Typing in timecode

Is there a setting to enable timecode typing behavior to behave like it did in the previous versions?

In V17 you have to click on the timecode display above the source viewer or the timeline viewer before you can start typing up the timecode. One exception is if you press "+" or "-" first then you can type in the timecode offset.

In the previous versions typing was context aware of the active panel selection. For example, all you had to do was click anywhere in the timeline viewer to make it active and you could type in a timecode. This old way is faster. You don't have to precisely aim for the small timecode display. I have to type timecodes many times a day.

I noticed this as well. Thanks for posting.

+1

That’s crucial
+1


Sent from my iPhone using Tapatalk

You can make a keyboard shortcut for timecode entry, no need to click anywhere.

Having to press it is of course another matter which I didn't have to deal with when the timeline was in focus in 16.

+1 here.
Super annoying, and cuts into speed of use considerably.
Was willing to put up with the lack of display in v16 but not to have it at all in v17 without shenanigans is a bit much.

You can make a keyboard shortcut for timecode entry, no need to click anywhere.

Tom, where's the command for timecode entry to be found? I can make the shortcut but can't locate the command itself.

Thanks!
Chris

You can make a keyboard shortcut for timecode entry, no need to click anywhere.

Tom, where's the command for timecode entry to be found? I can make the shortcut but can't locate the command itself.

Thanks!
Chris

Playback/Go To/Timecode

Perfect
Thanks!

Yeah, this is annoying.

Extending or shrinking clips numerically does not seem to be working either.

Wait trying to wrap my head around this one. Are people thinking this is a new feature? Or is this a bug?

+1000 with the thread this is a real problem.

The other bummer about this, and it is something I commented on in 16 is that it also shifts focus from the timeline to the record window every time you type in TC. So if you copy something and then go to a new timecode you then need to click back in the timecode windows to paste it.

Now, on the subject of active panel (focus), what kills me is that you have to click on the timeline panel to activate it before you can paste a clip to the timeline.

For example, you copy a clip from one timeline, then you open another timeline by clicking on it in the bin. At that point the bin is the active panel. CTRL+V paste can't paste until you make the current timeline panel active by clicking or by CTRL+4. This change happened in V15 or V14.

The way this worked in V12 was consistent with any other NLE. The paste was context aware. if you're pasting a timeline clip it was pasted on the timeline.

Now, on the subject of active panel (focus), what kills me is that you have to click on the timeline panel to activate it before you can paste a clip to the timeline.

For example, you copy a clip from one timeline, then you open another timeline by clicking on it in the bin. At that point the bin is the active panel. CTRL+V paste can't paste until you make the current timeline panel active by clicking or by CTRL+4. This change happened in V15 or V14.

The way this worked in V12 was consistent with any other NLE. The paste was context aware. if you're pasting a timeline clip it was pasted on the timeline.

+1

I won't respond further as I don't want to distract from the original thread but know that on this you are not alone!

I agree. Please change timecode entry back to work as V16. All other editing apps work this way.

Perhaps we are deprecating the Edit page for the Cut page and necessity use of the Speed Editor?




Otherwise, I just can't fathom an NLE removing a 30+year standard workflow.

+1 for this, it's ruining my life

IIn V17 you have to click on the timecode display above the source viewer or the timeline viewer before you can start typing up the timecode.

This is incorrect. You type a '=' first. No clicking involved.

I agree. Please change timecode entry back to work as V16. All other editing apps work this way.

As noted, the OP misrepresented what you have to do. You do not have to click, you can entirely type. As far as I know, you cannot just type numbers (without typing a shortcut first) into FCP X to jump to a timecode, so I don't think all other editors work that way. I could be wrong on that.

As far as I know, you cannot just type numbers (without typing a shortcut first) into FCP X to jump to a timecode, so I don't think all other editors work that way. I could be wrong on that.

FCP X is a very non-standard NLE. It's better to ignore it.

FCP X is a very non-standard NLE. It's better to ignore it.

EXACTLY.
BMD is racing to the bottom to FCPX/CutPage, 13 inch Macbooks and Mac minis.
Yet pro features are needed to make it a true editorial NLE.

v17 for Editorial has been a disappointment. So many bugs, so many inconsistencies, lack of progression and now 17 is WORSE than v16.

Yeah completely agree.
I should be able like before click on the source or program window and start typing numbers.
TC numbers are super small , this is a bad feature.

Still the same thing in Beta 9.
You have to directly click on timecode and type in.

Please , please lets go back to the way it was before when you could click on window and type TC #'s.

Still the same thing in Beta 9.
You have to directly click on timecode and type in.

No, you don't. You can invoke timecode entry by using keyboard shortcuts, default for Go To being =

Clicking on windows first is very inefficient, you should just use the keyboard shortcut for toggling between source and timeline viewers, default being Q.

Whether a click or a shortcut I think is incidental.

The new behavior is that an action is required before typing in the timecode.

That's new and unwelcome behavior.

Still the same thing in Beta 9.
You have to directly click on timecode and type in.

No, you don't. You can invoke timecode entry by using keyboard shortcuts, default for Go To being =

Clicking on windows first is very inefficient, you should just use the keyboard shortcut for toggling between source and timeline viewers, default being Q.

Thnx! That works but do I like it ......... I don't know about that.
Learn and adapt , I just hope this stay and they don't change it again.

+1

Having to use an action before typing in timecode is beyond annoying. I really hope they add back the option to enter TC like any other NLE without first typing "=" or clicking the box.

I just hope this stay and they don't change it again.

Really!? I think most of us are hoping it goes back to normal.

I just hope this stay and they don't change it again.

Really!? I think most of us are hoping it goes back to normal.

Hell, If BMD just adds the option to switch back (have an option for both) then I'll be happy. Not gonna pressure people to do it one way or the other...

While you wait to see if BMD changes timecode entry behavior back, Google "SharpKeys". This Windows program allows you to remap the NumLock key on the number pad to be the "equal" sign instead. It writes the change to the registry so you only have to do this once. This should make TC entry "a little" easier. There are probably ways to do this for Mac and Linux also.

Just make sure you have your bios set to turn numlock on at boot so the keyboard defaults to using the number keys instead of the navigation keys.

I went for a simpler option, Gary.

I remapped the new shortcut to Numpad's asterisk key. So it's closer to hand.

(Still don't like it, though. )

And I remapped it to the numpad 0 key. Found this to be faster for me. And with all the damn extra 0's we have to type in now to get timecode to even be usable, it's just an extra 0 to start with. Ugh I hope they fix all this.

I have been trying to rack my brain around this one for a while. I really hate this functionality but trying to wrap my head around why the powers at be may have implemented it. Anyone have any good ideas as to why they might have made this change? Is anyone seeing upside from it? The only thing I can think of is maybe it allows better integration with some of the panels like the new fairlight panel (I am pretty sure on that panel you hit a button before entering in TC).

I have been trying to rack my brain around this one for a while. I really hate this functionality but trying to wrap my head around why the powers at be may have implemented it. Anyone have any good ideas as to why they might have made this change? Is anyone seeing upside from it? The only thing I can think of is maybe it allows better integration with some of the panels like the new fairlight panel (I am pretty sure on that panel you hit a button before entering in TC).

It frees up prime real estate on an extended keyboard. The numeric keypad is used for geometrically-oriented shortcuts in things like the Color Page, and in many applications like Blender.

It makes timecode consistent: +, -, = to do relative plus, relative minus, or absolute.

Under the hood it may fit in better with their framework for managing keyboard shortcuts and keyboard focus.

That doesn't mean it's the best for some use cases. But the idea that they did it just because with no forethought doesn't make any sense to me.

(Jim, on a side note and just in case you don't use Macs at all, it turns out that Apple's extended keyboard places = directly above the 8 in the numeric keypad, which is pretty optimal location. I assume you're using a Dell extended keyboard or something like that where there is no = key on the keypad, so * is the closest you can get. That's also pretty convenient on the Apple extended keyboard -- being above the -, +, and Enter -- but not quite as central as the =.)

My wireless Logitech has no equal sign near the numpad. It does have dedicated navigation keys so no need for the numlock key. The numlock key is above the 7, so just a stretch of the index finger to hit the new = key.

(Jim I assume you're using a Dell extended keyboard )

Standard 104 (by far the most common keyboard on the planet) which doesn't include = on the Numpad.

I have been trying to rack my brain around this one for a while. I really hate this functionality but trying to wrap my head around why the powers at be may have implemented it. Anyone have any good ideas as to why they might have made this change? Is anyone seeing upside from it? The only thing I can think of is maybe it allows better integration with some of the panels like the new fairlight panel (I am pretty sure on that panel you hit a button before entering in TC).

It frees up prime real estate on an extended keyboard. The numeric keypad is used for geometrically-oriented shortcuts in things like the Color Page, and in many applications like Blender.

It makes timecode consistent: +, -, = to do relative plus, relative minus, or absolute.

Under the hood it may fit in better with their framework for managing keyboard shortcuts and keyboard focus.

That doesn't mean it's the best for some use cases. But the idea that they did it just because with no forethought doesn't make any sense to me.

(Jim, on a side note and just in case you don't use Macs at all, it turns out that Apple's extended keyboard places = directly above the 8 in the numeric keypad, which is pretty optimal location. I assume you're using a Dell extended keyboard or something like that where there is no = key on the keypad, so * is the closest you can get. That's also pretty convenient on the Apple extended keyboard -- being above the -, +, and Enter -- but not quite as central as the =.)

I totally agree I think there probably was some forethought I am just trying to figure out what that might be. I could see freeing up the keys for shortcuts as a possible explaination, but freeing up those keys doesn't seem like a compelling enough explanation to remove such a core functionality. Especially when those keys have had dual purposes in other versions (printer lights).



Sent from my Pixel 4 using Tapatalk

... doesn't seem like a compelling enough explanation to remove such a core functionality.

No functionality was removed. A procedure was slightly changed, arguably bringing it into consistency with the two relative changes (+ and -). You don't have to have a video editor explanation for why. My guess would be it has to do with cleaning up complex code where they've got to handle things like the timecode specially and in several places instead of taking advantage of their unified code for handling shortcuts. You can even see how it works now: hitting + jumps to and enables the timecode input.

Personally, I don't think I've ever typed in an absolute timecode, and am not sure the use case where you would do it more than a couple of times. (I imagine sitting in front of a client who has made handwritten notes and is calling out approximate timecode to you.) If it were a punch list of changes, I'd have a spreadsheet and use Paste Timecode in Resolve to guarantee I jump to the correct place, rather than typing it by hand. But I don't have the client-behind-me pressure and workflow.

They may yet bow to the vociferous criticism from some users. It is still beta.

I'm a little passionate about this because of some of the hyper-critical members of these forums who love to rant about how stupid BMD is and how ridiculously primitive Resolve is -- yet somehow they're so invested in it that they won't switch to any one of the many "superior" alternatives. You can argue that the timecode keying change costs you time and causes errors -- preferably with an explanation of your workflow so others of us can understand -- but speculation on the "why" will feed the trolls.

(And again, I'm not saying that the change is for the best. It works for me, but if it's a showstopper for enough users, BMD will have to deal with that. On my own part -- and being a bit inconsistent here -- I have suggested some changes about focus changing that when I put on my software developer hat make me cringe with what it will do to the code base. But the current behavior for several workflows is more complex/confusing/error-prone so I suggest. But that's just me.)

Personally, I don't think I've ever typed in an absolute timecode, and am not sure the use case where you would do it more than a couple of times.

I can totally understand that this is something that might not affect you, I don't know what kind of work you do, I can tell you that working in Broadcast television typing in absolute timecode is something we use all of the time. DaVinci is in a weird spot as they have to tailor the program to the needs of many individuals and workflows. I could see how someone working on more short form projects might not have need of this, but imagine if you had to hit a key or click a button before hitting the play button. Wouldn't you want to know why they made that change? Is there a bigger reason why this is happening that outweighs the inconvenience? Some of the other less popular changes had a more obvious why (ex removing the duplicate timeline from the contextual menu so that it could be assigned a keyboard shortcut).

This forum is one of the only places for people to give feedback to the development team and if something seems like it might be a move in the wrong direction I think it is important to voice that opinion. One can be critical and still supportive.

...

Personally, I don't think I've ever typed in an absolute timecode, and am not sure the use case where you would do it more than a couple of times. (I imagine sitting in front of a client who has made handwritten notes and is calling out approximate timecode to you.) If it were a punch list of changes, I'd have a spreadsheet and use Paste Timecode in Resolve to guarantee I jump to the correct place, rather than typing it by hand. But I don't have the client-behind-me pressure and workflow...

Navigating to absolute and relative timecodes is a frequent requirement whether the client is in the room or remote, and I've yet to meet an editor or colorist who would prefer copying and pasting between a spreadsheet and (any app) over entering timecodes on the numpad, which can be done very rapidly when you are used to it.

The being used to it part means that throwing an extra keystroke in is messing with years of muscle memory and adding keystrokes and hand/wrist movements to an already RSI-prone occupation. Additionally, as a colorist, it has broken my workflow for copying previous clip grade and 2nd to previous clip grade, as the = key no longer works as it used to and now requires a shift modifier, meaning more keystrokes and hand/wrist movements. A double whammy.

If this doesn't affect you, I understand, but it is a harsh imposition on many of us, and BMD has made no response as to why they think this is worth doing. I think we have a right to ask, although what I'd most like is for them to realize it just isn't a good idea and it is not going down well.

If BMD comes forward with a compelling reason, I'm happy to consider it.

I remapped the new shortcut to Numpad's asterisk key. So it's closer to hand.

And I remapped it to the numpad 0 key.

My wireless Logitech has no equal sign near the numpad. It does have dedicated navigation keys so no need for the numlock key. The numlock key is above the 7, so just a stretch of the index finger to hit the new = key.

Additionally, as a colorist, it has broken my workflow for copying previous clip grade and 2nd to previous clip grade, as the = key no longer works as it used to and now requires a shift modifier, meaning more keystrokes and hand/wrist movements. A double whammy.

Do you guys not have an Enter key on your Number pad then? That's what I have my Go To Timecode mapped to, which of course means I can still use - and = for copying grades from prior clips. Would be odd if you didn't, since both my Mac and Windows keyboards have this.

+1 (more like +100) on this. PLEASE fix this ASAP so it will work using the window focus to enter absolute or relative (+/-), complete or partial timecode as in DR16 and many (all?) previous versions! Including entering this to move/trim the marked edit on the edit page.

In Resolve Studio 17.4.3 this is no longer an issue.
Using an =, + or - key followed by a complete or partial timecode moves the playhead correctly.
Selecting a clip and using a + or - key followed by a complete or partial timecode moves the clip correctly.

My logitech wireless keyboard does not have an "=" key on or near the number pad. (who thought that was a good idea?)

My logitech wireless keyboard does not have an "=" key on or near the number pad. (who thought that was a good idea?)

I'm pretty sure it has an Enter key on the Numberpad though. Starting to wonder why no one on this or the other thread (viewtopic.php?f=21&t=129488&start=50) has answered me on this incredibly simple point.

I think it was changed so the Speed Editor could use it’s numpad for multicam takes.

ok, i've read this thread, but...

i'm still working with 16, and would like to try 17, but i have three tc (paper edl) based projects. very simple compiles, enter in, enter out, append, etc

i work exclusively in the edit page (not quite ready for the new fangled cut page)...

so, in 17- does simply selecting source window and typing in tc no longer work?
from the above thread it appears i have to tap '=' first, then enter tc?

if so, how can i map = to * on numeric keypad? (i'm asking since i've just checked in 16 keyboard mapping and can't see how to do it).

sorry if i'm appearing dense, but age is taking its toll...

tia

if so, how can i map = to * on numeric keypad?

Did you see my posts, or are they somehow invisible to people? Why would you map to * instead of Enter?

Don’t you need the “enter” key to enter the timecode?

Leslie, to map keys to different key codes you need to do it outside of Resolve. There are many programs to be found on the internet that can do it. SharpKeys is the one I used.