So i just went to test this and I can't reproduce. Kaivo 1.3.0 ( and 1.3.1 ) are responding to mod wheel OK, both from automation and external controller in Live.
The "mod cc" control in the INPUT module needs to be 1. At that setting you should see the mod light flash in the INPUT module when the modwheel goes from 0 to 127.
Can you think of anything else I should try to reproduce this?
I can't test it on the affected machines, so I'm not too hopeful. But if my hunch is right, this beta may make things better. http://madronalabs.com/media/aalto/Aalto1.8.1b2.pkg
If you want to play a different voice from each note of the Linnstrument, you want MIDI MPE. This can certainly sound different from using MIDI alone. It's hard for me to guess what you might mean by "completely different" though or whether it is a problem. In general I would advise to focus on MPE with your Linnstrument and I'll be here to help.
There's not much if anything in the manual on MPE yet. Sorry it's lagging behind reality. I'll do what I can to catch up soon.
Happy new year!
OK, thanks for the report. I'll see what I can do to reproduce this.
Virta at 96k is going to be a beast, but I'm going to make it better over time.
HI Roland, good to hear from you! So, probably what happened is you made presets in version 1.1 and then didn't do "convert presets" with version 1.2. I should have made a better effort to let people know this was needed. To fix it:
This will copy the presets from the old location to the new location in ~/Music/Madrona Labs while converting them from XML to JSON.
If you have any troubles you can let me know here or by email to (support at madronalabs.com) and I'll be around to help.
The Soundplane antennas are not available. If you're making one controller it's not too hard to make a copper foil one yourself. you will probably want to cut slits in them so they are a little flexible.
I advise everyone to start with a single-point sensor to test your technology and materials.
I love self-running patches! Thanks so much for sharing with the greater Aaltosphere. Please keep in touch, I'm interested to hear what finished music comes out of your process.
Is there a crash report or any other information you can send me? What exactly happens when Reaper crashes? Are you trying to do any particular actions beforehand? Thanks.
These betas should fix a few problems that came up with the latest releases:
As betas, these have not been extensively tested, but they seem to work so far. If you have had troubles with the recent releases, please try these and let me know how it goes.
These betas do work with the new licensing system, as indeed all future ones will. So if you have a license and the plugin is working for you, you may keep using it without any demo restrictions.
I'm very happy to have turned these fixes around quickly thanks to the new build scripts and licensing code in the new versions. In general, you can expect to get fixes from me more rapidly and more often because of this. And I'll have more time to work on other neat stuff too.
I just download Reaper to my Windows 10 machine and it's working here. I added some missing Microsoft runtime files in a 1.8.1 update coming soon. That may fix it for you. Please let me know.
I'm happy to help. There are three steps:
If something is not working you can reply here or email me at support at madronalabs.com.
OK, Let's focus on Aalto then. the other plugs take a lot of CPU even when they are functioning properly, so the problem will be much more obvious with Aalto. It looks like one voice of Virta is taking up 25% of CPU or something in your example, which is too much. But 10% or so would not be out of line.
For more background on CPU use in the plugins please see http://madronalabs.com/topics/3565-getting-the-most-out-of-kaivo
You may find some tips that help. They are expected to take up significant CPU when no notes are playing, for example.
back to Aalto, here's a question: when you load Aalto does the CPU meter seem to go up gradually?
Thanks for the assistance. if you are willing to hang around and try some of my experiments I'll be happy to give you a coupon in appreciation.
Hi Randy, i'm having an issue with Virta's vocoder. When i load a project that has an instance of Virta with 'Vocoder 256' set as Formant Mode, there's no output or visual graphing of carrier and program.
I'll look into this ASAP, thanks for the report.
A minor note: please post support issues in the software forum to help me keep track of them.
Kaivo has some additional fixes to correct problems that version 1.0.2 introduced in certain DAWs.
I've updated the website to replace the previous "My downloads" area with the new "My licenses" link. To replace your old watermarked plugins, simply run the new installers, then log into the website and visit your "My licenses" area. You should find links to your snazzy, new, very pointy license codes there. Just copy them to the system clipboard on either Mac OS or Windows, and click in the upper right of the plugin where it says to. Then you're all set!
Code signing for both Mac OS and Windows, also made possible by getting rid of the watermarking, is something else that should improve life for everyone. No more option-clicking to install, or me explaining to you that you have to do that. And with the plugins protected by a secure chain of certificates, you can be sure that they are genuine. There was a time when I didn't see the need for code signing. But after seeing some of the ransomware floating around these days, I'm convinced it's important.
A long time in coming, the new license system is more like the other plugin registration systems out there, and will hopefully reduce some of the confusion that came up about how to make things go. On my end, it's going to reduce server loads significantly and let me deploy new software versions much more quickly. What previously took several hours (I'm not proud to say) is now accomplished by typing "buildAll" and then, if everything sounds good, "deployAll." This will let me spend more time on making things sound good, and get any needed fixes to you faster and more frequently.
It's going to be a good year.
@enparticular: thanks for the report. Can you tell me what speed of CPU you have in your Early 2015 13" Macbook Pro?
I have exactly three reports of weird glitches, and all with this particular Macbook Pro. It's very mysterious.
Please try opening some patch that just makes noise by itself (Alessandro's Machines for example) then closing the plugin window. Does the problem get better / CPU use go down without the graphics showing?
Can you please try Kaivo and Virta and let me know if you have similar issues?
What if you make a new Logic project and make a new track with Aalto in it? Does the menu work then?
I'm updating my Logic to 10.2.4 to see if that affects anything. But mostly I'm on the same recent versions here and everything is working for me.
I'm going to look at the registration / menu code and try to see how this might be possible.
Did you register your plugin? You need to do this with version 1.8.0 and higher. If not registered the upper right will read "click to paste license."
Can you explain more? What happens when you click on the preset menu? Do you see the menu? If so what happens then?
@hyperscientist: you posted about how you weren't actually so frustrated, and then with your system details. Then I updated the website, had a major emergency, and had to recover from an image just prior to your post. If you have a way to recreate it, or can just provide your system details again, please do. Sorry for the trouble.
One more piece of info: the other person has this problem in Bitwig, but NOT in Ableton Live! So that's odd. Do you have any other hosts you can try it in?
Finally let's rule out the off chance that you are running an old debug version or something. Can you confirm the Kaivo version in the upper right?
The other person has an i7, same exact machine possibly. Are there any settings like App Nap you can experiment with?
thanks for the help.