nyVERB 1.1.0 adds a universal macOS build for Intel and Apple Silicon Macs while keeping macOS 13 as the minimum system version. For anyone still making records on an Intel machine, this is more than an installer tidy-up. Version 1.0.1 was Apple Silicon only, so those Macs were excluded before a DAW even had a chance to scan the plug-in.
noizplay's main product page has not caught up with the newer build at the time of writing. It still says Apple Silicon only, while the 1.1.0 release information identifies the Mac download as universal for Intel and Apple Silicon. Checking the version number matters here because the older requirement text describes a different binary.
Intel support is not a free pass for every old Mac. nyVERB still requires macOS 13 or newer, so a machine stuck on Monterey or an earlier release remains below the documented minimum. For an Intel owner, nyVERB 1.1's universal Mac build removes the processor barrier while leaving the operating system requirement exactly where it was.
Rosetta does not rescue the first release on Intel hardware. Apple uses Rosetta on Apple Silicon Macs to translate Intel software, not the other way around. An arm64-only plug-in cannot become Intel-compatible because somebody installs Rosetta or changes a DAW preference.
nyVERB also keeps both Mac plug-in formats in version 1.1.0. AU and VST3 are available, which means the host still has to support and successfully scan the format you install. Processor support only gets you past one checkpoint.
A failed scan on Intel now deserves a more specific diagnosis. Confirm the Mac runs macOS 13 or later, confirm nyVERB is actually version 1.1.0, then check whether the DAW is finding the installed AU or VST3. An old 1.0.1 copy left in a plug-in folder can make the whole situation look stranger than it is.
Installation and plug-in validation are separate events. macOS can accept the installer while Logic, Ableton Live, Reaper, or another host still needs to discover and validate the AU or VST3 afterward. Mixing those failures leads to bad fixes.
Intel users who tried nyVERB before 1.1.0 should pay attention to the actual copy their DAW loads. Plug-in caches and separate AU and VST3 locations can leave an older binary hanging around after a new installer has run. Rebooting five times will not turn version 1.0.1 into a universal build.
The newer installer also removes some guesswork from distribution. Version 1.1.0 arrives as a notarized disk image on Mac instead of relying on the earlier download arrangement, while Windows moved from a ZIP to a signed installer. On Intel, the useful part is still the binary inside the Mac package, not the prettier way it arrives.
Older studio Macs often live for years because the interface, drivers, sessions, and plug-ins around them already work. Upgrading the operating system just for one reverb can disturb that balance, so Intel compatibility should not be read as pressure to update a stable production box. nyVERB 1.1.0 supports Intel, but it does not lower its macOS requirement to meet older machines halfway.
The free demo is useful here because it tests the machine you actually own. Noizplay provides the full plug-in without a time limit, with a brief periodic fade until a license is entered, so you can check installation, scanning, playback, and session recall before paying. A universal label tells you which processors are inside the build, not whether the rest of your studio setup will cooperate.
If an Intel Mac meets the macOS 13 requirement and the current 1.1.0 AU or VST3 loads, the old Apple Silicon-only restriction is gone. If the same Mac cannot run macOS 13, the new universal binary does not create a supported route around that limit.
noizplay's main product page has not caught up with the newer build at the time of writing. It still says Apple Silicon only, while the 1.1.0 release information identifies the Mac download as universal for Intel and Apple Silicon. Checking the version number matters here because the older requirement text describes a different binary.
Intel support is not a free pass for every old Mac. nyVERB still requires macOS 13 or newer, so a machine stuck on Monterey or an earlier release remains below the documented minimum. For an Intel owner, nyVERB 1.1's universal Mac build removes the processor barrier while leaving the operating system requirement exactly where it was.
The universal build removes the architecture block
Apple's definition of a universal macOS binary is straightforward. A native Intel and Apple Silicon build carries executable code for both x86_64 Intel processors and arm64 Apple Silicon processors, and macOS runs the slice made for the machine underneath it. An Intel Mac is no longer being handed an Apple Silicon-only nyVERB binary it cannot execute.Rosetta does not rescue the first release on Intel hardware. Apple uses Rosetta on Apple Silicon Macs to translate Intel software, not the other way around. An arm64-only plug-in cannot become Intel-compatible because somebody installs Rosetta or changes a DAW preference.
nyVERB also keeps both Mac plug-in formats in version 1.1.0. AU and VST3 are available, which means the host still has to support and successfully scan the format you install. Processor support only gets you past one checkpoint.
A failed scan on Intel now deserves a more specific diagnosis. Confirm the Mac runs macOS 13 or later, confirm nyVERB is actually version 1.1.0, then check whether the DAW is finding the installed AU or VST3. An old 1.0.1 copy left in a plug-in folder can make the whole situation look stranger than it is.
The new installer cleans up first-run friction
Version 1.1.0 moves the Mac download to a notarized disk image containing an installer. Apple describes notarization as a check for known malicious content and code-signing problems, with Gatekeeper able to verify the resulting ticket when downloaded software is opened. It is useful protection, but it is not a certificate saying every DAW will load every plug-in without complaint.Installation and plug-in validation are separate events. macOS can accept the installer while Logic, Ableton Live, Reaper, or another host still needs to discover and validate the AU or VST3 afterward. Mixing those failures leads to bad fixes.
Intel users who tried nyVERB before 1.1.0 should pay attention to the actual copy their DAW loads. Plug-in caches and separate AU and VST3 locations can leave an older binary hanging around after a new installer has run. Rebooting five times will not turn version 1.0.1 into a universal build.
The newer installer also removes some guesswork from distribution. Version 1.1.0 arrives as a notarized disk image on Mac instead of relying on the earlier download arrangement, while Windows moved from a ZIP to a signed installer. On Intel, the useful part is still the binary inside the Mac package, not the prettier way it arrives.
macOS 13 remains the hard floor
The universal build widens nyVERB's hardware support, but Ventura remains the line on the floor. A 64-bit Intel processor alone does not qualify a system. The Mac must also run macOS 13 or newer, and the DAW has to remain usable on that operating system.Older studio Macs often live for years because the interface, drivers, sessions, and plug-ins around them already work. Upgrading the operating system just for one reverb can disturb that balance, so Intel compatibility should not be read as pressure to update a stable production box. nyVERB 1.1.0 supports Intel, but it does not lower its macOS requirement to meet older machines halfway.
The free demo is useful here because it tests the machine you actually own. Noizplay provides the full plug-in without a time limit, with a brief periodic fade until a license is entered, so you can check installation, scanning, playback, and session recall before paying. A universal label tells you which processors are inside the build, not whether the rest of your studio setup will cooperate.
If an Intel Mac meets the macOS 13 requirement and the current 1.1.0 AU or VST3 loads, the old Apple Silicon-only restriction is gone. If the same Mac cannot run macOS 13, the new universal binary does not create a supported route around that limit.
