The bug
When sleeping in a bed, stereo sounds that are on the left of the player do not switch around to the right, and vice versa, when player orientation changes.
How to reproduce
Create or find sound source (e.g. chicken coop) and orient player so sound is coming from left or right side.
Place bed in front of player with foot of bed closer.
Sleep in bed, which will reverse the orientation of the player in game. However, the sound will continue playing as if no reversal had happened.
Related issues
is duplicated by
Attachments
Comments


Is this still a concern in the current Minecraft version 1.7.4 / Launcher version 1.3.8 or later? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.

I will double-check and report back. Thanks.

Yes it is still happening. I've updated the affected version. Thanks.

Is this still a concern in the current Minecraft version 14w11b / Launcher version 1.3.11 or later? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.

I just tested it in 1.7.5, and it is still happening. I do not have a snapshot loaded to test - perhaps someone else could, or I can re-test when 1.8 comes out.

I've attached a zip file of a simple test creative world set up to test this bug.

Is this still a concern in the current Minecraft version 14w21b / Launcher version 1.4.4 or later? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.

Tested - it is still happening in 14w21b.

Relates to or duplicate of MC-3523

It sounds like it might be related for sure, though the "intended" effect mentioned there (sound not needing to change when in 3rd person view) would not be relevant here since lying in a bed is in 1st person mode.

Yes this is still in evidence in 1.8.1 pre 4. It is NOT resolved.

Keep in mind that the "Resolved"-Status on this ticket just means "Answered", and that we are waiting for further information on whether this issue still exists or not.

Confirmed for 1.13.1.

Fixed in 1.15.2 or earlier.

Just tested in 1.15.2, and it does seem to be fixed. Awesome!