Harmony Pro 1.0.0 requires macOS 12 Monterey or later on Mac, while its Windows installer targets x64 systems. That specification is narrower than the Mac-and-Windows label attached to Harmony Pro’s free chord assistant. A DAW only loads software built for its platform and plug-in format.
On macOS, the current 45.04 MB package includes AU, standard VST3, and a VST3 variant labeled for Ableton. It supports arm64 and x86_64, providing native Apple Silicon and Intel compatibility through one installer. The 10.02 MB Windows package supplies standard and Ableton Live VST3 variants, targets x64, and requires no separate library download.
The browser version lets you try Harmony Pro without installing the desktop package on that exact computer. That test cannot prove AU or VST3 compatibility, because a browser does not exercise your DAW’s plug-in scanner or validation process.
Windows users face a different boundary. The published installer is an x64 executable, and the developer does not document a 32-bit or native Arm64 package. Do not treat the x64 label as a promise of native Arm support.
The lack of a separate Windows library download removes one common setup chore, but it does not prove that every 64-bit host will accept the plug-in. The host must support VST3 and complete its own validation or scanning process. Likewise, the small installer size says nothing about whether an older DAW understands the installed format.
Ableton documents a practical MIDI difference, since AU devices lack direct MIDI output in Live while VST3 devices provide it. That distinction may affect later routing, so choosing AU merely because you are on a Mac can close off a workflow that VST3 preserves.
Harmony Pro’s download page explicitly lists a separate Ableton VST3 variant on both platforms, yet it does not explain the technical difference. Its presence matters during troubleshooting because the developer treats Live as a distinct target rather than an ordinary VST3 host.
VST3 uses defined system folders rather than the loose custom-folder habits associated with older VST2 plug-ins. On Windows, hosts expect 64-bit VST3 components in the shared VST3 folder under Program Files and Common Files. On macOS, VST3 and AU components belong in separate system plug-in folders, and neither should be dropped inside the DAW’s application directory.
In Live, confirm that the VST3 system source is enabled, or enable Audio Units when you deliberately installed the AU version on Mac. Turning the relevant source off and on can trigger a new scan, while holding Alt or Option during Rescan starts a deeper pass. Pointing VST2 and VST3 settings at the same directory creates confusion rather than finding more software.
Logic Pro can reset and rescan a selected Audio Unit, while a full Audio Unit reset makes it validate every component after reopening. FL Studio uses Manage plugins and Find installed plugins, then places newly verified software under the relevant VST3 or Audio Units category.
A failed scan should send you back to three facts before you reinstall anything. Confirm that the machine meets the operating-system and processor requirements, that you installed the format your host accepts, and that the host is scanning the standard location. Repeatedly running the same installer cannot correct a disabled plug-in source.
Apple Silicon adds one final host-side wrinkle. FL Studio maintains separate scan states for its native Apple Silicon and Rosetta modes, so changing runtime mode can require another scan even though Harmony Pro already provides an arm64 component. A plug-in visible in one mode but absent in the other points to the host’s database, not automatically to a broken Harmony Pro package.
On macOS, the current 45.04 MB package includes AU, standard VST3, and a VST3 variant labeled for Ableton. It supports arm64 and x86_64, providing native Apple Silicon and Intel compatibility through one installer. The 10.02 MB Windows package supplies standard and Ableton Live VST3 variants, targets x64, and requires no separate library download.
The browser version lets you try Harmony Pro without installing the desktop package on that exact computer. That test cannot prove AU or VST3 compatibility, because a browser does not exercise your DAW’s plug-in scanner or validation process.
The operating system sets a firm entry point
The Mac requirement has two parts that are easy to blur together. Apple Silicon and Intel processors are supported, but the computer must still run Monterey or a later macOS release. An Intel Mac that cannot move beyond Big Sur therefore sits below the documented operating-system minimum even though its processor architecture appears on the supported list.Windows users face a different boundary. The published installer is an x64 executable, and the developer does not document a 32-bit or native Arm64 package. Do not treat the x64 label as a promise of native Arm support.
The lack of a separate Windows library download removes one common setup chore, but it does not prove that every 64-bit host will accept the plug-in. The host must support VST3 and complete its own validation or scanning process. Likewise, the small installer size says nothing about whether an older DAW understands the installed format.
Your DAW decides which installed format matters
Logic Pro validates Audio Units, making Harmony Pro’s AU component the relevant choice there. Supported Windows hosts must load its VST3 build because no Windows AU version is published. Ableton Live on macOS can load either format, but cross-platform projects need VST3 because Audio Units do not load on Windows.Ableton documents a practical MIDI difference, since AU devices lack direct MIDI output in Live while VST3 devices provide it. That distinction may affect later routing, so choosing AU merely because you are on a Mac can close off a workflow that VST3 preserves.
Harmony Pro’s download page explicitly lists a separate Ableton VST3 variant on both platforms, yet it does not explain the technical difference. Its presence matters during troubleshooting because the developer treats Live as a distinct target rather than an ordinary VST3 host.
VST3 uses defined system folders rather than the loose custom-folder habits associated with older VST2 plug-ins. On Windows, hosts expect 64-bit VST3 components in the shared VST3 folder under Program Files and Common Files. On macOS, VST3 and AU components belong in separate system plug-in folders, and neither should be dropped inside the DAW’s application directory.
A missing plug-in usually means discovery failed
Installation and discovery are separate events, so close the DAW before installing, reopen it afterward, and allow the first scan to finish. Ableton notes that background indexing can leave newly installed devices temporarily absent for several minutes.In Live, confirm that the VST3 system source is enabled, or enable Audio Units when you deliberately installed the AU version on Mac. Turning the relevant source off and on can trigger a new scan, while holding Alt or Option during Rescan starts a deeper pass. Pointing VST2 and VST3 settings at the same directory creates confusion rather than finding more software.
Logic Pro can reset and rescan a selected Audio Unit, while a full Audio Unit reset makes it validate every component after reopening. FL Studio uses Manage plugins and Find installed plugins, then places newly verified software under the relevant VST3 or Audio Units category.
A failed scan should send you back to three facts before you reinstall anything. Confirm that the machine meets the operating-system and processor requirements, that you installed the format your host accepts, and that the host is scanning the standard location. Repeatedly running the same installer cannot correct a disabled plug-in source.
Apple Silicon adds one final host-side wrinkle. FL Studio maintains separate scan states for its native Apple Silicon and Rosetta modes, so changing runtime mode can require another scan even though Harmony Pro already provides an arm64 component. A plug-in visible in one mode but absent in the other points to the host’s database, not automatically to a broken Harmony Pro package.
