randy's Recent Posts
Interesting... could be differences in US / UK power responsible. But 0.0044 should be just fine. I like to see
The only thing I have noticed changing the amount of noise here is the USB hub configuration. One customer had an intermittent problem but that turned out to be a very noisy old neon lamp.
PS.
as I'm off-grid running off of solar power with good quality inverters
whaaaat?
Oh yeah, make sure "Use Audio Units" is on, in the File / Folder Preferences page in Live, and try "Rescan" there as well.
thank you for sharing. Like some artifact of bronze age electronics...
@mtvic, I'm not sure why. That configuration was tested a lot, and a problem with AU not showing was fixed for 1.6.1.
If the plugin is not showing up, you can look to verify that it's in the AU Library folder: /Library/Audio/Plug-Ins/Components. If it is there, you could try removing it using the Finder, then running the installer again. You can also try this voodoo to remove your Audio Units cache: http://support.apple.com/kb/ts1086
If you are ever getting random touches on the top or bottom, it is likely due to a noisy carrier set being selected. Setting the right carriers is needed to avoid noise from the power supply and any other noise. Unfortunately the frequency of this noise may change any time the power conditions change, such as plugging in a new USB hub, for example. As you probably know, go to the expert page and pick "select carriers" to do this.
Your symptoms about (a) sound very much like this is happening. You can look on the Touches page in calibrated view, and any carrier noise will show up as a particular pair of columns, symmetrical about the center, that are bouncing up more than the rest.
When you select carriers, the max noise for the best carrier set as displayed in the text window on the Expert page should be no more than 0.004. All shipped Soundplanes met this criterion in testing.
The (b) kind of touches sound like limitations of the touch tracker code, frankly. It can be made to do the chords you are looking for with the right combination off playing style and settings. I'm striving to make this much easier in the next version of the touch tracker.
Thanks for the tuning vis. idea. This would be a nice option I agree.
Hi Mark, version 1.2 is still at http://madronalabs.com/media/soundplane/Soundplane1.2.zip
That's odd about the ghost touches, because I haven't changed anything to do with touch detection in this version, except make the edges easier to get into... which is actually after touch detection. You can try setting the threshold higher, or the template tolerance lower.
I don't think you should have to recalibrate.
I could see adding different app states. For now you can save a backup of the app state file yourself if you like.
I should also ask you for more information about where and when you are seeing these ghost notes!
Please try Aalto in 64-bit Cubase, and tell me if the problem goes away.
Are you saying Cubase is 32-bit only?
Anyhow, I may have a fix-- please check the next update coming soon.
Hi Jose, I think the internet is the best book for this kind of work. On the software side, you can download JUCE and try to make some plugins. That will be a good way to get started. On the hardware side, you could start by playing with an Arduino or Raspberry Pi and get a feel for the communities of makers surrounding those projects. And then there's the NIME conference and all the new instruments people make and present there. These are a few places you could start.
Are you running the 32-bit or the 64-bit version?
Hi Simon, there aren't any crashes with Aalto 1.6.1 that I know about now. Is it reproducible? If so, what do you have to do to make it crash?
@eblomquist, I would try removing the component and installing 1.6.1. You can also try this voodoo to remove your Audio Units cache: http://support.apple.com/kb/ts1086
I'm getting reports of Aalto not showing up at all in Live after upgrades to 1.6.0. Unfortunately this was not seen in bets testing and I can't reproduce this bug here so far. So if 1.6.0 does not show up for you after install, please chime in with your OS and Live versions here. Be sure to mention whether you are running Live 32- or 64-bit. If possible, please try both versions and let me know the results.
If Aalto fails to show up in some other host, please mention that also. So far, this seems to be limited to Live.
It strikes me that the (usefulness) / (ease of development) ratio on this one is super high, so I'll try to sneak it into the next update.
Sorry you didn't get the news. It's on the front page news here and on Twitter, and I will always post about updates in both those places.
Wait, did you try the preset converter in 1.6.1 ? That VST version had the exact problem you started this thread with, and got fixed as I posted a few days ago.
I know just what you mean but I am sure Aalto has never done this. Possibly Cubase did it somewhere.
If you can find a preset file hat seems to be causing the trouble, please email it to me— I would of course like to guard against such problems. Sorry for the trouble.
In my opinion you can safely get rid of your old presets in the Library folders. Maybe try the converted versions first to make sure they are working well for you. But it sounds like all is well now.
I am pretty sure that I never added such a feature! It could be a feature of your DAW. It's certainly not a bad idea though.
Hi Bendik,
Thanks for your purchase. the license did not get made automatically because the email you used for the PayPal purchase was different than your madronalabs.com account email. I fixed this by adding the license, and now you should see the download links if you click "my downloads."
If you have any more questions, please contact me by email at support at madronalabs dot com for the quickest service.
@swey, are you on 1.6.1? If so, I'm taking a wild guess that you have some preset file that is corrupted. You could try converting just one directory of presets and see what happens. If you can find a particular file or kind of file that seems to be causing the problem, please mail one to me at support.
And, as always, what host / OS versions are you using?
Not fixed. Please use "fixed buffer size" in FL studio as a workaround for now.
Version 1.6 of Aalto is now available for Mac and Windows. This version contains many improvements for efficiency and host compatibility.
New in Aalto version 1.6:
- both AU and VST versions now use .mlpreset files in new JSON format
- added preset converter to convert all old presets to new format
- presets directory moved to ~/Music/Madrona Labs
- improved speed of preset loading
- fixed a problem with keyboard stealing in 64-bit VST
- now saving window size state properly in compatible DAWs
- fixed an issue with the oscillator and extreme pitch modulation
- added OSC enable / disable and port offset (Mac OS)
- sequencer now quantizes to currently selected musical scale.
- fix parameter loading when no DSP is active in application (for Max/MSP and Vienna Instruments)
- fixed problem with sequencer retrig
- fixed defaults for envelope trigger and x vel
- added defaults to make MIDI patches more compatible with Soundplane / t3d
- added clearer display of multiple channels in scope dials
- fixed a bug affecting MIDI timing
- added multi-channel MIDI receive for voice-per-channel operation with Soundplane / t3d
- fixed an issue affecting Save as... on some systems
- improved graphics performance
- fixed a problem that prevented MIDI program changes on some systems
- fixed bug when no MIDI Programs folder was present
- Scala keyboard mapping files (.kbm) now loaded if present in scales directory with same name as scale
- improved UI response for dials with only a few values
- on Save as... outside normal patch directory, warn then allow anyway.
- fix an issue loading patches if the home directory was renamed (Mac OS)
- fixed a bug where a program change could cause t3d to stop receiving
- added environment menu that contains editor and OSC settings
- added "reset editor size" option in settings
The Aalto 1.6 update is free for existing Aalto customers. A demo version is also available free of charge. The demo plays a gentle reminder sound every so often, does not allow saving and is not time-limited.
This Bluetooth idea is good. It would certainly be cheaper than an OLED display! The disadvantage would be that you need an iPad or something for calibration though, and then I would have to write that app... still intriguing though.
There were some automation problems on various hosts due to a bug in 1.6. Thanks for the reports, these are fixed for the next update.
Hi Josef, I added a license for the 1.5 download to your account. Sorry for the trouble.
Thanks for the example, i'll investigate when I'm back to work on Kaivo.
Just want to say thanks a lot for sharing—this thread should be fine!
Yes, good point about getting other tunings in there. If the module continues the Aalto / Kaivo way of doing things, then there will be a separate selector for tuning tables. We'll see if this is feasible or if it should get hacked into the zone map somehow.
There is a bug in the 1.6.0 VST that made a bunch of default presets in ~/Music/Madrona Labs. You can either go back to 1.5, or you can delete the ~/Music/Madrona Labs presets and use the 1.6.0 AU version to convert the presets again. Your old presets are still installed and unchanged.
Sorry for the hassle, working on 1.6.1 here.