randy's Recent Posts
I want to make more t-shirts but so far this takes a back seat to the "real" work. freeware plugins... probably as examples for an open-source project I am working on.
Another interesting feature could be the possibility to directly address several OSC port in parallel directly in the soundplane app.
I'm definitely planning to make this work with zones soon.
Hello, howdy,
I am working to get this feature rolled into a kaivo update soon. Thanks for your patience. Meanwhile you can use Kaivo on 3123 and Aalto on some other channel. I guess you are talking about layering both synths rather than doing a split?
Great, thanks for the feedback. I think Brian and I are converging on an initial design. This won't be out real soon, but we are definitely moving forward.
Hi, unfortunately this "ghost window" appears in ableton live 9.2b5 32bit and vst aalto 1.61 on mac OS X 10.10.3... :(
Can you use the 64-bit version of Live? I would recommend this if possible. Plugin hosting is much cleaner in 64-bit, this bug will be gone, and everything should be around 10% faster.
The issue does not come up for me an Aalto 1.6.1 / Live 9.1.7 / OS 10.10.2. Both AU and VST are working OK. I see there is a Live 9.1.8 version out, so I will try that and hopefully fix it if something broke again.
Can I double check with you that the AU is truly the problem and not the VST? I have had this problem with the VST in the past, but never with the AU.
I don't usually test with beta versions for compatibility because by definition they have their own bugs.
Noted! This idea has been on the back burner but could definitely happen at some point.
With the Soundplane you can slide any touch anywhere. With the Linnstrument I believe you can only slide a note in the x axis. In general I would say that the Soundplane is more like a continuous controller that lets you quantize it to keys, whereas the Linnstrument is more a 2D keyboard that lets you slide the keys after playing. They get to a similar place from different directions.
The biggest differences are with aesthetics and connectivity. Roger puts all the configurability and lots of labels on the instrument, so that no computer is needed to work with a MIDI device. Linnstrument outputs MIDI only. The Soundplane puts out raw pressure data that external devices can convert into MIDI, OSC or into sound directly. This requires a computer, for now. What I like about this approach is that the hardware is minimal and very reconfigurable.
I believe that OSC will continue to grow in popularity. It is capable of higher resolution than MIDI, and it is more suited for open-ended experimentation. On the down side it is not plug-and-play with any synthesizers, except the ones I make.
Two good instruments. Exciting times indeed.
It might be OK to have lights indicating the active zone map, if there were only four possibilities or fewer. Any more and I want to read the name! The current selections of chromatic, rows in fourths, rows in octaves seem to be sufficient for most people's needs, so for the simplest possible release we could just include these three.
The Soundplane is really an instrument first and foremost, one you can play and not look at, in contrast to most other controllers out there. So let's not waste too much time making it a controller when it's probably more elegant for people to just put a box of sliders next to it if they want sliders.
I think it's OK if we require an external device of some kind (tablet, phone, or computer) to switch maps.
So I guess I'm maybe gradually coming around to "no display".
NOTE: this will require Mac OS X version 10.7 or later to run.
Changes since 1.2.4:
- 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
For those few of you compiling your own version, note that I've moved to using the C++11 compiler provided by XCode. This will enable me to simplify my work with some modern C++ features, and is the reason for the new OS 10.7 requirement.
I do have some Finnish-Americans in the family and I like a good sauna very much! But mostly I just like the sounds of the words along with their meanings. The next plugin will probably be called "Virta."
Yes, certainly.
Hi Jay, is OSC enabled? are you seeing "receiving t3d" at left? Do the other presets work?
If not, go to the drop-down "gear" menu and turn on OSC. You can also select a port offset—0 should be compatible with previous versions.
I just tried all the versions you are on with the bongo party preset and it works OK here.
You may want to do the "normalize" procedure with the new Soundplane version. I am telling people that for improved finger touch at edges anyway. With juggling balls and a high threshold it probably doesn't matter.
There actually is a video here:
https://www.youtube.com/watch?v=Qckvsc2Gzjo
But it is not super useful any more because I changed the normalization routine to include another step. The ida in the "blue" step is to press with a firm palm just pressing down evenly everywhere. Really it's not too fussy. This is what controls the edge behavior.
Here's a capture of my normal map generated in the "blue" step:
Select view mode "test2" to see this. Note that the view scale is set to 3.0 so you can see better. After you normalize it should look something like this with bigger blobs near the edges over some areas. This compensates for the fact that the surface moves less near the edges where it is clamped.
Good news: I'm currently working on the next rev. of the touch detection and it's going well. It should be much better at close touches and the edge stuff. After this rev. I'm confident the code will settle down and I can take the time to document everything much better. It's hard to document a moving target! thanks for your understanding.
Sorry for the glitch! There's a technical problem with integration between the website and PayPal right now, so I have to see the emails and make licenses myself. I hope to fix this soon.
the tracking for the top and bottom rows is way worse in the new version.
Strange, should be the opposite.
Did you try normalizing with the new version? I bet that will fix it. Just go to the expert page and click "normalize" and follow the instructions in the text box.
Selecting carriers will not have any effect on touch detection except to minimize any radio frequency noise present.
Thanks for your purchase. You should have your download now.
Hi, Thanks for the good words. Sorry to disappoint but I have no plans to do a RE version. I have limited development resources (me) so I have to pick my projects really carefully.
okay, when you said 'the SP will initially not do anything' I thought you meant would not select carriers! Now I have seen the problem with no data afterwards until a recalibrate. That is fixed in the repo now.
Just posted a 1.2.5.2 with improved touch tracking (existing algorithm). Should be less prone to problems at edges and ghost touches between other touches.
This is the last tweak I'm doing on the 1.2 line, and now I can start in earnest on the new algorithm.
I'm following this with great interest. The next version of the touch detector should get rid of some of the quirks we all encounter. Hopefully I'll be sending out beta versions with the new detector soon—I'm very excited about this work.
I'm doing a Kaivo update pretty soon but it's mostly for compatibility. I'll try to sneak in something fun... but not delay it too much.
I'll check into the VST issues. I did test with Live and FL before sending out. So, it could be your Live or FL version somehow. I might try deleting the DLLs, both Kaivo and Kaivo_x64, then running the installer again.
About this window issue, Kaivo worked in previous versions of Live but the Live 9.1.7 update introduced this problem. I have a fix for it now, that is out in Aalto and will appear in Kaivo when I update Kaivo in the near future.
I thought you would probably just change the note names, I know inconsistent with guitar tuning, but id assume its what most users have got used to?
If people want to they can make their own setups that transpose to what they are used to. It's important to me to have nice sensible defaults going forward.
now if you do "select carriers" ... the SP will initially not do anything, until you also hit 'recalibrate'
I can't reproduce this one.
I will definitely do a sale in the winter. That's become sort of a tradition. I'm really not sure about anything sooner. I've read some good advice not to have sales too often because they get kind of addicting for everyone, myself included!
Fixed and changed the above link to version 1.2.5.1.
Whoops, I'll look into that, thanks for the report.
There has only been the 1.1 release of Kaivo for many months. Kaivo does not update itself automatically or anything like that. So something must have changed in your software setup there.
I don' t know what tells you "no compatible with live" , can you be more specific?
Yes, a spec for MPE was put together and I plan to implement it in both the Soundplane app and my software synthesizers very soon. It's a good thing.
Have you looked at the SoundplaneZonesOSC example in Max? This works with the ZoneExample1.json setup to send controllers as well as t3d notes. If you don't have Max then OSCulator could do the splitting— I guess this is what you are trying.
Ideally you could use just the Soundplane app to do this and have it send different controllers on different ports, but I'm a little ways off from implementing that.