KVR Audio

HcDoom · Post by **HcDoom** » Thu Sep 02, 2021 6:57 pm

This sounds so good that NFR doesnt mean anything, at least to me.

Another thread destroyed by totally other topic.

thecontrolcentre · Post by **thecontrolcentre** » Thu Sep 02, 2021 7:03 pm

HcDoom wrote: Thu Sep 02, 2021 6:57 pm This sounds so good that NFR doesnt mean anything, at least to me.

+1

HcDoom wrote: Thu Sep 02, 2021 6:57 pm Another thread destroyed by totally other topic.

Yeah, sorry 'bout that ...

Neon Breath · Post by **Neon Breath** » Thu Sep 02, 2021 7:19 pm

HcDoom wrote: Thu Sep 02, 2021 6:57 pm This sounds so good that NFR doesnt mean anything, at least to me. Another thread destroyed by totally other topic.

What is 'destroyed' ? Might not be interesting to you, just don't read if that's the case but that aspect of the plugin IS related. The thread is not '' A gorgeous new granular delay by Audio Damage - SOUND quality discussion only'' but about the plugin itself. That means the sound of course, but also the issues & problems it might have, technical stuff too, and licence issues enter this category.

noiseresearch · Post by **noiseresearch** » Fri Sep 03, 2021 10:34 am

Tested it. Like it. Sounds great. Good delay. Better than a lot of competitors but I ran into a bug.
Someone else having this?

It's probably GPU related bug. As soon as I have more than one instance open (not only loaded the GUI needs to be opened) the graphics of my whole system slows down. In Ableton Live the "limit" is three open instances – the GUI of Live as well as of ODC is not reacting anymore and I have to kill Live via the task manager. In Reaper I can open up four to five instances till the GUI is so slowed down it's not usable anymore. It's reacting but super slow.

Right now I do not see it as a complete deal breaker but it's annoying to take care not to open more than two windows of ODC - I sent an email to Audio Damage and I hope this can get sorted out. Just wonder if I'm the only one?

The CPU hit is easy and the GPU hit is also okay (around 25%) nevertheless the behavior is as described above. LatencyMon gives me good overall benchmarks.

bob swans · Post by **bob swans** » Fri Sep 03, 2021 11:44 am

noiseresearch wrote: Fri Sep 03, 2021 10:34 am Tested it. Like it. Sounds great. Good delay. Better than a lot of competitors but I ran into a bug.
Someone else having this?

It's probably GPU related bug. As soon as I have more than one instance open (not only loaded the GUI needs to be opened) the graphics of my whole system slows down. In Ableton Live the "limit" is three open instances – the GUI of Live as well as of ODC is not reacting anymore and I have to kill Live via the task manager. In Reaper I can open up four to five instances till the GUI is so slowed down it's not usable anymore. It's reacting but super slow.

Right now I do not see it as a complete deal breaker but it's annoying to take care not to open more than two windows of ODC - I sent an email to Audio Damage and I hope this can get sorted out. Just wonder if I'm the only one?

The CPU hit is easy and the GPU hit is also okay (around 25%) nevertheless the behavior is as described above. LatencyMon gives me good overall benchmarks.

I've been playing with the demo and decided to test this for you, It was all going okay and I had 4 instances open, then I clicked the name logo on one of them. Totally froze up Ableton and I had to kill the process.
I've been fighting with myself over getting this but I'm waiting until this is fixed I think.

noiseresearch · Post by **noiseresearch** » Fri Sep 03, 2021 12:25 pm

Thanks that you took time for testing. I'm sure it will be fixed. I'll post the answer by Audio Damage as soon as I get it. Luckily the intro offer last till 1st of October.

They are so long in the game and I used to use the first iteration of Dubstation and Ratshack Reverb ages ago... but I stoped using Audio Damage stuff like almost ten years ago. The products the offered lost appeal to me, although the drum machine (Tattoo) they offered was quite nice. Actually it would be nice to see an updated of that one. However, this delay seems to be a gem in a dirtbag of existing delays.

briefcasemanx · Post by **briefcasemanx** » Fri Sep 03, 2021 12:43 pm

noiseresearch wrote: Fri Sep 03, 2021 10:34 am The CPU hit is easy and the GPU hit is also okay (around 25%) nevertheless the behavior is as described above. LatencyMon gives me good overall benchmarks.

25% gpu uhhhhhh, I hope you're mistaken.

noiseresearch · Post by **noiseresearch** » Fri Sep 03, 2021 1:22 pm

briefcasemanx wrote: Fri Sep 03, 2021 12:43 pm
noiseresearch wrote: Fri Sep 03, 2021 10:34 am The CPU hit is easy and the GPU hit is also okay (around 25%) nevertheless the behavior is as described above. LatencyMon gives me good overall benchmarks.
25% gpu uhhhhhh, I hope you're mistaken.

Nope. Is that too much? I talked about a couple of instances though

