A gorgeous new granular delay by Audio Damage -

[noiseresearch]

Wonder what beta testers are doing today? Loading a plugin, making three presets and reporting it's fine? I mean... how is this possible? How can this bug not pop up while testing?

[noiseresearch]

For many of their plugins, the VST3 version doesn't save the GUI scale (should be a global preference ideally IMO).

That's true of all Audio Damage effects as far as I recall. It recalls the size per instance, per session. But when you reopen the session, the plugin always goes back to the default size. I agree it's annoying and would much prefer they allowed you to store current as default, or just saved the size per instance (and not also per session). It's been this way for so long I don't expect it to change.

Really? Ouch! Damn the delay sounds so good. I never had a problem with the support but if there are some drawbacks which can't be ironed out that's a bummer

[ThomasHelzle]

For many of their plugins, the VST3 version doesn't save the GUI scale (should be a global preference ideally IMO).

That's true of all Audio Damage effects as far as I recall. It recalls the size per instance, per session. But when you reopen the session, the plugin always goes back to the default size. I agree it's annoying and would much prefer they allowed you to store current as default, or just saved the size per instance (and not also per session). It's been this way for so long I don't expect it to change.

It's actually quite erratic for me - I just tried the ones I have installed.
Here is the behaviour I see:

-> Other Desert Cities: VST2 saves the size, VST3 doesn't.
-> Dubstation 2: doesn't save the GUI size in either version (also some other details like the preset name and the setting to ignore the mix value).
-> Axon 2: VST2 saves the size, VST3 doesn't.
-> Quanta: Both versions save the GUI size correctly.
-> Enso: VST2 saves the size, VST3 doesn't.

I save a default preset in Bitwig studio with the GUI scaled to max to have each new instance at full size on my 4k monitor, but this doesn't work for those who don't save it at all of course.
ATM I use the VST2 versions which mostly save the size, but in the long run it should just work in any version. Seems like a silly thing to get wrong to me.

Cheers,

Tom

[Dirtgrain]

VST3 has been taking a dump a lot for me lately in Live 11--Zynaptiq, Blue Cat Audio, HY-Plugins (crashing and not opening when opening new project). Zynaptiq told me this is an issue with Ableton. Not sure if this is relevant, but I thought it might be.

[mholloway]

Wonder what beta testers are doing today? Loading a plugin, making three presets and reporting it's fine? I mean... how is this possible? How can this bug not pop up while testing?

I'd be willing to bet that the Audio Damage 'beta testing team' consists of... the two guys who own and run Audio Damage, the company

[experimental.crow]

my rule of thumb for Audio Damage plug-ins:

if you like it for what it is right now , then you should get it ...
they do quality work ...

if you like it for what it could become , prepare for a game of chance ...
i simply cannot get a read on how much they listen to customer input ...
updates and feature additions seem sporadic ...

ymmv on customer service ; some people have had issues , others not so much ...

[Funkybot's Evil Twin]

VST3 has been taking a dump a lot for me lately in Live 11--Zynaptiq, Blue Cat Audio, HY-Plugins (crashing and not opening when opening new project). Zynaptiq told me this is an issue with Ableton. Not sure if this is relevant, but I thought it might be.

As a rule, I never use VST3 if VST2 is an option. VST3 plugins always seem to be the buggier versions. No one implements sample accurate automation in VST3, there's other ways to suspend processing on silence using VST2... There's no practical benefit to VST3 over VST2 but VST3 is generally the format with the large, format-specific bugs. And by that I mean, sometimes there's a bug in the code that breaks functionality regardless of plugin format...but when you read release notes you'll see a lot of VST3 specific bugs getting fixed that don't have VST2 counterparts.

[Michael99]

It's definitely a really nice sounding effect - I'm patiently waiting for the iOS version to be released right now.

[fairlyclose]

no license transfers - will wait til plugin boutique have it on sale

[Kypresso]

Ya, I'm not wrong. I said that they still allowed transfers after switching websites which they did. Then in 2017 they went NFR and apparently didn't notify customers. Bait and switch. Now go away and try and find plugins with cramping or aliasing or whatever you need to amuse yourself.

No need to be rude. You didn't read the thread from 2014 did you? License transfers were already unavailable then.

viewtopic.php?f=6&t=489038&p=6853467&hi ... R#p6853467

You keep saying 2014 but the thread is actually from 2017, it even shows that date on the snippet you posted.

[Raddler1]

This delay is really special, but because I suck with anything un-synced, I'm finding the cactus and mirage algorithms not very useful. Things get messy fast as I change the speed of the tape heads, I can't get anything in time. Total train wreck.

Not a huge fan of the reverse either so I'm left with 3 out of 6 useable algorithms. But, it's almost still worth buying because of the amazing sound and effortless tweak-ability.

[thecontrolcentre]

Ya, I'm not wrong. I said that they still allowed transfers after switching websites which they did. Then in 2017 they went NFR and apparently didn't notify customers. Bait and switch. Now go away and try and find plugins with cramping or aliasing or whatever you need to amuse yourself.

No need to be rude. You didn't read the thread from 2014 did you? License transfers were already unavailable then.

viewtopic.php?f=6&t=489038&p=6853467&hi ... R#p6853467

You keep saying 2014 but the thread is actually from 2017, it even shows that date on the snippet you posted.

My mistake. I did say it was 4 years ago originally (2017) but was contradicted.

AD NFR policy is at least 4 years old (perhaps more). There was a stink about it at the time. It happened when they moved to a new web address. I have seen a few unregistered AD codes for sale here, but no transfers.

[collider]

I sold all my Audio Damage stuff maybe 2 years (!!!) ago.
I received an unfriendly message and they got transferred.
I still receive all the updates per email and could still use the plugins, but I won't.

Never Audio Damage again. Never.

[Biome_Digital]

This delay is really special, but because I suck with anything un-synced, I'm finding the cactus and mirage algorithms not very useful. Things get messy fast as I change the speed of the tape heads, I can't get anything in time. Total train wreck.

Not a huge fan of the reverse either so I'm left with 3 out of 6 useable algorithms. But, it's almost still worth buying because of the amazing sound and effortless tweak-ability.

It's that slow train-wreck sound I loved about these!

You really just need Valhalla delay by the sounds of it.

[Raddler1]

This delay is really special, but because I suck with anything un-synced, I'm finding the cactus and mirage algorithms not very useful. Things get messy fast as I change the speed of the tape heads, I can't get anything in time. Total train wreck.

Not a huge fan of the reverse either so I'm left with 3 out of 6 useable algorithms. But, it's almost still worth buying because of the amazing sound and effortless tweak-ability.

It's that slow train-wreck sound I loved about these!

You really just need Valhalla delay by the sounds of it.

I like that slow effect too, but i can't figure out a practical workflow to keep it in time. I basically tweak till it kinda sounds right. Open to advice.

I prefer this delay over valhalla, just sounds better and gives me instant good results. Valhalla is too washy.