KVR Audio

heavymetalmixer · Post by **heavymetalmixer** » Tue Apr 20, 2021 5:59 pm

Another great release

sokoleski · Post by **sokoleski** » Tue Apr 20, 2021 9:34 pm

Great work!

Most welcome <3

.jon · Post by **.jon** » Wed Apr 21, 2021 7:59 am

Oh man, your site has a bunch of simply amazing plugins. Thank you!

kaspien2021 · Post by **kaspien2021** » Wed Apr 21, 2021 2:34 pm

Ong, some really immaculate plugs man, can't imagine workflow without chow tape now haha.

Sinisterbr · Post by **Sinisterbr** » Wed Apr 21, 2021 4:47 pm

This plugin is unbelievably cool. Thank you so much, Jatin!

Scrubbing Monkeys · Post by **Scrubbing Monkeys** » Thu Apr 22, 2021 11:28 pm

Dear God sir.......this is exactly how GUIs should be in 2021.
Thank you.
Plugin is awesome.
Very complete and tidy release.

Kr3eM · Post by **Kr3eM** » Thu Apr 22, 2021 11:52 pm

It's really impressive, sounds great. However I think I have found a bug... The Azimuth resets everytime I stop playback... not GUI parameter but the widening effect is gone next time I hit play, and as soon as I change it a little bit it comes back.

VST2 x64 version in Reaper 6.26 x64 / Win7 SP1

EDIT: I seems to be solved by not have the "Hard reset on playback start" option enabled... sooo my bad, carry on

chowdsp · Post by **chowdsp** » Fri Apr 23, 2021 12:15 am

Thanks all!

Scrubbing Monkeys wrote: ↑Thu Apr 22, 2021 11:28 pm Dear God sir.......this is exactly how GUIs should be in 2021.
Thank you.
Plugin is awesome.
Very complete and tidy release.

All credit for the plugin UI design belongs to @rbn777! For this release I also had some help implementing some of the new UI elements from https://github.com/NeelKanth333.

Scrubbing Monkeys · Post by **Scrubbing Monkeys** » Fri Apr 23, 2021 2:14 pm

chowdsp wrote: ↑Fri Apr 23, 2021 12:15 am Thanks all!
Scrubbing Monkeys wrote: ↑Thu Apr 22, 2021 11:28 pm Dear God sir.......this is exactly how GUIs should be in 2021.
Thank you.
Plugin is awesome.
Very complete and tidy release.
All credit for the plugin UI design belongs to @rbn777! For this release I also had some help implementing some of the new UI elements from https://github.com/NeelKanth333.

I was a bit surprised that a researcher / dsp guy was also a top notch gui guy as well. Anyway thanks again. i wish 300 other companies would search out the expertise of @rbn777.

Kr3eM · Post by **Kr3eM** » Fri Apr 23, 2021 2:52 pm

chowdsp wrote: ↑Fri Apr 23, 2021 12:15 am Thanks all!

No Sir, Thank you.

I have a little bug here after all, not the end of the world, but when I save a preset it will jump/load the preset that is last my folder after I hit return. So I have to manually load the preset I just saved...unless my preset name is such that it will be last in list.

Funkstar De Luxe2 · Post by **Funkstar De Luxe2** » Fri Apr 23, 2021 4:17 pm

I'm a moron. Please ignore.

chowdsp · Post by **chowdsp** » Thu Jun 24, 2021 3:43 pm

Hi again KVRers,
I've been working on adding some more options to the oversampling menu (see here and here), and had a question that I thought would be nice to "crowd-source". The basic question is: should oversampling be saved as part of a preset? The suggested options (so far) are as follows:

1. No (scrolling presets leaves the oversampliing factor unchanged)
2. Yes (scrolling presets may change the oversampling factor; this is the current behaviour)
3. Max (the preset oversampling factor will be used, unless it's smaller than the one manually set by the user)

I'm not really sure here what the right move is, so I was curious to hear some more opinions. Ideally the right solution will result in the fewest number of clicks for the most use cases, while also making intuitive sense to new users.

Thanks,
Jatin

Scrubbing Monkeys · Post by **Scrubbing Monkeys** » Thu Jun 24, 2021 3:49 pm

Hey Jatin
Interesting. At first I thought.....no. Then after consideration. It may be useful so yes option 2

Maybe leave Max for rendering.

Karmoon · Post by **Karmoon** » Thu Jun 24, 2021 4:31 pm

chowdsp wrote: ↑Thu Jun 24, 2021 3:43 pm Hi again KVRers,
I've been working on adding some more options to the oversampling menu (see here and here), and had a question that I thought would be nice to "crowd-source". The basic question is: should oversampling be saved as part of a preset? The suggested options (so far) are as follows:

1. No (scrolling presets leaves the oversampliing factor unchanged)
2. Yes (scrolling presets may change the oversampling factor; this is the current behaviour)
3. Max (the preset oversampling factor will be used, unless it's smaller than the one manually set by the user)

I'm not really sure here what the right move is, so I was curious to hear some more opinions. Ideally the right solution will result in the fewest number of clicks for the most use cases, while also making intuitive sense to new users.

Thanks,
Jatin

Hi Jatin,

In my opinion as a general thing oversampling should not be saved as part of a preset.

However, in this specific case where people have already used the plugin to design their presets, it might be good to have a 'preset override' option. This enables people to set the oversampling depending on their preferred workflow.

I think certain developers use this kind of system and I have found the flexibility facilitates my work.

These are nothing more than my opinions.

beingmf · Post by **beingmf** » Thu Jun 24, 2021 4:34 pm

Wow - a developer who asks the right questions! Thank you! My ongoing, annoying, experience with exactly this "issue" results in one clear answer: 1: No.

CHOW Tape Model by Jatin Chowdhury