LP8 Crash - Lost control surfaces

Hi,
Last night while editing some music LP8 crashed. I restarted it and continued to work but noticed that my two control surfaces were no longer defined including the special keys I had defined for transport control.
Is there anyway to restore my settings without having to go through the setup again? After I get them working again is there anyway to save the settings in case of another crash? I've lost this stuff several times now.

you need to use Logic control surface setting
wait...
I need a moment for the pictures
about axiom is not fully supported... as you know it comes from M-Audio
some bug could be force you to don't use it!
maybe Logic Crash comes directly from M-audio Axiom 61 keyboard...
*as you can see I have Logic control... but it is BCF-2000!!*
*it is recognized automatically*
*works without any crash!!!*
G

Similar Messages

  • Strange Crash when opening Logic 9 after deleting control surfaces preferences file

    Hey, I have been having issues where logic crashes when I save certain projects of mine, so I tried to find a solution and one that I had read said that I should delete the control surfaces preferences file named com.apple.logic.pro.cs.  I deleted the file, but it seems to have bricked my copy of Logic.  I have included a screenshot of what happens when I now open Logic, which requires a force quit to get out of.  If anyone has any suggestions of what I should do next I would really appreciate it.

    Solved.  It was an issue with my prokit (I had also been messing with that unfortunately).  Found another thread and followed their instructions, back in action.  Feel free to lock this thread.

  • Similar Post... Still Unanswered (Control Surfaces)

    I thought I'd try again...
    How can I get my control surfaces to modify software synth parameters inside logic?  Is there a way to route the controller to a software synth for tweaking synth sounds (I find the mouse very annoying for this especially live tweaking while recording)?
    Thanks!

    Thanks!  Like I said before I'm going to give it a go a little later w/ the Akai documentation I have for use with Logic Pro.  I know it works with my MPD32 Controller and MOTU's BPM 1.5...  I'll give it another go and see where it lands me... 
    I do have a Novation ZeRO SL MkII Controller which would be perfect for tweaking sounds but I've had very little luck using it...  I sometimes regret the purchase.  If it worked as well as it was supposed to it would be almost magical but it crashes constantly both the AutoMap 3.7 software it comes with as well as Logic Pro 9.  Some I'm a little nervous about using it with any projects.

  • 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

  • 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

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

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

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

  • 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

  • How do you delete a device in Logic Pro X Control Surfaces Setup?

    How do you delete a device in Logic Pro X > Control Surfaces > Setup?

    Go here:
    http://help.apple.com/logicpro/mac/10/
    Search on   Bounce

  • Any Video Control Surface Recommendations?

    Hi Guys,
    It's been some time since i've posted here i must admit, but i had a quick question and i'd appreciate some opinions!
    I have been editing videos for individual and corporate clients for a while now, and have been utilising logic etc to record some of my own soundtracks - but i now feel that a video/audio control surface would help streamline my workflow (an expensive luxury though!)--- and i wondered if you had any recommendations / advice?
    Note: I haven't had the need to really look into the hardware control surfaces, and googling has brought me to the Mackie MCU Pro, Tascam FW-1082 and an Alesis one... but they are a little out of my minds price-range (though not the pocket if reaallly persuaded)
    Many thanks,
    Adam

    Shane, thanks for your quick reply! I didn't say they were too expensive... just that in my limited/low knowledge of the things they seemed like an expensive luxury for me - not that they were / were not... i am aware quality costs money (it is why we buy what we buy apple as opposed to pc's etc).
    Have you had any experience with the Mackie? it seems like one would just be paying for the name- though undoubtedly it is probably a fantastic piece of kit, the Tascam does seem an equal competitor. Are there any others that you can reccomend/know of? i am struggling with net research- it mainly points me to those two..and a selection of home-user plastic jog wheels etc.
    Many thanks,
    Adam

Maybe you are looking for