Dear Blackmagic team and community,
I would like to report a critical usability issue that affects many users working with non-US keyboard layouts, specifically the German layout, in the Fusion page of DaVinci Resolve.
The default shortcuts for frame-by-frame navigation in Fusion are [ (Previous Frame) and ] (Next Frame). These shortcuts work flawlessly on a US/English keyboard, even when the Viewer is focused.
However, on a German keyboard layout, the characters [ and ] are only accessible via Alt Gr + 8/9. DaVinci Resolve does not recognize these combinations as valid shortcuts, and even when reassigning the frame-step function to more accessible keys (e.g., , and .), the shortcuts do not trigger consistently in the Fusion page — especially when the Viewer, Timeline, or Spline Editor is in focus.
As a result:
• Frame stepping is not usable via keyboard on a German layout without switching the entire system layout to US-English.
• This is highly disruptive to compositing work and animation tasks that require precise frame control.
• The issue affects only Fusion — the Edit and Cut pages handle shortcuts more reliably.
Please consider addressing this issue in a future update by:
1. Allowing keyboard shortcuts to be recognized based on character output, not physical keycode, so that layouts like German, French, etc., are fully supported.
2. Ensuring that custom shortcuts (e.g., ,, ., or arrow keys) reliably trigger frame stepping in Fusion, regardless of UI focus (Viewer, Timeline, Spline, etc.).
3. Providing alternative default shortcuts for frame stepping in Fusion that are compatible with international keyboard layouts.
Why this matters:
Precise frame stepping is essential in Fusion for tasks like keyframing, motion tracking, rotoscoping, and effects timing. Not being able to navigate frame by frame via keyboard significantly slows down the workflow and makes the software feel incomplete or broken in localized environments — despite being officially distributed in these markets.
I sincerely hope this issue will be acknowledged and addressed. Many professional users across Europe and beyond would greatly appreciate a fix.
Thank you for your excellent work and ongoing support.
Best regards,
Lennart Selle
I would like to report a critical usability issue that affects many users working with non-US keyboard layouts, specifically the German layout, in the Fusion page of DaVinci Resolve.
The default shortcuts for frame-by-frame navigation in Fusion are [ (Previous Frame) and ] (Next Frame). These shortcuts work flawlessly on a US/English keyboard, even when the Viewer is focused.
However, on a German keyboard layout, the characters [ and ] are only accessible via Alt Gr + 8/9. DaVinci Resolve does not recognize these combinations as valid shortcuts, and even when reassigning the frame-step function to more accessible keys (e.g., , and .), the shortcuts do not trigger consistently in the Fusion page — especially when the Viewer, Timeline, or Spline Editor is in focus.
As a result:
• Frame stepping is not usable via keyboard on a German layout without switching the entire system layout to US-English.
• This is highly disruptive to compositing work and animation tasks that require precise frame control.
• The issue affects only Fusion — the Edit and Cut pages handle shortcuts more reliably.
Please consider addressing this issue in a future update by:
1. Allowing keyboard shortcuts to be recognized based on character output, not physical keycode, so that layouts like German, French, etc., are fully supported.
2. Ensuring that custom shortcuts (e.g., ,, ., or arrow keys) reliably trigger frame stepping in Fusion, regardless of UI focus (Viewer, Timeline, Spline, etc.).
3. Providing alternative default shortcuts for frame stepping in Fusion that are compatible with international keyboard layouts.
Why this matters:
Precise frame stepping is essential in Fusion for tasks like keyframing, motion tracking, rotoscoping, and effects timing. Not being able to navigate frame by frame via keyboard significantly slows down the workflow and makes the software feel incomplete or broken in localized environments — despite being officially distributed in these markets.
I sincerely hope this issue will be acknowledged and addressed. Many professional users across Europe and beyond would greatly appreciate a fix.
Thank you for your excellent work and ongoing support.
Best regards,
Lennart Selle