# Version 1.1.17.0 is now live

**URL:** <https://forum.fxsound.com/t/version-1-1-17-0-is-now-live/1927>\
**Category:** Info and Announcements\
**Created:** [May 24, 2023, 1:14am UTC](https://forum.fxsound.com/t/version-1-1-17-0-is-now-live/1927 "2023-05-24T01:14:29Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![james](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.fxsound.com/james/32/2294_2.png) [@james](https://forum.fxsound.com/u/james)\
**Post date:** [May 24, 2023, 1:14am UTC](https://forum.fxsound.com/t/version-1-1-17-0-is-now-live/1927/1 "2023-05-24T01:14:29Z")

</div>

- Added language support for Hungarian, Dutch, and Thai
- Translation corrections for Vietnamese, Chinese, and Turkish
- New icon
- Notifications on Windows 11 can now be disabled in the OS settings
- Fixed bug power consumption bug in sleep
- Bug with NVDA screen reader fixed
- Accessibility fixes for keyboard focus and hint text in preset save

We have the Windows certification problem sorted. So expect more frequent updates going forward.

---

<div class="post-metadata">

**Author:** ![JohnFowler](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.fxsound.com/johnfowler/32/1038_2.png) [@JohnFowler](https://forum.fxsound.com/u/JohnFowler)\
**Post date:** [May 24, 2023, 7:19am UTC](https://forum.fxsound.com/t/version-1-1-17-0-is-now-live/1927/2 "2023-05-24T07:19:48Z")

</div>

**Congratulations to all!**  
Special congratulations to _ **@bvijay** _ and thank you for your help!  
It works perfectly in Hungarian.  
Best regards,  
John Fowler

---

<div class="post-metadata">

**Author:** ![Dolmatov](https://avatars.discourse-cdn.com/v4/letter/d/d26b3c/32.png) [@Dolmatov](https://forum.fxsound.com/u/Dolmatov)\
**Post date:** [May 24, 2023, 7:45am UTC](https://forum.fxsound.com/t/version-1-1-17-0-is-now-live/1927/3 "2023-05-24T07:45:41Z")

</div>

Which pill will you choose, left or right? (joke about the Matrix)

> **Summary**
>
> ![iO7etBeYpA](https://canada1.discourse-cdn.com/flex030/uploads/fxsound/original/2X/a/a9b167318cdb392c601b4746b0d6f4345496b771.jpeg)  
> On the left is a message about what’s new, on the right is a notification to the system about the device.

---

<div class="post-metadata">

**Author:** ![caleb59](https://avatars.discourse-cdn.com/v4/letter/c/b5a626/32.png) [@caleb59](https://forum.fxsound.com/u/caleb59)\
**Post date:** [May 24, 2023, 7:57am UTC](https://forum.fxsound.com/t/version-1-1-17-0-is-now-live/1927/4 "2023-05-24T07:57:11Z")

</div>

Are you kidding me?

 ![](https://canada1.discourse-cdn.com/flex030/uploads/fxsound/original/2X/f/f69284da9fabafa2e7f942535458929bceebae94.jpeg)

---

<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:** [May 24, 2023, 12:33pm UTC](https://forum.fxsound.com/t/version-1-1-17-0-is-now-live/1927/5 "2023-05-24T12:33:03Z")

</div>

> [@caleb59](#):
>
> Are you kidding me?
> 
> ![](https://canada1.discourse-cdn.com/flex030/uploads/fxsound/original/2X/f/f69284da9fabafa2e7f942535458929bceebae94.jpeg)

Hi Caleb,  
Could you please first try manually uninstalling the old version, and installing the new version?

---

<div class="post-metadata">

**Author:** ![caleb59](https://avatars.discourse-cdn.com/v4/letter/c/b5a626/32.png) [@caleb59](https://forum.fxsound.com/u/caleb59)\
**Post date:** [May 24, 2023, 1:08pm UTC](https://forum.fxsound.com/t/version-1-1-17-0-is-now-live/1927/6 "2023-05-24T13:08:55Z")

</div>

No problems when I manually uninstall the old version.

---

<div class="post-metadata">

**Author:** ![gidano](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.fxsound.com/gidano/32/664_2.png) [@gidano](https://forum.fxsound.com/u/gidano)\
**Post date:** [May 24, 2023, 3:43pm UTC](https://forum.fxsound.com/t/version-1-1-17-0-is-now-live/1927/7 "2023-05-24T15:43:23Z")

</div>

For me, it was perfectly updated from the installed version 1.1.16.

---

<div class="post-metadata">

**Author:** ![CriticalHit\_NL](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.fxsound.com/criticalhit_nl/32/2452_2.png) [@CriticalHit\_NL](https://forum.fxsound.com/u/CriticalHit_NL)\
**Post date:** [May 24, 2023, 11:23pm UTC](https://forum.fxsound.com/t/version-1-1-17-0-is-now-live/1927/9 "2023-05-24T23:23:12Z")

</div>

Happy to see a new version release! This is awesome!  
The upgrade from version 1.1.16.0 went smoothly here on Windows 10 22H2 with Realtek ALC4082 (Logitech Z906, analog) & Logitech G35 7.1

Unfortunately I do notice the bug from below link is not yet fixed in this version:

> [@Memory leak in audiodg.exe with FXSound 1.1.16.0](https://forum.fxsound.com/t/memory-leak-in-audiodg-exe-with-fxsound-1-1-16-0/1445):
>
> I’m here to report an issue that appears to only play when FXSound is running, currently version 1.1.16.0 and this has been happening for months and on two different systems. This issue mostly appears to happen when the system has been running for a prolonged period of time but it is random. Usually with 1+ day uptimes of operating system. The problem is that the system process audiodg.exe starts consuming considerable amounts of memory, sometimes even more than 1GB until FXSound is closed and…

@bvijay @james since it was not in the releasenotes I do not think a fix was yet implemented for this, is this true?  
If so, is there an idea when a fix for this issue could be released?

Thank you in advance and congratulations on the new release!

Keep it up. 😃

---

<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:** [May 25, 2023, 4:49am UTC](https://forum.fxsound.com/t/version-1-1-17-0-is-now-live/1927/10 "2023-05-25T04:49:57Z")

</div>

Hi @CriticalHit_NL,  
Sorry for not including the memory leak fix in this release. After some testing I found that the fix that I identified was not fully solving the issue in all scenarios. I am still investigating the fix for this. I am hopeful of including the fix in the next release.

---

<div class="post-metadata">

**Author:** ![CriticalHit\_NL](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.fxsound.com/criticalhit_nl/32/2452_2.png) [@CriticalHit\_NL](https://forum.fxsound.com/u/CriticalHit_NL)\
**Post date:** [May 25, 2023, 4:06pm UTC](https://forum.fxsound.com/t/version-1-1-17-0-is-now-live/1927/11 "2023-05-25T16:06:11Z")

</div>

Thank you for your reply @bvijay  
I understand, it is better this way to find a solution that fully solves the issue.  
Thank you for the heads up on this.

Looking forward to future updates. 👍

---

<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:** [May 26, 2023, 2:23am UTC](https://forum.fxsound.com/t/version-1-1-17-0-is-now-live/1927/12 "2023-05-26T02:23:30Z")

</div>

Thanks @CriticalHit_NL for understanding.

---

<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:** [May 26, 2023, 2:41am UTC](https://forum.fxsound.com/t/version-1-1-17-0-is-now-live/1927/13 "2023-05-26T02:41:14Z")

</div>

Thank you @JohnFowler.  
Hungarian language support is possible with your help in providing us the translation.

---

<div class="post-metadata">

**Author:** ![Hansonbiz](https://avatars.discourse-cdn.com/v4/letter/h/b77776/32.png) [@Hansonbiz](https://forum.fxsound.com/u/Hansonbiz)\
**Post date:** [May 27, 2023, 4:17am UTC](https://forum.fxsound.com/t/version-1-1-17-0-is-now-live/1927/14 "2023-05-27T04:17:44Z")

</div>

Thanks the improvements, FXS crew! Long-time user here. I’ve been really satisfied since leaving my old DFX for the new. The current 1.1.16.0 version has been stellar for my use. Everything just works with my Win 10/pro system.

Thus, my question: Is there a rush to update, or can I stick with what I have until I experience probs?

Keep up the great work, guys. I’m especially fond of the equalizer.

---

<div class="post-metadata">

**Author:** ![Dolmatov](https://avatars.discourse-cdn.com/v4/letter/d/d26b3c/32.png) [@Dolmatov](https://forum.fxsound.com/u/Dolmatov)\
**Post date:** [May 27, 2023, 10:25am UTC](https://forum.fxsound.com/t/version-1-1-17-0-is-now-live/1927/15 "2023-05-27T10:25:44Z")

</div>

If the situations in the changelog (first post) don’t concern you, then getting updates is not a top priority.

---

<div class="post-metadata">

**Author:** ![caleb59](https://avatars.discourse-cdn.com/v4/letter/c/b5a626/32.png) [@caleb59](https://forum.fxsound.com/u/caleb59)\
**Post date:** [May 27, 2023, 2:56pm UTC](https://forum.fxsound.com/t/version-1-1-17-0-is-now-live/1927/16 "2023-05-27T14:56:41Z")

</div>

FxSound notifications in this version are really horrible annoying sometimes. Like for example I’m using Sound Blaster Z - FxSound everytime when I start/restart my PC notify me 2x about used audio device.

It was ridiculous when I reinstalled Nvidia graphic card drivers - FxSound notified me 5x in a row about used audio device when I restarted my PC after Nvidia drivers installation.

Definitely I was forced in this way to completely disable any notifications from FxSound in Windows 11 settings.

---

<div class="post-metadata">

**Author:** ![Hansonbiz](https://avatars.discourse-cdn.com/v4/letter/h/b77776/32.png) [@Hansonbiz](https://forum.fxsound.com/u/Hansonbiz)\
**Post date:** [May 27, 2023, 3:09pm UTC](https://forum.fxsound.com/t/version-1-1-17-0-is-now-live/1927/17 "2023-05-27T15:09:45Z")

</div>

Thank you for your quick response!

---

<div class="post-metadata">

**Author:** ![Milincho](https://avatars.discourse-cdn.com/v4/letter/m/57b2e6/32.png) [@Milincho](https://forum.fxsound.com/u/Milincho)\
**Post date:** [May 30, 2023, 4:29pm UTC](https://forum.fxsound.com/t/version-1-1-17-0-is-now-live/1927/18 "2023-05-30T16:29:26Z")

</div>

After all this time… still no shortcuts support for other keyboards lang? it is _ridiculous_ that we have to change the keyboard to US for _just_ FxSound shortcuts… why is it so hard to _disable_ this “feature” nobody ever asked for?

---

<div class="post-metadata">

**Author:** ![james](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.fxsound.com/james/32/2294_2.png) [@james](https://forum.fxsound.com/u/james)\
**Post date:** [May 31, 2023, 3:35pm UTC](https://forum.fxsound.com/t/version-1-1-17-0-is-now-live/1927/19 "2023-05-31T15:35:45Z")

</div>

We’ll be working on a fix for this soon!

It’s one we’ve put off as it does require a decent amount of work for us to enable users to be able to select their own keyboard shortcuts.

The reason we auto disable it for non-US keyboards is that the default keyboard shortcuts we used were conflicting with some Windows shortcuts for non-US keyboards and we were getting complaints.

---

<div class="post-metadata">

**Author:** ![Ayman](https://avatars.discourse-cdn.com/v4/letter/a/dec6dc/32.png) [@Ayman](https://forum.fxsound.com/u/Ayman)\
**Post date:** [June 2, 2023, 1:04am UTC](https://forum.fxsound.com/t/version-1-1-17-0-is-now-live/1927/20 "2023-06-02T01:04:51Z")

</div>

Finally, my issue has got fixed, Thank you

---

<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:** [June 30, 2023, 4:44pm UTC](https://forum.fxsound.com/t/version-1-1-17-0-is-now-live/1927/21 "2023-06-30T16:44:13Z")

</div>

Hi @CriticalHit_NL, the fix for the memory leak is available in the latest version 1.1.18.0 available for download from our website. You can download and install this version. Thanks for your patience!

[Next page](https://forum.fxsound.com/t/version-1-1-17-0-is-now-live/1927.md?page=2)
