Automap templates

[glitchrock-buddha]

I spent some time on these, trying to get the best balance of sticking with the original synth layout and also making it make sense on the hardware. I'm pretty happy with them, and I think a few minutes playing with them and you'll remember you're way around pretty fast. It almost becomes almost with hardware. Mouseless bliss.

http://www.mediafire.com/?pxoxsa87p9gs81p
(updated May 1 2011)

In this file is novation automap templates for:

Analog Factory
Sylenth1
Poly-Ana
Pro-53
Oddity
Phoscyon
TAL-Baseline
TAL-Electro
TAL-Uno-62
ABL Pro
Gladiator 2

Enjoy those for now.
I'm sure I do more in a few days. Maybe tackle some biggies like Zebra and Alchemy. I'm debating wether or not to do the Arturia ones. They'd be perfect but so many buttons and controls are not available to be mapped on those, it drives me nuts. Arturia might make the rest of the parameters visible to automation/automap in futures updates. Hopefully.

Cheers!

[hangar17]

thank you!

=D

[timothyallan]

Do I need to run the gay automap server for these to work? Because I don't

[glitchrock-buddha]

Yes. But it should open automatically when you open Live. It can sit there unseen. Doesn't get in the way. With the newest beta they put back the option to have the window not open at startup.

Using automap templates is way better than regular midi templates.

[timothyallan]

I permanently turned off my automap server so it doesn't launch with Live. Maybe I'll stick on v3 and see if it's better than it was

[dbolt]

Thanks.. I've enjoyed using the Automap for Poly Ana its made me really want this synth bad..... I know this takes a lot of time to work out.. I've tried and get so frustrated and unhappy with the mapping that it's either start over or I just say buck it and move on... Now with Live 8's new configure feature I get lazy and map out 16 or so of the most used parameters and call it day... Your right this is as close as it gets to hardware that's for sure. I don't know about Zebra that synth is such a module type synth that it constantly changes and I've never even thought about mapping that one.... Good Luck!

Thanks again

To Tim: Yes you have to have the automap server running in the background... you have to open the templates up with the server program....

[Android Bishop]

sweeeeeet
gonna check these out when I get home

BTW whats with all the hate on the automap server? that's what makes automap awesome.

[deejay1]

excellent!!! thanks!

[timothyallan]

is everyone using v3? I'm still on 2 as I heard 3 just keeps nagging to upgrade to pro....

[glitchrock-buddha]

is everyone using v3? I'm still on 2 as I heard 3 just keeps nagging to upgrade to pro....

Oh ya you gotta have V3. It doesn't nag to go to pro at all, unless you try to use something that is pro only. But that's easy enough to avoid. I'm sure you'll need V3 to run these. I'm actually thinking about getting the pro version. Drag and drop of automapped parameters in the automap software would be awesome. I could also see the keystrokes being handy learned to buttons on the SL.


Also, if anybody notices an error in a template, I'd appreciate if they'd let me know. What I mean by an error in the map is like if a parameter is mapped to two knobs side by side or something which clearly was an accident. That happens sometimes when you're learning multiple controls one after another. One gets missed and you remap the last one you touched before that.

[Android Bishop]

oooh I like the sylenth one so far
its interesting to work out an automap that makes sense to me and look at how someone else came up with theirs. Many things different, some things the same. I noticed you, like me, have the filter cutoff and resonance mapped out on multiple pages because that shit is handy to have all over

[roach808]

Cheers.



dumb question here, how the hell get these templates to show up in live? I just started using automap like last week. Still wrapping my head around it you know.

[fragmentated]

Just wondering. Are you on a mac or a pc and did you use VSTs or AUs for these.

[glitchrock-buddha]

oooh I like the sylenth one so far
its interesting to work out an automap that makes sense to me and look at how someone else came up with theirs. Many things different, some things the same. I noticed you, like me, have the filter cutoff and resonance mapped out on multiple pages because that shit is handy to have all over

Glad you like it. I'm sure you've noticed that I made each notch select a mod destination where those are mapped to Env/Lfo/Misc mod destinations. I did that by counting how many menu items were in each drop down and setting the max value to that (step of one). Sometimes it needed a couple extra so as not to skip any. The one good thing about the notched encoders is for menu type controls. I'm not sure how you mapped these out, but I think this works well.

And ya, I repeated some filter controls once where I had some extra space. I found that it makes more sense to keep controls of certain types organized on separate pages rather than trying to squish everything on as few pages as possible.

At one point I think I had 6 pages mapped out and completely scrapped pages 3-6 and did it a different way. Actually I think I did that a couple times. It was kind of tricky to get Sylenth1 organized in a way that I liked.

[glitchrock-buddha]

dumb question here, how the hell get these templates to show up in live? I just started using automap like last week. Still wrapping my head around it you know.

You have to load it via the automap software while the SL is in template 38. And of course you have to be using automap wrapped versions of the plug-ins. For example it will say Sylenth1 (automap) in the VST folder.