Your projects will instantiate the automapped plug as long as it's the only One with that vst-id in your scan path.

As I said, I don't rely on the hosts behaviour scanning multiple plugs with the Same vst-id. Every Host behaves different. Sonar x1 lists both in its ui, but instantiated only the first scanned, and x1 sorts multiple Plugin paths alphabetically, which influences the scan order... Cubase lists both vst2.4 when the dll name length is shorter than 9 chars, the automap ones otherwise but can't find a plugs preset anymore then, when the dll name differs from the dll name the presets were made with... 

I advice to copy the Vst2 dlls to their own folder structure, so that these are singletons VST-id wise...

OK I think I understand this now. When I get the device I might shout out for some help But it looks like it will be relatively painless - and usefull - as long as I am prepared and take the neccesary precausions. Excluding the "normal" ones in Sonar seem like a good idea.

Just one final question - is there any issues with automap and 64-bit plugins on a totally 64-bit system with the occasional 32-bit favourite?

With 3.7.4 there was a bug, so that only the last automapped architecture of a Plug worked. With 4 this bug is gone, you can wrap x32 and x64 as you like.
X32 get bridged by Bitbridge in x1. Can't say much though, as I jBridge x32 ugs. There was an Automation  issue with jbridge (Independent of automap, but that had influence on it of course), no probs with 1.4 anymore 

Jackel - AKAI kontrolers are the worst money for features buy. Personally I don't like keyboard action, pure imitation of pads, and definetly - price. For me Novation are much, much better in any aspect. I also have no problems with Automap 4, but I have issue with Nocturn tabletop itself. I have USED Nocturn and sometimes, some knobs response with value jumps. I will try to clean pots, it should help.

adrian4u


Jackel - AKAI kontrolers are the worst money for features buy. Personally I don't like keyboard action, pure imitation of pads, and definetly - price. For me Novation are much, much better in any aspect. I also have no problems with Automap 4, but I have issue with Nocturn tabletop itself. I have USED Nocturn and sometimes, some knobs response with value jumps. I will try to clean pots, it should help.

I agree on features which is why I own 4 novation controllers and only 1 mpd18 which I dont use.  The feel of the mpk series I find excellent including the pitch bend and Mod wheels.  I suppose that is a personal preference but it definately doesnt make up for the shortcomings in integration.  I dig the little things like back lit wheels and wish novation had some of those details sometimes.
 
btw, I love having multiple novation controllers.  I have the zero setup to primarily cover the mixer with effects covered by the nocturn keyboard.   So I can be working with send levels and effect parameters simultaneously.  Its a fun workflow.  I do use the zero for larger effects like a channel strip or long eq.
 
 

Hey!


OK, I ended up taking the plunge today, even though I swore I'd wait until february But here it is, my brand new Remote Zero SL MKII

BUT, I can't get the top row endless encodere to do anything. The encoder rings show the value from whatever is highlighted but when I turn the encoder it self it doesn't do anything. Some plugs have a small jitter on the corresponding control but that's about it. Mostly nothing happens. Faders and the second row encoders seem to work fine. Any ideas what might be wrong? I couldn't get them to work in Live or Reason 5 either - although in Live, I can use them in the non-Automap mode so the hardware seem to be working. I've tried reloading the Automap template, device OS etc but to no avail.

Any suggestions to this?


Thanks

ProjectM


Hey!


OK, I ended up taking the plunge today, even though I swore I'd wait until february But here it is, my brand new Remote Zero SL MKII

BUT, I can't get the top row endless encodere to do anything. The encoder rings show the value from whatever is highlighted but when I turn the encoder it self it doesn't do anything. Some plugs have a small jitter on the corresponding control but that's about it. Mostly nothing happens. Faders and the second row encoders seem to work fine. Any ideas what might be wrong? I couldn't get them to work in Live or Reason 5 either - although in Live, I can use them in the non-Automap mode so the hardware seem to be working. I've tried reloading the Automap template, device OS etc but to no avail.

Any suggestions to this?


Thanks

If you bring up the Automap screen, check how they are set - if you click on a control it lets you set the control range min and max values and the mode each control works in. Try changing those and see if that helps.

Hey Drewfx1!


Thanks for that. Eehh... you wouldn't happen to know they they should be set at? They are in Normal Mode with Min=0, From=0, PointsxSize= 101x1.00, To=100, Max=100

Tried inverting with the same values (inverted of course) and Increment/Decrement mode. No change...

Oh to add to the fun - When in the Non-Automap Mode, when assigning one of the endless rotaries to something via the MIDI remote control thing in Sonar, they work.

Sheesh this is annoying!

ProjectM


Hey Drewfx1!


Thanks for that. Eehh... you wouldn't happen to know they they should be set at? They are in Normal Mode with Min=0, From=0, PointsxSize= 101x1.00, To=100, Max=100

Tried inverting with the same values (inverted of course) and Increment/Decrement mode. No change...

That's odd. I would think those settings should do something. What are they set to control?

Maybe compare and match all of the settings to be the same as a control that's working (you can assign 2 controls to the same thing)?

you wouldn't happen to know they they should be set at?

You can play with those things to get different behaviors - for instance a button can be set up as on/off, or momentary, or to step through values, and stuff like that.