haloman30

@Chaos Ophy Yeah if MC had it its own alsoft.ini that might do it - and yeah it'd be pretty cool if it made some of the other settings configurable in-game as well.

Alright I did a bit more testing and I think I've absolutely confirmed what the root of the issue is:

If there is an alsoft.ini that exists at the system level, the in-game option is ignored. If that file does not exist, then the in-game setting is used instead.

I renamed my alsoft.ini to something else so that OpenAL wouldn't use it anymore - and now the in-game toggle switch works as expected. HRTF turns on and off, and I can actually hear the audio change with it.

On Windows, the alsoft.ini is located in %AppData%\alsoft.ini. I can't say for sure where it is on Linux, but according to the Reddit post I linked in my previous comment, it should be located at ~/.alsoftrc.

I'm not sure if that's something that's fixable or if that's just a bug with how OpenAL itself works - but I wanted to once again let you guys know that detail as I bet it'll probably save you guys a ton of time and effort.

Hey so I've done some more research and I've found a workaround that allows me to play without my ears hurting - and I figure it might be helpful in solving the issue properly.

I found a [Reddit post|https://www.reddit.com/r/oculus/comments/1fzonq/psa_for_games_using_openal_including_minecraft/] instructing users on how to enable HRTF audio system-wide for VR purposes, and it instructs users to locate and modify a file called alsoft.ini. For 3D sound that works well in VR, the author instructs adding

hrtf = true

to the configuration. This was already set to true in my case - as I've played MC in VR before using Vivecraft - and as a test I changed it to false. Turns out, setting it to false properly disables HRTF within MC and it sounds identical to 1.18.2 and prior.

I should also note that the issue of the in-game toggle button not having any effect is still present - this time, it just doesn't enable since it's been disabled system wide. I'm not sure if this is intended behavior - it doesn't seem like it is, it really seems like the in-game option simply doesn't have any effect and it just uses whatever alsoft.ini says.

Either way, I hope that extra info is helpful to you guys regardless so that other people don't have to deal with this in the future.

Videos are recorded and added to the description.

I'm not so sure it is, seeing as MC 1.18.2 works just fine (and so does literally every version prior) - so it seems like it's some kind of issue with 1.19 that just doesn't play nicely with something in my hardware?

To me that still sounds like a software issue with MC, not a hardware issue.

Having this same issue and it still is present in 1.19.1 pre-releases as well. Really hoping this actually gets noticed and solved because this really sucks to listen to and makes post-1.18 pretty unpleasant to play (I'll literally go ahead and just mute the audio because in some cases the compressed sounds are genuinely painful)