hardware and software for electronic music 

randy's Recent Posts

Thu, Mar 06, 2014, 08:17

STICKY: Kaivo patch thread

A place for Kaivo patches! Just select copy to clipboard from the patch menu, and paste here to share.

Wed, Nov 22, 2017, 13:08

Some of these patches require certain granulator waveforms from outside Kaivo, maybe that is the problem?

Mon, Nov 20, 2017, 14:54

this works OK for me with the beta and all my factory patches. Do your factory patches sort OK?

In each patch there is a name stored with it that might be different from the name of the file. My guess is that they are being sorted by the internal names. If these get out of sync the sorting would be wrong. In the case of getting the patches from the forum these are likely not matching. I'll fix this somehow in the next version and for now you can change those internal names with a text editor.

Sun, Nov 19, 2017, 09:52

Thank you. Sorting was implemented from the beginning, but for some reason broke in the most recent version. I'm working to get an update out.

Tue, Nov 14, 2017, 14:18

OK. This is similar to a problem another person had on Windows.

I take then, that you're not using sym links to refer to any of the plugins or license directory?

I have not been able to reproduce this on Windows but I'll review the code and see what i can see.

Tue, Nov 14, 2017, 10:51

Thanks for the report.

When you hear the hissing sound, look in the registration area. Do you see you registered name there, or "DEMO"?

Are you using a symbolic link to manage any of your related files? There may be a problem following the link on Windows sometimes. If this is the case, please describe what you are linking to and how.

Tue, Dec 20, 2016, 11:11

Winter sale.

Dear music makers,

In appreciation for your support, it's time for the annual winter sale. Use the code MAYTHEREBEPEACE on any of the product pages to get 25% off any Madrona Labs plugin. From now through Jan 5.

Fri, Nov 03, 2017, 14:21

Soundplane software version 1.5.0 release

I've finished version 1.5.0 of the Soundplane software. This release is recommended for all Soundplane owners. It fixes some possible crashes and has an entirely rewritten touch tracker, almost a year in development. The benefits of this new tracker should be obvious as soon as you play it!

Direct link: Soundplane 1.5.0.zip, 5.9MB

version 1.5 changes:

  • new touch tracker algorithm:
    • consumes much less CPU
    • improved latency
    • improved pressure sensitivity
    • improved pressure uniformity
    • improved position accuracy
    • allows better tracking into corners
    • lengthy normalization step no longer required
    • fixed hanging touches
  • fix Kyma connection
  • improve selection of lowest-noise carrier set
  • fix a possible crash when switching zone presets
  • fixed a window-related crash on shutdown
  • fixed latency issue when in background for an extended time

In case you missed it, you can see me playing a Satie piece using the new software here:

I'm taking on some "real pieces" in addition to improvising, to feel out what changes will make the next model of Soundplane the best instrument we can make it.

The documentation does not reflect many aspects of the new software yet. Please post in the forums or email me anytime if you have questions.

NOTE: to install this version of the software I recommend removing the existing files in ~/Library/Application Support/Madrona Labs/Soundplane. Then running the new version the first time will run the carrier selection and create new defaults.

After the new prefs are made, select "default" from the OSC destinations menu to get OSC flowing again.

Tue, Nov 07, 2017, 11:32

Things have settled down. All the new work is in the "embedded" branch however. I need to merge to master, and also clean up the cmake and build instructions. Since there are not too many modules, it should be fairly simple to pull from the embedded branch and integrate with your own code in the meantime.

I made big changes to support the embedded work, but the work has not been done on the embedded system yet. The driver API is much more C-like now. it doesn't rely on a listener class and should be usable even in a single threaded environment. Let me know if you have any questions...

Mon, Nov 06, 2017, 16:34

Thanks. Sample size is very small, but so far the people having issues are on 10.10.5, and it's working for everyone on 10.12.x.

I am deploying the app for 10.9 and up, so running 10.10 shouldn't be a problem. But maybe it is for some reason. If you think of anything let me know!

Mon, Nov 06, 2017, 12:03

NOTE: two people so far have run into an issue where after trashing the prefs and running, the new version starts to select carrier frequencies, then hangs at 0%.

Please be advised that this bug exists, so you may want to hold off on version 1.5.0 if you can't spare the time to possibly revert. If you do have time to install and try it out, please let me know your results and the OS you are running.

Fri, Feb 13, 2015, 14:32

Call for input: Soundplane to CV module

This year it seems desirable and possible for Madrona Labs to make a Soundplane to CV device. This would be primarily a Eurorack module, but the circuit could also be built into its own enclosure for use with vintage synths etc.

Normally I do most of my design work in private, and only announce a product when it's pretty much done. But we (Brian and I) are going to change it up this time. Because neither of us is that deeply into the Eurorack world, it makes sense to solicit input early on in the process this time. This is going to be a utility device (though hopefully an elegant one) — so before we get too far along, let's make sure it will be useful to you!

