SSL 360° v2.1.12 shipped on 11 August 2026 and made the Harrison strip natively controllable from UC1 and the Plug-in Mixer. UF8 and UF1 reach it too, on the Plug-in Mixer layer. That is the headline.
The release notes underneath it are more useful. Four of the open items in that document concern the Harrison integration specifically, and two of them are not SSL's to fix.
Native control only applies to the second version of the channel strip. A version one instance still reaches the hardware the old way, through 360 Link.
That is a real caveat for anyone buying specifically for hands-on control from the UC1 panel. On Logic or LUNA right now, the integration is partial and the fix sits with someone else's release schedule.
There is a separate Logic entry worth noting too. On Tahoe, the SSL plug-in preset drop-down has a hit-area problem that makes the list hard to open unless you click one particular spot. SSL says it affects many of its own plug-ins along with the Harrison ones, and that Apple has been told.
Pro Tools, Cubase, Studio One and REAPER users are not in that queue. Neither is anyone on Windows, apart from a one-way communication note involving Mixbus.
Harrison plug-ins already had factory maps in there, alongside selected Waves, Universal Audio, Brainworx, and Slate Digital titles. So this was never an unmapped mess for 32C owners. It was a working setup that native support now supersedes.
Its documented ceiling was low. Link hosts VST3 only, passes stereo at most, does not carry MIDI, and cannot load SSL's own 360-enabled plug-ins at all. Plug-ins inside it also cannot load presets from the UC1 hardware, and cannot show an EQ readout on UF1. Metering works properly only if the manufacturer chose to expose the data.
Going native returns every one of those. Presets from the panel, proper metering, the UF1 readout, no stereo cap.
Then read SSL's own comparison one line further. Customizable control maps and parameter names are listed as a Link feature that native plug-ins do not have. If you spent an evening building a UC1 map for the Harrison strip that matched how you work, native support retires it. SSL decides the layout now.
That is a fair trade for most people and an annoying one for a few. Either way, it is worth settling before you retire a map you rely on.
Two of the four Harrison entries are ordinary bugs rather than waiting games, and both are the kind you meet in the first hour.
The first concerns the LED rings. On the mid EQ bands, gain displays on UC1 as a wrap from the left rather than as a pinpoint or a wrap from the center. So the ring is not telling you what it looks like; it is telling you. A small cut and a small boost both read as a short arc from the same end.
Until that changes, treat the mid-band rings as a rough presence indicator only. Take the actual value off the display, or off the screen, where the number is unambiguous.
The second is slower to spot and harder to ignore once you have. Scrolling the UC1 ROUTING menu takes four encoder turns before it moves to the next routing order option. On a controller built around a knob per function, four clicks to advance one item feels wrong every single time you do it.
Neither bug affects audio. Both affect how much you trust the panel, which for a controller is close to the same thing.
The release notes underneath it are more useful. Four of the open items in that document concern the Harrison integration specifically, and two of them are not SSL's to fix.
Native control only applies to the second version of the channel strip. A version one instance still reaches the hardware the old way, through 360 Link.
Logic and LUNA users are still waiting on full integration
SSL's notes say it plainly. The company is waiting on Apple for full Logic Pro compatibility with the Harrison 32C and 360 integration. It expects that fix to arrive with a Logic Pro update. A second entry says the same about LUNA and Universal Audio.That is a real caveat for anyone buying specifically for hands-on control from the UC1 panel. On Logic or LUNA right now, the integration is partial and the fix sits with someone else's release schedule.
There is a separate Logic entry worth noting too. On Tahoe, the SSL plug-in preset drop-down has a hit-area problem that makes the list hard to open unless you click one particular spot. SSL says it affects many of its own plug-ins along with the Harrison ones, and that Apple has been told.
Pro Tools, Cubase, Studio One and REAPER users are not in that queue. Neither is anyone on Windows, apart from a one-way communication note involving Mixbus.
Native control removes the one thing 360 Link did best
360 Link is a free wrapper that hosts a third-party VST3 and presents it to the Plug-in Mixer as a channel strip. You map it yourself by dragging parameters onto UC1 controls, by turning a knob and letting it listen, or by clicking the on-screen control first.Harrison plug-ins already had factory maps in there, alongside selected Waves, Universal Audio, Brainworx, and Slate Digital titles. So this was never an unmapped mess for 32C owners. It was a working setup that native support now supersedes.
Its documented ceiling was low. Link hosts VST3 only, passes stereo at most, does not carry MIDI, and cannot load SSL's own 360-enabled plug-ins at all. Plug-ins inside it also cannot load presets from the UC1 hardware, and cannot show an EQ readout on UF1. Metering works properly only if the manufacturer chose to expose the data.
Going native returns every one of those. Presets from the panel, proper metering, the UF1 readout, no stereo cap.
Then read SSL's own comparison one line further. Customizable control maps and parameter names are listed as a Link feature that native plug-ins do not have. If you spent an evening building a UC1 map for the Harrison strip that matched how you work, native support retires it. SSL decides the layout now.
That is a fair trade for most people and an annoying one for a few. Either way, it is worth settling before you retire a map you rely on.
The routing menu and the mid-band LEDs still misbehave
SSL describes UC1 as knob-per-function channel EQ and dynamics controls, with full bus compressor controls and a moving-coil gain reduction meter in the center section. The Harrison strip carries a four-band EQ, a compressor and a gate, so most of it has somewhere obvious to land.Two of the four Harrison entries are ordinary bugs rather than waiting games, and both are the kind you meet in the first hour.
The first concerns the LED rings. On the mid EQ bands, gain displays on UC1 as a wrap from the left rather than as a pinpoint or a wrap from the center. So the ring is not telling you what it looks like; it is telling you. A small cut and a small boost both read as a short arc from the same end.
Until that changes, treat the mid-band rings as a rough presence indicator only. Take the actual value off the display, or off the screen, where the number is unambiguous.
The second is slower to spot and harder to ignore once you have. Scrolling the UC1 ROUTING menu takes four encoder turns before it moves to the next routing order option. On a controller built around a knob per function, four clicks to advance one item feels wrong every single time you do it.
Neither bug affects audio. Both affect how much you trust the panel, which for a controller is close to the same thing.
