Audio popping issue

[XenophineEX]

My processor is also AMD

AMD FX(tm)-6300 Six-Core Processor 3.50 GHz
Installed Ram 16.0 GB @1866
Nvidia geforce gtx 960
mobo msi 970

It has played everything including this quite well, minus the sound issues.

Need to add it is on windows 10 home, (paid for) 64 bit.
Windows 10 Home version 21H2; OS Build 19044.1415

I can also add I have another 12gig's of vram across 3 drives, and 1 drive a solid state for only system performance at 80 gigs a ssd.

Another thing to add it that I have everything set to programs, as that would reap the most benefit here, setting things to background processes won't work. I have also gave the game near realtime processor priority, yet even then it only eats about 40%. The processor is also overclocked and running under 70 degrees at 4.2 ghz.

This is the mobo page https://us.msi.com/Motherboard/970-GAMING/Specification

the main take-away from that mobo page is the audio device: Audio

• Realtek® ALC1150 Codec
- 7.1-Channel High Definition Audio
- Supports S/PDIF output

[MoonstalkerZ]

My dad, a 40-year veteran of the programming industry, had several insights that I'd like to share here.

First, the community team's response of blaming user hardware may not be the opinion of the devs, or even of the individual community team members, but could be a result of orders from on high based on advice from lawyers. If SE delivered a non-functioning product, and the problem IS on their end, they could be liable for damages, depending on how the laws work in Japan. So though yes, the response sucks, we shouldn't be abusive to the community team - it's entirely possible they're just doing what the lawyers told them to, and being nasty isn't going to help them fix anything.

His second insight is about what the devs might have been dealing with when they were writing the new sound engine. If they were basing it around this third party system, they would have had to figure out how to work with an unfamiliar API, and there's a good chance they had to contort their programming around this API. Also, I could be wrong, but it doesn't look like Embody is a Japanese company, so if the documentation was only written in English and they didn't have any programmers fluent enough in English to understand the documentation, they'd need to get someone to translate first. Not only does that require someone who speaks both Japanese and English, but it requires a translator with programming knowledge in both languages. (Trust me, as a former amateur translator, googling stuff will only get you so far if you don't even understand the subject matter.) It's certainly not an excuse for the shoddy mess they pushed out at the last minute with no warning, but that's a programmer's opinion of what the devs' experience might have been.

Finally, he mentioned that their inability to reproduce the problem is a HUGE barrier to fixing it. He said that at this point, their best bet is to find someone who has the bug and flat out buy their computer (and pay for a replacement, of course - $2000 is nothing to SE).

So several takeaways from that.
1) Temper your expectations. They can't even reproduce the bug. It's not going to be fixed in two weeks unless they can immediately reproduce the bug.
2) I realize that means the game's going to be an awful experience for a long time. Go ahead and unsubscribe if you want, if enough people do it it'll put pressure on them to get it fixed quickly, but also don't feel bad if you don't unsubscribe - I plan on playing anyway, I still enjoy it enough that I'm not willing to give it up just to send a message.
3) I really do think they're trying. While the situation is extremely frustrating, even anger-inducing, writing abuse at the devs and the community team on the official forum isn't going to help any.
4) DO keep up the pressure, though. Keep talking about it, keep sending bug reports (DETAILED bug reports), keep tweeting. I understand we're all angry and frustrated, but do TRY not to be a total jerk about it.
5) I keep seeing people posting their hardware in here, bug symptoms and steps they've taken to fix it. Don't just post them in here, post bug reports as well. It's the bug reports that they're going to read.

[Maeklos]

So the VAC did actually stop the stuttering?

If thats the case it may be a problem with FX chips and their motherboards onboard audio. unfortunately its something I cant exactly test because who has sound cards anymore?

I'm stumped to be honest, I just cant believe that its not been addressed when its been reported thousands of times.

The VAC did not stop the stuttering. It just turned it from audio garbage (extremely loud G-G-G-G-G-G-G-G-G) to muting effects. Basically, the VAC driver wasn't putting through the audio garbage, making it sound like someone was flicking the Mute button really quickly.

[Maeklos]

So several takeaways from that.
1) Temper your expectations. They can't even reproduce the bug. It's not going to be fixed in two weeks unless they can immediately reproduce the bug.
2) I realize that means the game's going to be an awful experience for a long time. Go ahead and unsubscribe if you want, if enough people do it it'll put pressure on them to get it fixed quickly, but also don't feel bad if you don't unsubscribe - I plan on playing anyway, I still enjoy it enough that I'm not willing to give it up just to send a message.
3) I really do think they're trying. While the situation is extremely frustrating, even anger-inducing, writing abuse at the devs and the community team on the official forum isn't going to help any.
4) DO keep up the pressure, though. Keep talking about it, keep sending bug reports (DETAILED bug reports), keep tweeting. I understand we're all angry and frustrated, but do TRY not to be a total jerk about it.
5) I keep seeing people posting their hardware in here, bug symptoms and steps they've taken to fix it. Don't just post them in here, post bug reports as well. It's the bug reports that they're going to read.

