Controller assignments(axiom49) automating mutes assignments get scrambled up?

i have an axiom 49...so when I am in the arrange or mixer window, I hit Apple+L for learn mode. I want to be able to record mute automation realtime using my keyboard as the controller. So I select the mute on track one, the hit(for example) a white key. then go on down the line of tracks and assingn them side by side on my keyboard. so that each key represents the mute of each sequential track...but when i exit the window, like the first 4 or 5 tracks no longer respond and the tracks that do respond, are responding to the wrong keys...like everything got shifted over? does any body have any help on this issue?

Hi Mike,
Have you set the right MIDI channels for the tracks in the inspector? Or are they still set to 'all' (default)?
Deleting the .cs means deleting your control surfaces settings (cs stands for control surfaces).
Also make sure that no CC's are filtered out. See File>Project Settings>Midi>Input Filter.
regards, Erik.

Similar Messages

Learned controller assignments often get stuck in Logic.... (?)

Hey guys, when use hardware controllers for controlling parameters of softsynths in Logic, I find that the software knobs often get stuck while moving them. I can not see a pattern to this behaviour, but it happens if I learn assignments within Logic, or using my Novation remote SL and other controllers with templates.
Is this a known issue. Anyone else getting it?
thanks,
Rob

Yeah the whole controller assignment thing has me
baffled. It seems to be geared towards specific,
permanently installed "control surfaces".
Not really - you can completely create your own multi-layer control surfaces, it's just that doing a complete control surface, with bank shifts for controlling track groups and so on is a fair amount of work, and takes some getting to know the controller assignments window, and the terminology like "modes" and "zones" etc
However, the level of control it gives you is great, and if you want examples, you can for instance load a Logic Control controller surface into Logic and examine the way all it's assignments are configured.
If you want to be more sure you can set up a
transformer object to map midi cc's to your synths.
I find it's way better (for me at least) to develop my own control surface support. I use a Korg MicroKontrol and found the default controller support to be rather clunky and not ideal for me, so I've developed and been refining my own control surface support which suits my needs perfectly. It's takes time and is an ongoing process, but is highly useful.
I just wish some of the flaky behaviour was fixed, but my fingers are crossed for future versions...
In any case, if you want to map a fader to a softsynth parameter, just hit apple-L, click on the onscreen control, and twiddle you fader. Assignment learnt. Do this for the parameters you want, turn off learn mode, and twiddle away with perfect automation.
Don't also forget the automation quick access as well - assign your mod wheel to this, and you can select any parameter of a plug and quickly use the mod wheel to control it or write automation etc.

Controller Assignments fun.....automation controlling the WRONG ch strips!

Hello all,
Further to L8 deleting an entire zone of Controller Assignments and my backups not in fact, having backed up my CA setting, I am rebuilding the Zone.
As a perfect example of just how BAD the CA aspect of L8(.01) remains: I have a brand new environment with 32x Audio Channel strips and 8x Aux Channel strips.
I have successfully mapped controls from my Axiom61 in groups of 8 to audio channel strips 1-8, 9-16, 16-24 but when I do EXACTLY the same thing (learn automation) for channels 25-32 and then exit learn mode, my Axiom is controlling AUX Channels 1-8 and NOT Audio ch 25-32!!!
I mean I have clicked on each audio ch fader (25-32) assigning controls for volume, pan and solo precisely the same as for the previous 24 channels yet Logic assigns these last controls to the WRONG ch strips - ie Aux channels 1-8!
WHY? Pourquoi? Porque? PLEASE!
Is my environment screwed? Is this something to do with L8 deleting my Zone yesterday?
Thank you all....

It depends on how you are learning them. An assignment to a particular channel strip can be done a number of ways - accessing only audio channels, accessing audio objects by an offset, accessing channels based on the current fader bank offset and so on.
What are your assignments set as? If you are assigning them as fixed audio objects, you shouldn't run into this. If you can provide more details as to your assignment parameters, I can have a look and see if I get the same behaviour, or see what's going on.
Note: couldn't you keep all your controller assignments issues to one thread? - it makes it easier to keep track of things and keeps them self-contained with all the relevant info, rather than having related isues split across multiple threads.

HELP! Trashed Controller Assignments - backups? What backups?!

