randy's Recent Posts
There's no search built in here yet. You can use Google like this: "site:madronalabs.com thingToSearch"
You can use the trig input to the granulator to start a new grain when a key is pressed. Grains are always started in a round-robin fashion when a new trig comes in, or when the internal clock (set by rate) triggers a new one. Each voice has a maximum of 16 grains.
You can experiment with a rate of 0, maybe from there it will be easier to get to the behavior you are looking for. Grains will only be triggered by new notes. You probably want wrap off with a rate of 0, otherwise grains will go on indefinitely.
Also, turning on follow is needed for the grains to track a new note's pitch properly.
Hi Peter,
Don't worry about using the right terms, we're all here to improve understanding!
An incoming note on a MIDI channel triggers a voice. So if you play 8 notes on channel 1, and the DAW is sending channel 1 to Kaivo, you will have 8 voices playing. The DAW is really in charge of what note events to send to Kaivo or any plugin synthesizer.
The voices all have the same dial settings. So there is nothing more to find, there. A parameter is the sum of a dial setting plus a dynamic signal, however! And it is these dynamic signals that can be different for each voice.
The dynamic signals are what the multiple "needles" in each dial show. There is an illustration in the manual of multiple voices, each showing a different signal in a dial. Definitely give this section some attention.
Dynamic signals come from incoming note information, which will be different for each voice. Signals coming out of other modules can also be different for each voice. The most clear example is the "vox" signal in the KEY module. This signal has value 0 for voice 1, 1 for voice 2, 2 for voice 3 and so on. When you patch it to any destination you will see in the dial how it sets the parameter for each voice to a different value.
Thanks for the feedback. I don't know if FL studio will provide the needed data to make this happen. I can certainly make it work with drag + drop from the OS though, and that is indeed on my list.
P.S. nice gravatar.
if this is not working in the next update, there can be another soon after. The new license situation will make it much easier for me to get updates out. I might send out a demo-only beta you can test with in just a bit here too.
Yes, you can do this. You want to turn auto off on the noise generator, then send the get from the key module to the noise trig input so that every gate produces a new random value.
Hi Mark,
That OSC / MPE bug is fixed.
The library code will make its way into the Soundplane app. This should not produce any major changes in the Soundplane app however. I am excited to work on the new touch code after this release.
If I just open up a stereo track for recording on my laptop, the mic input comes into both channels. So I would think any mono input would do the same?
Thanks for the good words.
I'm sorry you lost a patch when things did not work as expected. I'll confess I have no idea what a macro knob does in Ableton, so I have not tested this. I'm also not quite clear from your description how to reproduce. Please send an email to support@madronalabs with a series of steps I can do to make the problem happen. Or, start a new thread on the forum here with your issue and the series of steps. This way I'll have the best chance of reproducing your issue and fixing it.
This is important to me but I'm trying to get these plugin updates out and I don't have much time to put on my Application Support hat today. I made a bug report so that I will look at this later. Meanwhile, I hope using stereo tracks for your input is a reasonable workaround for you.
OK, Given what I remember of Logic this makes sense. Can you use one of Logic's utility objects to make a stereo signal out of the mono signal?
I will give it a go and see if I can find an easier solution. I'll see if I can find room for a "mono" button in the audio input section too!
yep!
Glad it was so simple. Thanks for the info.
I can definitely add this. Thanks for the feedback!
Well, it's an issue I am taking seriously. If the update I'm working doesn't fix it, I'll try to get some projects / patches from to to test. Thanks for the info.
This is good to hear. Do you have any specifics you can share? I'd be very interested in your setup tips.
thanks and welcome!
Sorry you're having trouble. Can you try the samples and patches installer available on the product page? http://madronalabs.com/products/kaivo
Thanks for the good words! please keep me posted.
Ah, OK! glad to hear. Maybe the manual validation woke up DP somehow. I was about to get back to you without any real ideas, because the validation looked perfect.
Yes, I have a few size small left. Please send payment via PayPal to payment (at) madronalabs.com. $24 to North America, $36 elsewhere. Then I'll send you one next time I'm in the shop.
I have not been able to try a Seaboard, but I have an idea or two you can try.
Try recording the pressure as MIDI in your DAW. if this data is not smooth then the problem my lie with the DAW. Likewise if it is smooth, you can record some test data from the Roli and not just use that when testing to simplify the issue.
If you have a different DAW to try, that may make a big difference. Not all DAWs are equally capable with MPE data.
Also you can try different signal vector sizes in your DAW as well as any "sample accurate automation" settings.
Sorry for the trouble. This sounds like a bug that I am currently looking into with Kaivo, but I haven't heard about this issue with Virta. Please stay tuned for betas to test soon.
I don't really use the old bank/program concept. Aalto and friends just have a current patch.
If you need to load a patch under MIDI control you can check out the instructions for putting patches into the "MIDI Programs" directory.
I can't think of why else you would want banks / programs but if you have another use this is not taking care of, please let me know.
My first guess is, you need to run the installer as your personal account, in order to get the samples into your personal AppData\Roaming.
DP doesn't open VSTs?
The AudioUnits cache behavior is unfortunately not well documented by Apple, so the "delete your cache" advice approaches voodoo: a thing that works sometimes but I know not exactly why. So I can't say for sure what a missing cache would mean.
I can get more info if you open a Terminal and run 'auval -v aumu Aalt MLbs'. This will validate the Aalto AU. It looks like possibly this is failing on your system. Please send me the resulting text by email to support@madronalabs.com. Thanks!
OK! You reminded me that there used to be arrows when the patch cords were not moving. Yes, I cleaned up the interface at some point and removed these arrows. Sorry, I didn't remember that right away. There have been a lot of changes over the years!
Maybe they are smaller than they were previously? I still see arrows on both platforms. They are sometimes hidden under the mouse pointer. If you can take a screen shot showing this, please do.
Thanks for the good words.
Good morning and thanks!
More bodies are definitely coming in the future. I tried a tube model for the 1.0 but it did not make the cut. I'll definitely revisit that idea, Kaivo needs more "hollow" sounds.