Re: Audio issues using Discord and 2042 after S6 update.

---

@SP0000kS wrote:

Its a mic plug on your interface? or a mic through a webcam?

1024 is really big buffersize yes, at this point you have a lot of latency.

512 should be better as your cpu will work a bit more. But maybe not enough for BF for some.

I'm pretty sure i could run bf at 128 sample before.

For the one having the problem through windows driver, i suppose if they install asio4all they will be able to manage the buffer size.

But it's deeply not your job to fix bug like this. Im totally agree with you.

---

Yes it's a mic going through the interface... higher buffers seems to distort the audio from it, at least as far as Discord is concerned. The default buffer is 128, that's what I was at before this issue that we have.

Really not fun for people who like to stream.. as they all use mic through an interface.

Feel like i can go to 256/48khz, it should be better for your mic latency.

At 192 it crash the sound after like less than 5min of playing.

---

@SP0000kS wrote:

Really not fun for people who like to stream.. as they all use mic through an interface.

Feel like i can go to 256/48khz, it should be better for your mic latency.

At 192 it crash the sound after like less than 5min of playing.

---

Update to this: I skipped testing buffer size 512 because discord friends said my mic was still sounding bad... so I went to 256 buffer size tonight and played for about 2-3 hours with no audio issues from either ingoing or outgoing audio.

So it looks like at least Scarletts set to 256 buffer works for now. I will continue testing lower buffer until the problem happens and report which ones work for me and don't. Next time I can play I'll test 192, the next buffer lower, and see how that works and report back.

---

@JD_W0LF wrote:

---

@SP0000kS wrote:

Really not fun for people who like to stream.. as they all use mic through an interface.

Feel like i can go to 256/48khz, it should be better for your mic latency.

At 192 it crash the sound after like less than 5min of playing.

---

Update to this: I skipped testing buffer size 512 because discord friends said my mic was still sounding bad... so I went to 256 buffer size tonight and played for about 2-3 hours with no audio issues from either ingoing or outgoing audio.

So it looks like at least Scarletts set to 256 buffer works for now. I will continue testing lower buffer until the problem happens and report which ones work for me and don't. Next time I can play I'll test 192, the next buffer lower, and see how that works and report back.

---

To add to the above: I have not had time to do extensive testing with it yet but have ran the game for a few minutes while at 192 and it wasn't immediately buggy yet... Now to clarify, I have only tested a few minutes at this buffer size. I just haven't had time to test further yet, but I will be as soon as I can. If 192 buffer works fine for a couple hours play session, I will continue testing down to 160 as well.

The next lower buffer under 160 is my old default 128 which has this buggy audio...so if by a miracle 160 also works, I will be quite happy.... but we shall see...

I test again yesterday at a buffer size of 192 but it take less than 5min to crash the audio totally and you have to resynchro by changing the buffersize or sample rate if you dont want to lose your ears.

A buffer size of 256 is not necesserly bad. Its not the best for playing guitar for exemple, because you have to ear the note that was capture by the mic on your guitar really quick, not a second later. But at 256 you got just some millisecond more than through 192. 

128 will always be the better anyway, if your cpu could afford it. So it basically remain of a bad CPU optimisation of the program than you use.

I use to move the buffersize since i use asio interface wich is like 15 years.

---

@SP0000kS wrote:

I test again yesterday at a buffer size of 192 but it take less than 5min to crash the audio totally and you have to resynchro by changing the buffersize or sample rate if you dont want to lose your ears.

A buffer size of 256 is not necesserly bad. Its not the best for playing guitar for exemple, because you have to ear the note that was capture by the mic on your guitar really quick, not a second later. But at 256 you got just some millisecond more than through 192. 

128 will always be the better anyway, if your cpu could afford it. So it basically remain of a bad CPU optimisation of the program than you use.

I use to move the buffersize since i use asio interface wich is like 15 years.

---

This is a good point, I suppose with other people's systems this workaround might rely on different buffer sizes for different CPUs to work. Everyone should experiment for themselves to find out the lowest they can go.

Yes that's how it works. But never experience this for a videogame also.

It would have been nice to have some communication from EA/DICE about this.

It concern every people who want to stream. I feel it's pretty quiet from them.

I have the same issue as you guys. In-game audio cuts off after 1-5mins of playing, Discord is still working fine.

Using a Sennheiser USB head-set, but it behaves the same way as you discribe.

Problem started with S6 update.

---

@JD_W0LF wrote:

---

@SP0000kS wrote:

Really not fun for people who like to stream.. as they all use mic through an interface.

Feel like i can go to 256/48khz, it should be better for your mic latency.

At 192 it crash the sound after like less than 5min of playing.

---

Update to this: I skipped testing buffer size 512 because discord friends said my mic was still sounding bad... so I went to 256 buffer size tonight and played for about 2-3 hours with no audio issues from either ingoing or outgoing audio.

So it looks like at least Scarletts set to 256 buffer works for now. I will continue testing lower buffer until the problem happens and report which ones work for me and don't. Next time I can play I'll test 192, the next buffer lower, and see how that works and report back.

---

So I tested buffer at 192 once, and had no issues for a few minutes but couldn't actually play so I thought 192 would be fine in later testing... well I finally had a chance to play last night and 192 buffer did NOT work at all when I tried again. Crackly messed up audio just like before. So for me it looks like 256 is the lowest I can go until they fix this issue.

Few problems for user experience since s6 update : random blackscreen at end of match, random error matchmaking, high cpu usage, invisible floor (2-3 time) invisible weapon (1 time), sound problems through interface..

We have given some time trying some tweak to been able to play for this sound problem.

Imagine someone who just buy the game and experience this.

This is a total degraded service for a game update. And no communication about it.

We are still beta tester after 2 years.

After the BF2042 update of 31/10 there is still audio problem through asio interface:

- 128 buffersize (default) : audio cut after 1-2 minute of playing and never come back again.

- 192 buffersize : audio totally crackle/glich then crash immediatly and make a loud noise through speaker.

- 256 buffersize : audio seem normal but there is now some latency for the mic again if you stream or use discord.

Still the same audio problem than after the S6 update..

We should probably give up. I seriously doubt there is anything they can do since it seems to be tied with the new anticheat.