The basic idea

USB jack for powering the Soundplane. Module puts out CV / gates / mod outputs for individual touches. Like the Soundplane app, a zone map decides how the Soundplane surface is divided up into notes and what those notes are. You can switch between zone maps, and the name of the current one should be displayed somehow. Aside from this, visual feedback will be at least an LED per Z value. To keep costs low, probably nothing too graphical or fancy.

We're looking for input on things like:

How many voices?

Each voice of touch output will probably have 4 outputs for pitch, x, y and z. Setting up many voices on a modular is not the way most people use them, so I'm guessing that two voices of output will take care of 90% of what people want. We would probably add an expander module for more voices.

Any interesting modes?

A switch that changes z (pressure) into a strict on/off gate might be useful. Any other things like this?

Layout?

individual voice groups vertical or horizontal? voice outputs at bottom or top? I'm thinking top, because a USB jack on the bottom will go to the Soundplane.

Power?

The module will need roughly 250mA at 5v to power the Soundplane. Brian will correct me if I'm wrong. Then there's whatever computing and display the module needs to do, and the outputs. Do we need our own power supply, or a list of compatible Euro power supplies that we can point people to? Any choices in connectivity to make here?

Finally, we're still looking for a great name…

Sat, Jun 23, 2012, 19:49

STICKY: Soundplane Client for Mac

version 1.5.0
November 3, 2017
link: Soundplane 1.5.0.zip, 5.9MB

release notes:

To install this version: move the "Soundplane" application to your Applications folder, then move the directory "ZonePresets" to ~/Music/Madrona Labs/Soundplane.

When you launch the Soundplane application, the menu at the top of the "Zones" page should contain three presets: chromatic, rows in fourths and rows in octaves, followed by a list of all the JSON files in the ZonePresets folder. If the JSON files do not appear, the ZonePresets directory is probably not in the right place.

The format of the zone .json files is human-readable and relatively self-explaining. Take a look to see how to make your own zone maps.

The Soundplane Max/MSP examples require the CNMAT Max externals to run. These can be found at http://cnmat.berkeley.edu/downloads .

The Soundplane application is open-source, available under a permissive license. For source code and more technical information see http://github.com/madronalabs.

changes:

1.5:

  • new touch tracker algorithm:
    • consumes much less CPU
    • improved latency
    • improved pressure sensitivity
    • improved pressure uniformity
    • improved position accuracy
    • allows better tracking into corners
    • lengthy normalization step no longer required
    • fixed hanging touches
  • fix Kyma connection
  • improve selection of lowest-noise carrier set
  • fix a possible crash when switching zone presets
  • fixed a window-related crash on shutdown
  • fixed latency issue when in background for an extended time

1.4:

  • fixed a problem with MIDI output preventing slide between rows
  • tweaked pre-touch filtering for lower noise
  • (dev) new cmake-based build system
  • (dev) experimental Linux build
  • (dev) added HelloSoundplane command line app for low-level testing

1.3:

  • MPE MIDI support. Requires Aalto 1.7 / Kaivo 1.2.
  • Implemented note splits to multiple ports over OSC.
  • Improved stability and sensitivity of MIDI velocity
  • changed "z max" control to more intuitive "z scale."
  • fix crash with uninitialized driver on shutdown
  • allow 1-500Hz MIDI data rate
  • fix bug where pressure wasn't getting set w/o a MIDI connection
  • send quantized pitch bend on MIDI note off
  • fix touch tracker issues including zone-switch bug
  • fix to allow MIDI note 0
  • fix for double note off problem
  • fixes for MIDI glissando

1.2.5:

  • [1.2.5.1] Fixed a crash on startup if no preferences folder was present.
  • Kyma listener off by default to fix collisions on port 3124. Use 'kyma' toggle on Expert page to turn on.
  • fixed automatic connection to selected OSC service on startup.
  • restored some values from 1.1.2 to improve touch tracking.
  • add automatic saving of window dimensions. This is saved in /Application Support/SoundplaneViewState.txt.
  • fixed a problem resolving OSC services
  • fixed wrong MIDI note offsets in default Zone setups

1.2.4:

  • rendering fixes for Retina display
  • make touches easier to get into top and bottom rows
  • code signing application
  • turned Kyma polling over MIDI OFF by default
  • fixed some state issues on startup that required reselecting zone to refresh
  • clamp zone outputs to [0, 1] as documented
  • fix touch rotate bug
  • fix OSC browser
  • made normalizing easier and mre accurate
  • sending out x, y, and z from zones via MIDI.

1.1.2:

  • more complete fix to the note-off problem
  • restored the note lock feature for new zones.
  • fixed an odd font-related bug

