Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Automation Problems

I've been working my way through the Apple Pro Training Series and have run into a roadblock. I searched the forum and did find some suggestions to earlier similar questions, but nothing quite fits (and the solutions found by others don't seem to apply here).

Briefly, I can assign automation quick access to the mod wheel on my keyboard - and the little box comes up saying 'assignment learned' - but no matter what I've tried, the mod wheel will not input automation information on any track for any parameter. Everything just stays exactly as it is when it started and nothing changes. [Auto set to latch, all the parameters checked in the automation window.]

I don't know if it matters, but I'm using a Yamaha S90ES as the control keyboard through a MOTU micro express into the computer.

Any suggestions would be greatly appreciated.

Paul

2.0 InteliMac 2mb ram, Mac OS X (10.4.6)

Posted on Apr 30, 2006 2:11 PM

Reply
12 replies

Apr 30, 2006 7:21 PM in response to Paul Lowden

That's weird... wondering how your keyboard could possibly be sending System Reset in response to the mod wheel. User uploaded file But in any event, that message is the problem.

If you've moved the Mod Wheel, you should see something similar to:

Control Change Ch 1, 7, Lo7

I suggest trying to program it again using the usual method: click on "Learn" and move the mod wheel. Then, click "edit" and see what controller message was recorded.

If you get the same response, experiment with the following: try another controller, i.e., sustain pedal, pitch bend, even a note. See if any of those will "stick". Lemme know what happens.

Apr 30, 2006 8:04 PM in response to iSchwartz

Okay, the info that goes in is the following:

Control Change Ch 1, 1, Lo7, System Reset, 0, 0, Program Change Ch 5, 0, 0, 0, 0

With those parameters, no changes are made to the selected parameter (volume, as it happens) no matter what I do with the mod wheel. [BTW, I've now tried it with two different keyboards, to the same result.]

iShwartz, thanks for you help up to now. Any more suggestions?

Apr 30, 2006 8:09 PM in response to Paul Lowden

One correction to my above post... my example shows MIDI Volume (CC#7), not modwheel (CC#1).

Anyway, there's something seriously weird about your situation.

Try these things:

1. With Logic still up and running, switch your MIDI interfaces on and off, and then go into Logic Prefs and check "reset MIDI drivers". Then try the Quick Access assignment again.

If that doesn't work...

2. Shot in the dark: Do you have any other MIDI instruments' outputs connected to inputs on your MIDI interface? If do, disconnect them or turn those units off. Then, with only your one keyboard connected to the MIDI interface, repeat step 1.

If those things don't work, I hate to say it, but I don't know what else to advise.

Apr 30, 2006 9:02 PM in response to Paul Lowden

Okay, problem solved.

What I was doing when the dialogue was wanting to 'learn' which controller I would be using was give it a very healthy turn - all one way and then the other. Don't do that.

What Logic apparently wants is the lightest of touches to indicate which wheel or button or key. Land like a butterfly with sore feet, in other words.

That way, the controller provided the correct amount of information and the quick access automation worked as advertised.

Thanks, iSchwartz for your assistance.

Paul

Apr 30, 2006 9:12 PM in response to Paul Lowden

Not that it will help but I have run into the same roadblock as you. Logic says

command learned, yet nothing changes. I finally gave up because I think it

has something to do with my keyboard. I have a fairly old Roland U-20. I

thought it could be how the keyboard is set up, I have tried modifiying the

midi setup but midi is still a foriegn language to me and after tweeking all

the settings the best I know, I still have had no luck. I have heard of people

that have had success though I am not sure with what keyboard or control

surface they used. I am considering buying one of the newer keyboards and

hope that might help though I am not going to spend too much, since I know

that Logics midi interactions with certain hardware and software is sometimes

very finicky to say the least. I have a BCF2000 surface controller that I got to

work great in a Logic Control emulation mode, but after trying to set up

Reason and Logic together (according to a tutourial link posted on this

board), it has gone insane. While trying to get Logic and Reason to rewire

together, Logic started sending non-stop midi commands and the control

surface started acting like it was possesed. I finally had to turn it off and it

has not worked normally since. Even after restoring default settings the thing

does not work. So all I can say is dont give up, but be prepared for anything.

I will post anything I find that is usefull.

Automation Problems

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.