Voxengo Sound Delay 1.12 Free (Win/Mac)
05.2022 | 38 MB
Sound Delay is an auxiliary multi-channel signal delaying AAX, AudioUnit and VST plugin for professional sound and music production applications. You may specify delay time in both milliseconds and samples, with a high level of precision. This plugin – being technical in its purpose – provides a basic signal delaying function only, without signal feedback or modulation capabilities.
Sound Delay also features internal mid/side encoding and decoding, and allows you to delay mid and side channels independently.
Features & Compatibility
Sample-accurate delaying
Millisecond-accurate delaying
Up to 3 seconds overall delay
Stereo and multi-channel processing
Internal channel routing
Channel grouping
Mid/side processing
Preset manager
Undo/redo history
A/B comparisons
Contextual hint messages
All sample rates support
User interface color schemes
Resizable user interface
Retina and HighDPI support
Compatibility
This audio plugin can be loaded in any audio host application that conforms to the AudioUnit, AAX, or VST plugin specification.
This plugin is compatible with Windows (32- and 64-bit Windows XP, Vista, 7, 8, 10 and later version, if not announced as unsupported) and macOS (10.11 and later version, if not announced as unsupported) computers (2.5 GHz dual-core or faster processor with at least 4 GB of system RAM required). A separate binary distribution file is available for each target computer platform and audio plugin specification. If supported on a specific processor, the plugin may internally utilize AVX2-optimized code.
Compatible Windows and macOS plugin software: Cubase, Logic Pro, ProTools, Ableton Live, Reaper, OBS, Presonus Studio One, FL Studio, Cakewalk, Nuendo, WaveLab, GarageBand, Vegas, SoundForge, Audition, Samplitude, Digital Performer, Mixcraft, Bitwig Studio, Edius, others. Note that for Logic Pro you should download the AU,AAX package, not VST.
If you cannot get plugin component to work on macOS, you have to logout from the system and login again, it's a known issue not caused by plugin's own bug.