1.1:

  • PLEASE NOTE: moved support files to ~/Music/Madrona Labs.
  • fixed a problem where the wrong note value was sent on note-off
  • fixed a potential crash sending MIDI if a MIDI device was not set
  • made benign errors less alarming

1.0a2:

  • two new kinds of zones: z (pressure only) and a toggle switch.
  • fixed an error where inactive touches were continuously sending their data
  • shortened some JSON zone names (just remove "controller_" to fix your presets)
  • updated Max/MSP examples
  • moved matrix message into t3d OSC bundle with touches
  • restored some debug printing in the in-app console
  • added error info for JSON parsing
  • fixed possible bug with zone parsing
  • clarified the T3D format in docs
  • fixed an error reading calibration files
  • fix view issues for Retina display

1.0a1:
-new Zone features allow mapping notes and controllers to key grid
-changed t3d format for wider OSC compatibility
-OpenGL accelerated graphics
-fixed graphics for Retina display
-fixed a bug where SoundplaneController was initialized twice
-fixed OpenGL errors on quit
-fixed a possible crash in adjustPeak()
-fixed note release when quantized
-new raw matrix output

Fri, Nov 03, 2017, 13:16

No offense taken! I get it.

Fri, Nov 03, 2017, 07:46

Hiya,

Thanks for your feedback. I'd like to find a way to make back + forth easier in Ableton as you say. The thing that's a little difficult about drag & drop is that Kaivo only "allows" sounds to be around 8 seconds long. It breaks the normal flow of drag & drop if the whole thing is not used and you need another step to select part of the file after dropping somehow. So I have not really come up with a good way for drag&drop to work.

It could maybe just import the whole thing if under 8 secs, then put up a little dialog "would you like to clip?" otherwise.

The short-file limitation is because files have to be scanned to find all the best grain crossfade points and I don't want that startup to take forever. I believe right now if you just drop a long file into the Kaivo/Samples folder it will import the whole thing.

Fri, Oct 27, 2017, 10:19

Some other folks have reported that enabling "Force MPE" in Bitwig is needed to get my instruments working there. Does that work for you?

Sun, Oct 22, 2017, 10:01

There's not much context in your comment so I'm going to assume that you are in the common situation of using a MIDI keyboard, and don't want every note to start a new attack.

You might find unison mode helpful. I believe that if unison mode is on, and notes are played overlapping one another, the envelope will not retrigger.

Tue, Oct 17, 2017, 08:49

Yes, one wonders how or if they are going to do that! I have not yet tried this but I'm interested to find out if it's "commercial quality" in terms of efficiency, sound quality etc.

Tue, Oct 17, 2017, 08:46

This seems to work. You can always reach me at support@madronalabs.com.

Tue, Oct 17, 2017, 08:46

Thanks for the idea. My initial reaction is, this adds such a great amount of complexity and that's something I am trying to avoid. I wonder if there's a way to make multiple instances of the plugin work better together to achieve what you want.

I'm imagining how this could be done in a future modular environment (as always) with one KEY module and several sub-instances of the plugins. This has the advantage that you can mix Aalto, Kaivo, etc.

Currently in Aalto each voice has its own send to reverb, however they all share the same reverb.

Mon, Oct 16, 2017, 14:19

That's odd, I'll look at it. If you are not using the example patches that ship with the software, can you please zip up your MIDI Programs folder and send it to me so I can reproduce?

Thu, Oct 12, 2017, 15:47

email me at support@madronalabs.com with some kind of documentation of student status and I'll sort out a refund.

Thu, Oct 12, 2017, 10:48

It's still in flux. I'd hate to tell you something and then end up having been wrong. I think we can safely say it will be less wide than it is high. (how many HP is a square anyway?)

Thu, Oct 12, 2017, 10:46

There is a beta out, which you probably saw, you can find in another thread. This should fix the sequencer issue. If you need this fix you can use the beta temporarily. I still have some other issues related to tuning files to solve.

This particular beta period has been longer than usual getting to completion—thanks for your patience.

Wed, Aug 09, 2017, 11:16

Kaivo 1.3.3 beta available

I've fixed a few issues and uploaded a new beta version for intrepid Kaivo users: Kaivo1.3.3b1.

This beta is for Mac OS only. I plan to ship the final Mac version as well as the Windows version next week. I'll also update the other plugins with the relevant fixes then.

changes:

  • bugfix: the sequencer was not retriggering from reset input
  • bugfix: .kbm mappings were not always using all notes
  • bugfix: .kbm mappings were not setting reference note properly
  • fixed a rare condition where the metal string resonator could lock up

If you noticed any changes in how your patches behaved after installing Kaivo 1.3.1, hopefully the sequencer fix will get them back in shape.

