3D Sound System - Realistic frequency dampening

Resources Community Resources
#9

Not to burst your bubble, but the engine is already capable of handling this.

Attached is a sample file of a sound rotating around the origin with Rolloff settings in SoundService set to exaggerate the effect. (Careful the sound may be a bit loud on some audio devices)
EngineAttenuation.rbxl (15.5 KB)

What does your module do that isn’t already being done passively by Roblox?

7 Likes
#10

… I was told it didn’t. Wow. Thanks for letting me know!

Regardless, I suppose this could still be used to quickly and easily handle sound creation at specific positions?

Edit:

4 Likes
#11

Funny. In any case this sounds like it was a fun exercise

6 Likes
#12

It was! I did this to procrastinate my actual work cuz I got stuck on a bug and didn’t want to deal with it anymore :stuck_out_tongue_closed_eyes:

5 Likes
#13

I’m not sure why, but boatbomber’s seems more realistic and accurate. It could just be because the sound in his place is playing more frequently.

2 Likes
#14

Upon further testing with @sidnad10, we have determined that Rolloff handles based on distance, not angle relative to the camera LookVector. It simply makes sounds quieter the farther away they are. The fact that you think it is “behind” you is simply your brain interpreting it’s path to predict that it’s circling “around” you. This module is made to actually simulate how your ears interpret directional sounds.

You can prove this by having the object switch between a few studs in front and a few studs behind at random intervals. Close your eyes, and you’ll find yourself unable to tell when it is switching. Here, feel free to try it.
BlindTest.rbxl (18.7 KB)

Whereas the same test, but using the module, shows clear difference between front and back.
BlindTestModule.rbxl (20.2 KB)

This module is useful!

7 Likes
Audio not directional
#15

Yup! This reply explains why:

3 Likes
#16

Update:

After more testing, I’ve found that doing

Emitter.Sound.EqualizerSoundEffect.HighGain = -(-25 * cos(acos(dot(cf(Camera.CFrame.Position,v3(Camera.CFrame.LookVector.X,Camera.CFrame.Position.Y,Camera.CFrame.LookVector.Z)).LookVector.Unit,v3(Emitter.WorldPosition.Unit.X,Camera.CFrame.Position.Y,Emitter.WorldPosition.Unit.Z)))/pi * (pi / 2)) + 25)

for the HighGain calculation provides a much nicer and more realistic result.

The original edition had it dampen linearly, which meant that the sides were half-dampened.
This is an inSine ease, so it dampens more behind you than to the sides.

Files have been updated with this, and I recommend anyone who has already implemented this to insert the new file. API hasn’t changed, so you can just replace the module without any issues.

6 Likes
#17

I can’t hear the difference between BlindTest vs BlindTestModule and your game vs EngineAttenuation. Do you have any other examples that might be clearer?

3 Likes
#18

I suppose if you replace the SoundID with the ID of a sound with more high frequencies in it, the reduction of high frequency would be more apparent.

2 Likes
#19

It would be kind of cool to see roll off used with this!

2 Likes
#20

I would suggest also adding an function to attach an audio to this, so it can support all audios rather than just audios created by the script. I am going to modify the code to fit my use by doing this and if people are interested, I can link it here.

3 Likes
#21

I’d love for you to share your changes!

1 Like
#22

Here’s the code I used (Posted directly after :Create() function)

function SoundSystem:Attach(sound)
	local Equalizer	= sound:FindFirstChildOfClass("EqualizerSoundEffect") or newInst("EqualizerSoundEffect")
	Equalizer.LowGain	= 0
	Equalizer.MidGain	= 0
	Equalizer.HighGain	= 0
	Equalizer.Parent = sound
	local tbl = {Sound = sound}
	CurrentObjects[tbl]	= true
	spawn(function()
		repeat wait() until not sound:IsDescendantOf(workspace)
		
		CurrentObjects[tbl] = nil
	end)
end

Edit: I would like to add that this has not been tested, and will be pending testing until I have properly incorporated my Vehicle Physics into the file with this.

1 Like
#23

I don’t have access to my PC for a few days, but I plan on adding this feature to the master branch.

I do plan on rewriting the code, but the API is nice. I just think creating a thread to do a repeat wait() until is not the best way to accomplish that.

1 Like
#24

I made this for a StreamingEnabled environment, so it works pretty well for me. I use this quite often without seeing any sort of memory issues or anything related to that. I suppose you could do wait(1) if you are concerned.

1 Like
#25

Wait a second, this won’t work. It’ll call Emitter.WorldPosition to do the angle math, which would return nil instead of a Vector3.

2 Likes
#26

as said before, I have not yet tested it. I can fix that as soon as I have the vehicles properly setup in this file.

2 Likes
#27

I haven’t tested it, but this may break if someone uses the system and changes a user’s listener - although I’m not sure many people use it, it can be used to change where a user ‘hears’ from.

local listenerType, listener = game:GetService("SoundService"):GetListener()

You seem to use the angle to the user’s camera to do the effects, so if the player is listening from somewhere else, it won’t work correctly. (unless you’ve changed something since I’ve last looked.)

2 Likes
#28

I didn’t know that was a thing. When I have a chance, I’ll fiddle with it until that is supported. Thanks for letting me know!

1 Like