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

Similar Messages

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.

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.

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.

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

Control surfaces with Logic?

Have a Macbook pro & looking to get Logic. Previously was running Cubase with a Yamaha O1v deck & it worked great with Cubase. Sold all that & looking to get a more compact project studio going ... what control surfaces integrate well with Logic?

The Yamaha O1v had a fader mapping setup that worked really really well with Cubase. You simply selected the O1v from a drop down menu in Cubase and all the faders and EQ settings automatically mapped to the board. Only a few boards were listed in the Cubase menu.
Curious if there are certain boards might be listed in a similar feature in Logic.
(Planning on jumping on the Logic train at the same time as picking up a board...)

Control surface with keyboard controller

I'm fairly new to Logic and sequencing (but not Macs) so I'm on a steep learning curve.
I set up Logic with a Yamaha 01x as an interface and control surface. That's working o.k (after some dramas). I play software synths with an Edirol PCR controller keyboard. What I want to do dedicate the 01x to sequencer and mixing duties and assign the keyboard knobs and sliders to soft synth controls, (preferably globally - as in not plug-in by plug-in). When I try to use the learn function on a soft synth it doesn't want to take the assignment. It flashes the name of the keyboard briefly then reverts back to the name of the 01x port. I'm thinking it has something to do with the fact the keyboard is a separate USB midi interface. Whatever it is, I don't know where to find a set-up page for the keyboard or the combination of the keyboard and the 01x. Funny thing is, setting up my keyboard is so easy in MainStage which is part of the same software suite.
I can't find anything in the manual that deals with this sort of hardware controller combination. Any help would be greatly appreciated.

I still can't get this working so I am posting some more information in case someone can see a glaring hole in my logic (pun definitely intended).
I have tried setting up controller assignments in both the Logic preferences and by the learn function within the plug-ins. My keyboard is a USB MIDI interface but it is not seen as a control surface by Logic. (As you say, Bee Jay, that's a good thing). It is sending out notes and controller messages on its own discrete port, port 1 (of two), channel 1. The synths in MainStage can see my keyboard and my control surface just fine. I can't see why it should be any different with Logic? Certain controllers always work (pitch bend, mod wheel pan volume and aftertouch). I have not been able to assign any of the other controls of any soft synth. Even if I set the soft synth destination to receive a source I know the keyboard is putting out (I can see it on the transport bar input display), it still doesn't work the control. I've tried deleting all "learned" controllers and starting again - Many times now.
Needless to say, I'm getting to that stage. . .

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

Original 02R and control surface

Dear Logic Users,
This is a brilliant forum! I've always been amazed by the knowledge of everyone out there.
This time, I have a really tricky problem to solve.
I've obtained a Yamaha 02R and I wish to use it as a control surface in Logic. Although it's not directly supported, I've read you can use the learn features of Logic to connect via midi.
I also have a MOTU Midi Express XT.
When I select menu Apple Pro Logic --> Preferences --> Control Surfaces --> Learn parameter 'no parameter selected' or 'controller assignments' and learn
The motu midi express seems to beam the synchronisation tick without giving me chance to move a fader on my 02R.
Does anyone know how I can disable this feature in my MOTU.
Or - does anyone know how i can setup a port and parameter I can learn.
I know I've got a long way to go, but any help here would be amazing.
Kind regards,
Andrew

Currently, my settings in the Yam 02R are as follows:
Currently, my 02R settings are as follows:
SETUP button --> 3/4
Transmit Key Remote - selected
MIDI Warning OFF - unselected
Insert Tx Bulk Wait - selected
SETUP button --> 4/4
Touch sense select- selected
Tx 02R Link Message - selected
Rx 02R Link Message - selected
MIDI button --> 1/5
Receive Channel: 1
Enable
Prgoram Change
Parameter Chg.
Control Change
Transmit Channel: 1
Enable
Program Change
Parameter Chg.
Omni
Program Change
Echo
Program Change - unselected
Maybe I need to link these to the transmit and receive in Logic? would anyone know how to do this?
Thanks
Andy

Getting control surface back

Hi, I have a Korg microKontrol which used to run as a control surface. Since I installed an 01V96 the microKontrol is no longer working as a control surface. It is still listed and shown on the setup page but the LED's and operation are that of a simple MIDI controller keyboard.

Never mind

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

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.

Yamaha 01v96 v2 as control surface.

Similar Messages

Maybe you are looking for