wrong key bindings for hotcues

Is there something reported in your mixxx.log file found at /Users/<username>/Library/Application Support/Mixxx/?

"... not found, using en_US.kbd.cfg"

But the Y key print y in the search box?

Hi Daniel, this fell off my radar. Just checked. Lanuage is set to german (germany). When typing the "y" key in the search box prints y and "z" key z and still z sets the first cue point while y does nothing.

I opened mixxx.log. a search for "error" brings up
Debug [Main]: "Error: Unable to import console: no such extension"
Debug [Main]: "Error: Unable to import svg: no such extension"
Debug [Main]: "Error: Unable to import console: no such extension"
Debug [Main]: "Error: Unable to import svg: no such extension"
Warning [Main]: src/skin/legacyskinparser.cpp:1963 SKIN ERROR at skin:knob_textless.xml:21 <KnobComposed>: Invalid <TooltipId> in skin.xml: "booth_gain"
Warning [Main]: src/skin/legacyskinparser.cpp:1963 SKIN ERROR at skin:knob_textless.xml:21 <KnobComposed>: Invalid <TooltipId> in skin.xml: "booth_gain"

unsure if related to this problem.

Confirmed, looks like there is always the default en_US keyboard layout active, no matter the current locale.

There is no entry in the log about parsing a *.kbd.cfg at all.
maOS 10.11.6 "Mixxx" "2.1.0-alpha-pre" "(git master r6390; built on: Nov 25 2017)

I cannot confirm this on a German Ubuntu Trusty using the latest 2.1 alpha
No entry means it actually reads the res/keyboard/de_DE.kbd.cfg
Does Ö work for ch2 cue?

Thanks Jus for confirming and Daniel for taking a look at this bug.

Downloaded latest macOS master build from dec 5th. pressing "ö" doesn't do anything for me. sometimes the tracklists jumps to a different position when pressing ö.

While testing I am noticing that the hotcue keys for Deck 2 are broken as well. M and Shift + M for cue 1 work as expected. But cue 2, 3, 4 are not working.

Could it be this bug is limited to macOS?

Daniel if you want access to a mac to take a look, I can offer screensharing as an option.

I will try to test this on a borrowed Mac, although I will only be able to test with an en_US keyboard.

Thanks for having a look at the bug.

You can test with other keyboard layouts by adding other languages in the
macOS System preferences > Keyboard > Input sources
+ Check ``Show input menu in menu bar``

> On Mar 30, 2018, at 13:15, Be <email address hidden> wrote:
>
> I will try to test this on a borrowed Mac, although I will only be able
> to test with an en_US keyboard.
>
> --
> You received this bug notification because you are a member of Mixxx
> Development Team, which is subscribed to Mixxx.
> https://bugs.launchpad.net/bugs/1723920
>
> Title:
> wrong key bindings for hotcues
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mixxx/+bug/1723920/+subscriptions

Tested this again with the latest available 2.2.0-rc (build 2.2 r6638) on macOS 10.14.2 (18C54), and i can NOT confirm this time.

I do think, a lot of the confusion comes from not knowing which keyboard mapping Mixxx actually uses when starting up. There is a debug line missing when loading a default mapping. [1]

So if a user set its system language to EN, but the Mixxx language to DE, it loads up the EN layout. The systems keyboard mapping must explicitly set to EN too. There are possibly many other combinations, since e.g. The Mixxx app language setting is DE, but the Mixxx keyboard language is de_DE , and so on.

[1] https://github.com/mixxxdj/mixxx/blob/master/src/mixxx.cpp#L794

Sorry, I do not keep track with what's happening on Launchpad as this bug tracking system is driving me nuts :(

In my case, macOS 10.13.6, Mixxx 2.1.8 and language set to "system" while system is german.

For me this problem is unchanged. pressing "y" which is hotcue 1 does nothing while pressing "z" sets hotcue 1. but that is not correct behaviour for german locale as "YXCV" are expected to be hotcue 1234.

Is this solvable? Another solution is to simply use mixxx in english locale and be done. But then again, it makes no sense to offer other locales if key bindings are then broken.

Just tested again with latest "Mixxx" "2.3.0-alpha-pre" "(git master r6782; built on: Apr 27 2019 @ 21:23:37) on macos 10.14.3 (german) and it works as expected. Pressing YXCV correctly trigger hotcue 1-4

@foss-4
Please test with the latest Mixxx:
a) The locale your mac is set to.
   From the terminal execute ``defaults read -g AppleLocale``, and post the output.
b) start Mixxx in developer mode ``./mixxx --developer``, and look in the terminal output for a line similar to ``Found and will use custom keyboard preset`` or `` de_DE.kbd.cfg not found, using en_US.kbd.cfg``

macOS 10.13.6, mixxx 2.3.0-alpha-pre (build master r6782)
verified: works as expected

macOS 10.13.6, mixxx 2.2.1 (build 2.2 r6690)
verified: works as expected

setting milestone to 2.2.1 as that's the first version known to fix this. feel free to also test 2.1.8 and adjust milestone. but I think that download should be hidden on the website or put into a new "old releases" section so not wasting time on testing that.

Mixxx now uses GitHub for bug tracking. This bug has been migrated to:
https://github.com/mixxxdj/mixxx/issues/8949