Logic Control Track Lock

I do not want the Logic control to follow selections in the arrange when I select tracks in Logic. The manual says that if I turn Track Lock on, then track selections in logic will not effect the logic control, but it makes no difference when I turn it on. Is this a bug or am I missing something. I have 3 xts and I want them all to never change fader groups.

But LC does not relate to the Environment audio mixer, it relates to the Track Mixer. If you want your audio mixer in the environment to relate to LC, you''ll have to arrange the objects to match the track mixer.
BTW an easy way to make sure the track order matches the order in your environment is, when you set up the song, select and drag all the audio objects in the environment into the tracklist. (drop them on Track 1)
Generally this is only a good idea at the start, before you have any regions in place in the arrange tracks, as, if you do it when you have content, the audio in the tracks will be assigned to different audio objects to what they were originally. (Although, you can get around this, by cutting all the track content then changing the order, as I described, then doing: 'paste at original position' and select 'keep Inst.' in the dialog which follows.)

Similar Messages

Logic Control Selecting Hidden Tracks/ Don't Want That!

i'm mixing and i have alot of hidden tracks. i only want logic control to select tracks that are on the arrange page. is this possible?
thanks

Sorry but I've never come across a way of doing this (I use a different control surface but the software principles still apply). I don't believe Logic is flexible to report hidden tracks to the control surface interface and there's nothing about it in the Control Surfaces manual.
Quel dommage...
Pete

"Hide" feature DOESN'T Hide tracks from Logic Control

Okay, so this has been driving me crazy ever since the implementation of the "Hide" feature. No matter what tracks I hide, they are still cluttered on my Logic Control. I was told way back when that this was supposed to be fixed by now........needless to say it's not.
My Arrange is nice and clean and organized for mixing, but my LC still shows those "hidden" tracks causing time consuming sifting through pages of unusued MIDI tracks/etc. How do any of you work around this?
Thanks in advance,
M-De'
www.nbth.com
G5 Quad Mac OS X (10.4.8) LogicPro 7.2.3

Well....i did figure out a sort of "work around" for the problem that helps. When you're getting ready to mix or frankly, whenever you'd like......if you put a stack of "No Output" objects in between your MIDI and Audio tracks you want Hidden then it kinda helps. At least it gives you an artificial separation of sorts in that when you flip through the pages it's easier to tell we're you're at. But indeed, this is a lame bug.
M-De'
G5 Quad Mac OS X (10.4.8) LogicPro 7.2.3

Keystation Pro 88 (or other controller) as the Logic Control

