Hello FxSound Support Team,

I hope this message finds you well. I am currently working on a script to automate certain functionalities within FxSound, and I am interested in exploring whether FxSound provides a command-line interface (CLI) or any other automation options.

The goal of the automation script is to streamline the activation process of FxSound, making it more convenient for me. If FxSound offers a CLI or any other methods for automation, I would greatly appreciate information on the available commands or interfaces.

Your guidance on this matter would be invaluable in enhancing the automation capabilities of FxSound. If there are specific resources or documentation that I should refer to, please provide the necessary details.

Thank you for your time and assistance. I look forward to hearing from you.

Multiple users have requested the addition of one or more bands at the low end of FxSound's current 9-band EQ, in order to allow more precise control of frequencies below 86 Hz (with 20 Hz generally accepted as the bottom limit of human hearing).

Various difficulties attempting to combine FxSound with Surround Sound setups and technologies (such as 5.1 setups, 7.1 setups, Dolby, THX, etc.) keep getting reported on the forum.
FxSound was made with stereo setups in mind, and, as such, there are no explicit options to configure separate speakers within the UI or the Settings.
There is a three-part option available within FxSound’s “Configure Speakers” dialog box in Sound Settings: to set the device up as either stereo, 5.1, or 7.1 - but results vary, and while changing the configuration works for some, it just as often fails to work for others.
It also seems worth mentioning that several forum members have found different makeshift and sometimes counter-intuitive solutions for their particular problems, like switching to Mono, or setting the default frequency format to 24/96.

Stereo Crossfeed so listening via headphones feels as natural as listening via Stereo Speakers.
Loudness Equalization so sound isn't unnecessarily fluctuating while listening to any audio.
7.1 Virtual Surround Sound that works as closely as possible to Dolby Surround.

Forum member Ananda96 requested the addition of the possibility to "pin" FxSound's main user interface into place, similar to the one found in RainMeter widgets.

Some forum members have voiced complaints about the UI, stating that they think FxSound's main user inferface is too big, and some have requested adding an option to resize it.
On this topic, it seems worth noting that this issue was already (at least partially) addressed by a drastic reduction of the size of the main Power On/Off button plus the move of all buttons to the top right corner of the UI since v1.1.20.0, and, that an "Expand/Minimize" button, which allows users to switch to a miniature/minimalist version of the UI, is already present at the top right corner of the UI as well.

Describe the bug
When turning the program on, a component for an audio wave visualizer appears, and when turning the program off, it disappears this causes the layout to shift which affects the experience of the user and predictability when interacting with the software.

To Reproduce
Steps to reproduce the behavior:

1. Open FxSound
2. Press the turn on/off button
3. Notice how the layout shift and the user need to adjust to new placement for the elements

Expected behavior
It'd be a smoother experience if there were no noticable layout shift (by adding some placeholder or spacing)

Screenshots

System information

• Windows 10

Forum member Aryan opened a thread on the FxSound forum noting that after every closure of the program, the UI automatically places itself back in the center of the screen; this happens both with the large form of the UI as well as with its minimalized form.
An update was requested to either make both forms of the UI remember their user-chosen position on the screen at all times, or to add one or more options to the Settings to allow more control over the UI's screen position.
This feature request is closely related to the previously added #24:

Forum member Ananda96 requested the addition of the possibility to "pin" FxSound's main user interface into place, similar to the one found in RainMeter widgets.

Is your feature request related to a problem? Please describe.
I have an audio interface.
It creates multiple virtual channels. (e.g. Chat, System, Music, etc.)
I want to use FxSound to change the EQ of say Chat, keep the default output of the system to... System.
The same goes for every other channel and its respective use.

The app provides the ability to alter only one channel which is great, but then forces itself to be the main output device, causing all other applications and the system to route their audio through that ONE channel, which I don't want to do.

What happens is, FxSound app thinks it knows better, and keeps switching automatically back to being the default output when I try to make the System channel the default one and only use FxSound channel as an output device for the apps that used to have Chat as their output channel.

Describe the solution you'd like
FxSound to either have an option to allow for this annoying quirk to be turned off, or to simply forego it all together.
I IMO should be able to EQ one V-Channel while keeping the rest of my system and my defaults unaltered.

Describe alternatives you've considered
The only alternative would be me setting everything else manually to output to System for example...

Unreasonable, specially when I want to alter one app's output to occasionally fix a friend's audio because I want to hear them better without them having to buy a better microphone.

Additional context
I want to set Discord's and ONLY Discord's output to be the virtual FxSound output channel, I don't need it affecting the rest of my system.
I am on Windows 11.

Forum user @johnepalmer recently posted a request for the addition of an option in FxSound's Settings which would allow users to choose between either enabling or disabling the launch of FxSound on startup.
https://forum.fxsound.com/t/suggestion-for-upgrade-startup-option-general-settings/2141

Multiple users have requested increasing the number of custom-made and/or Bonus Presets able to be saved within the main interface.
Currently, this number is limited to 10 additional Presets.

A lot of forum users have requested the creation/development of versions of FxSound for other operating systems, such as:

1. Mac/iOS,
2. Android,
3. Linux,
4. Windows phones;

