thetechnobear's Recent Posts

I see it :)

this was a lot of fun... look mum no computer yet a Soundplane ! :)

any news on further development on the Soundplane software, in particular the touch tracker? are you likely to be looking over that code base any time soon?

Ive been doing some more work on MEC, my project which provides a standalone solution for the Soundplane (and Eigenharp), basically turning things like rPI/BBB into 'intelligent dongles' , so the Soundplane can be more like 'a standalone instrument' rather than a computer controller.

currently works with Eigenharps and Soundplane, and connecting too MPE devices (im using the Axoloti to make it computer independent :))

if your back into 'Soundplane' mode, it'd be great to discuss a few thoughts i have. as Im getting a little bit too much latency with the Soundplane due to the CPU requirements of the touch tracker.

so not sure if I can get some performance gains, or really need to move to something more powerful, the O-Driod C2 is quite a tempting candidate, given the rPI3 wont work.

anyway, I know, not much point in discussing unless your actively looking at the Soundplane software... since I think its quite a while since you were look at that code base.

Finally, I've got it finished..... and wow, it was worth the effort!

I use the Bela Salt as a means to allow the Soundplane to be connected to decode its protocol...
Ive made it so that there are custom layouts, and options like playing in fourths, quantised fully and partial, or none.

I was also inspired by the Intellijel Planar, so Im using the CV inputs to you can directly modulate the soundplane touch position.....
also as the Bela has audio in/out, Im using it as a kind of VCA controlled directly by touch (using Z, but also a mode where it can do x/y cross fade :) )

anyway, here's me playing it for the first time....
youtube link

I'll probably do a follow up video that goes into a bit of details, as its really shows how the soundplane could be the 'ultimate' eurorack control surface :)

my software is my Github for those interested, it could be no doubt adapted for other platforms).

I hope Randy does not mind me posting this here,
I think its very relevant to the Soundplane community,
as a small community I hope Soundplane musicians will appreciate being part of a broader community.

If you have Soundplane, or other expressive controller/instrument.
please come and join us, and help spread the word so we can form a community around these wonderful instruments.

Today, we are launching a new community forum for musicians interested in expressive electronic instruments and controllers.

PolyExpression's aim is to form a community of all musicians using the wide variety of expressive electronic instruments that exist today (and tomorrow).

Excellent communities exist already for each instrument, maintained by the manufacture, these are perfect for support.
This community differs as it is independent from instrument / manufacturer, a place where all these musicians can come together in one place, to share their enthusiasm for adding expression to electronic music using this uniquely wonderful instruments.

Whilst these instruments are each unique, and we want to celebrate this too, there are also many topics, issues and inspiration that are shared between them. These range from their goals, workflows, sound design and to more “mundane” topics like software and hardware issues.

Together we hope we can share these experiences with a broader range of musicians, and learn and be inspired by each other.

Please come and join us, help us build a community that shares its love for Polyphonic Expression in electronic music.


this video was a challenge for the AE modular,
but I use Aalto for both the Eigenharp part, and also the Soundplane, so lots of Madrona Labs work in this :)

Journey thru Space]

(click on image to play, if my markdown-fu is correct ;) ... dont think this forum supports embedded videos?)

any news on this? release at superbooth ? ... my rack is waiting for this now :)

lol - just noticed, first post on this was nearly 4 years ago... doesn't time fly!

yes, Ive had it working in various forms on Linux, both desktop and rPI, and yeah on the mac it was under VMware.

this was the libusb implementation in the madronalabs repo.

Ive not done much recently with it, as I was waiting for Randy to complete the 'reworked' tracker, but now that's done and released - I do plan to come back to it asap.

all plugins updated , and soundplane release too, feels like xmas - hope to get to play with it all over the weekend :)

thank you for your hard work, and continued developments... looking forward to sumu

btw: is the all the code for the soundplane release in GitHub... as its now released/stable, I could look to doing my small derivatives :)

perhaps an interesting market for rPI3 :) (so ARM)
particularly, if you make it standalone... Im increasingly using rPI headless.

recently did a port of monome norns to rPI + Push2, feels like a complete instrument

something along these lines with Aalto, and soundplane support, would be tremendous.

ok, Push2 is not going to entice many, but we could be creative in this area... my Orac 1.1 for example is going to support remote display, so use your iPhone/iPad , or anything that you can create a UI in that uses OSC.

so this is a direction im heading anyway...

but still, Id probably even buy a Norns, if you basically used if as a hardware platform for your Synths and Soundplane support :)

@rsdio , agreed, I tend to mostly use Z straight into a vca , so you can play the envelope.

