Logic Control Jog Wheel Erratic in 7.1.1, OK in 6.4.3

Rotating the Jog Wheel clockwise causes the SPL to leap to bar 13, 66, 201 and rotating counter-clockwise allows no rewind function except return to zero. I have re-initialized everything including key commands, even re-installing Logic Pro 7.1 and updating to 7.1.1 and no difference. The Logic Control continues to work perfectly under Logic Pro 6.4.3, so this is specifically related to Logic Pro 7 Can anyone offer any help?

Anybody know anything about this??

Similar Messages

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 and Logic Pro 9.1.0

I'm running Logic Pro 9.1.1 and Logic Control V1.02 which makes it mackie control.
Today i set it up with Logic and noticed a few things:
1. The level reading on the Logic Control's display is choppy...meaning if i raise a fader really slowly the display levels also rise slowly synced with on the onscreen faders. However if i move the faders a bit faster, the Logic Control display reading is very choppy--it always settles at the right level, but the changes are jumpy. Is this usual ? This was not the case with Logic 7.
2. A few times the locator bar jumped forward missing beats, as if stop/play were pressed repeatedly. I rebuilt defaults and now it seems to be working fine, This used to happen to me in Logic Pro 7 as well, maybe its a fault with my controller. Anyone ever experience this ?
Thanks
Faisal

Cowbell, my experience has been different.
I tried the Logic Control mode but things were really wierd, some buttons not working, then the whole control lost contact with logic till i re-launched.
The Scroll bar jumping thing was happening a lot more often.
Then i deleted LC, trashed preferences and re-booted in Mackie Control mode.
Still strangeness and i went did the check TOUCHLESS FADER thing and all is working fine now which is WEIRD!!!!!! I think i may have a defect in the jog wheel/transport section but its all working fine for now.
I'll give it a few days.
Thanks !!

Shuttle Express jog wheel

Hello there,
I would like to use my +contour design+ Shuttle Express for controlling Logic 8.
But the factory settings for the jog wheel, don't work for jog or scrub.
Does somebody knows how to set the parameters of the jog wheel, to use it for scrubbing audio ?
Or can somebody post his parameters, or settings ?
Thank you

Hi Janak,
So I thought of a decent way to do it using an event structure. I have posted the code and it uses graph instead of a chart. I hope it helps.
Brian K.
Attachments:
mechanic.vi ‏18 KB

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?

Using Logic X-Mod Wheel not being received.

Im having an issue with the mod wheel info on passing to Logic X. Its not m¥ controller because it works in Pro Tools.
Odd ly if I assign another controller with the same CC number , Mod. info can be recorded ( but not from the Mod wheel )
Thansk, GF

Not sure exactly how this happened but there was one command called Jog Wheel. I removed that and the Mod Wheel started working.Thanks ErikSimon as this was found in the Controller Assignment window.
GF

Jog Wheel on Front Panel

I am searching for a Jog wheel /knob of sorts for controlling user input of time/frequency on the front panel.
What I would like to do is akin to the Jog wheel that we use on ham radio stations to change frequencies/channels etc. Essentially, you can use the same wheel to turn in 0.1 Hz increments, 1 Hz increments ....and even in 1MHz increments.
We need to look at a large amount of waveform data, and I want to have the functionality of moving forward, or backward in time to see different results.
Currently, we use Labview Professional Development System 8.0.1.
Appreciate your help!!
~Janak
Message Edited by mechanical13 on 04-25-2007 10:24 AM

Hi Janak,
So I thought of a decent way to do it using an event structure. I have posted the code and it uses graph instead of a chart. I hope it helps.
Brian K.
Attachments:
mechanic.vi ‏18 KB

Emagic Logic Control firmware install file Logic 8 pro

Can anyone help by telling me how to install the firmware on my old Logic Control. I have tried to run the Mackie midi update and now the Logic Control will not boot, I thing the firmware has been damaged. Emagic used to send a .mid file does anyone have it? I was burgled and all my software discs were taken. Please help if you can.

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 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?

Possible to use Mackie Logic Control to control volume faders in MainStage

Hi, is it possible to get Mackie Logic Control to work with the volume faders of the various channel strips in MainStage. Is seems Mackie Control is automatically mapped when using Logic - but MainStage doesn't seem to automatically map faders unless I am missing something. Any help is appreciated. Thanks.