Besides these, there were also requests for a "portable" version of FxSound, a "sideloadable" version, a VST plugin version, etc..

I met a bug when I was playing the CS2.Every times I click the 'K' to speak in the game,after I release it,the sound output will be really strange.It just like the sound is slow down and I need to change the output device so that it can output normally.I also changed my devices but it didn't work.
In the CS2 settings,when I select the output device as the fxsound the problem will come out,but no thing wrong when I select my sony headset.

Describe the bug
When the main audio device is silent for a few minutes, FX Sound switches to Oculus Virtual Device ( from Oculus App )

To Reproduce
Steps to reproduce the behavior:

1. Do nothing, play nothing
2. It switches to Oculus Device

Expected behavior
Don't switch

System information

• Windows 11
• Dell Monitor ( from Nvidia graphics card )

Additional context
Sometimes the main audio device disappears from the list, so I have to go through windows settings to pick it up again

Many forum members have reported issues attempting to use FxSound with Bluetooth connectivity and Bluetooth devices.
In short, Bluetooth is an issue that keeps popping up on the forum, with a wide range of reported malfunctions.
To illustrate this point: a search across the forum for the term "Bluetooth" currently returns 46 results,
https://forum.fxsound.com/search?q=Bluetooth

Describe the bug
Latest FX Version Shows Annoying Action Center Notifications When disabled, re-enabled after reboot ](https://forum.fxsound.com/t/latest-fx-version-shows-annoying-action-center-notifications-when-switching-playback-devices-and-when-i-completely-disable-all-notifications-for-fxsound-they-re-enable-themselves-ive-tried-everything-any-ideas-thanks/2049/17)

@bvijay74 reported in the above linked thread

In Windows 10 I see that disabling FxSound notifications in the system settings doesn’t show the notifications until applications exits.

But OS is persisting the settings and when the application starts again, notifications start to appear unless they are disabled again.
Since the OS behaviour is different from Windows 11, I need to debug this further and implement an OS specific fix.

To Reproduce
Steps to reproduce the behavior:

1. Go to Action centre, Notifications & actions
2. Click on 'disable for FXSound'
3. Reboot
4. Login
5. Notifications enabled after reboot, and displayed in action centre

Expected behavior
No notifications after reboot

System information

• Windows 10 December 2023 patch
• Realtek Speakers, bluetooth headphones
• FxSound v1.1.20.0 installed from fxsound website

Additional context

Reported at the link above, but no GitHub issue created

Since FxSound is open source now, why not merge https://github.com/fxsound2/Strings into this repo here directly?
That way we don't have to open PR's for both repos for additions / changes.

A couple of users/forum members - Foioyoi, zanezonair, and spark, among possible others - have requested the addition of a virtual PreAmp to FxSound in order to allow easy volume control.
On this topic, it seems worth mentioning that, in recent versions of Windows, the shortcut Win + G should already allow access to volume control for FxSound (see added screenshot); and, that there are several other programs like e.g. EarTrumpet (as well as many/most media players) available online, which are able to perform a similar function, free of charge.

Forum member 1FF proposed adding a blank / zero-processing Preset to the drop-down menu of existing pre-loaded / factory default ones.

https://forum.fxsound.com/t/language-options/27/117

Example:

Adding an option, to the installer .exe or elsewhere, which allows users to select which alphabets and fonts are installed, and which aren't, in order to avoid confusion - Latin, Asian, Arabic, et cetera.
Requested by @raddyst: #19 (comment)

Forum member orionsp156 reported the following:

FxSound is missing a Title and does not have unique window info.
I am talking about the Windows-process with which FxSound can be viewed with the AutoIt Window Info program.
That makes it hard to move the FxSound window automatically (or by script) at startup.
Please add a Title to the program/executable.

Link to the thread:
https://forum.fxsound.com/t/the-executable-windows-process/2132

Multiple forum members have reported issues with Spotify; eventually, most of those turned out to be self-inflicted.
The remaining issues can be summed up as follows:

1. Distorted audio, reported by GustavoPix,
   https://forum.fxsound.com/t/distortion-using-fxsound-in-certains-music/1071
2. Choppy audio, reported by Innocentrag,
   https://forum.fxsound.com/t/audio-cuts-out-randomly-when-listening-to-spotify/2434
3. No sound, reported by Europeanonion,
   https://forum.fxsound.com/t/installed-app-works-upon-reload-it-does-not/2527

Possible cause(s):
Not much is known on these issues, since the amount of posts made by the reporting members was very sparse.

Possible solution(s):
For the second issue, the advice given by forum member caleb59 seems worth repeating;

1. Install the latest Intel Rapid Storage Technology drivers (for Intel users),
2. Run a scan with LatencyMon for possible latency issues on the machine.

Note: Improvement of stutter issues was also reported on other websites after turning off the onboard WiFi or Bluetooth (without disabling the network adapter) or after removing any attached WiFi or Bluetooth dongles.

V1.1.20.0 introduced customizable Shortcuts in response to tireless demand from users, but, while doing so, only left users the option to cycle Presets forwards/downwards through the list using the new "Change Preset" Shortcut.
Since then, multiple forum users have voiced their desire for the addition - or, one might say, the return - of an option to also cycle Presets backwards/upwards via the Shortcuts, instead of only forwards.

Multiple users have repeatedly complained about issues combining FxSound with apps like Discord, Skype, Zoom, MS Teams, etc., with various reported malfunctions.
The most frequently reported problem is loss of sound on the app itself (one way, or both ways).
Other reported issues were e.g.:
Loss of sound on the entire system;
No noticeable enhancements to the audio even though FxSound was active;
Clipping;
Unprompted switching of the active audio device; and,
Error pop-ups for certain audio devices,
Among others.
Most of these programs have their own Settings, as well as their own bugs, which of course complicates smooth simultaneous operation.

Troubleshooting:
Try setting FxSound as the Default Communication Device in your Windows Sound Settings - this actually sets FxSound as both the Default Device ànd the Default Communication Device simultaneously, but, only shows it as the Default Device.

Several forum members have complained that after installing FxSound, the Balance option, which allows a user to adjust Left/Right channel audio dsitribution (a.k.a. panning), disappears from all the Levels tab in Windows Sound.

Posted by Brock in April 2022:
https://forum.fxsound.com/t/balance-control/701
Posted by DesperateRightNow in February 2023:
https://forum.fxsound.com/t/audio-balance-in-right-and-left-headphone-sides/1678
Posted by midgetiguana in April 2023:
https://forum.fxsound.com/t/how-to-change-volume-levels-for-different-ears/1832
Posted by Chamila26 in August 2023:
https://forum.fxsound.com/t/unbalanced-left-right-channels/2223

Possible workarounds:

• Using a browser extension or media player with panning options, like EQ Extension for Chrome, EQ Extension for FireFox, WinAmp Media Player, or any other software supporting balance controls;
• Forum member Brock noted that setting a different device as the Default Device, usually remedies this issue:

From my experience, the only time the left/right volume balance does not work, is when the 'wrong' speakers are selected as default. On the sound panel (left click on speaker icon at bottom right, > sounds > playback), we usually see first "Speakers - FxSound Audio" - balance will not work with this selected. Then below that usually something like "Speakers - Realtek High Definition Audio," left click and select this as default, and the balance control works once more, and FX processing remains active.

Source: https://forum.fxsound.com/t/how-to-change-volume-levels-for-different-ears/1832/3

Many users appear to be strongly and personally affected by FxSound's notifications; and thus, many users have requested the addition of one or more options in the Settings menu:
Some users have expressed the desire to re-enable all notifications - these users often wish to return to the notification style seen in v1.1.15.0;
Some users have expressed the desire to disable them all;
Some users have expressed the desire to be able to customize FxSound's notifications, to be able to choose which are displayed, and which aren't.
It is important to note that there is a known conflict with Windows' own app-specific notification controls.
For example, some users have attempted to disable all of FxSound's notifications through their Windows notification controls, and have reported that this failed to work.

Describe the bug
When changing some values to change the sound, there is some delay, not sure if is on purpose, if its loading or something, and I don't really know if it happens only to me

To Reproduce
Steps to reproduce the behavior:
Change the values of Ambience, Dynamic Boost etc...

Expected behavior
Delay on the modification of sound

System information

• Windows Pro Educational 20H2
• Intel Smart Sound (I couldn't find what the name is, only shows that)

Hello, I have found a curious bug. Special characters @ and € no longer work when the FxSound app is active. If I switch off the app, it works as usual.
System:
Edition Windows 11 Pro
Version 23H2
Installed on 12.12.2023
Operating system build 22635.2915
Performance Windows Feature Experience Pack 1000.22682.1000.0
Keyboard:
Cherry MX-Board 10.0 N FL RGB

German Layout

Minimizing the program while in use could be a nice use case as it is often needed.

Having program already open on the taskbar is sometimes better while in use as managing functionality is more controllable than it is while in item state.

Currently there is not minimizing option. Options are either controlling from icon, opening the application and then closing it.

Is your feature request related to a problem? Please describe.
Nowadays, the sound of video music and musical instruments has a serious impact on children's heart health.
Now on the web you won't find any! There's no musical instrument in the children's primer video.
So, it's important to separate the sounds of the instruments.

Describe the solution you'd like
Current state-of-the-art algorithms
https://mvsep.com/en/algorithms

Description:
Multiple forum members have reported this error; a pop-up appears with the following text and added links:

"Oops! There's an issue with your playback device settings.
Before we can get started, please go through the troubleshooting steps here.
Contact us if you're still having problems."

I can see this error appear when I manually disable the FxSound Speakers device in my Windows Sound Settings.
A former moderator stated the following on this error:
"If that is a clean installation of Windows, normally the installation of FxSound should work fine and I have never experienced this issue reported here and there myself."

The error also appears often when users attempt to combine FxSound with Remote Desktop (RDP) access to another computer, albeit usually due to wrongful configuration of Remote Desktop-related settings.
This is the forum thread exploring the issues with RDP:
https://forum.fxsound.com/t/verified-bug-if-youre-getting-the-oops-theres-an-issue-error-read-this-first-oops-error/847

Is your feature request related to a problem? Please describe.
No

Describe the solution you'd like
Add an option to use more than 1 device and play audio through both of them simultaneously

Describe alternatives you've considered
None

Additional context
Add any other context or screenshots about the feature request here.

Steps to reproduce the behavior:

1. Go to Settings;
2. Click on Help;
3. Scroll down to Maintenance;
4. Click on Check for updates;
5. Browser opens https://www.fxsound.com/changelog

Desired behavior:
Clicking Check for updates updates FxSound to the latest version.

So far, two (but probably more) users have posted complaints on the forum about losing Windows system sounds after installing FxSound, usually occurring on Windows 11.
In the first case, with user "lonewolf" who posted last May, the problem was resolved simply by restarting the computer.
https://forum.fxsound.com/t/windows-11-system-sounds/1920
In the other case, with user "Europeanonion" who posted about two weeks ago, the problem remained unresolved (as far as I know); the user simultaneously reported a loss of all sound on Spotify after installing FxSound, apparently decided to uninstall FxSound, and, in any case, never created a second post.
https://forum.fxsound.com/t/installed-app-works-upon-reload-it-does-not/2527

Multiple forum members have complained about issues with FxSound while the Display is Off or the machine is in Sleep Mode a.k.a. Standby Mode.

Description:
When the Display is turned Off or the computer goes into Sleep Mode,

1. Playback device is lost or switched;
2. The audio lags or glitches;
3. CPU/GPU/RAM usage intensifies;
4. Battery drain intensifies.

1. Playback device is lost or switched

Possible cause(s):
Usually due to lack of support for modern standby power states (S0 low-power idle).

Possible solution(s):

1. Disable all unneeded devices including hidden ones in Windows Sound Settings;
2. Disable automatic switching in the General tab of FxSound's Settings;
3. Change the Power settings to make the computer/display stay on longer;
4. Check if your computer supports modern standby power states (S0 low-power idle) by running this command:
   powercfg /a
5. This workaround suggested by forum member metanoiance:

Using Notepad, I made a text file with the following lines, and saved it as .bat:
taskkill /f /im FxSound.exe
cd C:\Program Files\FxSound LLC\FxSound
start /min FxSound.exe
Then I used the default Windows Task Scheduler to run the file on wake-up. Meaning every time the PC wakes up from sleep or hibernation, the FxSound.exe will be restarted.
Note that the second line in the .bat file can differ depending on where you installed FxSound.

2. The audio lags or glitches

Possible cause(s):
HDMI monitor audio has proven to be prone to glitches, even without FxSound.

Possible solution(s):

1. See solution 1. above,
2. See solution 2. above,
3. Free up space on C:\ drive,
4. Install the latest Intel Rapid Storage Technology drivers (for Intel users),
5. Run a scan with LatencyMon for possible latency issues on the machine.

3. CPU/GPU/RAM usage intensifies

Possible cause(s)/solution(s):
Unknown.

4. Battery drain intensifies

Possible cause(s)/solution(s):
Unknown.

Source file not found C:\Users\WilliamKnight\AppData\Roaming\FxSound LLC\FxSound 1.1.20.0\install\fxsound1.cab
Found the error. My local account name had an empty space in the name, evidently the installer couldn't install some of the necessary files due to this "space"? So I removed the space from the name of my local account in Windows 11 and then re-ran the installer and everything installed perfectly.

This feature was initially proposed by @NullDev; since then, at least 6 other users have voiced similar and/or concurrent requests:
https://forum.fxsound.com/t/feature-request-preferred-device/1694
Such an option could allow ranking and/or disabling of audio devices: for example, by saving a list of previously connected devices in the UI, with adjustable ranking positions through dragging and/or buttons, as well as an x/close or trash-can button for disconnected or preferably undetected devices.
The device ranked first, would be categorized as, "Always change Output Device to this device when connected."
It's worth noting that there will be known conflicts between such a "Preferred/Priority Device" option, and the already-existing "Automatically switch to newly connected output device" option located under the General tab of the Settings menu, as well as with the introduction of another popular feature to automatically switch Presets and Playback Devices, initially proposed by @jamesarcher9000 (see #9 ).

Describe the bug
On windows 10, i have a 5.1 surround sound system.
When you run the game "The Last of Us - Part I" on settings, the game see by default only 2.0 sounds system.
When i disable FXSound, the game found my sound card and the 5.1 surround sound system.

Expected behavior
FXsound must be seen as 5.1 like how it's configure on my windows system

Screenshots

Good configuration with my sound card

System information

• Windows 10 Pro 1909
• internal chipset Realtek from motherboard ASRock Z97

Multiple users have requested the addition/creation of AutoEq presets to be used in combination with FxSound.
AutoEq presets are automatically generated Equalizer settings tailor-made for various different headphone models, aimed mainly at neutralizing their respective frequency response output.
This is a link to AutoEq's page on GitHub:
https://github.com/jaakkopasanen/AutoEq/wiki
This is AutoEq's main website:
https://autoeq.app

Hello -

So, I've spent some time trying to see if my issue with FXS has been reported by other users, and if so, if anyone has a suggested resolution or workaround. I have found a lot of entries describing similar issues to what I'm experiencing with various suggestions of things to try to resolve the issue. Unfortunately, after going through a majority of those suggestions, I'm still having the same intermittent issue in FXS. I have also gone through the “first-aid-kit” list with no success. However, through the various testing & install/reinstalls of the app & drivers, I decided to open up this ticket to provide some information that might be of use to the developers to help debug this potential issue. I'll try to describe the best that I can.

Bug Description
I believe my issue has already been reported by varius other users files under different categories. My FXS issues would fit under any one of these: Bluetooth Connectivity Issues, FXS Random Application Crashes, FXS Random Audio Drops/cutouts, FXS Audio Drops/Cutouts and/or App crashes when new Bluetooth Headset connects or Disconnects.

To Reproduce
So, all of these issues seem to be very random. My best suggestion to try to reproduce would be have at least 2 bluetooth audio devices available, and randomly connect them, with FXS running (either auto switch to new device, or unchecked to manually change output devices). Have a YouTube video open in Firefox and playing. Have an video playing (trying both playing & just open and paused) outside of the browser - I'm using KMPlayer specifically. While these are playing, turn on 1 of the BT-Audio devices, let it connect. This will most often cause the audio to drop (The audio playing through FXS to my TV via HDMI will cut out). This drop happens regardless of the FXS - swith automatically setting is on or off. If the audio drops, and in FXS, I swith the output to the bluetooth, then switch the audio back to the previous device (my case, the TV) - the audio might come back. Sometimes, the FXS app may actually hang, and then it may crash completely, or it might recover in a minute or so. Now, during the same time, the Youtube video playing in Firefox mostly like freezes (same as if the internet connection would have been cut). Sometimes, if I do a Refresh on the Youtube page and it reloads and I start playing it, I'd say a 50/50 shot, this will bring back the Audio to whatever I have selected in FXS. If that does not bring back the audio, then I would turn off and back on the BT-audio device and if FXSound already has that device selected, a fair shot the audio will be heard on the BL-Headset. I may have to do that off/back on process 2-3 times. On the third time it might connect. Note that if I have a video playing in KMplayer, the video playback either freezes or playback becomes very stuttered and slow in KMPlayer.

One scenario I've noticed that seems to be a reliable way to get the audio to start replaying on the BT-Headset via FXS during these random drops is this: I've got a youtube video and a KMPlayer video playing, I connect my BT-headset, FXS Auto switches to the headset & the audio is dropped. There is a good chance that if I just exit FXS, the audio will suddenly start playing to my BT-headset, just through regular Windows 10 Audio output - not through FXS which I just shut down. Now, if I start FXS back up, and give it a few seconds, the audio resets, and audio is reconnected & enhanced via FXS again, playing through to my BT-headset as expected. But again, this process results are hit or miss. I'd say a 60% chance this will work, 30% it will not, 10% chance the app will just crash again.

Regarding the times when the FXS app crashes. This seemed to be happening quite often at first. This has become less frequent since I've gone through others' suggestions such as removing unused bluetooth devices, doing fresh installs of devices (bluetooth, bluetooth headsets, etc). I have set Windows to capture the crash dumps when the FXS app crashes. I've probably captured well over 30 app crashes over a week or so period of time. I've opened up these dump files, and they are always the same (every single one lists the same information, and, it seems to point to a volumechange procedure or process). I'm posting the text of the latest crash dump file analysis below. As I said, every single crash dump file is exactly the same.

I'm hoping that this information might help the you narrow in on the cause of this. It almost seems that this bug might be the cause of a lot of these issues, so resolving this might resolve a lot of them. I guess, there's a chance as well that something specific on my PC is the root cause of this, I'm not sure. Hope this helps.

Expected behavior
Not to have these application crashes to occur, and to have a much more "seemless" audio output switching in FXS.

Screenshots
Not applicable

System information
-Windows 10
-Latest version of FXS v1.1.20.0
-KMPlayer (x86) - Latest version
-Intel Wireless Bluetooth
-Bluetooth audio devices in particular. I don't use HDMI or hard connected audio devices very much.
-Note: All windows drivers for ALL devices are up to date and all Windows 10 Updates are installed.

** NOTES **
NOTE 1: I've also done multiple uninstalls, re-installs, ensuring the FXS driver was deleted completely from the driver store and reinstalled new, none of which resolved these issues.

NOTE 2: I've noticed references to some issues with HDMI monitors and audio lags, etc. I have run the Latency Monitor, and yes, that app does say that I've got higher than normal latency that might be causing issues. I've worked to get that lowered, but not resolved. However, I don't have issues with audio lagging or glitching WHEN I'm getting audio through FXS. The only "lagging" or "glitching" is most often in KMPlayer and when the audio has been dropped while FXS is running. I'm assuming that KMPlayer is struggling to figure out the proper output audio to use, resulting in it's glitched and often the app will just completely freeze and I'll have to end task it until I can get FXS sorted out and playing audio again.

FXSound Crash Dump File Analysis Text
Microsoft (R) Windows Debugger Version 10.0.19041.685 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\TempMatt\fxsound\CrashDumps\FxSound.exe.24544.dmp]
User Mini Dump File with Full Memory: Only application data is available

Symbol search path is: srv*
Executable search path is:
Windows 10 Version 19045 MP (16 procs) Free x64
Product: WinNt, suite: SingleUserTS Personal
19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Debug session time: Thu Dec 21 11:34:56.000 2023 (UTC - 6:00)
System Uptime: 0 days 17:56:40.572
Process Uptime: 0 days 0:05:35.000
................................................................
........
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(5fe0.2594): Access violation - code c0000005 (first/second chance not available)
For analysis of this file, run !analyze -v
ntdll!NtWaitForMultipleObjects+0x14:
00007ffc`3124db34 c3 ret
0:009> !analyze -v

Exception Analysis

Key Values String 1

Key : AV.Dereference
Value : NullPtr
Key : AV.Fault
Value: Read
Key : Analysis.CPU.Sec
Value: 0
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on INTELONE
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.Sec
Value: 1
Key : Analysis.Memory.CommitPeak.Mb
Value: 151
Key : Analysis.System
Value: CreateObject
Key : Timeline.OS.Boot.DeltaSec
Value: 64600
Key : Timeline.Process.Start.DeltaSec
Value: 335

NTGLOBALFLAG: 0

PROCESS_BAM_CURRENT_THROTTLED: 0

PROCESS_BAM_PREVIOUS_THROTTLED: 0

APPLICATION_VERIFIER_FLAGS: 0

CONTEXT: (.ecxr)
rax=0000000000000000 rbx=00007ff7c168e5a0 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000001 rdi=0000000000000001
rip=00007ff7c13170a4 rsp=0000005ce27ff810 rbp=0000005ce27ffbc8
r8=00007ff7c168ea0c r9=0000005ce27ff190 r10=0000020f291fadc0
r11=0000020f2ec64b10 r12=0000000000000e0d r13=0000020f2e5b7120
r14=0000020f2e9d7690 r15=0000005ce27ff930
iopl=0 nv up ei pl nz na po nc
cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010206
FxSound+0xb70a4:
00007ff7c13170a4 488b01 mov rax,qword ptr [rcx] ds:0000000000000000=????????????????
Resetting default scope

EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 00007ff7c13170a4 (FxSound+0x00000000000b70a4)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000000
Attempt to read from address 0000000000000000

PROCESS_NAME: FxSound.exe

READ_ADDRESS: 0000000000000000

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE_STR: c0000005

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 0000000000000000

STACK_TEXT:
0000005ce27ff810 00007ffc27f0f4d6 : 0000005ce27ff8b8 0000000000000001 0000020f2e885bf0 0000020f2e9d7620 : FxSound+0xb70a4
0000005ce27ff850 00007ffc27f0ea42 : 0000000000000000 0000005ce27ff920 0000000000000000 0000000000000001 : AudioSes!CVolumeChangedEvent::Invoke+0x26
0000005ce27ff880 00007ffc27f0f6a7 : 0000020f00000000 0000005ce27ff930 00007ff7c169ad58 0000000000000001 : AudioSes!CLockedList<ATL::CComPtr,0,0>::ForEachEntry+0xea
0000005ce27ff910 00007ffc27e14d84 : 0000020f2db94160 0000020f2e577630 0000000000000000 0000000000000000 : AudioSes!CAudioEndpointVolume::OnVolumeChangedEvent+0xe7
0000005ce27ff950 00007ffc31220cd9 : 0000020f2db94160 0000020f00000b09 0000020f2e5b7120 0000020f2db94250 : MMDevAPI!CMediaNotifications::OnMediaNotificationWorkerHandler+0x1f4
0000005ce27ffa00 00007ffc312031ba : 0000020f29120af8 0000020f2db66500 0000000000000000 0000020f29120b68 : ntdll!TppSimplepExecuteCallback+0x99
0000005ce27ffa50 00007ffc2f6a7344 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : ntdll!TppWorkerThread+0x68a
0000005ce27ffd50 00007ffc312026b1 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : kernel32!BaseThreadInitThunk+0x14
0000005ce27ffd80 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : ntdll!RtlUserThreadStart+0x21

SYMBOL_NAME: FxSound+b70a4

MODULE_NAME: FxSound

IMAGE_NAME: FxSound.exe

STACK_COMMAND: ~9s ; .ecxr ; kb

FAILURE_BUCKET_ID: NULL_POINTER_READ_c0000005_FxSound.exe!Unknown

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {1545195b-1d08-84c5-33ee-b8f8b95b6c62}

Followup: MachineOwner

Users living in China cannot download the Bonus Presets located at
https://www.fxsound.com/presets
I've translated and reposted a share by one of the most helpful forum regulars, containing all 12 Bonus Presets, as well as 47 others, which can be found at
https://forum.fxsound.com/t/bonus-presets-designed-by-the-lead-audio-engineer-cannot-be-downloaded/1574/10

Forum members Ananda96, Paultx and JMBWITHCATS (among possible others) have requested the addition of one or more options to allow users to change, or customize, the color scheme of the UI and its Visualizer, for aesthetic reasons (i.e., they don't like the current color scheme).
On this topic, it seems worth mentioning that the legacy "DFX" version supported adjustable "skins," which were a popular feature; see:
https://web.archive.org/web/*/skins.fxsound.com*/
(Link shared by forum member Dolmatov)

Forum member mumpi noted that on German/Austrian/Swiss keyboard layouts, the standard 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/

Forum members CDandVinyl and joezim007 have asked about the available Command Line options for FxSound.
In response, @bvijay74 shared this list of available Command Line options:

–preset
–view <1> or <2> for minimal or full view
–output
–language

@bvijay74 also shared the following elaboration on language controls:

By default the OS UI language will be used for FxSound UI.
If the language is not supported, then UI will be loaded in English.
To override the OS language and load FxSound in a different language use the command line option,
FxSound.exe --language=language code
The command line options available are,
Korean
–language=ko
Indonesian
–language=id
Vietnamese
–language=vi
Portuguese
–language=pt
Chinese (Simplified)
–language=zh
Chinese (Traditional)
–language=zh-TW
–language=zh-HK
–language=zh-MO
–language=zh-Hant
For example,
FxSound.exe --language=ko will open FxSound in Korean even if the OS UI is in English.

Note: forum member CDandVinyl discovered the following solution:

I found a solution.
I'm trying to always start the app with my chosen default preset, rather than have FxSound overwrite it on close.
I've managed to achieve his by setting the three config files in
AppData\Roaming\FxSound
to Read Only.
This way, the app will always start with your preferred settings in place and won't overwrite them.

Multiple forum members have reported various different cases of strange and unwanted distortions in their audio after installing FxSound.
While some cases get solved, the causes more often than not remain unknown.
In cases of stuttering/lagging audio, the advice given by forum member caleb59 to install the latest Intel Rapid Storage Technology drivers for Intel users, and to run a scan with LatencyMon for possible latency issues on the machine, proved to be most helpful so far.
Improvement of stutter issues was also reported on other websites after turning off the onboard WiFi or Bluetooth (without disabling the network adapter) or after removing any attached WiFi or Bluetooth dongles.
It also seems worth noting that FxSound's Ambience slider was specifically designed to add a form of echo known as reverb to the audio output.

This feature was initially proposed by @jamesarcher9000:
"The idea here being that if you could, say, set your Playback Device to headphones and Preset to Music when running Spotify, for example. And as you started playing music on Spotify, FxSound would automatically swap the Playback Device and Preset to match what you've set for the Spotify app."
https://forum.fxsound.com/t/option-to-set-default-playback-devices-and-presets-that-automatically-switch-when-using-selected-apps/28
So far, upwards of 13 forum users have voiced similar and/or concurrent requests.
It's worth noting that there will be known conflicts between such an "Auto-Switch" option and the already-existing "Automatically switch to newly connected output device" option located under the General tab of the Settings menu, as well as with the future addition of a "Preferred/Priority Device" option, another extremely popular feature request launched by @NullDev:
https://forum.fxsound.com/t/feature-request-preferred-device/1694

All versions of the FxSound installer from v1.1.14.0 up to v1.1.20.0 came back with one or more Trojan reports, except for v1.1.16.0:
One detection by NANO-Antivirus every time,
and one detection by Rising for v1.1.14.0 and v1.1.15.0 only.
NANO-Antivirus was contacted and confirmed the most recent Trojan report for v1.1.20.0 was a false positive.
Since FxSound is not malicious software, it should be noted that this is not an actual bug on FxSound's behalf, but rather an error on behalf of certain antivirus programs running through VirusTotal.com.

Firstly, it's worth mentioning that thanks to efforts made by @bvijay74, a number of helpful steps have already been taken to improve the experience of FxSound for users with visibility issues, who are combining FxSound with screen readers like NVDA, JAWS, and Windows Narrator:

1. Improved access to the "Save New Preset" dialog box;
2. Manual access to the Effects sliders, the EQ bands and the EQ frequency settings via the TAB key;
3. Manual control of the Effects sliders, the EQ bands and the EQ frequency settings via the arrow keys.

@MesterPerfect reported the following remaining issues while using FxSound v1.1.20.0 with a screen reader:

1. The inability to access any of the buttons on the top right of the UI through the TAB key (the "Donate" link, the Power button, the Settings menu, the Resize arrows, and the x/Close button);
2. The inability to properly use the "Import/Export Presets" dialog box, due to the inability to recognize the names of files and folders;
3. While the ability exists to access all tabs in the Settings menu (General, Help, and Donate), the inability to access any items within the General tab remains (i.e.: the buttons to change the language, as well as the "Automatically switch to newly connected output device," "Hide help tips for audio controls" and "Disable keyboard shortcuts" selection boxes).

Started hearing a consistent crackling sound when running the program, whether or not it's on or off (red button in the menu). It only happens a few seconds after FXsound starts running. When it's not running, the device sound is normal.
I've uninstalled the older version I was using (don't recall which one) and installed the latest one (1.1.20.0). Toggled "Exclusive mode" in the sound settings for all sound devices, as well as changing all formats into 2 channel, 24 bit, 48000 Hz, disabled all enhancements and checked for driver updates. I lowered system volume below 100 for sound devices and tweaked FXsound enhancer and spatial sound settings, no difference there either. There's a post that mentioned a more recent driver date than the one I have.


The 2019 version is the one I have.
I'm using windows 10 with 3.5 mm jack headphones (don't know if that matters or not).

1. "Failed to enumerate objects in the container. Access is denied."
2. "Settings file not found!" (AppData)
3. "Source file not found!" (fxsound1.cab in AppData \ Roaming)
4. "Invalid digital signature." (fxsound1.cab in AppData \ Roaming)

1. Installation fails and the error "Failed to enumerate objects in the container. Access is denied." appears

Description:
"Error Applying Security
An error occurred while applying security information to:
C: \ ProgramData \ FxSound
Failed to enumerate objects in the container. Access is denied."

Reported by:
Forum member fevglikbgjhs
https://forum.fxsound.com/t/settings-file-not-found-when-trying-to-launch-fxsound/1542/12

Possible cause(s):
Elaboration by @bvijay74:
This error means that the user account does not have any access permission to the folder C: \ProgramData\FxSound. The default settings are stored in C: \ProgramData\FxSound during installation and copied to %APPDATA%\FxSound for each user on application launch. So, the user launching the application should have permission to read settings from C: \ProgramData\FxSound.

Possible solution(s):

• Confirm if the logged-in user has permission to the required folder with the command "icacls"
• Log in with a different user account;
• Change the folder permissions;
• Uncheck Read-only under Properties > Attributes;
• Run FxSound as Administrator.

2. Installation seems successful, but launch fails and the error "Settings file not found!" appears (AppData)

Description:

Reported by:
Forum member Plide
https://forum.fxsound.com/t/settings-file-not-found-when-trying-to-launch-fxsound/1542

Possible cause(s):
The absence of permission to access the AppData folder.

Possible solution(s):

• Confirm if the logged-in user has permission to the required folder with the command "icacls"
• Change the folder permissions;
• Copy the file manually - elaboration by @bvijay74:
  Check if the file FxSound.settings file is present in the %APPDATA%\FxSound directory. FxSound installation should normally create the defaults settings file in this directory. If the file is not created due to any permission issue, then you can copy FxSound.settings from %PROGRAMDATA%\FxSound to %APPDATA%\FxSound.
• Run FxSound as Administrator - elaboration by @bvijay74:
  If the FxSound.settings file is not present in %APPDATA%\FxSound, then upon FxSound launch the file gets created. User will get the error only if FxSound does not have the permission to create the file. So, running FxSound as an Administrator is another option to overcome the issue. Subsequent launches can be as standard user, but the settings changes will not get saved. Application launch error can be avoided this way and this does not require any manual changes to the settings file.
• Tutorial for fixing the "Settings file not found!" error on Windows 11 by forum member justinfoHowto:
  https://www.youtube.com/watch?si=iUpOVhBwpGPK7iFX

3. Installation fails and the error "Source file not found!" appears (fxsound1.cab in AppData \ Roaming)

Description:

Reported by:
Forum members JaspaR,
https://forum.fxsound.com/t/cant-install-source-file-not-found-fxsound1-cab-in-roamingappdata/896
LolplayerYT
https://forum.fxsound.com/t/it-says-that-i-need-to-verify-the-files-but-i-dont-know-how-to-fix-it/2412

Possible cause(s):
Usually on old versions of Windows (7, XP) with outdated root certificates. If the root certificates are out of date, then there may be problems checking the valid digital signatures of files.

Possible solution(s):

• Update certificates or system;
• Install from the Microsoft Store;
• Solution shared by @bvijay74:
  Extract the installer by running fxsound_setup.exe /extract
  Once the files are extracted, you can verify the cab file signature by running
  signtool verify /pa fxsound1.cab
  Then run fxsound.x64.msi on 64 bit systems or fxsound.msi on 32 bit systems, to install FxSound.

4. Installation fails and the error "Invalid digital signature." appears (fxsound1.cab in AppData \ Roaming)

Description:
"A file that is required cannot be installed because the cabinet file [...]fxsound1.cab has an invalid digital signature. This may indicate that the cabinet file is corrupt."

Reported by:
Forum members Zipper,
https://forum.fxsound.com/t/corrupt-cab/1613
Ayman,
https://forum.fxsound.com/t/error-when-installing-on-windows-7-x86/1923
salvofogliani
https://forum.fxsound.com/t/installation-problem/1915

Possible cause(s):
Usually on old versions of Windows (7, XP) with outdated root certificates. If the root certificates are out of date, then there may be problems checking the valid digital signatures of files.

Possible solution(s):

• Update certificates or system;
• Install from the Microsoft Store;
• Solution shared by @bvijay74:
  Extract the installer by running fxsound_setup.exe /extract
  Once the files are extracted, you can verify the cab file signature by running
  signtool verify /pa fxsound1.cab
  Then run fxsound.x64.msi on 64 bit systems or fxsound.msi on 32 bit systems, to install FxSound.