And I don’t see that changing in eurorack :)

it might be nice if Z could be switched between pressure and (note on)velocity

will the firmware be user upgradeable, handy if any bugs become apparent etc.
(and open sourced?!)

really looking forward to this, if you need early adopters/testers, Id love to help out.

(im definitely going to need more oscillators/filters and vcas :) )

cool... look forward to meeting you, Im Berlin bound tomorrow :)

Ive now booked my tickets for superbooth too... so will see you there :)

the issue with VCV rack is that they should have diverged from the 'physical world' for polyphony... i.e. where modules and cables could be polyphonic.. like they can in Reaktor (not blocks) and a few other software modulars (e.g. P900)

having used Reaktor Blocks with MPE, the novelty of wiring up multiple voices soon becomes pretty tedious.

one of those times, where the software version should be not restricted in the same way as eurorack.

(anyway this is why I didn't bother creating a T3D or MPE module, like I did for Blocks/Reaktor)

I checked Kaivo 1.3.2 with L10 , and it was fine too

when you lose the sound - does the little oscilloscope show anything?

Kaivo working fine for me in Live 10.
Im using Live 10.0.1b10, macOS 10.13.2, both VST and AU (64bit), latest kaivo (1.3.0 ?)

cool, much better :)

had a play over the last few days, and the tracker does feel better and in particular the top and bottom rows are much more reliable... i can now use them, before I found them too likely to trigger the row above - so this is excellent.

a couple of small bugs:

first, now only 3123 works , if you select another port (e.g. 3) in aalto etc, then SP app shows the new port (aalto(3) , but when you select it, you dont get any sound, and in fact its still sending OSC messages on 3123

second, i think your sending empty osc packets continuously?
(or the frame bundle has a bunch of empty messages)

if you do an oscdump you will see

  /t3d/frm ii 10209708 65590
  /t3d/frm ii 10209724 65590
  /t3d/frm ii 10209740 65590


ok, the OSC kind of works ;)

but you have something odd going on with the port offset....
the default for t3d is 3123, but you seem to be using 3125?

anyway the upshot is, is you need to set the osc offset in Aalto to 2 to work.
(using aalto 1.8.0, Kaivo 1.3.0)

from logs, look like you are connecting from 3125 onwards, and created an inbound socket for 3124... not looked for why this is yet :)

(also default in the dropdown appears to use 3125)

perhaps a simple change to move 0 back to 3123, and perhaps move your input port if required to 3122.

Starting Soundplane...
SoundplaneModel: listening for OSC on port 3124...
MLOSCListener: trying listen on port 3124...
MLOSCListener::listenToOSC: created receive socket on port 3124.
initializing pthread attributes...
creating listener thread...
MLOSCListener running socket. 
SoundplaneOSCOutput: trying connect to ports starting at 3125 
                 connected to port 3125
                 connected to port 3126
                 connected to port 3127
                 connected to port 3128
                 connected to port 3129
                 connected to port 3130
                 connected to port 3131
                 connected to port 3132
                 connected to port 3133
                 connected to port 3134
                 connected to port 3135
                 connected to port 3136
                 connected to port 3137
                 connected to port 3138
                 connected to port 3139
                 connected to port 3140

btw: any chance you could move the forum software over to Discourse, it really is much better forum software... and formatting options (for code) are much better ;)

anyway, this was just a quick sanity check... will hopefully have time to sit down for some quality time with the soundplane (on 1.7.0) later today :)

he he, i know how that goes ;)

what was the issue with the kernel panics? when i looked at this (on eigend) it was due to completion events being returned to a process that had been stopped/killed ... so all i could do was to ensure the process closed cleanly.
did you find another fix?

Have you had a chance to fix1.6 yet? I’d love to move to it, and also look at porting my code to it.
Thanks Mark

ah, those are the pesky kind of bugs...
hope the fix is not too difficult.

oops, bad news... the OSC t3d output seems to be broken...

its not working with Aalto properly, and when i look at the underlying osc message I can see its hanging on to notes that have been released, and its transmitting all 16 touches on every update.

ive tried resetting to factory defaults , recalibating, changing touches, rotate - all make no difference.

note: the touches display looks absolutely fine, so seems to be OSC.
note2: though ive not tested MPE... so could be interface between the touch model and the outputs.

Im going to have to rollback, or rather reinstall 1.5 for now :(

ooh, great news, can't wait to try this...
thanks for the continued development.

look forward to digging into the source again in the new year.

unfortunately, all my macs are on 10.12 now, soon going to be testing 10.13

one thing, apple change the usb stack significantly on 10.11...
but for my development, the issues i encountered were the other way - things working on 10.10, started crashing on 10.11+ ( they have been slowly improving). that said, i didn't have to alter anything (other than ensuring the apps closed down the usb connection correctly).
sorry, not helpful, but perhaps useful to know why 10.10 is likely to be different to 10.12 (and probably 10.11/10.13)

is the code base now stable, and in GitHub? or are you still working on it?
are the changes done for the embedded/eurorack system?

if its not under going significant changes, Id like to update my fork, to bring in some of my changes (midi/note offset visualisation)...
and also use if for rPI etc (will be interesting to see performance impact on non-desktop systems)

works fine here ... macOS 10.12.6 :)

@Sanne.... this works as expected for me in Live 9.7.4 / Mac OS X.
i.e. in arrangement , start record, it tracks all changes, when you switch presets it records the new values, and subsequent changes...
and no need to hit rearm automation.
(it works identical in Aalto as for other plugins e.g. u-he diva/ace )

one thing you do need to be careful of, is when you do playback, you must start aalto in the same state as you did when recording ... which Randy in his OP alluded too.

you can achieve this in one of two ways

  • use a program change on the recorded clip (MIDI Programs folder)
  • when you start recording, switch to your starting preset (and hence save all automation values)

as fars as I see this achieves what you want... i.e. start recording, select preset, alter values to get a nice sound, repeat many times... then use playback, and find the place you liked... stop, and hit 'save preset as'

note: when you do playback it will NOT change preset name, this is because ableton is as such recording the preset change, just recording the values of the preset.
... btw: i didnt try changing presets via Program change messages, Id assume that would be recorded. (though you'd have to be careful between sessions to NOT change your program ordering )

@randy, I dont think aalto needs to track changes, surely this is exactly what DAWs do with automation, why replicate the functionality... the only thing id prefer, is an easier/quicker way to assign program changes. perhaps just assign to existing presets into different banks/programs #. (rather than copying presets around)

ideally what Id like is...

a) updated Aalto with more voices but apart from that the same.

b) a completely new instrument, kind of similar to Aalto ,but not Aalto 2, that would not need to be patch compatible i.e. not limited/shackled to what Aalto does already (so well)

(u-he are doing this with Zebra 3, they already have said it will not be compatible with Zebra ... I think they said they will allow imports of patches, but they may/will sound different)

I do agree about Kaivo, I don't use it as much as I thought I would (and no where near as much as Aalto) because its resonance peaks are really hard to contain... I find its quite a small zone of usability, perhaps within only an octave. (pitch can wander too, but I think thats part of the beast)

anyway, Id love to see another out n out synth from ML...
also perhaps we can skip the sequencer, so we can have a bit more UI real estate for voice control... I know alot use the sequencer, but is it not easier to just use the sequencing/automation facilities already present in every daw (or use a MIDI sequencer VST)

if I want to build, is the 'embedded' branch, the latest and greatest? and are all the necessary changes to madronalib already checked in?

also do you know if the cpu load has dropped with the new tracker?

generally, thinking about updating my fork, to get my midi goodies... and also the mec repo, so I can test it again on my bela.

so I got distracted and left the SP turned on for about an hour or so, untouched - when I came back there were lots of green patches in the middle...I had to turn it to 0.20 to get rid of them all.
but then by chance, I decided to hit 'recalibrate' ... and they all disappeared, even when turned down to 0.10 .. is this what you would expect?

this is all great news :)

if you can improve the boundaries, that will make a huge difference for me, in the previous version I rarely used the top/bottom rows, as I couldn't be 100% sure it'd trigger the correct note.

when doing the boundaries, perhaps you can also work out (or even estimate) the useable area of the top and bottom row, so that why can be scaled to that...
e.g. if 50% of the top row perhaps its better, to have Y run 0..1 over that 50%?

another observation, so you talked about x/y and turning up to x10, and then using lo thresh to get rid of green patches... so I did this (though even without , I wasn't getting false triggers) , I turned it up to about 0.12-0.13 (default of 0.10).. and they disappeared, but noticed after about 5 minutes of playing, they seem to be appearing again, so turned it to .14, gone, then a few minutes, .15 etc...
but got distracted, turned off the SP/SP app... can back after a while, and noticed I could turned it down to .12/3 again
always the green patches in the same area (centre, most played/worn ? ... I couldn't really figure if this was a 'software' issue, or if the surface is 'warming up', perhaps not returning to the 'same point'


( as I said, it wasn't causing any false triggers, I was merely following your instructions above-- so perhaps this is expected, nothing to 'worry' about)