randy's Recent Posts
OK, I see, thanks.
Yes, the version is your problem. You are running 1.4.6. You have to find that old plugin and remove it.
I don't know anything about Studio One, but some DAWs can have an optional VST Plugins folder of their own.
Are you sure you are running the Aalto 1.7.0? You can check in the registration area in the plugin. An older version will not load newer patches. A newer version should load older patches just fine.
/AppData/Roaming ... is the right place. It will use the current user's files, so you could have problems if for some reason it was installed as Administrator and now you are running as a different user, or vice versa.
I hear this would be cool, but to be honest it's not high on my list of features to add. The main reason is that these areas where the plugin communicates with the host are the ones that give me the most trouble. Different hosts can behave differently and require a lot of testing to get things right. The clock input is one example. Getting clock sync right across all the different hosts I'm testing on took a long time.
Meanwhile rendering out a click and triggering other sounds with it as you suggest, is a cool idea. I always prefer working in audio over MIDI anyway.
p.s. until we add a search bar you can type "site:madronalabs.com mysearch" into Google.
Weird, I'll check it out.
Very nice sound design and demos!
For patches like "ARP Mad Sciencist" and "PER increasing feedback" it would be helpful if there were some notes, so people know that they need to turn the host clock on or whatever.
I know it would be cool to put notes in the patches themselves. I have this as an Aalto 2.0 feature.
Hi, I'll try to answer your questions about Aalto CM. It should work well but is lagging behind the main Aalto release in several important features. I believe it's at par with version 1.5. For a list of new Aalto features since then you can look at the README for Aalto: http://madronalabs.com/media/aalto/_read_me_first.txt
If you install a newer version of Aalto it will install over the CM component. You can save the CM component by copying it from /Library/Audio/Plug-Ins/Components to a safe place.
CM edition is not Retina ready. The release version is better but you may still see some blurry displays. This is because drawing all the animating dials simply takes too long on a Retina display. In the future, I will use OpenGL to accelerate the drawing.
I am planning to add a search button here. Meanwhile you can use Google to search for things on this site. Type in Google's search bar "site:madronalabs.com Aalto CM" (for example).
There are a bunch of ways you could make Aalto start up when you want. I would automate some parameter that turns the sound off / on. Like the gate level. Or you could modulate something outside of Aalto, like the channel level.
Or, you can change the patch so it only plays when a key is held down to get more control. turning on 'key trig' in the sequencer and using the envelope to get the signal, you can get a key-controlled drone, then just use a long MIDI note to control the sound.
There are sometimes glitches with the sequencer with Live 9.x and Aalto 1.7, after a few minutes of playback like you describe. There will be a fix for this coming soon. To work around this you can add key control as I'm describing above and then restart the sequencer with a new note every few bars or something so it will stay in sync.
Hmm. I have heard good feedback about El Capitan. I'm not sure how to go about reproducing your issue.
Possibly your Audio Units cache has a problem. You can try removing the cache at ~/Library/Caches/com.apple.audiounits.cache, and then removing and reinstalling the AUs.
Yes.
I tried to implement the canDo as per Bitwig's suggestions, a simple thing. Too bad to hear it is not working. I am in touch with Bitwig and will investigate. Though OSC is going to be more important long term, I want to help make MPE support as smooth as possible.
OK, I'll reexamine all this after I get the Virta beta out/ Thanks for the detailed feedback.
Are you moving to Bitwig as your main DAW now? I guess that means you are liking it? I haven't heard from too many Bitwig users yet.
Cool, thanks for the update.
I'll definitely announce any sales via the email list as well as the website.
Getting there!
I haven't done pre-orders but I wouldn't rule it out. I assume most people just want to pay when it's done, and they can have their software. What about a pre-order is attractive to you?
Hey thanks for the nice feedback. I'm glad to hear my intentions as far as usability and sound are coming across. What you're describing is the way I think of them too.
I wanted the focus of Kaivo to be making timbres from a sound as more of a palette, not so much playing back samples. And didn't want to add the complexity of a scrolling interface. And also, until version 1.2 all samples were loaded into RAM immediately when the plugin was made. There are all reasons why I made the maximum length short.
When the "key/seq" toggle is set to seq, the envelope is triggered by the sequencer gates. The gates are turned on with the blue toggles under the sequencer. The left gate output controls seq 1 and the delayed gate output controls seq 2. That's all there is to it.
What @garf said.
@stefagleykin, do you mean Madrona Labs, or @kroaton?
All the source and instructions for my Soundplane 8x8 project are posted at http://madronalabs.com/DIY.
In MPE mode, x and y are always controller #s 73 and 74. You can see all the outputs for the different modes here: http://madronalabs.com/topics/4718-key-outputs-by-protocol
OK thanks for the report, I'll look into this.
Yes it would.
The bent pitch would always line up with the notes on the grid. There is no concept of "bending" separate from the grid of notes actually. There are only the notes on the grid and spaces in between them, which interpolate the grid points. So everything always aligns.
Did you go from 1.5 to 1.6 or higher? The preset format changed with that release. Choose "convert presets" from the main menu to get all your presets moved to the new format.
Did you try turning animations off and closing the window to see if it was graphics issues?
OK, I understand a little better. Originally there was no menu for selectin gprotocol—it was all automatic. Then when I added the menu (because of MIDI MPE support), is stopped being automatic.
Auto detecting t3d is not what everyone wants—imagine a system where you have t3d data flowing from your Soundplane but you want to use another Aalto or Kaivo via MIDI.
I think that Aalto should remember the last manual protocol setting and use that as the default for the next instance of the plugin created. Unfortunately there is no "plugin class preferences" that would allow this to be implemented easily. I don't see a problem with adding it and have added this to the features list.
The video right now would be me going back and forth between XCode and my coffee maker.
@spacefunk, you selected a patch that plays continuously. Unlike most other software synths, Aalto can play when no notes are being played, just like a modular synth. if you select any patch that does not play continuously, then turn up the level in the GATE module, you will have a drone.
Clicking on other channels can cause Ableton to send clock information which may affect the sequencer. It all depends on the patch.
In the Aalto track, are you playing notes at 4:60? These can cause Aalto's sequencer to restart if "key trig" is on in the SEQUENCER module.
The correct behavior should be: changing the preset never changes the input protocol selection. So it shouldn't be restoring it. That information is stored in a song, but not in a preset. I think you are saying the following:
- given: you have OSC input working in Aalto
- action: you load a preset using the preset menu
- result: OSC input stops working
- result: the OSC protocol menu does not change
- action: select MIDI input protocol, then select OSC
- result: OSC input works
Is that correct? You don't have to be quite this pedantic when submitting bug reports, but from your language above I can't tell what steps to take to reproduce your problem.
You mention AU presets only. Does the VST work for you?
Thanks for the report.
Not currently, but I want to add OSC control over all parameters, including matrixes like the patcher.