randy's Recent Posts
Thanks for the example, i'll investigate when I'm back to work on Kaivo.
Just want to say thanks a lot for sharing—this thread should be fine!
Yes, good point about getting other tunings in there. If the module continues the Aalto / Kaivo way of doing things, then there will be a separate selector for tuning tables. We'll see if this is feasible or if it should get hacked into the zone map somehow.
There is a bug in the 1.6.0 VST that made a bunch of default presets in ~/Music/Madrona Labs. You can either go back to 1.5, or you can delete the ~/Music/Madrona Labs presets and use the 1.6.0 AU version to convert the presets again. Your old presets are still installed and unchanged.
Sorry for the hassle, working on 1.6.1 here.
I send out a newsletter every month or two. The last one was on Feb 13 called ' Aalto 1.6: free update now available'. You could check your spam folder, or try this link to make sure you are subscribed: http://eepurl.com/hsZjQ
It would not be too hard to put some oscillator code in the module and have a mode where it would output oscillators instead of pitch CVs. That might make people want tons of configuration options that wouldn't have come up, otherwise. But it seems too useful to pass up if the CPU in the module has the power.
@saemola, so, the opposite of this then? I don't know, I think it's pretty tight.
No news. Working on it, of course!
This is good info because it seems to mean the absent plugin problem can be fixed by restarting, resetting Audio Units cache, or similar.
Stuck window problem is fixed. I'm trying to complete some other fixes right now.
Hopefully I'm very close to a fix here. Meanwhile please email me at support if you need a 1.5.0 installer.
Our current idea is that you can edit zone maps on a computer, then download them to the module. On the module you can just select them. Cable-wise, I think Brian had something clever with a USB A->A cable in mind. I could be wrong.
Or could there be a Soundplane firmware update that allows zone maps to be stored on the Soundplane itself?
This is kind of a genius idea, but the Soundplane doesn't have any NVRAM.
I'm not super into the MIDI interface only idea because the really special things about a Soundplane + CV system would be lack of gear-bloat and a really fast, high-resolution connection between gesture and voltage. There could be a MIDI out though—if not in the initial module, then in a future tabletop device.
The great Expert Sleepers jacks were created by Os himself. I think we have to pat him on the back and leave those to him!
Hmm, can't reproduce. What Live version? If less than 9.1.7, can you try 9.1.7?
Hey @avantronica, tI think I understand the use of these ideas but I have to limit complexity somewhere in the plugin, otherwise I might as well just write a DAW. :-)
I know you use max but are running into some of the plugin problems in Max 7. Have you looked at Numerology? It's a mature DAW made by an awesome, independent coder, with a more sequencer-like set of features.
I plan to do a major redesign this year.
@mfrasconi, or anyone with the AU not loading, can you please open a Terminal and type:
auval -v aumu Aalt MLbs
And let me know what you see there. Maybe email the result to support @ madronalabs so that it doesn't clutter up the thread.
This will perform validation on the AU and report any errors. Thanks for your help.
@pete66, when you log in to the site here you should see a 'My Downloads' link, click that and you should see the link to the Aalto 1.6 installer.
I am keeping my replies about Aalto 1.6 bugs in the software forum.
I recognize that MIDI learn is a thing a few people really really want, but it's not a trivial feature to add. I would like to add it. Meanwhile you have the workaround of using one of the many hosts with good MIDI learn capabilities.
@evildragon thanks for the comments about the patch menu—I like your default idea and I should do that. On the sorting, I am mixing files and folders alphabetically the way the OS does it, and I think this is what makes the most sense.
That's what Apple says we should do. But practically, they made a customer support nightmare by saying files should be saved somewhere, and then hiding that directory from the user. I don't think this was a good decision and I'm trying to do the best thing for users. I'm following the lead of some other companies (like Ableton) and putting everything possible in ~/Music where users can actually see their own files.
I can verify this problem on my old 10.6.8 machine now. I will fix it ASAP.
Meanwhile, your old presets are where you left them. You can go back to Aalto 1.5 to use them.
I added a license for the Aalto 1.5 download to your account in case you did not save your installer.
Glad it's working for you.
I will add search here soon. meanwhile you can go to google and type for example "site:madronalabs.com tuning tables"
OK, I needed some good news today!
Great news thanks!
This should make a fix easy to find.
The 1.6 update has brought with it more bugs than usual. Sorry for any inconvenience.
1.5 installers available
For those of you who didn't save your previous installers, and are hosed, I made a 1.5.0 installer to help you get back to work ASAP. To download you will need a license for the special 1.5.0 product. Ask by emailing support @ madrona labs . com and I will send you one.
I'm going to make threads for the various issues people are seeing. If you see your issue being discussed in a thread, what can help me most is if you simply chime in with your OS / Host specs so I can get more data.
Yep, it's easier for everyone if there's only one place where all the patches go. So I just use the name to file the factory patches.
I'll change it to look for "Aalto[space]" in the next version. Or I guess I could do something more clever like look for dash Aalto and then leave out the dash. But in my experience cleverness usually leads to more problems later...
So, I have Yosemite installed here and can reproduce the 1.6 issues with Live. The good news is that there only seems to be a problem with the 32-bit version. 64-bit is working fine.
On the 32-bit version the following things happen:
- AU version does not load at all
- VST version has the blank window problem
This is with Live 9.1.7 32-bit, Aalto 1.6, Mac OS 10.10.2.
I'll get on this next week. Meanwhile, please try the 64-bit version of Live if you are having problems.
Sorry you're having trouble, I will give this a try ASAP.
One thing that might help in the meantime is using a different process buffer size in FL / Studio One if possible. Do you know what buffer size you are using currently?
The patches come with the demo installer. But I think I see: maybe you want to install just the patches. I should make a patch-only one. Meanwhile, you can just run the demo installer, and then run your personalized installer again. Or move the .dlls in VSTPLUGINS yourself.
Thanks for the additional info, I appreciate it.
That was quick.
Sorry, you are going to have to remind me what drawing problem you are talking about though. I'm going to be doing updates a lot more frequently this year, so hopefully I can get you a fix soon.
[EDIT]
never mind, I guess you mean the one above. I have Live 9.1.7 and it's working fine, so I'll have to try Yosemite now.
So the information on JUCE is not right, because I am using the latest version.
Hey, it's out!