Logic 9 with Roland VS100 Control surface Issue.

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

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

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.

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

  • CME Control surface issues.

    No matter what I do, even when I try and use the learn function, I still can't get the transports of the CME to control Logic. The only thing that the CME will control is the volume, all 8 sliders do the same thing, volume, but when I control Reason with the CME, stand alone, the transports on the CME work GREAT! Since I do use Logic and Reason through Rewire, it would be nice if I could do the same with the CME for Logic.

    Hi Moogy77,
    The transport controls are controlled as key commands. You can assign buttons on your controller to trigger those commands. Check out the Logic Pro 8 Control Surfaces Support guide in the Help menu and on page 55 is a section titled Assigning Buttons to Key Commands. That is how you will get the transport controls working.
    Cheers

  • Logic Pro X: control surface "Scrub" no longer working

    Hi everyone,
    I'm a relatively new user of Logic Pro, and a very new user of Logic Pro X - I'm hoping someone can point me in the right direction!
    I've been using DAW Remote HD (by EUM Labs) on an iPad 1 with Logic Pro 9, and found them to be a great combination.
    Two weeks ago I upgraded to Logic Pro X, and I've found a problem which has been driving me crazy. Basically, the "Scrub" function using the Jog wheel in DAW Remote HD has stopped working. Using the jog wheel just to jog forwards and backwards works fine; however, when I hit the Jog / Scrub toggle, the "Play" button lights up, and then regardless of whether I try to scrub forwards or backwards the playhead just "jiggles" in place and nothing happens - no scrubbing.
    Can anyone help? I'm guessing the control surface assignment has gone awry somewhere, but have *no clue* where to start. I've had a look at the Controller Assignments expert view in Logic Pro X, and had a read through the Control Surfaces documentation, but I'm all at sea. Is this a bug somewhere, or is this something I can "fix" myself?
    Thanks in advance if anyone can help. I can't use the native Logic Remote as I only have an iPad 1, and am hoping I can get this important function working again on DAW Remote HD as it's pretty vital in my workflow.
    All the best,
    Sarah

    Hi everyone,
    I've been doing a bit more research into this and am wondering if it might actually be a bug. I've deleted my control surface config file, reinstalled the DAW Remote several times clean, both automatic and manual, and even tried it out with completely different control surface software on my iPad1.
    In all cases the "scrub" function doesn't work properly - it stutters and "jiggles" and moves forwards randomly, and all the while the jog / scrub toggle enables the "PLAY" button (I'm not sure if this latter is intended functionality or not - I never noticed when it was working in Logic Pro 9).
    Could it be that Logic Pro X is interpreting the scrub command(s) differently from Logic Pro 9, or even incorrectly? I don't know anywhere near enough about control surface commands to comment - just that the apps & functions were working with Logic Pro 9 and now aren't with Logic Pro X.
    Would someone mind giving this a second check to see if it can be replicated? Basically use an iPad control surface app like DAW Remote HD, AC-7, LPTouch, etc, with Logic Pro X and try and get the "scrub" working on the jog wheel (jog works fine - it's scrub that's the issue).
    I'm using an iPad 1 so don't have access to the Logic Remote, and it seems a bit expensive to upgrade the iPad to get access to a scrub wheel.
    Thanks!
    Sarah

  • 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

  • Exerienced in adding Control surface info?

    when I go to control surface settings... it only lists faders as 1-12. in Logic and Roland's manuals, it says it can use all 16 faders. So, it think that this is why Logic is doesn't know what to do when i reached that 13th fader which is BUS2. Anyone have experience adding changes to these types of parameters to get faders 13-16 to play nice????

    After about 20 minutes of messing around, I figured it out. So, for future refference of other Logic tortured souls: To have all faders on your Control Surface accounted for, make sure that under Logic Pro menu/Prefferences/Control surface/setup and make sure "mixer view" is correct. Before, it was suspisiously at 12....when my mixer has 16 faders. Problem Solved. Enjoy.

  • Logic 9 with Axiom 25 and Roland VS100 issues

    Im trying to help a friend with his setup. He has :
    Logic 9
    MacBookPro
    Roland VS100 I/O
    Axiom 25 1st gen controller
    Ive got him so that the VS 100 gives him the audio and transport functions. Roland US had a Controller Plugin for this that loads works in Logic/Garage Band and this is all working fine. Under Controller Setup in Logic the VS 100 shows up and the MIDI IN/OUT are both set to CONTROL.
    As soon as he plugs in his AXIOM 25, the axiom will play a software a instrument just fine, however, the VS100 transport functions are now gone and the unit is basically sending out midi notes to the plugin instrument when he hits any transport buttons on the VS100. No transport control on the VS works.
    The AXIOM manual says its core midi compliant and needs no driver
    Also, the AXIOM will not do the transport functions either once its plugged in with or without adding it as a controller in Logic. Both the VS100 and the AXIOM show up in the AMS and show online.
    I tried changing the Global midi channel on the Axiom to channel 2 and matching the same midi input channel in Logic but no dice
    If we have both controllers added in the Logic setup, the Roland MIDI IN/MIDI OUT will allow us to select CONTROL and the AXIOM MIDI IN/MIDI OUT only show port 1
    If we uplug the VS100, the AXIOM will then show CONTROL as an option,.
    What Im thinking is that BOTH controllers are trying to take control in Logic. Is there a way to work around this in Logic so that he can use his AXIOM to play the synths and the VS100 for transport? Thats all hes wanting to do BTW, shouldnt be that complicated.
    Ive been using LogMeIn to help him but I dont know what else to check here. Any help would be greatly appreciated
    Thanks guys

    I would say I'm somewhat disappointed that with 171 views not one person has made any suggestions for this issue. Well I ended up resolving my own issue! Turns out that this issue was being caused by use of a sample rate of 192khz with my Motu Ultralite mk3. Once I dropped the sample rate down to 9600 all the distortion was gone. Now to be fair, I presently reverted back to OSX 10.5.7 for testing purposes, but it behaved exactly the same as it did in OSX 10.6.1. So my bet is all along the issue has been the high sample rate of 192 causing the problems with 3rd Party apps (Massive) etc.... Interesting, that I don't notice these distortion issues at 192 with the instruments/sounds in Logic 9. Oh well, I'm glad it is resolved, now on to making music!
    Message was edited by: flashbak

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

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

  • 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

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

  • Digidesign Command 8 control surface with Logic?

    Does anyone have any experience getting a Command 8 to function as a control surface for Logic Pro 7? I'm really having trouble finding any information on it and I could really use some help. I'd appreciate any input or suggestions. Thanks,
    -Jeff

    Although it may have a standalone mode, it's not emulating any particular controller, such as the Logic Control or Mackie HUI protocols. It may send MIDI control messages that Logic can pick up (my Trigger Finger can do that as well). However, unless Logic sees the right ID from the Command 8 (whether in native or emulation mode), it won't recognize it as a control surface and send messages back and forth with it, thus not being able to take advantage of things like the display and motorized faders.
    It looks like the Command 8 and the ProjectMix I/O look rather similar (yes, I know that Digidesign and M-Audio are owned by the same parent company).
    jord

  • Issues re Tascam FW-1082 & FW-1884 control surface - integration with FCP

    The joint Tascam/Apple release put out in 2005 touting seamless compatibility between these two products (see below) turns out to be a gross exageration. Basic functions are conceivably compatible, but some do not work and there is a paucity of documentation available. The many buttons and controls on the Tascam's control surfaces are rendered useless. The consumer consumer has been wronged and these are not cheap products. Countless similar posts on this site backs me up on this.
    I have the Tascam fw-1884, which has the same setup as the 1082. Have any of you been able to assign quick keys on the tascam using the keyboard customization tool in FCP? I've followed the example on Tascam's support site, but it does not seem to work.
    Also, looking for more documentation/tutorials/consultants who can help me master all the features of the Tascam with FCP 5.
    Thanks,
    David
    TASCAM interfaces now compatible with Apple®'s
    Final Cut® Pro 5 & Soundtrack Pro
    MCP (Mackie Control Protocol) onboard Final Cut Pro 5 allows the use of external audio control surfaces to edit and manipulate audio
    Montebello, CA—April 16, 2005—TASCAM's full line of FireWire audio control surfaces and interfaces are now compatible with Apple®'s Final Cut Pro 5 and Soundtrack Pro editing software with Apple's unveiling of the Final Cut® Studio production suite that includes the Final Cut Pro® 5 upgrade.
    This major upgrade to the Apple's Emmy award-winning software means that Final Cut Pro 5 and Soundtrack Pro are now fully compatible with MCP (Mackie Control Protocol) devices, so you can use external audio control surfaces— including TASCAM's FW-1884 or FW-1082—to edit and manipulate audio more efficiently.
    TASCAM's newest audio controller, the FW-1082, has nine motorized faders for adjusting audio levels during mix playback utilizing the revamped software. Editors can turn up a dialog line or reduce the music level during a voiceover section without clicking on breakpoints. Just grab a fader and go! The transport buttons can be used to start and stop playback in any editor that supports the Mackie Control or Mackie HUI. TASCAM's FW-1082 also has a MIDI fader mode that can be used in programs like Apple Motion 2 to adjust parameters in real-time during playback. And since it's an audio interface as well, producers can record voiceover and sound effects right in the edit suite with professional results.
    The FW-1082 has four mic inputs, four line ins and S/PDIF digital in and out – all available at 96kHz. It features 10 inputs, including four balanced XLR mic inputs with phantom power. Eight channel strips each feature a 60mm touch-sensitive moving fader and select/solo/mute buttons, and a moving master fader.
    For even more I/O and surface control, the FW-1884 offers 18-channels of inputs (eight analog and eight ADAT digital and two S/PDIF coaxial or optical), eight balanced XLR mic/line inputs with high-quality mic preamps and phantom power, plus nine 100mm motorized touch-sensitive faders.
    G4 dual processor 1.25mhz   Mac OS X (10.4.6)   FCP 5.1.1

    So after writing this question I closed the laptop, leaving the Tascam on & connected. Returned 30 mins later to see if anyone had replied (where are you all??!!), opened the laptop & the Tascam suddenly springs to lift, faders move & Soft LCD app shows activity correctly.
    So, all appears to be OK although I don't really know why...!!

  • 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

Maybe you are looking for