Hello, I installed 'Midi Monitor' and when I slide the 'Master Volume' fader on the Mackie Control, Midi Monitor reports the following:
17:02:29.250 From Port A Note On 1 E7 127
17:02:29.251 From Port A Pitch Wheel 9 -7888
17:02:29.254 From Port A Pitch Wheel 9 -7824
17:02:29.264 From Port A Pitch Wheel 9 -7696
17:02:29.274 From Port A Pitch Wheel 9 -7520
17:02:29.285 From Port A Pitch Wheel 9 -7392
17:02:29.295 From Port A Pitch Wheel 9 -7232
17:02:29.305 From Port A Pitch Wheel 9 -7040
17:02:29.315 From Port A Pitch Wheel 9 -6896
17:02:29.326 From Port A Pitch Wheel 9 -6704
17:02:29.336 From Port A Pitch Wheel 9 -6528
17:02:29.346 From Port A Pitch Wheel 9 -6304
17:02:29.356 From Port A Pitch Wheel 9 -6128
17:02:29.367 From Port A Pitch Wheel 9 -5808
17:02:29.377 From Port A Pitch Wheel 9 -5696
17:02:29.387 From Port A Pitch Wheel 9 -5520
17:02:29.397 From Port A Pitch Wheel 9 -5264
17:02:29.407 From Port A Pitch Wheel 9 -5056
17:02:29.418 From Port A Pitch Wheel 9 -4800
17:02:29.428 From Port A Pitch Wheel 9 -4592
17:02:29.438 From Port A Pitch Wheel 9 -4320
17:02:29.448 From Port A Pitch Wheel 9 -4112
17:02:29.459 From Port A Pitch Wheel 9 -3904
17:02:29.469 From Port A Pitch Wheel 9 -3632
17:02:29.479 From Port A Pitch Wheel 9 -3424
17:02:29.489 From Port A Pitch Wheel 9 -3168
17:02:29.500 From Port A Pitch Wheel 9 -2960
17:02:29.510 From Port A Pitch Wheel 9 -2720
17:02:29.520 From Port A Pitch Wheel 9 -2528
17:02:29.530 From Port A Pitch Wheel 9 -2320
17:02:29.541 From Port A Pitch Wheel 9 -2080
17:02:29.551 From Port A Pitch Wheel 9 -1888
17:02:29.561 From Port A Pitch Wheel 9 -1648
17:02:29.571 From Port A Pitch Wheel 9 -1472
17:02:29.582 From Port A Pitch Wheel 9 -1248
17:02:29.592 From Port A Pitch Wheel 9 -1072
17:02:29.602 From Port A Pitch Wheel 9 -864
17:02:29.612 From Port A Pitch Wheel 9 -720
17:02:29.623 From Port A Pitch Wheel 9 -576
17:02:29.633 From Port A Pitch Wheel 9 -384
17:02:29.643 From Port A Pitch Wheel 9 -224
17:02:29.653 From Port A Pitch Wheel 9 -48
17:02:29.663 From Port A Pitch Wheel 9 96
17:02:29.674 From Port A Pitch Wheel 9 304
17:02:29.684 From Port A Pitch Wheel 9 448
17:02:29.694 From Port A Pitch Wheel 9 592
17:02:29.704 From Port A Pitch Wheel 9 784
17:02:29.715 From Port A Pitch Wheel 9 928
17:02:29.725 From Port A Pitch Wheel 9 1104
17:02:29.735 From Port A Pitch Wheel 9 1248
17:02:29.745 From Port A Pitch Wheel 9 1440
17:02:29.756 From Port A Pitch Wheel 9 1584
17:02:29.766 From Port A Pitch Wheel 9 1728
17:02:29.776 From Port A Pitch Wheel 9 1904
17:02:29.786 From Port A Pitch Wheel 9 2048
17:02:29.797 From Port A Pitch Wheel 9 2208
17:02:29.807 From Port A Pitch Wheel 9 2352
17:02:29.817 From Port A Pitch Wheel 9 2512
17:02:29.827 From Port A Pitch Wheel 9 2640
17:02:29.838 From Port A Pitch Wheel 9 2832
17:02:29.848 From Port A Pitch Wheel 9 2960
17:02:29.858 From Port A Pitch Wheel 9 3104
17:02:29.868 From Port A Pitch Wheel 9 3280
17:02:29.879 From Port A Pitch Wheel 9 3424
17:02:29.889 From Port A Pitch Wheel 9 3600
17:02:29.899 From Port A Pitch Wheel 9 3744
17:02:29.909 From Port A Pitch Wheel 9 3920
17:02:29.920 From Port A Pitch Wheel 9 4096
17:02:29.930 From Port A Pitch Wheel 9 4256
17:02:29.940 From Port A Pitch Wheel 9 4464
17:02:29.950 From Port A Pitch Wheel 9 4624
17:02:29.960 From Port A Pitch Wheel 9 4832
17:02:29.971 From Port A Pitch Wheel 9 4992
17:02:29.981 From Port A Pitch Wheel 9 5184
17:02:29.991 From Port A Pitch Wheel 9 5328
17:02:30.001 From Port A Pitch Wheel 9 5520
17:02:30.012 From Port A Pitch Wheel 9 5664
17:02:30.022 From Port A Pitch Wheel 9 5808
17:02:30.032 From Port A Pitch Wheel 9 6000
17:02:30.042 From Port A Pitch Wheel 9 6144
17:02:30.053 From Port A Pitch Wheel 9 6320
17:02:30.063 From Port A Pitch Wheel 9 6464
17:02:30.073 From Port A Pitch Wheel 9 6640
17:02:30.083 From Port A Pitch Wheel 9 6800
17:02:30.094 From Port A Pitch Wheel 9 6960
17:02:30.104 From Port A Pitch Wheel 9 7168
17:02:30.114 From Port A Pitch Wheel 9 7328
17:02:30.124 From Port A Pitch Wheel 9 7520
17:02:30.134 From Port A Pitch Wheel 9 7680
17:02:30.145 From Port A Pitch Wheel 9 7872
17:02:30.155 From Port A Pitch Wheel 9 8000
17:02:30.165 From Port A Pitch Wheel 9 8144
17:02:30.176 From Port A Pitch Wheel 9 8176
17:02:30.453 From Port A Note Off 1 E7 0
17:02:31.298 From Port A Note On 1 E7 127
17:02:31.299 From Port A Pitch Wheel 9 8176
17:02:31.384 From Port A Pitch Wheel 9 8176
17:02:31.394 From Port A Pitch Wheel 9 8080
17:02:31.404 From Port A Pitch Wheel 9 8000
17:02:31.415 From Port A Pitch Wheel 9 7888
17:02:31.425 From Port A Pitch Wheel 9 7760
17:02:31.435 From Port A Pitch Wheel 9 7552
17:02:31.445 From Port A Pitch Wheel 9 7392
17:02:31.456 From Port A Pitch Wheel 9 7216
17:02:31.466 From Port A Pitch Wheel 9 6976
17:02:31.476 From Port A Pitch Wheel 9 6800
17:02:31.486 From Port A Pitch Wheel 9 6576
17:02:31.497 From Port A Pitch Wheel 9 6400
17:02:31.507 From Port A Pitch Wheel 9 6176
17:02:31.517 From Port A Pitch Wheel 9 6000
17:02:31.527 From Port A Pitch Wheel 9 5808
17:02:31.537 From Port A Pitch Wheel 9 5568
17:02:31.548 From Port A Pitch Wheel 9 5360
17:02:31.558 From Port A Pitch Wheel 9 5104
17:02:31.568 From Port A Pitch Wheel 9 4896
17:02:31.578 From Port A Pitch Wheel 9 4592
17:02:31.589 From Port A Pitch Wheel 9 4352
17:02:31.599 From Port A Pitch Wheel 9 4048
17:02:31.609 From Port A Pitch Wheel 9 3824
17:02:31.619 From Port A Pitch Wheel 9 3552
17:02:31.630 From Port A Pitch Wheel 9 3216
17:02:31.640 From Port A Pitch Wheel 9 2960
17:02:31.650 From Port A Pitch Wheel 9 2656
17:02:31.660 From Port A Pitch Wheel 9 2432
17:02:31.671 From Port A Pitch Wheel 9 2112
17:02:31.681 From Port A Pitch Wheel 9 1856
17:02:31.691 From Port A Pitch Wheel 9 1584
17:02:31.701 From Port A Pitch Wheel 9 1232
17:02:31.711 From Port A Pitch Wheel 9 944
17:02:31.722 From Port A Pitch Wheel 9 576
17:02:31.732 From Port A Pitch Wheel 9 304
17:02:31.742 From Port A Pitch Wheel 9 -80
17:02:31.753 From Port A Pitch Wheel 9 -368
17:02:31.763 From Port A Pitch Wheel 9 -672
17:02:31.773 From Port A Pitch Wheel 9 -1056
17:02:31.783 From Port A Pitch Wheel 9 -1360
17:02:31.793 From Port A Pitch Wheel 9 -1712
17:02:31.804 From Port A Pitch Wheel 9 -2000
17:02:31.814 From Port A Pitch Wheel 9 -2352
17:02:31.824 From Port A Pitch Wheel 9 -2624
17:02:31.834 From Port A Pitch Wheel 9 -2960
17:02:31.845 From Port A Pitch Wheel 9 -3232
17:02:31.855 From Port A Pitch Wheel 9 -3520
17:02:31.865 From Port A Pitch Wheel 9 -3872
17:02:31.875 From Port A Pitch Wheel 9 -4160
17:02:31.886 From Port A Pitch Wheel 9 -4480
17:02:31.896 From Port A Pitch Wheel 9 -4736
17:02:31.906 From Port A Pitch Wheel 9 -5088
17:02:31.916 From Port A Pitch Wheel 9 -5392
17:02:31.927 From Port A Pitch Wheel 9 -5680
17:02:31.937 From Port A Pitch Wheel 9 -6064
17:02:31.947 From Port A Pitch Wheel 9 -6368
17:02:31.957 From Port A Pitch Wheel 9 -6752
17:02:31.967 From Port A Pitch Wheel 9 -7040
17:02:31.978 From Port A Pitch Wheel 9 -7392
17:02:31.989 From Port A Note Off 1 E7 0
17:02:32.045 From Port A Note On 1 E7 127
17:02:32.046 From Port A Pitch Wheel 9 -8192
17:02:32.203 From Port A Pitch Wheel 9 -8192
17:02:32.225 From Port A Note Off 1 E7 0

L8 is seeing my Axiom as a Logic Control and it's wreaking havoc!

A new twist on all the control surface issues - I have a M-Audio Axiom 25 connected via USB and it's not setup in anyway as a control surface via the control surfaces preferences. I have never used it as such and never need to because I own a Logic Control.
All of the sudden, L8 is recognizing midi note input from the M-Audio as LC input - i.e. if I press an A3 it doesn't sound a midi note, but rather performs a specific Logic Control function as defined in the Key Command Preferences.
Of course, it's even worse because I have an Apogee Ensemble so Logic doesn't even recognize a potential Control Surface unless everything is powered up in just such a perfect way.
So I have a Logic Control that isn't recognized, and an Axiom 25 that is recognized as something it's not and if I go to Control Surfaces preferences, it's as if the world of cotrollers doesn't even exist because the master list of options is gone baby gone.
Anyone find a workaround for this?

totally different ports!
The LC is connected via my AMT8 - the Axiom is on it's own port via USB, so that shouldn't be issue.
I've tried cabling the Axiom port directly from the input object to a monitor and then terminating the connection just so I can see what it's transmitting - the "bad" notes don't show up as anything in the monitor and even though I've broken the Sum cable from the input object and the Axiom port is only cabled to a monitor and nothing else (the Sequencer input is not connected to anything at all!), L8 is receiving those key presses as LC commands.
So strange

