randy's Recent Posts
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.
I have three instances of Aalto in Live. Using the gear menu in Aalto I set "OSC Enabled" for each one. Then for each one I set a different "OSC Port offset": 1, 2 and 3. On launching Live with this setup, each Aalto should broadcast itself as a Zeroconf service over UDP.
Then opening the Soundplane app (1.1.2) I see all of the Aalto instances in the OSC output menu. I can switch between them in the Soundplane app and they all play in turn.
The link is in the sticky thread above and also here:
This is just some small fixes and an update to work with the most recent Aalto / Madronalib changes. Now I'm beginning work on a new generation of the touch tracking software.
NOTE: I recommend that upon installation, you remove your old SoundplaneAppState.txt and then recalibrate with this new version. As always, that file is ~/Library/Application Support/Madrona Labs/SoundplaneAppState.txt.
Thanks, will send a fix ASAP
No worries!
I just used version 1.1.2 in a show with several Aaltos and it was working well. here is a link:
http://madronalabs.com/media/soundplane/Soundplane1.1.2.zip
The only issue I'm aware of that will come up with 1.1.2 is that you may have to select an Aalto OSC output on startup even if it looks like it is already selected.
I'm going to put Mark's fix in a 1.2.5 ASAP, probably today. I noticed after some playing, and I think after Mark's calling it to my attention, however, that the touch detection was somehow off in 1.2.x So I would use 1.1.2 for a show right now while I check this out.
Sorry for any headaches. I made a lot of changes recently and they are taking a little time to settle down.
Did you try moving them from Administrator to your regular login as @carmine, above?
You may be editing files in the wrong location. Aalto 1.6 and up are using ~/Music. Previous versions use ~/Library/Plug-Ins/Presets...
Just try a simpler test first, make a new .scl file and see if it shows up in the menu.
You can just edit the scl files. You could also make a .kbm file to specify how the notes in the scale map to MIDI notes. without a kbm file Aalto / Kaivo use a default mapping with A440 as the tonic 1/1. Full docs are on the Scala Home Page.
You may have to close and reopen Aalto after the files are changed. I'll have a look at this.
Wow! that really does sound amazing. Is is a dry climate? You have a stream or something?
Maybe you are sick of almonds, but I find almond butter on apples to be a great breakfast.
I was just curious what sort of place you lived in that was off-grid. It sounds wonderful.
In general, US or UK power (mains) lines shouldn't interfere with the Soundplane carriers. But there's always some device that can cause a problem, like the lamp one customer had, and this might show up in a different frequency in a 50 vs 60 Hz environment.
The carriers are all in the range of 10-30 kHz. This frequency range is a good one for the Soundplane because nearly nothing transmits RF on it, and any transmission attenuates very quickly with distance. The Soundplane picks between all the possible choices at "select carriers" time.
Aalto 1.6.1 is out now for Mac and Windows. You can get it at all the usual places. If you have a license, click "my downloads" up there to get the link to your personalized version. If you want to try the demo, go to the
product page. Make sure to get the patches download if you're on Mac OS.
1.6.1 changes:
- fixed a problem where parameter automation was turning off due to a loop.
- Fixed "ghost window" issue on close in 32-bit Live
- fixed issue with AU version not loading in Live
- fixed errors in OSC enabled state
- fixed a possible crash in the patch converter
- patch converter on VST version was generating default patches from .aupreset - fixed
If Kaivo is not doing this, then I hope I can fix it in Aalto for the next update.
My busy fingers always play a few notes on my keyboard before I test CCs. This is probably why I never saw this.
You can look at the .scl file in ~/Music/Madrona Labs/Scales to see what the actual ratios are, and reorder them if you like. if there is no .kbm file A is defined as 1/1. Then the ratios in the scale are in order as intervals up from that. So in this file the 567/512 is the minor second or A#.
Checking with my calculator, indeed 1323/1024 is a little less than 21/16. I don't know from any other source if this is the way LaMonte Young played it!
Good to hear, I hope that's a good workaround for you right now. I hope to roll out a fix for poor old 32-bit land soon.