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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Add comment