I have read about major bugs in the Controller Assignments/Automation side of L8 (they remain and persist in 8.01 - the version I am using) - bugs such as whole Modes/Zones literally vanishing from in front of my eyes.
Specifically that is vanishing as a result of, for example, being prompted when a control is currently assigned to another parameter and being asked to reassign/cancel etc I click on "reassign" and hey presto, the zone for my Axiom61 has been deleted, along with half a dozen associated modes and several hours of tedious work.
Not to mention that generally working on Controller Assignments has been nothing but trouble from the start, with spurious problems such as L8 just not responding to controls from one minute to the next.
The above disappearing act has happened twice: Both instances occurred at the same kind of "reassign" prompt, though the first time I did not lose a whole ZONE just a MODE within my newly defined Axiom zone.
Anyway, the question is this:
I had understood that I needed to backup two files to protect my Contoller Assignments -
/user/library/preferences/com.apple.logic.pro.cs
/user/library/preferences/com.apple.logic.pro.plist
BUT, having restored these from a backup I took a few hours ago, I find that my Controller Assignments are still absent.
Can anyone help?
Much appreciated in advance.
BTW, L8 is, in my humble view, generally SIGNIFICANTLY better than any previous version. I have used them all.
I just haven't ever set up Controller Assignments. Until now....

Specifically that is vanishing as a result of, for example, being prompted
when a control is currently assigned to another parameter and being asked
to reassign/cancel etc I click on "reassign" and hey presto, the zone for my
Axiom61 has been deleted, along with half a dozen associated modes and
several hours of tedious work.
Yep, I reported that one back in 7.1, and a looong list of numerous other horrible bugs with the controller assignments...
LP8 uses the files you mentioned. LP7 uses the ones in /user/library/preferences/logic/ but it also uses the LP8 main pref plist as well, we discussed this before. It's odd.
In any case, I got very careful about making multiple backups of controller assignments, but eventually I basically mostly gave up with my custom assignments because it was too buggy.
It was the one thing I wanted fixed in 8, and I was very dissapointed.
Oh, I also developed lots of workarounds while tip-toeing around in the controller assignments winodw. One is to duplicate all your commands into different modes, as a backup set without the same controller prefs. That way, if your modes get hosed through this or any other bugs, you can copy them back in from another mode.

Controller Assignments not working

I have 2 midi controllers which I have assigned the endless rotaries and faders to control Logic bundled synths and 3rd party sofsynths.
I have used the learn function to succsesfully control all softsynths with the hardware controllers, but usually when i reopen logic a day or 2 later the assigned functions no longer work. This is perplexing, as all the learned information appears in the controller assignments expert view window.
I am getting relly sick of constantly remapping. Is this a fault in Logic 9 or am I dong something wrong?

Hi did you fix your problem....?

Logic Express 9 doesn't remember my controller assignments

Hi,
I'm using M-Audio Axiom 25 and UC-33e with Logic Express 9. I know how to use the midi learn function, and I'm able to get everything working until I quit logic and open it up again. After that, the previously working assignments won't work, even though logic shows them in the controller assignments window and shows that some midi data is coming in. I've been searching the forum and m-audio forum as well, and they said, that the problem must be with logic. Apparently I'm not the only one with the problem.
However I managed to get the key commands work (with Axiom 25, not UC-33e) by exporting them, but I'd also like to be able to use the knobs etc.

I was never ever able to get Logic 8 to remember my controller assignments for very long or at all. Nor was I was ever able to find a solution to the problem despite all my efforts to try.
My solution was third party. I purchased a Novation Remote SL which uses Automap. As aggravating as it was to have to do this, it solved my problems permanently. Automap is Novation's software that maps itself to Logic as well as to many if not most audio units. It also perfectly controls transport functions without a hitch.
I felt a bit non plused that such a simple feature in Logic was never very reliable. I haven't tried it since upgrading to Logic 9 since I'm still happily using the Remote with Automap. Hopefully someone can provide better help other than simple explaining how to set the learn function up in Logic. The manual explains that just fine. A better explanation as to how to keep it working or get around the bugginess of it would be more useful - and that I was never able to find.

Sharing controller assignments

