Using a Yamaha o2r as external control surface?

I've been trying to get my o2r to work as a control surface for the audio mixer in fcp5 .. with no luck.
The 'iControl' that I use for Garageband does actually adjust the pan control (but only the pan!) .. its just occurred to me that I don't know whether this is through midi or the usb!
Does anyone know whether the o2r can be linked up?
Thanks

If the O2R supports Mackie emulation it should work, if it doesn't then it most likely won't work. You'll need to check the manual for the O2R to find out.

Similar Messages

  • Yamaha 01v96 v2 as control surface.

    Hi there, does anyone out there use this digi mixer as a control surface? My problem is;
    1/ When I set the DAW channels to 2-3 and do everything logic tells me, it seems that the mixer continuously and repeatedly outputs a c-2 note event. I can get over this by putting a filter between the MIDI 3 port and the sequencer input but it sould not be happening.
    2/ The control surface tends to be very tempramental and loses contact with Logic. Message on mixer "01v96 has gone offline and is waiting for midi input". Message on Logic "Logic has lost contact with 01v96, please power cycle"
    Any help would be much appreciated.
    Matt

    Hi there Morten.
    Have been having the same problem. Spoke to several people about this fact (while bouncing the O2R96 goes off line). No solution yet. Must say my bounces are fine tho. Haven't had a blip on them yet. Just the tedium with the "okay" depress. How are yours?
    As for the MIDI out activity you see on the transport bar, have spoken to Yamaha Kemble at length about this (to try to get rid of it as it was bugging me too. What happens when the counter gets to 000000? Still haven't got there yet...). They assured me that this is an essential part of the O2R96s communication sync with Logic. The O2R96 sends a MIDI message to Logic (every second apparently) in order to asertain whether "it" can hear "it". This is then/'should be' echoed back by Logic. Apparently this prevents MIDI data jams by telling the user that Logic is no longer in contact with the O2R96. Basically that alert you get "Logic is unable to communicate with "O2R96". Please Powercycle..." If it still bugs you, you could get rid of the MIDI window in the transport bar? This does however take away one's All MIDI Note Off command away...
    Hope that answers the why question.
    Karl

  • Random sound generated from external midi device even without a song opened... How to uninstall external control surfaces?

    Recently bought systems used :
         Roland FA-08 workstation
         Mixingtable with USB connection Yamaha MG12XU
         Mac Os X 10.9.4 Maverick with Logic Pro X 10.0.7
    for each system the latest usb-drivers are installed
    Problem :
    I get random noises generated (non-stop) from the connected synthesizer FA08 starting up Logic, even without a song opened.
    (My midi local is switched of, that's not the solution)
    The problem started (i think) installing the Mackie control for the DAW use as was suggested by the Roland manual
    in Logic Pro X > Control Surfaces > setup...
    Other than my remote control i now have Mackie controllers that i can not remove from the setup. Right click says 'delete' but
    they are not deleted, the program even crashed once. Reinstalling Logic does not remove them either.
    I read somewhere that there should be a 'controller rebuild'-command but that doesn't seem to exist.
    And i have no idea why in the 'inspector', the host of the Mackie Control seems to be my I-pad (?)
    I suspect that te problem is either some midi/usb driver conflict when used with Mavericks
    or te use of the mackie controller conflicting with
    the audio-bord of the yamaha mixing console MG 12XU (which seems to be working fine) or with the DAW controller of the FA 08
    Audio/Midi setup of my computer seems to be installed correctly.
    How can i uninstall this controller settings ?
    Anyone has an idea why i get random noise generated?
    Anyhow, it is impossible working with Logic this way..
    Please help..

    In case you need to get back the default Logic control surface setup you can delete the Control Surface preference file and the default file will be rebuilt. It's a good way to get back to Logic's initial control surface setting. Also, if you had chosen to edit the Logic Remote CS entry instead of remove it there are adjustments that can be made, like disabling Active Sensing, or even disabling "Flash Mute and Solo Buttons" on the basic Control Surface Preferences pane.
    Deleting the Logic 10 Control Surface Prefs.
    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.
    Delete the com.apple.logic.pro.cs file from the preferences folder.
    Note: to get to the User-Library the tilde ~ has to be included.        ~/Library/Preferences

  • Control surface toggle audio clip mixer

    Thought I'd post this as it took me some time to work out it was possible.
    External control surfaces now work with the Audio Track Mixer, but I couldn't find a way (or any info) on how to make it work with the new Audio Clip Mixer. Eventually I found 'Toggle Control Surface Mixer Mode' in the keyboard shortcuts and now everything is working well in both modes.
    This works for mute, solo and level in the Clip Mixer. I've not yet attempted any automation, I can't see a way to turn on the 'record keyframes' other than manually one track at a time. Still, progress to this point is very welcome.

    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

  • Virus TI Polar as Control Surface?

    I want to my Virus TI Polar (using the hardware knobs) as a control surface for some of Logic's soft synths, but I've been unable to do so. I've tried a number of things (within the Control Surfaces Setup and the Controller Assignments Window), but before detailing what I've tried and what happens, does anyone know if it's simply not possible to use the Virus as a control surface for Logic's plug-ins? I'll be happy to detail what I've tried if someone out there knows or thinks it's possible. Thanks.

    Bee Jay, thanks for all your help. Below are my best answers, though I might be getting in over my head...
    There are scenarios where that is normal - for example, if your Virus is on a MIDI port designated as a control surface, or has commands learnt by controller assignments, the controller assignments layer intercepts and 'steals' the MIDI commands so they don't ever reach the sequencer part of Logic (so they will not be indiciated in the transport window).
    Hmm, according my Audio Midi setup, the Virus has two ports "Virus TI MIDI" and "Virus TI Synth (internal)". I don't know how I would know whether either of these are "designated" as a control surface.
    It was just a guess, really. Do they have the Virus manual online I could take a gander at..?
    Sure - go to http://www.access-music.de/downloads.php4?product=virustipolar#cat4 -- there are two documents, "Virus Control Tutorial" (the first on the list) and " Using the Virus TI with Logic 7" the fourth one on the list (there's no manual for using the Virus with Logic 8 yet, that I know of.
    And, to answer your other question, I did try at one point using Logic's controller assignments window to individually assign Virus knobs to ES1 and ES2 parameters, but it didn't work (long story).
    Same deal - no MIDI events are seen at all?
    What happens is this: In learn mode, I'd touch the ES1 cutoff knob, for example. I'd see the "waiting for incoming messages" message; in the "control" column of the window it will say "no message received yet"; in the parameter column I'd see "ES1: Cutoff". Then I'd move the Virus Filter 1 Cutoff knob, and the parameter column will change to "Virus TI: Filter1 Cutoff", but the "control" column will still say "no message received yet", (which I don't think it should say, right?). In any case, at that point I'd try going out of learn mode, and the Virus Filter cutoff knob will not control the ES1 cutoff knob. Sometimes, thinking I was doing the process wrong, I'd try it in reverse, moving the Virus knob, then the ES1, etc., but it never works.
    I also tried using Logic's Control Surfaces Setup to create a Virus device with no luck.
    It's not still defined as a control surface in your setup, I take it?
    That's right. I couldn't add it by scanning or manual add.
    What I would do is try using something like MIDIpipe to examine the MIDI coming in - leave Logic out of the equation at first. Twiddle the Virus knobs - is any MIDI data been generated at all, or any MIDI port..?
    I'll try this. I'm under the weather today and I think I should go home and crash, so the next time I respond might not be til tomorrow. Thanks again for taking the time to help, Bee Jay.

  • Using Yamaha AW2400 as control surface for Logic Pro 9

    I am a freelance pro sound engineer currently working as tech support for a local school. They have a Yamaha AW2400 in their studio, something which I have never come across before despite using numerous Yammy desks. They also have a Mac running Lion and Logic Pro 9.
    What I want to do is use the desk as a control surface for Logic and record direct to the Mac if possible. I have installed the Yamaha USB-MIDI drivers on the Mac and had the desk running as a device for file transfer (via the USB connection) but everything else is beyond my knowledge of the desk and Logic.
    I am a Pro Tools guy so Logic is a bit new to me but I know how to setup a new control surface. and the basic operations.
    What I need help with is...
    - what control surface to use as there is no preset on the desk for a AW2400
    - what port settings to use on Logic
    - what TX and RX settings to use on the AW2400
    - what Remote Out settings to use on the AW2400
    - any other info I may need
    Thanks in advance, hope some can help.

    See page 204 of the AW2400 User Guide...
    http://www2.yamaha.co.jp/manual/pdf/pa/english/recorders/aw2400_en_om_b0.pdf
    Note: the User Guide says that only LP7 is supported but you never know.. it may work with LP9... Test and see..

  • 02R96 and other Yamaha control surfaces - break Learn Assignment?

    Can someone throw some light on this:
    The 02R96 and other Yamaha control surfaces send out this Active Sensing thing, which is just a real, downright nuisance for all kinds of reasons.
    1) How am I supposed to get plug-in parameter assignments automatically learnt if the 02R96's active sensing keeps jumping in every second? Logic thinks that's the MIDI message I want to assign to my parameter! There doesn't seem to be a way of telling the learn process to ignore what's going on on a certain MIDI port. Result: can't automate my plug-ins. There seems to be no way of doing it.
    2) Another thing about active sensing - you can't get Logic to just shaddup about it if the control surface isn't on. What if I want to keep my 02R96 turned off for some reason? There should be a Disable control surface button or something - anything to prevent having to remove the 02R96 setup entirely from the Logic session! Really not good...any thoughts or insights? (especially on the parameter learning stuff..that's a real show stopper)
    Adrian

    The Mackie Control support lets you edit all parameters of instuments and effects plugins. If you don't have a Mackie Control, you can also use John Pitcairn's LCXmu, which acts as a virtual Logic Control translator between your controller and Logic.
    I have a Korg microKontrol running with LCXmu, and it's excellent, way better than Logic'a native mK support, and you can access all instrument & plugin parameters, with the names coming up on the mK screens etc.
    Have a look at LCXmu at OpusLocus and see whether your hardware is a directly supported device. Even if it isn't, you can still use it, you just have to set up some manual mapping stuff, depending on what buttons etc you have on your controller.
    Otherwise, you are back to manually assigning parameters using Logic's controller assignments - but they are buggy.
    I have to say that LCXmu has completely solved all controller issues I had using the micoKontrol as a little portable controller. It's ace.

  • 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

  • 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 01V96 as a control surface.

    Hi, I am having some serious issues using my 01v96 in remote mode (via MIDI) as a control surface. The first thing is that when the 01v96 is listed on the setup page Logic continually outputs a C -2 note about once a second. It also outputs sysex data and continually zaps my free memory. This is worsened with Studio Manager running at the same time. The other thing is, I can use the first 8 channel strips when the input port is listed as all but not when I try to change it to a specific port. I cant get the second 8 channel faders to work at all, even manually adding the control surfaces. In fact, as soon as I try to change to a specific port the 01v says it has gone offline and is waiting for MIDI input.

    I have now got the 01v to operate as a control surface however it is still causing logic to output a C -2 note event at roughly 1 second intervals. Any idea what this could be??
    Also, logic is registering the sysex data from port 1 of the 01v. On Clicks & Ports I can manually connect all of the MIDI ins apart from yam. port 1 to the seq. & thru but is there any other way of simply knocking out one of the midi in ports in logic. Unfortunately it won't let me do it in OSX.

  • Can I use a VS-700C control surface with Logic Pro?

    Hi,
    Does anybody know if I can use a Roland VS-700C control surface and/or VS-700R audio interface with Logic Pro?
    Cheers,
    Craig

    If it supports the Makie protocol, it might work... but I wouldn't purchase one on that basis without trying it first.

  • 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

  • Im looking for the cheapest and smallest transport control surface to use with logic 9(and X when i upgrade my lappy). usb.

    Ive seen the presonus faderport but there looks to be lots of problems? is this still the case or has it been fixed?
    Or have you any info on godens...if there even is?
    cheers.x

    If I could make a suggestion. I too have the Axiom49 and love it. I would not get rid of it. But for control of Logic, I use the Presonus FaderPort. It works flawlessly. Plug it into a USB port, add the Mackie HUI controller in the preferences, set the input and output (of that control surface) to the FaderPort, and your done. Motorized fader, limitless pan knob, etc. You may want to look into this little gem. It will be less expensive than a new MIDI controller, that's for sure.
    Peter

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

  • Using an Edirol PCR-300 as a keyboard and MIDI control surface. Any luck

    In the manual for the Edirol it lists 8 or 10 templates for Logic and then doesn't go on to say exactly what they do. I tried adding the PCR from the list of supported surfaces but it's not there.
    There is some instruction in the PCR manual to open the Audi0o Midi data manager and create nodes with connections, but I'n not sure exactly what the point of that is supposed to be.
    After doing some digging I found something that that the Edirol had to be supported in Mackie emulation mode. I recently did some major problematic upgrades and lots of this appear to be lost. I don't know which Mackie mode it supports. My guess it would be HUI, because unlike the MCU the Edirol isn't really bidirection is this correct?
    I think I had it working before the upgrade, but now I've got the old problem back. I can get the control surface to sort of work and then when I touch a regular key the whole screen goes crazy with windows popping up and down then disappearing.
    I think for some reason the Edirol is sending out messages that are telling Logic to frequently cycle through screen sets. I did think I had figured out this problem once before after diligent searching, but I forgot how I did it.
    Any ideas on how to get the Edirol PCR-300 to play well with Logic?

    Yes I have installed the drivers as the PCR 300 works with Logic 8.

Maybe you are looking for