LogicPro X + Native Instruments Massive?

As the Novation community has developed over the years, it has naturally found the bulk of it's voice on Social Media. To ensure we can be there to discuss and support you as best we can, we’ve decided to close the forum.

The conversation isn’t over, though. We’re waiting for you; come say hi.

Also, be sure to check out some of our friends.

As ever, thank you for your support.

Thanks for reading, The Novation Team

If you're having a technical difficulty, get in touch via http://bit.ly/NovationSupport and our technicians will get back to you as soon as they can!

9 posts / 0 new
Last post
tbarbe
Offline
Last seen: 3 years 1 month ago
Joined: 02/12/2014 - 13:09
LogicPro X + Native Instruments Massive?

Hi

Just got my Zero SLMkII -- and now Im starting to see that LogicPro X is possibly not well supported since it has its own internal mapping set up and Im not sure what to use - autoMap? or LogicX mapping stuffs.

 

Can anyone comment on how they are using this with LogicX or not? or any comments on best method to get my Massive synth mapped?

I didn't install the latest Novation USB drivers 2.4.8 - because the last upate was so long ago that I felt like they might not even be proper for the latest OSX 10.9.1 at this stage..

 

did I just pick up a device thats no longer really being supported? or can anyone else comment to their using this ok with latest set ups?

 

doh.

 

 

tbarbe
Offline
Last seen: 3 years 1 month ago
Joined: 02/12/2014 - 13:09

Ok! just called Support and they had a beta AutoMap for me!  :) woo hoo... awesome... trying soon - will report back.

tbarbe
Offline
Last seen: 3 years 1 month ago
Joined: 02/12/2014 - 13:09

ok I got beta automap installed... it seems to work!  only complaint is how long now it takes to launch LogicX - the loading of plug-ins and I guess its binding maps to all the plug ins... now logic takes a long time to boot... I wonder if there is a way to reduce this time.

 

Im also wondering as to setting up manually using midi control vs using auto-map.... anyone try it either way to compare?

skijumptoes
Offline
Last seen: 1 year 5 months ago
Joined: 03/26/2013 - 13:22

It shouldn't slow Logic X down too bad, only the first time you rescan the plugins if you've wrapped them.

If you don't want to use automap then just turn it off and assign using the plugins built-in midi learn controls, or Logic's smart controls.  The SL's are very flexible like that.

And yes, still works fine, but i would imagine that Automap will be replaced in the coming years.. But that won't stop it from working of course, no one will smash your door down and uninstall the software! ;)  

In terms of Automap vs Midi CC's etc. I like both ways of working, it depends what you want to do with it - If you want to do sound design from the front panel, then it's nice to automap and save the settings.  If you only want to tweak Cutoff/resonance etc. then it's easy to turn automap off and use the built in DAW/Plugin midi learn functions for a couple of knobs in that session.

One thing you need to be wary of is that if you unwrap a plugin and the wrapped version is saved in a Logic project it will not find the plugin if you were to reload that project, and you will lose the presets as you replace it with the standard (non wrapped) version.  So, where possible, try not to always use automap wrapped plugins to ensure that your projects remain future proof.

tbarbe
Offline
Last seen: 3 years 1 month ago
Joined: 02/12/2014 - 13:09

Hey great - thanks for the reply....

I've been digging into midi learn and control surface info in Logic... seems like its powerful enough to handle most of this stuff but I just have to map it out myself.

Good thing to think about in terms of the future proofing of the projects... seems like wrapping the plug ins is possibly not the prerferred way anymore in LogicX

any limitations you have found using built in midi learn? 

( I tried mapping some controller knobs to the LogicX smart controls - but was not successful yet - any ideas on that one? )

tbarbe
Offline
Last seen: 3 years 1 month ago
Joined: 02/12/2014 - 13:09

btw the rescanning seems to be taking place every time I launch LogicX -- this is the 4.8.3beta version of Automap - so not sure if thats expected or some setting I need to tweak...

 

 

skijumptoes
Offline
Last seen: 1 year 5 months ago
Joined: 03/26/2013 - 13:22

Limitations in using midi learn for me are:

1. Can't use the transport controls on my SL without having to go back in to automap mode, although pressing 'r' on computer keyboard starts recording so it's not such a biggy really! :)

2. Those little lights around the rotaries don't move when i'm playing back automation (Damn! Is that not what sold me on getting an SL!?) ;)

 

The positives of not using Automap are:

1. Future proofing my sessions - If Novation made it clear to customers what they plan for Automap, and whether it will evolve into something like inControl which doesn't need wrapping i wouldn't mind using it, right now it does concern me - Main reason is that i use my mac professionally for developing so i have to ensure it's up to date - Not always the best thing to do with an Audio setup, most swear by sticking with what works and not to update unless necessary.  If i done that, then Automap would be fine for years and years.

2. Sometimes Automap can be controlling a plugin when you don't realise, so many times i've moved the faders thinking i was in mixer mode and it's messed my patch settings up.

3. I can map to plugin patch selection buttons at times when Automap refuses to, this is important if you want to flick through presets via the controller.

 

Logic X smart controls:

It's easy, just pop the controller out of automap mode, then map the parameter mapping to the plugin first (This is usually done by default with Logic's built-in instruments etc. but you may wish to change them to what you want.)

Then map each control to your SL by pressing the External Assignment LEARN button, click a control and then move a rotary etc. And do it for each control on the smart control display... Very quick to do.

Shut the learn button off when you're done of course.

Basically, Parameter map is from the smart controls to the plugin, and External Assignment is your map from the smart controls to midi controller.

The best thing about smart controls, is if you use them in conjunction with Logic track stacks, as you can have multiple instruments and/or effects going into a single smart controls. For example, you can have a smart control set up to bring the volume of a sub oscilator, or reverb effect that's not the main instrument.  As they are track stacks you can actually affect an instrument which is changing a different melody for example.

I've used it before with a pad instrument and had an arpeggiated lead on top, and was able to affect how much of the mix of the arp sound (on a seperate plugin) was included via the smart controls.   Jeez, i hope that makes sense lol

So, yes you're right Smart Controls are actually more powerful due to the integration across multiple instruments/effects/plugins at once. 

 

Rescanning plugins:

Go to Preferences panel of Automap, And in the bottom right corner is a tick box 'Use Logic 64 Bit friendly audiounits'  - Tick this, and it will probably sort the rescanning issue you have.  Mine's been ticked since using Logic 9, and i've never had a problem with rescanning plugins.

 

tbarbe
Offline
Last seen: 3 years 1 month ago
Joined: 02/12/2014 - 13:09

You rock man... thanks - Im going to try some of this stuff now.... hats off to you for the kind info and advice!!

Ill let you know about the use 64bit friendly check box... :)

 

tbarbe
Offline
Last seen: 3 years 1 month ago
Joined: 02/12/2014 - 13:09

awesome!  after checking this box... then restarting automap and the logic project -it loaded one last time and then afterwards was able to boot without this massive loading time.

 

:)  thank you skijumptoes