randy's Recent Posts
Hmm that's odd, I haven't heard of any CPU problems with Aalto 1.5. I'll try to duplicate this here. What OS are you running?
Things to try:
- make a fresh Logic project, make a new Aalto, and try that
- make sure buffer size in Logic prefs is something reasonable, like 256
- close Aalto window, does performance improve?
I haven't heard of the password problem either, sorry-that sounds like a nuisance. I wonder if clearing your browser cookies might help.
Blast. OK, I see the key trig issue and will get a fix out ASAP. Thanks for the report.
The date on the archive files themselves is what I mean. You should be fine.
The typo actually affected both Mac and Windows. D'oh. I posted a fix, still as version 1.5.0. The release date on these new downloads should read February 16.
all of my patches lack of the x vel setting in ENV 1 - so they sound different. this is not acceptable by any means
eek, a typo in the Windows version somehow made it through testing! I'll send out a 1.5.1 update today.
Thanks for the quick report.
The slower UI is actually by design. Aalto does a lot more drawing than most plugins and this can really bother some hosts. So I have slowed down some things to avoid clicks in the sound in high-CPU situations. I don't like seeing this either but after all, it's the sound that matters! Someday i will have a full OpenGL interface and we can get back up to speed.
I just posted the 1.4.1 update to the Mac version of Aalto. This fixes the Logic validation problem some people were seeing on Mac OS 10.8.
The Windows version is unchanged for now.
Mac users, please note that using the Aalto installer on OS X 10.8 requires that you control-click to open the installer to get past Gatekeeper’s code signing. Now that I have a computer running 10.8, I can address this and some other details that come up with the new operating system and Retina displays very soon.
There is still some issue with the user presets in the installer, but I can not wrestle with Apple’s PackageMaker any more today. Installing the user presets from the demo version should work for now until I have time to tidy things up more.
It's damp and chilly, and I hear the gray pitter patter of endless rain. Looking out my window I see gray sky, gray water, gray trees and gray clouds. That's right, it's Christmas in Seattle.
Because of your support of Aalto these past few months, I can now work full time to bring you more software and hardware to make music with. And that is something I am very thankful for. I am very excited about what we will have to offer this coming year: Aalto for Windows, the Soundplane A, and more software instruments that are even farther off the beaten path.
As a small way to say thanks, today I'm releasing Aaltoverb for Mac OS X. Aaltoverb is just the reverb section from Aalto, packaged up as its own plugin and with mix and brightness knobs added. It won't replace your ValhallaShimmer, but it is easy on the CPU and on the eyes, and I hope it makes a nice addition to your box of colors. Download it here: [Aaltoverb.dmg]
Happy holidays and all best wishes for the new year!
[edit]
And, a day later, Aaltoverb 1.1.1 is out! During my morning-after listening I found I had changed the sound a little too much when adding the brightness control, taking away some of the magic. So now the brightness is not as useful but the magic is back.
OK, thanks for the update, I'll try sending you an OpenGL-free version in a bit.
I have sped up drawing to the screen using OpenGL, and it works on Mac and Windows here, but I wonder if this is going slower on your machine for some reason.
Do you know if you have a recent, or any, OpenGL driver? A good place to start looking would be here: [http://www.opengl.org/wiki/Getting_Started#Windows]
If you want to try upgrading your drivers that would be interesting. if not, maybe I'll send you a version with OpenGL turned off and we can see what happens.
No, that doesn't help. Just to be clear about what I mean regarding UI responsiveness, I'm referring to things such as the shape of the envelope not updating smoothly when changing parameters. Aalto's envelopes are snappy and redraw immediately on param change. Kaivo's seem to lag heavily. Same with the noise offset. I have no idea if this is my machine or if others experience the same thing.
Thanks for explaining better. So, that's not a problem. Because Kaivo does so much drawing, I do draw those things like envelopes at a lower priority so they are less likely to get in the way. Aalto is going to be more like this with the next update.
e: Displaying the Kaivo window makes my CPU load meter jump from 4% to 60%. Hiding it drops it back to 4%.
What if you turn 'anim' off, what does that do?
Yep! It's going to be a little while after Kaivo comes out, stay tuned.
Hmm, well I think that machine should be running more voices!
If you close the Kaivo window, does that help? It's possible there is something weird going on with graphics.
If you stop audio, does the UI become responsive?
thanks
I still can't play more than 2 voices at once without some serious breakup and the UI is highly unresponsive.
Ouch, what kind of CPU / OS are you running? 32 or 64 bit? Thanks.
Kaivo is in beta now, shipping next month. Thanks to Surachai of Trash Audio for the demo.
I am working to get it out this month. Please stay tuned for a release date.
It could be that the waveguide is at a setting where it is feeding back forever.
There is also the possibility of a plain old stuck note. I try to avoid them but with some hosts they are bound to happen. If you see this a lot please let me know what host you are using.
Thanks for the update. You see why I hesitate to dive into people's Max patches. :-)
Thanks for the feedback. I would love to do that but I have other fish to fry right now. In the meantime you can use Google search, just go to the Google and search for "site:madronalabs.com fish" for example (3 hits related to tacos, before this post!)
In other words, you send a message to one plugin, and both plugins appear to receive it?
Do you hear the change in both plugins, or simply see it?
Please email me a patch to support @ madronalabs and I will take a look.
Oh no a case of the blues... and cowboys too... I'll make a big noise about shipping Kaivo, so you can stay tuned to the mailing list for that... then shortly thereafter will follow the announcement you are waiting for.
Hola,
I am not getting an aleph from the first run. I would be excited to work with one, but I have to work full time on Kaivo at the moment anyway. So there will have to be a computer in the mix for now.
A3 is the real center. So there is a bug in the manual. Thanks for pointing this out!
Hey plusch, welcome and thanks for sharing.
The thing is, it won't be useful the way most modulators would be useful, because the sound will be interrupted---one kind of model has to be built and another one taken away. But I can see it would be handy maybe if you had a control surface and were designing patches.
The thing is, it won't be useful the way most modulators would be useful, because the sound will be interrupted---one kind of model has to be built and another one taken away. But I can see it would be handy maybe if you had a control surface and were designing patches.
Would you say those factors you mentioned or less /equally/more important than the voice amount itself in terms of cpu usage?
Er, well, it's changing every day right now--- I'm just working to make it better.
one request for the final version: sample changing / model type / body all midi controllable. On Live I am unable to access those with a midi controller, but maybe it's just a Live thing, does it work in other hosts?
This is about the menu controls just not working with MIDI right now. I will see if I can add that.
Nice. Welcome and thanks for the waves!
Different models take up different amounts of CPU. Also, low notes on the resonators take up more CPU.
I'm going to add "none" as resonator / model options so people can save CPU or test things that way.
yes
@abstractcats I have no idea what that could be. Maybe it's just related to the ungodly CPU use at present. Let's keep an eye on it in future betas.