randy's Recent Posts
Nice! I'm glad you find that Aalto pairs well with acoustic instruments, I think so too. Thanks for sharing.
Using aliases to folders should work. If it doesn't, checking permission is the only thing I could think of, also. I'm going to investigate this along with some other Kaivo issues very soon.
You may have noticed that Kaivo is slow to open–this is because it loads all the samples into RAM when it is loaded. In general it is just not set up well to use a lot of samples right now. I would recommend copying the ones you want to use into your main samples directory, and maybe getting rid of some of the factory ones you don't use, to speed up load times. I'll improve this for the next update.
What I like better than the idea of bipolar / unipolar switches, is the addition of some way to offset / scale the data more easily after it comes from the source.
I think a signal coming from a source such as "vox" should reflect what the actual data is---in this case a voice number from 0-3. With sequencer output I can see more of a case for adding an output option since it's not representing anything in particular.
There's no way to change the location of the Madrona Labs folder, but using aliases in the patches / samples folders should work. If you tell me what OS you are using, I can try to reproduce the problem.
Some signals are unipolar and others bipolar. I tried to go for the most common uses of the signals in deciding which to make them. I think this could be explained better in the manual.
Hopefully the pan modulation you describe is not too tedious to set up with the aid of the animated dials. looking at the four signal values all at once in the dial, you should be able to dial in the amount of modulation you want quite quickly.
The lack of fine tuning of small amounts of modulation is a problem sometimes. I would like to add a numerical mode for precise control when it's needed.
Welcome aboard, and thanks for the feedback and ideas. I'm always trying to find ways to do things better. I've thought that some time down the road it would be cool to be able to interpolate between presets, so maybe the "advanced preset browser" can be the same UI that allows that.
There is one big Kaivo optimization I plan to do, which will put each voice on a separate core of your computer. This should make a lot of difference on your quad core CPU. It's not a simple change and I have some other things to finish first, but it's definitely on my roadmap, so please hang in there.
Kaivo should also benefit a little from the next update where it gets the features I've been adding to Aalto. This won't be as dramatic though.
Wow, looks like my post got mangled somehow.
I was trying to say, if you use shorter files, you should be able to make a 2D wavetable with accurate pitch. With anything shorter than a second I was not able to hear pitch errors, so a stack of 4x128 waveforms should be in tune just fine and offer lots of wavetable goodness.
Hi @rydan,
Sorry I dropped the ball on this. It looks like I missed your first message here entirely and I didn't have this issue on my list of Kaivo bugs. There's only one of me and I'm definitely capable of slipping up sometimes, so it doesn't hurt to remind me if you're waiting on an answer. I
With the help of your video I was able to reproduce what you are hearing. I should be able to fix this for the next update. Meanwhile if you use shorter files (
Hi Adrian,
Kaivo will at least get a minor update soon with the many Aalto features that were new in Aalto 1.6. Beyond that I'm not sure what else I can add to Kaivo before my next plugin comes out. I will do the patch / sample installer thing at some time for sure, it's a feature I want very much.
Hi, and welcome.
VST plugins are put in a standard location on your computer so all the different DAWs know where to find them. on Mac OS X that is in (your computer) / (your hard drive) / Library / Audio / Plug-Ins / VST. The installer will put it right there.
To see your Library folder on Mac OS you can hold down the Option key while selecting the “Go” menu from the Finder. Sorry this is a bit complicated, it’s Apple’s decision to make ~/Library hard to access.
There are also some Ableton settings that need to be correct in order to use external VSTs or Audio Units. Here are the relevant docs from Ableton:
Ableton / VST docs
Thanks for the report. Of course Kaivo should sound the same when rendered. So I'll treat this as a bug and investigate.
The audio engine renders the same samples in either case, and I never have heard any difference in testing. My first guess is this is a problem with MIDI notes or controllers not being played back correctly.
You could try different buffer settings in Live to see if there is any difference.
Sure, Kaivo can make very nice wavetable sounds. If you look at the oscillator samples called "sine to square" or "sine to saw" you will see an example. There are only 4 "waves" in these, which is the maximum number of different waves you can have vertically.
You can also add another axis for a vector synthesis type of oscillator. Kaivo's grains will snap to the nearest appropriate zero crossing if "sync" is on. So if you put a large number of slightly different waves going left to right, this is like a long transwave. You could just record a filter sweep or something to try it out. Probably you want all granulator settings turned on: follow, sync, and wrap.
I love this project. I hope I get to try it one of these days.
Thanks for sharing your experience with AU versus VST support in Max. I think the plugin hosting was dramatically changed for Max 7, so there may still be some issues to work out.
In general, Aalto signals from the patcher simply run at audio rate and are not smoothed. A few of them are smoothed after they come out of the patcher in order to avoid aliasing. There are different amounts of smoothing going on in different places and a lot of it was simply tuned by ear, so unfortunately I don't have a good list for you. This could be something to document better.
A quick search of the code turns up the few parameters that have a vactrol response:
- oscillator fm index
- oscillator timbre
- gate level
Bravo! I love these quite different pieces—I would say of both of them that they use their time in a way that is well-considered. You are also using the expressive capabilities of the Soundplane very fully, with a kind of gestural language that is very suited to the instrument. I look forward to more!
Really nice Mark! Such a great variety in articulation demonstrated here, you are really making the melody sing.
I hesitate to even mention a date because I'm in research mode now, working on some changes. But I would like to get started on a new run soon, later this summer I hope.
There isn't an easy one. I should really add this as a KEY module option.
If you just want to tune to one specific thing and leave it there, you could make a Scala scale with a kbm mapping. Say you want to tune everything two cents sharp and you are working in the 12-equal scale. Then save this to a text file my12-equal.scl:
! my12-equal.scl
!
12
!
100.
200.
300.
400.
500.
600.
700.
800.
900.
1000.
1100.
2/1
then save this to another file my12-equal.kbm:
! keyboard mapping my12-equal.kbm:
!
! Size of map (greater than or equal to the number of notes in the scale
! to be mapped). The pattern repeats every so many keys:
12
! First MIDI note number to retune:
0
! Last MIDI note number to retune:
127
! Middle note where scale degree 0 is mapped to:
60
! Reference note for which frequency is given:
69
! Frequency to tune the above note to (floating point e.g. 440.0):
440.0
! Scale degree to consider as formal octave (determines difference in pitch
! between adjacent mapping patterns):
12
! Mapping.
! The numbers represent scale degrees mapped to keys. The first degree is for
! the given middle note, the next for subsequent higher keys.
! For an unmapped key, put in an "x". At the end, unmapped keys may be left out.
0
1
2
3
4
5
6
7
8
9
10
11
Put these in a folder in the Scales directory ~/Music/Madrona Labs/Scales. Select them in the key scale menu.
THEN, by changing the 440.0 in the kbm file to some other value and reloading you can get exactly the frequency you want. You may have to close the Aalto winow and open it again to see the new scl / kbm files.
A dial would be easier, I know.
[EDIT]
I'm not sure what I was thinking about above. Getting the oscillator in tune is very easy to do with the main OSC pitch control. Since the oscillator is FM-based, both the modulator and carrier change by the same amount when you shift the tuning. Holding down the shift key enables fine tuning on any dial, including the oscillator pitch. This makes it easy to dial in pitch in 0.1 Hz increments.
I recognize the need to switch between presets while tuning to some other instrument, which currently will reset the oscillator pitch. So I'll still get to adding a master tune when I can.
Could I basically turn the Y quantizing off by setting each cell in a column to be the same note? Then it would effectively function the same as the Continuum fingerboard.
yes, there's a default setting that does exactly this. If you set every row to send the same notes, there is one whole axis devoted to controlling timbre. If each row sends different notes, you can trade this timbre control for more notes, while still using y within each key to control timbre.
I should add for context that when the Soundplane talks to a computer, it just sends the raw pressure data. So everything we are talking about can be changed easily in software and if there's a useful option that doesn't exist for some reason I will add it.
The Soundplane is a lot like the Continuum. The underlying sensor is very much a continuous device capable of smooth changes. The grid of keys on top of it is applied after the initial data is gathered.
so like the continuum, Y is never quantised.
I would say it's always quantized. Which is to say, it always sends the nearest grid value and does not vary continuously. You are either in one row of keys, or another, not between.
It's probably clearer to talk about what data generated from the Y measurements are quantized, because this is what is really going on. Pitch data generated from Y is always quantized to the note grid. Timbre control data generated from y is continuous within the row of keys, or zone.
Thanks for that detailed response @thetechnobear, it's really special to hear from someone who has had a chance to compare the two instruments.
I would say it's more a question of feel than sound. These instruments can both play many different synthesizers, and a Continuum and Soundplane playing a given synth sound will sound the same, but they will feel different, have different limitations, and that will probably cause the playing to be different too.
It will be a little while before the next batch of Soundplanes is available. I'll make sure to get some more Soundplane-specific patches and videos out into the world by then.
Hi Björn,
Thanks for the feedback. I know, as a designer it really bothers me. Unfortunately the problem is mixed up in the web / PayPal system, so it's not too easy to fix. I'm rolling out a whole new licensing system soon, and it will handle your name properly.
Very interesting. I always play mine flat.
Sorry to hear it. Aalto CM has not had an update for a long time. I will give it one after my next plugin is done.
So, I guess you are OK but not ideal now. Sorry it's not great for you. It's hard to diagnose what might be going on on Windows machines where there are so many different kinds of audio cards and drivers.
You can't really trust what different programs say about CPU load relative to one another. They measure different things. Look in the Performance tab in the Task Manager if you want to compare different programs in a fair way.
Everything is independent for each voice, except the reverb. You can see this by looking at the dial animations. If you see four pointers in the dials at different locations, those are the values of the four voices. There is an illustration in the manual about this.
A few controls have no signal inputs, and thus no way to set a different value for each voice. These have dials that do not show a signal view. The gate decay is one example.
The delay comes before the filter in the waveguide/delay. If you turn the frequency down to 1 sec or something, you can hear this.
The main purpose of the Soundplane CV module is to enable Soundplane -> modular connection without a computer around. So aside from using it to load zone maps I would really resist any feature creep in that direction. For release, anyway.
It's true—each voice has a sequencer that is a completely separate processor from the other voices. Looking at a patch like "techniques / seq multirate" is the best way to see this. Each voice has a different signal created at the KEY module vox output. These signals are sent to the "rate" input of each SEQUENCER. And so each runs at a different rate.
There are lots of little examples in the Aalto techniques folder that may show interesting ways of using control. I wish that each example had a nice verbal description with it, but that's a feature I will have to add later.
The key trig input is the one way of controlling the position of each sequencer precisely. If you turn on key trig in this patch, each sequencer restarts whenever a note is send to that voice. So I believe this is the "syncing them all at will" you want.
There is no precise way to send just one of the sequencers forward one step. However, you can set the rate to the lowest nonzero value, then use an envelope to turn up the rate of just one of the voices for a time when a note is played. (setting the rate to 0 will not allow the modulation through, so a rate of 0.002 is needed currently)
In Kaivo there is a trig input to the sequencer, that increases the flexibility of what can be done.
The changes when you turn the number of voices are not well defined. when a voice is off, its sequencer may be in an undefined state if the number of steps has changed, for example, while it was off. This can definitely be improved.
There are a lot of things I could make controllable (put into the front panel) but haven't. This is to make the design approachable. There is always a tradeoff between flexibility and usability. I try to make the modules work together so that once you know them a little better, interesting and surprising things can be done.
You don't seem arrogant—I am always happy to discuss ideas about what makes a better synthesizer.
Hmm, I think that the patcher is a much more readable UI.