10.1 Update - Loss of control surface

Hi,
Went through the control surface setup after upgrading, but finding I'm needing to repeat this step every time I use Logic - The Mackie HUI (for Novation LaunchKey) vanishes 100% of the time.
Any ideas?
(LaunchKey is USB connected to a late 2013 MacBook Pro, running Yosem)

jjacto wrote:
Hi,
Went through the control surface setup after upgrading, but finding I'm needing to repeat this step every time I use Logic - The Mackie HUI (for Novation LaunchKey) vanishes 100% of the time.
Any ideas?
(LaunchKey is USB connected to a late 2013 MacBook Pro, running Yosem)
Possibly a corrupted Control Surface file.
With Logic not running follow the procedure below, the cs file will be rebuilt next time Logic starts.
In the Finder, choose Go > Go to Folder from the menu.
Type ~/Library/Preferences in the "Go to the folder" field. Note: type the path exactly as you see it here: ~/Library/Preferences
Press the Go button.
If you are having trouble with a control surface in Logic Pro.
then delete the com.apple.logic.pro.cs file from the preferences folder.

Similar Messages

Can i control surface logic 9 with digi 002 mixer? on snow leopard 10.6.8

Hi I'm trying to connect my digi002 mixer to use it as a control surface with logic 9, is there anyway of doing this?
I have an RME Hammerfall DSP Multiface II, that I'm using as my main sound card, but would like to light it with the 002 and use the 002 converters as well, so that in total i get 16 channels I/O + if I could get control surface of logic with the 002 would be great.....
I heard about the Multi-Client CoreAudio Driver, but not 100% sure if and how it works to control surface logic with 002.
Anyone???
Help please....
Thx...
G

I assume you have working installer discs? If so here's a suggestion:
Clean Install of Snow Leopard
Be sure you backup your files to an external drive or second internal drive because the following procedure will remove everything from the hard drive.
     1. Boot the computer using the Snow Leopard Installer Disc. Insert the disc into the
         optical drive and restart the computer. After the chime press and hold down the
         "C" key. Release the key when you see a small spinning gear appear below the
         dark gray Apple logo.
     2. After the installer loads select your language and click on the Continue
         button. When the menu bar appears select Disk Utility from the Utilities menu.
         After DU loads select the hard drive entry from the left side list (mfgr.'s ID and drive
         size.) Click on the Partition tab in the DU main window. Set the number of
         partitions to one (1) from the Partitions drop down menu, set the format type to Mac
         OS Extended (Journaled, if supported), then click on the Partition button.
     3. When the formatting has completed quit DU and return to the installer. Proceed
         with the OS X installation and follow the directions included with the installer.
     4. When the installation has completed your computer will Restart into the Setup
         Assistant. Be sure you configure your initial admin account with the exact same
         username and password that you used on your old drive. After you finish Setup
         Assistant will complete the installation after which you will be running a fresh
         install of OS X. You can now begin the update process by opening Software
         Update and installing all recommended updates to bring your installation current.

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.

Turning oxygen 25 into control surface

Im trying to make the knobs on my Maudio oxygen 25 control the channel strips in logic. The controller works with playing notes inside of logic but I can't get it to do anything else. Thanks

I set it up manually in Logic and in FCP.
I think where I might have gone wrong is that I manually added the MCU via OSX Audio/MIDI Setup and added connection lines between the MCU and my Motu Ultralite -- from the info I've gathered so far I should not need to add the MCU at all -- only need to select it via FCP/Logic and tell it which MIDI Port to use.
If that doesn't work with FCP, then I'll have to get a separate dedicate MIDI interface and try that.
I do have a request for the Apple developers working on FCP, please, please, please update the Control Surface support code -- it's pretty obvious that requiring the Audio Mixer window to be open to "activate" the MCU is VERY un-Mac like, something I'd expect to find on a Microsoft Windows platform, not a Mac. I wouldn't think fixing this problem in FCP as a patch would be a big deal -- would it?
Thanks, Rob.

