[Bug] Macro delays not working with K6 Pro ISO

[farconada]

Describe the Bug

Macro delays dont work with the K6 Pro ISO version

Keyboard Used

Keychron K6 Pro ISO ES

Link to product page (if applicable)

No response

Operating System

Linux

qmk doctor Output

No response

Is AutoHotKey / Karabiner installed

• [ ] AutoHotKey (Windows)
• [ ] Karabiner (macOS)

Other keyboard-related software installed

No response

Additional Context

No response

[farconada]

please, help

[PeterMortensen]

Re "not working": Can you be more specific?

In what way are macro delays not working? For example,

• How exactly was the macro created?
• Are macro delays not accepted by the Via clone? Is there the same problem in Via?
• Are the macro delays not recorded during macro recording?
• Do the macro delays appear to be entered, but don't have any effect when the macro is executed?
• What is the macro source for the macro? Example (delays 17 ms and 400 ms):
  • {+KC_F24}{17}{-KC_F24}{400}c
    • What are the exact steps to reproduce the problem?

For example, Via has a setting, "SKIP RECORDING DELAYS", which will leave out delays in the recorded macro (it is probably for backwards compatibility with older versions of firmware).

Can you isolate the problem to either the Via clone or the keyboard? For example, trying it in Via (with "SKIP RECORDING DELAYS" disabled (it is somewhat confusing as the popup text is for what happens if clicked, not the current state)). Via requires a JSON file to be downloaded and imported (tab "DESIGN" (third tab on the top)). If it appears to be hanging, ignore that and load the JSON file anyway. Repowering the keyboard while Via is open is the best bet if it, for some reason, does not work as expected (here are more troubleshooting steps).

[farconada]

With keychron launcher, but when I reconnect the delay has dissapeared. I have pushed "submit"

[PeterMortensen]

Re "...when I reconnect the delay has disappeared. I have pushed "submit"": It is mostly likely a problem with the Via clone. It could be confirmed by doing the same with Via (that would exclude the keyboard as the cause).

Note that "SKIP RECORDING DELAYS" in Via should be off.

Or maybe there is a similar setting in the Via clone?