LOGIC PRO X - MACKIE C4 PRO

So, is anyone else's Mackie C4 Pro not fully functioning how it's supposed to using Logic Pro X?

Good morning Sarah. Sorry for the late reply. Had a busy week with my family & home studio.
I'll actually head to my main studio later on today & I'll be able to fully describe what's going on with my Mackie C4 Pro when using it with Logic Pro X.
Just off top: ALL of my Tools only show "On/Off" options which I've never seen before. The name of the actually Tool is not displayed (or working) like it does on Logic Pro 9.
Also, the Channel & Function buttons basically don't work/aren't applied to Logic Pro X. It's so weird considering the Mackie C4 IS in the Logic Pro X's Control Surface manual.
I REALLY hope Apple, Inc. addresses this ASAP so I could continue to work on LPX.
Any idea where I could notify Apple, Inc. directly about this "bug"?

Similar Messages

Connection problems between logic Pro X and Mackie MCU PRO

Hello, I need help.
I bought a mackie MCU control PRO and don´t work on my Logic Pro x. Does anyone know if I have to do something in the logic to configure? or should it automatically go?
Thanks for your help
This is my equipment list if you have any questions;
MAc Book Pro, Maverik IOX
Motu Ultralite
Mackie MCU PRO
Logic Pro X

Not enough information to help you.

Using Mackie Control with Logic Pro 7 and Yamaha O1X

I currently own a Yamaha O1x which is a mixer/control surface/audio interface that I use with Logic Pro 7. I am planning on selling the O1X and replacing it with the Mackie Control Universal as my DAW controller and using the Apogee Ensemble as my audio interface. I already have purchased the Mackie Control Universal and would like to begin using it instead of the O1X as my DAW controller, but while I am waiting for the Apogee Ensemble to be released I still need the audio interface capabilties of the O1X. The O1X uses Yamaha's MLAN protocol to connect to the G5. MLAN is a firewire interface that can transmit both audio and midi. Does anyone have a suggestion for a work-around solution so that I can use my Mackie Control Universal (which connects via midi cable) and only use the audio capability but not the control surface of the O1X via the firewire connection? I haven't been able to figure my way through this one and see if it is possible. I have already tried having them both hooked up at the same time, and the Mackie Control seemed to work fine but the audio on the O1X didn't seem to be connecting and functioning properly. I appreciate any help as I am anxious to use my Mackie Control.
Thank you!

