Ah okay! That does make sense! I assume I don't check the channel count properly. Thanks for the extra details!
Recent community posts
When you say "buttons" you mean buttons on your actual computer keyboard, or keys on a midi keyboard?
Sounds like the plugin is stealing input focus from your DAW, which makes it so you can't use the buttons. FL Studio has a button for this on the plugin's toolbar. However, this is definitely not a problem exclusive to Nimble Kick, I've had this happen with many of the plugins I use. I'd recommend you get a midi keyboard to work around this problem.
Hmm that's a pretty unique request! I can definitely make that knob go above 200%, but there will probably be a lot of artifacting as a result. Curious - what do you need it for? And how far beyond 200% do you think you'll need to go?
I suspect it has something to do with the way the license dialog is shown (it's opened as a separate window). Perhaps something is going wrong there, although I'm not entirely sure what. The only way I can see a stack overflow happening is if the modal window callback is being called instantly when the window is opened. Maybe this helps narrow it down? Since this considers the licensing code, if you have any more questions, let's chat via email!
There's no demo available, sorry :( Do you have more details about the segfault? Perhaps I can shed some light on what's potentially going wrong. If you have a stack trace or so, you can email email@example.com!
Multiple outputs has been suggested before, which is still something I want to add. Thanks for showing interest in that, it tells me people really want it! 😁
In FL, the slide notes are exclusive/specific to FL-based plugins, so they can not be handled by external VST plugins unfortunately. You can, however, use midi pitch automation to make pitch slides.
I'm not entirely sure what you mean with the "boing-pitch" effect after listening to Frequencerz - Burning, unless you mean the very long pitch-automated tails? I guess you could technically do that with either a longer sample, or by enabling the loop function in Nimble Kick.
Which folders does Studio One check? You should be able to find this in the options under “Locations”.
What folder is Nimble Kick installed to exactly? And, are you using the 32 bit or 64 bit version?
Can you give some more details? How high of a frequency are we talking about? Is it audible, or can you only see it in an analyzer? Does it happen for all the algorithms? Which settings are you using? What are the technical details of the sample you are using?
Looks like it. Unfortunately I can't support and release VST2 versions of any of my plugins, as VST2 has been deprecated and it's not possible to get a new license agreement with Steinberg for VST2 plugins. :(
I think you'll have to look for either a way to load VST3 plugins into a VST2 host, or switch to a different DAW altogether, but that might be a difficult step to take.
On Windows the install path will be C:\Program Files\Common Files\VST3\, which is a standard VST3 path that should work in every DAW. Are you having problems finding the plugin in your DAW?
Did you accidentally uncheck the "Separate tail" box? You might also have accidentally set the "Time" knob to something too high or too low, making the separator invisible.
Hope this helps!
You might need to make your midi notes slightly shorter so that the ADSR has time to release. Kontakt can't solve this without introducing latency, since Midi notes don't carry a note length value (as you can play midi live).
That's really weird. I just tried 1.0.4 on Logic myself and it seems to work just fine. Are you sure that Nimble Kick in Logic is routed correctly and all? Can you try it in an empty project?
Couple things that could be the problem here:
- Have you entered your license key in the dialog that comes up when you first start Nimble Kick? On MacOS the dialog might be a bit hidden behind other windows in some cases, this is an issue I'm aware of.
- Which notes are you playing? You'll have to look for the right octave, as notes outside of the pitch range won't play any sound.
It depends - if you're using the "Resample" algorithm you'll end up with the most basic pitching possible, I wouldn't recommend using that unless you have a good reason for it. You should probably stick with Time Machine.
If you're already using the time machine algorithm and you're noticing this problem, that's normal as well depending on the sample you put in. Due to the nature of the algorithm, you're better off using samples that are slightly longer than your beat length. For example, if your track is 150 BPM, don't make your kick sample exactly 400ms, make them slightly longer such as ~450ms, because otherwise the algorithm won't know how to fill up the empty space at the end.
Alternatively, you could just set the Stretch knob to ~111% to compensate for the artefact.