I really like these takeaways and add my own support to them. The team just made an amazing expansion with Endwalker. And, yes, it sucks that we can't enjoy it -now-, but I think that we can all agree that these folks who have just gotten out of at least a couple months' worth of hard crunch deserve some time off with their families for the holidays. Plus, we've all already gotten 21 days of free game time out of all this. Adding it up for everyone who's subscribed, that means that Yoshi-P's given his players something like $20 million just to try to set things right already.

So, keep it up, don't give up, but temper expectations until after the holidays.

[XenophineEX]

The VAC did not stop the stuttering. It just turned it from audio garbage (extremely loud G-G-G-G-G-G-G-G-G) to muting effects. Basically, the VAC driver wasn't putting through the audio garbage, making it sound like someone was flicking the Mute button really quickly.

That is what I have without buying their new audio codec, just quick fades in and out of everything. It is really horrible on all combos, as every step seems to make it worse.

[XenophineEX]

My dad, a 40-year veteran of the programming industry, had several insights that I'd like to share here.

First, the community team's response of blaming user hardware may not be the opinion of the devs, or even of the individual community team members, but could be a result of orders from on high based on advice from lawyers. If SE delivered a non-functioning product, and the problem IS on their end, they could be liable for damages, depending on how the laws work in Japan. So though yes, the response sucks, we shouldn't be abusive to the community team - it's entirely possible they're just doing what the lawyers told them to, and being nasty isn't going to help them fix anything.

His second insight is about what the devs might have been dealing with when they were writing the new sound engine. If they were basing it around this third party system, they would have had to figure out how to work with an unfamiliar API, and there's a good chance they had to contort their programming around this API. Also, I could be wrong, but it doesn't look like Embody is a Japanese company, so if the documentation was only written in English and they didn't have any programmers fluent enough in English to understand the documentation, they'd need to get someone to translate first. Not only does that require someone who speaks both Japanese and English, but it requires a translator with programming knowledge in both languages. (Trust me, as a former amateur translator, googling stuff will only get you so far if you don't even understand the subject matter.) It's certainly not an excuse for the shoddy mess they pushed out at the last minute with no warning, but that's a programmer's opinion of what the devs' experience might have been.

Finally, he mentioned that their inability to reproduce the problem is a HUGE barrier to fixing it. He said that at this point, their best bet is to find someone who has the bug and flat out buy their computer (and pay for a replacement, of course - $2000 is nothing to SE).

So several takeaways from that.
1) Temper your expectations. They can't even reproduce the bug. It's not going to be fixed in two weeks unless they can immediately reproduce the bug.
2) I realize that means the game's going to be an awful experience for a long time. Go ahead and unsubscribe if you want, if enough people do it it'll put pressure on them to get it fixed quickly, but also don't feel bad if you don't unsubscribe - I plan on playing anyway, I still enjoy it enough that I'm not willing to give it up just to send a message.
3) I really do think they're trying. While the situation is extremely frustrating, even anger-inducing, writing abuse at the devs and the community team on the official forum isn't going to help any.
4) DO keep up the pressure, though. Keep talking about it, keep sending bug reports (DETAILED bug reports), keep tweeting. I understand we're all angry and frustrated, but do TRY not to be a total jerk about it.
5) I keep seeing people posting their hardware in here, bug symptoms and steps they've taken to fix it. Don't just post them in here, post bug reports as well. It's the bug reports that they're going to read.

I posted my specs, they can reproduce it under 600 bucks even with a chip shortage, as everything I have was readily made and still in stock.

[XenophineEX]

Main take-aways I have seen are with AMD processors and realtek audio drivers.

As far as my mobo from msi (the 970) this is the latest update to my realtek driver.

Realtek High Definition Audio Driver
Version
6.0.1.8010
Release Date
2017-02-07
File Size
357.68 MB

btw downloading from msi means it is already done, as opposed to that other method of 40kb a sec

I will install my mobo driver again, and report here if by some chance of haleion it makes the sound stop stuttering

restarted the pc twice, but now is the true test on if it works (also have siren log in ques)

ehh not too bad only 25, used to be 1900

I will que duty roulette and test the sound.

(only up to Stormblood so my testing will be limited)

so the stuttering is still there, seems wholly attached to combat only. Mainly aoe, but anything involving a 4 combo is also affected. *sigh*

The system seems to be bottlenecking itself with sounds from different sources. Instead of using compression it is just letting every sound fly one on the other overlapping till we get stuttering. Reminds me of when I first started using fruity loops, a sound program for music, I didn't know what compression was then and I just let everything play at the same volume and I got the same results as what is going on in this game. I would hope we didn't inherit some newfound audio mixer that doesn't know how to to use compressors.

