New kickdrum synthesizer: Audija KickDrum VST/AU

[bite_me]

@ sqigls Installs side by side.

[vanerio]

A new update is ready! Thank you Audija, best kick synth out there

[Jan_Audija]

Hi Jan,

you got it solved with the latest Beta

that's good news, excellent!
____________________________________________________________________

This plug-in is new for me, and I can already see why there has been so much positive buzz about it online. It’s pretty slick for a Beta, and it’s encouraging to see so many user suggestions being implemented.

That’s a fantastic way to collaborate for ideas. It also builds a sense of community that’s incredibly lacking with much bigger software companies. This is fun and quick to use. And all of these sculpting possibilities will keep my kick drum OCD at bay...for a while at least.

Thank you! without all this valuable feedback KickDrum would have been "finished" already. Since 1.3 it's in the hand of the users trying to meet the needs the best way possible, so if your OCD comes up again, please leave a note
____________________________________________________________________

just bought this, based on the positive response here and the features i'm seeing being implemented in the beta. before i install - can v1 and v2 beta be installed simultaneously or does the beta overwrite v1 ?
cheers

Thank you for your purchase! yes, as bite_me already replied, completely seperate plugins. When 2.0.0 is ready, 1.3 will become 2.0.0 - all the presets and plugin states in current projects using 1.3 will then just load KickDrum 2.0.0

[Jan_Audija]

Hello Everyone!

