randy's Recent Posts
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. :-)
Now that Aalto is out, I'm making a new forum topic for support issues.
Please use this thread for questions and issues that don't already have their own threads above.
After reading the Reaper manual and looking on their forums I can't figure it out either. Waiting for a response from their forums.
I will get Reaper and test ASAP and see what I can find out.
Problem: Aalto fails to validate and appear in menu when running Logic in 64-bit mode.
Solution: Switch Logic to 32-bit mode, then validate. When switching back to 64-bit mode, Aalto should continue to run fine.
thanks @bobbyrich for the solution. Anyone with additional info, please post here.
I figured out the problem. I switched from Logic 64 bit to 32 bit mode and alto validated.
OK, super. Thanks for the report. I'll make a thread so people can find this answer more easily.
@bobbyrich the validation bug reported before is fixed on both versions now.
Did you put your component in ~/Library/Audio/Plug-Ins/Components? Restart Logic? Sorry I haven't heard of this problem before.
Aalto is currently an Audio Units (AU) plugin for Mac only. So, you will need to find a host that can host AU plugins. These are like VST, but a different incompatible format.
For starters I might recommend Numerology. It has a lenient demo mode that actually allows you to save your work, within limits.
@heath you can do it by patching any signal that is different for each voice to the sequencer rate or offset inputs.
The preset "adorable gleeps" has a clear example of this.
This is a thread for anyone having trouble with parameter automation. i have tested it in Live 8.1.5 and in Logic Pro 8. it works fine on both of these platforms for me. Some of you have reported issues with Logic. Let's collect some info so I can figure out what the problem might be.
If you have have problems, please list:
- Mac OS version
- Application version
- Detailed description of what to do to cause the problem.
@walker: I'm going to start a thread about parameter automation.
@sensi: One day, yes. For now Aalto has a low memory profile so a 64 bit version would not give any improvement.
I'm going to leave the thread up so people can find it if they have the same problem. But I'll go ahead and make a bold note
@dsk but of course! There will be a special version for Aalto with x, y and z inputs to the patcher. In fact, I initially designed Aalto to be used with the Soundplane.
@kaput, sorry i missed your post earlier.. . Automation works fine for me in Logic. I made a thread for this issue. Please reply to that thread with a more detailed description of what goes wrong and let's figure it out.
Try patching the pitch or voice or vel outputs to the sequencer rate. You will hear that each voice's sequencer runs at its own rate. in fact there is a SEQ module within each voice, but all of them share the same patch inputs.
The offset input also affects each sequencer independently. You can understand this if you study the factory patch "adorable gleeps."
Sorry about the problem. I'm going to try to figure this out soon to get a fix in the next update. I don't have access to an Intel Mac Pro so I might ask to send you some debugging versions to try if you have time.
For now, making your watermarked copy is a manual process. I'm doing them within an hour or so this morning. Thanks for your support.
@yasha, thanks for the report. I'll look into what could cause this.
I know it's a big CPU hog and hope to improve it lots over the next month or so.