randy's Recent Posts
The sequencer's output is quantized inside the sequencer module. So this same quantized signal is the one that is sent to the oscillator pitch, or any other parameter.
All the quantizing is designed around a 1.0 / octave system. This means that a change of 1.0 in the value of the signal will produce a one octave change in the pitch. For example, 0 = A3, 1.0 = A4, 2.0 = A5. The oscillator pitch input is set to 1.0 / octave if the pitch input attenuverter (little dial) is set to its default.
While you can send the quantized signal to other things, quantizing doesn't "make sense" for most parameters in the way it does for pitch.
It's fixed and will be out within a couple of weeks.
It's an American Apparel unisex size small.
https://www.americanapparel.net/sizing/default.asp?chart=mu.shirts
Thanks.
Thanks.
MIDI learn is on my list for v.2. Thanks for checking in again.
MIDI learn is on my list for v.2. Thanks for checking in again.
Only the pitch control for the oscillator, and not other controls? That is very strange and like nothing I have heard of. I hope 1.6, coming within a few weeks, will fix this for you. Please stay tuned.
This will be fixed when you have a folder ~/Library/Audio/Presets/Madrona Labs/Aalto. See my other message.
A few people are seeing errors with presets installation. I do not know what the problem is yet. I have had people check file permissions and so forth, but there are no clues.
A solution for now: get the following zip file:
http://madronalabs.com/media/temp/Aalto_presets.zip
Unzip it, and put the resulting "Aalto" folder into ~/Library/Audio/Presets/Madrona Labs. Then you will have done what the installer does, and the presets will appear in the top menu inside Aalto.
To get to your Library folder 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, and why I’m moving the presets again in the next version.
Hi, sorry about this! I know, it's been an issue for a while and will be fixed in the update after the coming 1.6. Please stay tuned.
Sorry, only smalls left now.
There's been a lot of work done with Madrona Labs’ instruments and OSC (Open Sound Control) lately. I’m not sure why the sudden flurry of developments—maybe winter is suited to working on these plumbing/scaffolding types of activities. In any case, I'm very happy to see it. Open Sound Control is much more suited than MIDI for handling the high-resolution, rich, per-touch data that comes from instruments like the Soundplane.
First, here are a couple of videos from António Machado, showing his work with a Haken Continuum, Kaivo, and Aalto. He uses the EigenD environment and an “agent” (EigenD object) written by Mark Harris to give high-res, note-per-touch data to Aalto and Kaivo. It’s rare to see a techy video that is this enjoyable to listen to in its own right, so a big thanks to António and Mark, and please enjoy...
With his Soundplane, Mark goes further into the details of the agent and builds a modular synth step-by-step in the EigenD environment in a series of videos:
Mark has been busy— he has also put together some instruments that work in Reaktor over OSC. Reaktor-enabled Soundplane owners take note! These can be found here on the forums.
Developments like these get me excited to support the next steps with new software features. I plan to offer more and more flexibility for expert users. But in a way, that is the easy part. The flexibility needs to be there, but without getting in the way of the simple experience, where you just plug the instrument in and it works immediately, offering an intimate connection to your music.
Yes.
Thanks for the report. This will be fixed in the next update.
First I've seen this, thanks for the report.
being sent over UDP, t3d messages can theoretically arrive out of order. I have never seen this happen myself however.
possibly this could be circumvented, by watching frame messages, and if we haven't had an update since N ms, then turn the note off.
I think this is the best solution, since for most applications receiving OSC it doesn't seem to be a problem. We could also add an optional "resend touch off" to the Soundplane app.
I have more work to do on timing, and plan to use the bundle timestamps to remove the jitter you are seeing. Practically, it doesn't seem to be a big issue for the continuous data. I find that a slower rate like 100 Hz or even less is enough to transmit anything my fingers can put out.
This could be just an oversight. I guess that the channel for a note row can override the overall channel set by the UI dial.
see your email.
Will the sale run until a certain time tomorrow (Dec 10)?
Until the end of the day today, Pacific Standard Time.
Hi Reptil, In the past I have heard of some issues with multithreading that affect Xeon machines in particular. I have made a bunch of changes in Aalto 1.6, coming very soon, that might fix some of these problems. They will also be rolled into the next version of Kaivo soon. I hope you will stay in touch, test these coming versions, let me know if things improve on your system.
Hmm, odd. Thanks for the good and detailed feedback. I'll check into what changed from 1.0 to 1.1. A rate of 0 is weird from a math perspective sometimes, but makes sense as UI meaning "never loop unless triggered." It's possible there are some subtle issues here I missed.
Thanks for the feedback. This will be fixed in the next update.
Kaivo is not an application, it is a plugin in VST and AU formats. You will have to use it with a VST or Audio Unit host. Some of the popular hosts are Ableton Live, GarageBand, FL Studio, and so on. How to load Kaivo depends on what host you are using.
The plugin should be in /Library/Audio/Plug-Ins/Components. To get here in the Finder, the path starts from "Computer" then "Macintosh HD" or whatever you have your system hard drive called, before "Library." But there's no reason you should need to go to that directory. The plugin will show up in your host, however your host accesses the list of plug-in instruments.
The multiple channels in the granulator source are like a palette of waves. The sound comes from a crossfade of the two tracks bordering any x, y position the grains are coming from. So, the number of channels in the file doesn't really have any connection to a multichannel output.
I might do quad versions of all the plugins if there is a demand. So far just one or two people have wanted this so it's a ways down the list.
Glad to hear, enjoy!
OK! Thanks for the feedback.
I have to get the Aalto update out first, then will address this ASAP.
Hi Rastko,
First thing I'm wondering is, did you do "select carriers" for your Soundplane? This looks at all the possible frequencies and chooses the ones with lowest noise. If you do this you may stop seeing the jittery areas. Go to Expert -> select carriers. The result will be saved in the Prefs file.
In any case the Jitter is radio-frequency noise at some frequencies. Normally the "loudest" noise is from the Soundplane's own power supply, because the frequencies in question do not travel far. But it's possible there may be external noise sources. So if you do "select carriers" when you are seeing the worst noise, you will guard against that particular noise source.
X and Y are absolute positions from 0-1 across the surface. dX and dY are the change in position after a touch is started, until it ends. So, moving right makes dX > 0, moving left makes dX
The matrix switch sends the raw touch matrix over OSC. It is not normally needed. You can see the example Max/MSP patch for an example if you are interested and Have Max/MSP.
Please see your email.