randy's Recent Posts
Sorted.
Thanks for the feedback. Everyone wants to lock something different, so I decided an arbitrary parameter lock is the way to go. Lots of details to figure out wrt. UI but I'll definitely do this at some point.
At some point I had a diagram with shielding between each column / row carrier. I have since determined that this isn't really needed because the capacitance between two thin plates side-by-side is very small.
I would start with carriers connected to outputs and pickups connected to inputs. The rest really depends on your audio interface. You can start with only the + connection to pickup or carrier. My guess is, you will want to connect the - connections of pickups and carriers together.
I look forward to seeing your project!
Thanks for following up with the solution. I'll look into adding better error messages or otherwise improving the experience when this situation comes up.
Sorry you're having trouble. The GIF didn't make it—you can email it to me at support if you'd like.
If pasting the license goes OK, but the plugin is not licensed the next time you open it, there was probably an issue with writing to the disk. Maybe you are running as some account that does not have permission to write to the license directory? You can try copying the license to the directory by hand to find out.
On Windows, license files are in C:/AppData/Roaming/Madrona Labs/Licenses. When the plugin starts up it looks for a file with its name “Aalto.txt” “Kaivo.txt” etc. in this location. The file is a plain text file that contains the license key. So, you can try looking there to see if there is an old license.
Unfortunately these AppData folders are now hidden by default in Windows 10. To see them, try this tip: http://www.pcworld.com/article/2690709/whats-in-the-hidden-windows-appdata-folder-and-how-to-find-it-if-you-need-it.html
Thanks again. Great reportage! This is very helpful. I'll investigate ASAP.
Please keep me posted. It's hard to imagine what the cause might be right now, because the LFO is such a simple and bullet-proof object.
What kind of CPU are you using?
Thanks, will look at it soon.
You could use MIDI MPE, sending out a control on one channel to affect the pitch of just one voice. Then have a few of these controls for different voices.
It seems like you are starting with two sources of data, one from say a sequencer and one from a controller. In my view you want to first merge the sources into one, then send them to Aalto. You have some particular vision in mind for control and to get to it you are probably going to need control over that merging process.
I think of OSC and MIDI as different languages, French and English, say. I have one translator device that allows me to tune into either language and understand it perfectly. But if I bypass the translator and try to listen to input in both languages at once, it's very confusing. This is a good description of the architecture going on inside the plugins.
Working on both-- the new detection takes a lot less expensive filtering. I'm excited about it. I'll be at beta within a week, I'm pretty sure. I'll clean it up for that release, so I'd wait just a bit. It will be very helpful if you can try compiling it for Linux at that point!
You know the Soundplane Zones can send MIDI controllers out right? So Aalto should be able to take notes from a MIDI sequence and controls from the Soundplane at the same time, just as you suggest above, by using MIDI.
Also you can send out rhythmic patterns from the sequencer and at the same time use the Soundplane for pitch, in either OSC or MIDI mode. Unlike with most software synthesizers, pitch and gate are patchable in the matrix. You are free to use any signal you want to control oscillator pitch. So it's pretty flexible already.
Hmmm. Big Hmmm. Thanks for the detailed info, this one is new to me.
When the dials get stuck, can you hear that the signals they control within Aalto get stuck as well? I think you are saying that's the case, but that's probably the most important clue for me to start thinking about.
Meanwhile I'll try to set my Windows 10 box up to run at 96k by default, and see if I ever run into this.
Also, if you can keep a list of the specific parts that get stuck and let me know, that would be helpful.
Thanks for the info about Steinberg and u-he. I just don't have a timetable for this. There is no one more sad about it than me. I am the only programmer making instruments for this small company of mine and I don't have time to do all of the cool projects I would like to.
Yes, I put a fix for this in the previous update 1.3.2.
Can you describe how you want to use this in more detail? It doesn't make sense to get notes from MIDI + OSC at the same time because they would step on each other and create stuck notes. So I guess you mean other control data. What kinds are you interested in? Thanks
Thanks for the reminder. I have been completely immersed in making a new Soundplane touch detector. Very soon I can get a beta of this out and then I'll look back at Kaivo.
Sorry, I sort of hid this information. It's in the readme: http://madronalabs.com/media/kaivo/_read_me_first.txt
I use Audacity (free) to make the files.
Thanks for the report, I'll try to duplicate this.
testing
Oops, sorry I missed this the first time around. I'm glad to hear Virta is making creature voices! No promises about AAX but I hear you and I'll check into AAX support again one of these days.
These posts asking for DIY help appear to be fairly elaborate spam. The questions are copied from electronics.stackexchange.com and links to kynix.com have been added. The other poster has a kynix.com email.
I have suspended the users.
Hmm. Can you get this problem with any of the factory patches? If not, can you please email me the broken patch?
Thanks for the report. Can you send me the scale that is failing to work?
Well, I definitely appreciate the sentiment behind this idea. I want to play Aalto forever too. And longevity of tools is also a big concern.
I do still have plans to work toward a kind of general-purpose music appliance that could run Aalto. So imagine this: a little box with great audio I/O on it, and a cable from that box to a tablet running a graphical interface. So you put your tablet + appliance on the shelf and 20 years later, they should still run.
I guess that's not too terribly different from just having an extra laptop that you never update and putting that on the shelf.
To make a really good hardware Aalto, I would have to put a touchscreen with the patcher UI in the middle. And then engineer a custom rotary encoder / display for the scope dials... OK, I can imagine it still being useful without full-on oscillating dials. This is maybe within the realm of possibility.
It makes sense that a "Madrona host" would have Soundplane input.
For something very minimal, savihost is a pretty cool idea.
Ableton Link looks interesting for syncing with other apps.
I have been thinking about a very simple host with an audio recorder. doing it that way keeps the number of versions of things I have to build lower, which lets me make more things.
Hi and welcome aboard! Thanks for the nice feedback.
Safe travels!
Hi Michael. Thanks for the report—I'm sorry you're having trouble. Can you send me the patch you are using? You can just choose "Copy to clipboard" from the main menu then email it to support at madronalabs.
I'm surprised to hear that freezing has become worse for you. I tested here any couldn't get any freezes with these versions. But maybe there's something that instigates the freeze that I was not doing. I would love to fix this once and for all.
I see a few requests for help about electronic circuits. That's fine but this probably is not the best place to get an answer! I started this section more to answer questions about the Soundplane theory and help people making a homebrew version. I'm not that skilled at electronic design myself, in general.
Here are a couple of online forums where people seem willing to respond to newbie questions:
http://www.electro-tech-online.com/
http://electronics.stackexchange.com/