randy's Recent Posts
Fixed for 1.1!
Thanks for the details! I suspect some out of bounds numbers are getting through and fragging the oscillator. Will look at how to prevent this for 1.1.
OK, I'll have to learn about those fancy features to see if I can reproduce this.
I had some weird intermittent problem with the Configure... menu like that, then it went away in 1.0. What are your Live version and Mac OS versions?
Thanks for the thoughts. I will look at Silent Way.
Some people don't want to use a computer in their setups at all, so a racked CV converter would be a very good thing for them. You might be surprised how little a capable DSP costs.
I am making the CPU usage better every day, so I think it's pointless for me to document it in that way now.
Glad to hear that .scl will be a good choice.
Please stay tuned for an update in around two weeks.
Thanks for the detailed report. I cannot reproduce this one. But, I don't have 10.6 here so that may be why.
There are other problems with automation that I have to address. So some of my automation code will be rewritten for version 1.1, (coming soon!) and hopefully fix your problem. I'll put it in the bug database so I remember to check.
Of course I think tunings besides 12-ET are important, or the button wouldn't be there in the first place! So I would hope that seeing it can make you happy rather than sad. I am planning to load Scala .scl files.
As to when, your feedback as a paying customer makes it a priority! If it goes quickly, I can get it in the next update along with the optimizations I'm doing now. If not, then the one after that.
The details are not yet fixed, but some kind of configuration software that can do what you are describing is planned for the Soundplane A. You could configure it to have a bunch of virtual keys, and then mark those somehow on the surface. Also, I have a very simple reference pattern planned that should be easy to learn your way around.
it's much easier to get away with it
I wondered in the part why anyone would want a standalone app. I can't argue with this reasoning! LOL. I will put a standalone on the to-do list.
In the meantime I would suggest using a super light AU host like Apple's AU Lab.
It is intentional. Many controllers send out a low-resolution signal for pitch bend, with only 128 values. If the pitch bend is not smoothed on the way to the synth, there is always a clicking noise when moving the controller.
I'll have a listen and see if I can make it faster.
One voice takes about 30% of my CPU meter in Logic on my five-year-old Macbook Pro (1.83G Core Duo). So, you can do much better!
I guess the first thing I would do is try another host and see what happens. If you don't have one you can download a Numerology or Live demo.
Also, I should add: the registered version takes the same amount of CPU as the demo. So, something weird would appear to be going on.
Updates to the same major version will be free forever. If I release a version 2, I might charge an upgrade cost, but I don't even have a version 2 planned.
The "mod" dial in the key section selects the CC that is sent to the "mod" signal output. So there is one assignable controller that gets saved with each preset.
I am hearing the need for more assignable controllers.
Aftertouch is indeed a different MIDI message from control change.
Other people want this too--- it's possible but not easy. So I will probably do it, but not soon.
I would be happy to do that for fun when I get time, like after the 1.1 update.
I always recommend making a 1x1 controller (single pressure sensor) with your audio interface first. This way you can check to see if the electronics will support an 8x8 version, and hopefully have some fun.
I'm happy to answer questions about the porting and MaxForLive work if someone wants to take it on.
Thanks for the good words, Alex!
I have found a problem with parameter automation and Logic, which I think will address your symptom. So I expect this to be fixed in the next update.
Wow. I have not heard of this one before and can't duplicate it here-- this morning I fixed an automation bug and changed params many many times. And I am on Ableton 8.1.5
Try starting with an empty Live document, and put a fresh Aalto in it (click the Aalto with the little AU picture, not one of the presets) then bring the GATE level dial up. Does that work? Then click the arrows in the Device frame to hot-swap presets.
If all else fails and you are brave you could try Live 8.2, out today.
It's no secret Aalto is a huge CPU hog. I am addressing this with the next update.
Apparently, some combination of Ableton and MacOS makes the presets fail to load. I haven't been able to reproduce this yet.
The workaround is to make your presets folder by hand. Make a folder ~/Library/Audio/Presets/Madrona Labs/Aalto . This is the one that Live should be making for you. Then put all the .aupreset files from the "Aalto 1.1 presets " directory in there. The Aalto patches show up in the Plug-in Devices menu in Live.
It's gonna be OK.
Please tell me your Ableton and MacOS versions!
Thanks for the update, I'm glad to know things are working. I bet Aalto did get some "out of bounds" information that caused it to stop making sound.
OK, thanks for the report. It sounds like Aalto's DSP chain is "blowing up", or making numbers out of bounds. Why this would happen on DP and not other hosts is a mystery. I will get a demo of DP and investigate.
One thing you can try is: put a new Aalto in DP (getting the pop), load the default patch into that copy, save your document, close it. Maybe next time you can load the document without Aalto blowing up.
Host sync is coming soon!
In Aalto news, I put together a bigger collection of factory patches for our favorite synthesizer. Now there are 60 patches, more than twice the size of the 1.0 set. You can get them on the Aalto page.
Special thanks to Jesse Juup, Ben Phenix, and Crown Hill Repeater for your contributions.
When using Renoise versions less than 2.6, there is a buzz in Aalto's output at some buffer sizes or when rendering to disk. There are two ways to fix this.
Use compatibility option in
Renoise: Click on "?" in the instrument panel, then enable the "Static
Buffers" option, which will buffer and drive the plugin's render function with
256 samples - always.
Get a beta of Renoise 2.6.
Hey, thanks for trying this and sending the movie. I know what's going on with the gates and can fix in the next update.
I guess, I can not really recommend this solution for tight sequencing. I could make it so when the offset is moving backwards fast, the output doesn't change. But that is kind of messy. I think it's better to wait and put the energy into host sync.
OK, will do ASAP. This is a good way for me to spend some time helping customers today or tomorrow, because I'm not allowed to work on the code this week.
(afterthought) Realistically I can only bust out so many good patches myself, but I think a few more in the short term will help. I'll see what I can collect from our beta folks too.
I think the best move after that would be to get patches embedded in forum posts here somehow. Or otherwise shared through your Madrona account. Unfortunately it will take a little time to get with our Web guy and pull this off. But I'm thinking of bumping it up in priority.
It's a big priority, just down from performance improvements and bug fixes. I hope to include it with the next update in 2-4 wks.
Until then, you could use a parameter, like aftertouch, to get sync. Draw a ramp in your host app that takes 1 bar (or 4, or whatever) to go from 0-127, then loop that. By setting the number of steps in the sequencer to 1, and putting the ramp into the offset, you should even be able to host sync the sequencer, triggers and all. I haven't tried this, so if you do please let me know how it goes!
@clarke68 thanks for the comments. I'm glad I did it that way-- I've already heard a nice composition incorporating the demo sound from someone who can't afford the full version right now. :-)