Audio playback loudness is always zero, even if the asset is playable

Help and Feedback Art Design Support
#1

Before you tell me to post this in bug reports, I don’t have the ability to do so.
The problem here is that I try to play a audio in game, but it never plays. Even though I can run the preview of the audio just fine, but then I noticed that the playbackLoudness property is always 0. Which for some reason, happens to ALL of the audios that I insert as of recent. Making audios UNUSABLE for me.
Example of preview working with playbackLoudness set to 0.

If anyone has a solution to this PLEASE tell me.

#2

Are you actually fetching PlaybackLoudness in a script? It tends to read as 0 in Studio’s property window.

#3

I just ran it in a script, it still returned 0. Also other sounds do have the correct playbackLoudness.

#4

Are you experiencing this on any public audio? If so, could you provide the ID?

#5

No, it is with all newly inserted audio in studio. Public or not, it just won’t function correctly.

#6

I can only get a client to read non-zero PlaybackLoudness and Changed events don’t fire for it at all. You said other sounds do have correct PlaybackLoudness. Are these sounds being checked by a regular Script with RunContext not set to Client? << This sentence is not advising that you change how you read the property, I just want to know if you’re able to do it on the server side.

#7

No, the sounds are being played on the server.

#8

Is this property showing a number that is not zero in that same script for any audio that you have?

#9

No, any script I run it in shows a playbackloudness of 0.

#10

It doesn’t seem like server Scripts can read PlaybackLoudness. Servers don’t need to hear or process audio for loudness, they only replicate the other properties for client usage. Only clients can effectively use that property. I imagine that’s because it’d be a bit unnecessary to process every playing sound on the server and replicate it when it’s not being used for anything.

#11

Actually running it on the client works for some weird reason, it wasn’t working before. But atleast I have a solution now. Thanks for helping.

#12

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.