Logic control in JSF's jsp

Hello I have fundmental question to ask;
In Struts or JSP page, you can use logic control to determine what will display. For intance, the tag on strut <logic:match> <logic:equals>. I am wondering how to have this sort logic in JSF. Thanks!

Thanks guys!
the simple solution is what you said:
in JSF page, binding rendered to a propertity in the bean. on the bean create the property - method to have the logic to return true or false. Do you think if it is a better solution than using jstl -- I dont know too much JSTL - I am more service side developer such as proxy service, application server to host tcp connection from clients...

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.

Updating logic control problem

Hi. Hope somebody can help. I just bought a used Logic Control and I'm trying to update it to Mackie Control functionality. I have the update but the instructions are a bit confusing I have imported the MIDI file into Logic but then I am told to "Disable the Mackie Control/Logic Control as a midi controller". I don't know what this means. I have tried removing it from the control surfaces setup but no luck. When I play the midi file I get nothing. The logic control stays in "Waiting for MIDI upgrade" mode but no update. Help!

I am told to "Disable the Mackie Control/Logic Control as a midi
controller". I don't know what this means. I have tried removing
it from the control surfaces setup but no luck
From the instructions you state, that's what I'd infer from them.
When I play the midi file I get nothing. The logic control stays
in "Waiting for MIDI upgrade" mode but no update.
Where are you playing to MIDI file to? You sure you're playing it to the MIDI port that the LC is on, and that your interface isn't filtering sysex data?

Final Cut Express and logic control

Hi,
has anyone ever achieved to combine final cut express and logic control?
I'm a logic audio user and Iwould be greatful to influence major features of final cut with the controller "logic control XT" and let them work together.
Thanks for your help and ideas!
Alex

No. FCE has no mixer.

Logic Control Jog Wheel Erratic in 7.1.1, OK in 6.4.3

Similar Messages

Maybe you are looking for