Jump to content

how to make learned assignments project specific?


Ben Young

Recommended Posts

Controller assignments are system-specific, in the main.

 

It ,may be possible to use regular MIDI commands and process them with the environment in some cases, but if it's definitely controller assignments you want, they are global...

Link to comment
Share on other sites

For example???

 

for example, I want to assign the knobs on my korg nanokontrol to various settings in ultrabeat for one project, but to different settings in another project. I know I could change the scene, but that is a hassle, and I would like to be able to change the different parameters without changing scene/reLearning controls everytime I change projects.

 

thanks

Link to comment
Share on other sites

For example???

 

for example, I want to assign the knobs on my korg nanokontrol to various settings in ultrabeat for one project, but to different settings in another project. I know I could change the scene, but that is a hassle, and I would like to be able to change the different parameters without changing scene/reLearning controls everytime I change projects.

 

thanks

 

Change the scene? I use the Zones/Modes and have yet to leave scene one. Well, I did use scene 2 once for some expanded features.

 

Once you get used to this concept, your nanoK will have endless possibilities.

 

 

 

For example:

 

http://www.logicprohelp.com/viewtopic.php?t=55301&highlight=nanok

Link to comment
Share on other sites

thanks for the responses so far. I'm really frustrated and confused about this, so I'm going to take a break and try again later.

 

I don't know if I clearly explained what I want to do, so I'll try to give a more concrete example:

 

say I have two projects, named Hip Hop and Glitch.

 

in each project I have an instance of ultrabeat. In Hip Hop, I want to control the volumes of 9 samples using the faders, and the panning of 9 samples using the knobs. But in Glitch, I want to control the volumes of 18 samples using the faders and knobs.

 

I hope this makes it clear. Sorry for my ignorance, I'm new to mac/logic and not extremely experienced with DAWs in general.

 

thanks

Link to comment
Share on other sites

As I said, you can do this with the environment - rig up some faders, set their input conditions to match the MIDI you are sending from the knobs, cable them to your UB software instrument, and set the output definitions (or transform them) into the necessary fader events to remote control the instrument.

 

The environment stuff is project specific, so you can set up different routings and environments for each project.

 

Controller assignments in general are intended for setting up your control surface to work with Logic, and this is a system-wide thing. What you want to do isn't unreasonable, but Logic's control surface settings are not really designed for it.

Link to comment
Share on other sites

As Shiver said, you can do that using zones and modes. This allows you to record different collections of assignments. You could have one collection called "Glitch" and the other "Hip Hop".

 

Heck if you wanted you could even have 3 collections called "Hip Hop tracking", "Hip Hop Sound Design" and "Hip Hop Mixing", with different assignments for different phases of the song's production.

 

So in reality, the flexibility Logic offers is more than what you're asking (one collection of assignments per project). The downside to this is, it's not automatic, you have to manually create the zones and modes and manually switch them. Enter Beej's solution: using the environment, which will give you an automatic project specific mapping that will work as soon as you open the project - no need to switch anything.

Link to comment
Share on other sites

Controller assignments have one other downside imo - they are not that reliable. I've documented many many bugs*, some minor, some major, and it's very easy to lose all your assignments with a wrong keypress.

 

If/when they work as expected, there is a lot of functionality there, but they do require some futzing and aren't the most transparent or easily grokkable implementation around.

 

Real world situations has you probably using a bit of both methods, depending on your requirements. Remember to regularly back up your control surface prefs though, if you don't want to lose them.

 

* To be fair, I haven't rechecked them in recent Logic versions as I got too depressed waiting years for new Logic versions, checking out the behaviour, and finding out the identical bugs were still there version after version. So some of them may have been addressed. Perhaps.

Link to comment
Share on other sites

thanks for the responses so far. I'm really frustrated and confused about this, so I'm going to take a break and try again later.

 

I don't know if I clearly explained what I want to do, so I'll try to give a more concrete example:

 

say I have two projects, named Hip Hop and Glitch.

 

in each project I have an instance of ultrabeat. In Hip Hop, I want to control the volumes of 9 samples using the faders, and the panning of 9 samples using the knobs. But in Glitch, I want to control the volumes of 18 samples using the faders and knobs.

 

I hope this makes it clear. Sorry for my ignorance, I'm new to mac/logic and not extremely experienced with DAWs in general.

 

thanks

 

Using one NanoKontrol is going to force you to push a button to change something no matter what, so you have defeated your purpose anyway.

 

The answer is clear. To save you the time and trouble, get an additional nanoK.

 

There is your 18 faders/pans/mutes and solos. That is equivalent to having two scenes without switching.

 

Having two can open up an entirely new world for you using either the environment or the CS assignments.

 

I am not even going to mention what the nanopad can do.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...