Presswerk 1.1.6 Update Released

[tasmaniandevil]

Hi everyone,

the Presswerk 1.1.6 update has now been released.

Presswerk 1.1.6 comes with CLAP and native silicon AAX support. Next to many fixes and improvements, this update also adds support for displaying the gain reduction meter directly in the host's track meter if the host supports this feature.

Presswerk-116.jpg

As usual, the update is free for existing license holders. Simply download from the product page and install over the old version.

https://u-he.com/products/presswerk/

Cheers,
the u-he crew

---

Improvements

* Supports the latest macOS versions (Sonoma/Sequoia)
* Support for CLAP
* Native Apple silicon support for Pro Tools (AAX)
* VST3 SDK updated to 3.7.8
* Improved GUI performance
* Improved dialog handling
* Added 50% & 60% GUI scaling options
* VST2 > VST3 migration support for hosts using the IPluginCompatibility interface
* Support for gain reduction meter displayed in host mixer (VST3, CLAP, AAX)
* Improved latency compensation (no more dropouts when activating bypass)
* Linux install-script improvements
* Browser: added option to show/hide folders
* Browser: saving search results now supports drag & drop
* Browser: save dialog description and usage fields now scroll while entering text
* Browser: drag & drop folders onto smart folders to assign tags
* Improved parameter automation in Pro Tools
* Registration dialog automatically purges unsupported characters
* Windows installer comes with an uninstaller
* Windows installer remembers last used options
* Windows installer blocks installation to ProgramData location
* Twitter link replaced with Mastodon in u-he menu

Fixes

* Fixed: external sidechain was broken in VST2
* Fixed: VST3 crashes in Digital Performer related to plugin GUI
* Fixed: dialogs could appear behind plugin GUI in Cubase (Windows only)
* Fixed: it was possible to open the same dialog window twice; this could lead to a crash
* Fixed: Windows UI scaling was messing with dialog positioning
* Fixed: using CMD+A in dialogs made the GUI disappear in Logic
* Fixed: aborted preset save operation could lead to wrong metadata being displayed in the inspector
* Fixed: using the "duplicate" option in the browser could crash if permissions were missing
* Fixed: Renoise no longer needs the "enable keyboard" option for menus to work
* Fixed: plugin focus no longer needed for dropdown menus to work (Mac only)
* Fixed: problem when loading the init preset immediately after loading the plugin (Mac only)
* Fixed: plugin stayed mono when using the "Mono > Stereo" option in Logic under native silicon
* Fixed: GUI glitch when switching to smaller GUI size (Pro Tools only)
* Fixed: problem when automating parameters with identical names (Pro Tools only)
* Fixed: preset search input field did not receive mouse input (Pro Tools only)
* Fixed: scroll wheel not working on second display under some conditions (Windows only)
* Fixed: installer now scaled correctly on high-resolution displays (Windows only)
* Fixed: preset overwrite dialog was not showing up (Linux only)
* Fixed: default author was set to preset name in presets (Linux only)
* Fixed: auto-versioning feature wasn't working (Linux only)
* Fixed: right-click preset selection frame wasn't disappearing (Linux only)
* Fixed: input field was empty when editing preset search result (Linux only)
* Fixed: double-click on menus could lead to crash (Linux only)
* Fixed: dialogs always opened at the left edge of the screen (Linux only)
* Fixed: dialogs could be opened multiple times (Linux only)
* Even more small fixes and improvements

Special Notes

* This is the last version that includes VST2 support on Mac, Windows and Linux.
* This is the last version including 32-bit support on Windows.
* AAX and CLAP versions are 64-bit only.

[zvenx]

Thanks Tas.
rsp

[cloudnoize]

Thank you, Tas!

[lunardigs]

Downloads:

Presswerk 1.1.6 RC1 16947 Mac
Presswerk 1.1.6 RC1 16947 Windows
Presswerk 1.1.6 RC1 16947 Linux

Hey, the links above do not work for me?

[tasmaniandevil]

Hey, the links above do not work for me?

They are the same kind of link as always.
And they do work just fine over here.
Maybe try a different browser?

[robisme]

Great. I couldn't wait to use it all as clap plugins. When it's officially released, will it seamlessly be replaced in my projects, or shouldn't I wait before I change all the instances from vst3 to clap in my templates?

[tasmaniandevil]

Iirc Bitwig are in the process of including a feature to automatically replace VST3s with CLAP in existing projects. But I am not sure if it's in the current Bitwig version yet. And I am also not sure if we still need to implement this on our side as well, or if it will just work once the host supports it.

[robisme]

Iirc Bitwig are in the process of including a feature to automatically replace VST3s with CLAP in existing projects. But I am not sure if it's in the current Bitwig version yet. And I am also not sure if we still need to implement this on our side as well, or if it will just work once the host supports it.

I gave up on Bitwig, currently I use Reaper.

[tasmaniandevil]

Reaper most likely doesn't support this yet, as the feature to replace VST3 with CLAP is pretty new, or might still be in development (not sure).

[lunardigs]

Hey, the links above do not work for me?

They are the same kind of link as always.
And they do work just fine over here.
Maybe try a different browser?

Ok, sorry to bother. It works now, same browser; no idea ... Thanks!

[OdoSendaidokai]

Reaper most likely doesn't support this yet, as the feature to replace VST3 with CLAP is pretty new, or might still be in development (not sure).

Was thinking when would I use that feature. Normally I select by purpose if I want use VST3 or CLAP. Do you know in which situations this could be helpful?

[tasmaniandevil]

Was thinking when would I use that feature. Normally I select by purpose if I want use VST3 or CLAP. Do you know in which situations this could be helpful?

If users want to switch from one format to another, e.g. if they stop installing VST3 versions, then the host could detect that there is an equivalent CLAP version available. Old projects which were created with VST3 would still work, they would simply load the CLAP plugin and all the plugin settings are loaded in the CLAP version.
Easy and painless transition for the user.

[robisme]

Wouldn't a python script replace the plugin id in a project file for exemple. I think it's possible in the Bitwig's .dawproject file, as it is only an xml in a zip. For Reaper it might be too, as .PPR files are txt.
or a simple ctrl+h?

[Urs]

Wouldn't a python script replace the plugin id in a project file for exemple. I think it's possible in the Bitwig's .dawproject file, as it is only an xml in a zip. For Reaper it might be too, as .PPR files are txt.
or a simple ctrl+h?

This won't be needed, we hope.

For now, all plug-in formats are available, and will be, probably for years to come.

Once a file format is not available anymore (e.g. VST2 will be phased out for apparent reasons), we reckon that most - if not all - hosts will support migration paths to VST3 or CLAP by the time it's needed.

That said, while our official installers will come without VST2 from Q2 2025, installers with an identical version including VST2 support will remain available in our release archives. (One of the major reasons we spent the past few years updating old and new products is to have a current VST2 version one last time, before we need to fade it out)

[tasmaniandevil]

The Presswerk 1.1.6 update has now been released. I've updated the first post accordingly.
The release version is newer than the RC that was posted here, so please download the official release version from the product page.