VOGONS

Common searches


indirect sound

Topic actions

Reply 160 of 168, by KainXVIII

User metadata
Rank Member
Rank
Member
lowenz wrote:
There is :) […]
Show full quote

There is 😀

https://www.indirectsound.com/downloads.html

Version 0.20 — 2019-09-21
Changes since the previous version:

Fix how Doppler Factor is used
This fixes the bad engine revving sounds in Drome Racers
This also correctly constrains the amount of frequency change that can happen as a result of Doppler calculations
Fix buffer description copies for old versions of DirectSound
IndirectSound had assumed that buffer descriptions were always the same size as DirectSound 7 or later

Ah, thanks!

Reply 162 of 168, by Discrete_BOB_058

User metadata
Rank Member
Rank
Member
KainXVIII wrote on 2019-10-02, 09:26:
lowenz wrote:
There is :) […]
Show full quote

There is 😀

https://www.indirectsound.com/downloads.html

Version 0.20 — 2019-09-21
Changes since the previous version:

Fix how Doppler Factor is used
This fixes the bad engine revving sounds in Drome Racers
This also correctly constrains the amount of frequency change that can happen as a result of Doppler calculations
Fix buffer description copies for old versions of DirectSound
IndirectSound had assumed that buffer descriptions were always the same size as DirectSound 7 or later

Ah, thanks!

Is this a DSound3D emulator for modern Windows OS? I don't know anything about
this software?

YouTube Channel:
DEADHistory Walkthroughs

PC SPECS:-
CPU: AMD Ryzen 5 1600
GPU: ZOTAC NVIDIA GeForce GTX 1050Ti OC Edition
RAM: 8GB*2 Corsair Vengeance LPX DDR4 2400MHz
Motherboard: Gigabyte Aorus B450M
PSU: Corsair VX550
Sound Card: Realtek ALC892

Reply 164 of 168, by UCyborg

User metadata
Rank Member
Rank
Member
jonpol wrote on 2019-01-14, 17:24:
lowenz wrote on 2019-01-14, 12:24:

The registry mod procedure ( https://www.indirectsound.com/registryIssues.html ) is still needed?

Yes, that is still needed for those games that create the DirectSound interface using COM functions. Luckily this is a small percentage; most games just use the DirectSound functions.

There is another way.

Edit: Oops, never mind, I posted too fast. This is for different use case. Don't try it, it'll cause circular dependency.

Arthur Schopenhauer wrote:

A man can be himself only so long as he is alone; and if he does not love solitude, he will not love freedom; for it is only when he is alone that he is really free.

Reply 165 of 168, by jonpol

User metadata
Rank Newbie
Rank
Newbie
UCyborg wrote on 2020-06-20, 18:34:
jonpol wrote on 2019-01-14, 17:24:
lowenz wrote on 2019-01-14, 12:24:

The registry mod procedure ( https://www.indirectsound.com/registryIssues.html ) is still needed?

Yes, that is still needed for those games that create the DirectSound interface using COM functions. Luckily this is a small percentage; most games just use the DirectSound functions.

There is another way.

Edit: Oops, never mind, I posted too fast. This is for different use case. Don't try it, it'll cause circular dependency.

Interesting. But yeah, that wouldn't work for IndirectSound because I still load the real dsound.dll behind the scenes. It might work for DSOAL (not sure if it uses the real dsound.dll or not), but that would also change your system's behavior for every game, which seems a bit drastic. I think it's probably good to be able to try different dsound.dlls for troubleshooting purposes, even if it's slightly annoying to have to manually copy them. (I guess something like ALchemy's installer is the user-friendly solution to that.)

Reply 167 of 168, by UCyborg

User metadata
Rank Member
Rank
Member
jonpol wrote on 2020-06-20, 19:05:

but that would also change your system's behavior for every game

Actually, you still have to put game.exe.local file in its folder for the registry setting to be effective.

lowenz wrote on 2020-06-20, 19:39:

You can build OpenAL Soft (on which DSOAL is based) with WASAPI support only.
I do this way to avoid any possible problem 😁

Seems like an overkill since there's a config option for that, see here. You could set:

drivers = -dsound,

or

drivers = wasapi
Arthur Schopenhauer wrote:

A man can be himself only so long as he is alone; and if he does not love solitude, he will not love freedom; for it is only when he is alone that he is really free.

Reply 168 of 168, by jonpol

User metadata
Rank Newbie
Rank
Newbie
UCyborg wrote on 2020-06-25, 08:38:
jonpol wrote on 2020-06-20, 19:05:

but that would also change your system's behavior for every game

Actually, you still have to put game.exe.local file in its folder for the registry setting to be effective.

Oh, ok, I guess I didn't read the description carefully enough. In that case I think I'd rather just copy the dsound.dll around anyway, but it's nice there's another option for DSOAL users if they'd prefer that.

I also just discovered that the registry settings that I had made in HKEY_CURRENT_USER to make IndirectSound work on my main machine were no longer there, presumably removed by some Windows Update. I had hoped that Windows would leave them alone (as opposed to changes made in HKEY_LOCAL_MACHINE, which involve modifying existing entries and which were known to get reset to Windows defaults by updates), but that appears to not be the case 🙁
Maybe this was already known, but it was new to me. I guess I should modify my instructions to make it clear that either method will have to be repeated periodically. It is more annoying to have to enter in new keys (what I recommend doing in HKEY_CURRENT_USER) than modifying existing ones (the alternate method in HKEY_LOCAL_MACHINE), but I guess I still prefer modfying HKEY_CURRENT_USER for safety reasons because you can always just delete the keys and get back to the default Windows behavior. I guess I could also supply a REG file to automate the process, but I don't think I'd want the liability if someone's registry got messed up (my existing instructions are intentionally not very detailed for this exact reason).

UCyborg, I don't suppose you know of any way of preventing Windows from removing entries? 😀