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

[dorremifasol]

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!

The VST3 plugin loads and shows correctly but as soon as I press the play button I get the following message:

"A serious error has occurred inside the plug-in 'Presswerk'.
WaveLab Pro could control it, but it would be best to save your work and restart
WaveLab Pro."

[Urs]

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.

That's a good idea. I'll check if that's a viable option, we would need the system pasteboard while currently we always use internal handling of copy/paste.

[Urs]

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.

That's a good idea. I'll check if that's a viable option, we would need the system pasteboard while currently we always use internal handling of copy/paste.

We have a pretty unconventional idea on handling this which requires less work than anything else. We would create a backwards compatible version using the old ID. You'd open your projects with this version and behind each instance of Presswerk VST2 you'd insert a VST3. On the UI of the VST2 you'd find a button labelled "send settings via audio". Clicking this would then send a short (very quiet) noise burst containing the preset in the audio stream. The adjacent VST3 version would read that modem-style noise burst and set its parameters accordingly. In other words, we'd bring back vintage data tape in a modern take. Then you remove the VST2 instances and you're done.

We'll try this first and see if/how it works.

[dorremifasol]

We have a pretty unconventional idea on handling this which requires less work than anything else. We would create a backwards compatible version using the old ID. You'd open your projects with this version and behind each instance of Presswerk VST2 you'd insert a VST3. On the UI of the VST2 you'd find a button labelled "send settings via audio". Clicking this would then send a short (very quiet) noise burst containing the preset in the audio stream. The adjacent VST3 version would read that modem-style noise burst and set its parameters accordingly. In other words, we'd bring back vintage data tape in a modern take. Then you remove the VST2 instances and you're done.

We'll try this first and see if/how it works.

Thanks Urs, that would be great. But I think it would involve some additional input processing to detect the data burst start, just for that case only. Maybe it would be even easier if both the old ID VST2 and the new VST3 version had options hidden in the u-he logo sub menu to export and import the parameters using the system clipboard. That's how I would try to do it at least...

[Urs]

We have a pretty unconventional idea on handling this which requires less work than anything else. We would create a backwards compatible version using the old ID. You'd open your projects with this version and behind each instance of Presswerk VST2 you'd insert a VST3. On the UI of the VST2 you'd find a button labelled "send settings via audio". Clicking this would then send a short (very quiet) noise burst containing the preset in the audio stream. The adjacent VST3 version would read that modem-style noise burst and set its parameters accordingly. In other words, we'd bring back vintage data tape in a modern take. Then you remove the VST2 instances and you're done.

We'll try this first and see if/how it works.

Thanks Urs, that would be great. But I think it would involve some additional input processing to detect the data burst start, just for that case only. Maybe it would be even easier if both the old ID VST2 and the new VST3 version had options hidden in the u-he logo sub menu to export and import the parameters using the system clipboard. That's how I would try to do it at least...

Both ways are feasable.

The detection code would require less than a millionth part of Presswerk's CPU consumption. It would only have to compare the first three samples of an incoming audio buffer to virtually always bypass, except for, say, once in a year where it checks a fourth sample.

[comfortablynick]

Adding preset copy/paste would be great anyway! I love that feature in Valhalla and TDR plugins.

Thanks for working on this issue! I had written a script to edit my Reaper project files to change the VST ID, which worked as a viable workaround but was a pain in the butt!

Nick

[Mmmmarcus]

When you say public beta, does this mean Presswerk is available for people who don't actually own Presswerk since before? Or do you need a license to use this as a full version?

[EvilDragon]

You do need a license to use it as a full version, that's a given.

[Mmmmarcus]

You do need a license to use it as a full version, that's a given.

Alright, thanks. I do know they handed out serials when they did the public beta before releasing Presswerk. But I missed out on it then. Seems like quite an interesting plugin.

[#rob]

I do know they handed out serials when they did the public beta before releasing Presswerk.

Uhm no, we didn't.

We already had the copy protection mechanism built in when Presswerk went public beta prior to its release, so we provided a single free license that everybody could use to participate and evaluate. Obviously, this single public beta serial number is no longer active and will not work any longer, since Presswerk is long out of its public beta days and can already be purchased from our web store.

But at no point did we give out free licenses for Presswerk's full version to the public.

In this respect, "public beta" means that we don't restrict the testing to our few internal beta testers anymore and that anyone interested is welcome to participate. It doesn't matter if you already own Presswerk or not, because the public beta version will work in demo mode without time or feature limitations (apart from occasional vinyl noises) just like any of our other demo versions.

[Musical Gym]

found it

[crizdee]

Hi,

Just a quick note to say the new build is working good so far in Pro Tools 10 HD TDM Lion. AAX32

The link is now working much better.

I'll be trying more over the next few days so will let you know if i find anything relevant.

P.S. would kill for a TDM version

Chris

[MrMoneypenny]

Hi Urs & support,

thanks for your work on Presserk. I did convert my AL9 projects on my laptop, worked fine.
But on my Desktop the convert process gets stuck.

Are there any files in the AL9 Folder, that should not be in there? Like movie files or anything like this?

I tried a few folders, alwasy the same behaviour: process stucks.

Best Bastian

[DaddyAdv]

Same for me with L9 files under Win7: process runs fine for selected single files, but larger batches get stuck at certain files. Still trying to find a failure mechanism.

[DaddyAdv]

GOT IT:
The file conversion gets stuck if the directory and/or filename name contains an umlaut (ä,ü,ö).

When changing the umlaut to a,o,u it works.