Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Random loud audio crackle upon clicking "View Results" in playlists #20017

Closed
TomG16 opened this issue Aug 29, 2022 · 3 comments · Fixed by #20025
Closed

Random loud audio crackle upon clicking "View Results" in playlists #20017

TomG16 opened this issue Aug 29, 2022 · 3 comments · Fixed by #20025
Assignees

Comments

@TomG16
Copy link

TomG16 commented Aug 29, 2022

Type

Game behaviour

Bug description

A varying in loudness click/crackle can be heard upon clicking the "View Results" button of a song in playlists.

-It varies between to a loud click to sometimes not even noticeable. Also happens with music/effects ON

Screenshots or videos

cracklebuglazer.mp4

Version

2022.821.0

Logs

runtime.log
network.log
updater.log
performance.log
database.log
legacy-ipc.log

@smoogipoo
Copy link
Contributor

Sounds like the sample is potentially played with 100% volume for one frame or something.

@peppy
Copy link
Member

peppy commented Aug 30, 2022

Looks to be related to DrawableAudioMixer as used here:

private DrawableAudioMixer mixer;

Changing this to an AudioContainer fixes the issue.

I'll take a brief journey to see if I can figure the underlying cause, but I don't actually think a mixer is appropriate or required here.

@peppy
Copy link
Member

peppy commented Aug 30, 2022

This happens without any sample playback. Just having the CreateMixer calls is enough.

JetBrains.Rider.2022-08-30.at.06.17.12.mp4

Note the volume spikes here. This is with game volume set to 0% and sample playback disabled (as shown top-left).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants