KVR Audio

prodigal_sounds · Post by **prodigal_sounds** » Sun Jun 21, 2020 4:39 am

Opened UI in my test-bed Cakewalk project. Preset name was blank, of course.
Typed new preset name. Pressed SAVE button.
Got dialog "Preset already exists. Overwrite?"

Is this expected? Does it save the preset as soon as the cursor leaves the combi box after typing the new name?

prodigal_sounds · Post by **prodigal_sounds** » Sun Jun 21, 2020 4:47 am

Given any patch, if I turn up the POWER AMP: DRIVE, there is a noticeable drop in output volume (without touching any other control). Is this expected behavior?

guitarzan · Post by **guitarzan** » Sun Jun 21, 2020 5:51 am

I get the power amp drive thing too, seems odd. Also get the auto save behavior (just type name of preset, hit the save button, says preset already exists…).

jbraner · Post by **jbraner** » Sun Jun 21, 2020 9:18 am

garrinm wrote: Sun Jun 21, 2020 3:15 am Minor patch 0.5.1 incoming. Tweaked the tone stack to cut out some of the mud / boom that seems to always pile up. I also revisited the approach for separating the mids from the lows to get a bit more audible separation there.

https://github.com/resonantdsp/ResonantAmp

I can never find where to actually download - on these github (etc) pages.
I'm still using
https://drive.google.com/file/d/1aOKUJy ... noSLS/view
is that the latest build?

garrinm · Post by **garrinm** » Sun Jun 21, 2020 11:46 am

prodigal_sounds wrote: Sun Jun 21, 2020 4:39 am Opened UI in my test-bed Cakewalk project. Preset name was blank, of course.
Typed new preset name. Pressed SAVE button.
Got dialog "Preset already exists. Overwrite?"

Is this expected? Does it save the preset as soon as the cursor leaves the combi box after typing the new name?

That's an error, I need to re-visit the preset workflow. But yes, at the moment it does unfortunately save as soon as you click away after typing a new name. By the way the presets are stored in your C:\Users\user\AppData\Roaming\Resonant DSP\Resonant Amp. You can remove them there. In the next patch I will improve this and allow remove presets from the UI.

prodigal_sounds wrote: Sun Jun 21, 2020 4:47 am Given any patch, if I turn up the POWER AMP: DRIVE, there is a noticeable drop in output volume (without touching any other control). Is this expected behavior?

That's a nasty bug. I just found the issue, I will fix this ASAP. Thanks for the report.

jbraner wrote: Sun Jun 21, 2020 9:18 am I can never find where to actually download - on these github (etc) pages.
I'm still using
<span class="skimlinks-unlinked">https://drive.google.com/file/d/1aOKUJy ... view</span>
is that the latest build?

Same download links. I'm thinking of making a website soon and hosting the downloads there, but until then I'll keep posting the drive URLs here to make things clear.

jbraner · Post by **jbraner** » Sun Jun 21, 2020 11:56 am

Same download links.

OK thanks - that's what I thought.
I don't know why you can never download directly from ie the github page.

garrinm · Post by **garrinm** » Sun Jun 21, 2020 1:49 pm

Minor patch 0.5.2 addresses the pre amp drive volume issue. Please note this will affect any saved presets.

https://github.com/resonantdsp/ResonantAmp
Installer: https://drive.google.com/open?id=1aOKUJ ... sQv2_noSLS
VS3: https://drive.google.com/open?id=1BrrAs ... Hjl1CVIRMk

The plan is to mark 0.6.0 as the beta, and at that point I will add version numbers to the file names so that you can have multiple versions of the plugin. On top of that I will make efforts to mitigate changes that could impact your presets (and I have good motivation to do this because it's a big hassle for me to update all the factory plugins anytime I change the model--I don't know how many more times I can listen to my guitar through the "level 11" preset without going insane).

garrinm · Post by **garrinm** » Sun Jun 21, 2020 3:44 pm

prodigal_sounds wrote: Sun Jun 21, 2020 4:47 am Given any patch, if I turn up the POWER AMP: DRIVE, there is a noticeable drop in output volume (without touching any other control). Is this expected behavior?

Actually there might have been two issues at play here. I addressed one related to the interaction between the pre amp and the power amp that could make the volume go down when you increased the power amp drive.

But it's also possible you had a high "sag" setting stored from your last session with the plugin. The sag model changed significantly and very large values will cause a prominent compression drop in signal level. It might be that by turning up the drive with a high sag value you heard that compression?

