No Communication with CP100 Control Surface

We've been using the CP100 with Final Touch, but Color isn't talking to it. The dialog still comes up asking if we would like to use the CP100. I hit the Yes button and...nothing works. Any clues?

I had luck getting it to work like this...
- Connect the CP100 to the Mac via Ethernet Port 1 and the TDLAN port on the panel
- Right-click on the Color application and Show Package Contents
- Go into Contents-->MacOS-->
- Change the file named 'openNDRVSocket' to 'openNDRVSocketTemplate'
At this point, launch Color and you'll get the CP100 prompt for a new device. This time, when you click yes, it should prompt you for an administrator password.
After this, the panel has been working well.
--Tex

Similar Messages

  • Logic Unexpectedly Quits  / Conflict with Motomix control surface

    Logic unexpectedly quits when I try to open a new song.
    So I installed ProApplicationSupport and I trashed the Logic preferences. But it didn´t help.
    But I found out, that Logic does not have this problem
    - after deleting in Logic the control surface for the CM Motormix that I use in my setup; no problem with other control surfaces (But having the same problem again after reinstalling the control surface for the Motormix)
    or
    - launching Logic with another user (I am working with the admin user)
    What can I do?
    Thanks for help!
    Powermac 2 x 2.5 Ghz   Mac OS X (10.4.8)   Logic 7.2.1

    Hi
    Tried this?
    http://support.apple.com/kb/TS3968
    Also: Basic troubleshooting steps:
    http://support.apple.com/kb/HT2375
    Perhaps you deleted some other, more important files at the same time?
    CCT

  • Communication with motor control using RS-232

    I need to use labview to communication with a stepper motor drive using the serial port RS-232. Could someone please get me started I'm not sure if a should use VISA or instrument I/O. And if I use one of those, how would I set it up?

    Hi Phil,
    Outside of LabView, how do you communicate with or control the motor drive?  If you are able to use software like HyperTerminal or Procomm, then using the VISA serial communication tools will be the simple way of implementing your solution.
    Here are some links which may provide clues on how to proceed.  You can also do a search on VISA Serial communication.
    Happy wiring!!
    JLV
    LINKS:
    Link 1: Although this one talks about an error, it does provide instructions on how to setup the VISA session:
    http://forums.ni.com/ni/board/message?board.id=170&message.id=99660&query.id=0#M99660
    Link 2: Here are some examples: (good starting point):
    http://forums.ni.com/ni/board/message?board.id=170&message.id=65873&query.id=0#M65873
    Link 3: more info:
    http://forums.ni.com/ni/board/message?board.id=170&message.id=86971&query.id=0#M86971

  • Final Cut Express with Universal Control Surface?

    I would like to buy Final Cut Express. I want to use a universal control surface such as the Tascam FW1082 with my editing. I know the FC Pro has control surface compatibility, but does the new FC Express?

    Bummer. But, thank you for answering my question.

  • No communication with device control through AJA Io?

    So this is weird (to me). I'm trying to capture a few Beta tapes and can't seem to get the device control going. For whatever reason I'm getting the "No Communication" message in my Log and Capture window. Of course, I'm getting the image in the window, but I can't control the deck through Log and Capture.
    My settings seem right:
    -Deck in remote mode
    -FCP set to AJA Io device control
    -Capture settings at AJA Io Betacam to DV (I know this isn't a problem because I can see the image)
    -I have unplugged and reset each cable in each port on the deck, Io, and computer
    The only thing I can think about is that the last footage I captured was from my MiniDV camera, so I must have tweaked some kind of a setting that I don't know about. Any thoughts?
    Thanks,
    Stef

    Device control: AJA Io RS-422 NTSC
    The RS-422 cable is connected to both the deck and the AJA. The Firewire cable is connected to my 400 port and the AJA.
    There has to be some kind of a problem with my 400 port, because I just daisy chained the AJA (which only uses a 400 cable) through my Lacie drive, which is connected to the laptop through the 800 port.
    Is there an explanation for this? Hopefully besides, "Sounds like your 400 port chucks it, Stef. Time to go get a new one."
    Message was edited by: majormajor22

  • Using a Control Surface with the Clip Mixer

    I'm contemplating purchasing a Mackie MCU to help automate some of the volume edits I have to make using 5 tracks in the Audio Clip Mixer over 80 hours of video.  I've tried to contact Adobe support, but they are about as cluless as a bag of hammers.  When I asked if the clip mixer works with a control surface (after 4 calls and 4 different agents) I was told no.  Which is total BS as there is toggle in the clip mixer called "Toggle Control Surface Clip Mixer Mode". They read from scripts and have no clue what they are talking about.   I guess I should not be surprised as its an outsourced call center staffed with drones who have never even used the software, much less in production!  Adobe you should be ashamed of your support, it's appauling! (BTW I own an online Magazine in the 3d industry and will be writting an article about your appauling support soon) 
    Anyway, onto my specific questions:
    1) The Mackie MCU has overlay cards for button mappings for many different apps, but PP is not one of them.  What functionaliy is mapped to the control surface specially from PP and the clipmixer?
    2) Is there a way to group channels so that keyframes can be written to multiple clips at the same time by using one fader?
    3) In the clip mixer there is a keyframe toggle, does such a toggle translate to the control surface?
    4) Sometimes I want to manually keyframe, rather thanan make adjustments while the playhead is moving, so I will simply click the fader slider to write a keyframe, manually move the playhead and then adjust the fader to write the subsequent keyframes.  As faders on a control surface can not be pushed like a button, is there a way to generate a keyframe from the control surface?
    5) Are there any known limitations using the control surface vs the software for both the clip and track mixers?
    Jeff

    The Mackie device has some quirks, and while basic functionality is there, PPro does not have as strong support with mackie as it does with eucon through the avid artist series.  The physical MCU keys switched between different versions of the device and what is undo on one is a different function on another, so sadly, depending on what model you get, those buttons may or may not be correct by the label that is on the device.  There is no way for us to tell which one you have.
    Clip mixer mode can be enabled either through the fly out menu in the clip mixer or by assigning a keyboard shortcut.  When engaged, it supports the faders, pan/balance/mute and solo.  If automation is engaged it will record automation, though you can't engage clip mixer automation via the control surface like you can on the track mixer.
    Unfortunately there is no way to group channels at this time, aside from making a submix, but I do not think this is what you were requesting.
    There is not a way to manually enter a keyframe via a button on the control surface.
    It is possible to customize some of the control surface buttons by hitting the button assignments button in the Mackie control surface window.  This is mostly limited to the function keys and a few others
    The touch and latch mode lights is a known bug.
    If you want more customization, the Avid Artist series has much better support in this regard.  We set up many soft keys, but you can also create your own very easily. 
    I will take a look at the other issues you have raised as they sound like bugs, but I also encourage you to file them through here: https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform as it will help us to gauge how many are using the mackie protocol vs eucon.
    Thanks
    Todd

  • 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

  • Unable to delete control surfaces

    Just installed Logic Pro X and inadvertantly added an incorrect control surface.  Attempted to delect unsuccessfully.  Possible bug?

    Patrick, just delete the Control Surface preference file and start over.
    In the Finder, choose Go > Go to Folder from the menu.
    Type ~/Library/Preferences in the "Go to the folder" field.
    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.
    p.s. be sure and include the tilde ~ in the above directions.

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

  • Logic 9 is not recognizing my midi control surface.

    hi, i am currently running logic pro 9 on os 10.6.8 and i have an m audio oxygen 49 controller. i deleted this by mistake in logic. it is seen in my midi/audio setup but i cannot install it in logic again because it is not being recognized. it is usb and tried shutting it off and disconnecting it but still nothing.
    can some one please help before i rip all the hair out of my head?

    First thing to do is quit Logic and delete the control surfaces preference file, it 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.
    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.
    In this order:
    1. Delete the control surface preference file, be sure and include the tilde ~ in the path name just as it's written above.
    2. Unplug the Oxy49
    3. Reboot the computer, let it settle.
    4. Plug in the Oxy49, wait 30 seconds
    5.Start Logic

  • Control Surfaces compatible with Premiere Pro CC

    Hello!
    I am starting a new gig and I am building out a edit bay for the project.  I have only build a bay with FCP7 so I am a little hesitiant on things like peripherals.  Since Control Surfaces are new to support in Premiere please let me know what kind of experience you've all had in working with them.  I have had sucess with the Behringer BCF2000 on FCP but I've had my eye on the PreSonus FaderPort.
    Can anyone lend any input or experience?
    Thanks!

    Hi Dan,
    Picked up a FaderPort last Wednesday and I'm gonna return it on Monday.
    Here's the story. First of all, if just going by the specs, Premiere is not supported by FaderPort.
    FaderPort uses either the Mackie HUI or the Mackie Control protocol but it's defaulted to HUI so you have to switch it over yourself, a procedure that is not explained explicitly in the manual.
    Once you do that the key mapping is "all weird" and I could not make any sense of it, so after two days of fighting it, I gave up and will return the thing (thank god for the 30-day free return policy in Sweden).
    In essence, I would not go for the FaderPort with Premiere.
    Honestly speaking, after some research, I am yet to find a control surface that explicitly states full compatibility with Premiere.
    I was over on the Avid website and was looking at the Avid Artist Mix compatibility specs, Premiere is not even on the list. Audition is, but there is no functionality listing for it, unlike all the other supported DAWs.
    I don't really know why no control surface I've seen explicitly supports Premiere, might be because Premiere only recently got the control surface functionality, but I think that both the surface makers and Adobe need to shape up and iron this out, because I'm not gonna mix a 90 minute dance show video using the mouse for a fader!
    Cheers, J

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

  • Incomplete control parameter for communication with the BW system

    Hello SAP Experts!
    We have R/3, which is ECC 6.0 and BI 7. While loading data to target, we are facing errors BD87.
    Application Document not posted.
    R3/030:Incomplete control parameter for communication with the BW sys.
    Please, I invite your valuable inputs
    Thanks & Regards
    Vanitha

    Seems like your source system is not active...
    Try transaction RSA1 -> Source Systems -> select system and
    click 'activate'.
    Also read,
    Note 398335 - Error message R3 030
    Note 359412 - Error message R3030, control parameter incomplete
    Regards
    Juan

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

  • Control surface problem with tracks assigned to Rewire channels

    I'm using Logic 9 and Reason 4. My control surface is an M-Audio ProjectMix using Mackie emulation.
    I have a simple project in Reason with 2 instruments, and a created a simple Logic project. I then created 2 external midi tracks, and then used the library tab to assign them to the Reason devices.
    My problem is that, unless I set the control surface to Track, it always shows the rewire objects (and they don't have any controllable properties). This is annoying as they are taking up space on the control surface, and since they are not visible in the mixer in Arrage mode (unless I go to View>Show Other Tracks) I would not expect them to be visible on the control surface. And most annoyingly, whichever rewire object in the mixer is selected, all the rewire channels on the control surface will display that object's name (surely that's not supposed to happen).
    Interestingly, if I create either 2 instruments or a multi in the environment, and wire them into the Rewire objects, then set the tracks to point to the instruments, the problem disappears.
    This does not sound like correct behaviour to me; can anybody confirm that this is what you would expect?
    Thanks,
    Adam.
    PS. I would guess that it's because Logic treats them, internally, as having the same channel, which is why they can't be individually controlled.

    Let's try "disable handshake" in the nucleus remote. You have to restart the nucleus for the change to take effect.
    It worked for me!
    Regards

Maybe you are looking for