New beta release v.1.1.31.0

A new beta release with the fix for the unhandled exception when upgrading from a previous release is fixed. The new release is available at https://github.com/fxsound2/fxsound-app/releases/download/beta/fxsound_setup.exe

Please install this version and give it a try.

Thanks for your patience and sorry for the trouble caused by the exception in the previous release.

7 Likes

Thank you very much for the new version, I have a question about the parameters, specifically how to assign new values to the keys like Clarity, Ambience, Surround Sound, Dynamic Boost, Bass Boost.

[Preset Information]
CLASS1 : Effect Type
Preset Name: prueba3
FxSound Version: 9

[General Settings]
0: Double Params Flag
1: Total number of elements

[Main Parameters]
1: Main 0
2: Main 1
0: Main 2
3: Main 3
4: Main 4
5: Main 5

# [EQUIVALENCIES]
# 0: 0
# 1: 13
# 2: 25
# 3: 38
# 4: 51
# 5: 64
# 6: 76
# 7: 89
# 8: 102
# 9: 115
# 10: 127

[Element Parameters]
0: Element Number
   0: Param 0
   0: Param 1
   0: Param 2
   0: Param 3
   0: Param 4
   0: Param 5
   0: Param 6

[Application Dependent Data]
7: Number of Application Dependent Integers
0: Number of Application Dependent Reals
0: Number of Application Dependent Strings

[Integer Parameters]
1: Integer[0]
1: Integer[1]
0: Integer[2]
1: Integer[3]
1: Integer[4]
0: Integer[5]
2: Integer[6]

[Equalizer Settings]
10: Number of EQ Bands
1: On/Off Flag

[Equalizer Frequencies and Gains]
Band 1
   62.5: CF
   5.03937: Boost/Cut
Band 2
   95.23: CF
   12: Boost/Cut
Band 3
   179.44: CF
   12: Boost/Cut
Band 4
   342.4: CF
   12: Boost/Cut
Band 5
   630: CF
   12: Boost/Cut
Band 6
   1250: CF
   12: Boost/Cut
Band 7
   2700: CF
   12: Boost/Cut
Band 8
   5300: CF
   12: Boost/Cut
Band 9
   7500: CF
   12: Boost/Cut
Band 10
   13000: CF
   12: Boost/Cut

In the EQUIVALENCIES section, I try to give values from 1 to 10 to the current values of [Main parameters], 1:13, 2:25, 3:38 and so on.

I share the code corresponding to a test preset (.fac file) with a proposed data structure to make it more user friendly. I would like to be able to edit the values of Clarity, Ambient, etc. with values from 1 to 10.

Thank you!

1 Like

tested v1.1.31.0 working fine just like before dont notice unusual

windows 11 iot ltsc
build 2600.33.23

usage and ui seem ok to me thanks

1 Like

does not collapse into the taskbar by clicking on the icon (but it collapses normally in the tray.)

1 Like

It is not updated unless you delete the old version.shows errors

Yes, to collapse to task bar, use the minimise button.

Can you please elaborate on this issue?

Wish I could say it worked for me. Win 11 latest updates. Removed old app with Geek program. Ran install as administrator. Flashes same unhandled exception and disappears. Try to run program Icon on desktop and program launches, error shows, then all disappears. No joy here. Loved your program for years. Thank you!

BTW the link at github you listed did not work for me. Had to use.

It was version 1.1.31.0

What is unclear? I had 1.1.30, I downloaded 1.1.31 and it didn’t install on top of the old one. I had to delete 1.1.30 and then install 1.1.31.

The beta is promoted to latest release. So, you can download it from fxsound website also.

2 Likes

Uninstalled v.1.1.31.0 using geek program. Also went into registry and deleted all traces of “fxsound”. Reinstalled and still have exception error.

Could I safely run a previous version of FXSound before the exception issue began? I looked in GitHub and did not find any older version. Please advise.
Thank you,

If you are still getting an exception, can you please share the log file found at %APPDATA%\FxSound\fxsound.log

You can find the previous releases in GitHub at,
Releases · fxsound2/fxsound-app


FxSound logs
Log started: 13 Mar 2025 6:08:31pm

v1.1.31.0
Windows 10
x64

Unhandled exception
Exception code: 0xC0000005
Exception flags: 0x0
Exception address: 0x00007FF72EA802C0

UnhandledExceptionFilter at 0x7FFB8A6E1620
memcpy at 0x7FFB8CDD6F40
_C_specific_handler at 0x7FFB8CDBF770
_chkstk at 0x7FFB8CDD5350
RtlFindCharInUnicodeString at 0x7FFB8CD4DDF0
KiUserExceptionDispatcher at 0x7FFB8CDD4450
BaseThreadInitThunk at 0x7FFB8AE82580
RtlUserThreadStart at 0x7FFB8CD8AF10

1 Like

Thanks for sharing the logs. I will analyze the cause of this crash.
Did you try rebooting after the installation and launching FxSound?

1 Like

Yes, and no joy. Also tried previous versions and they would not run because of other reasons. No errors, just did not run completely.

It seems like the exception that you are getting is different from most others got which was resolved in the latest version.
Will it be possible for you to create a memory dump from the crashing application?
When you get the exception message, don’t close the message box. Instead go to Task Manager, right-click on FxSound process and select Create memory dump file

FXSound and the exception box both disappear before I can click on the close box. The FXSound app does not appear in the any processes within task manager. Strangely enough the Sound Icon shows FXSound as the default sound app. There is an FXSound desktop icon left. When I click on it all shows briefly again then disappears as well. NO FXSound process running?

Also, I installed 1.1.31.0 on my Win10 laptop. Never had FXSound installed before. All works perfectly.

1 Like

does not collapse into the taskbar by clicking on the icon (but it collapses normally in the tray.)
will it be fixed?

thanks a lot for fixing this.

There’s still some weird behaviour:
FXSound ALWAYS starts at the middle of my screen, when i move it back to my liked position down left side, i figured out when i’m not using my PC for roundabout 2 hours (is my monitor timeout) it jumps back to the middle of the screen.
Could you make it sticky same as Rainmeter works??
(no clickthrough no accidently moving of the app)

may be add some transparency and color change…
i asked this before, hope will never die.

1 Like