NumLock bug Beta 2

DaVinci Resolve 19 Public Beta Discussion
  • Author
  • Message
Offline

Cesar Tejada

  • Posts: 155
  • Joined: Wed Mar 04, 2020 1:13 pm
  • Real Name: Cesar Augusto Tejada

NumLock bug Beta 2

PostThu May 09, 2024 12:17 am

My native language is Spanish so I tend to use special characters like:  ¿ á é í ó ú ¡


If my keyboard has NumLock enabled and I press ALT + any number in the Numpad,  Resolve focus the typing field to the timeline timecode.

That behavior wasn't happening to me before.

If I try to type for example ALT+0191 I can't because the typing jumps straight to the timecode.

I have Resolve 18 in another machine and no issues.

My keyboard shortcuts are exactly the same on each machine.

Even in the deliver page if I try to name my file with special characters the typing field jumps to the timecode.


Hope this bug is fixed in the next update.

Sent from my Mi A3 using Tapatalk
Microsoft Windows 10 Pro

Processor: Intel i7-13700K 16 Cores
GPU: NVIDIA GeForce RTX 4070
Memory: Corsair DDR5 64GB
MB: ASUS TUF GAMING Z790-PLUS WIFI
Offline

Jim Simon

  • Posts: 31214
  • Joined: Fri Dec 23, 2016 1:47 am

Re: NumLock bug Beta 2

PostThu May 09, 2024 4:06 pm

I'm seeing the same in Studio 19b2 for Windows.

Can't enter any Alt+ characters in either Text or Text+.