I'll be curious to know if the issue is resolved.

Thanks,
Garrin

prodigal_sounds · Post by **prodigal_sounds** » Sun Jun 21, 2020 4:00 pm

SAG is at 5. I don't think high sag is involved.
I downloaded a fresh copy of the VST a few minutes ago. If the problem still exists, it is much less noticeable to the point that I am not sure it's actually a thing. I'll keep messing around and if I find a combination where it comes back as strongly, I'll let you know.

garrinm · Post by **garrinm** » Sun Jun 21, 2020 4:28 pm

Minor patch 0.5.3 is a further tweak on the last patch to help get more stable levels out of the power amp drive with large sag values.

NOTE: if you're just trying this out again after a 0.4.x version, you will want to ditch your old configurations (you can use the "init" preset to get back to defaults) as they SAG behaviour has changed significantly, and both the pre amp and power amp DRIVE controls are slightly different.

https://github.com/resonantdsp/ResonantAmp
Installer: https://drive.google.com/open?id=1aOKUJ ... sQv2_noSLS
VS3: https://drive.google.com/open?id=1BrrAs ... Hjl1CVIRMk

EDIT: also the installer will correctly overwrite the previous install. This, embarrassingly, wasn't the behaviour previously.

funky lime · Post by **funky lime** » Sun Jun 21, 2020 5:23 pm

Quick request, sorry if it's been asked already or is otherwise dumb: Especially since there are so many versions in such a small amount of time, would it be possible to check the version number from within the plugin? Maybe display it next to the logo?

kvraudio38 · Post by **kvraudio38** » Sun Jun 21, 2020 6:11 pm

I extracted the .so file from the OpenSUSE rpm file and placed it in ~/.vst/ on my Fedora 32 system and it works great as far as I can see and hear.

On a side note, I agree with the request about adding version number in the plugin. This would make it easier to go back and forth when "debugging", I think.

garrinm · Post by **garrinm** » Sun Jun 21, 2020 8:04 pm

funky lime wrote: Sun Jun 21, 2020 5:23 pm Quick request, sorry if it's been asked already or is otherwise dumb: Especially since there are so many versions in such a small amount of time, would it be possible to check the version number from within the plugin? Maybe display it next to the logo?

Good idea, thank for the recommendation. I'll include this in the next update.

Kott · Post by **Kott** » Sun Jun 21, 2020 11:05 pm

kvraudio38 wrote: Sun Jun 21, 2020 6:11 pm I extracted the .so file from the OpenSUSE rpm file and placed it in ~/.vst/ on my Fedora 32 system and it works great as far as I can see and hear.

good)

the most recent builds are available in my repo https://software.opensuse.org//download ... esonantAmp

garrinm · Post by **garrinm** » Sun Jun 21, 2020 11:22 pm

I'm very close to finishing up version 0.6.0. I will declare that one the beta, which is mainly a commitment from my side to a certain level of stability and quality. This isn't a big model update, instead I'm focusing on usability: I'm adding tooltips to explain the parameters, and I'm making improvements to the preset selection. The main goal is to have something stable, easy to use, and that sounds good. That's why 0.5.0 was a bit round up release, I wanted to get a chance to test all those bigger changes before beta.

Here then is an overview of my tentative plans moving forward:

I’m expecting the beta to last a little while with perhaps no major model features (though I’ll certainly want to tweak it, and if an issue comes up that requires major work then that’s what I have to do). I want to bring the plugin to mac users and I want to minimize technical hurdles to getting it working / getting a good sound out of it.

Concurrently with the beta, I’d like to start work on a paid version. The current version is open source, so it's not going anywhere, no need to worry about that. It's there for anyone to enjoy, and more importantly to learn from. I’m thrilled to see the response so far and that someone’s already ported it (thanks Kott). While I work on the paid version I’ll keep bringing model improvements into the open source version as I discover them.

For the paid version, the plan is essentially to add guitar pedals, extend the cabinet modelling, and create a better workflow experience (probably adding some EQ options and the like). I’d expect to reach a higher level of polish, both for the UI and the user experience. The hope is to create value *beyond* the dynamic tube amp model. The selling point here is that it will have more parity with professional tools, incorporate more of the guitar recording workflow into the plugin, and achieve an overall higher level of polish to the user experience.

I'll be sharing more details when I have more concrete plans.

Swanky Amp (release 1.4.0)