Has anybody got their setup like this? I've been trying to get this to work for the past 6 hours and no luck. Can someone please help me? Just bought Studio 2 days ago and haven't touched it yet cuz I can't get the keyboard to fully work.
Joined: 17 Jan 2006
Posts: 55
Location: Los Angeles
Posted: Sun Jul 15, 2007 12:03 am Post subject: Keystation Pro 88 (or other controller) as the Logic Control
I'm sure some of you already know how to do this. I just figured I'd write this up at some point to share with others. The basic idea is to use the Keystaion Pro 88 (or some other MIDI Controller) as an actual Control Surface, or in this case the Logic Control, to have more freedom with the MIDI Controller, i.e. using the group of 8 faders (on the Keystation) to control Volume for tracks 1-8 in the arrange window, and then hitting Bank Right to automatically control tracks 9-16, and as a result making a universal controller not bound by specific channel messages, or MIDI CC Volume messages etc... in short the essence of any Control Surface.
What I'm describing below is what this app will also do: http://www.opuslocus.com/lcxmu/index.php
I basically just wanted to avoid using a separate application all together. Keep in mind that the app does simplify the whole process, but Logic inherently can do pretty much everything the app does.
I recommend reading this in its entirety before attempting.
KeyStation Pro 88 as Logic Control
Part One: Add Logic Control as Control Surface
1. Open Logic.
2. Preferences / Control Surfaces / Setup...
3. New / Install / Select your preferred device (in my case Logic Control
4. Click the icon in the setup window for the Logic Control.
5. On the left hand side under "Logic Control" you should see an "Out Port:" and "Input:" ... select the desired MIDI in/out through which your device is connected.
6. Open Preferences / Control Surfaces / Controller Assignments. Make sure you select the "EXPERT VIEW" check box.
7. You should now see a bunch of different Zones in the Zone column, one of which is "Control Surface: Logic Control"
8. Create your own Zone, KeyStation Pro 88 (or whatever) using the Plus sign in the bottom left corner of the Controller Assignments window.
9. Now basically go through the existing parameters already available in the Logic Control Zones, Select what you want. You can select entire Modes or individual Controls / Parameters. You can select multiple values (only multiple Control / Parameters NOT modes) by selecting and dragging or simply with select and holding command.
10. Command-C the selected Modes and then click back onto you user zone that you created above.
11. Click inside the Mode column (or Control / Parameter column depending upon what you selected and copied from the Logic Control zones).
12. Command-V to paste the Modes into your user Zone.
13. Do this for as many Modes / Controls you want, that your specific MIDI controller interface will be able to handle.
Part Two: Assigning Input Values
1. Open Preferences / Control Surfaces / Controller Assignments
2. Now for each parameter that you copied, you will need to set the input MIDI value from your controller.
3. Click on your User Zone, then Mode, then the first parameter in the 3rd column.
4. You should see a "MIDI Input" option (this should already be set correctly as long as you set it earlier in Step 5 of Part One). If it's not set to the correct MIDI input (which I found to be the case sometimes even after Step 5), then change that here.
5. Next to "Value Change:" you will see a box with MIDI data in it. Delete the existing date by highlight and delete.
6. Activate "Learn Mode" (bottom right corner of Controller Assignments window) then click within the "Value Change" box, then move the corresponding fader, button etc. The "Value Change" should now show the MIDI data value for that fader. Be careful here, there should only be 3 groups of 2 for data here... if you see 2 groups, of 3 groups, of 2 then typically the FIRST group of 3 should be the value you want here. You can always delete the data, and move the fader again to be sure. The reason for the 2 groups of 3 is not in error: some buttons send TWO MIDI values, one on press and one on release. You can use this to your advantage and assign TWO different functions to these buttons, thus the first (press hold) value can do one thing and the second (release) value can do another. You can also change the MIDI controller to only send 1 message on press and nothing on release, or simply make sure that only the on value is present in the "Value Change" box.
7. You'll have to do this for all the different knobs / faders etc. on your MIDI controller. There are many shortcuts of course. You can manually type in the Values if you know them. For the Keystation Pro, M-Audio has an app called Enigma that I recommend for changing controller parameters and much more on the Keystation. You can use this app to assign all the actual control data that each button or fader sends to the sequencer, once you know the values you can convert that data to the MIDI data values and enter them into the Value Change box.
8. Once you're done assigning values to the controllers, you can delete all the Zones except for the user Zone you created earlier. Before you do this, it's a good idea to back up the Control Surface preference file just in case you ever want to grab something else from the Logic Control Zones. You could always add a second Logic Control and copy the Zone from that, but you'd have to reassign all the MIDI Input: values ... short version, just back up the preference file before you delete the Zones. The reason why you want to delete the Zones that you're not using is simply because if you have a controller that happens to send out MIDI data to the sequencer, and the actual Logic Control happens to have that MIDI data value already inherent it it's Zones, then you could be asking for trouble, simply put you'd be sending MIDI data to change Volume and the Logic Control maybe has that MIDI Data Value already assigned to Pan for the existing track.
The file to backup is located here: ~Users/username/Library/Preferences/Logic/com.apple.logic.pro.cs
As a precaution I have always backed up my Logic Preference file WITH this .cs file. Technically it's not necessary... for instance: Let's say you trash your preferences and open Logic to find that the Logic Control is missing from the Control Surfaces Setup. So you add it back and now you find out that Logic is missing the User Zone that you created. If you close Logic and copy the .cs file back to the directory above, then upon reopening Logic you should find your User Zone is in place again. But I've had mixed results with that, so just in case I copy over the preference file with the .cs file as a pair. It seems that the Logic pref file only contains information that the Logic Control is a Control Surface on your system and the .cs file is the preferences for that specific Surface.
Another note: after a recent Logic update, maybe 7.2? ... it was whichever update added support for more Control Surfaces, I can't remember. This update basically erased all the hours of hard work linking the Keystation to Logic as the Logic Control. This only happened with this specific Control Surface update, but not with 7.2.3, probably simply because they didn't make any changes to the .cs pref file.
Anyhow, when this happens again in the future, there seems to be a quick fix. I take NO responsibility for you somehow crashing Logic on a continual basis after applying the fix. Personally I have seen NO issues by doing this at all. I simply copied a version of the .cs file with the new update missing the Keystation Zone, as well as a version of the .cs file WITH the Keystation Zone, to a PC (I think it was a PC, don't believe I tried it with textedit, although should work as well). I opened both of the files in notepad and compared them. I noticed the word Keystation towards the bottom and realized that most all the data (gibberish) was exactly the same up until a point in which the file with the Keystation data had a group that was absent from the new .cs pref file from the new update. So I basically copied the data from the old .cs pref file, pasted it into the new .cs pref file, saved it and open Logic. Logic warned me that a pref file was corrupt or something of that nature, but loaded fine anyway, and the Keystation Zone was back in Controller Assignments.
One last thing... the problem that some of you may run into is that by making your MIDI controller a Control Surface, or turning your Keystation Pro into a Logic Control, limits some of the functionality of the MIDI Controller. For instance, a Logic Control's main purpose is to control different faders, knobs and what not of MANY different tracks. When you move a fader for volume on the Logic control, it will move the fader corresponding to the selected track... it's not programed to say change the actual midi CC 7 for Volume, only the actual Fader. Thus, what if you want the MOD wheel to still control modulation and you want the sustatin pedal to continue to act as a sustain pedal. Well, if Logic sees that Port 1 is the input for the Logic Control, but in reality the Keystation, then it's only going to allow specific events through. The way around this issue is by using both the input options that the Keystation has... hook the MIDI out into Logic and use the USB port as well. I run the Keystation as a Logic Control through the USB port, and use the MIDI out for actual MIDI data. But the catch is you have to make sure you only connect the MIDI Port into Logic's sequencer in the environment. Thus open the environment, open Clicks & Ports, Port 1 and Port 2 are the IN/OUT for the USB port. Midi Port is the Keystation's MIDI port. Select and delete the cable for the SUM, and run individual cables for the ports you want to use. Thus, all your other MIDI interface Ports, the Caps Lock keyboard etc. Just be sure that if your using Port 1 (USB Port Out from Keystation) for the fake Logic Control, that it DOES NOT cable into the "Input View" or "to Recording & Thru". This creates yet another issue:
The controls on the Keystation have to send SOME form of MIDI control message / data to Logic. Well if the faders on the Keystation are preset to send Ch1-9, Volume 0-127 messages, then when you move a fader on the Keystation (as the Logic Control) since the Keystation is still reaching the sequencer from the MIDI port, you will be sending MIDI values that can effect your current track possibly when you don't want to. The work around for this is to be sure that all the faders / knobs that you want to use as your fake Logic Control are sending useless MIDI data... i.e. CC 75, 76, 77, and so on. This way moving faders won't effect playback, although you could still in theory record this MIDI data into your sequencer. You could however filter this events from entering the sequencer input with a transformer since you know precisely what MIDI CC values you are changing. The easy way to assign these values is to use the program Enigma from M-Audio that I mentioned above.
More discussion specifically related to the Keystation Pro 88:
You can do a lot using the Controller Assignments and different Zones from the Logic Control. For instance, the real Logic Control has Solo, Mute, and Record buttons for the 8 faders. The Keystation Pro only has 1 button underneath each fader. But you could use one of the other buttons to toggle Solo, Mute, and Record mode so that depending on which mode your in, the buttons underneath each fader will correspond to Mute or Solo etc. By the way, a good setup from my experience is to use the first 8 faders of the Keystation as the track faders, and the final 9th fader for Master Volume. You can then set two of the buttons underneath the Knobs as Bank Left and Bank Right buttons to change the 8 fader tracks to correspond to the onscreen track groups of 8. Also don't forget that you can assign TWO functions to EACH button, since a button press can send a value of 127 and a button release can send a 00 value. So if you press and hold a button it can activate "Shift-select Mode" and until released it can make the buttons under the faders act as Volume to Zero resets or whatever you want. When you release the button it will go back to just Mute mode or Solo mode. The Controller Assignments window has MANY options, and parameters some of which are very confusing and take a lot of trial and error to understand... the manual helps a little but of course isn't perfect.

I'm thinking about buying a Keystation Pro 88 (2nd hand) so I was googling around and found this:
http://www.soundonsound.com/sos/Oct04/articles/keystation.htm
[quote]
I had some trouble getting the transport controls to work with Emagic's Logic, even when I loaded the 'Pro 88 Logic Preset.LSO' file on the supplied CD-ROM into Logic. I contacted the guys who designed and set up the Keystation here in the UK at the old Evolution offices, and between us we managed to work out what was going wrong. First of all, you need to enter the appropriate MIDI key commands in Logic's user preferences. These cannot be updated with an LSO file, so the commands have to be entered using the Learn Key function in Logic (see the screenshot below for the list we used). Then we discovered that the transport keys were toggling, which meant that only each second press of each key was actually working. It turned out that I had an early version of the Logic preset before this had been fixed, but the more recent one has been put on the M Audio web site for anyone else that needs it. It took about 30 seconds to change the output commands so that the buttons were no longer toggling.[/quote]
Did you get it to work correctly eventually?

BCF2000 - assigning within Logic Control Mode

I am using a Behringer BCF2000 with Logic 7 Pro on a G4 powerbook. My BCF2000 is working fine in Logic Control Mode (USB Mode U-3), what I would like to do is add a few of my own parameters, mainly logic's tape delay feedback (as I make dub) to one of the dials, for example.
Also I would love to be able to trigger a few sound effects (maybe an exs patch) using an assigned button, for those on-the-fly dub vibes.
I sussed the patch editing and storing in the normal factory mode, but in Logic control mode, I can't seem to create my own patches and store them. Is this possible? and if so, how can I "learn" the functions like tape delay feedback.
Any help would be greatly appreciated! Thanks guys!
Ben (Brazil)

I sussed the patch editing and storing in the normal
factory mode, but in Logic control mode, I can't seem
to create my own patches and store them. Is this
possible? and if so, how can I "learn" the functions
like tape delay feedback.
Any help would be greatly appreciated! Thanks guys!
Ben (Brazil)
I have not been able to program mine in LC emulation
though I have been able to program the other presets.
Something I have not tried yet is trying to program the
many parameters in the controller assignments window.
I have discovered that by having the BCF in LCmode
going to the Controller Assignments window and
selecting expert and follow then clicking on
the different modes and such that the BCF
responds to what you are choosing on the screen.
I have not had the time yet to confirm this but
I believe the BCF is already preprogrammed to
do many of these in LC emulation. For example when I choose
track on screen the BCF would change its display
to "tr" and so on. This is a big discovery for me since
I new that in LCemulation the Unit was capable of
accessing all or most of what a Mackie Logic Control
unit could. I could never figure out how to get to those
parameters. This is one way to figure it out I suppose.
Behringer suggests that you read the docs for the Mackie,
I have not found this to be too helpful yet. Hope this helps.

Emagic Logic Control jog wheel...

My logic control is was working fine; and then poof - No v pots and no jog wheel - mackie suggested i delete a preferences file; which has bought my v pots back to life...However the jog wheel and the timeline still misbehave...
The line skips back and forth between a couple of bars...and moves forwards jumping backswards and forwards if i spin the wheel really quickly...if, when the line is further into the track i move the jog normal scrolling pace it runs the line backwards towards zero; speed it up and it jumps all over the place.
I rang apple but the wanted to charge me £144.99 for phone advise - so im begging someone here to help me if you can...
Many thanks Dave

its not showing in my audio midi set up - but never has previously...but the device it connects via does show up - From what was said in the quick start guide, you only have to add it as a control surface within logic...Where logic already has the relevant driver; waiting to be selected from a list...As for updating anything; I havn't touched a thing. It was literally a case of one day, everything worked; the next day it didn't - mackie said logic had made a corrupt preference file (user/whatever your user nameis/library/preferences/logic) that their would be a file named should be something like
(Com.apple.logic.pro.CS) which there was, and to drag the file to the trash then restart the
computer...This did work to an extent; the 'v-pot' part of the control which had stopped working came back to life and everything now works fine...accept the jog/timeline issue...
I have added it in Audio Midi set up...in the hope that it will help - What properties should I set it to have? anything special - Appologies for seeming dense, I just make music; normally things just seem to have worked! And my technical knowledge is somewhat lacking im affraid.
Thanks for your help - it really is appriciated
Dave

Logic control/BCF2000

hi
I'm using a Behringer BCF2000 in Logic Control emulation mode. So far almost everything is ok. There's one problem: if I shift the faderbank by one step to the next bank (that would be the next group of 8 tracks), the fader one on the BCF is controlling track 10 and not as supposed, track 9. I can change the Mixer View parameter in the setup window from 9 to 8, then it works, but as soon as i jump back one faderbank step, the parametervalue switches back to 9. How can i save the settings ? Quiting Logic and restart doesn't help?
thanks for any help
christian

I sussed the patch editing and storing in the normal
factory mode, but in Logic control mode, I can't seem
to create my own patches and store them. Is this
possible? and if so, how can I "learn" the functions
like tape delay feedback.
Any help would be greatly appreciated! Thanks guys!
Ben (Brazil)
I have not been able to program mine in LC emulation
though I have been able to program the other presets.
Something I have not tried yet is trying to program the
many parameters in the controller assignments window.
I have discovered that by having the BCF in LCmode
going to the Controller Assignments window and
selecting expert and follow then clicking on
the different modes and such that the BCF
responds to what you are choosing on the screen.
I have not had the time yet to confirm this but
I believe the BCF is already preprogrammed to
do many of these in LC emulation. For example when I choose
track on screen the BCF would change its display
to "tr" and so on. This is a big discovery for me since
I new that in LCemulation the Unit was capable of
accessing all or most of what a Mackie Logic Control
unit could. I could never figure out how to get to those
parameters. This is one way to figure it out I suppose.
Behringer suggests that you read the docs for the Mackie,
I have not found this to be too helpful yet. Hope this helps.

Logic Control plays music notes!!!

Hi. My Logic Control behaves fine with audio tracks and midi tracks , but on Audio Instrument tracks (eg Sculpture , ES2 ) anything i press of move on the Logic Control plays the softsynth. The transport , track arm etc , all buttons behave like a keyboard. Even the channel faders play music notes. Its behaving like a Midi keyboard controller!
What am i doing wrong.....what should i do.
Also , the Logic Control does NOT show up in the Logic Setup assistant , nor the Audio Midi Setup. Though it shows up in Logic and works fine with audio tracks , the LCD displays my midi tracks just fine etc etc.
please help.
Faisal

Hi Allan. So sorry but i didnt understand which problem ur talking about---does ur Logic Control also play notes , or does it not show up in ur setup assistant ?
Thanks for ur post, i shall try and do what u do.

Logic Control broken by Logic Pro 8

My Logic Control, which has worked fine from Logic 5 to 7, now in Logic 8 has become almost inoperative.
1. the "save" button no longer works. It should not need assigning, according to the Apple Logic support guy, who is getting the same problem with his Logic Control. No solution yet.
2. the track display behaves erratically. When moving a fader, that track suddenly reads "volume" in the display, and won't go away. the track next door to the right of it immediately loses its name. Normally, this would never happen. the track is restored to semi-normalcy by pressing the "zoom" button - which, far as I know, is not the function of the zoom button, anyway.
Tried deleting and reinstalling Logic Control in the Control Surfaces prefs. No change.
Just thought I'd post this in case anyone out there is experiencing the same, and, hopefully has come up with a solution. help

ambient8 wrote:
I'm not denying that. I am quite aware that Logic 8 has issues. Being factual is important though. Especially when bringing credibility into question. If Logic causes you so many problems perhaps you should consider migrating to a new DAW. Gotta be able to enjoy your work. Pro Tools 8 looks quite tempting to me actually.
Cheers
Factual is every bit as important as literate.
I use Logic 7. In Logic 7 the control surface works perfectly, the audio output is not corrupted at the 2nd bit and all of the audio configuration functions are intact. None of this is true in Logic 8.
And please note that by saying that logic 8 is causing "me" so many problems you imply that these are not real issues, but apple have admitted to these issues and done NOTHING for "6 months".. Am I supposed to use defective software or do my job?
So please tell me why did you advise me to ditch Logic 8 (which I have stated that I DO NOT use) and moving to another DAW?

Logic Control and LP8

Hi,
I'm surprised at the lack of outrage over the terrible state of the Logic Control unit implementation in Logic Pro . With earlier versions of Logic I found using the LC unit a delight, recording and mixing several projects with it. Now (8.0.1) it's simply not worth using. I've tried all I know . . . rebuild defaults, trash preferences, re-install the unit, build a new autoload template (even Logic's templates don't work any better in this respect). Global mode doesn't work and track selection is a problem in any mode. One exception: if you're content with using the up/down arrows on the LC for track selection it works better . . . even in Global mode . . . it will actually put a track into Record and not mention the dreaded "Automation Folder"! Apple has stated that the unit is "behaving as expected". Mackie advised me to check for double .cs preference files(there weren't). Nobody said "Oh yeah . . . it's a problem". Either the issue isn't as widespread as I imagine or the relevant companies are not aware of the problem. This unit wasn't cheap. I paid $1764.00 Canadian when I bought it. It was worth every penny at the time, but now it looks more like a non-usable piece of metal that cost over three times more than the software (LP8) that appears to be crippling it.
What gives?
RW

Yep, I'm amazed at how broken it is in LP8, both major and minor issues. It's like nobody tested the MCU when they'd reworking the GUI and other stuff for LP8.
I've certainly reported this as a bug, so it's not like they aren't aware of it. I really hope they are tackling all this stuff (as well as all the other stuff) for an update soon...

Logic control - fader problem.

I am having a strange problem with Logic control - sometimes one of the faders will go to the top but in logic it will read a value of - 13 db - and whenever i try to correct it it just goes back to that setting.
I do not have any automation on the track.
can anyone explain this behavior?
cheers
DP 2.7Ghz Mac OS X (10.4)

Try rebuilding defaults or do the following...
Open the control preferences and delete the logic control from the list.
Turn off the logic control
Exit logic
Restart logic
After logic is up and running, turn on the logic control
P.s. Have you updated your firmware lately?
AD2

Logic Control & "Global View"

Hi,
When switching Global View on a Logic Control unit, say from Audio Tracks to Audio Instruments, the LCD always jumps to the highest instrument or track available. For example, I might be using 8 of 24 available audio tracks and five of 64 available audio instruments. When I switch views the LCD will show either instrument 64 on the left, or audio track 24. I then must either select an instrument via mouse on the arrange page or scroll back via the bank buttons on the LC to have, say, audio instrument 1 visible. Why? Any fix out there?
Along the same line, an improvement in the Logic Control interface would be intelligent switching between views on the LCD. For example, if an audio track is selected via mouse on the arrange page, the LC view would jump to that "type" of view even if the global view selected (on the LC) was "Outputs" or "Midi Tracks".
Cheers,
RW

On my system (with Logic Control) each Global page remembers where it last was. If I was looking at busses 9-16 last time I was on the Global bus mode, that is where I return to next time I engage busses in Global mode.
I like the fact that the LC does not switch to another object type when in Global mode. I use this to use the faders for busses while looking at tracks.
I do wish that tracks which are hidden in the arrange (and track mixer) would also be hidden on the LC when not in Global mode. This would allow global mode to show any object regardless of hidden state or use in the Arrange, and Global off to reflect the track status of the Arrange page.

Logic Control - XT display not resonding, noise coming thru midi....

I have a Logic Control and a Logic Control XT. XT on left, channels 1-8. Display on XT lights up, but doesn't recognize tracks (faders and other controls, do however).
"Midi in" on XT causes noise in my monitors (don't tell me it's impossible because midi sends 0 or 1 -- it IS causing interference in my monitors). Can bad midi cables or a bad midi interface cause noise?
Is my set up somehow incorrect?

I have a Logic Control and a Logic Control XT. XT on
left, channels 1-8. Display on XT lights up, but
doesn't recognize tracks (faders and other controls,
do however).
So everything works, but you get nothing on the display? When you power it up, do words come up on the display then (like a "Logic Control XT" welcome message?)
If not, perhaps the display has died?
"Midi in" on XT causes noise in my monitors (don't
tell me it's impossible because midi sends 0 or 1 --
it IS causing interference in my monitors). Can bad
midi cables or a bad midi interface cause noise?
You might have some kind of ground loop issue, which seems unlikely seeing as MIDI cables don't have a direct electrical connection.
It may be that your computer causes interference when sending MIDI (nothing to do with the Logic Control). Early motherboards, for instance, gave audio problems when using USB MIDI - I had an old motherboard which gave clicks in the audio drivers when sending MIDI via USB, which is why I used the serial bus MIDI instead, and that solved the problem.
Is my set up somehow incorrect?
Difficult to tell from just the info you provide!

