Search Issue Tracker
Fixed in 5.0.X
Votes
0
Found in
5.0.0a16
Issue ID
619029
Regression
No
Observations about naming of effects
Observations about naming of effects.
- All the effects are ending with the word "effect", e.g. "Echo effect, Reverb effect" and etc. Maybe it would make more sense to rename the "Add..." dropdown to "Add effects..." or "Effects..." - and then rename all the effects to "Reverb, Echo, High pass Filter, Low Pass Filter, Flange, Distortion" and etc.
- Question: How is "SFX Reverb" different from a "Reverb"?
- What is the use case for having two distinct effects like "High Pass Simple" and "High Pass" effect? Would an audio designer not just use "High Pass" effect, where there is an extra parameter to tweak/play with? I know from myself (in Live) that I always avoid the simple sampler named "Simpler" and go for the full advanced instrument named "Sampler"
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment