Logic Pro 9 Midi Problems Multiple Devices

Hello, im having issues with using multiple external devices in Logic Pro 9.  I have a virus TI 2 and a prophet hooked up to a Saffire Pro 40 audio card which I am using the Midi Hub. 
Basically, If I have an external instrument (prophet) playing on a track I have to turn the virus off or else there is midi problems communicating with the prophet 08.
The Biggest issue i'm having here is that when the midi data in the external instrument track is playing, if I'm selected on the track while its playing, I get an extreme cluster #$)* of midi on the midi input display and it completely and utterly destroys what the prophet is trying to play into logic.
In my Midi setup on Mac Snow Leopard, I have the ins and outs of the prophet going to the saffire pro 40.  The virus is connected and playing midi via USB. 
Anyone know how I should be setting this up so the midi information is not getting messed up?  Yes, I have consulted the user manuals. 

Not: My ZED R Mixer connected FireWire 400 800 cable with iMac

Similar Messages

  • Macbook 1,83 Quatafire 610 Logic Pro Midi Problem

    I use an Esi Quatafire 610 with my Macbook (1,83 Intel Dual Core) and Logic Pro 7.2.3. Since
    the last Systemupdate (10.4.10) and Securityupdates, the Midi-Interface of the Quatafire have
    "hang ons" at Port 1. Port 2 seems to be ok. I tried the Quatafire with my G5 (2,0 Dual) and
    don´t have any Problem here. So the Quatafire itsself seems to be ok.
    I also installed the Audio-Update for Intel machines but this was no solution. Does anyone
    know something about this problem? The Quatafire works with Apple Core-Midi drivers.

    So yes I am playing on the virtual instruments.  No separate audio device.  I have external speakers plugged into my computer so when I play my keyboard through Logic, sound comes out of my computer external speakers and not the keyboard speakers(I turn the keyboard volume off).  The problem I described happens for the various virtual instruments I have tried, strings, woodwinds, pianos etc.  In the Logic audio settings it says
    Output Device:  Built in Output
    Input Device:  Built in Microphone
    I/O Buffer Size:  256 samples
    When I say the keyboard stops, I mean no sound comes out of my computer speakers for a few seconds.  It is as if someone turns the keyboard off for a few seconds and then back on.  This happens in Logic when Im trying out different virtual instruments.  You are correct when saying it happens only when Logic is running whether I am recording MIDI or just playing and NOT recording.  I hope that makes sense.  It wouldn't be such a huge problem, but it happens so often it makes it hard to play or record something thats longer than 10 seconds.  Thanks for the help.

  • Downloading Logic Pro X onto multiple macs

    Will I be able to install (download) Logic Pro X onto multiple macs like I did with Logic 8? (Only one used at a time).

    Yes you can. (Sorry. The other post with the answer popped up as soon as I posted.
    Thx

  • Logic Pro Midi Keyboard Randomly Stops

    Hi, I am fairly new to Logic Pro 9 and music composition software in general.  I have a Yamaha P85 keyboard that I am using with Logic.  I use an E-MU midi 2x2 to hook it up to my computer (imac 2011).  The keyboard has a midi in/out slots where I have a midi cable in the midi OUT slot.  It connects to my E-MU midi device in the midi IN slot.  A usb cable connects the midi device to my computer.  The keyboard is recognized in my computer MIDI settings and works in Logic Pro.  The problem is when im recording in logic or just playing, the keyboard will randomly stop for a few seconds (no sound when I hit keys) and nothing will be recorded during this period (if I'm recording).  After 1-5 seconds the keyboard will work again.  This happens randomly even when I'm not recording in Logic.  Another problem is sometimes, also randomly, a note will be held (sustained) when I'm not holding down the key.  Again, this happens in Logic whether I'm recording or not.  I have searched a lot online and read many forums, but I cannot find an answer.  Any help would be appreciated.  Thanks in advance.

    So yes I am playing on the virtual instruments.  No separate audio device.  I have external speakers plugged into my computer so when I play my keyboard through Logic, sound comes out of my computer external speakers and not the keyboard speakers(I turn the keyboard volume off).  The problem I described happens for the various virtual instruments I have tried, strings, woodwinds, pianos etc.  In the Logic audio settings it says
    Output Device:  Built in Output
    Input Device:  Built in Microphone
    I/O Buffer Size:  256 samples
    When I say the keyboard stops, I mean no sound comes out of my computer speakers for a few seconds.  It is as if someone turns the keyboard off for a few seconds and then back on.  This happens in Logic when Im trying out different virtual instruments.  You are correct when saying it happens only when Logic is running whether I am recording MIDI or just playing and NOT recording.  I hope that makes sense.  It wouldn't be such a huge problem, but it happens so often it makes it hard to play or record something thats longer than 10 seconds.  Thanks for the help.

  • Logic Pro midi start/stop remote

    I would like to start and stop (and even record) in logic with MIDI-commands from my keyboard (Roland RD-700GX).
    The keyboard has several midi buttons which are progammable but the message which is sent, is not a controler or SysEx but the start/stop status bytes of the MIDI-protocol. Logic cannot recognise these messages. Is there any trick or what can I do to work around this problem.

    voss.audio wrote:
    (look at FAH and FCH!)
    Well I downloaded the Midi Implementation manual and it says that these the S1 and S2 buttons send this messages for start/stop. They are labeled as "Real Time Midi messages" but I could not understand if they are MMC ones for this device. If it is standard MMC it must looks like:
    *MMC messages*
    An MMC message (that is sent to, or generated by, an MMC device) is:
    *F0 7F deviceID 06 command F7*
    The third byte is the Device ID.
    The fifth byte is the command:
    01 Stop
    02 Play
    03 Deferred Play
    04 Fast Forward
    05 Rewind
    06 Record Strobe (Punch In)
    07 Record Exit (Punch out)
    08 Record Ready (Record Pause)
    09 Pause
    0A Eject
    0B Chase
    0F MMC Reset
    40 Write
    44 Locate/Go to
    47 Shuttle
    Where the Roland Device ID is 41 as far as I remember.
    You can try the S1 & S2 start/play function but first enable "Listen to MMC Input" logic sync setting ( see the pic below ).
    I downloaded the User Manual of the RD-700GX as well, so in page 103 I found "Transmitting the Control Change (USER CC)". can you try to assign for S1 & S2 buttons ? If yes then assign CC13 for S1 and CC14 for S2 ( values 0 for example ). After that try to learn the Logic Keycommands dialog for play stop using this buttons - see my first post picture.
    !http://img707.imageshack.us/img707/9002/mmc.gif!
    !http://img59.imageshack.us/img59/4967/aglogo45.gif! [www.audiogrocery.com|http://www.audiogrocery.com]

  • Logic pro 9 problems with yosemite

    I use a PreSonus Audio Box 22VSL audio interface to run my Logic 9 Pro studio and ever since I upgraded to Yosemite, it hasn't worked properly.  What's the problem?

    Assuming you are running the v1.3 version of the PreSonus Drivers/firmware etc... (and if not, try them out to see if they help even though they are only certified for 10.9.4)
    http://www.presonus.com/support/downloads/AudioBox-22VSL
    Then the problem is.. you didn't check to see if your 22VSL was compatible with Yosemite before you upgraded your OS X.....
    Latest OS X & Logic Pro Compatibility Information
    Solution?
    Roll back to your previous configuration using the backups that you made before upgrading... (You did make backups yes?)
    or...
    Wait until PreSonus release updated drivers/firmware for their devices.... which may be a while yet based on their previous performance in doing so.

  • Why won't my Mac & Logic Pro detect my input device(s)?

    Hey,
    I'm using a macbook with OSX 10.8.2 and Logic Pro with a steinberg interface. I have also tried a tascam interface that was given to me by a friend to try, but I still have the same problem:
    Logic doesnt detect either of the interfaces, and neither does my mac. However both interfaces detect the computer as indicated by their LEDs. I can switch on things like phantom power on the interfaces themselves, so the connection is live, but neither the computer nor the program can see them.
    I have used this exact setup in the past, but it's been over a year since I used logic and now I'm out of practice and just stumped.
    Any help?

    Alright.., I will try this and hope i´ll do it right. My (a little older ) MacBook Pro has the same problem, it just wont shut down. Things works kind of fine until I shall shut it down, cause then the wheel will spin and spin and spin (and it goes to sleep still spinning), so it must be some corrupted files or app that is stuck. I just bought MacOs10.6.3 to reinstall or recover the harddrive, but I´ve never done these things on a Mac before. I have formated in Windows alright, but I am worried about the drivers, I dont know how to back them up! ??? Where do I find them? I hope I dont have to wipe the disc out fully, that it helps with just some cleaning up. I will come back after my "operation".. please wish me good luck! I really dont want it to crash completely.. Thank you for all the information I had here. See you soon.. '
    / Maria

  • Logic Pro 9 problems with 10.7.4

    Hello!
    When I work with Logic Pro 9 (9.1.7) and OS X Lion 10.7.4 - Logic crashes and freezes about 2-3 times a day. Never have I noticed this situation before.
    Maybe I should install Combo Update of OS X?
    I need it to live performances and propably I should come back to Snow Leopard?
    I have MBP 15 (early 2011)
    Anybody knows the problem??

    I'm having similar problems with Logic Pro Studio 8 after I updated to 10.7.4 last night. I can work for about 15 to 20 minutes and then Logic freezes and I have to Force Quit. Logic was relatively fine in Lion up until now, even though there are odd slider bar behaviors, which I'm learning to live with. Freezing is an issue that I can't live with. Yikes!
    In the particular song I'm working on there are no 3rd party plug-ins being used. All native Logic stuff.

  • Logic Pro X Problem please Help!

    Hello, I have an iMac 2013 with maverick IOS X 10.9.1.I bought Logic Pro X and sound card Alesis IO2express.I ll try to open an Audio track and i see the Input 1 but when i press create i can't see anymore the input 1 where i have my mic.Its No Inputs on the new track.I dont know what to do, i think i tried everything.Pls if someone knows tell me! I bought the programm 179euros and the sound card 104 euros and i cant use them.I have the Rode NT2 mic.Pls HELP

    nenikos1 wrote:
    Hello, I have an iMac 2013 with maverick IOS X 10.9.1.I bought Logic Pro X and sound card Alesis IO2express.I ll try to open an Audio track and i see the Input 1 but when i press create i can't see anymore the input 1 where i have my mic.Its No Inputs on the new track.I dont know what to do, i think i tried everything.Pls if someone knows tell me! I bought the programm 179euros and the sound card 104 euros and i cant use them.I have the Rode NT2 mic.Pls HELP
    A known problem with the latest Apple updates.
    It's all over this forum, take a look around.

  • Logic Pro 8 problem on new iMac running 10.6.7

    I just purchased a new iMac (3.2 Ghz core i3) running 10.6.7
    I have ran all the system updates.
    I have migrated Logic Pro 8.0.2 from my old iMac (running os 10.4.11).
    I have also performed a clean install of Logic Pro and am still having same issue, which is:
    When trying to open Logic, it starts to load various AUs, and other startup items, and then simply "quits." I have de-installed all my 3rd party products. This install of logic is an upgrade from Logic 7, upgraded from logic 6.
    Any thoughts on why it is not running? (PS. none of the apps from the Logic Suite are running, ie... Soundtrack, comressor, etc...)

    Hi
    Did you do all the "ProApplications" support downloads after you installed Logic?
    Also .... maybe this could be the issue with a migration???
    http://support.apple.com/kb/TS2914
    CCT

  • Logic Pro Audio Problems

    Just installed Logic Pro 9 and got this error: "Error code -2 was returned by the Audio driver". Help!

    My audio driver is up to date. However after installation it just keeps crashing when trying to open or play or work on a project. Also throwing this message "System Overload. The audio engine was not able to process all required data in time. (-10011)".

  • Recent logic pro 9 problem

    i have been successfully using logic pro on my imac, however - recently and much to my annoyance the visual image of the audio signal disappears when ever i finish recording- making it a pain to edit.
    The image reappears when i transfer it to my lap top but still nothing on the imac on return - is this just a setting that i am unaware of that somebody may have altered or is something else - please help . thanks

    http://discussions.apple.com/thread.jspa?threadID=2371889&tstart=0

  • Logic pro 8 problems with mavericks

    Logic Pro 8 worked fine with snow leopard. Just upgraded to mavericks and now when the playhead moves across the screen it wipes the track region clean (leaves empty black space). If you use the slider to move the viewable area from Left to Right the area refreshes and becomes viewable again but this is a major pain and a dissapointment.
    Anyone else experience this? Know a fix?
    Thanks.

    Re your comment and assumption: If you choose to buy a new Mac (and that in itself indicates you are not struggling that much financially)  at no point in my post did I say I had done that or even intended to!
    Well, to have to run Mavericks and not being able to downgrade to an older version of OS X indicates you just have bought a recent Mac.... because modern Macs cannot run, say Snow Leopard as that particular OS X doesn't support the modern hardware found in recent Macs..
    That is, of course...unless you meant there is a different reason why you can't/won't downgrade? If the latter is the case then that is a choice you are making based on your own priorities.. which was the other point i was trying to make.
    Re your: and complaining about it here.. is a waste of everyone's time... surely noone is under any obligation to reply, or even to read a post. And "everyone" in this case appears to be just octopi and you! Goodness me.
    Actually.. I was refering to yourself (and others who do much the same thing) more than anyone else.... As I said, because Apple 'isn't here" complaining here about Apple's actions is frankly a waste of your time (and efforts) and everyone else's for that matter. hence why I included that link which demonstrates a much more effective manner of getting across your displeasure with Apple's polivies.. to Apple themselves!
    I don't believe that octopi's post indicated any form of arrogance or bullying.. Just him venting the much felt frustration over posts from people who don't do the proper research prior to upgrading their OS X and then complaining about it later!
    Again, these type of posts are  all too common here and in other such forums.. and after a while it does get a bit old you know.... especially when there is post after post on the same subject which few people take the time to read first before posting up their own post... repeating what has been said countless times before.
    So please bear that in mind before passing judgement on octopi who actually does a great deal of good for the most part, and spends a good deal of his (unpaid) time.. helping out other users.. in these forums...
    Cheers..
    Nigel

  • My Main Logic Pro 7 Problems

    I am new to logic..
    I use a G4 powerbook 1Gb with Mbox.
    In Logic there is an error: while trying to synchronize midi and audio.
    Something with the SMPTE -I think. How do I fix this?
    One other thing. If I record directly on my external hard drive..-will there be a problem with the playback and sound?
    Will there a problem with the PCI bus? I read somewhere that I should perhaps move my slot forward.
    And finally..Could someone tell me a way to work with logic and pro tools without running into problems with the external interface (Mbox) settings - everytime I open pro tools after being in Logic or the other way around.
    Sorry for the inconvenience.
    Hopefully I will get some answers soon.

    Hopefully I will get some answers soon.
    i am sure you will get loads of answers soon. your syncronization errors can be due to difference in frame rate expected by your interface or by logic. make sure that - as you are in london - they are set to PAL standards ie 25 fps. you can set this in song settings-> syncronization.
    it is infact recommended to record onto an external harddrive, as they are faster than your p[owerbook internal drive and in case your system drive is often needed for system related activities. as far as your pci bus is concerned i can't see what problems you are worried about.
    as far as problems with protools and logic and mbox, can't help you there except to say if you have logic i don't see the need to use protools anyway. but others may have advice relating to that.
    good luck

  • Logic Pro Midi Kontakt Issue...

    I've just bought the Spitfire Albion 1 library and love it already. Although there is one problem which I can't seem to find the answer to anywhere, which is that when i am recording for instance a legato strings section from my midi keyboard, and using the kontakt modwheel (my keyboard doesn't have a modwheel, so i use the one on the kontakt interface), moving the mod wheel up and down makes all the difference it should, however when I stop recording and play back what i have recorded, it is wherever the mod wheel is placed after that determines the sound outcome. This means i can only have one modwheel value for one recording, which restricts the dynamics of compositions. Hope that all made sense and wondering how i can fix it? I'm relatively new to logic and kontakt, so am unsure about the whole situation

    Hi
    Kontakt does not pass the internal Mod Wheel info out to Logic. For libraries such as Albion, recording into Logic or creating the MIDI CC info offline, is essential.
    You could manually create it using MIDI Draw, the Step Editor etc., though you may want to look into getting an additional keyboard or controller with a decent Mod Wheel.
    CCT

Maybe you are looking for