Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.3.0b1
Issue ID
953199
Regression
No
[Android] Audio distortion when audio was recorded with device's microphone
Steps to reproduce:
1) Download attached project and open in Unity
2) Build and run project on a device
3) Press on 'C# sript' button
4) Change 'Clip lenght' to ~ 5sec
5) Press on 'Start Rec' button
6) Record a sound
7) Press on 'Play aClip' button
Observe the distorted output
Expected result: Microphone should record a sound without major distortion
Actual result: Recorded audio is distorted
Reproduced with:
5.5.4p5, 5.6.3p4, 2017.1.1p3, 2017.2.0f1, 2017.3.0b1
Devices under testing:
Reproduced with:
(5052)Asus K011, OS:4.4.2, CPU:x86, GPU:Intel/BayTrail, Build:asus/WW_K011/K011:4.4.2/KOT49H/WW_user_3.1.23.191_20160107:user/release-keys
Not reproduced with:
Google Pixel, OS:8.0.0, CPU:arm64-v8a, GPU:Adreno (TM) 530, Build:google/sailfish/sailfish:7.1.2/NJH47D/4045516:user/release-keys
Samsung GT I9300 (Galaxy S3), OS:4.3, CPU:armeabi-v7a, GPU:Mali-400 MP, Build:samsung/m0xx/m0:4.3/JSS15J/I9300XXUGNG3:user/release-keys
Samsung SM T533, OS:5.1.1, CPU:armeabi-v7a, GPU:Adreno (TM) 306, Build:samsung/matissevewifixx/matissevewifi:5.1.1/LMY47X/T533XXS1BPL2:user/release-keys
Note: Recorded audio with an external app did not reproduced this behavior
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note:
Won't fix - too small impact, only one device and a very specific workflow.