Search Issue Tracker
Fixed in 5.1.2
Votes
2
Found in
5.0.0b21
Issue ID
670070
Regression
Yes
Audio clip volume is normalized when "Force to Mono" is enabled on a 16-bit stereo wav
Attached project:
- Includes 2 pairs of audio clips that demonstrate the issue.
- Notice the difference in volume between each clip and its "forcemono" equivalent, even though the source wav data is exactly the same.
To reproduce from scratch:
- Create a 16-bit stereo wav file with very low volume; import it into Unity.
- View and listen to audio preview; note the volume is low.
- Check "Force to Mono" in the clip settings and click Apply.
- View and listen to audio preview; note the volume has been normalized.
To further investigate:
- Attenuate or amplify the original clip data; reimport into Unity.
- View and listen to audio preview with "Force to Mono" enabled; note the volume appears exactly the same as in previous steps (even though the wav has been modified).
Comments (1)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Resources.UnloadUnusedAssets() freezes the Editor when releasing Mesh objects
- 16-bit Sprite Textures have a banding effect and loss of data when packing into Variant Sprite Atlas
- HDRP Cluster artifacts when having more than 100 lights
- ParticleCollisionEvent.intersection generates extremely high values when particles collide while in Play Mode
- Custom attributes are not properly converted to subgraphs
ScoCorp
May 11, 2015 06:00
Any progress on this? This is throwing our audio levels out of whack. Some clips are way louder than expected - but only if the source wav was stereo!
The bug was only introduced in Unity 5 when a normalization pass was lumped in with Force to Mono. Please just delete this new "feature" and restore it to Unity 4 functionality.
If you want to keep the normalize option, add a new Normalize checkbox to the importer.