Low cost Mackie control surface for FCP 6?

Could someone recommend an inexpensive control surface for FCP 6? Perhaps a bit more expensive than the Berhinger but cheaper than the Tascam.

I've had nothing but grief since installing the FW-1082 and sure could use some help when you return. Here is my current situation (copied from my post on the TASCAM forum which yielded zero responses):
I know the instructions say that the FW-1082 should be plugged directly into the computer interface and that nothing should be plugged into it. Unfortunately my Intel iMac only has one FW400 and one FW800 port. There are other FW400 peripherals such as HDD's and camcorder video capture. With only one FW400 port, it means either I plug the FW-1082 directly into the computer and then connect the FW400 hub to the second FW-1082 port, or plug the hub directly into the computer and the FW-1082 into it. Which ever approach I use, it results in very unstable operation. Sometimes the 'Firewire' LED never lights. Other times the FW-1082 keeps reseting itself every few seconds. Unfortunately I no longer have the option of returning it, so I must find some way to use it with my existing hardware.
I just installed V1.06 of the Mac drivers and 'Fix for Mac OSX 10.4.10 FireWire' from the TASCAM website, restarted the computer, and now the Firewire LED on the FW-1082 never lights. The 'fix' mentioned above rolls back the extension 'AppleFWAudio' to V2.0.1. to resolve a problem with the OSX 10.4.10 update. Unfortunately, I don't know how to restore it to its previous state. Help!
(I apologize for posting this in the FCP forum, but this is the only place I've been able to find fellow FW-1082 users.)

BCF 2000 Control Surface FCP 6

hello all. just picked up a Behringer BCF2000 control surface. i can't seem to get it working with FCP 6.
my search seems to indicate that it "just works" for others. so there's something simple that i'm not doing right.
i have the BCF 2000 in Mackie Baby HUI emulation mode. Control Surfaces allows me to add it. i've tried various combinations of in and out ports. i have the "add key frames" toggle on in the audio mixer. nothing.
if you have experience / insight please help.
R.

DB, I was just pointing out my experiences. I couldn't remember at the moment which emulation I was using.
I may try LC now just to see if there's any difference.
Roland, here is the link to the document about changing emulation modes.
http://www.behringerdownload.de/BCF2000/BCF2000Emulationmodes.pdf
I am using the Mackie Control for Cubase/Nuendo. You may need to update the firmware to use it with your Mac. Here is the software download page:
http://www.behringer.com/05support/bc_download/bcdownloads.cfm?lang=eng
tim

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

Logic 9 with Roland VS100 Control surface Issue.

Hey guys, Ive got a Roland VS100 to use with Logic 9 here.
The VS is setup directly according to instructions as well as Logic.
The issue is when I push play on the VS 100, Logic stays in the first second and just stutters, the transport will NOT move down the timeline.
Ive checked all the syn setting in Logic and mad sure the VS 100 was set to " other" for Control Surfaces which it uses Mackie Contorl Universal.
Any ideas? Sonar forum is no help. Loop is OFF before anyone asks

I was fortunate and only have to do it once. I did this over a year ago, but from what I remmber I updated the operating system on the VS100 first, then the drivers for my mac.
I use an AKAI MPK25 for midi. I directly connect it into the mac using one of the USB ports. No issues and works great with Logic.
I never tried to connect a midi keyboard directly to the VS100, but I know you can probably try using Midi in/Midi out capabilities, but I dont understand the reason why.. are you going to use the BK5 to trigger functions from the VS100?

Avid MC Transport Control Surface now working in CS 5.5

Not sure if anyone is interested, but because Adobe doesn't have a EUCON integrated support, it greatly limits the control surfaces that can be used with it.
I googled a bunch of different things but in the end it seems like the general conclusion was that the MC Transport doesn't work with Premiere Pro, not a big deal if you don't have one, but really sucks if you do have one and use Premiere for a lot of your work.
However, following the age-old adage of "never say die" I finally figured out a work-around that has my Avid MC Transport working pretty darn good with Adobe Premiere CS 5.5 on my Mac.
I posted it here: on creative cow where you can see the whole thread: http://forums.creativecow.net/readpost/3/911511
Hi Andree,
I had the same problem but figured it out, you can see it here http://wp.me/p1hbRg-e
or I'll paste it here for you as well:
I recently made the switch from PC to MAC for the long-form documentary I'm making. A decision that so far, I definitely regret. But more on that later.
For the moment I thought I'd start posting notes about problems I've run into and solutions to them that I've found in case any one else runs into these same problems.
I purchased the Avid/Euphonix MC Transport for use in my editing as having a jog/shuttle definitely speeds things up remarkably once you are accustomed to them.
However I didn't notice that Adobe Premiere was not supported and this is my editing program of choice although I do have FCP and Media Composer 5.52.
I googled around and even contacted Euphonix/Avid support and no one seemed to have a solution.
In frustration I then ordered a Contour Shuttle Pro v2 (which is sort of like downsizing from a Porche to a Honda. Both great cars, but which one would you kick out of bed first? Exactly.)
So while waiting for international shipping I tried a bit of a wild idea and I installed the drivers for both the Bella Pro Premiere keyboard (which I don't have) and the Contour Shuttle (which I don't have either) and then began customizing the MC Transport commands to match the command keys in Adobe Premiere.
As a note; you might not need to do this on your system. I'm using a Mac 12 core and this workaround only worked once I installed those drivers but logically speaking you shouldn't need to do it.
And hey! It works!!!!
Some things aren't as perfect as they are in Avid or FCP such as the shuttle wheel shifting to different speeds smoothly. But damn! The jog wheel works perfectly.
Customizing the Soft Keys just involves ensuring that Adobe Premiere Pro CS 5.5 is open and then choosing the soft key around the wheel and once it is highlighted in the EUCON controller, then assigning a KEY command.
For example your center three keys above the jog wheel should have J, K, and L assigned accordingly.
And however you wish to customize it after that. I use for cutting at timeline (CTRL + K), next edit (page down), previous edit (page up) and it is working like a charm.
All the other soft keys including shift command respond the same.
To program the jog wheel. Select it and choose Command, select Wheel from the drop down, then select jog right and choose special command and pick "right arrow" and then repeat for select jog left and choose special command and choose "left arrow."
The shuttle you have to choose the shuttle and again add a wheel command and then in choose shuttle and create a new shuttle wheel command. Then from shuttle drop down, choose for Section 0 add key and set it to K (stop), then for Shuttle Section 1 add L key once and for each shuttle section add one more L key. Shuttle section 7 has LLLLLLL assigned to it.
For the shuttle -1 Section choose J and for each minus section following that add one more J.
It's not perfect but it certainly does what I need it to do!
Hope that helps anyone else out there.
Best,
Darius

Thanks Pepe, seems to be a quick workaround! (FWIW in Logic 7.1, the command I see is Logic→Preferences→Control Surfaces→Rebuild Defaults. I assume that's what you're referring to.)
It'd be great if Apple/Tascam fixed this, but it only takes a second to rebuild the devices, so it's no biggie.

How can I manually enter MIDI channel number in Control Surface expert Value Change field?

I am creating a software interface for a multidimensional controller which can transmit many linear values at the same time. I can not use Learn mode because it always sends data from all sources, but I can split them by MIDI channels. I would like to manually enter controlling values into Control Surface expert view.
I seem to be able only to input the message, but not MIDI channel on which it is transmitted.

Stupid me, it's hex... so 80 is Note Off ch 1, 90 Note On ch 1 etc

Which control surface do you use, would like to use or have used for audio?

I am shopping control surfaces for mixing audio in Premiere Pro CC. I am buying used so I would sure like to get it right the first time. I am looking for feedback from those who have used a control surface as well as those who have just looked around. I have searched high and low for information from Premiere Pro users but have found very little. Even the Audition folks have not shared much information about experiences with audio control surfaces.
Here are some consoles I've looked at but cannot determine compatibility (due to lack of information):
Mackie Control Universal MCU Pro 8
Digidesign Command 8
Digidesign Digi 002 Pro Tools Console
M-Audio ProjectMix I/O Control Surface
Icon QCon Pro USB Midi Controller Station
Behringer B-Control Fader BCF2000
Radikal Technologies SAC 2.2 DAW controller
Avid Artist Mix Control 8 Fader Euphonix DAW Mixing Control Surface
Tascam FW-1884 Firewire Control Surface
Tascam FW-1082 Firewire Control Surface
CM Labs Motormix
CM Labs Motormix 2
CM Labs MotorMate
Novation ZeRO SL MkII MIDI DAW Control Surface
Nektar Panorama P1 USB Midi DAW Control Surface
Alesis Master Control
If you have experience with any of these consoles, or have any to add to the list, specifically with Premiere Pro, please leave a note here. I believe there will be others who will check this discussion looking for the same answers as I. Documentation of these control surfaces is very thin when it coms to discovering if they are MCU or EUCON protocol (or other) - and even if I was able to discern a flavor I still do not know which features will work in Premiere, such as transport controls, faders, plug-in modifiers, et al.
So I guess my goal here is to come up with a list of work/don't work features for each of these control surfaces and more so we can make informed bang for the buck decisions. My budget for a used control surface is $300-400, but I'd be willing to go to $500-600 or more if the features/integration were significantly better.
Thanks!

Here is the list with the responses I have received from the manufacturers, (3) so far.
Mackie Control Universal MCU Pro 8
The MCU Pro uses three different types of MIDI operating protocols (Mackie Control, HUI, and Logic Control). We have not tested the MCU Pro here in Tech Support with Premiere Pro. You will want to contact Adobe directly to see if they support the Mackie Control, HUI or Logic Control protocols with the Premiere Pro software. It is up to the manufacture of the software on how well these MIDI operating protocols are implemented into the software. With contacting Adobe directly you will be able to see what control surfaces are supported with their software.
Digidesign Command 8
Digidesign Digi 002 Pro Tools Console
M-Audio ProjectMix I/O Control Surface
The Project Mix I/O is a discontinued product. However, it should work properly with basically any DAW program. I can't speak to specifically Premiere Pro, but we have a few customers who use that combination and those customers report it works just fine.
Icon QCon Pro USB Midi Controller Station
Behringer B-Control Fader BCF2000
Thank you for your email! Yes, you are able to use the BCF2000 to control Adobe Pro CC. YOu will need to program the controller into Mackie Emulation mode. Mackie Emulation will allow full functionality within your software. Attached you will find a PDF showing each emulation mode. Here are a few informative links explaining setup and application:
http://forums.adobe.com/thread/1286249
http://helpx.adobe.com/premiere-pro/using/control-surface-support.html
The former will provide a better understanding of connectivity.
Radikal Technologies SAC 2.2 DAW controller
Avid Artist Mix Control 8 Fader Euphonix DAW Mixing Control Surface
Tascam FW-1884 Firewire Control Surface
Tascam FW-1082 Firewire Control Surface
CM Labs Motormix
CM Labs Motormix 2
CM Labs MotorMate
Novation ZeRO SL MkII MIDI DAW Control Surface
Nektar Panorama P1 USB Midi DAW Control Surface
Alesis Master Control

How do I update my ActiveX controls without breaking existing VIs?

Hi, I'm new to LabView. I've inherited a labview application that makes use of several user-written VIS. All these vi files use an ActiveX control. For better or worse, the way they've done it is to put a ActiveX Container on the front panel. They then picked "Insert ActiveX Control", and picked the correct OCX. In the block diagram, they set up a "Invoke" Node and wire the ActiveX control to that.
The problem occurs when I update the ActiveX control. I added a couple of methods and reregistered it. When I run one of my vi files, I get:
Error 0 occurred at VI Open & Init Spinstand
Possible Reasons....
I then thought that going to the front panel and deleting the ActiveX control and reinser
ting it would work. Instead I got the message:
Error 1598667368 occurred at VI open & Init...
I should point out that I'm not even attempting to use the new function yet; I'm just running an old .vi file with the updated ActiveX control.
The version of LabView I'm using is 6.0.2. Can anyone tell me what's going on? Is there a way to gracefully update the ActiveX control? I'm I adding ActiveX controls in the best way?
Any help or references would be greatly appreciated.
Thanks,
Andrew Walker

Updating *.OCX OR *.DLL Component When Active X Automation Interface has Changed
Given that you have changed the ActiveX automation interface, e.g: by appending new functions, then, the original 'registered' ActiveX server automation interface is no longer compatible with the new one.
In this case you must: (1) �un-register� the original interface; (2) Copy the New *.OCX/*.DLL File over the previous ones; (3) Then �re-register the new interface�; (4) After that you must visit ALL your LabVIEW Diagram �PROPERTY� and �METHOD� ActiveX automation nodes and re-reference those same functions.
These FOUR (4) Steps are further explained below:
1. Unregister the *.OCX or *.DLL file by running the command
Regsvr32 /u ��
Make sure that points to the full path name for your *.OCX or *.dll file. You must use the opening and closing quotes if your file path has spaces.
2. Copy the new *.OCX or *.DLL files over the old ones
This means that you will be over-writing the old *.OCX or *.DLL with the new files. Replacing these files is re-commended so that you do not end up with multiple copies of the same file.
3. Register The New *.OCX Controls
Register the new controls by running the command
Regsvr32 ��
This will now honor your new ActiveX automation interface in place of the last one.
4. Re-Visit All �PROPERTY� and �METHOD� Nodes and Re-Reference the same functions that appear in those nodes
This means that you will be right-clicking on all the existing PROPERTY and METHOD nodes and choosing the functions accordingly from the drop-down list-view/menu. If the list view is grayed-out, then Steps 1 to 3 did not take!
NB: GOTCHA FOR *.DDL Users
If you have sub-VIs that use the *.dll Ref icon then you will have to cut and re-insert this reference control in all those sub-Vis. A quick way is to copy the top level *.Dll ref icon and paste it over the control and indicator versions of the same in those sub VIs.
These four Steps plus the 'Gotcha Step' have worked consistenly when I have had to update ActiveX controls featuring a changed automation interface.

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.

Using Logic Pro 9 and Tascam DM-4800. Can't get the Tascam to work as a control surface via firewire... any help would be appreciated! Thanks!

The DM-4800 and Logic see each other, the firewire shows as 'locked' on both. Can pass audio back and fourth, no automation from the Tascam though. I know its either a midi setting or control surface settings... but I'm stumped. Newbie at Logic here. Any ideas what to check? Thanks in advance!

Plug in the usb lead.

Getting my control surface to work properly

I have a usb kebyboard, alesis photon 25. when i plug it in with audition running it says midi channel one is being triggered at the bottom when i press a key on the keyboard so i know it is picking up a signal. i have enabled everything that i can think of via the sequencer window and i just cant get the keyboard to trigger the vsti, please any suggestions would be much appreciated. thanks

To see how to handle Control Surface have a look at this:
http://manuals.info.apple.com/en/ControlSurfacesSupport.pdf
You can find it in Logic Documents folder too (it's on installation disk).
The problem is if the system recognizes the BR in MIDI Audio Setup or if some drivers are needed.
cheers
rob

10.1 Update - Loss of control surface

Similar Messages

Maybe you are looking for