Dropper and dispenser sound is not directional

Confirmed on Samsung Galaxy S6 (SM-G920W8), Android 5.1.1 MCPE 0.14.3 single player creative.

Compare with any door in the same circuit: you'll hear the intensity of the open/close sound decrease gradually as you move away from the door.

I am afraid we can not reproduce this bug in the recent version. Please update affected versions if this bug still occurs.

Still an issue in 0.15.3; dropper and dispenser sound is at the same full volume until you're out of range, when it stops. (It should fade)

This also affects buttons, pressure plate, lever and tripwire hook

Confirmed for 0.15.90.2. (Tested on Pocket Edition.)

I noticed that the dispenser sound is directional when it's firing eggs or snowballs, for example, but not when empty.

Affects 0.16.0 Beta Build 4 (AKA 0.15.90.7).

Affects 0.15.10 & 0.15.90.8 (0.16.0 beta build 5).

This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).

Having this same issue in 19w12b snapshot.

More specifically, a dropper when dropping items or when empty, activated by a redstone clock circuit.

Information from a duplicate report (MCPE-48919) confirms that the sounds from pressure plates, levers, buttons, tripwires, and comparators aren't directional either.

Confirmed for 1.12 and 1.13.0.2.

1.14.30.51 also

I've attached a resource pack that fixes this issue:

Here is a demonstration of the fix:

Code/data analysis:

Sound directionality is determined by the true/false value given to "is3D" in the "sounds" part of individual sound definitions in sounds\sound_definitions.json. It appears that the default value is "true" for every sound except random.click. The attached pack fixes this bug by inserting "is3D" and "min_distance" into the following section of sound_definitions.json:

"random.click" : {
         "__use_legacy_max_distance" : "true",
         "min_distance" : 1.5,
         "category" : "ui",
         "sounds" : [
            {
               "load_on_low_memory" : true,
               "is3D" : true,
               "name" : "sounds/random/click",
               "volume" : 0.20
            }
         ]
      },

The "min_distance" : 1.5 makes the attenuation begin at 1.5 blocks from the source. I tested several values and felt that this was most balanced. Without it the sound drop-off is too much, and with a higher value the sound drop-off is not as noticeable.

Affects 1.17.40.20

@unknown, I can't reproduce in 1.17.40.20 Beta. What steps did you use to test this issue?

This is already fixed in 1.17.30.