randy's Recent Posts
not since Jan 20, sorry!
This averaging you are describing should indeed happen, but only with a few inputs from the patcher to the BODY module. Are you just testing with that one?
If you look at a lot of the example patches, where the vox input to the patcher sends different signals to different voices, for example, you should be able to confirm the behavior you are looking for.
The reason the BODY module is averaging the inputs is that there is only one BODY for all the voices. So this kind of breaks the convention of all the other modules that each voice has its own independent copy of the module. But since I wanted the BODY to be patchable I had to get signals to it some way and this averaging was the least confusing thing i could think of.
what's the difference between hitting "quantize" and patching from pitch to LFO frequency?
These do totally different things, so I'm not sure how to answer that.
You can see what quantize does when you look in the display. See how a solid line turns into dots? Those are the values of the LFO output in x and y changing from continuous values to quantized values. The output signal is restricted only to specific values that are in the scale chosen in the KEY module. When patches to the pitch of the oscillator with default scaling, this will make all the pitch changes "in tune" with the selected scale.
If it glitches when you change to a new patch, look at how many voices are being used. If it's 8 or something turn it down and let me know if it recovers.
Is this a new problem? Have you been using Kaivo successfully before? If so, can you think of anything that might have changed?
Thanks, I'll take a look.
This doesn't sound like an issue I am familiar with. Is it a particular patch that does it? If so, can you send me the patch?
I use Audacity. This readme has a short note I wrote about how to use it to make the multichannel files:
Hi Mark,
Thanks for your purchase. Since the emails for the PayPal transaction and your Madrona Labs account were different, the system could not find your account automatically. I added the license to your account. Now you can click ‘My downloads’ to get links to your customized software.
If you need anything else, please email me at support at madronalabs.com. I won't always see a forum post right away.
[EDIT] I tried to send you an email— it looks like your email is not working.
-Randy
Hi Greg,
I have seen this with El Cap and Live 9.5 also. I think it's more an issue with the CPU meter.
If you open up Activity Monitor, you can see that when the Madrona GUI is open, Live takes up a lot more CPU overall than when the GUI is closed, as you would expect. The Activity Monitor is a better measure of what's really going on in the system.
It doesn't make sense that Live's CPU meter would be backwards, I understand. My guess is that it's reporting DSP use a percentage of the time the OS gives to the app to execute, and when the plugin window is open, DSP is less of that time overall.
If you are hearing glitches with the window closed, and not with it open, let me know. Otherwise i think we can chalk this up to "don't trust the Live CPU meter."
¯_(ツ)_/¯ OK, glad it's working.
Well, that is strange. This is a new one for me—I can't think of why it would be heavier on the CPU on a newer computer, other things being equal.
What is the Buffer Size you have set in Live's preferences?
If you close the plugin window, does the CPU use change?
What if you make a new project and put a fresh Aalto in it? Do you get the same problem? If not, maybe it's something in the settings of the project.
Dying to show you something! The beta is very near completion and when it is being tested I'll make a few demo vids.
Dying to show you something! The beta is very near completion and when it is being tested I'll make a few demo vids.
I do know the Sea board, but I have absolutely no idea what kind of sensors are inside. There are a lot of sensor options to look at. Many devices use FSRs, either custom or off the shelf. The big advantage of the Soundplane sensor is that since we make it ourselves, I can tune the feel to be exactly what we want by varying the elastic layer in thickness and shape.
The DIY instructions are more aimed at research than making a finished instrument. Interfaces with a lot of I/O are not necessarily expensive—but this kind of setup with all the wires is probably not good for touring with either!
Any computer is fine for the FFTs. They all produce the same results. The best kind, is probably one you have already. My guess is a recent Arduino can probably do a 1x8 matrix at a reasonable sampling rate.
Thanks for the note. Still working hard and feeling like I'm close to a beta here.
I think you get this. You had it right up until the end. The antennas are not mixed with each other. So to do an 8x8 version you need 8 audio inputs and a separate FFT on each.
I also wish you could describe how to record it properly, as an example, some render settings do a good job even if the audio in real time is distorting from CPU burden. Reaper offline idle seems to work. I will do more experiments. I wish this advice could be available to the community.
Sorry, I just saw this post. It's hard to offer advice about recording because it depends almost entirely on the DAW, and there are a lot of different ones. Please post about your experiments in the software forum and hopefully we can build up some knowledge about Reaper use over time. I don't think I have a lot of users on Reaper but from what I have heard it is a good alternative to have.
OK, I fixed it for today only.
A lot of people seem to have missed it this time around, so you can use the code 'nottoolate' until the 30th. Enjoy.
Oops, sorry, my mistake, I had Aalto on the brain. I don't know about any then.
If you missed by a day or two feel free to email me at support for the hookup.
I realized that I could at least give users of Mac OS 10.6 some more security by making a permanent download for Aalto 1.6.1. So if you are still on Mac OS 10.6, and would like access to it, let me know and I'll add a special license for Aalto 1.6.1 to your account. This will enable a personalized download of 1.6.1 indefinitely, and of course you can still download Aalto 1.7 or higher if and when you upgrade your computer.
There are three good sets by Adrian Jimenez: you can find these at http://www.zensound.es/ . I think there are some others out there too.
@granum, thanks for your support!
When a DAW sends audio to a plugin for processing, it stores chunks of samples in a sample buffer. If this buffer is big, say 2048 samples, the buffering adds latency you can hear. When the buffer is very small, say 16 samples, processing overhead starts to use up lots of CPU. There is almost always a user setting to vary this buffer size.
Some DAWs do not send the same number of samples every time, but send a variable number: say 256, then 3, then 17, then 216... This is usually done to make sample-accurate automation work. However, some plugins have a problem with these different-sized chunks and this can cause bugs. So, there is sometimes a setting to disable this buffer size changing, thus: fixed buffer size.
I have tested that Aalto / Kaivo work with changing buffer sizes in the past. But maybe there is some problem that only the way Bitwig is doing it is revealing. Or maybe this is not the issue at all! But now you know what I meant.
Please check out this article on "getting the most out of Kaivo": http://madronalabs.com/topics/3565-getting-the-most-out-of-kaivo
It's got some tips and points out ways that Aalto and Kaivo are a bit different from other synths in use. Turning down the number of voices to the amount you are actually using is often a good idea. Also, turning off graphics may help.
I haven't used Reaper much, but if it's at 20-30% but not recording that a problem. What happens instead of recording? You get glitches?
Most DAWs have a freeze or offline render option where the track is recorded in non real time. This should do what you are trying to if you can find such an option in Reaper.
Hey zenwarlord at yahoo.com, thanks for the feedback, please check your email re: duplicate purchase.
Any pre sale with the winter discount?
No.
