hardware and software for electronic music 

randy's Recent Posts

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.

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…

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.

Thu, Dec 02, 2010, 09:35

STICKY: Aalto Patch Thread!

I'm going to make this thread sticky. It should be a good place to find and share Aalto patches. I'll try to post one every day or two for a while.

It would be cool if we could embed Soundcloud links here, but setting that up will take some time.

Thu, Sep 28, 2017, 10:05

Cool, thanks for sharing!

Tue, Sep 26, 2017, 08:37

I can't think of any reasons why that wouldn't work. Keep me posted!

Tue, Sep 19, 2017, 09:26

I can also look at making the behavior more predictable when changing the number of voices. That is not something I ever thought about using as a kind of performance control, so I didn't test it in that use. But it seems useful, so I'll put it on the list.

The beta that's currently out for Mac should have a fix for the sequencer retrig issue.

Mon, Sep 18, 2017, 11:09

I think I did by email.

Mon, Sep 18, 2017, 11:09

Any modern Mac should work. Personally I buy refurbished ones from Apple's online store usually.

Mon, Sep 18, 2017, 11:08

You could use the "vox" output of the key module to send a different x offset of the granulator position to each voice. This should be more predictable than trying to change the number of voices on the fly.

Mon, Sep 18, 2017, 10:53

I'm working on software currently alongside plugin work. The Soundplane touch detector has to be rewritten in order to work on our embedded boards.

Mon, Sep 11, 2017, 13:47

I searched the forum and found a potential solution: try turning on "Force MPE" in Bitwig.

Mon, Sep 11, 2017, 11:06

I know people are using Aalto in MPE mode with Linnstrument. I'm not sure if this works in Bitwig, but it should. It should work in demo mode also. Did you change the protocol to MIDI MPE in the settings (gear) menu? Aside from that, there is nothing else to do in Aalto.

Possibly, check your DAW channel settings in Bitwig.

Mon, Sep 11, 2017, 11:04

I'm finishing up this bugfix release currently. Please stay tuned!

Wed, Aug 30, 2017, 10:27

You bring up an area where Virta can really be improved. I appreciate the feedback. With the current system you "can do anything" by choosing or making the right Scala files... but it's not easy to just pick, say, G dorian as you say.

I'm currently working on the code that reads Scala files to fix some bugs and make it more flexible. Then building on that foundation I can add some built-in mappings that will make it easier to select a given scale or mode without making a new file.

Wed, Aug 30, 2017, 10:20

the bend dial in the KEY module controls how much MIDI pitch bend will affect the pitch. Then, you can see the changing pitch signal in any dials you have it routed to, probably the complex oscillator pitch, for example.

Thanks for the nice feedback!

Mon, Aug 28, 2017, 08:44

Thanks for the add'l info. I still have it on my list to check out Virta at 96k more deeply.

Mon, Aug 28, 2017, 08:43

Hi Richard, Aalto will play at A=440Hz by default. There's no master tune setting either (for now), so it's safe to say the issue is not within Aalto. I'd look to your DAW settings or MIDI controller or... ?