u-he

Urs · Post by **Urs** » Tue Mar 15, 2016 5:59 pm

Hi all,

Bad news: We messed up, big time!

Good news: We have a solution (+ Mac users aren't affected)

There's a bug in the current version of Presswerk VST2 Win: It uses a wrong VST2 plug-in ID. This ID helps hosts to identify plug-ins. As a result, project files couldn't be swapped cross platform in some hosts. Unfortunately we noticed this only after we released Presswerk V1.1. First it wasn't much of a problem, a mere oversight, but soon more and more people ran into issues. Our recent customer survey shows that hundreds of Presswerk users are potentially affected. We need to fix this once and for all!

Here's how: We'll switch the plug-in ID on VST2 Win. This will break existing projects in some hosts. So we're offering a tool that can update project files of affected hosts (Live 8 or newer, recent Cubase, recent Sonar, Studio One) to work with the correct ID. That "Project Converter" is available for Win and Mac and it's part of the download.

If that isn't a solution for you, we're offering an alternative: VST3. If your host supports it, keep your old Presswerk V1.1.0 VST2 and use the new VST3 for your next projects.

A few Presswerk users will have to stick to the old version, or render their existing projects one last time before upgrading, e.g. if they have parameter automation. Or, wait it out until their host supports VST3. Eventually they will.

We've prepared a pdf guide to show the options, and we've also set up a webpage with in-depth information.

We are extremely sorry for the inconvenience this causes (I had sleepless nights over this). I think though we came up with the best possible solution in the long run. It took some time to get there because we needed both VST3 support and the project conversion tool to be ready for this.

Please give it a go, we're hoping to catch problems as soon as possible and make the transition as flawless as possible for the people who are affected!

download Presswerk 1.1.1 Mac (rev 4332) AAX/AU/VST2/VST3
download Presswerk 1.1.1 Win (rev 4332) AAX/VST2/VST3

Please let us know what you find, don't hesitate to contact support at u-he dot com for issues and post any question you have in this thread.

Also, this is our first public beta test of our VST3 rewrite. Internal tests were very positive

Thanks,

- Urs

P.S.: Bitwig Studio is affected too, but they are releasing a fix built into it soon.

P.P.S.: There'll be a full list of fixes and stuff, but we would like to focus on the main issue right now.

SJ_Digriz · Post by **SJ_Digriz** » Tue Mar 15, 2016 6:18 pm

EDIT: never mind, I just needed to read the entire post. I'll let you know what I find using the VST3 version.

Alexander_D · Post by **Alexander_D** » Tue Mar 15, 2016 8:48 pm

Should I install this if I already in Mac users group and use it as AU?

zvenx · Post by **zvenx** » Tue Mar 15, 2016 8:58 pm

Thanks. off to test vst3.
rsp

zvenx · Post by **zvenx** » Tue Mar 15, 2016 9:18 pm

IS there a trick to get this to duck in Cubase in the alternate view modes? Beyond the usual, use vst3, enable side chain, and ensure sidechain is set to external (which may be the part I am missing.. is this only available in the main view not the alternate views?

thanks
rsp

sascha · Post by **sascha** » Wed Mar 16, 2016 7:45 am

Feature set is unchanged: For sidechaining, use the main view.

zvenx · Post by **zvenx** » Wed Mar 16, 2016 11:18 am

sascha wrote:Feature set is unchanged: For sidechaining, use the main view.

Thanks
rsp

dorremifasol · Post by **dorremifasol** » Wed Mar 16, 2016 2:02 pm

Unfortunately the VST3 version doesn't seem to work in the new Wavelab Pro 9

abique · Post by **abique** » Wed Mar 16, 2016 2:07 pm

dorremifasol wrote:Unfortunately the VST3 version doesn't seem to work in the new Wavelab Pro 9

Can you explain a bit what does not work? Is the UI not showing up? Are the parameters not showing up in the host? No sound?

Thank you!

david.beholder · Post by **david.beholder** » Wed Mar 16, 2016 11:26 pm

Urs wrote:HSo we're offering a tool that can update project files of affected hosts (Live 8 or newer, recent Cubase, recent Sonar, Studio One) to work with the correct ID. That "Project Converter" is available for Win and Mac and it's part of the download.

Does it mean that Reaper is not affected?

EvilDragon · Post by **EvilDragon** » Thu Mar 17, 2016 7:59 am

Yep, Reaper is not affected.

david.beholder · Post by **david.beholder** » Thu Mar 17, 2016 8:05 am

EvilDragon wrote:Yep, Reaper is not affected.

mind to share details? reaper is not using vst id?

sascha · Post by **sascha** » Thu Mar 17, 2016 8:09 am

Details are given comprehensively in the embedded docs, i.e. with all info needed, and in-depth explanations of what is affected and technical details. Everybody please read.

Urs · Post by **Urs** » Thu Mar 17, 2016 8:14 am

david.beholder wrote:
EvilDragon wrote:Yep, Reaper is not affected.
mind to share details? reaper is not using vst id?

Hosts that are not affected seem to identify plug-ins by a mix out of ID, dll path/filename and name reported by the plug-in. Such that, if two of those three are the same, it'll just work.

We of course don't know for sure how they work, but we tested many. Out of the many we tested, Cubase, Sonar, Studio One and Live couldn't find the updated Presswerk. Neither could Bitwig Studio, but people at Bitwig generously added a workaround that'll be available soon.

dorremifasol · Post by **dorremifasol** » Fri Mar 18, 2016 9:37 am

It would be really great if there was a way to copy the settings from a VST2 instance to a VST3 instance. Any ideas about how to do this? That would help in converting old projects too.

u-he

KVR Audio

Presswerk 1.1.1.4332 beta (VST3 + ID Fix + Project Converter)