Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2018.4.X, 2019.2.X, 2019.3.X
Votes
2
Found in
2018.4.0f1
2019.2.0f1
2019.2.2f1
2019.3.0a1
2020.1.0a1
Issue ID
1179486
Regression
Yes
Playables API AudioMixerPlayable plays only the clip from first input when crossfading at least two clips
How to reproduce:
1. Open user's attached project (animation_engine.zip)
2. Open The "Main Scene" Scene > Enter the Play Mode
3. In Hierarchy Window select "AudioController" GameObject
4. In Inspector Window > find "Audio Controller" Script > Change "Mix Value" value to 0.50
5. Listen to an outputted clip sound
Expected result: Audio clips from both inputs are playing (CrossfadingWorks.mp4)
Actual result: The PlayableGraph Visualizer shows both clips crossfading as expected, but only the clip from the first input is heard (CrossfadingNotWorking.mp4)
Reproducible with: 2018.4.0f1, 2018.4.8f1, 2019.2.5f1, 2019.3.0b3, 2020.1.0a4
Not reproducible with: 2017.4.32f1
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
5argon
Nov 02, 2019 12:02
I have confirmed this is fixed in 2019.3.0b9 (where it wasn't in 2019.3.0b8)
jadelion1235
Oct 31, 2019 22:02
Even though this shows as Fixed in 2019.2, the bug is still present in 2019.2.11f1.
Is there a specific release that will reflect this bug fix?
mangax
Sep 11, 2019 04:32
i confirm this issue.