Logic Control Faders Moving On Their Own

i have logic control by emagic v1.02. yes i have ensemble but its turned off and i'm using built in audio. what it does is when logic 8 is open and i touch a fader,even without song playing, when i touch the fader, it moves up about a few db. tried on different projects and does the same. there is no automation. anyone else experiencing this? and is there a fix?
thanks

Be sure to Rebuild Defaults for control surfaces after changing Logic's preferences for Touching Fader Selects Track. This might clear it up.
1.02 is the latest firmware for these devices. They've worked perfectly until Logic 8. Apple definitely made some mistakes and overlooked a few items when they rebuilt the control surface subsystem. Nobody's LC or MC is working in LP8 100% yet. I'm sure they'll fix it. Just a matter of time.

Aux Channelstrips and Logic Control

Hi,
It seems almost impossible to have ONLY the tracks in the arrange window reflected in my Logic Control + Extender. If I use BFD 2 with many Aux they will appear on the Logic Control, although they are not shown in the arrange and cluttering up my workflow!
Why is it so difficult just to have the tracks in the arrange laid down to the Logic Control???

Read the manual's section where Environment is covered. Environment is the part of Logic which gives it unlimited power to control (or the ability of being controlled by) MIDI devices. Basically, the control surface could be configured in the Environment, including the way all the knobs and sliders are used if need be. However, you must know what you are doing and what you are configuring all the knobs and sliders for. Besides, a ready-to-use Logic template or set of templates for your keyboard may already exist.

Logic Control Track Lock

Similar Messages

Maybe you are looking for