Audio popping issue

[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."

[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!

[TojiSuzuhara]

asked the Legend Soken directly himself on twitter and he responded saying they are planning to have this fixed BEFORE 6.1. As frustrating as this issue is, i have nothing but respect that a lead developer goes out of their way to respond to people personally like this. Crossing my fingers this gets fixed asap

https://twitter.com/SOKENsquareenix/...54502893629443

hopefully this helps alleviate fears

[Nuki]

asked the Legend Soken directly himself on twitter and he responded saying they are planning to have this fixed BEFORE 6.1. As frustrating as this issue is, i have nothing but respect that a lead developer goes out of their way to respond to people personally like this. Crossing my fingers this gets fixed asap

https://twitter.com/SOKENsquareenix/...54502893629443

hopefully this helps alleviate fears

to be fair, they could just post an announcement on the lodestone for that, but i guess they dont want bad press on their homepage since they push all these new shiny "audio tools"

Iam happy that its getting fixed now so i dont rly care.

[TojiSuzuhara]

to be fair, they could just post an announcement on the lodestone for that, but i guess they dont want bad press on their homepage since they push all these new shiny "audio tools"

Iam happy that its getting fixed now so i dont rly care.

i think its that and the fact that this is most likely considered a "fringe" issue. its nice knowing i wasn't crazy and the only one having this problem, but i've just accepted the fact that more ppl would need to be experiencing this for them to acknowledge it "officially" on the lodestone

[ClaraKitty]

asked the Legend Soken directly himself on twitter and he responded saying they are planning to have this fixed BEFORE 6.1. As frustrating as this issue is, i have nothing but respect that a lead developer goes out of their way to respond to people personally like this. Crossing my fingers this gets fixed asap

https://twitter.com/SOKENsquareenix/...54502893629443

hopefully this helps alleviate fears

That's fantastic! That's all we wanted to hear.

My husband hasn't had this issue at all and his PC is older than mine, so he's been hoping it gets fixed for my sake.

[Narissa]

asked the Legend Soken directly himself on twitter and he responded saying they are planning to have this fixed BEFORE 6.1. As frustrating as this issue is, i have nothing but respect that a lead developer goes out of their way to respond to people personally like this. Crossing my fingers this gets fixed asap

https://twitter.com/SOKENsquareenix/...54502893629443

hopefully this helps alleviate fears

Oh thank fk.. playing this game with no sound has been rather annoying and very boring

[rojimboo]

I've had it set to allow exclusive mode and to give priority, with all other playback devices disabled all along, so no luck there.

For Linux to handle something game related better than windows is certainly a first for me though, really interesting. (Not to mention on a game built for windows!) Maybe the move off the sinking ship might be sooner than I thought.

Thank you for testing this! Sucks that it didn't work though

Yeah, I was completely surprised that Linux worked better than Windows here. I'm not sure that's ever happened to me before. Sure, I can get parity with Windows in most games, but less buggy or better in Linux?? Never, haha.

(you don't have to reply this but giving it anyway to ended the discussion)
Mine live in the region that doesn't have FF14 on the steam unfortunately, but i hope i can work it out using the standalone... but that's for another day, thank you for sharing it ^^

No worries dude! If you ever need a hand with stuff to get FFXIV working on Linux, gimme a shout

I can replicate it under the conditions of having the SFX muted in various content using a xeon x5960 overclocked to 4.2Ghz,
but my living room setup with a xeon 1680v2 at 4.2ghz struggles to replicate the same increases of cpu usage (that said i was testing off-peak)

Ah ok. So it affects a wide variety of CPUs (perhaps all?). That's really unfortunate. Doesn't seem like there's much people can do on Windows to help with this annoying bug.

Here's a toast with a beer, whilst waiting for the fix to land! Cheers!