Hello.
I am trying to figure out if it is possible to export and share the controller assignments I have mapped to a custom interface.
I am using Logic Pro 9, on a MacBook Pro 15" 10.6.3, in conjunction with TouchOSC (running on an iPad) and OSCulator.
The setup is to use the iPad as a touch surface controller for Logic 9. Running the OSC signals sent from TouchOSC on the iPad through OSCulator where you can reroute these incoming signals to MIDI. So I map all of the faders and pots and buttons on my interface to Logic. Save the project as a Template and share the template.
However, the controller assignments do not get saved with the template.
So how do I share my controller assignments? That's pretty much all I want to know.
I have tried the files called something like "user/Library/Preferences/com.apple.logic.pro.cs" but it did not work.

Colin Honigman wrote:
Tried it. Doesn't do it.
Well, the problem seems to be the "floating ports" - have a look at the *IAC Tip*
I show in this topic link:
http://discussions.apple.com/thread.jspa?threadID=2403538&tstart=30
Read it carefully. I recommend just to learn a few assignments first using the IAC bus as a constant port, try to transfer this assignments to the other machine using the IAC setup and if it works (it should be) then re-make all assignments using the IAC tip.
!http://img59.imageshack.us/img59/4967/aglogo45.gif!

Controller Assignments Deleted After Crash

I know this topic was brushed on briefly in a previous thread a while back, but I haven't found any real working solutions to the issue.
I have spent lots of time and labor programming complex assignments for multiple controllers in expert view of the controller assignments window for the various soft synths i use. And then they just get deleted if Logic crashes with no way of recalling them. This is extremely frustrating.
I need these assignments to be permanently saved for the music I make.
I know that backing up the library file described in the Control Surfaces Manual does nothing. I just can't believe there hasn't been a solution/bug fix to this issue. This can be a major issue for a lot of people.
Any ideas?

I've been bitten by this bug many times myself, so I've learned to keep a clean copy of the control surface prefs file on hand so I can just drag it back into place in case of a crash - takes a matter of seconds to be back up and running.
Here's what you do. Set everything up the way you want, then quit Logic. Then create a copy of the control surface pref file and keep it somewhere safe. Next time Logic crashes, drag the copy (actually a copy of the copy!) back into your Prefs folder and you'll be good to go.
The file you're looking for is called "com.apple.logic.pro.cs" and it's in your [user] > Library > Preferences folder.
Hope that helps!

Why doesn't Logic Pro X remember controller assignments when I switch patches?

I'm trying to work with setting up External Controller Assignments with my Akai MPK25. I'd like to have Knob 1 map to the 1st Automatic Smart Control knob I can see (like Timbre or Cutoff or whichever is leftmost) OR have Knob 1 always map to the same paramater (Timbre, Cutoff, etc).
I'm able to successfully set them up on a single patch but the moment I switch to a different patch, Logic completely forgets the assignments. And if then I switch back to the original patch, the assignments are also ost. If I toggle "Compare" in the Automatic Smart Controls window back and forth, Logic loses the assignments. But oddly, it remembers one or two (out of eight potential paramater assignments).
How do I get Logic to remember these assignments?
Here's a screenshot of my window: https://www.dropbox.com/s/uqzqen6etkh0uxf/Screen%20Shot%202013-11-24%20at%205.02 .43%20PM.png
Thanks so much in advance.

No, no need to chase any pur.
You can clickhold that No Output slot and assign an output.
...but for that to work you need to have chosen your audio hardware in the preferences, of course. And while you're at it, make sure you also have all Advanced Tools enabled.

Have the Controller Assignments been fixed?

Ok, while I'm waiting for mine to arrive, if anyone out there is familiar with the (many) bugs in the handling of controller assignments, can they tell me whether these have been fixed in LP8?
Or are the same issues still there?
A reliable controller assignments window is the one thing I've most wanted since the dawn of LP7...
Cheers mateys!

