Search Issue Tracker
Fixed
Fixed in 6000.0.15f1, 7000.0.0a12
Votes
0
Found in
6000.0.5f1
6000.1.0a7
Issue ID
UUM-73045
Regression
No
Audio random container pitch fields can be set beyond their max and min constraints
*Steps to reproduce:*
# Create and open an empty project.
# Create an audio random container asset (Asset > Create > Audio > Audio Random Container).
# Set the pitch float field to 5000. It clamps to 1200.
# Set the pitch float field again to 5000.
*Actual results:* It clamps to 2400.
*Expected results:* It clamps to 1200.
*Reproducible with versions:*
6000.0.5f1
*Tested on (OS):* MacOS (M1) 14.4.1
*Notes:*
* This also applies to clamping to minimum values, i.e. it clamps to -2400 instead of -1200.
* This also applies to the randomize min and max fields.
* This does not apply to any other field, such as volume and time.
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
- Getting a deprecated package for JetBrains Rider pop up when opening or creating a project
- [Android] Volume level of the same audio file is different on Samsung Galaxy Tab A8 between 2023.3.0b3 and 2023.3.0b4
- ‘Expected end of value’ warning occurs when a property declaration includes five or more variable references
- Crash on BurstCompilerService::CompileAsync when entering Play mode in a specific scene
- InvalidOperationException when using Game Camera Preview in Scene window with a custom RenderGraph pass
Resolution Note (fix version 7000.0.0a12):
Fixed an issue in the Audio Random Container where the pitch field clamp range was inconsistent and could be set beyond the UI clamp range (-1200 and +1200).
Resolution Note (fix version 6000.0.15f1):
Fixed an issue in the Audio Random Container where the pitch field clamp range was inconsistent and could be set beyond the UI clamp range (-1200 and +1200).