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

Similar Messages

Logic control firmware updatelink is down! Please help!

Hi!
I need the latest firmware update to use my logic control also for cubase. can anyone help?
http://www.mackie.com/de/products/mcu/mcu_upgrade.html
the update is down
Does anyone have the
Logic Control v1.02 (ZIP 13KB)
and can upload it for me?
thanks in advance!!!
Chris

Hi,
beside that the proposed config has no NAT, it appears fine. Can you send output of "show dsl interface" and "show atm PVC 2/35".

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?

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

How do you update Mackie Logic control with logic pro 7?

I moved my setup to a new location and now when I boot up my logic control its just a blue screen. Ive found its firmware has been blanked. I did some research and it seems emagic used to send users an old .mid file to fix it, but that was long ago. Now all i have is a 1.02 from Mackie, but every time i go to play the song it says error code 1. Does anyone know how to fix this? I think I turned off MTC and the midi clock, but still no go. Does anyone know how I can correct this within Logic pro 7? Any help would be appreciated! Ive never had to do anything with logic control before this, but turn it on!

I figured it out! I had to reset midi drivers in Logic, then a unitor tab came up that was NOT previously there (?) under midi settings and from there i was able to turn off VTC/LTC which was causing the error code.

Hi, I've just up-dated my OS in my MacPro 3.1 from 10.5 to 10.6.8 and can't seem to install my Logic Pro 8, any advise? can I install my Logic 8 in the 10.6.8 OS? Thanks

Hi, I've just up-dated my OS in my MacPro 3.1 from 10.5 to 10.6.8 and can't seem to install my Logi Pro 8, I can install the libraries but not the program, is it possible to install or do I have to up-grade to Logic 9? Thanks

It's either that Logic 8 is looking for the Rosetta emulation program or that Logic 8 was previously installed on this OS, in which case you will have to remove some preference files and install receipt.
I think the Rosetta emulation is downloadable for SL.

Logic pro won't install on macbook pro

I have Logic Studio 9.1.5 working on my iMac i7 under OS X 6.8. It is an upgrade of an upgrade, etc going back to V 5.5. I have the original Emagic key from Logic 5.5. My recollection is that I had to use this to install the Logic Studio upgrade to get Logic Pro 8, but that when I upgraded to V9, the key was not necessary.
I'll be visiting some remote sites for recording later this fall, and decided to move Logic to my MacBook Pro for the trip. It came with Lion. I installed the minimal setup from the Logic Studio package to get Logic Pro 9 on the MBP. It asked me for the serial number and to insert the EMagic key at the start of the install process. Once installed, it would not launch under Lion so I installed the 9.1.5 update. When I tried to launch after this update, Logic started up, but I was asked for the serial number and Emagic key again. This time, it reported that my key is not elegible for this upgrade. Makes no sense, given I had this running with no probllem on the iMac.
Have there been any other steps required to install under Lion? Is there anything else anyone can suggest to look into?

Samuel, this won't help you, but it may help some others.
I had CS2 installed on my good old TiBook 400MHz, and it worked fine there. When I got my new MBP C2D 2.33 yesterday, I followed the instructions for connecting via FireWire, and after 2 hours, everything copied over just fine. So far, everything works fine too, which is really amazing to me, including the Adobe CS2 applications.
I did make sure that my old TiBook was up-to-date, and ran Mac Janitor on it, and fixed permissions. That may have made the difference.
The only things which don't run now are the old OS9 applications, and Final Cut Express 3.0 (but there is a work-around using the esc key).
Hope this is encouraging to someone who is thinking about gettig a MBP C2D.

Strange Crash when opening Logic 9 after deleting control surfaces preferences file

Hey, I have been having issues where logic crashes when I save certain projects of mine, so I tried to find a solution and one that I had read said that I should delete the control surfaces preferences file named com.apple.logic.pro.cs. I deleted the file, but it seems to have bricked my copy of Logic. I have included a screenshot of what happens when I now open Logic, which requires a force quit to get out of. If anyone has any suggestions of what I should do next I would really appreciate it.

Solved. It was an issue with my prokit (I had also been messing with that unfortunately). Found another thread and followed their instructions, back in action. Feel free to lock this thread.

Default mastering file Logic Pro 9

I have Logic Pro 9 and Logic X installed. Most of my current work is done on Logic 9 as I am still learning X. I set up a default mastering file so that when I master a song, I start the default file and drag the PCM version of the file into the mastering file. All the inserts I need are pre-configured, ie; multimeter, EQ, multipressor etc. Every once in a while when I want to master a song, I click on the default mastering file I created, and it launches Logic X. Is there any way to prevent this from happening. Once this happens, I have to delete the mastering file I created and re-create it using Logic Pro 9. Logic X will always start as the default unless I do this. Anyone have similar problem and work around?
Ralph

Hi
The Art Of Sound wrote:
CCT,
Wouldn't you agree however, that using a template.. rather than a project, is a much simplier and more beneficial route for the future, to take for such things?
It might be, but the OP seems to like to simply double click on the Mastering Project file. Equally simple, especially if it is locked, to prevent accidental overwriting.
2x click the file, (Logic opens, if it isn't already), File Save As, start work
Each to their own I guess
CCT

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 erased firmware problem

I'm using an Emagic (Mackie) Logic Control version 1.0 with Logic Express 7.1 and tried to update it to version 1.02 this afternoon. Whoops! It gets halfway through (the dots dash along the LCD as they should) and then it displays "Update Failed!!! - (Error Code 1) and that's as far as we get. If I then switch it off and back on again I get nothing - just a blank screen. Logic no longer recognizes it either, so I'm guessing that it has erased the firmware, but because it won't load the new firmware I'm effectively left with a wedge shaped doorstop!
Anyone got any ideas?
Many thanks!

A suggestion from the Logic User Group:
http://logic-users.org/forums/LUG/thread/80451
Hope this helps.
cheers
rob

How do I install logic 9 on an older macbook pro ?

I downloaded logic 9 on my new macbook pro through to App Store. I want to also run it on my older macbook (Early 2008) currently using mac os x 10.5.8. How do I upgrade the Os X so it works and how do I install logic on the old one ?
- I can't go from 10.5 to 10.8
- I need at least 10.6.8 to run Logic Pro 9
- Once the Os X is up to date, how do I transfer the app, if possible avoiding downloading 20Gb again.

Hi just curious, how is Logic running on your new Macbook?

I can't install my old logic 8 on my new macbook pro. It says it does not support powerpc applications anymore. what do i need to do?? this is ridiculous!!!

I can't install my old logic 8 on my new macbook pro. It says it does not support powerpc applications anymore. what do i need to do?? this is ridiculous!!!

Logic 8 will probably run on your new machine but the installation program contains some older PPC code for pre Intel Macs. This was not a problem as all OSX versions contained the "Rosetta" PPC emulation, that is, up until Lion when all PPC emulation was dropped.
There are ways to do this however, try searching Google for: Installing Logic 8 under Lion or Mountain Lion.

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

Emagic Logic Control firmware install file Logic 8 pro

Similar Messages

Maybe you are looking for