Controller assignments includes quick access, control surfaces and now MIDI key commands in addition to the learn controls functionality. The whole nine yards of wax enchilada balls.
My specific problems relate to th controller learn to plugins functionality, and basic buggy operation of the window itself (for instance, clicking on cancel in one of the reassignment warning dialogs will just delete all of your assignments.)
Ok, here's a long post - I haven't exhaustively through this stuff with LP8 yet (too depressing) but I did verify that the core bad behaviour still exists identically to LP7.x...
Ah slippery haddocks, I would post the feedback I sent to Apple, but I can't find a local copy - I posted it to OSXAudio so I usually retrieve it from there but the site is down at the moment - when it comes back up, I will get it and post it...
As a quick general example, I have eight sliders I want to map to softsynth controls - let's say the GB synths, because they have limited controls. So I open the first one, and map the eight controls to my eight sliders. Cool. Works fine. I then load up the next one, and map those eight controls to my sliders.
This is cool, because whatever GB instrument I load in the instrument slot, my controller will control the 8 parameters I want.
I keep going. At some point (which is random), the odd learned control will just stop working - ie, after I've learned maybe 6 or 7 instruments, a random control on a previous instrument just won't respond. If you try and "fix" it by relearning the control, sometimes it works, sometimes it doesn't. Sometimes it just means other controls randomly stop working.
Worse still, when you twiddle a control to see which parameter it's assigned to, the incorrect assignment is called up in the controller assignments window, so you just don't have a clue what's going on.
There are plenty of others, but basically, setting up controller assignments works for a few simple things, but it corrupts and becomes a major pain very quickly.
It's a shame, because I was developing an awesome controller config, where I had buttons on my controller that would switch modes between mixer, instrument, plugin settings and so on, and I always had the most important parameters of all my plugs under my fingertips.
Except for Logic's randomly flaky corruption which rendered the whole thing pointless (as you never knew what was randomly going to stop working).

Why is my easy view and expert view not showing up in my controller assignments window

when i go to contol surfaces and then select the controller assignments i do not have the option to hit the easy view or the expert view i was wondering if anyone knew why this is?

Same solution as dplavin. Thanks!
Afterwords there were some changes in Add-ons that were enabled/disabled that then had to be straightened out.
I disabled Test Pilot which was in the process of testing thinking that it might have had something to do with the problem. I have not updated to the latest version of 5.0 because one favorite Add-on [Firegestures] is supposed to be incompatible.

How can I save controller assignments with a project?

How can I save controller assignments with a project, so that I can use different controller assignments for the same synth in another project
Let's say I am controlling a Logic instrument with MIDI and CC data sent from MaxMSP. I have created a composition and would now like to make another one, with new assignments of controllers, in a new project. Is it possible to save the first piece's c.a. with it's project, so that I can switch between projects and have the controller assignments switch accordingly? Is that something that's become possible in Logic X with Smart Control or another workaround?
Thanks a lot for any hints!

With standard instruments you can cable transformers before the objects translating incoming cc's to "fader" events.
With the new plug-ins they've hacked into Logic (ultrabeat, sculpture) this isn't possible, so your stuck with the "controller assignments" window which to me seems to be aimed at dedicated control surfaces and autoloads. My experiences with the controller assignments window aren't good, as i've found it drops incoming messages quite often.
Knowing how to do this(controller assignments per song) would give me a reason to open the controller assignments window again..Pretty useless to me otherwise.

Is anyone here fluent in the Controller Assignments window?

I have a Mackie C4 Pro and I built a rather complex environment layer of virtual sliders (that works) for controlling parameters of an external synth not supported by the C4.
I would like to control all the knobs in this particular environment via the C4...however, Logic's implementation of the C4's driver combined with the Controller Assignments window is cryptic to say the least. Despite reading the manual, it still makes little sense as to why things are not working.
As it stands, the mackie C4 has about 50 modes within a particular zone, most of which are usable with the exception of 8 "user" modes.
These 8 user modes are selectable from the C4 itself yet contain no control assignments. Attempting to create control assignments yields no effect on the C4. When I try to apply even a label to my newly attempted controller assignments, the label field resets itself to blank when I switch between modes. As well, the parameter field remains ghosted and uneditable.
Right now all I am trying to do is assign mod wheel control to one of the v-pots under the user mode #1. So far it seems to be resisting any customization.
here is a screen shot of my controller assignments window:
http://dl.dropbox.com/u/10478471/controllerAssignments.png

