Search Issue Tracker
By Design
Votes
3
Found in
2018.4.0f1
2019.1.0b2
2019.1.7f1
2019.2.0a1
2019.3.0a1
Issue ID
1164994
Regression
No
[Linux] AudioClip generated by an external process (LMMS) and loaded into the editor has no samples
To reproduce:
0) Download LMMS 1.2, run it and then link it to Unity Editor in Edit->Preferences->LMMS
1) Create a new project
2) Import the scripts in LMMS.zip
3) Import .mmp file
4) In Temp folder, find .wav file that is generated and play it
Expected: It plays a short sound for few seconds
5) Select .mmp file in Editor
6) Play it in Inspector
Actual:
Error: Cannot create FMOD::Sound instance for resource , (Error loading file. )
UnityEditor.AudioUtil:PlayClip(AudioClip, Int32, Boolean)
UnityEditor.AudioClipInspector:PlayClip(AudioClip, Int32, Boolean) (at /home/builduser/buildslave/unity/build/Editor/Mono/Inspector/AudioClipInspector.cs:151)
<..>
Reproduced in 2018.4.0f1, 2019.1.0b2, 2019.3.0a6
Comments (3)
-
JesseSTG
Jun 30, 2020 16:21
Any suggestion on what I can do instead? I'd like to be able to include my LMMS project files (XML files) in my source tree instead of their output (uncompressed WAV files).
-
JesseSTG
Sep 18, 2019 19:22
This also happens on Windows, on Unity 2019.2.5f1. Same error, so I don't think this is Linux-specific.
-
JesseSTG
Jul 24, 2019 19:40
Is there any progress on this? This bug is blocking all work on my LMMS importer.
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
- Popup windows spawn on the incorrect monitor when the Editor is placed near the boundary of scaled monitor next to a monitor with different scaling
- Hidden Tabs do not shift into empty space after closing visible Tabs
- [Android] Application not deployed on a device when "activity-alias" is used in the AndroidManifest
- Shader compile process adds shader ID to the constant buffer name when the word "Globals" is being used in Vulkan
- Audio Mixer Snapshot link to the documentation isn’t working
Resolution Note:
It seems like this (managed audio importer generating/writing clip data) isn't expected to work today, since clip data is stored separately.
It may be possible to make it work with future importer work.