randy's Recent Posts
Yes I don't have the rights to reproduce the Synmag article. I don't really feel a need to anyway, because most of my customers can't read it. I'll write more info here in English soon—but mostly I'm working on finishing the synthesizer!
I'm glad you are interested! I don't have much I can say about it yet.
I'll be releasing a free program alongside Sumu, which does the analysis of audio recordings and turns them into the bandwidth-enhanced partials format.
Thanks for the thoughts! So non-German readers aren't left behind I'll be posting more Sumu info very soon.
Thanks for the feedback.
That's it, sorry for the late reply here!
It's a fine question! My synths work with pretty easily alternate tunings but not with MTS-ESP for now. I may add it in the future.
Cool! I had a beer and watched you play with my synths, it was fun.
I'm working to finish up that Aaltoverb release. The M1 code is done. I plan to release Aalto 2 early next year.
Sorry that didn't help. I can find the info for you, if you let me know what plugin or what particular info you were interested in.
All the existing plugins will definitely be getting major updates in the coming year. I'm excited to be rolling out a new graphics layer that will make things generally faster, better multi-core support, native Apple Silicon support and lots of other improvements. These will be v2 versions and will be paid upgrades.
At one point I did promise at least some new models for Kaivo for free so I'll sneak some into another 1.x update before I send out v2.
Thanks for the note!
Thanks for the info. I'm working on an update that will fix this.
It's cool—I'm a bit embarrassed it's taken so long! I really don't know about a timetable—as you say, I'm just trying to get Sumu out—but I can commit to doing at least another couple of resonators or bodies for Kaivo soon after Sumu ships.
Thanks for the good report and the additional info. If it does it outside of MPE mode, that will make it easier for me to track down. I've made a bug report.
I don't test much in Reaper, so I wonder if this is an initialization problem in Virta that is triggered by Reaper. If you have a chance to try a different DAW, please let me know if you see the issue there. Thanks again.
that's great to hear, thanks for sharing this info!
shipping this fall.
@thetechnobear thank you for posting the info!
I'm not an expert with Ableton and I have to look this up every time. So maybe someone else can explain better. If I remember right, sending the output of the synth track to another audio track, then recording that track, is the simplest way.
Hi, I guess when the Soundplane app was made I never considered much the idea that there would be hardware synths with MPE. While I can't be of much help immediately, I'll add an MPE MIDI out mode to the Soundplane app feature list.
Do you have Max/MSP? That's probably what I would use to make something that does what you want.
I appreciate your thoughts on smoothing. The code in this case does not help because it's not something I can just drop into my own framework. Finding the time is the hard part. I'll be making a big list of Aalto enhancements soon and this should be near the top.
Thanks for the thoughts @pdt.
@aleatoire, I played the WAV sample you sent me and on the long decay there is only DC, in other words, a constant value that slowly decays. This is at under -50dB, so I don't see it as a major problem. But I wonder if something in your audio chain does not like the DC and is converting it into high frequencies somehow, with the distortion you are describing. From the sound you sent me that is my only guess.
In any case this explains why the "leak" setting removed the problem. It removes DC.
I appreciate the reminder. I'm not sure how I missed this the first time around, so sorry about that!
It's an easy fix if some params want to be smoothed and others don't. But in the case of the waveguide frequency some people might want this to be smoothed and others might not. A user-configurable smoothing frequency for each parameter would be too complicated, I think.
I could see an approach of smoothing changes, unless the parameter has not been changed for a short while. So if you start modulating gradually away from 0, the first change won't be a jump anyway and it will still sound smooth. But if the first modulation is a high value, it would immediately jump to that value, then begin smooth changes if values kept flowing in, as from poly aftertouch and so on.
Woo! I know, I was thinking I should mark the occasion somehow but I'm so busy trying to finish software... ha.
I guess it's my right to have a ten-year anniversary any time I want. So maybe in the near future.
It's about time for Aalto 2. I should probably have a paid upgrade more than once a decade!
Hey, nice to see you here—thanks for the update!
I really like that cyborg shoegazey piece and would love to hear it longer.
I thought also that you were just experiencing the normal operation of Kaivo's resonator. But this sounds like something different. I'll try to reproduce this with your patch. Aléatoire, please feel free to send me a wav file of the artifacts to support at madronalabs.com.
FYI I've added NEON support to madronalib now using sse2neon and everything runs as expected. I've merged this into the master branch. Updates of the plugins, starting with Aaltoverb, will be coming soon.
When Aalto gets a program change N message it's supposed to select the Nth program in the "MIDI Programs" directory and switch to it. Max doesn't look for or know about these files at all.
Oh there should be some unique controls all right. Excited to share more concrete info this summer.
Aalto responds to the MIDI program change message, not the VST concept of effect programs. It's the "midievent" stuff you were trying to do originally that should work. There's no setting to disable it.
I just pulled up Live to verify that the program change message is working in Aalto and it is.
I'm sorry I don't have more time to dive into making a Max patch right now. I'm sure someone at the Max forum could help.