Thu, Oct 12, 2017, 10:43

If you are interested in helping out with testing, you can use the beta and give me feedback. If you are more interested in getting music made, use a stable version (in this case, 1.3.2). This beta process has been longer than usual and hopefully will be wrapping up soon.

Tue, Feb 23, 2016, 09:04

Seattle Music Machine Salon

The Seattle Music Machine Salon is a new monthly discussion group, open to all and free of charge. Each month we’ll have a presentation and a guided discussion on some aspect of making music with computers and electronics. Topics will include the practical and the not so practical: new software and hardware tools, compositional strategies, academic and popular styles of electronic music, its history and future.

Our first event is Friday, March 4 from 7 to 9pm at Ada’s Technical Books in Capitol Hill. Ada’s offers a comfortable, inspirational atmosphere, and great food and coffee. They are at 425 15th Ave East. Please visit their site at http://www.seattletechnicalbooks.com/ for more info and directions.

Everyone is welcome! This includes all ages and skill levels. The aim is to create a diverse group that will expand viewpoints and spark new projects. The only requirements are an interest in the topic and the ability to engage in respectful discussion.

March 4 presentation:
Randy Jones of Madrona Labs will demonstrate his new software instrument Virta, a patchable, sound-controlled synthesizer and effects toolbox.

March 4 discussion topic:
Seattle electronic music resources. What are some important foundations of the local scene for you? What are some less visible resources that should be better known?

Wed, Oct 11, 2017, 12:14

Yes, we do one most months. A couple of times this summer we cancelled because it seemed like everyone would be out of town. There's a website: http://seattlemusicmachines.org/ and a mailing list you can sign up to from the menu on it.

Thu, Jan 03, 2013, 12:40

Better workflow for Aalto

I was making a little music with Aalto over the holidays. I was trying to set up a flow where I could just tweak the knobs while recording audio out of Aalto, and record a lot of tracks that I would just mix together to get the finished piece. But, as you may have found, this is easier said than done! I have ideas on how to make things better.

Tweaking while recording


One problem is that the main DAWs don't let you record audio while tweaking knobs of a synth or effect. Logic has a real time bounce, for example, but locks out control changes while it's going on. Live won't record audio out of a synth unless you are in render mode.


One workaround is to use Numerology from Five12. It's great for on-the-fly sequencing and tweaking, and will let you record audio while you do this. It's a little less than ideal in that the audio is all sent to automatically-named files that you have to sort out later. But in even allowing recording while tweaking it offers a cool feature that the big DAWs don't. The drawback for me is that it's not the environment I want to mix in.


I checked out Reaper and did not get far enough to decide whether this would be a good solution for live recording. I could deal with learning to mix in it if it offered this capability. Anyone tried this in Reaper?


Finally, one solution might be a simple record button in Aalto. But I try to avoid adding things that the DAW should be doing well. Anyone up for writing a DAW this year with Live’s ease-of-use and timing, Logic’s MIDI implementation and Reaper’s efficiency?

Resetting


Another problem with the flow as it stands is resetting Aalto back to a patch at the start of a loop or arrangement. I'd like to set up one patch, do a take of knob-tweaking, and then automatically have Aalto recall a previous patch or saved state back at the beginning to set up the same jumping-off point for exploration. This is a little difficult now.


One way to do it, currently, is using MIDI program automation. Aalto 1.3 added the ability (underdocumented, currently) to switch programs via MIDI program change messages. See here for details. So, you can make a patch, save it to the "MIDI Programs" directory, and record a program change message in your DAW of choice. This is fairly easy in Logic, and in Live looks clunky but possible. There's an extra step of saving a patch, though, every time you want to define a new starting point. Not ideal. Maybe I don't care about the patch in general but just as an element in one song.


Resetting the patch is also needed to make the flow sort-of-good in programs like Live and Logic that don't allow control changes. An offline bounce (much faster than real time) after each tweaking pass may not be a bad price to pay for recording in my environment of choice, and so I can simply record the parameter change data---but the reset is also essential here.


There are a few ideas I have for a solution. One is to add a menu choice "broadcast all parameters." This would do what it says, allowing parameter automation systems to capture the entire state of the plugin. I think that with more than 100 parameters, though, this might overwhelm the capabilities of the DAW, and would certainly make a mess of the param menus.


A refinement of that idea is to have two menu options, one to say "start keeping track of what parameters I changed," and another to reset only those changed parameters. This would definitely work, the only drawback is a little added complexity. You would still need to be careful to save your song with all the params at their initial states!


I'm happy that Aalto 1.3.1 is very solid after the 1.3 shakeup, and I'm looking forward to working on some of these workflow details now. I welcome your suggestions!

Sat, Sep 30, 2017, 10:59

I've had many requests for this. It will happen.