BETA TESTING SOUND MODULE

[Buford]

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?

I run all announcements from the LS Panel speakers, A/C, Avionics, PTU from different speakers each and Elec even from an independent instance of Sound.exe on another PC.
Loosing that possibility would be a drawback for me.
By sure to group for example the announcements coming from the same speaker in the real aircraft makes sense, but in past it had not been that complicated to highlight them all and assign them together.

[jeehell]

Well I will see if it's not too complex to go back to individual settings.
But I really believe it's overkill. PTU can NOT be heard in real life from the flight deck. Same as APU, except when front doors or windows are open and bleed is off. You won't be able to differentiate A/C noise and avionics unless you put your ear into an A/C outlets (one of the 10 or so in the cockpit...)...

[Buford]

Yes, I know, it’s more for playing around. I love the barking dog from the backside…one is used to from the PAX perspective

[jeehell]

I released the beta sound module for 61.10.1
https://www.jeehell.org/Sound 61.10.1.zip

It does allow individual sound setting, multiple selection in the list for a quick setup, and it still has the sound group feature for fast easy setup for those with only a couple soundcards...

[balu69]

Hello JeanLuc
Thank you for the new version. So far everything is fine. The sound is complete again and the assignment works perfectly.

[LH320]

When I press the EMER CALL switch, I receive an error message:



The switch is assigned correctly. Is the assignment of the sound file incorrect?

[jeehell]

@LH320: I just fixed that for a soon coming release.

For everyone else, do you have any kind of issues with this new sound module? performance?
Did you notice any improvement? (most notable one would be "crackling" when some ambient looping sounds are playing like air cond, avionics ventilation,...)

[stefangr]

For me the new sound module is working fine, no longer delays of several seconds. Looking good.

Just one thing which makes me wonder - not sure if I am doing wrong or not: I never hear the TripleClick.wav after disconnecting the A/P. My normal procedure on approach / final would be:

- AP 1 is on
- Activate LOC / capture LOC
- Activate APP + AP2
- Capture G/S
- Disconnect A/P

Then I hear cavalry charge.wav, but not TripleClick.wav afterwards. Both sounds are active in the sound options with "Main speaker" and volume 100. I disconnect A/P by pressing the joystick button twice. Button is assigned in FMGS_Config.exe to "CPT APTO" (as push event as well as release event).

Thanks
Stefan

[LH320]

For me, the new allocation of the sound output is a clear improvement. I had problems with the standard version. I could not separate two sound outputs (cabin and outside). With the new sound module it works. I have not yet been able to determine the exact cause.

There is a sound "autobrake off" and a corresponding ECAM message been available. Maybe in a future release also?

I confirm the missing TripleClick.wav

[jeehell]

...
Just one thing which makes me wonder - not sure if I am doing wrong or not: I never hear the TripleClick.wav after disconnecting the A/P.
...

I have made a fix in the new sound module which should do it.
However I believe the "legacy" sound module is probably prone to that one as well...

[jeehell]

An important message on this beta sound module thread.
Next version of this beta sound module will include a very important feature: engine sounds.
You may wonder "why bother with playing your own engine sounds when P3D can do it?" so here are a few points:
1. For some time already, the software has it's own engine model (thrust, fuel flow, etc). It's all done outside P3D, thrust is just reinjected into P3D for the aerodynamics
2. P3D engine has had it's share of sound issues (sound fading out without notice, some looping sounds end up bad like engine starter, flaps)
3. Future of the software and P3D: this is important to me, even if people believe I forgot about MSFS2020/2024, that is actually not true, and I/we need a coherent product for the future, including sounds. Sound is one of (not the biggest sorry... and those are not yet 100% done...) blocking aspects to go with MSFS right now.

That being said, I have acquired a CFM56 sound set licence from TSS. I am allowed to redistribute it. For obvious reasons, the set is encrypted and is totally unusable outside of my software. The set will be bundled with my software at some point (and at least with the new beta sound module of course).
With some work, I am now able to play the wav files in the same manner as P3D does it.
This means the new version should give at least the same feeling as the P3D one for people using a normal CFM sound set from TSS.
I have taken the opportunity to fix some things such as starter sound (no more looping if you do a dry/wet cranking). I will need to work on the flaps at some point.

What does it mean for people who don't use TSS sounds?
in theory, any P3D sound set can be used with the system. The future (and testing on your part) will tell and help me adapt the code of course.

For new comers, the software will be fully inclusive of all what's needed now.

One very important point, as I know some of you have particular "needs":
I have NOT modeled exterior view sounds. As of now, the only sounds you will hear are from the cockpit position.
Is it something blocking for you? Can you live without exterior view sounds?
In theory it should be possible to code the outside view sounds as well, but that requires quite some code to get camera position in order to modulate the sounds accordingly.


So please give me your thoughts here...

[LH320]

That's good news! Now I also understand (I also use TSS, by the way) why I always had this sound dropout when starting the engine. For me, the exterior view sound is not necessary - I don't do a walkaround either . I only simulate (with GSX) the sound from the outside that I can hear in the cockpit, e.g. that of the tug. For this reason, I can do without the exterior view sound. But that's just my opinion.

[Buford]

First of all: THX a lot for the update related to the future of the software!
Regarding outside sounds I could well live without them, while others may have other preferences.
Using it with MSFS with the mod (and of course with all its compromises) my experience is, the default outside sound, if needed, is not that ugly that one could not accept it for just having a look from outside, but for sure that would also be related to the base model - which in MSFS until now is a NEO with LEAP engines - used in future.

[balu69]

I would also like to say a big thank you for the further development.
I personally like to switch to the outside view during the flight and look at the scenery and clouds from this perspective. The sound is not essential. Nevertheless, it is nice when the engines can be heard.

[Capt. PERO]

I would also like to say a big thank you for the further development.
I personally like to switch to the outside view during the flight and look at the scenery and clouds from this perspective. The sound is not essential. Nevertheless, it is nice when the engines can be heard.

100% agree.