randy's Recent Posts
*** updated with latest Mac and Windows links ***
I've just posted a public beta of Vutu for MacOS (edit: and now for WIndows!). Vutu is the sound analysis program for the upcoming Sumu synthesizer.
links:
Mac: http://madronalabs.com/media/vutu/Vutu%200.9.9.dmg
Windows: http://madronalabs.com/media/vutu/VutuWin0.9.10.zip
A Vutu quickstart video is also online now. I haven't had a chance to write any better documentation yet, and I"m not sure I will before I get the Sumu beta out. However, Vutu in its current form is pretty simple anyway, and most of what you need to know you can find out by fooling around with the dials and listening and looking.
Vutu analyzes sounds using Loris, developed by Kelly Fitz and Lippold Haken at the CERL Sound Group. A detailed intro to Loris is available on Hakenaudio.com: Current Research in Real-time Sound Morphing More publications are also linked from the CERL Sound Group Loris page. Loris is distributed under the GNU General Public License (GPL) and thus, Vutu is also. Vutu's source is available on Github.
Vutu is built on a cross-platform GUI framework I developed called mlvg. Compiling it for Windows and Linux should therefore be a reasonably easy task, but I know there will be a bunch of details to iron out, so I'm not taking that on until after I can make a Sumu beta.
That was a lot of info and links. Why would you want to play with Vutu right now? Some reasons might be:
- You want to get started making your own sound bank for Sumu.
- You have to try out the newest audio software, whatever it is, and this was just released today.
- You enjoy looking at bandwidth-enhanced partials and hearing odd noises.
Each voice of Sumu will be able to play back 64 bandwidth-enhanced partials simultaneously. A bandwidth-enhanced partial is basically a single sine wave, modulated with noise. So at any given instant of time, in addition to frequency, amplitude and phase, it also has a bandwidth, or noisiness. Making sounds out of such partials is a very powerful technique, and I think it's pretty easy to grasp. What's been difficult about additive synthesis is the large amount of control data that's needed. How do you generate it all? My answer in Sumu is to use the familiar patchable interface, but extended so that each patch cord carries separate signals for each partial. This allows sound design in a playful, exploratory way that should be familiar to any modular user. Honestly I think it will be fun as hell.
Thanks to Kelly Fitz and Lippold Haken for creating and sharing Loris. Thanks also to Greg Wuller for helping me get going with the Loris source code, and for utu, which became Vutu. Utu is a Finnish word for "mist" or "fog", like Sumu. Vutu is short for visual utu.
Vutu requirements
A Metal-capable Mac running MacOS 10.14 (Mojave) or greater.
Vutu is native for Intel and Apple Silicon.
Since it's an analyzer and not a real-time program (except for playing the results), CPU doesn't really matter.
Thanks for sharing! With a patch that uses the filter, you should see more of a difference.
Hi @marsdietz thanks for your kind note. I hear your compelling use case for an iOS version. I'm not working on iOS versions just yet, but I'm working on things that we would need to get in place before that effort. in other words you'll see Aalto 2.0 before too long, and shortly after that it could be possible to have an iOS version. I'll probably telegraph my intent before that and solicit some beta testing. Please stay tuned!
Happy Solstice, and here's to change and evolution. This goes out with all my best wishes to everyone for health, peace and prosperity in what has been such a hard year for so many. I hope that, despite COVID, you are finding ways to keep sane and happy, to nurture your body and spirit. A few weeks ago I got away on a short trip to meet some friends at the Pacific Bonsai Museum. That's where the lovely grouping of golden larch trees on the sale image here comes from. Visiting was a meditative, inspiring and world-expanding trip for me and if you're in the Seattle area, I recommend it highly.
From now through January 6 2021, our year-end sale is happening! You can use the code EVOLVE to get 30% off all our software. If you're an Aalto fan but you've been holding out on getting Kaivo or Virta or Aaltoverb, now's a great time. And yes, our simple bundle deal is in effect along with the year-end discount, if you choose to take advantage of them both. This results in some big discounts!
Finally, if you're looking for a last-minute gift, you should know that it's easy to give a Madrona Labs software license! A gift license can even be part of a simple bundle with one you bought for yourself and I'll be happy to transfer it free of charge (and judgement). Just email me at support@madronalabs.com to let me know. I'm taking Dec 25, Dec 31, and Jan 1 away from the computer but otherwise I'll be available within 24 hours (and probably less) to help make your holiday dreams come true.
Yep, we're about to have our end of year sale in a couple of days!
There's no further discount on the Studio Bundle however. We cap discounts at 30% to keep things sane and that's what the bundle offers any time.
I'm working to grow the company to where we can make a Soundplane Model B and support it well. it's been a long journey! Thanks for your continued interest.
I'm starting Team Notes as a place for me and other folks on Team Madrona Labs to post more casual things for a smaller audience. If you're seeing this, I guess you're that audience. Welcome!
Typical posts might be special interests within our special interest: technical details about making the software, or about making the coffee, what we're listening to, rants on technology and how it's making everything better or making everything worse, recipes... you get the idea. If there's anything you've always wanted to know, please reply here with your ideas!
This orange clipboard has my notes from the current Sumu optimization. I'm figuring out how to run four of the Moog filters in parallel in around the time it previously took to run one, and thinking about how to generalize this solution in an elegant way. I still do big abstract thinking much better when I'm using actual pen and paper.
Making code faster with SIMD (Single Instruction, Multiple Data) processing is something I've enjoyed doing since Motorola first released their Altivec-enabled PowerPC processors. From Altivec to SSE and AVX and ARM NEON, the SIMD concept has remained largely the same across processor generations for the last 25 years. Compilers have gotten better at optimizing C++ code for SIMD, but to get the fastest results, the right algorithms and data structures have to be picked to kind of make the CPU happy, which is much higher-level thinking. And zooming out even further there are more human-centered tradeoffs to think of: what kind of code reduces the potential for bugs, what is redadable and maintainable, what will be easy to learn for new people coming aboard the project? Are we optimizing for just the latest Apple machines, or do we want this stuff to be runnable on a ten year old ThinkPad? The questions may start out purely technical, but very soon the answers start to reflect an organization's values.
Sumu makes heavy use of SIMD already in its oscillator banks. But the 4x filter object is one that had to wait until after the initial release. Between this and other optimizations, Sumu 1.2 will use around 30% less CPU than 1.1.3. And there's more optimizing to come. My goal is to run it on this ten year old ThinkPad over here!
@rjschrei sorry to hear about your gear.
Thanks everyone! Sooooo much moss wants to grow on our roof here in the Pacific Northwest. I think I'm going to hire a professional.
Thanks for the additional info. If you can email me at support@madronalabs.com and send a crash log, it will help me figure this out.
Hey @intervolver I hear you are pretty frustrated with the sample import process, even without the crash. Obviously, you're not alone. I have plans to make it better.
As far as the crash, please contact me at support@madronalabs.com. I'm not getting any crashes with importing here, so maybe it's the specific files you are importing that can cause it. I'd like to get a hold of them and try to reproduce the problem.
Maybe it's overwriting the created .sumu files that is causing the crash? When you describe reimporting on your edit, one difference is that the files already exist. If you try deleting all the .sumu files in the folder you're writing to and importing again, you could test this. I'll do so as well.
Looks tasty!
These are already imported into .sumu format! So, you do the following:
- go to our Google drive
- click the "..." to download the whole theory folder
- put the theory folder in .../Madrona Labs/Sumu/Partials with all the other partials.
The "import partials" converts utu files into .sumu format. You do not need to do that here.
We have had MPE support since version 1.1.0.
With the Sumu 1.1 release out, VST3 versions of Aalto, Kaivo and Virta are the top priority now. We're working hard on them.
Hi, sorry your post got buried—feel free to hit me up via support @ madronalabs any time.
I appreciate the feedback. I know importing partials is super clunky. Part of this is for legal reasons: the Loris software that I use to do the analysis is under a GPL license and would require that my entire synthesizer be open source, if I were to incorporate it. I have plans to address this in the future and make the workflow much better.
You mention some Vutu things I can definitely improve. The '90s are hip again but I can definitely do better on some workflow things.
At some point I plan to add parameter locks which would take care of the voices issue.
People have different ideas about which way is "correct" for scrolling. There's a setting in the main "..." -> GUI -> normal / reverse.
I hope you are enjoying the sounds, please stay tuned and I will work to improve other things about the software.
Wow, this is a weird one. Please keep us posted on whather the 3D driver fix is helpful!
Happy October! I've just uploaded an update to Sumu, version 1.1.3.
This update brings fixes to two main issues with version 1.1.0. On Mac OS, a crash in AU validation was affecting users with Intel-based computers. This has been fixed. On Windows, an expired code signing certificate was causing difficulties in downloading. This is also fixed.
Along the way I discovered a few additional problems. Here's a full list of the changes since 1.1.0:
- fix AU validation crash on Intel processors
- add Azure code signing for Windows DLL and installer
- fix JSON-related bugs in partials import
- fix rare crash in space display rendering
- fix running on MacOS 10.13 and higher
- optimize JSON parsing for very long files
- fix FM mod index bug
Because of the bug fixes, I recommend this free update to every Sumu user. Installers are over here!
Hi @lumena, sorry it's giving you trouble, can you identify a particular .utu file you are importing that is causing the issue? Does it ever succeed? Please follow up with me by email at support @ madronalabs.com if you would like to send a file.
Maybe not too distant!
Now that Sumu is out with MPE, I'm working to make VST3 updates of the other synths with a fix to the keyboard problem and a couple of other long-standing bugs, ASAP.
Glad to hear!
The Sumu 1.1 update is out, bringing MPE support as well as a bunch of bug fixes and enhancements. These include:
- gui: fix scrolling after setting default in popup dials
- gui: fix missing update bug when pasting registration
- osc: fix zipper noise in AM mod index
- AU wrapper: fix Obj-C namespace collisions
- fix UI scale bug with muliple displays of different scales
- allow slower LFO times
- increase LFO popup dials precision
- adjust text position for negative numbers in Dials
- increase pulses ratio dial precision
- fix slow LFO sync
- improve host clock sync
- reset pulses hi scale offsets when adjusting past zero
- fixed issue loading state saved by beta version
- added MIDI learn for dials via popup menu
- added main […] menu with gui and input settings
- gui : added numbers on / off menu
- gui : added scroll normal / reverse menu
- input: added protocol [MIDI / MPE] menu
- input: added MPE bend range [ 0 / 12 / 24 / 48 / 96 ] menu
- input: reduced latency of gate and pitch in patcher
- input: added MPE mode
- input: don't reset voice time in unison mode legato
- partials: add interpolation to time dial
NOTE: we are still working on meeting the latest requirements for Windows code signing. Windows will claim that the Sumu installer may be dangerous and you will need to click "Keep anyway" a few times. We'll update the installer as soon as we can address this.
Hi Peter, the way to do it is to use Sumu to import the .utu files. There's info in the manual and I've just made a new Quickstart from some info on the forums:
I hope this helps, if you have any questions please email me at support.
best,
Randy
Wow, that's interesting. I guess the other profile is for Direct3D?
Of course it's still not ideal if there's a setting you have to change to use Sumu but I'm glad you have a workaround.
received thanks!
Thanks. I have a Windows 11 machine here. Do you have a utility you are using to track GPU memory usage? I'm happy to research this but using the same one will help me reproduce what you are seeing.
Hi and thanks for the report. This is not familiar to me. I can check into it. What operating system are you using please?
Hi, sorry for the delay, I had one last long weekend adventure this summer.
It could be that your import is actually successful. The message "partials file not found" should show up in the partials module only when the patch itself is referring to a partials file that it can't find. Are you trying to load a patch you've downloaded and the partials to go with it?
After loading the folder "Vutu" that you made, what you should expect to see is the one partials map (utu) in the top level of the menu in the partials module. If you look in the Madrona Labs/Sumu/Partials diretory, you should see that one file in there converted to a .sumu file. Once you choose it from the partials chooser the "partials file not found" message shbould go away.
@cupcake thanks for the info! And sorry for the confusion. I'll look at the installer and try to remedy this.
Yes, it's currently unsigned as we complete the verification process for code signing. Meanwhile thanks for your patience.
