Audio popping issue

[Maeklos]

The FX-8350, which multiple people here have posted they have (and also which I have) was released in October 2012. It is not limited to CPUs in double-digit age.

Yeah. It's a chipset that can *still* be found on $1k computers on Amazon and elsewhere. I bought my computer brand new 4 years ago and it's got FX-8350s in it, simply because they're solid chips. With my 1070 Ti, I can run every game I've played in at least High settings, if not Ultra or equivalent. So, blaming sound issues on "old hardware" is kind of a subversive take on SE's part. Perhaps more appropriate would have been to say "hardware we hadn't tested on" or something.

[Lagunow]

Yeah. It's a chipset that can *still* be found on $1k computers on Amazon and elsewhere. I bought my computer brand new 4 years ago and it's got FX-8350s in it, simply because they're solid chips. With my 1070 Ti, I can run every game I've played in at least High settings, if not Ultra or equivalent. So, blaming sound issues on "old hardware" is kind of a subversive take on SE's part. Perhaps more appropriate would have been to say "hardware we hadn't tested on" or something.

Indeed. FX-8350 is still pretty fine for a lower/mid-budget PC.

Since they've implied that we're trying to run the game on a toaster, I did a requirement check on system requirements lab, and found that FX-8350 is actually above not only "minimum requirements", but the "recommend requirements" as well. I recommend everyone does it as well, so we have proof it's not a "we're trying to run the game on a toaster" issue.

[Grimno]

Indeed. FX-8350 is still pretty fine for a lower/mid-budget PC.

Since they've implied that we're trying to run the game on a toaster, I did a requirement check on system requirements lab, and found that FX-8350 is actually above not only "minimum requirements", but the "recommend requirements" as well. I recommend everyone does it as well, so we have proof it's not a "we're trying to run the game on a toaster" issue.

I myself am using a FX 8320 which from what I see is only "slightly" lower then the FX 8350 (About 6%) so if that 8350 is above recommend requirements, mine should absolutely be okay then.

[AsheStrachan]

I'm kinda scared that since its mostly with people who have older CPUs,we might not actually get a fix for this,and just sorta be left out,get a better CPU kinda thing
Which is stupid,since ShB worked perfect

[polyphanes]

I'm kinda scared that since its mostly with people who have older CPUs,we might not actually get a fix for this,and just sorta be left out,get a better CPU kinda thing
Which is stupid,since ShB worked perfect

In addition to the fact that it's clear that it's not as simple as saying "old hardware" given how many other newer machines have this same issue, including when the benchmark itself identifies and provides no problems or bugs of any sort along these lines, there is also the issue of having perfectly serviceable software just a few weeks back prior to FFXIV 6.0 that worked totally fine (and which many people are calling for a return to at least until such an issue with an improved sound engine is provided). Plus...I mean, it does sound a little weird for a game that's operating on fundamentally ten-year-old code and software/server models to say that we need newer machines
now to keep up with it.

[Grimno]

In addition to the fact that it's clear that it's not as simple as saying "old hardware" given how many other newer machines have this same issue, including when the benchmark itself identifies and provides no problems or bugs of any sort along these lines, there is also the issue of having perfectly serviceable software just a few weeks back prior to FFXIV 6.0 that worked totally fine (and which many people are calling for a return to at least until such an issue with an improved sound engine is provided). Plus...I mean, it does sound a little weird for a game that's operating on fundamentally ten-year-old code and software/server models to say that we need newer machines
now to keep up with it.

Yeah like my processor isn't new, but they say
"Older then 10 years" and I see a ton of folks, myself included, using the FX 8320, and that was october 2012, so it's 9 years old.

Side Note: Turned on the "Spatial Pack" and the popping seems to have gone away.
The new problem is.. well... the audio pack sounds terrible. Voices and music are normal, but sound effects now have a muffled sound like they're underwater.
I also noticed if the spatial audio is on, the Equalizer HAS to be set to normal.
Changing it to Bass/Treble/Voice/Logi will cause it to stutter, but changing it back to Normal will instantly fix it.
This is not a solution since I'll have to buy the pack once the trial is over...

[sylphic]

AMD FX 8320 E this is the processor I have and I am having this same issue. I am going to try the Dx9 switch and try that.

[AluneTempest]

Why is the benchmark that was supposed to be the program that shows if our system is able to run the game does not present this problem?

I've done the test without any program running along the test and with several programs running along the test and always had good results.

The benchmark doesn't even have the option of this immersive audio, so it shouldn't have this update in the audio driver.

[Vendi]

getting more and more obvious by the day that the problem stems from the implementation of this 3rd party audio mod that nobody wanted

Considering all the tried "fixes" done on this forum alone, it should also be pretty clear that nothing can be done on the user side. I also feel like that it is pretty obvious and at this point anyone should be able to dedutct, that the reason is probably the implementation of the 3rd party audio programm or the changes to accommodate its use. I just find it mostly baffling that no method of reversing to the old audio was made during development/ implementation (which is usually a standart when you are doing such drastic changes that could affect the whole playerbase). In addition, I also find it very concerning that this issue (at this point) perists already for 3 weeks, because it has been known since day 1 and is one of the biggest problems, besides login issues.
All we can do is just giving them the bug report stats, explanations and keep hoping, I guess.
I am not even mad anymore, just pretty disappointed.