You need to connect only the Audio and not the MIDI between your 01x and Mac. You can achieve this in mLan Graphic Patchbay-connect the cables between the Nodes in Audio part of a Graphic Patchbay, connect the Wordclock but do not make any MIDI connections. this way it should work as you want. the other way is to Make your regular connection from mLan Autoconnector and disable the MIDI ports that are dedicated to control the DAW by 01x by some freeware utility (01x uses port 1 for that...)
As this is quite 01x specific, please visit 01xray.com/forums where you will find more help, or send me PM.
As Apogee enssemble is expected to have great features, I would rather recommend the i88x instead of Enssemble (i88x has two Mic preamps-the best Yamaha produces (derived from Dm2000)VERY good converters (mLan is known for low jitter and it was tested with Rosseta by a mate from 01x forum who said (he tested it in store with other people) that i88x sounded better-may believe it or not...).The mLan Graphis Patchbay application allows you to patch connections between mLan devices and computer -very flexible. 01x already does almost the same as Mackie control and it is for almost the same price.... But maybe you are pi_ssed of waiting for new mLan drivers? I am just speculating....

Mackie onyx 1640i digital mixer compatible with logic pro x??

I have a macbook pro 10.9.1. And was curious about purchasing a mackie onyx 1640i digital mixer. Is it compatible with logic pro x DAW?? Feed back would be much, much appreciated!

Well I got the 13 mackbook pro retina, mackie onyx1640i three days ago and havent got the onyx and the mac to talk to each other. Problem is, mackie had a firewire 400 output and the Mac has a thunderbolt input. So i guess you got to use adapters? I have an old macbook pro and it does have a 400 firewire input. I dont know what they were thinking, they need a 400 firewire and one end and a thunderbolt cable at he other. Marco805

New User, Mackie 800R with Logic Pro 7

I'm a new user of Logic 7. I'm trying to figure out how to sync logic to The Mackie Onyx 800R.
My set up is a Digi 003 Rack with the Mackie connected via optical (lightpipe). In Pro-tools I can go to set up and select optical as my clock. In the logic manual I don't see anything that even mentions optical inputs or how to use another device as the clock. Any help would be greatly appreciated.
Thanks!!

Thanks very much for the reply. I don't think Core Audio can select the Mackie as the clock source.
In Pro-tools there is a menu which can selct internal clock or external. Within the external choices there is the option of selecting Adat optical as the external clock. I'm not finding anything like that in Logic. I see ways to sync to MTC or sympte but not this. Any others with thoughts on this or advice, I'd be very grateful. Thanks!

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.

Will a Mackie Control Universal V.2.1.2 work with Logic Pro 9?

Will a Mackie Universal Controller V. 1.2.1 work with Logic Pro 9?

Mine does. There was something If I can remember how to do it about after the update selecting the controller to mackie controller. You have the option within the controller itself to be mackie controller or logic controller. If it powers up and says mackie controller, You should be fine. If you have a problem get back to me, Ill look for the link that tells you how to change it.

Logic Pro 8 and Mackie HUI Controller

I have the above running and control surface setup appears to be normal. However, while Logic is recognized on the HUI at bootup (verbiage in the display...) I get no control out of any faders, assignment buttons or channel strips. The only thing that seems to work are the jog wheel to move the playhead and the transport controls themselves. Everything else appears to be dead and I can't activate any assignment zone.
Any clues as to why this would be? Logic or Mackie??
any help would be appreciated.
thanks

It may be a corrupt preference file for the control surface:
There have been a few issues since version 8, some of which have been rectified with the 8.0.2 update.
Some that remain are;
• Save LED doesn't go out after save
• Some on screen alerts cannot be responded to via the controller
There are a few others but overall it is working well for most people.
Make sure you don't have a corrupt preference file for the control surfaces. In my experience, this preference file is even more sensitive than the main logic preference file. Ditch it and rebuild.. It's a pain if you have many custom features set up, but is necessary to get things going again.
Once you have a set of logic preferences that are working well, copy the two files to the desktop and select them both, then right click and create archive... Then you'll have a pair of 'good' files that you can drop into the prefs folder when things go crazy again.
After a crash, you will want to drop the fresh ones in there.... as a crash always seems to corrupt the prefs files in my experience.
MacHD / Users / 'your account'/ Library / Preferences / (in here you look for, "com.apple.logic.pro.cs" for controllers
"com.apple.logic.pro.plist" for the app

Is the Mackie Control broken in Logic Pro 9 ??

Haven't upgraded yet and read that Logic 9 has broken Mackie Control support.
True ? I only have the central unit. Works fine with LP7, but i want to move to an Intel Mac soon and will have to upgrade to Logic 9. Mackie Control support is very important to me.

My Logic control does not work properly in either 10.5 or 10.6 with Logic 9. The odd thing is that the same Logic Control is working better on my iMac running 10.6 than it does on my Mac Pro in either 10.5 or 10.6. Is there a way to keep my logic control working? Firmware 1.02 and its the original Logic control not the mackie control. Had to buy a motu micro lite so I could use the controller with SL.

Logic Express on MBP 2.2 to Logic Pro or Wait? Track count? 720 RPM drive?

Hey there,
Just a few easy questions, some of which I am sure have been asked but didn't find with search.
Wondering if I should upgrade to Logic Pro or wait until after Leapord? As their is some speculation the FCP is going to come out (NEW) and be very, VERY Apple like, not like iMovie, (he said, and saw), but nonetheless very VERY Apple like for FCP, so wondering how far Logic is. Also, how many times can you install LP?
Right now everything from Storm Drum FX EXtreme, EWQL SO, VLS, etc, are all on PC and I still don't use the PC that much and am hoping new LOGIC include a great drum machine.
II. Anyone know what track counts you can expect with off the shelf MBP 2.2 and plug ins? (Soft Synths)?
III. Has anyone upgrade their HD to 7200? If so, more or less batter life? Any real world difference besides boot up time in AUDIO work advantages?
Thanks

Now see, this is what I was afraid of. (LOL), I have built PC's for a long time and was always under the impression having a 7200 RPM System drive is fine and these days so fast with eSata that on a MBP 2.2 (which is what I have - someone asked what I was using, or did they mean software), that is should be plenty fast enough, just wondering though for samples, BFD, DrumCore, VSL, etc if those should go on a firewire.
I also use Absysnth (if this is what you mean (other poster), Nuendo, FC Express, SX3, Logic E, Reason, ......
Two scenarios:
Music=Mine, Drum machine, really like the Addictive (also have and Drumcore) as well as have Groove Agent, Storm Drum, (No storm drum yet or FX Extreme for Intel, let alone EWQLSO?), bass, guitar, vocals.
Scenario II. Scoring Trailers:
Soft Synth, Samplers (EWQL/VSL), Reason, Absynth.
Most of the time I could do this on a old system equal to first duo on PC on the system disc, although I had 4 HD's. The Firewire is Mackie 400F, which also has a firewire, (extra) that I have plugged a digital cam cord AND up popped iDVD, iMovie, also have FCP.
But it's interesting that the two responses I got one said much better performance, the other not.
So, are we using in the new 2.2 (LED) eSata)? Is the a 32 slot for the MBP for eSata HD? Isn't this supposed to be the fastest?
http://www.firmtek.com/seritek/seritek-2sm2-e/
Thanks!

Logic Pro 9.1.7 + Imac 2010 + 10.7.4 + Firewire = Audio Error and Solution.

Hi all,
This post is the end of a weeks long hair pulling, to save other people the pain of my past week, here is a quick rundown of the issue and the solution that for us at least worked.
All the software is legit and fully updated btw, before people ask.
Logic Pro 9.1.7 on 2010 Imac on 10.6.x, Refx Nexus, Sylenth plus many other VST's and Au's, Mackie Pro + Extender, 2 Midi Keyboards (Oxygen 49 and Alexis 49) and with a M-Audio 410 external soundcard running 10.1.3 driver, all working.. only issue we had was when copying midi between tracks into differing plugins the midi would corrupt the plugin requiring a restart of Logic.
This error we later discovered was due to midi automation for plugins being copied over, but that is not this issue.
Updated OS from 10.6 to 10.7.4 by way of 10.7.4 Combi Update. Removed M-Audio Drivers and then installed 10.7.4,
Installed brand new GRAID 4TB external disk (Raid 0 at 64kb block sixe) and connected M-Audio 410 via daisy chain.
Installed M-Audio Drivers, all ok.. at first..
Graid is 800, M-Audio is 400.. Connected as Imac -> GRaid -> Maudio
At first, its good, no issues.
Copied over a whopping 550GB off Imac onto external.. then later on, rebooted mac and started working on music.
Ran Logic Pro (64bit mode), whilst using Midi with Nexus we discovered the Audio at first was ok, but quickly over time degraded to where the sounds started becoming distorted, the more we went on, the more the distortion increased, after a while the midi notes were just sounding awful.
Rebooted mac
Started using Logic again, not 1 minute in, External drive and M-Audio disconnected themselves from the Mac.
Rebooted
Hard drive now seen, no M-Audio.
Now though, even using Itunes or Quicktime or VLC on any mp3 via internal soundcard, quality was.. well terrible. Within 2 seconds of hitting play, you knew it was bad.
Shutdown, removed external drive from chain, rebooted Mac -> M-Audio
M-Audio now seen, sound quality dreadful, shutdown Mac, rebooted without M-Audio, sound still awful just on Internal audio.
Time passes, I smoke too much, prod and poke and eventually reach for the install media
(Lots of shutdowns and restarts in next bit, after each line, also carefully reset and tested every Audio setting.)
Removed M-Audio driver
Installed 10.7.4
Installed M-Audio
All good again.
Later, as a test, connected External drive on its own, no M-Audio
All good.
Second test, added External Drive plus chain to M-Audio
Not good, M-Audio seen but even though sound bars showing on M-Audio software, no sound out to mixer
Removed External Drive from Chain, M-Audio now straight to Mac.
All BAD; sound was terrible,
Disconnected M-Audio
Playing any Mp3 via internal Audio, terrible..
Whatever happened, has thrown the entire Audio system into a mess, again!.
Removed M-Audio driver.
Reinstalled 10.7.4
Reinstalled M-Audio Driver
All good, on internal or external Audio
Disconnected M-Audio
Reconnected External Drive Only
Drive OK, Internal Sound OK.
Removed External drive
Reconnected M-Audio
All ok, internal or External.
Ok, Final conclusion.
When the M-Audio (400FW) is connected to Mac via External Drive (800) the Audio is knackered from that point onwards on 10.7.4, removing M-Audio drivers and re-installing makes no difference, even the Internal Sound is knackered.
Only solution at this point, remove M-Audio driver, reboot, reinstall 10.7.4, reboot, reinstall M-Audio Driver, reboot.
Then its all good again.
My guess is this, and I am probably wrong but it is all I can think of.
When the M-Audio is daisychained the Mac changes a setting somewhere, probably to adjust for high latency, at this point it is written somewhere (either as a file or as DSP bios setting) that is not being reset.
This is why it is completely broken until 10.7.4 is re-installed at which point whatever setting it is that was changed, is reset.
This is all I can think of, I have posted this so that if someone else in the weeks ahead has a similar issue, it will save you the stress and late nights I had this past week.
Take care all.

I was seeing the same problem... I'm a new Logic user, switching from DP, and so it was a minty fresh install of Logic Pro 9.1.7 under ML.
It turned out to be a third party graphics driver that was screwing up some internal process: specifically, the dirver for AirDisplay, an iOS app that lets you use an iPad as a portable monitor. When I removed the driver, the problem cleared up instantly, and I have done 9 hour sessions in Logic since then without a single hiccup.
If you're running a third party driver, remove it, repair permissions and see if the problem clears up.

Is this a bug in Logic Pro?

I use a MAC G5 with Logic Pro 7.2.1 - I play a Korg Triton through a Motu Micro Express Midi interface to access the sounds in Logic as well as my Ivory Grand Piano Plug In. A Mackie Control Universal is my interface.
Ever since I got geared up last March I noticed that when I changed files (song projects) from client to client during the course of the day that my Ivory track would show up transposed a step down. Not limited to the Ivory track sometimes a Bass track, maybe a Bass from Apples Jam Packs, would be transposed.
I never have messed with the transposition of any Logic track, I don't even know how to do that, but I have transposed a song or two in the Ivory Grand Piano Plug In Window.
It was my understanding that once you close the Logic file that it would remember the parameters of that file the next time you opened it.
Well something very telling happened yesterday. In the morning I worked on a clients song. It was a song that early on I may have transposed the Ivory track to help the singer. I closed out of that file and when I brought up a file of another client's work their Ivory track and their Bass track were transposed down a step. Keep in mind that the day before that client's track played down perfectly in the right key and I'm sure I closed the file with it in the right key. And obviously all the audio tracks remained in the original correct key.
Here's the kicker. Fearing that I would mess up my client's song I quickly closed the file without saving any changes and completely closed Logic. When I rebooted Logic Pro and reopened their file the Ivory Grand piano track and the Logic Bass track were in key again!
This has happened quite a few times to me but only now have I realized that completely closing down Logic fixes the problem. ie - If I just ping pong from one file to the next without closing Logic down I have this transposing problem on the Midi instrument tracks.
I'd like to remedy this because it's time consuming to close down Logic between every client. Any ideas? Thanks

InnoMan, I experience frequent problems with Logic Pro that require quitting and relaunching the application. I'd say in a typical 3-hour session working with Logic, I end up doing this about 4 or 5 times. The glitches I experience sometimes involve transposition of notes.
Tell me, when your track gets transposed, does it actually appear transposed, or does it just sound that way? In other words, does the region become magically set to transpose (say, set to +4 or something)? Or, when you go into the region, have the notes been moved?
If neither of these things is happening, but the track just sounds wrong, then that's a problem I've been having. I have a bass line that repeats throughout a track, and it's all in key (A). Recently, I moved that baseline further along in the track. I changed nothing. The first time I listened to it, it all sounded fine. Every subsequent listening, however, sounded like the notes had been transposed to a completely different key. The region had not been transposed, and the notes in the region are still in A. However, it sounds completely off.
I tried completely recreating the region, instead of using a copy from earlier in the track. That worked on the first listen, however again, subsequent listenings and the notes are off.
I'm guessing that upgrading to Logic 7.2.1 might make a difference (I'm using 7.1.1). However, Apple wants me to give them $50 for this experiment, and given Logic's reliability so far (pretty bad), I'm loathe to give Apple more money for this thing.
Anyhow, let me know your experience. Thanks.

Logic Pro X inaccessible after waking from sleep when using an MCU Control Surface

I'm having a problem I cannot seem to get around without force quitting Logic every time. If I have a Control Surface setup as a Mackie Control (v1.0); and if the computer goes to sleep, and then i turn off the controller while the computer is asleep (for any reason), and then wake the computer without turning on the controller first, Logic becomes completely unusable and must be force quit.
My controller in this example is Solid State Logic's Nucleus controller, however it happens with other Mackie Control compatible controllers (i have another one i tested against), BUT not a real Mackie Controller sold by Mackie (i tested with that as well); more details below.
For the SSL controller, Logic automatically sets it up like this:
Now if the computer goes to sleep, and i wake it up, i get the following dialog, which is fine:
After clicking on "Continue" button or hitting the enter key, Logic is rendered useless, as if there is a modal dialog still open somewhere. Clicking anywhere on the gui results in white flashes and nothing else. doing cmd+Q to quit actually makes it try to quit (a save dialog appears), but it never does successfully quit, making me resort to force-quitting. For an example, here's a pic of the file menu at this point:
I also have a regular Mackie Control Unit (MCU Pro) and the strange thing is with that unit, everything works fine after sleep, turning off controller, and re-awakening. However, there is a difference in what kind of dialog is displayed after the sleep, which probably has something to do with this issue.
Here is the setup screen of the MCU Pro:
And here is the dialog for the missing ports after waking from sleep:
This dialog is completely different than the other control surface's missing ports dialog. When clicking on "Keep unassigned" here, Logic resumes working fine.
The project is as minimal as possible; nothing is loaded, all that's there is an empty instrument track and a Control Surface configured.
I'm using a Mac Mini (late 2012)
Processor 2,6 GHz Intel Core i7
Memory 16 GB 1600 MHz DDR3
Graphics Intel HD Graphics 4000
Software OS X 10.9.4 (13E28)
with Logic Pro X 10.0.7
Any help would be greatly appreciated!!

Did you ever figure out a solution to this problem?
I just pulled out my original Emagic Logic Control (MIDI) and I have having the same problem.

How do I make a Tascam FW-1082 "work" with Logic Pro?

I just purchased logic pro and a tascam FW-1082. im trying to get them to work together, but i dont really know where to start. I ran the tascam driver, and did some configuring in logic, but it doesnt seem like they are working together seamlessly. my previous workflow involved a digi 002 with pro tools, and id like to configure logic and the tascam and logic to work like that. so, what do i do?
1.5 G4 12" powerbook/ single 1.8 g5 powermac Mac OS X (10.4.4) logic Pro, tascam FW-1082

It emulates a Mackie Control which Logic supports. Open the Control Surfaces setup/install window, make sure MIDI ins and outs are both connected, turn on the unit and it should appear a in couple of seconds. If it doesn't, manually install it. It's reasonably clear and the 1082 is even listed in the install window. You shouldn't have much trouble.

Linking between two Logic Pro machines for recording...

I am working on a film overseas where I need to run two Macs recording live concerts to Logic Pro simulatinously. How do I effectivly sync these two machines in a master/slave set-up? Can I use MMC, or is there a different protocol?

fuzzynormal wrote:
If you're doing post (and of course you would), you can always synch your tracks after the fact.
But the previous response is on target. If you got a lot riding on the recording I'd suggest getting dedicated audio hardware, (rent if you have to) capturing the tracks with confidence, and then importing those tracks to do your post-mix with Logic.
Anyway, how many simultaneous tracks do you need to grab?
FYI, I've recorded my drummer (8-channels) with a old ProTools rig on a ancient G4, and the rest of the band with my Mackie 16 channel rig running into a MacBook Pro with Logic. Synched 'em in post, no problem.
Depending on the length of the recording and the material being recorded, differences in clock can get you subtle but difficult-to-fix phasing issues with that approach.
Probably not an issue when you're recording a drummer through a Mackie, but if this gig is a big one, there may be very different gear and artists involved, and probably a couple sets of extremely expensive ears listening to the final result.

LOGIC PRO X - MACKIE C4 PRO

Similar Messages

Maybe you are looking for