Search Issue Tracker
Active
Votes
0
Found in
6000.0.58f1
6000.2.6f1
6000.3.0b3
Issue ID
UUM-119391
Regression
Yes
[Quest] Pitch Shifter causes audio degradation on Quest 2 devices when sped up
Steps to reproduce:
1. Open the attached user's project "AudioPitchShifter.zip"
2. Switch to Android
3. Build to Quest 2
4. Once application loads, wait for the audio to start
5. Press the "A" button on the Quest 2 controller
6. Observe the audio degradation once the audio is sped up
Expected result: Audio quality remains the same once sped up
Actual result: Audio quality worsens when sped up
Reproducible with: 2023.3.0a11, 6000.0.58f1, 6000.2.6f1, 6000.3.0b3
Not reproducible with 2023.3.0a10, 2022.3.66f1
Reproducible with these devices:
VLNQA00417 - Oculus Quest 2 (Quest 2), CPU: Snapdragon XR2, GPU: Adreno 650, OS: 10
Not reproducible with these devices:
VLNQA00644 - Oculus Quest 3S (Quest 3S), CPU: Google Tensor G2, GPU: Adreno 740, OS: 14
VLNQA00609 - Oculus Quest 3 (Quest 3), CPU: Snapdragon XR2 Gen 2 (SM8550), GPU: Adreno 740, OS: 12
Notes:
-Used Quest 2 device is on the latest v79.0 firmware update
-Issue does not reproduce in Editor or Standalone Windows Player
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Quest] Pitch Shifter causes audio degradation on Quest 2 devices when sped up
- "GUI Error: Invalid GUILayout" and "NullReferenceException" are thrown when adding Scenes to "Scenes in Baking Set" in Adaptive Probe Volumes
- Inspector window not updating when switching GameObjects in Play Mode while having a VR headset connected
- “UnityException: GetInvalidFilenameChars” errors are thrown, and the Overlay Save Preset button becomes unusable when entering Play Mode with a shortcut while Overlay Save Preset window is opened
- "UnityException: GetName can only be called from the main thread." erors are thrown when the Shortcuts window is opened and entering Play Mode with a shortcut
Add comment