LP X 10.1 not working with MCU Pro control surface

Since installing LPX 10.1 my MCU Pro (firmware version 4.0.2) no longer works with Logic. Logic is still reporting the existence of a "Logic Control" in the control surfaces list, but doesn't send anything to or receive anything from the controller, and the controller itself remains completely unresponsive.
I've read multiple reports of other MCU Pro owners having the same problem after installing 10.1. Has anyone found a way around this, or do I just have to wait and hope that Apple will address it to restore the functionality of my studio?
(I'm also running Yosemite 10.1 for an OS, BTW.)

Thanks for the link, although I already knew about that thread. The solutions listed therein did not help.
However, I MAY have resolved my problem (although I guess only time will tell for certain). I was running the next-to-latest firmware for the MCU Pro (4.0.2) and assumed that there was unlikely to be anything in the most recent 4.0.3 firmware that would help, since it still predated the release of 10.1. However, I finally went looking for the 4.0.3 firmware this afternoon, and one of the items in the short list of updates was:
"Fixed soft reset bug that could cause the MCU Pro or XT Pro to freeze when being reset by a DAW application."
That sounded exactly like what I was seeing, even though I'd not seen it happen prior to installing LPX 10.1. So I managed to get the MCU Pro firmware updated; Logic could send MIDI to it once the MCU Pro was in an update mode rather than trying to act as a control surface, fortunately. After updating the firmware, selecting for the unit to act as a Logic Control again and then re-adding it to Logic's control surfaces setup, it once again seemed to lock up ... that is, until I then shut down and restarted both it and Logic Pro X. At that point, it started working again (hallelujah!), and has continued to work normally through a couple of shutdown and restart cycles since. So for now I am keeping my fingers crossed, and would recommend to any other MCU Pro owners that, if they aren't already running the latest firmware for their MCU Pro, to try doing that upgrade first before they despair.

Similar Messages

USB superdrive not working with Mac Pro

Is there a trick to getting a USB Superdrive working with a Macpro?
The drive in the Macpro no longer ejects and have tried connecting the USB drive to both the front and back ports - does it not work with Mac Pros?
Any pointers in the right direction would be much appreciated.

I had a problem my superdrive. It would play dvd's and cd's that were already burnt but would not burn blank DVDs or CDs- in the recent past it had no problems burning. In addition, the Finder would not display the superdrive. When I put a blank disc in it would go to Disk Utilities and would not allow burning. With help from Apple I discovered the problem-- The settings in CDS & DVDs had been changed from When you insert a blank DVD/CD "Ask what to do to to "GO to Disk Utilities". If this sounds like your problem try changing the settings to this:
Try going to; System Preferences/ CDs & DVDs
Change these two settings to this:
When you insert a blank CD: Ask what to do
When you insert a blank DVD: Ask what to do
NOTE: If they are already set to this you probably have a different problem. If they are set to Go to Disk Utilitiy this is probably a solution.
And
Then go to Finder Preferences
Make sure that under "Show these items on desktop:" that the checkbox for CDs, DVDs, and iPods is checked.
Try to burn the DVD again (reload Disc- perhaps restart) and try again.
Don't know how these setting changed but they did. It worked for me.
Message was edited by: pj176

Lightroom (CC) 2015 is not working with Macbook pro 2015 model ! any clues about it ??

lightroom (CC) 2015 is not working with Macbook pro 2015 model ! any clues about it ??

Ahmed
Generally signing out and signing in (signing out and back into the Creative Cloud application ) will fix this. If it isn't resolving the issue for you, let us know what you see and we can try something else.
Pattie

Adobe Audition 6 and Mackie MCU Pro Control Surface

I have recently opbtained a Mackie MCU Pro Control Surface, for use with Adobe Audition CS6. At first I used it with an HP i7 running Windows 8. It worked like a dream, doing everything that I expected of it. Now, I have plugged it to my Laptop, running Windows 7 Home Premium. Sadly it refuses to respond to any commands in either direction. The PC giives the two-note ackowledgment that the USB is comminucating. However, that's as far as it goes.
Audition on the laptop knows what's connected and all options offer the USB connected device correctly named. Whatever I do, there is no sign of the Mackie MCU Pro waking up. It just seems to sit there, probably thinking it's a 'fridge or a toaster.
Has anyone else used this combination and did it work OK? I'm sure I'm mssing something obvious and there's an 'enable' of some sort. Can anyone offer any thoughts?
Thabk you for your time and help.
Alan

I have completely reset the Laptop (Packard Bell Easynote) to factory defaults and reinstalled Audition from scratch. It is now exactly the same as that installed on the desktop, except that the Laptop is Windows 7 (64-bit Home Premium) and the Desktop is Windows 8.
I was hopeful that a fresh install of Audition CS6 would set the Mackie Control Surface off and running. Sadly, it is not the case.
So:
With precisely the same software (same source and same S/N) the Mackie worlks correctly with the Desktop but doesn't work at all with the laptop.
Just for the record, when plugging the USB from the Mackie to the laptop, it produces the usual two-tone acknowledgement that it is seeing something it recognises, but that is as far as it goes.
I'm now at a loss. Does anyone have any further thoughts?
Many thanks,
Alan

CISCO Box not working with Infrared Remove Control Repeater

There was an Infrared Remote Control Repeater set-up in my newly purchased house. It works for my LG DVD player, but does not work with my CISCO CHS435HDB box. Are there any work around for this? Should I change to a different box?

If you are using a repeater, make sure the piece that is relaying the IR signal is pointing directly the font of the Cisco box and nothing is plugged into the IR input port in the back of the box.
Anthony_VZ
**If someones post has helped you, please acknowledge their assistance by clicking the red thumbs up button to give them Kudos. If you are the original poster and any response gave you your answer, please mark the post that had the answer as the solution**
Notice: Content posted by Verizon employees is meant to be informational and does not supersede or change the Verizon Forums User Guidelines or Terms or Service, or your Customer Agreement Terms and Conditions or plan

External Monitor Not Working With Macbook Pro

My computer was working fine with an external monitor, then my computer froze, and I had to hold down the power button. When I turned it back on, my computer would not work with an external monitor. I've tried different cables, so it's not the cable. The monitor is being detected by the computer, but nothing is showen on the external monitor. When connecting the monitor to the computer, the computer's screen goes blue, then turns back to normal. I
I cannot reset the SMC by removing the battery, I do not have the confidence to remove my battery, and do not have the time to send the computer to someone else to do it.
I also tried updating my OS from 10.7.4 (Might've been 10.7.3) to 10.7.5.
My computer is a MacBook Pro (13-inch, Mid 2010), running OS X 10.7.5 Lion.
I need to get this problem fixed ASAP, any help is appreciated.
Kind Regards,
Sergee237

I forgot to mention, I'm connecting the monitor via MiniDisplay -> HDMI. I've also tried USB -> HDMI and USB -> DVI -> HDMI but none of them seem to work.

External isight not working with Macbook Pro early 2008

My external isight is not working with my Macbook Pro early 2008 (2.4 GHz, Intel Core 2 Duo, 6 GB RAM, OSX Lion). It goes warm when plugged into the firewire port but is not recognized in system prefs (lists as "unknown device" and also does not turn on (green light. I tried resetting PRAM and all the other stuff as suggested here but no luck. It used to work fine on a 1st generation Macbook and I remember that one of the first times I tried it with this machine here it turned on for a few secs (green light) but then it just simply stopped.
Unfortunately, I have no other firewire device to check the port.
Any ideas, dear community?

Our (old) external Firewire iSights can be sensitive to dust, shock, vibration, humidity, and other environmental factors in storage. (I store my spare in its original plastic shipping case with a new desiccant pack on a solid shelf - never in a desk drawer or other container that moves.)
You have tried several good things and may be finding that your old iSight needs work.
Here are the alternatives I can offer. Consider any you have not tried in any order you like:
(1) You can try Apple's suggestions from http://support.apple.com/kb/HT2090
Test in more than one user account and with more than one Apple softwre application.
(2) My expanded suggestions here: http://www.ralphjohns.co.uk/EZJim/EZJimpage4.html
(3) Reset Firewire ports using the info from this old archived Apple article: http://web.archive.org/web/20090331211534/http://support.apple.com/kb/HT1317
(4) If you have no local Apple Authorized service Provider who can help you, other service options are here: http://www.apple.com/support/isight/service/
(5) Consider a new USB cam with current warranty such as one of these: http://www.mac-compatible-web-cam.com/
Message was edited by: EZ Jim

My canon EOS DIGITAL ver 24.0 in not working with mac pro os x

MY CANON EOS DIGITAL SOFTWARE VER 24.0 IS NOT WORKING WITH THIS VERSION OF MAC OS X

Atiya wrote:
I have a Mac Pro (2 x 2.4 GHz Quad-Core, model identifier MacPro5,1) purchased in late 2010 and a 24" LED Cinema Display. The Mac Pro has three video ports--a full-sized DVI and two mini DVI. When I plug the Cinema Display into either of the mini DVI ports, I cannot get a picture, although the iSight camera works fine. If I plug another monitor into the full-sized DVI port the computer believes that is the only monitor. The Cinema Display works fine with my MacBook, so there is nothing physically wrong with it.
Is it not possible to use this monitor with a Mac Pro without an adapter, even though the Mac Pro does have mini DVI ports?
I use a 24" LED with my Mac Pro. Works a treat!
Does this help you? http://support.apple.com/kb/TS2400
EZ Jim
Mac Pro Quad Core (Early 2009) 2.93Ghz Mac OS X (10.6.6); MacBook Pro (13 inch, Mid 2009) 2.26GHz (10.6.6)
LED Cinema Display; G4 PowerBook 1.67GHz (10.4.11); iBookSE 366MHz (10.3.9); External iSight; iPod4touch4.2.1

External Display not working with MacBook Pro 13" (early 2011)

I just bought the current MacBook Pro 13" (i7 processor). My external display (Benq 20"W, 1600x1050) always says "No Signal Detected!". I've tried it with a DVI-Adapter (Griffin Video Display Converter) and with a VGA-Adapter (LMP Mini DisplayPort-VGA-Adapter). With lower resolution I once got a picture (but with weird lines). On my old MacBook (white, 2.16 Ghz) there was never a problem with this display (also OS X 10.6.6). Who can help?

Check this post if you want more info:
http://discussions.apple.com/thread.jspa?threadID=2774718
The gist is that DVI is currently very iffy through Thunderbolt. Mini display -> mini display OR mini display -> HDMI should work fine. It's most likely not your adapter itself but the fact that it's DVI.
If you can, get a mini display -> HDMI adapter and try that (assuming your external has HDMI).
I should hear back tomorrow or Monday from apple engineers with more specific info about this issue and I will update then.
BTW- DVI anywhere in the chain will make things fail. Mini Display -> DVI and a DVI/HDMI cable won't work with any reliability (I've tested it on three completely different monitors).

Rocketfish adapter not working with MacBook Pro 13 inch

I have a rocketfish HDMI to mini displayport adapter. I have tried to connect it to a 22 inch monitor and a 50 inch TV as an extended monitor but the MacBook does not recognize the extended display.
Any ideas on how to resolve or is the adapter not supported?

Check this post if you want more info:
http://discussions.apple.com/thread.jspa?threadID=2774718
The gist is that DVI is currently very iffy through Thunderbolt. Mini display -> mini display OR mini display -> HDMI should work fine. It's most likely not your adapter itself but the fact that it's DVI.
If you can, get a mini display -> HDMI adapter and try that (assuming your external has HDMI).
I should hear back tomorrow or Monday from apple engineers with more specific info about this issue and I will update then.
BTW- DVI anywhere in the chain will make things fail. Mini Display -> DVI and a DVI/HDMI cable won't work with any reliability (I've tested it on three completely different monitors).

Scanning not working with Acrobat Pro X or Photoshop?

My Epson Perfection V350 scanner is listed as a supported scanner on Apple's site.
After installing the latest versions of Acrobat Pro X and Photoshop Extended, the scanner is not available to either app. After several useless exchanges with Adobe online support, I called phone support tonight. I was told that neither Acrobat nor Photoshop support scanning in Mountain Lion and I should use Apple's Image Capture. If that is true it should be considered a catastrophe by Apple, Adobe, and Mac users. I tried installing the latest Photoshop TWAIN driver with not luck. I updated to Mountain Lion because scanning wasn't working in Lion. Appalling.
I have Epson driver 8.0 installed. It is all I can find. If anyone knows of something more recent, or a workaround for this nasty problem, I'm all eyes.
Acrobat Pro X is 10.1.4 and Photoshop Extended is 13.0.1

Satchmo wrote:
Matt, you are right about the Epson Scan Utility. I didn't have it installed. I installed it before you posted, and the scanner appears and works in Acrobat, but Photoshop still can't see it. So, half way there. Thanks. The driver was the same as I had installed.
Is there any part of your version of Photoshop 64 bit? The Epson TWAIN driver is only 32 bit, so that may be the difference. You mentioned in your first post that you installed the latest Photoshop TWAIN driver. I wonder if that is the problem. Is there a way you can go back to an earlier version of that part of Photoshop? I am not familiar with Photoshop.
If you visit the Drivers and Downloads for the Epson Perfection v350, you find no driver download but this message:
Description: The latest Mac OS X ICA scanner driver for your Epson product is available only via Apple's Software Update. Here's how to get it:
Connect the all-in-one or scanner to your Mac and power it on.
Select the menu, then Software Update.
Follow the on-screen instructions to install the available updates.
Note: Software Updates may find multiple updates for your system. You may choose to install all or some of the updates by clicking onShow Details.
Compatible Systems: Mac OS X (v10.8.x)
That is a load of hooey: Software Update installs nothing for the scanner. And it doesn't supply the requisite Epson Scan Utility.
I am well aware of how Epson's pages are laid out. That is why I gave you the direct download link. The ICA drivers are for Image Capture. They do not use the TWAIN technology. When you are on EPSON's site, you have to override the browser sniffer and say that you are using OS X 10.6. Then you will see the Epson Scan software. Much easier just to give you a direct download link from their ftp server.
And yes, the ICA drivers probably were already installed with Mountain Lion. I think a universal ICA driver is supplied as part of ML for Canon and EPSON scanners. You can check by looking in the /Library/Image Capture/Devices folder for the EPSON ICA driver. You will find the TWAIN driver you just installed at /Library/Image Capture TWAIN Data Sources.

ExternalInterface in C# form does not work with debug ActiveX control

Hello,
I have a C# form that is a container for the Flash ActiveX
control. Everything works find as far as communication between the
two (container and Actionscript) if I use the release version of
the ActiveX control. If I use the debug version, the container does
not receive call events. Obviously I need to be able to debug both
the C# and actionscript code simultaneously. I have searched this
forum (and others) for any insight, but nothing glares out at me.
Could this possibly be a security issue?
Brad

I thing I have a solution for you. I created a note on it end of November (unfortunately, our systems have not replicated it to the outside yet). Here is the content of the note:
Symptom
Using Visual Studio .NET, database logon code is not recognized.
Crystal reports Viewer database logon parameter screen prompts for login.
This symptom is only observed when using Crystal Reports 2008 Service Pack 2.
Crystal Reports 2008 with Service Pack 1 works as expected.
Reproducing the Issue
Use Crystal Reports 2008 SP2 to create a report with dynamic parameter(s)
Use the following code from the Crystal Reports SDK for VS .NET
Dim crDatabase As Database
Dim crTables As TablesDim crTable As Table
Dim crTableLogOnInfo As TableLogOnInfo
Dim crConnectionInfo As ConnectionInfo
crReportDocument.Load("<path>")
crReportDocument.Refresh()
crConnectionInfo = New ConnectionInfo()
With crConnectionInfo
.ServerName = "<New Server Name>"
.Password = "<password>"
End With
crDatabase = crReportDocument,Database
crTables = crDatabase.Tables
For Each crTable In crTables
crTableLogOnInfo = crTable.LogOnInfo
crTableLogOnInfo.ConnectionInfo = crConnectionInfo
crTable.ApplyLogOnInfo(crTableLogOnInfo)
Next
CrystalReportViewer1.ReportSource = crReportDocument
The above code works with Crystal Reports 2008 SP 1
Resolution
Add .DataSourceConnections(0).SetConnection to the code as follows:
For Each crTable In crTables
crTableLogOnInfo = crTable.LogOnInfo
crTableLogOnInfo.ConnectionInfo = crConnectionInfo
crTable.ApplyLogOnInfo(crTableLogOnInfo)
Next
''This is the line of code to be added ****
crReportDocument.DataSourceConnections(0).SetConnection("Sever Name", "Database Name", "Use ID", "Password")
CrystalReportViewer1.ReportSource = crReportDocument
The issue has been submitted for a resolution.
Tracking number is ADAPT01333806.

Old MagSafe Airline Adapter not working with MacBook Pro Retina

I've got an old MagSafe Airline Adapter (one I bought when it first came out) that I'm trying to use with my MacBook Pro Retina (using a MagSafe to MagSafe 2 Converter). Sometimes the light is green, sometimes it is off, sometimes the battery icon in the menu bar shows plugged in, sometimes not, but in any combination, the machine is not maintaining charge; the battery discharges at a normal rate for just being on battery. For giggles, I borrowed my seatmate's year-or-two-old MagSafe adapter (the one with the right-angle plug) and plugged it into my machine (also using the MagSafe to MagSafe 2 converter). The light on that one turns orange, and though the battery icon shows "Not Charging", the battery is maintaining charge with the newer adapter. (My adapter, BTW, is able to maintain the charge on her 13" MacBook Pro.)
Was there a change to recent versions of this adapter to make the new ones work with the Retina MacBooks where the old one will not?

the green light on the mag safe turns on?
you should reduce your usage to a very minimal amount as I'm sure the airline doesn't output a strong enough signal for you to be running full screen films with high res. Maybe you should close your macbook P and see if it is charged after a little while of not using it.
turn your screen lights down, turn the sound gHZ down, quit all the downloadin'.
if you must run flash make sure you have the latest version (from the adobe site).
You're computer is intense and if you use it more then it's gaining, of course it going to be draining .
But this is probably moot since you're probably on said plane now. or was.
I'd imagine if you're not satisfied with the product you should return it detailing your situation.

Novation Remote 25SL Not Working with Logic Pro (Logic Automap)

Hi,
I can't seem to get my new Novation Remote 25 SL to work in Logic Automap mode.
I have the Remote SL in Logic AutoMap (template #39). When I launch Logic Pro 7, The Remote SL shows : "Logic AutoMap" on the Left LCD display, and nothing else happens, it seems to be frozen at this state. The Up/Down arrows on the Left side don't change anything.
Any clues why this is happening ?
I have read many posts on this and other forums of user issues in setting the Remote up properly, and have it work in Logic Automode. Tried many configurations, and settings, re-installed sw, OS 1.0.13, but no luck so far.
I would like to hear from Logic Pro 7 users who have successfully setup their Remote SL with Logic Pro 7.2.1 in Logic Automode, and are working with this system without any issues.
This will be very helpful in figuring out if there is something wrong in my settings, or if the unit itself is defective, or I am doing something wrong during the installation of the software ? I have been trying to get this thing to work for the past two days, with no success so far.
The Remote SL should be a wonderful controller for Logic Pro 7 (once it works !) so, I'm being as patient as I can with this thing.
I'm using Logic pro 7.2.1 on a Mac G5 2.5 Quad, Mac OSX 10.4.6
Thanks.

Hi Blaze,
I tried your settings, but no change, the Remote SL is still frozen showing :
"Logic Automap" on the left LCD .
You mention setting "Mixer View 64" well the parameter I see is called :
"Mixer View Fader" which I guess is the same one you are referring to. I set it to 64, it was set to 8, but has not changed anything. Still having the same problem. This problem is dragging into Day 3, what a bummer.
Thanks.

USB Interface Not Working With Logic Pro 9

Hello,
I've had a Tascam US-1641 for several years now with absolutely zero issues on my old PC. Ever since I upgraded to Mac (early 2011 17 inch Macbook Pro running Snow Leopard) I've had nothing but problems with the US-1641. No matter how many times I uninstall-reinstall the drivers and what USB port I plug it into, whenever I turn on the device and it's connected to my Macbook, it crashes my operating system and it freezes everything I was doing. Logic Pro doesn't load and when it sometimes does (10 minutes later), it immediately crashes when I click anything.
I've tried several tips to fix it and nothing worked. The most popular choice was select the default input/output in Logic to the system audio, then quit Logic, turn on the interface, then restart Logic. No such luck. I have to reboot my machine at least 5 times, uninstall/reinstall the driver and hope it works to use the interface. I thought it was the operating system, so I upgraded to Mountain Lion and installed the new driver for Mountain Lion, after of course deleting the other drivers and removing all previous data, and it is still giving me the same problems.
I don't have the money to afford a replacement model or a different interface from a different company, so I'm hoping you guys can help me figure out what exactly it is that's causing the interface to freeze my operating system and crashing my Mac whenever I try to use it. I am getting extremely frustrated at this and as much as I love OSX and Logic, what good is this piece of software if I can't use it? I need help.
Thank you.

The problem lies with Tascam and their inability to write stable drivers for OS X... and isn't anything to do with Logic Pro ..
As you know, you are not the only person to have had this issue and the reality is, while the 1641 might work fine with Windows, when it comes to OS X Macs.. it's an entirely different story... depending on the version of OS XS you are running.
The one tip I have read, that seemed to fix it for most people.. (Though not all) is as follows;
(Thanks to Paulypaulpaul for this)
-uninstall your tascam driver 2.10
-restart
-install driver 1.03
-restart
-plug in your tascam
-goto where you download your drivers (http://tascam.com/product/us-1641/downloads/), scroll down to the bottom where it says firmware, Download the firmware 1.02 (3rd from top under firmware), install it. your control panal should now read 1.03 for your drivers and 1.02 for your firmware.
-install drivers 2.10
-restart
Follow each of the steps exactly.. including all restarts when indicated..
...and good luck...

LP X 10.1 not working with MCU Pro control surface

Similar Messages

Maybe you are looking for