Unknown change with sounds? causing sounds to be choppy, sometimes not heard at all

Details
Sounds that previously acted fine in my games now sound choppy. At times, this issue gets to the extent where a sound can barely be heard at all.

  • There may have been a change to sounds that has caused this.
  • This bug was first encountered/reported by someone on 1/26/2024.
  • At the time of it first being reported, I did not experience it personally, but it now seems to have worsened, and I am now experiencing it easily.
  • This bug is experienced both in Roblox Player and Roblox Studio.
  • This bug does not seem to affect mobile clients or the Windows Roblox app. It does not affect console either. This only seems to affect the normal Roblox Player on computers.

Reproduction Steps
Set a sound’s TimePosition on a loop (used to act fine, now it sounds choppy)

Expected Results
Sounds should play when they should and should not sound choppy

Actual Results
Sounds are now choppy, and sometimes cannot even be heard

Screenshots / Videos
image
^ When bug was first reported (1/26/2024)
robloxapp-20240211-2051279.wmv (1.7 MB)
^ Choppy sound
https://cdn.discordapp.com/attachments/794636708946771979/1211351549901537330/2024-02-25_11-20-28.mp4?ex=65ede20b&is=65db6d0b&hm=9b3ce37692263cb0bc8931ce61897a1dcc86b3930f6880bc21644cddbe0b4193&
^ Sound cannot be heard at all


^ Choppy sound as experienced in Roblox Studio

^ A snippet of my script used to set the sound’s TimePosition. Note that sounds were fine using this method up until the sounds started sounding choppy.

Note: Previously, I had a similar issue with SPECIFIC sounds being choppy using TimePosition. On the other hand, all sounds now seem to be affected.

1 Like

We’ve filed a ticket into our internal database for this issue and will start investigating, we will update you when we have further information.

Thanks for flagging!

3 Likes

Is this the reason for today’s extended audio moderation times? Several of my audio submissions have been awaiting approval for over three hours.

1 Like

I don’t think so. This bug isn’t from today. I did notice one of my sounds was never approved today, though.

1 Like

Update: this bug does not seem to affect mobile clients or the Windows Roblox app. This only seems to affect the normal Roblox Player on computers. Not sure about console

1 Like

Update: it does not affect console either. Therefore, this bug only applies to the Roblox Player for computer.

1 Like

This is just a shot in the dark but could you change the wait(0.1) to just task.wait()? This is most likely a Roblox problem but I’m wondering if the refresh rate changes anything about the choppiness.

Either way is virtually ineffective, as shown here:

1 Like

I meant to say to put task.wait() with no number inside, like literally task.wait()

Just wanted to see if it would improve it or not.

Also virtually ineffective

1 Like

I don’t think this would change anything since I believe the bug has to do with sounds themselves and not how wait works. Otherwise, it would affect things other than sounds.

It seems as though this bug has now been patched on this week’s patch update.

https://cdn.discordapp.com/attachments/820658752168001559/1215109513896796250/2024-03-06_20-25-51.mp4?ex=65fb8deb&is=65e918eb&hm=a436a83ba1994d364c966267b1c7a32f0c8c65b4c462f506f28337f82bd51658&

1 Like

It only seems to be partially fixed. Quoted from a friend, they state:

Not everything is fixed
I did a test yesterday, old propulsion sounds have started to sound fine, however if you make a new one the effect will persist
Which [is] weird af
Because for me my alstom was sounding fine but the [siemens] wasn’t, then the [siemens] sounded fine but then the alstom [broke]
So idk what was up with that
I do know that the bug lingers while running in [studio] but not in roblox client

So from what I’m understanding, it’s only persisted to new audios instead?

That seems what I thought because I heard something broken on one game that also uses the TimePosition based script.

1 Like

I’m not actually sure right now. I’m trying to verify this. It is very odd.

I’m currently still trying to verify if this is still happening or not. Stay tuned.

This bug has likely been fixed. I’ll be closing it now.

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