Audio popping issue

[Scylia]

I also like to report my issues with audio popping.
This is very noticeable when flying around in Labyrinthos and seems to be tied to Ambient Sounds.
When I disabled Ambient Sounds, the issue went away.

DirectX 11
CPU: AMD Ryzen 3700x
GPU: RTX 3070
Immerse Audio installed but not enabled.

[Au-ro]

Thank for finally responding zhexos! Please tell us it's a hot fix patch.

[rojimboo]

I posted this on Reddit too in of the posts related to this, but thought it might be useful here too. But I'm glad there is a fix coming! So this might not be necessary even.

TLDR - Please try messing about with sample rates and WASAPI mode on Windows to see if it helps.

On Linux I fixed this with

winetricks -q sound=alsa

At first I suspected something to do with Pulseaudio in Wine and Linuxy things, but reading so many Windows users also having the issue the fault could lie elsewhere. By bypassing Pulseaudio and software resampling, the crackling stopped. I wonder if setting a global sample rate at 16-bit 44.1 khz on Windows would also fix it...if that's the sample rate that FFXIV uses? And WASAPI exclusive mode, because then there would be no resampling utilising CPU and messing about with things.

Anyways, I'm super happy the crackling and popping went away. It was driving me nuts.

[Zholi]

It's being targeted for the next hotfix, for those worried. This is based on my own reading in Japanese of the original post, not a machine translation.

[TojiSuzuhara]

was there a post on the japanese forum too then?

[Nommers]

It's being targeted for the next hotfix, for those worried. This is based on my own reading in Japanese of the original post, not a machine translation.

For those of us sweating bullets at the prospect of waiting until 6.1, could you explain what gives you this impression? The Japanese version of this portion of the text is:

ご迷惑をおかけして申し訳ございませんが、次回のパッチに向けてパターン検証を行った上で
追加の修正リリースを行いたいと考えておりますので、修正までもう少しお待ちいただければ幸いです。

Which DeepL translates as

We apologize for any inconvenience this may cause, but we would like to release an additional fix after we have verified the pattern for the next patch.
We would like to release an additional fix, so please wait a little longer for the fix.

In fact the Japanese version includes the phrase "次回のパッチ" which I believe is "jikai no pacchi," literally "next patch" (DISCLAIMER: I can't read kanji and even with how long Square is taking to fix this I don't think there's enough time for me to learn). Which is also exactly what the English version says. The second line is a little less clear to me - is it in there? It's not that I don't believe you, I'm just curious what about the Japanese text gives you the impression this is coming in a hotfix rather than a patch. Other than the absurdity of waiting two months, of course.

EDIT: Link to the original JP community rep post from a few days ago for those who missed it: https://forum.square-enix.com/ffxiv/...=1#post5797104

[Zholi]

追加の修正リリース "supplemental fix release," roughly. Supplemental as opposed to a mainline patch. DeepL is just rendering this as "additional fix."

[rainichan]

Both Soken and the Japanese rep mentioned the next patch. As far as know there aren't fixed dates for the next patches yet (as there were for 6.01 and 6.05), there being just the information that 6.1 is gonna be out before the end of the first quarter (so, by the end of March, probably).

For those who have been here at the beginning of other expansions, is there a chance of being an extra patch before 6.1 (like a 6.08 or something)?
Or for all other expansions, has it always been X.01, X.05 and then X.1?

Historically there have been more than just the initial .01 and .05 patches - ShB had a 5.08, SB had 4.06 and 4.06a, HW had 3.07, and though it's been like 8.5 years, I'm pretty sure 2.0 had some fix patches (they aren't listed on their patch archives) so an extra fix patch at the end of this month/sometime next month isn't out of the realm of possibilities. For the record, 5.05 and 5.08 were about a month apart, 4.05 and 4.06 were 20 days, 3.05 and 3.07 were 34 days. So, about ~1month or so, I would wager, unless they push a fix out quicker. I hope it's quicker with a hotfix tbh, since I've had all the problems documented in here and it really decreased how the final EW fight and subsequent cutscenes played out for me :/ no one else should have that issue when they get there.

EDIT: There was a JP Radio Mog Station that had Yoshi-P on to talk about some things in terms of 6.0 and some technical things about what the 6.0 patch brought. One of the things translated by the FFXIV discord was, with emphasis mine:

"・侍や黒のようなピュアDPSはちょっとケチりすぎたかなと思っているので6.08で調整する
Pure Firepower jobs like SAM and BLM will have DPS buff since the devs do think they were a bit stingy on them. It will be for 6.08"

Hopefully the audio fixes will be in 6.08 with some other job adjustments!

[Arcee]

In the radio interview today/yesterday I think YoshiP mentioned a .08 patch that had some Job tuning and other small tweaks in it, no talk of a release date but it can't be too far off if there's nothing major outside of tuning/bug fixes.

e: Oh the poster above mentioned exactly where I read this. That's what I get for posting right after waking up!

[ClaraKitty]

Sorry, but this is the very first thing Square Enix told us to try several weeks ago, and as far as I know it didn't work for anyone.

There was another tweet from Soken yesterday promising that fixes will be included in "the next version." https://twitter.com/sokensquareenix/...792569867?s=21 I sincerely hope he doesn't mean 6.1 because that is months off. The post-6.05 Known Issues post on Lodestone mentioned that they wanted to have the two listed issues fixed by the weekend. One's already been fixed. Maybe there will be another patch today fixing the other one that also attempts to address the audio. I don't exactly have my hopes up but I guess we'll see.

EDIT: There's also been a post by a community rep over on the Japanese forums: https://forum.square-enix.com/ffxiv/...=1#post5797104

DeepL translation:


Together with Soken's tweet, this is very good news. The post immediately following this also mentions that FX series CPUs are a rarity in Japan. Given the apparent inconsistency in how the bug affects other hardware configurations I suppose it makes sense that the issue would take a long time to track down. I'm still praying for a Lodestone post so that we don't have to dig through twitter and filter forum posts through the language barrier. Still, here's hoping this is fixed sooner than later.

Ah, this is wonderful to see! So they are addressing it!