KVR Audio

kvaca · Post by **kvaca** » Sun Nov 05, 2017 6:38 pm

omiroad wrote:
Funkybot's Evil Twin wrote:Are there a lot actual bug reports or just design decisions that people are questioning or looking to see improved upon?
The volume burst when switching settings just isn't anything I have experienced before with other plugins.

During my testing it clipped on my master bus, so the volume jumps would be even louder if I had worked with more headroom. I just don't wanna get my ears blown out.

pity you erased your original statement, I have almost pissed myself from laughing

omiroad · Post by **omiroad** » Sun Nov 05, 2017 6:46 pm

Okay, I'll say it again just for you: Not getting my ears blown out is not a feature request.

It's a nice plugin otherwise so I didn't wanna seem so grumpy.

kvaca · Post by **kvaca** » Sun Nov 05, 2017 6:54 pm

omiroad wrote: It's a nice plugin otherwise so I didn't wanna seem so grumpy.

I have appreciated your intentions, just cannot help myself when reading that level of dry sarcasm...

Funkybot's Evil Twin · Sun Nov 05, 2017 7:17 pm

I'd definitely agree that getting your ears blown out by volume spikes would be a bug. Not getting that here. That said, have you heard of ice9? It's a free plugin you throw on your matter out that will mute any audio that exceeds a set threshold. Designed specifically to prevent ears from getting blown out. I recommend everyone put it last on their master output and save that as a template.

ere2learn · Post by **ere2learn** » Sun Nov 05, 2017 7:22 pm

Link for Ice9

http://www.cerberusaudio.com/Software/Products/Ice9/

zvenx · Post by **zvenx** » Sun Nov 05, 2017 7:51 pm

Funkybot's Evil Twin wrote:I'd definitely agree that getting your ears blown out by volume spikes would be a bug. Not getting that here. That said, have you heard of ice9? It's a free plugin you throw on your matter out that will mute any audio that exceeds a set threshold. Designed specifically to prevent ears from getting blown out. I recommend everyone put it last on their master output and save that as a template.

i do find sometimes with lots of compression switching to the 2A model causes( occasionally) the first milliseconds of the attack to be missed (as in not compressed so it is seeing the makeup gain but not the threshold) as it is switching models.
I would think this is normal and I either stop playing when switching models or turn my speak down when switching models.

rsp

omiroad · Post by **omiroad** » Sun Nov 05, 2017 7:56 pm

Funkybot's Evil Twin wrote:I'd definitely agree that getting your ears blown out by volume spikes would be a bug. Not getting that here. That said, have you heard of ice9? It's a free plugin you throw on your matter out that will mute any audio that exceeds a set threshold. Designed specifically to prevent ears from getting blown out. I recommend everyone put it last on their master output and save that as a template.

That's a nice tip, thank you. Not a total fix but I can see that coming in handy in more cases.

Vortifex · Post by **Vortifex** » Sun Nov 05, 2017 11:52 pm

drakmaniso · Post by **drakmaniso** » Mon Nov 06, 2017 11:11 am

ere2learn wrote:Link for Ice9

http://www.cerberusaudio.com/Software/Products/Ice9/

+1 for Ice9

Some put a limiter on the master for ear protection; but if, during tracking/sound designing, you inadvertently push the signal too hot, the distortion induced by limiter-clipping can become part of your sound design without you realizing it (which leads to an unmixable mess).

Ice9 makes it impossible to ignore clipping on the master, because each clip provokes a fade-out. IMHO this a feature that should be part of every DAW...

DaveGamble · Post by **DaveGamble** » Mon Nov 06, 2017 2:08 pm

zvenx wrote: i do find sometimes with lots of compression switching to the 2A model causes( occasionally) the first milliseconds of the attack to be missed (as in not compressed so it is seeing the makeup gain but not the threshold) as it is switching models.
I would think this is normal and I either stop playing when switching models or turn my speak down when switching models.

The real problem is that the 2A has a slow attack, compared to a lot of stuff, so the first transient gets through. But I can't "jumpstart" a compressor with GR, or you'd not get the right behaviour at the start of a render. Essentially, you're repatching in a different piece of gear; drop gains before you do, or there will be pops.

I'll have a ponder as to whether there's anything that could be done to improve this, but switching between models on the fly, with audio passing through is not intended usage.

Dave.
Edit: Maybe they should just be different plugins?

zvenx · Post by **zvenx** » Mon Nov 06, 2017 2:25 pm

DaveGamble wrote:..........

Dave.
Edit: Maybe they should just be different plugins?

Please No!!! Thats the beauty of this... one plug in for every compressor need.
To me you have explained why it happens, which correlates with my own observations.....indeed either lower the volume or just hit pause between switching to the 2a.
rsp

DaveGamble · Post by **DaveGamble** » Mon Nov 06, 2017 2:27 pm

pabloaldunate wrote:
HcDoom wrote:Is this plugin really so buggy as everyone writes or these are just isolated cases?
As much as I love their products it seems like we all are beta testing.

I have no reports of crashes or hangs.

There was an issue with the 76D model causing undesirable distortion in 1.00, which, in 1.01 is replaced with the model causing desirable distortion.

TrackComp does a bunch of things that seemingly no other plugin does (switching between completely disjoint circuit simulators, and some new UX ideas), and that's causing some discussion. I'm really sorry if you feel let down, but I made a decision (and strongarmed Krz) to get the thing into peoples hands sooner rather than later. And I am fixing all the things

Dave.

omiroad · Post by **omiroad** » Mon Nov 06, 2017 2:38 pm

DaveGamble wrote:I'll have a ponder as to whether there's anything that could be done to improve this, but switching between models on the fly, with audio passing through is not intended usage.

Dave.
Edit: Maybe they should just be different plugins?

Well, yes, if a setting in your plugin isn't meant to be changed while using it then it might as well be an upfront choice when selecting the plugin.

But it would make more sense to me to make it useable with that workflow.

Funkybot's Evil Twin · Mon Nov 06, 2017 2:42 pm

Would it be possible to mute or ramp the output down/up briefly while the internal settings caught up? You won't be able to stop users from switch models while audio is playing back so a quiet glitch would be better than a loud one IMO.

DaveGamble · Post by **DaveGamble** » Mon Nov 06, 2017 2:48 pm

Funkybot's Evil Twin wrote:Would it be possible to mute or ramp the output down/up briefly while the internal settings caught up? You won't be able to stop users from switch models while audio is playing back so a quiet glitch would be better than a loud one IMO.

It would. And maybe there's a slick way to identify between user-generated changes vs session start etc. I continue to ponder

Dave.

DMGAudio TrackComp 2