# Issue with Default Shortcuts **URL:** \ **Category:** Share Feedback\ **Created:** [August 9, 2023, 8:52pm UTC](https://forum.fxsound.com/t/issue-with-default-shortcuts/2148 "2023-08-09T20:52:52Z")\ **Posts on this page:** 13\ **Page:** 1
**Author:** ![vukbo](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.fxsound.com/vukbo/32/1226_2.png) [@vukbo](https://forum.fxsound.com/u/vukbo)\ **Post date:** [August 9, 2023, 8:52pm UTC](https://forum.fxsound.com/t/issue-with-default-shortcuts/2148/1 "2023-08-09T20:52:52Z")
# Hy 👋 ## Background I started to use this app several days ago. I really like it so far, it is very clean and works like intended. Props to the devs, making such a smooth App is hard work! ❀ ## Issue I started to run into one issue tho. The Default Shortcuts (STRG + ALT + [Q,E,A,D,W,S]) conflict with my US international keyboard layout. Typing these special characters (Ă€,Ă„,Ă©,ĂĄ,ß,Ă°) is therefore impossible right now, without accidentaly triggering the Apps shortcuts. That is a real bummer, because the shortcuts are really nice to have on Windows. ## Limitations Changing my keyboard layout is sadly not an option. My first language is german, so I do need a lot of the special characters stated above, but I also write a lot of english therefore I have the US international keyboard. It allows me to write in both languages with ease, without changing the layout constantly in the operating system. ## Possible Solution **1. Changing the Default Shortcuts** This solution might be the most _“straightforward”_ to do. Changing the default shortcuts to other keys so it wouldn’t interfere anymore. Thinking of characters like STRG + ALT + (F,G,H,J,K) on the US international keyboard, because they are not assigned to any special characters. _Possible Issues: I. The new shortcuts could interfere with other layouts/special characters. Would need further research and thorough testing. II. The new shortcuts wouldn’t be so conveniently placed, like the current layout._ * * * **2. Adding the possibility for Custom Shortcuts** This would take more time, but might be worth the effort. Being able to set the shortcuts by yourself. Like having the described function and being able to assign your own shortcut to it. This would not only fix the keyboard layout issue. It would make FXSound compatible with workflows of other Apss, that might have their own set of shortcuts. Personally I would prefer this solution, but I do understand that every new feature needs a lot of effort in regards to development. _Possible Issues: I. A big investment development wise._ ## Finale Hope I could get the issue across and my layman solutions to it. 😅 Have a nice day! ---
**Author:** ![doolhoofd](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.fxsound.com/doolhoofd/32/1131_2.png) [@doolhoofd](https://forum.fxsound.com/u/doolhoofd)\ **Post date:** [August 9, 2023, 9:33pm UTC](https://forum.fxsound.com/t/issue-with-default-shortcuts/2148/2 "2023-08-09T21:33:07Z")
Hy! 👋 Thank you for your understanding regarding the programming efforts, and for thinking ahead as well. You can rest assured that the team has every intention to address the shortcuts issue as soon as possible: > [@Adjust Keyboard Shortcuts Keymap](https://forum.fxsound.com/t/adjust-keyboard-shortcuts-keymap/31): > > This would fix some issues we’re running into with Non-English keyboards conflicting with the default keyboard shortcuts. > [@On another topic](https://forum.fxsound.com/t/2079/1): > > Option to change keyboard shortcuts (and re-enable keyboard shortcuts for non-US keyboards) In the meanwhile, one of our most helpful forum regulars proposed the following solution: > [@Shortcuts setting overrides keys](https://forum.fxsound.com/t/shortcuts-setting-overrides-keys/1545/11): > > You are describing a hotkey conflict. If we accept that DFX cannot resolve the write error on the saved state, there is no option but to re-assign the key thru a third-party app or setting. Google [hotkey manager]. > > [https://www.howtogeek.com/710290/how-to-remap-any-key-or-shortcut-on-windows-10/](https://www.howtogeek.com/710290/how-to-remap-any-key-or-shortcut-on-windows-10/) > > [Release SharpKeys 3.9.4 · randyrants/sharpkeys · GitHub](https://github.com/randyrants/sharpkeys/releases/tag/v3.9.4) > > Your install should save the setting. My “tip” is a hack. I would use SharpKeys to create the registry string or entry. Then, I would save that as a .reg file for future use. On a new OS install, if the setting continues to fail, merge the reg file. No need to install a keymapper. > > Pro Tip: > Modify that file to remove the settings. Save both ie “KeymapEnable.reg” and “KeymapDisable.reg” > > There is nothing proprietary about key mapping. And yet another solution would be to simply disable the shortcuts for the time being, and avoid the key conflict altogether. There’s a checkbox in the Settings menu dedicated to the shortcuts: ![shortcuts](https://canada1.discourse-cdn.com/flex030/uploads/fxsound/original/2X/4/4158a967ea232cbcfc1555d48a3472b4657becbf.png) The team also added the following info which could be useful towards this purpose: > [@Can't disable Keyboard Shortcuts](https://forum.fxsound.com/t/cant-disable-keyboard-shortcuts/927/4): > > If they’re greyed out they should already be disabled. But it sounds like they’re still active? @bvijay any idea what might be going on here? > [@Can't disable Keyboard Shortcuts](https://forum.fxsound.com/t/cant-disable-keyboard-shortcuts/927/5): > > The option can get greyed out if the keyboard is non-English or if the keyboard language selected in the system settings is non-English. So, please check the keyboard language selected in system tray or system settings. > > ![image](https://canada1.discourse-cdn.com/flex030/uploads/fxsound/original/1X/401967bd9cfbf8f9fbebacc956b43973e83ebfa0.png) > > ![image](https://canada1.discourse-cdn.com/flex030/uploads/fxsound/original/1X/d418c7fef25147fd20f6e5201d76103dc3869785.png) ---
**Author:** ![vukbo](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.fxsound.com/vukbo/32/1226_2.png) [@vukbo](https://forum.fxsound.com/u/vukbo)\ **Post date:** [August 9, 2023, 10:03pm UTC](https://forum.fxsound.com/t/issue-with-default-shortcuts/2148/3 "2023-08-09T22:03:16Z")
Ohh thank you for this quick and thourough answer. ❀ ---
**Author:** ![doolhoofd](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.fxsound.com/doolhoofd/32/1131_2.png) [@doolhoofd](https://forum.fxsound.com/u/doolhoofd)\ **Post date:** [August 9, 2023, 10:08pm UTC](https://forum.fxsound.com/t/issue-with-default-shortcuts/2148/4 "2023-08-09T22:08:41Z")
Happy to help. ![alice - avec plaisir](https://canada1.discourse-cdn.com/flex030/uploads/fxsound/original/2X/9/954e313047c7f5897a960d4094131d8d7f78c2a4.gif) ---
**Author:** ![Speedyblupi](https://avatars.discourse-cdn.com/v4/letter/s/5daacb/32.png) [@Speedyblupi](https://forum.fxsound.com/u/Speedyblupi)\ **Post date:** [August 15, 2023, 5:50am UTC](https://forum.fxsound.com/t/issue-with-default-shortcuts/2148/5 "2023-08-15T05:50:44Z")
With all due respect _why the fuck_ is ctrl+alt+e a default shortcut for this app? This is the Windows shortcut for typing an e with an acute accent (Ă©). There is no indication when installing the app that it will automatically hijack this shortcut, which many people rely on. Giving us the option to enable it would be fine, but doing it by default is horrible. ---
**Author:** ![framug](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.fxsound.com/framug/32/1340_2.png) [@framug](https://forum.fxsound.com/u/framug)\ **Post date:** [August 18, 2023, 11:11am UTC](https://forum.fxsound.com/t/issue-with-default-shortcuts/2148/6 "2023-08-18T11:11:45Z")
Hello, I’m working since a long time in an open source application in C#. I would like to use fxsound for improve users experience (and also mine). For this, I would be able to change the fxsound ambient (music when music is played, movies when films played, TV, and also specific like voice improve for films with too; much surround spatial effects but less loud for voice). The best way I suppose would be to use shortcuts but, this software is international (For example, I’m french with azerty keyboard). Then, do you have a planned date for international shortcuts working ? B.R. Franck. ---
**Author:** ![doolhoofd](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.fxsound.com/doolhoofd/32/1131_2.png) [@doolhoofd](https://forum.fxsound.com/u/doolhoofd)\ **Post date:** [August 20, 2023, 12:50am UTC](https://forum.fxsound.com/t/issue-with-default-shortcuts/2148/7 "2023-08-20T00:50:23Z")
> [@framug](#): > > Then, do you have a planned date for international shortcuts working ? > B.R. > Franck. There are plans to add modifiable keyboard shortcuts as an update for v1.1.21.0. Please note that this is not a promise, just a goal that’s currently being strived for. ---
**Author:** ![framug](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.fxsound.com/framug/32/1340_2.png) [@framug](https://forum.fxsound.com/u/framug)\ **Post date:** [August 20, 2023, 2:27pm UTC](https://forum.fxsound.com/t/issue-with-default-shortcuts/2148/8 "2023-08-20T14:27:13Z")
Hello, Thanks for your answer. A question, please. Is your software free ? Open source ? Is the code available somewhere ? Also, instead of using shortcuts, if by chance you plan to create a way for a direct access as fxsound ambient changes (an API like) then, please, let me know. 😉 Regards. ---
**Author:** ![doolhoofd](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.fxsound.com/doolhoofd/32/1131_2.png) [@doolhoofd](https://forum.fxsound.com/u/doolhoofd)\ **Post date:** [August 20, 2023, 5:13pm UTC](https://forum.fxsound.com/t/issue-with-default-shortcuts/2148/9 "2023-08-20T17:13:26Z")
> [@framug](#): > > Is your software free ? If you mean, does it cost 0 $, then yes, FxSound is free. > [@framug](#): > > Open source ? Not yet, but there are serious plans on the table to make it opensource soon. > [@framug](#): > > Is the code available somewhere ? Sorry, no, not yet. > [@framug](#): > > Also, instead of using shortcuts, if by chance you plan to create a way for a direct access as fxsound ambient changes (an API like) then, please, let me know. 😉 OK, I will keep your post in mind, and will be sure to do that. ---
**Author:** ![doolhoofd](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.fxsound.com/doolhoofd/32/1131_2.png) [@doolhoofd](https://forum.fxsound.com/u/doolhoofd)\ **Post date:** [December 14, 2023, 11:01pm UTC](https://forum.fxsound.com/t/issue-with-default-shortcuts/2148/10 "2023-12-14T23:01:59Z")
> [@framug](#): > > Open source ? Yepperz: > **[FxSound LLC](https://github.com/fxsound2/)** > > FxSound LLC has 2 repositories available. Follow their code on GitHub. ---
**Author:** ![Hansk](https://avatars.discourse-cdn.com/v4/letter/h/bc8723/32.png) [@Hansk](https://forum.fxsound.com/u/Hansk)\ **Post date:** [April 25, 2024, 3:53pm UTC](https://forum.fxsound.com/t/issue-with-default-shortcuts/2148/11 "2024-04-25T15:53:38Z")
Although this thread is somewhat cold, I do have maybe something to add. With the current version of FS v1.1.22.0 the keyboard shortcuts seem to work. I’m on a fully updated W11 system AND using an American International keyboard setting. No problem with that setting. But of course there’s another issue: W11 doesn’t provide any clarity on which keyboard shortcuts are owned by which process
 Not even the ‘global’ hotkeys. I found lots of people need that clarity; how else can you know if a certain hotkey combination is already in use? Or what will you break if you ‘overrule’ an existing hotkey? There is a tool available on the internet called Hotkey Explorer. You can download it. But please beware, DON’T use it. It will mess up your system because it will ‘push’ all the possible hotkeys and feeds it to you system. Messy, not to say the least. I found another tool called Hotkey Detective. It is on GitHub, open source. This really helps to find out which process owns a hotkey combination. Though, this does not solve everything: - a hotkey combination may be globally reserved, or by an app. The latter ones, will still be bound to that app while your using that app. - there are still 64-bit and x86 hotkey owners. So, beware to look for both options. - some combinations don’t seem to have a global owner, but still do not work when I allocate them to FS (e.g. like Ctl Alt Q or Ctl Alt C) Instead of Ctl Alt Q I found that Ctl Alt R does work as a globally defined hotkey in windows on my system. Hope this helps! ---
**Author:** ![doolhoofd](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.fxsound.com/doolhoofd/32/1131_2.png) [@doolhoofd](https://forum.fxsound.com/u/doolhoofd)\ **Post date:** [April 30, 2024, 11:04pm UTC](https://forum.fxsound.com/t/issue-with-default-shortcuts/2148/12 "2024-04-30T23:04:21Z")
> [@Hansk](#): > > I found another tool called Hotkey Detective. It is on GitHub, open source. > This really helps to find out which process owns a hotkey combination. [https://github.com/ITachiLab/hotkey-detective](https://github.com/ITachiLab/hotkey-detective) Another great post, Hans! Thank you. ---
**Author:** ![Antman](https://avatars.discourse-cdn.com/v4/letter/a/eb8c5e/32.png) [@Antman](https://forum.fxsound.com/u/Antman)\ **Post date:** [May 25, 2024, 9:22pm UTC](https://forum.fxsound.com/t/issue-with-default-shortcuts/2148/13 "2024-05-25T21:22:51Z")
It toggles all audio outputs to speak with a French accent. Listen carefully and it sounds more like “Dafuq is why”. It may or may not be possible to avoid all key mapping conflicts. Perhaps the better question relates to that.