Illegal property override: Value “/Sound/MSS_PlayRandom_Loop_Preset2.MSS_PlayRandom_Loop_Preset2.OutputFormat” has an override of “Stereo” (default “Mono”) for property “/Script/MetasoundEngine.MetaSoundSource:OutputFormat” on an instance of “/Script/MetasoundEngine.MetaSoundSource”. (ValkyrieValidator_Properties) Fix: Reset Property to Default
Please select what you are reporting on:
Creative
What Type of Bug are you experiencing?
Audio
Steps to Reproduce
after 40.00 update, this audio preset, attached to a prefab as an audio component, started reporting validation issues. though fine before
Expected Result
playing audio as it was before
Observed Result
after 40.00 update, this audio preset, attached to a prefab as an audio component, started reporting validation issues. though fine before. Can still Launch Session
Hello, is the output format something you were able to modify directly? Could you give us the exact repro steps setting up a new sound to get the validation error?
We continue to experience this bug and are concerned that with v41.00, these warnings will become Errors meaning we’ll not be able to use metasounds in our project. How do we solve this?
Metasound Source Assets are read-only, with very limited options available for us through subclassing them.
The options available for us are working fine without issues, but there are internal configs that are not exposed and we can’t edit (this Output mode Stereo/Mono) is one of them.
We can’t edit that option, it is not exposed and marked as “read-only”. Just using the source as normally wanting in any scenario will trigger that validation warning (which will be an error in v41.00). We can’t manually fix it due to being not exposed, and even we use the Fix-up tool, it does nothing since the read-only state of it.
I guess this was caused due to the default value of the internal metasound class being changed some updates ago. But the UEFN validation tool still checking for the old value, probably was forgotten to get updated to match the new internal default value, causing the error described above.
@OKomili@Sprintermax
This property is allowed to be non-default (even though it is hidden) as of 41.00, so the validation tool should stop complaining about it when this goes live.
