glitchrock-buddha wrote: When you say the latest version, what version do you mean? I'm currently using 3.5b1. You might have 3.4.1, which is the latest full release, but I prefer the recent beta.
Off to try it, as it can't be any less stable than 3.4.1, serious!
Yeah that's an awesome trick, I'm taking you up on it for sure. Moved all completed songs with Kore instances over to VST versions, I'll sit down this weekend and do the songs I'm working on next, then disable AU plug ins in Kore. I use AU plug ins outside of Kore regularly with quite a few cool freebies that are AU only etc. Automap, would be far more fun for me if it wasn't hosed as far as the Original two LED SLs are concerned. They really should have worked with Ableton to get Mackie control support and Automap at the same time... frustrating. Why Cubase always gets third party support right where everyone else just craps their pants and looks confused I'll never know? ReWire, Automap etc. all well supported in Cubase, a DAW I'll probably never use for music.....I run automap versions of all my plug-ins in Kore, which is loaded in Live. Again though, I only have VSTs enabled in both Kore and Live, no audio units. I have automap pro enabled as well.
Are you using automapped audio units? I'd stay away. With VSTs, the greatest thing is that if you ever get worried about automap being buggy or just don't trust it in a live situation, you can simply remove the automap versions of your VSTs temporarily and all tyhose VSTs will just load their regular versions and you don't have to have automap in the equation. Later (as long as you don't save the set), you can put your automap VSTs back in your folder where they were, and the next time you open your set, they will all be the automap versions again. This isn't possible with audio units. This is a little known secret because you have to move the automap VSTs into your system VST folder (they get created in your user VST folder).