i did now
its kind of ironic that there's no help available through apple's website for a rather elaborate implementation in their own software...especially when considering Apple wrote the driver for the C4

Why does Logic Pro 9.1.8 Fail to respond to Controller Assignments?

I have recently bought the Akai MPD32 and am currently using it with Logic Pro 9.1.8. I spent 2 hours mapping Controller Assignments to various knobs and sliders e.t.c. and they all saved. I backed up the preference files from the Library in case I needed to replace them for some reason. After a few times of closing and opening Logic the assignments no longer work! They are still displayed in the Controller Assignments window but do not respond to the movements I am making on the controller. I have tried replacing the preference files which doesn't seem to work. All my MIDI devices are connected before I start Logic and the MPD32 is on the same preset as when I assigned the controls.
I was hoping someone could help because I was hoping on an easier workflow but it seems impossible at the moment.
Liam

I backed up all 5 Logic files in the Preferences folder after setting up and assigning the MPD32.
I deleted the files and replaced them with the backups but it still refuses to behave. I had all my midi devices linked to the correct ports and my assignments were under MPD32 Port 1, when the assignments failed the MPD was still in 'port 1'.
This is quite a pain in the backside and I don't want to have to do this multiple times a day.
Anyone got any other suggestions?

Logic keeps losing controller assignments???

I have an Axiom 49 with it's transport buttons assigned to various logic functions. I have assigned these in the key command section by "learn new assignment" Every so often these commands stop working altogether as if Logic "forgets" them. When I look at the learned command line it still shows the assignment but it isn't until I "relearn" the exact same assignment that it works again. This is extremely frustrating. Does anyone know why this happens and if there is a workaround? Thanks.

don'tforgetyourtowel wrote:
This may work for your controller assignment issues. I haven't tried that specifically but it definitely works for solving problems with midi ports changing depending on what you have hooked up when you boot Logic.
The CA (Controller Assignments) are "Pre", regarding the Logic Physical Input in Click & Ports layer, so this will not solve the "Input Floating Ports" problem I guess... I think a little tip using IAC bus can work cause once IAC is activated it is a MAC constant virtual port.
*The IAC Tip*
1. Cut the "Sum" cable from the Physical Input and cable the IAC (Bus1) port to the Monitor object (1) - see the pic below. You can name the Monitor (IAC Bus1 IN) etc.
2. Cable all physical ports to the "Sum Physical Ports" Monitor object (2).
3. Create an Instrument object (3), assign its port to IAC, set its midi channel to "All" and cable from "Sum Physical Ports" Monitor object (2).
4. Create a new Fader in the Environment and cable it to the IAC Instrument as shown (4).
5. Move the fader of your external controller you plan to learn to see what is its CC# and channel# in the "Sum Physical Ports" Monitor. (You can skip this step if you are familiar with the physical fader/knob hardware CC assignment previously).
6. Select the virtual fader (4) labeled as "Temp Learn" in the environment and set its output CC definition number and midi channel to match your external controller you plan to learn in the inspector.
7. Save your new midi setup as a Logic template song.
8. Press (Command+K) to open the Logic CA expert dialog. Do the standard "learn" procedure to learn any channel strip or plugin parameter but instead of moving the external controller fader/knob you must move the virtual environment fader labeled as "Temp Learn" (4). This way Logic CA will be learned from the IAC bus (you will see that in the CA expert dialog). After this "Dummy" learn process you can tweak the physical controller - done!
The method must solve the "Input Floating Ports" problem cause all CA assignments will be learned from the IAC port which is constant (non-floating until you may decide to switch it OFF in the Mac AMS).
The other good side is if you decide to move your Logic Preference file ( i.e CA) to another machine - all assignments must work this way ( I did not try yet but in theory it must work ).
Another advantage is that you can patch lots of interesting "Transformer Gears" between the "Sum Physical Ports" Monitor (2) and the Instrument IAC port (3). In other words you can use the Logic Environment as an advanced "MIDI JUNCTION" engine serving its midi processing to other apps, CA etc...
!http://img714.imageshack.us/img714/5460/iacca.gif!
!http://img59.imageshack.us/img59/4967/aglogo45.gif!

Controller assignments(axiom49) automating mutes assignments get scrambled up?

Similar Messages

Maybe you are looking for