randy's Recent Posts
Today I put an installer for Soundplane version 1.4 on the web site. This version fixes a problem with sliding between rows when using MIDI, and has improved filtering so that touches are less noisy.
The most exciting part remains under the hood, for now. Version 1.4 comes with the ability to build an experimental version for Linux. Thanks go to Per Eckerdal for leading the charge and bringing his Linux expertise. If you have the time and the ability to build Linux software, feel free to check out the soundplane repository on github and experiment with it.
Please note! This is not currently "support for Linux." It is an experimental build aimed toward future support. So please don't email me at support about Linux things, but please do share your experiences or questions on the hardware forum, and I'll be very interested and offer help when I can. So far I hear that it works—with some issues—on one Debian system, but is not playing well with Ubuntu on the Raspberry Pi.
The cross-platform build is also a move toward supporting Windows. I'm currently focused on getting the next plugin out and there is not a firm schedule for this work, but it's a thing I want to see happen.
Good to hear, thanks for the info. If you come up with anything else of course I'm interested. I have a BeagleBone Black arriving here soon to try out.
Just an oversight, not intended to be private.
I merged Per's versions with the master branch today and tested everything on Mac OS. With success! I have no way to try the Linux version but I should have a Linux computer here soon. I'm sure you will beat me to it! If Axoloti is running something Debian-like, this should be straightforward.
Note that this moves us to a cmake-based build—please see the build instructions.
These are at:
git@bitbucket.org:per_eckerdal/soundplane.git
git@bitbucket.org:per_eckerdal/madronalib.git
a few small madronalib changes were needed for Per's Linux port. I have yet to merge them into the master. When I do, the changes will show up in master on the madronalabs repo.
Thanks for your support!
Of course, I’ll look back here to see who wants them and add licenses as soon as I'm able.
Hi, sorry for the slow resolution on this. I took one stab at fixing the download problem and failed. Now I am on a retreat through this weekend working on the new plugin. I'll have to get back to the download issue next week. Thanks for your patience.
[UPDATE] another try and fail. I'm going to meet up with my web guy this week to work on it.
I plan to keep the touch tracker code open source. It should be easy to port. I'm certainly up for helping, as much as my time permits. There's also a Linux port in the works using libusb. I have no idea if an STM32F4 will be capable of running the touch detector, but let me finish it on Intel and then I can help try to make that happen.
Hiya, I don't have much time right now so this is short. But I think you are on the right path. If you got that the carriers need to be synched to the ADC clock to avoid drift, you understand this pretty well.
a 1kHz sampling rate as used in the Soundplane may be overkill. The material damps the overall response rate, and fingers don't move super fast, so half that would be enough for a good controller in my experience.
We do the FFT on the Soundplane to reduce the bandwidth needed. We are currently maxing out the bandwidth of one USB hi-speed channel.
As always, my advice is: try 1 taxel first!
Check out this lovely Soundplane performance en plein air.
off the grid: on a plane from ingMob on Vimeo.
Hi hez, OK, I'll have to give Bitwig a look and try to reproduce this. Sorry for the trouble, this is on my bug list and I'll investigate as soon as I can.
Thanks for the update. I will test the MIDI response at a buffer size of 32.
There is no drawback to using a buffer size of 64, because Aalto has a minimum buffer size of 64 internally.
You might know this, but for reference, 64 samples is only about a millisecond, in which time sound travels about 1 foot (0.3m). So you get the same additional latency when moving your head 1 foot!
@ezmony see your email!
Excellent! Thanks for sharing.
If you are using both envelopes and pressure to control the gate, you can create a situation where notes will be stuck on. Does this happen with a preset patch? If so, which one? Or if you need help with your own patch you can paste it here.
Generally you can use either MIDI notes or direct pressure (channel pressure) to control the note volume, but not both.
Tip: use the animations in the dials to look at what each voice of your patch is doing for each signal as it flows through the synth.
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. :-)