randy's Recent Posts
This is fixed for 1.6, coming very soon.
Hi K, you might try the muffwiggler or monome forums as well! Those places are a bit more well-traveled...
I haven't put much time into that—I guess most people are making their own. Anyone got one to share?
I did do a tweak to the control signals to allow the Soundplane to play the existing Aalto / Kaivo presets more gracefully. this will be in a Aalto / Kaivo update soon.
This is a limitation of the Soundplane software right now. Currently all simultaneous touches have to be more than approximately one inch apart from one another. I can see how the design leads you to apply guitar technique, but really the Soundplane is its own thing — more like a continuous surface that is multi-touch, than a collection of keys played discretely.
The good news is that I think I can do a much better job of distinguishing adjacent touches in the Soundplane software and this work will be happening soon.
Thanks for the feedback. Due to the way the models are constructed and computed, you can't really morph from one to another, unfortunately. Cool idea though.
The values are always on a 1.0/octave system. If they are quantized, they will only fall on the notes of the scale you pick. If not quantized, they can represent any pitch. Either way, the 1.0 / octave system is used.
Think of it this way: 1.0 / octave is the scale of pitch measurement, just like feet or meters are scales of distance measurement. A signal in the patcher has no meaning, it's just a number. Let's say it's 2. Then patching that 2 to a pitch input gives it the meaning A5.
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.