JeeHell FMGS forums

Hello

I am doing some application refactoring in the sound module, in order to eliminate some problems with it (sound artifacts, heavy CPU usage, settings saving/loading).
The beta version of the sound app can be downloaded from here:
https://www.jeehell.org/Sound 61.10.1.zip
It is contained in a zip file which you must put in c:\A320FMGS\Sound folder on the PC where your sound application is used.
It works only with latest version released today(61.10.1).

The sound settings are now stored in an XML file which should be correctly read when some updates are introduced.

As for the sound cards, you will have the option to define 4 devices:
1. main speakers (basically the FWC/TCAS/GPWS output...)
2. Ambient Cockpit sounds (relays, air cond, avionics, ...)
3. Ambient Exterior (not that many but the external HORN, gear and gear doors)
4. Ambient Cabin (only cabin chimes for now)

You can of course assign the same sound card to each of these four "sound groups", if you only have a limited number of outputs.
If you use USB outputs with the same name, windows allows you to change the names of your devices:
https://www.majorgeeks.com/content/page ... vices.html

Let me know in this thread all your feedback on this beta sound app.

Hello JL!
The link does not work!
Best regards
peter

fixed

Hello JL!
I got this message and you see whats i the sound directory.
Best regards
peter

sorry no attachment possible!
Best regards
peter

That is strange it should be possible. Maybe the picture size is too big, try downsizing.

Hi Jena Luc
When I open the sound.exe it I get the error message that it cannot open the file c:\a320fmgs\sound\sounds\crc.wav.
This is because I don't have my installation on the C drive.
If I create the folder structure in C and copy the crc.wav file in, sound.exe starts without any problems

but so I hear the noises twice.
If I remove the one crc.wav file in my installation folder, I get the error message again, but this time with the path to my installation folder

I've updated the file in https://www.jeehell.org/Sound 60.0.6.zip it should get rid of the error message on start.

the error message no longer appears.
The link in your latest post is not complete, but the one in the first posting works.
What I still have is that the sound is not clear. it's like the sound is played twice twice, slightly delayed.
What I also had with the front versions was that the sound module kept disappearing. I click on it, make a change and after about 2 seconds. it disappears again and I have to click on it again in the taskbar

You don't have the old application running alongside?
What kind of sound cards do you use?
Do you have P3D sounds on the same sound card?

Hello JL!
Now it works!
best regards
peter

I connected the P3D sound to the soundcard on the mainboard.
I have all sounds from the A320 FMGS via speakers that are connected to the monitor, and this is connected to the FMGS computer via an HDMI cable.
It's clearly audible when I do the CVR test or turn seat belts on and off
To test, I put all A320 FMGS sounds on the main soundcard and this is also audible

pe_martin, do you have any issues like hearing the sounds twice?

Hello JH no!
I have serveral sound devices.
Best regards
peter

balu69 wrote: ↑Tue Dec 19, 2023 6:38 pm the error message no longer appears.
The link in your latest post is not complete, but the one in the first posting works.
What I still have is that the sound is not clear. it's like the sound is played twice twice, slightly delayed.
What I also had with the front versions was that the sound module kept disappearing. I click on it, make a change and after about 2 seconds. it disappears again and I have to click on it again in the taskbar

Hello Jean Luc,
since yesterday i tested the Version 60.0.6 of the sound.exe and i can confirm the same as balu69. the sound is playing twice, i think, and the modul goes to the taskbar after two seconds. only when the P3d is not running i can make changes an the modul stays there.

I hear the BELL and HORN sound when I press the CALL MECH switch on the overhead.
The assignment does not seem to be clear.

The bell sound is a big it dates from a time when I did not have the HORN sound. That will be corrected.
Do you have dual sounds for the other sounds?

Hello JL,
I've gone back to the old sound.exe because I can assign my sound cards with the individual sounds better there and am not tied to predefined ranges.
an xml file for the old sound.exe in which you define the sounds and sound cards would be great. and of course the xml file should not be overwritten during an update.

jeehell wrote: ↑Sat Jan 06, 2024 10:17 pm The bell sound is a big it dates from a time when I did not have the HORN sound. That will be corrected.
Do you have dual sounds for the other sounds?

No. The other sounds sems to be ok.

Hi,

I made rather big changes in this BETA sound module (in the background).
https://www.jeehell.org/Sound 61.10.0.zip

Please let me know if it is more stable for you, if you have any troubles, and also CPU usage you get.

Hi JeanLuc
Thank you for continuing to develop the A320.
The sound is better now and no longer has an echo.
I have the feeling that SeatBells and NoSmoking used to piiing and with the new version it's more like png.
CPU says about 0.46%.
In general, I like the previous version better, where I can define the output for each individual sound myself.
If I could sort the options by the "Name" or "Sound Device" column, it would make searching or setting up easier.

To be honest, I don't really see why defining sound one by one is better, because I don't see any reasons to play the FWC/GPWS/TCAS sounds on different devices each?
That change is to actually make it way easier: all sounds which come from the same physical speaker in the real aircraft have their own "group". so if you change your sound card for main speakers then you only need to make ONE change for the group instead of the 50+ sounds of FWC/GPWS/TCAS?
Same for atmosphere sounds (ambient), you have CKPT, CABIN and EXTERIOR, do you really have more speakers than that? and I don't see why you'd play the AIRCOND sound from the EXT device or the gear aero sound from the CABIN speaker?

On another note, I believe I found the issue with the signs (and probably other short sounds) will be fixed.

you are certainly right with your argument and your version makes sense.
Yes, the calls (e.g. 2000) are not pronounced in full (tou tousa...). But I assume that you have already fixed this.