randy's Recent Posts
The velocity of each note is also sent to the ENV1 and ENV2 modules. A MIDI velocity of 0 will turn off the note in progress via ENV1 and ENV2 as you would expect.
The vel signal from the KEY module is used to add modulation to notes, not turn them on and off. It stays on after a note is off. Say you want to modulate a filter cutoff via velocity, and your note rings out after is it released. Here the modulating signal must retain the velocity value after the release, or the filter will turn down when the note goes off, too.
I gather you are using the arpeggiator on board the Linnstrument. I can't test that here but I have some suggestions.
The arpeggiator is sending MIDI notes, these are triggering envelopes and flowing through the patcher in Aalto. The Linnstrument is also sending aftertouch messages, that get sent through the patcher. In general you can only use one of these ways of triggering notes. If you turn an Aalto voice on with aftertouch, and then turn it off with a note-off message, you will get an unexpected end to the note.
Maybe Linnstrument has a way of using pressure to control the note-on veolcity of the arpeggiator? This way you would be just using MIDI notes and everything would be consistent.
@spunkytoofers thanks for tidying up, I'll reply over there.
Thanks for the feedback. I hope to fix this for the update coming soon.
I don't understand what arpeggiator you mean either. In general, you have to pick either notes or aftertouch to control envelopes, not both. if the arpeggiator is sending notes and the Linnstrument is sending aftertouch, then the two things might conflict.
I made this thread to explain how to report bugs. not to report bugs in. It will help keep the site organized better if you start a new topic with your problem instead. Thanks!
Good morning Soundplane players, the Soundplane software version 1.3 is out now, with a lot of improvements for you:
- 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
As always, you can get it from the hardware forums, or from this link:
[Soundplane1.3.zip]
This is not possible currently. I had planned not to allow zones to overlap, because of the many complications this presents. But if you want this I can think of a way to accommodate it.
I guess the easiest way is for a single zone to have an optional second destination. Then a lot more UI and so forth will not be needed.
Of course, one can imagine other layers, overlapping zones and so on, but this quickly gets nontrivial to implement, especially when a zone editing UI is added.
I guess you said you are a Max/MSP user so hopefully this takes care of your performance needs, for the moment.
You can do that by changing the values in the .kbm file above.
I will happily give you a 1.6.1. Please give me until next week to take care of this. There seems to be some problem with the watermarking I need to figure out.
in Live,the Kaivo synth dissappears but it leaves an empty white Gui box on the screen
This is a problem some people encountered in the pervious version of Aalto. The next Kaivo update coming soon should fix it. Sorry for the inconvenience.
As reported it happens only in the 32-bit version. So if you want to use the 64-bit version instead that's a good workaround meanwhile.
No, no VST version. I will bring back Aaltoverb properly at some point.
I wrote a post about this topic with a lot of suggestions:
http://madronalabs.com/topics/3565-getting-the-most-out-of-kaivo
Also if this is a Xeon system you may be running into the multithreading issues I mention above. Please stay tuned for the next update coming soon.
No problem, I added it to your account.
I mistyped the address. :-)
Soon. Overall it looks a lot like Aalto and Kaivo.
Well, audio input and frequency analysis of said audio, and of course an envelope follower, will be available in the patcher. So you can make audio-controlled synths or effects with it. You could even patch up something like a de-esser. But it's definitely more a creative tool than for utility effects.
Visually, it will be a lot like Aalto and Kaivo because I think that's a good interface to stay with for now.
More soon!
All versions of all software come with free upgrades until the next major version (2.0 Aalto will be next). The major version will be a small purchase. I've been updating Aalto for five years and I'm still on 1.x, it's all been free upgrades.
I hear you.
the 1.3.1 fix doesn't work with kyma
re: Kyma, can you give me any more detailed report of the problem? What step exactly do you notice something went wrong?
If you look in the Soundplane app console, is there any information? Any error messages?
Is the kyma switch in Expert page on? If so, try turning it off and on, then look for any error messages.
I can make a debug version to display more info. Please contact me by email at support@madronalabs so I can keep track of the conversation better.
That was my guess... voices canceling each other. Thanks for the followup.
Aalto 2.0 will be after the new plugin, not soon. Please stay tuned for beta calls etc...
@zgoheen I know exactly what you are talking about. It's a basic problem with the way OSC / t3d voices are allocated and I didn't realize it until the zone split thing was done and I really had to move on and ship something. OSC voices have always been set up kind of like independent channels of CV / gate / etc that are always on. This model works for one Soundplane->Aalto connection but not for splits. To fix it I have to write a voice allocator for OSC like there is for MIDI. This won't be too hard so you can look for it soon.
I'll check into this, thanks.
seems reasonable! I plan to rework the sequencer for Aalto 2.0 so it could happen then.
Hey, I hope it was a simple matter of resetting the port # so I just distributed a fix.
[Soundplane1.3.1.zip]
The problem is I picked a UDP port for the incoming Kyma information that duplicates the default port with offset = 1 (3124). So if you have a Kyma connection that port will be busy and offset 1 will not for for Soundplane->Aalto connection. I can change the default in the next Aalto version, or maybe ask Symbolic to change the Kyma default port.
What would you want to control via OSC? I feel like maybe I asked you this so if you can point me to an answer that would be great. I'll make sure it makes it into the new feature requests list on github.
I think I know what the problem is. Sorry to have overlooked this, but Kyma isn't part of my testing here because I don't have one. I needed to change a port number because of a conflict. I'll figure out a fix.
If you look at the new split example zone maps they show different zones being sent to different OSC ports. So you could have Aalto listening on one port and Kyma on another one, yes.
ah crap. why OSX 10.7?
I know, I hear you, but I had to do this sometime in order to update my development tools. Apple only supports the C++11 language as far back as 10.7. I wish very much they had made it accessible on 10.6.8 because that was indeed a good solid operating system.
Meanwhile, Aalto 1.6.1 is very stable and should keep you going for years on 10.6.8 if you want.
pitch bend range is not changing when the soundplane tells it too via the NRPN
Hmm, I thought that was working, I'll check into it, thanks.
Midi Learn in this release?
Nope.
BTW why dll began to weigh less? (about 2mb) :D the same as whole installer (Win), about 5 mb.
I'm always working to optimize things where I can. The new Microsoft libraries I use are a little smaller too.