hey all, anyone else noticed this?
i've tried using the mod wheel on my controller a few times before now with Aalto and it never worked, so i just assumed that my modwheel's CC was wrong and forgot about it til now, but i've just checked it properly and it's firing out CC1 as it should be. all my other softsynths pick up the mod data fine. this is using Live 8.2.5 on Mac 10.6.8.

also tried sending mod data via a Live clip and that doesn't work either - Aalto is just deaf to mod data here.

another very small thing i noticed: the 'Pitch' output light doesn't actually light up when receiving downwards-pitching pitchbend data (upwards lights up ok)

randomisation rarely makes anything useful, and mostly just sounds like random noise, something that's very easy to do with Aalto anyway. it can be cool for happy accidents, but there are more elegant ways of coming up with new sounds easily. one possible cool alternative is preset breeding, where you choose 2 presets ('mum & dad') and have a morph slider between the 2, similar to Reaktor or the vintage Greenoak Crystal vst.

hi randy, i've come across what i think is a bug in 1.2.6 vst, where voice 1 becomes 'rectified' (only playing half the waveform, usually the top half). voices 2, 3 and 4 always play fine.

even though i've seen this a few times now, i can never pintpoint the cause or series of events that lead to it. next time i see it happen i'd like to grab a log snapshot to send you so you can see for yourself. where's this log stored? in previous versions of aalto there was that little square on the right hand side that opened a live log but its not there anymore...

hey randy - just happened again! lots of tweaking of the default patch into some bit noisy drone thing, then got bored with the patch and hit 'default' again - rectified 1st voice! is there any log i can grab while it's open?

TIP! map Aalto's 'offset' dial to a 16-note keyspan in Ableton Live to trigger Aalto's sequencer from wherever you want. great for when you've created a sequence in Aalto that you then want to chop up in realtime.

to map 'offset' to a keyspan, open the Live device view and click 'configure', move the 'offset' knob and it'll appear in the control list. select it and go into midi map mode, hold down C1 and tap D#2.
now all steps in Aalto's seq are mapped to your keyboard/pad controller. mash away!

this is either a great 'easter egg' feature or its a great bug!
i've been messing with the unison mode with the 'voice' patched into 'offset' and using the seq to create one-note chords etc. and am getting some incredible sounds. but something i just noticed was that the unison detune amount can be altered with the last fader in the seq. so for a 4 note unison chord (with offset input of 1 tick on the dial so 4 voices are playing at once), the number 4 slider will affect the de/tuning of the unison notes! is this a sneaky easter egg behaviour, or are things goin weird at my end in a really cool way ?

[edit] ok it only happens when making a preset from scratch using 'default' preset and only while using the vst version (au works as expected) so its some kind of really cool bug i guess. i can't copy-paste the preset here as i'm still using a demo, but i can post a screengrab if anyone wants to try out the 'quirk' ?

[edit2] ok, loading up the preset 'aalto techniques > seq chord' will show you how its patched, BUT this preset doesnt do the unison detune trick on the last slider, even tho all settings are pretty much identical. but making it from sratch still shows the same odd-but-cool behaviour...!?

ahhhh ok, yea changing the rate brought all 4 voices back under control. i don't think i fully understand your explanation but at least i know how to change it now! thanks for explaining. it'll sink in one day :)

now its my turn to be confused! not sure from your reply whether you mean its a bug or a feature..?! the odd behaviour doesnt bother me but there are some irregularities in the way it works. eg:

try the preset 'aalto techniques > seq chord'

as you can see, its patched the same way as my vid example, but the difference here is that all 4 sliders in the seq affect the tuning of the 4 voices FULLY, whereas with the newly created patch example in the vid, the last slider only partially affects the tuning of the previous slider's voice.

strange things are afoot!
i'll leave it with you anyway - still having fun here

hi, just installed the 1.2.1 update to try the bugfixed seq, but it seems its still broken. moving the sliders in the seq doesnt produce audible clicks anymore, but it still becomes unresponsive after a few tweaks.

i also noticed that the 1.2.1 vst's creation date was 9th of this month, over a week ago. does this sound right to you?