randy's Recent Posts
I'll start the topic off with an easy one.
*Why "Aalto?" *
It's the Finnish word for "wave."
Will this be a VST or AU or what?
Mac AU and VST will come first because that's the platform I am developing on. Windows VST will follow soon.
When can I buy the Windows and Mac VST versions?
My current plan is to get the Windows version out, along with the Mac VST, in mid-December.
There is no copy protection. Copy protection always creates hassles for legitimate users, is by definition a hassle. When you purchase a license for Aalto, you get a watermarked copy that uniquely identifies it as yours. At runtime there are transparent checks to verify that the watermarks are intact, and that people are holding up their end of the license terms.
Sorry i didn't see your note for a while! The Mac VST version will be out with the Windows one, my best guess is that this will be in mid-December. Yes, it will run on 10.5.
Thanks for this information! It seems there is some problem with Logic and Aalto and multi-CPU machines. I am trying to push the 1.1 update out the door now, which should make it better overall. I hope you stay tuned, and let me know if the 1.1 demo works better for you.
I totally understand. I will look at solutions for you for the next update after 1.1.
So, Aalto is an Audio Unit plugin. You need to run it in an AU host such as Logic or Live. Max/MSP is also an AU host, if you use the audiounit~ object. So, I would look into running Aalto directly in Max/MSP.
Maybe try some very simple AU synth with audiounit~ first, to get something working.
I don't have anything like an "Aalto patch" though. Aside from some early prototypes it wasn't made using Max/MSP.
If you explain what you want to do that you can't do now, I can try to help. Have you tried using audiounit~?
Yup, here I am working on it. Thanks for your vote of confidence!
Fixed for 1.1 bud!
OK, you demonstrated this and it looks like an issue with logarithmic controls. I will see what I can do.
Hopefully next week!
I think this is fixed for 1.1.
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.