u-he

savantgarde · Post by **savantgarde** » Tue Jan 24, 2012 7:30 pm

It seems that Automap 4 can't correctly detect when a new preset is loaded in Zebra 2.5.2. Is this a known problem?

xh3rv · Post by **xh3rv** » Wed Jan 25, 2012 2:37 am

It's been mentioned before, dunno if it's still on the radar though.

http://www.kvraudio.com/forum/viewtopic ... ht=automap

Parameter blindness happens with a lot of plugs other than u-he's, there's some dancing required for Automap somehow

savantgarde · Post by **savantgarde** » Wed Jan 25, 2012 8:14 am

Yeah, I noticed the thing about controller positions not getting updated upon patch change, which is a problem U-He shares with at least ValhallaDSP. However, I was specifically thinking of the patch itself. Automap tracks the currently loaded patch, but doesn't realize when a new one has been loaded (unless you re-open the host).

From what I understand Automap can save controller maps per patch, so considering Zebra's semi-modular nature, this ability would be highly welcome.

xh3rv · Post by **xh3rv** » Wed Jan 25, 2012 9:30 am

savantgarde wrote:
From what I understand Automap can save controller maps per patch, so considering Zebra's semi-modular nature, this ability would be highly welcome.

Automap can use different maps for each instance of a plug, but doesn't automate anything like that. Aside from a default per plug, maps can only be saved and loaded manually (this turns out to update parameters as well, so reloading a default map can help after a preset change). I *wish* something like Zebra's semi-modularity was handled smartly by Automap grumble grumble grumble. Zebra's XYs can help a lot though.

savantgarde · Post by **savantgarde** » Wed Jan 25, 2012 9:39 am

Ah, maybe I should turn to loading maps myself when loading a new preset. It's not perfect, but should meet my needs re semi-modularity AFAICT.

u-he

KVR Audio

Automap 4 can't detect Zebra preset changes