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.

Similar Messages

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 9 and Logic Control Surface

I recently received a Behringer BCF2000 as a gift and have successfully set it up in LC (Logic Control) mode. I'm having an odd problem, however, as the control surface only is receiving from Logic and changes on the BCF2000 are not reflecting in logic. When I change sliders/pan positions/etc in Logic, the BCF2000 reflects these changes. However, pressing buttons on the BCF2000 is unresponsive and if I move a slider, the motorized fader will return to the position as set in Logic.
I have been scouring the manuals for a solution, I'm sure it's something simple but I'm getting very frustrated. Any help would be immensely appreciated. Thanks!

Indeed.
Remove the control surface driver, and use LC Xmu instead. It's the absolute best way to use the Korg controllers with Logic, and has just about every feature you want/need.
http://www.opuslocus.com/lcxmu/

Logic Control issues again!

Details and history:
Emagic Logic Control---used to work just fine in Logic 6 and then started acting up on Logic Pro 7.
All faders and buttons work just fine. But from time to time, the PLAYHEAD jumps forward and keeps doing so. At this time the Stop and Play button lights also keep turning on and off and the SCRUB and ZOOM light come on at times too.
Rebuilding defaults does not help.
Then randomly, it starts working perfectly and might do so for hours. Very moody!
Logic Control is connected to AMT8 and is the only external midi device in my setup currently. Previously i had a Yamaha Motif as well and it would work just fine.
On Logic Pro 9.1.1, the same random behaviour, its like a cd skipping when music is playing so only solution is to turn it off. Rebuilding defaults helps at times, other times it does not. I did check/uncheck TOUCHLESS FADER option, one time it worked, other times it did not.
I updated the LC firmware to Mackie Control a few months ago. With Logic Pro 7, it greatly reduced the SEIZURES, not curing it completely.
On a PC with Presonus Studio One, it worked great, had one seizure in months, rest was awesome.
I tried booting it up on Logic Control mode night b4 last, and selected Logic Control in preferences/setup and deleted mackie control. No help.
Reverted to Mackie Control mode and things were great last night.
Today, madness again!!!
How do i diagnose this, is it hardware failure ? An issue with the AMT 8 ??
BTW, on the PC the mackie control was connected to the midi I/O of an RME card.
Today i will try connecting it via an Evolution UC33 and see if the AMT is the culprit.
Any help please ?? At this point i am seriously thinking about ditching this for a Euphonix MC Mix......but i'd rather save the cash and find a solution.
Sorry about the long post, i just want to be able to work.
Thanks
Faisal

Ok its working great now, at least for now. No SEIZURE!
Steps:
1. Delete Mackie Control or Logic Control from setup.
2. Trash preferences.
3. Boot up in Logic Control mode
4. Re-Scan.
5. Check TOUCHLESS Fader if need be.
All good. However, these steps don't always work!
Will keep u posted.
Thanks

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

"Logic Control" Assigned to "Session 1" Message

Hello fellow Logicheads:
Running Logic 10.0.7. Here's the message:
I have checked to make sure that all interfaces are connected and switched on. Checked the MIDI port setting of Logic Control, reset all MIDI drivers, yet message persists.
What am I missing?
Thanks!!

Hi
I am guessing that the "Logic Remote" is/was a device connected over wifi using an AudioMIDI Setup network session?
Open AMS and check that all is correct there.
CCT

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?

CUPC – Unable to go into deskphone control mode and unable to chat