I use Alt+0176 (degree's symbol) for testing.
My Biases:

You NEED training.
You NEED a desktop.
You NEED a calibrated (non-computer) display.
Offline

Andy Mees

  • Posts: 3341
  • Joined: Wed Aug 22, 2012 7:48 am

Re: NumLock bug Beta 2

PostThu May 09, 2024 4:47 pm

In v19 I believe they addressed a long standing flaw and frequent complaint in Resolve being that it required a special keypress before one could navigate by timecode using teh numpad keys (a standard capability on most every other NLE). It might be that the issue you are now seeing in v19 is a by-product of that fix.
Offline

Jim Simon

  • Posts: 31214
  • Joined: Fri Dec 23, 2016 1:47 am

Re: NumLock bug Beta 2

PostThu May 09, 2024 4:59 pm

It might be, but it shouldn't be.

When a text box is active, all entries should be considered as text entries. (It worked this way before BMD muffed timecode entry a while back.)
My Biases:

You NEED training.
You NEED a desktop.
You NEED a calibrated (non-computer) display.
Offline

Cesar Tejada

  • Posts: 155
  • Joined: Wed Mar 04, 2020 1:13 pm
  • Real Name: Cesar Augusto Tejada

Re: NumLock bug Beta 2

PostThu May 09, 2024 5:11 pm

Jim Simon wrote:It might be, but it shouldn't be.

When a text box is active, all entries should be considered as text entries. (It worked this way before BMD muffed timecode entry a while back.)
Exactly, that's how's supposed to be working. If a text field it's active all values should go there.

Sent from my Mi A3 using Tapatalk
Microsoft Windows 10 Pro

Processor: Intel i7-13700K 16 Cores
GPU: NVIDIA GeForce RTX 4070
Memory: Corsair DDR5 64GB
MB: ASUS TUF GAMING Z790-PLUS WIFI
Online
User avatar

Joe Shapiro

  • Posts: 2892
  • Joined: Thu Jul 25, 2013 7:23 am
  • Location: Los Angeles CA USA

Re: NumLock bug Beta 2

PostFri May 10, 2024 8:30 am

You’d think that’s how it’d work. That all characters would go to the text field.
But it doesn’t and hasn’t as long as I’ve used Resolve.

Try typing Shift + Left Arrow. Should be sent to the text field where it would select the previous character. But instead it moves the playhead backwards by multiple frames.

This Alt scenario is worse than before but the basic issue has been there - by design I suspect - for many years.
Director, Editor, Problem Solver. Been cutting indie features for 23 years. FCP editor from version 2 to 7.
Resolve 19b2
MacBook Pro 16" M1 Max 64GB RAM, macOS 14.4.1
MacBook Air 13" M1 8GB RAM, macOS 14.2.1
Offline

Cesar Tejada

  • Posts: 155
  • Joined: Wed Mar 04, 2020 1:13 pm
  • Real Name: Cesar Augusto Tejada

Re: NumLock bug Beta 2

PostSat Jun 08, 2024 8:47 pm

Joe Shapiro wrote:You’d think that’s how it’d work. That all characters would go to the text field.
But it doesn’t and hasn’t as long as I’ve used Resolve.

Try typing Shift + Left Arrow. Should be sent to the text field where it would select the previous character. But instead it moves the playhead backwards by multiple frames.

This Alt scenario is worse than before but the basic issue has been there - by design I suspect - for many years.


I updated to 19 b3, and the problem I mentioned before was fixed.

I typed Shift + Left Arrow and it stayed on the Text Field and selected the previous character. Nothing triggered the focus on the timeline.

Btw I'm on PC and have NumLock enabled.
Microsoft Windows 10 Pro

Processor: Intel i7-13700K 16 Cores
GPU: NVIDIA GeForce RTX 4070
Memory: Corsair DDR5 64GB
MB: ASUS TUF GAMING Z790-PLUS WIFI
Online
User avatar

Joe Shapiro

  • Posts: 2892
  • Joined: Thu Jul 25, 2013 7:23 am
  • Location: Los Angeles CA USA

Re: NumLock bug Beta 2

PostSun Jun 09, 2024 2:43 am

They fixed it? Awesome! Thanks for the update!
Director, Editor, Problem Solver. Been cutting indie features for 23 years. FCP editor from version 2 to 7.
Resolve 19b2
MacBook Pro 16" M1 Max 64GB RAM, macOS 14.4.1
MacBook Air 13" M1 8GB RAM, macOS 14.2.1
Offline

Jim Simon

  • Posts: 31214
  • Joined: Fri Dec 23, 2016 1:47 am

Re: NumLock bug Beta 2

PostSun Jun 09, 2024 7:22 pm

I'm still seeing the playhead move when I type Alt+0176 into a Text title. No degree symbol in sight. :(
For a Text+ title, nothing happens. It's like Resolve isn't getting the keyboard entries at all.

Studio 19b3 for Windows.
My Biases:

You NEED training.
You NEED a desktop.
You NEED a calibrated (non-computer) display.
Offline

Cesar Tejada

  • Posts: 155
  • Joined: Wed Mar 04, 2020 1:13 pm
  • Real Name: Cesar Augusto Tejada

Re: NumLock bug Beta 2

PostSun Jun 09, 2024 7:35 pm

Jim Simon wrote:I'm still seeing the playhead move when I type Alt+0176 into a Text title. No degree symbol in sight. :(
For a Text+ title, nothing happens. It's like Resolve isn't getting the keyboard entries at all.

Studio 19b3 for Windows.

Hi Jim! That's weird, I managed to type it without any problems on beta 3 on Windows.
Screenshot 2024-06-09 153200.png
Screenshot 2024-06-09 153200.png (72.2 KiB) Viewed 97 times

Did you ensure you have NumLock Enabled on your keyboard?
Microsoft Windows 10 Pro

Processor: Intel i7-13700K 16 Cores
GPU: NVIDIA GeForce RTX 4070
Memory: Corsair DDR5 64GB
MB: ASUS TUF GAMING Z790-PLUS WIFI
Offline

Jim Simon

  • Posts: 31214
  • Joined: Fri Dec 23, 2016 1:47 am

Re: NumLock bug Beta 2

PostSun Jun 09, 2024 8:14 pm

Cesar Tejada wrote:Did you ensure you have NumLock Enabled on your keyboard?
I did. As soon as I hit the 0, the Text Box loses highlight and the Timeline box gets it.

So I tried turning NumLock off...and it worked.

Weird!
My Biases:

You NEED training.
You NEED a desktop.
You NEED a calibrated (non-computer) display.
Offline

Cesar Tejada

  • Posts: 155
  • Joined: Wed Mar 04, 2020 1:13 pm
  • Real Name: Cesar Augusto Tejada

Re: NumLock bug Beta 2

PostMon Jun 10, 2024 12:02 am

Jim Simon wrote:
Cesar Tejada wrote:Did you ensure you have NumLock Enabled on your keyboard?
I did. As soon as I hit the 0, the Text Box loses highlight and the Timeline box gets it.

So I tried turning NumLock off...and it worked.

Weird!


Absolutely weird! :lol:
Microsoft Windows 10 Pro

Processor: Intel i7-13700K 16 Cores
GPU: NVIDIA GeForce RTX 4070
Memory: Corsair DDR5 64GB
MB: ASUS TUF GAMING Z790-PLUS WIFI

Return to DaVinci Resolve 19 Public Beta

Who is online

Users browsing this forum: No registered users and 6 guests