(what's a compressor you ask? It is the filter that allows things to be heard despite overbearing harmonics, they are also known as crunchers with heavier music, the idea being when a sound frequency hits a certain range it is "compressed" or lowered to fall in line with the set maximum of the other volumes. It makes it so that you can hear everything, rather than 1 thing.

[-BlueGreen-]

First, the community team's response of blaming user hardware may not be the opinion of the devs, or even of the individual community team members, but could be a result of orders from on high based on advice from lawyers. If SE delivered a non-functioning product, and the problem IS on their end, they could be liable for damages, depending on how the laws work in Japan. So though yes, the response sucks, we shouldn't be abusive to the community team - it's entirely possible they're just doing what the lawyers told them to, and being nasty isn't going to help them fix anything.

I was just thinking about this point today. I figure if this indeed does go on long enough, they could be facing something along the lines of a class action lawsuit. After all, they put out a benchmark to help players test for system readiness prior to purchasing the expansion, and many players no doubt ran the benchmark and later ordered the expansion and purchased game time confident they’d be able to enjoy the game with their current hardware (congestion aside). The fact that many are now discovering that their hardware is now unable to run the game as expected means that the benchmark was misleading. IMO, in this context, I feel a strategy of “blame the user’s hardware” will make matters worse, not better. If they refuse to properly fix this, they could be on the hook for paying out refunds on the expansion, playtime, and potentially any other purchases that depended on a working expansion (eg, you wouldn’t have bought a fantasia to try male Viera if you knew the game would be unplayable).

Could you imagine if something like Microsoft did this with Windows? Imagine releasing a tool to test for compatibility with the next version, claiming that it will work, allowing the customer to purchase the product, then making a late breaking change that they then refuse to fix later. Now imagine that the user has no way to know that it actually won’t work until they’ve already installed it and registered the license key. Going through the normal channels, that user is no longer eligible for a refund, but obviously they will want one if no fix is on the horizon. At this point the company essentially used a lie (working benchmark/compatibility tool) to get their mon y, and then ran. I’m fairly sure that in some form or fashion that move is illegal in most countries.

I feel like SE’s best bet would be to completely revert the sound driver to what it was in the benchmark even if that does mean breaking compatibility with that new plugin. That would at least make the game playable in the short term, and they can work on possibly bringing that back in later. Of course, if they’ve entered into some sort of contract with that company over this (I’d assume that SE gets a portion of the sales of that sound pack, otherwise, why would SE bother in the first place?), that could seriously complicate this mess.

I haven’t heard anyone mentioning anything positive about the sound plugin, so it makes me wonder if sales will be a flop for it.

Anyway, I’ll post a detailed bug report around Monday or so when I return home.

[XenophineEX]

I was just thinking about this point today. I figure if this indeed does go on long enough, they could be facing something along the lines of a class action lawsuit. After all, they put out a benchmark to help players test for system readiness prior to purchasing the expansion, and many players no doubt ran the benchmark and later ordered the expansion and purchased game time confident they’d be able to enjoy the game with their current hardware (congestion aside). The fact that many are now discovering that their hardware is now unable to run the game as expected means that the benchmark was misleading. IMO, in this context, I feel a strategy of “blame the user’s hardware” will make matters worse, not better. If they refuse to properly fix this, they could be on the hook for paying out refunds on the expansion, playtime, and potentially any other purchases that depended on a working expansion (eg, you wouldn’t have bought a fantasia to try male Viera if you knew the game would be unplayable).

Could you imagine if something like Microsoft did this with Windows? Imagine releasing a tool to test for compatibility with the next version, claiming that it will work, allowing the customer to purchase the product, then making a late breaking change that they then refuse to fix later. Now imagine that the user has no way to know that it actually won’t work until they’ve already installed it and registered the license key. Going through the normal channels, that user is no longer eligible for a refund, but obviously they will want one if no fix is on the horizon. At this point the company essentially used a lie (working benchmark/compatibility tool) to get their mon y, and then ran. I’m fairly sure that in some form or fashion that move is illegal in most countries.

I feel like SE’s best bet would be to completely revert the sound driver to what it was in the benchmark even if that does mean breaking compatibility with that new plugin. That would at least make the game playable in the short term, and they can work on possibly bringing that back in later. Of course, if they’ve entered into some sort of contract with that company over this (I’d assume that SE gets a portion of the sales of that sound pack, otherwise, why would SE bother in the first place?), that could seriously complicate this mess.

I haven’t heard anyone mentioning anything positive about the sound plugin, so it makes me wonder if sales will be a flop for it.

Anyway, I’ll post a detailed bug report around Monday or so when I return home.

The second you start siding with blood sucking lawyers you are no better than the Ascians.

[Ariel_Valmont]

And thats where i doesn't add up. I am having this issue most in single instances like the rising stones and every inn room. With the spatial audio pack activated i just have to enter those instances and wait a few seconds until the audio breaks. However with the pack activated combat is fine. If i deactivate the audio pack it is exactly reverted. Single instances are fine unless i am not using any Skills, but combat sound is broken.

My issues are almost exclusively in combat, weather they be in the over world or instances, although I will get minor stuttering anywhere it’s nothing compared to the harsh sounds that happen in combat.