Although KickDrum is still in BETA, I'd like to have it as stable as possible while it is developing, so some of you might have noticed that after the bigger update of BETA 7, the context menu and the analyze function could cause a crash. Also, on Mac, icons weren't drawn, and there was a floating bug resulting in undefined behavior in several DAWs on Mac (some of the vector graphics that went as resources into the plugin had their permissions set to no access, which disallowed the DAWs from using these SVGs and either resulted in crashes or undefined behavior. I am quite sure this issue was the reason why, for example, Ableton couldn't find the VST3 in the system-wide plugin folder, which was an issue since the release of the BETA). Then BETA 8 went out yesterday to address these issues, but the device automations were broken—this overall was a little bit too bumpy for my taste, but the analyze function and the smoothing took everything out of me to get to work, and I was quite exhausted after weeks of implementing these. For a couple of days, things consolidated and everything feels much clearer now, which hopefully is reflected in today's release. Thank you for your patience and encouragement!

So today I'd like to invite you to test BETA 8.1, which should have resolved all these issues:

KickDrum 2.0.0 BETA 8.1 Changelog

Also, I'd like to tell you that the date for the full release of KickDrum 2.0.0 is finally set:

- 26th of November 2024 -

This also happens to be the first anniversary of Audija. What a better occasion could there be to celebrate that?

Also recently, the servers had a lot of hiccups, so currently Kevin is overhauling the codebase and he is quite happy with all the improvement possibilities he found so far, so fingers crossed by next week there will be a faster server and improved code behind the website.

Thank you!

[Jan_Audija]

A new update is ready! Thank you Audija, best kick synth out there

thank you!

[sqigls]

____________________________________________________________________

just bought this, based on the positive response here and the features i'm seeing being implemented in the beta. before i install - can v1 and v2 beta be installed simultaneously or does the beta overwrite v1 ?
cheers

Thank you for your purchase! yes, as bite_me already replied, completely seperate plugins. When 2.0.0 is ready, 1.3 will become 2.0.0 - all the presets and plugin states in current projects using 1.3 will then just load KickDrum 2.0.0

handy plugin thank you

for the record though, installing v2 beta on top of v1 leaves me with only v2 beta and no v1.
Sequoia, Cubase 12
the beta installer must have deleted v1 because i never touched it.

[Jan_Audija]

handy plugin thank you

for the record though, installing v2 beta on top of v1 leaves me with only v2 beta and no v1.
Sequoia, Cubase 12
the beta installer must have deleted v1 because i never touched it.

Thank you!
I think we can solve that, let's try the following:

- could you please close all DAWs
- redownload both setups for 1.3 and BETA 8.1
- delete all KickDrum and KickDrumBETA .component and .vst3 files
in these 4 folders:
systemwide AUv2: /Library/Audio/Plug-Ins/Components/
systemwide VST3: /Library/Audio/Plug-Ins/VST3/
user specific AUv2: ~/Library/Audio/Plug-Ins/Components/
user specific VST3: ~/Library/Audio/Plug-Ins/VST3/
- run both setups (after installation there should be 4 files added: two in /Library/Audio/Plug-Ins/Components/ and two in /Library/Audio/Plug-Ins/VST3/)
- restart your mac
- DAW should be happy now, showing both plugins side by side

if that is not working let's get into the details via mail - hello@audija.com

[sqigls]

the beta deletes the v1 plugin upon installation.
then I install v1 again and that installer deletes the beta plugin.

I don't use AU

also the beta was working fine in a Cubase 12 project, saving settings, open and close the project it recalls etc, no problem... then the next day every time i try to open the project Kickdrum Beta crashes. I think i will just wait until v2 is released.
cheers

[Jan_Audija]

the beta deletes the v1 plugin upon installation.
then I install v1 again and that installer deletes the beta plugin.

I don't use AU

also the beta was working fine in a Cubase 12 project, saving settings, open and close the project it recalls etc, no problem... then the next day every time i try to open the project Kickdrum Beta crashes. I think i will just wait until v2 is released.
cheers

the beta is there to find such issues and it it would be awesome if we could resolve this!

[sqigls]

ok i'll email you

BTW, i reinstalled v1.3, but kept a backup of the v2 beta VST3 file... then just 'cut n pasted' it back into the system VST3 folder after re-installing v1...
Live 11 and Cubase 12 both opened and recognised both versions of the plugin with no problem. I opened the Cubase project that was crashing yesterday and it's fine again. So i guess I'll wait and see if you have any specific tests you want me to run? meanwhile i'll start getting familiar with the plugin.
cheers

[twoodts]

Is there a way to switch sample to next/previous within a folder after I've dragged a sample from file explorer? To quickly audition different samples while keeping same settings.

[Jan_Audija]

Is there a way to switch sample to next/previous within a folder after I've dragged a sample from file explorer? To quickly audition different samples while keeping same settings.

Yes, if you add a sample device and click on the folder icon the sample browser opens, where you can skip through samples by clicking the up/down arrows; in the plugin options you can set the default folder, with which the sample browser should start and also you can browse through folders within the sample browser. Is this what you were looking for?

[twoodts]

I can live with that. I was thinking more like a button in the area where the open/close sample browser is. But that of course is fairly crowded already. Is there a way to not play the sample when selecting it? For example if I have the DAW playing midi notes into the plugin it'd be handy if the sample didn't play when you select it but when a midi note comes in to trigger the whole kick it would play the selected like it already obviously does.

Two small things that might bug loads of people... or just me.

• You can't escape from the sample vol and pan fields with Esc key. Instead it selects everything in the field.

• You can't reset the vol or pan value by Ctrl (or Alt ...I'm on Windows if that wasn't clear) clicking the number. Would be nice to have a way to reset the value.

[Jan_Audija]

maybe we can do that and on click give a messagebox showing the currently selected sample, that way the sample browser can be closed while selecting - i added that to the list.
yes, if you click the speaker icon above the arrows you can turn "play on select" on/off.
do you want the Esc button to restore the original value, before you entered the textinput? - i would need to check if that is possible, because Esc is reserved in some DAWs. if you want to exit with the currently typed value you can hit Enter or click anywhere in the plugin.
that's a nice idea! - Ctrl + Click for restoring the default value is on the list now

[swilow11]

Gotta say, I much prefer double click to reset to default.