# New Shortcuts

**URL:** <https://forum.fxsound.com/t/new-shortcuts/2551>\
**Category:** Share Feedback\
**Created:** [November 27, 2023, 8:24pm UTC](https://forum.fxsound.com/t/new-shortcuts/2551 "2023-11-27T20:24:01Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![Michiel](https://avatars.discourse-cdn.com/v4/letter/m/dbc845/32.png) [@Michiel](https://forum.fxsound.com/u/Michiel)\
**Post date:** [November 27, 2023, 8:24pm UTC](https://forum.fxsound.com/t/new-shortcuts/2551/1 "2023-11-27T20:24:01Z")

</div>

I would love to see a function to customize shortcuts. I really like the control+alt+a and control+alt+d from 1.19.0. Please make the shortcuts customizable.

---

<div class="post-metadata">

**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:** [November 27, 2023, 9:36pm UTC](https://forum.fxsound.com/t/new-shortcuts/2551/2 "2023-11-27T21:36:05Z")

</div>

Hayo Michiel,  
The latest version released is v1.1.20.0, which includes customizable shortcuts, due to a continuous high demand from users for such a function.  
You can download it for free from [fxsound.com](http://fxsound.com/) or the [Microsoft Store](https://apps.microsoft.com/store/detail/fxsound/XP8JK4TBQ03LZ4), as usual.  
If this was helpful, then please mark your query as solved.

 ![image](https://canada1.discourse-cdn.com/flex030/uploads/fxsound/original/2X/0/0c0893c1929f95123433c2944368e95171933747.png)

---

<div class="post-metadata">

**Author:** ![FrozenWarrior401](https://avatars.discourse-cdn.com/v4/letter/f/8edcca/32.png) [@FrozenWarrior401](https://forum.fxsound.com/u/FrozenWarrior401)\
**Post date:** [January 12, 2024, 3:41pm UTC](https://forum.fxsound.com/t/new-shortcuts/2551/3 "2024-01-12T15:41:32Z")

</div>

How to enable shortcuts?  
v1.1.16.0

 ![image](https://canada1.discourse-cdn.com/flex030/uploads/fxsound/original/2X/7/7d0141bf72c2cfb87731521b91f21ba0aec0d9d3.png)

---

<div class="post-metadata">

**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:** [January 12, 2024, 3:48pm UTC](https://forum.fxsound.com/t/new-shortcuts/2551/4 "2024-01-12T15:48:30Z")

</div>

> [@FrozenWarrior401](#):
>
> How to enable shortcuts?  
> v1.1.16.0

Update to v1.1.20.0?

---

<div class="post-metadata">

**Author:** ![FrozenWarrior401](https://avatars.discourse-cdn.com/v4/letter/f/8edcca/32.png) [@FrozenWarrior401](https://forum.fxsound.com/u/FrozenWarrior401)\
**Post date:** [January 12, 2024, 3:53pm UTC](https://forum.fxsound.com/t/new-shortcuts/2551/5 "2024-01-12T15:53:39Z")

</div>

Excellent, it’s working!  
I first installed the app via Microsoft Store, manually downloading the latest version enabled the shortcuts.

Thanks!!

---

<div class="post-metadata">

**Author:** ![mumpi](https://avatars.discourse-cdn.com/v4/letter/m/4bbf92/32.png) [@mumpi](https://forum.fxsound.com/u/mumpi)\
**Post date:** [January 17, 2024, 10:46am UTC](https://forum.fxsound.com/t/new-shortcuts/2551/6 "2024-01-17T10:46:18Z")

</div>

Feedback from a German user:

When using a German keyboard layout, CTRL+ALT+Q is interpreted as ALT GR+Q, which is where the @ sign sits on a German keyboard. When on (was the default on my system), the shortcut blocks using this character. Can be quite an inconvenience and “hard to find”, especially when using the software for the first time.

I know it’s customizable. I am talking about considering a change of the default setting.

---

<div class="post-metadata">

**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:** [January 17, 2024, 1:34pm UTC](https://forum.fxsound.com/t/new-shortcuts/2551/7 "2024-01-17T13:34:20Z")

</div>

> [@mumpi](#):
>
> I know it’s customizable. I am talking about considering a change of the default setting.

Thank you for the suggestion.  
I can understand that, from your standpoint, simply changing the combination to a different one, seems like a straightforward solution to your particular problem.  
However, it is worth taking into account that there are many other keyboard layouts out there, Latin as well as non-Latin ones, and so the probability of recreating the same problem, only for a different keyboard layout, is something that needs to be taken into account - and, in order to achieve 100% compatibility, we would have to review each key combination for every possible keyboard layout.  
I think a smarter road to travel would be to simply acknowledge that creating a piece of software that is 100% conflict-free, is a utopian goal, which is ultimately impossible to achieve in practice.

> **[Keyboard layout](https://en.m.wikipedia.org/wiki/Keyboard_layout#:~:text=They%20can%20be%20divided%20into,QZERTY%20and%20national%20variants%20thereof)**
>
> A keyboard layout is any specific physical, visual or functional arrangement of the keys, legends, or key-meaning associations (respectively) of a computer keyboard, mobile phone, or other computer-controlled typographic keyboard. 
> Physical layout is the actual positioning of keys on a keyboard. Visual layout is the arrangement of the legends (labels, markings, engravings) that appear on those keys. Functional layout is the arrangement of the key-meaning association or keyboard mapping, determin...

---

<div class="post-metadata">

**Author:** ![mumpi](https://avatars.discourse-cdn.com/v4/letter/m/4bbf92/32.png) [@mumpi](https://forum.fxsound.com/u/mumpi)\
**Post date:** [January 17, 2024, 1:52pm UTC](https://forum.fxsound.com/t/new-shortcuts/2551/8 "2024-01-17T13:52:51Z")

</div>

Sure thing, understood.

THEN, maybe it would be smarter not to enable the shortcuts by default. Things is, it took me quite a few minutes to figure out that FxSound was the cause for the @ “key” not working anymore. I mean, who uses this key nowadays? 😉 If I wouldn’t have had any music running, it may have been even longer (I noticed the change in sound) and potentially frustrating.

When you newly install FxSound on a German system (lots of Swiss, Austrian and other users included) this can cause some major inconvenience. Also consider the no-nerd users, who may not even make the connection.

Anyway, honestly and no offence, I don’t really care if and how you handle this “issue”. It is addressed on my end. I just wanted to point it out, so you are aware in case someone else reports it. Surely you cannot really address this for each and every key combination, as you rightly said, but you can change the default behaviour and e.g. display a warning that a key combination may be taken and that users should be aware of it when enabling. (Or you can go to CTRL+SHIFT or ALT-SHIFT as default, which does not default to characters on standard layouts.)

---

<div class="post-metadata">

**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:** [January 17, 2024, 2:02pm UTC](https://forum.fxsound.com/t/new-shortcuts/2551/9 "2024-01-17T14:02:03Z")

</div>

> [@mumpi](#):
>
> THEN, maybe it would be smarter not to enable the shortcuts by default.

> [@mumpi](#):
>
> you can change the default behaviour and e.g. display a warning that a key combination may be taken and that users should be aware of it when enabling.

These are both good suggestions.  
Thanks.

@bvijay

---

<div class="post-metadata">

**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:** [January 17, 2024, 11:30pm UTC](https://forum.fxsound.com/t/new-shortcuts/2551/10 "2024-01-17T23:30:18Z")

</div>

💫 Freshly added to the GitHub Issues:

> <https://github.com/fxsound2/fxsound-app/issues/53>
>
> Forum member mumpi noted that on German/Austrian/Swiss keyboard layouts, the sta…ndard Ctrl+Alt+Q shortcut to toggle FxSound On/Off conflicts with the creation of the "@" symbol; and also proposed several possible solutions:
> 
> \- Change the key combination for shortcuts: "You can go to CTRL+SHIFT or ALT-SHIFT as default, which does not default to characters on standard layouts."
> \- Have the shortcuts disabled by default on first launch;
> \- Display a warning pop-up on first launch to notify users of the conflict.
> 
> Sources:
> https://forum.fxsound.com/t/new-shortcuts/2551/6/
> https://forum.fxsound.com/t/new-shortcuts/2551/8/

---

<div class="post-metadata">

**Author:** ![bvijay](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.fxsound.com/bvijay/32/84_2.png) [@bvijay](https://forum.fxsound.com/u/bvijay)\
**Post date:** [January 22, 2024, 3:03pm UTC](https://forum.fxsound.com/t/new-shortcuts/2551/11 "2024-01-22T15:03:06Z")

</div>

Thanks @mumpi for the suggestions. It should be possible to find out if the keyboard combination is used by the system as shortcut for another character. We can prevent those combinations from being reused. I will also see if Ctrl+Shift or Alt+Shift can be used instead of Ctrl+Alt to avoid shortcuts from conflicting with AltGr shortcuts.
