sure it would be nice to have standalone MadronaLabs synths, but as mentioned there are simple ways to host a plugin.
my observations concern only multi-instrumental situations, where Aalso is one of those instruments.
If one uses Aalso only, there are of course no problems.
today I used Aalto as reference to determine the pitchbend range for my Kenton USB MIDI/CV interface, and it was very difficult, rather impossible to find the right setting.
MIDI keyboard -> Aalto with initial preset (no modulations)
MIDI keyboard -> Scala Relayer -> Kenton -> VCO
It turns out Aalto is slightly off between C# and H when using .scl files, because after a while I used Diva as reference, and could immediately determine the Kenton pitchbend range of 2 semitones. Diva, the VCO, and later FM8, lined up perfectly. When played at the same time there were only slow beatings for a note or two. Aalto was the only one that created heavy beatings, so it is clear to me that Aalto's tuning system is not quite correct.
I used sine waves and the identical .scl file (dorian_schl) for all synths (except FM8 which I tuned by ear). The VCO is a Furtherrr Generator which is a very stable analogue oscillator with perfect scaling over many octaves. So I'm sure I eliminated all possible error sources.
I've used microtunings a lot with Aalto, but this is the first time I discovered this error.
Not a big problem, only a detail. I just thought I'd mention it after discovering. When Virta is released, maybe you'll find some time to replicate this behavior, and have a look what could be the reason. No hurry at all.
today I compared three softsynths, Aalto, Z3TA, and Diva. With 12-tone tunings, Z3TA and Diva correlate (as well as Scala Relayer and analogue VCO). Aalto does not. But I don't think it is some kind of oscillator drift. And I used a patch with one voice (no polyphony). The only logical conclusion is that Aalto does not interpret the tuning file correctly.
However, when I try non-12-tone tunings, all synths spread apart, no correlation except for the one reference note. I have no idea why is that. Tuning synths together is a very difficult task!
setup for Harrison Mixbus:
at last, it's working at my place in Windows! Phew, that was strange. It was indeed the 'old' 1.0.0 version. Strange why it wasn't removed after deinstalling, and why the new version wasn't installed after two installations.
True, also Kaivo has Aalto name and version number. Doesn't matter, it appears these are only tags. I just tried to look everywhere why things didn't work for me, what version the dll's are, etc.
Thanks very much, now I can start to explore Virta on my main workstation.
sorry, but I see no change in 1.0.1. It still doesn't receive audio (except for the 'pre' output).
There's also one more thing, in the dll properties/details it says under File Description: Aalto, and under Product Version: 1.7.
Thank you so much for this quick update, but I'm afraid it doesn't change a thing for Windows users. I would really recommend to build VST effect version, that would solve the problem once and for all.
Edit: hm, apparently it works for others. I deinstalled 1.0.1 and made sure there was no old version anymore, and reinstalled. Still the same.
Edit: the dll date is from March 28. It must be the old version. That's impossible.
the VST3 standard supports multiple channels including sidechain. The VST2 standard not, you're right. But even VST3 does not allow audio input in many hosts if the plugin is an instrument, not an effect.
I'm working in Harrison Mixbus and Cubase, on Windows.
Edit: tried it in Logic, and now I understand. You meant the Logic sidechain.
"in virta dialog, select side chain input"
oh, I missed that one. Well in that case it should work in every DAW. Will try it out tonight.
Edit: hmm, Virta has two inputs, not 3 or 4. So there's no sidechain input.
Virta should be a VST of course. Or two versions, one VST and one VSTi for the synth part only. Then setup in any DAW is without problem.
"Reaper sees Virta as a vsti instead of a vst"
yep, that's the cause. In other words, on Windows it's very unlikely that the current VSTi version of Virta will work. On Mac (AU) it works of course.
Maybe this should be explained a bit how this works in Windows: there are VSTi's with audio input, but to use them as an insert, there must be an extra VST version. Only then it will work as an insert effect. That's why there are two dll's for such instruments.
But there's no hurry. For me at least.
I must admit today was the first time I started to read the Kaivo manual. The illustrations from David Chandler are terrific. And the text is so well written, which makes reading both a pleasure and a learning experience even if one 'knows' about physical modeling and granular sampling, and synthesis in general. Such quality manuals are rare.
While reading there was some Balinese Gamelan music playing on my computer, quite a perfect accompaniment. Starting Kaivo with the 'pan multi bells' patch, hitting or holding some notes from time to time was unsurprisingly a good match to the Gamelan music.
Since I have a faster computer Kaivo will serve me for a long time, and I only wanted to thank you and all others who have contributed in the making of this fantastic instrument.
ah, that's the explanation. One of those famous "it's not a bug, it's a feature" cases. Yes I think it would be good to have a checkbox in the settings to switch oscillator drift off, for those cases when you need precise pitches. Besides, Diva has an extensive set of trimmers, with detune, drift, variance, etc.
for me it would also be good, like others have mentioned, if the module could load customisable microtunings. But I understand if this may be too complicated for the first batch.
There are iPad apps that cost much, but they are dedicated for professional applications. Mostly related to film industry.
Myself I'm happy with my Lemur interface to control Aalto on a computer. Although in future I might buy a more powerful iPad (currently the most powerful iPad I own is 4th generation). In this case a software like Aalto might run well on such an iDevice with enough CPU power.
I think this is something to think about in the future. Maybe in the near future, who knows.
I don't expect noticeable latency. I know some iPad apps of that kind. The only thing one has to remember is that there is only mono-touch, not multi-touch.
[quote]with "OSC parameters directly" I meant the way to go in a future world where I have written that feature. Sorry to disappoint. The feature will be Aalto / Kaivo recognizing parameter changes over OSC directly. I plan to do this in the next version, I can see a lot of uses for it.[/quote]
That is still the case with Aalto 1.7, is that right?
I would like to control Aalto parameters via OSC and Lemur/iPad. I think this is not possible now. But will it become possible?