I never had a GUI issue with audio software and therefore never checked GPU. And as I even rarely watch videos or other GPU related stuff on my audio station I never cared.
What number would be more appropriate for the GPU?

EDIT: I see. I opened in Live 6 instances of BYOME, 6 of MMultiAnalyzer and 6 of SPAN and hit the 25% mark now. But everything is stable. No slow down GUI or crash. If I could see something I could work in Live

So for sure there is something wrong with ODC

briefcasemanx · Post by **briefcasemanx** » Fri Sep 03, 2021 1:32 pm

noiseresearch wrote: Fri Sep 03, 2021 1:22 pm
briefcasemanx wrote: Fri Sep 03, 2021 12:43 pm
noiseresearch wrote: Fri Sep 03, 2021 10:34 am The CPU hit is easy and the GPU hit is also okay (around 25%) nevertheless the behavior is as described above. LatencyMon gives me good overall benchmarks.
25% gpu uhhhhhh, I hope you're mistaken.
Nope. Is that too much? I never had a GUI issue with audio software and therefore never checked GPU. And as I even rarely watch videos or other GPU related stuff on my audio station I never cared.
What number would be more appropriate for the GPU?

Plugins use almost all CPU, it shouldn't be using up much you at all unless:
1. The plugin is coded in a very non-standard and probably extremely difficult way
2. You're on an ancient computer, and you're using onboard graphics instead of a discrete gpu.
3. A bug

How are you even determining gpu usage for a plugin? What is gpu usage percentage at when you disable the audio damage plugin? If it really used 25% gpu your computer would explode (which you said happened!) if you tried to run 4 instances, which isn't normal for a plugin that takes only 2% CPU.

If you're accurately reading it's gpu usage at 25% it's probably why you can't run many instances, as you said. But 25% gpu usage for a plugin definitely isn't good.

noiseresearch · Post by **noiseresearch** » Fri Sep 03, 2021 1:49 pm

briefcasemanx wrote: Fri Sep 03, 2021 1:32 pm How are you even determining gpu usage for a plugin? What is gpu usage percentage at when you disable the audio damage plugin?

I "measure" with the Windows Task Manager. I'll make later a proper test as right now I need to leave my browser open cause I'm uploading something.

Vortifex · Post by **Vortifex** » Fri Sep 03, 2021 1:52 pm

Edited

ThomasHelzle · Post by **ThomasHelzle** » Fri Sep 03, 2021 3:55 pm

noiseresearch wrote: Fri Sep 03, 2021 10:34 am Tested it. Like it. Sounds great. Good delay. Better than a lot of competitors but I ran into a bug.
Someone else having this?

It's probably GPU related bug. As soon as I have more than one instance open (not only loaded the GUI needs to be opened) the graphics of my whole system slows down. In Ableton Live the "limit" is three open instances – the GUI of Live as well as of ODC is not reacting anymore and I have to kill Live via the task manager. In Reaper I can open up four to five instances till the GUI is so slowed down it's not usable anymore. It's reacting but super slow.

Yeah, I reported it too but didn't hear back.
For many of their plugins, the VST3 version doesn't save the GUI scale (should be a global preference ideally IMO). So I had a VST2 and VST3 version open for testing at the same time and couldn't access Bitwig or the plugin GUI anymore at all, complete freeze. Had to kill Bitwig with the taskmanager the first time in ages. 100% repeatable.
And I have quite beefy GPUs (RTX 2080 TI & GTX 1080 TI with latest drivers), so I do not think it's that. Windows 8.1 x64.
I'd think it's some kind of threading bug.

Let's hope they fix it quickly, it's quite a showstopper bug and one of the first to trip even the Bitwig sandboxing that normally prevents such things.

Cheers,

Tom

Funkybot's Evil Twin · Fri Sep 03, 2021 4:18 pm

Running the VST2 version in Reaper on Windows 10 and opening 4 instances froze up Reaper. This is on an Ryzen 3950x, 32GB Ram, Radeon RX 5500 XT w/ 4GB GDDR6...

Agree there's some kind of bug here with multiple instances or the GUI opened multiple times.

plexuss · Post by **plexuss** » Fri Sep 03, 2021 4:26 pm

Funkybot's Evil Twin wrote: Fri Sep 03, 2021 4:18 pm Running the VST2 version in Reaper on Windows 10 and opening 4 instances froze up Reaper. This is on an Ryzen 3950x, 32GB Ram, Radeon RX 5500 XT w/ 4GB GDDR6...

Agree there's some kind of bug here with multiple instances or the GUI opened multiple times.

Confirmed here as well macPOS + Reaper 6 AU/VST3. I already emailed them about it. Other instances show a blank screen sized the same as the plugin window.

Funkybot's Evil Twin · Fri Sep 03, 2021 4:41 pm

ThomasHelzle wrote: Fri Sep 03, 2021 3:55 pm 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.