randy's Recent Posts

OK, I get it now. I did not know if you meant versions of patches, or of the plugin. Updating to Aalto 1.8.3 should fix this. It's a free update.

Sorry, can you explain in more detail? I don't understand what you mean.

When the problem happens,

  • what operation did you do immediately before the problem?
  • what did you expect to happen next?
  • what happened instead?

Of course having any sort of sound engine begs the question of why aren't there more sounds! I think just a few really solid ones might be a sweet spot though. Like some old analog synths that had 8 presets or whatever.

You can email me at support @ madronalabs.com if you like.

If you start from the default patch, which has no patch cords going into the sequencer, and just set the int/host toggle to host, you'll have a simple patch that should track the clock repeatably.

The Model B will be more refined but not have an internal sound engine. Maybe down the road!

That's weird. Are you possibly modulating the start point of the sequencer somehow in the patch? Because otherwise it should be totally repeatable.

What happens if you start from 0.0.0.0 every time? Does anything change?

Aalto's sequencer will start on the first note whenever the host clock starts. It synchronizes to the nearest beat (1/4 note.) So if you want it to stay in sync with your track you will have to start playback on the one, in general.

This is by design—it's a simple tool more like a modular looping sequencer than a score-based one.

Thank you for taking the time to make this clear example. This certainly seems to be a bug with the MPE handling. I'm currently working on this very system and hopefully I'll have a fix to try soon.

What kind of controller are you using? I'm just curious.

There have been some issues with Windows from time to time but hardly ever on a Mac. So I don't have too many ideas. Are you running any anti-virus software? You could try turning it off. Also, possibly the installer was corrupted so just downloading it again may work.

I would just use the default location on your startup drive and see if you can get that to work. With an external drive, permissions issues come to mind, but I can't think of why it would install 10 presets and then stop. Unless the drive is full.

Yes, there are around 150.

You could try reinstalling. What OS are you on?

Happy summer from the PNW, USA, where things are not bad, considering. I've just wrapped up some infrastructure work fixing some long-standing issues and resulting in an update to all the plugins that's available now for both MacOS and Windows.

The change list for Aalto looks like this:

  • added handling of "all notes off" and "all sound off" MIDI messages
  • fixed bugs with Scala .scl and .kbm handling
  • fixed issue with step sequencer not quantizing to current scale
  • fixed issue with step sequencer UI not reaching maximum when dragging
  • added slower LFO minimum speed and finer adjust (0.0001 Hz)
  • added response to "canDo" MPE query in VST plugin
  • increased glide time to reduce zipper noise for panel parameters
  • fixed possible DSP freeze with extreme LFO feedback
  • fixed sometimes missing t3d light
  • fixed sometimes missing label backgrounds

Kaivo and Virta have some additional changes to fix audio glitches when certain parameters were changed. See those "read_me_first" files for details.

Since so many parts of the plugins are handled by the same underlying code, I've tweaked the version numbering a bit to reflect this. All the plugins are now at version 1.8.3, which looks like a big step for Kaivo and Virta (from 1.3).

Hmm, I have always put out the beta call through the newsletter, which is mostly customers, so I never thought about whether it will be closed in that sense. I guess if you have an account you're good.

I haven't released any samples.

I haven't updated the instructions for Audacity for a while but they are at the end of the readme for Kaivo: https://madronalabs.com/media/kaivo/_read_me_first.txt If they don't seem to work anymore, please let me know.

I'll send out a Sumu beta testing invite soon, hopefully!

Thanks for your support and ideas! Enjoy the instruments.

I'll try to do some good general tutorial stuff on additive synthesis in the manual. I don't actually know any of the synths you mention because I kind of stay in my own little world when I'm designing. But I look forward to checking some out and hearing people's comparisons later on.

@nichttuntun, you can import any WAV format file. For making 4-channel WAVs I use Audacity. You can convince most DAWs to make this format. I would love to make this easier but I didn't want to spend the time writing my own audio editor. Maybe in the future.

@thetechnobear I did make sure the Soundplane repo is up-to-date. I haven't been able to test the libusb support. Please let me know how it goes!

I want to do it!

@hougaard, I'm not sure what problem you mean. Same as @spotta? The account looks OK. Please email me at support for faster response.

Thanks for the note. I'll be doing some work on MPE compatibility in the future and have added this item to the list.

@ian_craig thanks for the good words! That was a simple request from a user and in no way messes up the design, so... done!

@nichttuntun That wavetable granulator is what I'm pointing to with the 2D granulator in Kaivo. Have you tried making your own 2D waveforms yet? Of course, it only does 4 channels. More a limitation of the interface than anything else.

I've done yet more work on the Soundplane code. In addition to fixing an intermittent error that a few people ran into since version 1.5, this 1.7 release adds new Mac system code to get the lowest possible latency.

link: Soundplane 1.7.0 beta 1 dmg

changes:

  • allow running app hidden / in background without added latency
  • fix redundant calibrate on startup
  • fix a stuck notes issue
  • add quick recovery after unplug / replug instrument

OSC has been tested here fully, MIDI less well. Please give it a whirl and let me know about any issues.

Full Kyma functionality may or may not be restored with this release. Unfortunately, I can't test that here. I'll try to get some quality time with a recent Kyma in the near future.

NOTE: the 1.7.0 release is final and available from the "STICKY: Soundplane client for Mac" thread.

Note that the docs are not up to date. In short, you can use a .kbm by naming it the same as the .scl you want it to go with (except the extension), and putting it in the same directory. There's a forum thread or two here that should provide more background. Please contact me here or at the support email if you have any questions.

thanks!

Absolutely. Sorry for the confusion.

Make sure you have Live 10.0.3. The 10.0.2 release is known to be buggy. See a rant thread here: https://www.kvraudio.com/forum/viewtopic.php?p=7093149

You can also try the VST plugins if you are using the AU ones currently.

If you are still finding problems please let me know more specifics. Which patches are not working? If it's a factory one you can tell me or if only your own just copy as text and paste it here.

Yes, sorry this thread is very old!

Since years everything is in ~/Music/Madrona Labs so that people are not confused about which Library folder, or hidden library folders. Feel free to email me at support@madronalabs with any questions.

I'm putting out an update of each plugin soon for stability / compatibility. Meanwhile I'll be releasing a few betas first for Mac and later for Windows.

http://madronalabs.com/media/aalto/Aalto1.8.3b5.pkg

version 1.8.3 changes:

  • added handling of "all notes off" and "all sound off" MIDI messages
  • fixed bugs with Scala .scl and .kbm handling
  • fixed issue with step sequencer not quantizing to current scale
  • fixed issue with step sequencer UI not reaching maximum when dragging
  • more to come...

There is a known issue with AU plugins in Live 10.0.2. Does the VST plugin work better?

I'm still fighting another bug longer than expected, so here's a DLL to try for Windows: http://madronalabs.com/media/temp/Aalto_x64-1.8.3.zip

It's just a raw DLL so place it into your VSTPlugins folder directly. It's only the 64-bit version with the tuning fix and other fixes.

The crashing bug preventing release currently affects only the 32-bit version. As soon as that's sorted I can make installers and release all the plugins.