Home Lab – learning Presence
CUCM 9
CUPS 9 (not 8.6 as virtually all of the help and discussion forums, documents, etc are for)
CUPC 8.6 (3 copies running on 3 different laptops)
4 users configured in CUCM for Presence capabilities
No LDAP integration
Current status:
Presence indicators for phones works fine, no issues
3 users can log into their CUPC clients and Presence information from their own associated deskphone displays correctly (ie if User 1 takes his deskphone offhook, the CUPC for User 1 shows as “On the Phone”
Users can place phone calls with each other by typing the DN in the “Search for name or number” field
I have two different issues that I have not been able to solve all day – they may be related to each other.
The first issue: I am unable to go into deskphone mode. Although the checkbox is visible – it appears to be greyed out and clicking in it does nothing.
The second issue: I am unable to start a chat session. I highlite a contact (that I manually entered), right click, and select chat. I get an error message that says “Failed to start conversation. Invalid parameter”
I have scoured the Cisco site for docs and most of them pertain to CUPS 8.6 and not 9. There is a difference in that v9 does not have the Application -> IP Phone Messenger selection.
My current configs:
CUCM
          4 application users – CUPS-AXL (with Stand CCM SuperUsers permissions), CUPS-Deskphone, CUPS-CTIGW, and CUPS-PhoneMSG (all with Standard CTI Allow control of all devices).
          3 end users – From top to bottom, all users have passwords and digest credentials. Under Service Settings, all users have the “Enable user for Unified CM IM and Presence” checked. This is the replacement for the assigning license capabilities from version 8.6. Also under Service Settings, all users have a UC Service Profile assigned. The UC Service Profile has two UC service settings – a Presence and IM Profile and a CTI Profile. Under Device Information – all user have been associated to two different devices (their hardphone and the CUPC client). Under the Directory Number Association portion – each user has their own primary line selected from the drop down box. Under the Permissions Information section - each user has Standard CCM End Users and Standard CTI Enabled permissions.
          Devices – each user has a 7960 hard phone and a CUPC. For each device (both types) at the Device Level -> Owner User ID, Protocol Specific Information -> BLF Presence Group, SUBSCRIBE CSS are all set. Under the line for each device (both types) – Allow control of device from CTI is checked, in the Associated Devices window is the MAC and UPC<name> of the devices, Under Users Associated with Line is the correct user
          Under System –> Application Server, the CUP server is configured.
          Under System -> Licensing, all users and devices are licensed. There is no Capabilities Assignment in version 9
CUPS
          Under Diagnostics -> System Troubleshooter -> all green except for the things not configured, LDAP, 3rd party, etc
          User Management -> End User -> are licensed for IM and Presence and have Microsoft RCC enabled. They also show 2 devices
          Under Application – this is where its different from v8 to v9.
          Application -> Legacy Clients -> Settings. I have set the TFTP server IP to the CUCM
          Application -> Legacy Clients -> CCMCIP Profile. I created a new profile, set the Primary and Secondary CCMCIP Host to be the IP Address of the CUCM Publisher. For Server Certification Verfication, I selected Any Certificate from the drop down. I assigned this profile to all 4 of my users.
          Application -> Microsoft RCC settings. Application status = on. For Application Username and password, I have tried using CUPS-Deskphone and CUPS-CTIGW with their appropriate passwords. There is not difference in using either one of them. CUCM address is address of my Pub. I assigned this Microsoft RCC service to all 4 of my users.
So, as I said, I have been working on this all day today burning my fingers and my mouse up on Google. To no avail.
Any ideas anyone?
Jeff

Update –
          Well, I finally bit the bullet and stood up a MS AD domain in my lab.
          I integrated CUCM into the LDAP and imported the users from LDAP
          I also stood up a DNS server.
          I reconfigured CUPS to the new domain, joined all of the endpoint laptops to the domain, and retested.
          Same place as I was before with the deskphone mode – however, my ability to IM is fixed (as was expected).
          Using CUPS, I am not able to go into deskphone control mode. The option box is still greyed out.
          However, I installed Jabber for Windows on the same laptops.
          In Jabber, I am able to select the option at the bottom of the window to use my deskphone for calls, and then I can move it back to the Jabber client.
          So, anyone have any ideas why CUPC refuses to let me go into deskphone control mode?
          All features and functions of the JFW work great. No problems.
Jeff

How do I run a Midi Light show from within Logic Pro?

Hello,
I'm trying to figure out how to run a midi light show along side or within logic pro. I currently run .wav synth files through logic into an Onyx Satellite into the PA system, I want to run a lights show that fits perfectly with each part of the songs running on logic pro. I need tips on everything: hardware, what intelligent lights I need, how to best program and set this up.
Any help would be greatly appreciated
Message was edited by: Host <to clarify Subject>

Hi
I use the NSI MC1616 midi controller. with it you can control 16 separate banks of lights and store 16 scenes. the unit uses midi program change messages for each scene and CC #1 info for fade rate. Since the MC1616 sends the program info midi out, I use it to send the commands to logic in real time, playing along with the song, pressing the scene buttons, to program the lighting cues.
Hope this helps
Don

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

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?

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 Working Properly anyone?

My logic control has not been working properly for a while.
It does most things fine but it does not do the following:
1. The Automation buttons don't do as they are supposed to; Pressing Latch, Touch or Write just enables READ mode.
2. Pressing the Down Arrow button Enables Send #8- It's supposed to scroll through the sends 1, 2, 3, 4 etc.
3. The Rotary pots for Send/Pan when turned send the Send/Pan paremeter to either 0 or 127!!
That's most of the problems. There may be more but I would really appreciate any help on this.
Thanks
Felix

If you are working in 64 bit mode, i think i can help, as i had the exact same issue.
1. Quit Logic
2. Trash the Control Surface Pref file "com.apple.logic.pro.cs"
3. Go to The Logic application - go Command-I to open up its information pane. Click the button to open Logic in 32-bit mode.
4. Open any Logic file.
5. Confirm that your automation buttons now work correctly
6. Quit Logic.
7. Go back to the information pane. De-click the 32-bit button
8. Re-opn Logic in 64 bit mode. You should be all fixed.
HTH

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 problem

My Logic Control is going mad. It keeps flicking the PLAY/STOP buttons automatically and the rulers keep jumping forward making the control surface useless.
Someone asked me to check if the Logic Control was receiving these commands to make sure it was not a hardware issue. I am not so savvy, can someone please offer any help in diagnosing the problem, please.
Thanks
Faisal

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?

BCF2000 - assigning within Logic Control Mode

Similar Messages

Maybe you are looking for