Why is my Keystation Pro 88 keyboard changing my Logic screensets?

After just installing my Apogee Ensemble, I inadvertantly turned it off while inserting a hi-Z instrument (easy to do - be careful!). I got a black OSX screen with instructions to restart. Since then, any note I play on my Keystation Pro 88 controller sends a MIDI control message to Logic, which changes the screen view, or turns on the metronome, or whatever. Also, My MIDI Express XT shows MIDI signal present at ALL outputs when I hit any key on the keyboard. Also, hitting certain computer keyboard letters will make a MIDI-generated sound elsewhere. In other words, MIDI control signals are flying everywhere!
All my settings in Audio-MIDI Control look normal.
Do I need to reinstall Logic?

I'll try that. Another clue, however: my Mackie Universal Control also send incorrect messages; ie. fader adjustments result in pitch changes, transport controls do not work, etc.

Similar Messages

  • Why is my Mac Pro wireless keyboard not being found after changing batteries

    Why does my Mac Pro not find the wireless keyboard after changing the batteries.  I restarted the computer but it still doesn't recognize the keyboard?

    Troubleshooting wireless mouse and keyboard issues
    OS X: Bluetooth devices become unresponsive

  • Why has my macbook pro serial number changed after getting it repaired?

    I just noticed that the serial number in the 'about this mac' information has a different serial number to what is on the back of the macbook pro, which is the same serial number on my apple care/phone . I had a lot of issues with my macbook pro it was sent to repair in july 2013 then in august 2013. Why has the serial number changed? I tried using my original serial number to use the online apple care service however it did not recgonice my serial number when I tried the new serial number it regconised it but said I did not have apple care but I do. I don't know what the apple team have done to my macbook as it requires to go in for repair again.

    Was it repaired at Apple or an authorized service provider?
    You need to contact the repair place/store and/or call Apple and make them aware of the problem - sooner rather than later. Make sure you give them the repair/case number so they can find the paperwork for it.
    I had a logic board replaced and the tech also did not do anything - I called Apple and the tech came back to my house to take care of it. It's important because you want to make sure that your Applecare is being associated with the right serial number.

  • Why is my Macbook pro Maverick keyboard frize

    I was working with my new Maverick when the keyboard froze on me twice in 10 minutes. I have to restart the system to be able to use it every time it happens. In total since picking up my Maverick the next day it was made available for sale. I have had this problem four time. technical team done all they can, but still getting the same problem.
    I am still within the warranty should I return it for a new one or give them the chance to put it right? But again, it's a new prices computer I should not be experiencing this.

    It sounds like you're having the freeze issue many of us are having:
    https://discussions.apple.com/thread/5481839?start=0&tstart=0
    So far Apple seems to be aware of the problem but there isn't a solid conclusion on whether it's hardware or software related.

  • Why does my macbook pro 2011 keyboard/trackpad make noises like it's bending/crinkling when i move the computer?

    Happens when i reposition the macbook.  Also occurs when i apply slight pressure to case (wresting my wrists on it), but doesn't require it to happen.  2011 Thunderbolt 15" macbook pro - stock.

    Check if an AASP (Apple Authorised Service Provider) is closer, as some do not trust Geek Squad to diagnose something as simple as "all the keys are missing". But judge for yourself.: http://support.apple.com/kb/HT1434

  • KeyStation Pro 88 midi- usb broken 10.4.11

    Can't think of a better place to post this given the expertise in the forum. I have a problem with my Keystation Pro 88 which I'm using as a USB-midi interface. I have a Mackie Control connected to it.
    Started LP8 last night and it couldn't see the MCU anymore. I tried trashing prefs but it didn't help. In fact, LP8 crashed when I tried to re-add the MCU.
    In Audio Midi Setup meanwhile there is no Midi Out on port 2 on the Keystation - which there should be. I've tried trashing prefs and starting again with all that but try as I might I can't get AMS to recognise the midi out on port 2. This is regardless of the setting of "Midi out via USB" on the KS. To make it worse, AMS crashes fairly regularly now.
    I can't find anything else out there about this.
    I have updated to 10.4.11 and it was working before the update. Maybe it was working after as well but I've been sick and travelling for a few weeks so haven't sat down in the studio for a while.
    Any ideas? Really stuck!
    Thanks very much!
    Mac Pro 4x2ghz, 2gb; Mackie Onyx Satellite; Keystation Pro 88; Akai MPD16; MCU; Logic Studio
    Here is a representative crash log from AMS:
    Date/Time: 2007-12-12 16:55:31.592 +0000
    OS Version: 10.4.11 (Build 8S2167)
    Report Version: 4
    Command: Audio MIDI Setup
    Path: /Applications/Utilities/Audio MIDI Setup.app/Contents/MacOS/Audio MIDI Setup
    Parent: WindowServer [86]
    Version: 2.1.1 (2.1.1)
    Build Version: 142
    Project Name: AudioConsole
    Source Version: 510000
    PID: 293
    Thread: 0
    Exception: EXCBADACCESS (0x0001)
    Codes: KERNPROTECTIONFAILURE (0x0002) at 0x00000000
    Thread 0 Crashed:
    0 libobjc.A.dylib 0x90a594c7 objc_msgSend + 23
    1 com.apple.AppKit 0x9331342b -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 614
    2 com.apple.AppKit 0x93312493 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 217
    3 com.apple.AppKit 0x93313061 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 3239
    4 com.apple.AppKit 0x93313061 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 3239
    5 com.apple.AppKit 0x93313061 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 3239
    6 com.apple.AppKit 0x93313061 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 3239
    7 com.apple.AppKit 0x93313061 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 3239
    8 com.apple.AppKit 0x93313061 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 3239
    9 com.apple.AppKit 0x93311b98 -[NSThemeFrame _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 290
    10 com.apple.AppKit 0x93311382 -[NSView _displayRectIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:] + 523
    11 com.apple.AppKit 0x93310cae -[NSView displayIfNeeded] + 439
    12 com.apple.AppKit 0x93310a52 -[NSWindow displayIfNeeded] + 168
    13 com.apple.AppKit 0x93360d8c _handleWindowNeedsDisplay + 206
    14 com.apple.CoreFoundation 0x9082dd0e __CFRunLoopDoObservers + 342
    15 com.apple.CoreFoundation 0x9082cdb0 CFRunLoopRunSpecific + 827
    16 com.apple.CoreFoundation 0x9082ca6e CFRunLoopRunInMode + 61
    17 com.apple.HIToolbox 0x92def878 RunCurrentEventLoopInMode + 285
    18 com.apple.HIToolbox 0x92deef82 ReceiveNextEventCommon + 385
    19 com.apple.HIToolbox 0x92deedd9 BlockUntilNextEventMatchingListInMode + 81
    20 com.apple.AppKit 0x93295485 _DPSNextEvent + 572
    21 com.apple.AppKit 0x93295076 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 137
    22 com.apple.AppKit 0x9328edfb -[NSApplication run] + 512
    23 com.apple.AppKit 0x93282d4f NSApplicationMain + 573
    24 com.apple.audio.AudioMIDISetup 0x000028ea 0x1000 + 6378
    25 com.apple.audio.AudioMIDISetup 0x00002811 0x1000 + 6161
    Thread 1:
    0 libSystem.B.dylib 0x900248c7 semaphorewait_signaltrap + 7
    1 com.apple.Foundation 0x9284d250 -[NSConditionLock lockWhenCondition:] + 39
    2 com.apple.AppKit 0x9336c2a4 -[NSUIHeartBeat _heartBeatThread:] + 377
    3 com.apple.Foundation 0x927f72c0 forkThreadForFunction + 123
    4 libSystem.B.dylib 0x90024227 pthreadbody + 84
    Thread 2:
    0 libSystem.B.dylib 0x90009cd7 machmsgtrap + 7
    1 com.apple.audio.midi.CoreMIDI 0x96ac693b XServerMachPort::ReceiveMessage(int&, void*, int&) + 101
    2 com.apple.audio.midi.CoreMIDI 0x96abee8d MIDIInPortThread::Run() + 113
    3 com.apple.audio.midi.CoreMIDI 0x96abfb6d XThread::RunHelper(void*) + 17
    4 com.apple.audio.midi.CoreMIDI 0x96ac74ad CAPThread::Entry(CAPThread*) + 93
    5 libSystem.B.dylib 0x90024227 pthreadbody + 84
    Thread 3:
    0 libSystem.B.dylib 0x90009cd7 machmsgtrap + 7
    1 com.apple.CoreFoundation 0x9082d253 CFRunLoopRunSpecific + 2014
    2 com.apple.CoreFoundation 0x9083e128 CFRunLoopRun + 60
    3 com.apple.DVCPROHDMuxer 0x165770fb AVS::DestroyAVCDeviceController(AVS::AVCDeviceController*) + 297
    4 libSystem.B.dylib 0x90024227 pthreadbody + 84
    Thread 0 crashed with X86 Thread State (32-bit):
    eax: 0x00000000 ebx: 0x93313746 ecx: 0x938e8538 edx: 0x0030afa0
    edi: 0x00000008 esi: 0x0030aeb0 ebp: 0xbfffdd58 esp: 0xbfffdb84
    ss: 0x0000001f efl: 0x00010206 eip: 0x90a594c7 cs: 0x00000017
    ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037
    Binary Images Description:
    0x1000 - 0x46fff com.apple.audio.AudioMIDISetup 2.1.1 /Applications/Utilities/Audio MIDI Setup.app/Contents/MacOS/Audio MIDI Setup
    0x16276000 - 0x1627bfff com.apple.audio.AppleHDAHALPlugIn 1.3.7 (1.3.7a23) /System/Library/Extensions/AppleHDA.kext/Contents/PlugIns/AppleHDAHALPlugIn.bun dle/Contents/MacOS/AppleHDAHALPlugIn
    0x162c6000 - 0x162c9fff com.apple.LiveType.component 2.1.2 /Library/QuickTime/LiveType.component/Contents/MacOS/LiveType
    0x16423000 - 0x16479fff com.apple.DVCPROHDAudio 1.3 /Library/Audio/Plug-Ins/HAL/DVCPROHDAudio.plugin/Contents/MacOS/DVCPROHDAudio
    0x164d8000 - 0x1653dfff com.apple.LiveType.framework 2.1.2 /System/Library/PrivateFrameworks/LiveType.framework/Versions/A/LiveType
    0x16565000 - 0x165affff com.apple.DVCPROHDMuxer 1.3 /Library/QuickTime/DVCPROHDMuxer.component/Contents/MacOS/DVCPROHDMuxer
    0x8fe00000 - 0x8fe4afff dyld 46.16 /usr/lib/dyld
    0x90000000 - 0x90171fff libSystem.B.dylib /usr/lib/libSystem.B.dylib
    0x901c1000 - 0x901c3fff libmathCommon.A.dylib /usr/lib/system/libmathCommon.A.dylib
    0x901c5000 - 0x90202fff com.apple.CoreText 1.1.3 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreText.framework/Versions/A/CoreText
    0x90229000 - 0x902fffff ATS /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ATS.framework/Versions/A/ATS
    0x9031f000 - 0x90774fff com.apple.CoreGraphics 1.258.77 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/CoreGraphics
    0x9080b000 - 0x908d3fff com.apple.CoreFoundation 6.4.8 (368.31) /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
    0x90911000 - 0x90911fff com.apple.CoreServices 10.4 (???) /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
    0x90913000 - 0x90a07fff libicucore.A.dylib /usr/lib/libicucore.A.dylib
    0x90a57000 - 0x90ad6fff libobjc.A.dylib /usr/lib/libobjc.A.dylib
    0x90aff000 - 0x90b63fff libstdc++.6.dylib /usr/lib/libstdc++.6.dylib
    0x90bd2000 - 0x90bd9fff libgcc_s.1.dylib /usr/lib/libgcc_s.1.dylib
    0x90bde000 - 0x90c51fff com.apple.framework.IOKit 1.4.8 (???) /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
    0x90c66000 - 0x90c78fff libauto.dylib /usr/lib/libauto.dylib
    0x90c7e000 - 0x90f24fff com.apple.CoreServices.CarbonCore 682.28 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/A/CarbonCore
    0x90f67000 - 0x90fcffff com.apple.CoreServices.OSServices 4.1 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServi ces.framework/Versions/A/OSServices
    0x91008000 - 0x91047fff com.apple.CFNetwork 129.22 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CFNetwo rk.framework/Versions/A/CFNetwork
    0x9105a000 - 0x9106afff com.apple.WebServices 1.1.3 (1.1.0) /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/WebServ icesCore.framework/Versions/A/WebServicesCore
    0x91075000 - 0x910f4fff com.apple.SearchKit 1.0.7 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchK it.framework/Versions/A/SearchKit
    0x9112e000 - 0x9114cfff com.apple.Metadata 10.4.4 (121.36) /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadat a.framework/Versions/A/Metadata
    0x91158000 - 0x91166fff libz.1.dylib /usr/lib/libz.1.dylib
    0x91169000 - 0x91308fff com.apple.security 4.5.2 (29774) /System/Library/Frameworks/Security.framework/Versions/A/Security
    0x91406000 - 0x9140efff com.apple.DiskArbitration 2.1.2 /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
    0x91415000 - 0x9141cfff libbsm.dylib /usr/lib/libbsm.dylib
    0x91420000 - 0x91446fff com.apple.SystemConfiguration 1.8.6 /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfi guration
    0x91458000 - 0x914cefff com.apple.audio.CoreAudio 3.0.5 /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio
    0x9151f000 - 0x9151ffff com.apple.ApplicationServices 10.4 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Application Services
    0x91521000 - 0x9154dfff com.apple.AE 314 (313) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ AE.framework/Versions/A/AE
    0x91560000 - 0x91634fff com.apple.ColorSync 4.4.9 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ColorSync.framework/Versions/A/ColorSync
    0x9166f000 - 0x916e2fff com.apple.print.framework.PrintCore 4.6 (177.13) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ PrintCore.framework/Versions/A/PrintCore
    0x91710000 - 0x917b9fff com.apple.QD 3.10.25 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ QD.framework/Versions/A/QD
    0x917df000 - 0x9182afff com.apple.HIServices 1.5.2 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ HIServices.framework/Versions/A/HIServices
    0x91849000 - 0x9185ffff com.apple.LangAnalysis 1.6.3 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ LangAnalysis.framework/Versions/A/LangAnalysis
    0x9186b000 - 0x91886fff com.apple.FindByContent 1.5 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ FindByContent.framework/Versions/A/FindByContent
    0x91891000 - 0x918cefff com.apple.LaunchServices 182 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ LaunchServices.framework/Versions/A/LaunchServices
    0x918e2000 - 0x918eefff com.apple.speech.synthesis.framework 3.5 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ SpeechSynthesis.framework/Versions/A/SpeechSynthesis
    0x918f5000 - 0x91935fff com.apple.ImageIO.framework 1.5.6 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/ImageIO
    0x91948000 - 0x919fafff libcrypto.0.9.7.dylib /usr/lib/libcrypto.0.9.7.dylib
    0x91a40000 - 0x91a56fff libcups.2.dylib /usr/lib/libcups.2.dylib
    0x91a5b000 - 0x91a79fff libJPEG.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libJPEG.dylib
    0x91a7e000 - 0x91addfff libJP2.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libJP2.dylib
    0x91aef000 - 0x91af3fff libGIF.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libGIF.dylib
    0x91af5000 - 0x91b7dfff libRaw.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libRaw.dylib
    0x91b81000 - 0x91bbefff libTIFF.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libTIFF.dylib
    0x91bc4000 - 0x91bdefff libPng.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libPng.dylib
    0x91be3000 - 0x91be5fff libRadiance.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libRadiance.dylib
    0x91be7000 - 0x91cc5fff libxml2.2.dylib /usr/lib/libxml2.2.dylib
    0x91ce2000 - 0x91ce2fff com.apple.Accelerate 1.3.1 (Accelerate 1.3.1) /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate
    0x91ce4000 - 0x91d72fff com.apple.vImage 2.5 /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.fr amework/Versions/A/vImage
    0x91d79000 - 0x91d79fff com.apple.Accelerate.vecLib 3.3.1 (vecLib 3.3.1) /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/vecLib
    0x91d7b000 - 0x91dd4fff libvMisc.dylib /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libvMisc.dylib
    0x91ddd000 - 0x91e01fff libvDSP.dylib /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libvDSP.dylib
    0x91e09000 - 0x92212fff libBLAS.dylib /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libBLAS.dylib
    0x9224c000 - 0x92600fff libLAPACK.dylib /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libLAPACK.dylib
    0x9262d000 - 0x9271afff libiconv.2.dylib /usr/lib/libiconv.2.dylib
    0x9271c000 - 0x92799fff com.apple.DesktopServices 1.3.6 /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/Desk topServicesPriv
    0x927da000 - 0x92a0afff com.apple.Foundation 6.4.9 (567.36) /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
    0x92b24000 - 0x92b3bfff libGL.dylib /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib
    0x92b46000 - 0x92b9efff libGLU.dylib /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib
    0x92bb2000 - 0x92bb2fff com.apple.Carbon 10.4 (???) /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
    0x92bb4000 - 0x92bc4fff com.apple.ImageCapture 3.0.4 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture. framework/Versions/A/ImageCapture
    0x92bd3000 - 0x92bdbfff com.apple.speech.recognition.framework 3.6 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecogni tion.framework/Versions/A/SpeechRecognition
    0x92be1000 - 0x92be7fff com.apple.securityhi 2.0.1 (24742) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.fr amework/Versions/A/SecurityHI
    0x92bed000 - 0x92c7efff com.apple.ink.framework 101.2.1 (71) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework /Versions/A/Ink
    0x92c92000 - 0x92c96fff com.apple.help 1.0.3 (32.1) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framewor k/Versions/A/Help
    0x92c99000 - 0x92cb7fff com.apple.openscripting 1.2.5 (???) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting .framework/Versions/A/OpenScripting
    0x92cc9000 - 0x92ccffff com.apple.print.framework.Print 5.2 (192.4) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framewo rk/Versions/A/Print
    0x92cd5000 - 0x92d38fff com.apple.htmlrendering 66.1 (1.1.3) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HTMLRendering .framework/Versions/A/HTMLRendering
    0x92d5f000 - 0x92da0fff com.apple.NavigationServices 3.4.4 (3.4.3) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/NavigationSer vices.framework/Versions/A/NavigationServices
    0x92dc7000 - 0x92dd5fff com.apple.audio.SoundManager 3.9.1 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CarbonSound.f ramework/Versions/A/CarbonSound
    0x92ddc000 - 0x92de1fff com.apple.CommonPanels 1.2.3 (73) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels. framework/Versions/A/CommonPanels
    0x92de6000 - 0x930dbfff com.apple.HIToolbox 1.4.10 (???) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.fra mework/Versions/A/HIToolbox
    0x931e1000 - 0x931ecfff com.apple.opengl 1.4.16 /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL
    0x9327c000 - 0x9327cfff com.apple.Cocoa 6.4 (???) /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa
    0x9327e000 - 0x93934fff com.apple.AppKit 6.4.9 (824.44) /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
    0x93cb5000 - 0x93d30fff com.apple.CoreData 91 (92.1) /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData
    0x93d69000 - 0x93e22fff com.apple.audio.toolbox.AudioToolbox 1.4.7 /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox
    0x93e65000 - 0x93e65fff com.apple.audio.units.AudioUnit 1.4.2 /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit
    0x93e67000 - 0x94028fff com.apple.QuartzCore 1.4.12 /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
    0x9406e000 - 0x940affff libsqlite3.0.dylib /usr/lib/libsqlite3.0.dylib
    0x940b7000 - 0x940f1fff libGLImage.dylib /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dyl ib
    0x940f6000 - 0x9410cfff com.apple.CoreVideo 1.4.2 /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo
    0x942a0000 - 0x942affff libCGATS.A.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/Resources/libCGATS.A.dylib
    0x942b6000 - 0x942c1fff libCSync.A.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/Resources/libCSync.A.dylib
    0x9430d000 - 0x94327fff libRIP.A.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/Resources/libRIP.A.dylib
    0x9432d000 - 0x94642fff com.apple.QuickTime 7.3.0 /System/Library/Frameworks/QuickTime.framework/Versions/A/QuickTime
    0x96aba000 - 0x96af0fff com.apple.audio.midi.CoreMIDI 1.5.1 (41) /System/Library/Frameworks/CoreMIDI.framework/Versions/A/CoreMIDI
    Model: MacPro1,1, BootROM MP11.005C.B08, 4 processors, Dual-Core Intel Xeon, 2 GHz, 2 GB
    Graphics: NVIDIA GeForce 7300 GT, NVIDIA GeForce 7300 GT, PCIe, 256 MB
    Memory Module: DIMM Riser A/DIMM 1, 512 MB, DDR2 FB-DIMM, 667 MHz
    Memory Module: DIMM Riser A/DIMM 2, 512 MB, DDR2 FB-DIMM, 667 MHz
    Memory Module: DIMM Riser B/DIMM 1, 512 MB, DDR2 FB-DIMM, 667 MHz
    Memory Module: DIMM Riser B/DIMM 2, 512 MB, DDR2 FB-DIMM, 667 MHz
    AirPort: spairportwireless_card_type_airportextreme (0x14E4, 0x87), Broadcom BCM43xx 1.0 (4.170.13.1)
    Bluetooth: Version 1.9.5f4, 2 service, 0 devices, 1 incoming serial ports
    Network Service: AirPort, AirPort, en2
    PCI Card: NVIDIA GeForce 7300 GT, Display, Slot-1
    Serial ATA Device: WDC WD2500JS-41SGB0, 232.89 GB
    Serial ATA Device: WDC WD800JD-00JNC0, 74.53 GB
    Parallel ATA Device: PIONEER DVD-RW DVR-111D
    USB Device: Hub in Apple Pro Keyboard, Mitsumi Electric, Up to 12 Mb/sec, 500 mA
    USB Device: Optical USB Mouse, Logitech, Up to 1.5 Mb/sec, 100 mA
    USB Device: Apple Pro Keyboard, Mitsumi Electric, Up to 12 Mb/sec, 250 mA
    USB Device: Keystation Pro 88, Evolution Electronics Ltd., Up to 12 Mb/sec, 500 mA
    USB Device: Bluetooth USB Host Controller, Apple, Inc., Up to 12 Mb/sec, 500 mA
    FireWire Device: built-in_hub, unknown_value, Unknown
    FireWire Device: LaCie d2 Extreme LUN 0, LaCie Group SA, Up to 800 Mb/sec
    FireWire Device: Mackie Onyx Satellite, Loud Technologies Inc., Up to 400 Mb/sec

    Bee Jay wrote:
    If you are having weird issues with AMS and MIDI drivers, try trashing user*/library/preferences/ByHost/com.apple.MIDI. and giving it a restart. Your can also try trashing your user/Caches folder as well...
    Well, AMS still crashes and the port is still missing but Logic now sees my Mackie Control again so all that needs to work, does after trying your suggestion. Cheers!
    Will nurse it along and to a complete fresh install with Leopard at some point in the future.
    Thanks again.

  • Changing the logic board

    will I lose my apps in my macbook pro if I change the logic board? For example, I have Logic Pro 8 on my macbook pro. My mac didn't turn on anymore, I went to the Apple store and they told me that I need to change the logic board. If I get the logic board fix, or replaced, will I lose my apps (Logic Pro 8) or will the app still be on there? Please respond because I don't want to lose my projects and the software.
    Thanks

    Not off topic ... this is *YOUR* post ...
    To start, you can sell your old one for the parts that still work (SuperDrive, display, ...).  Gives you some money back on a new one. 
    And PLEASE do not read my following statements as "just pay to fix it" ... I am just stating facts and I for one would probably buy new and sell old for parts
    Second ... *most* new units come with Lion, and due to the firmware (PCs have BIOS on EPROMs, Machas "EFI Firmware), getting anthing less than Lion to run is tricky (just look up the number of existing posts on this subject).  Some have successfully pulled it off, but it all sounds complicated and I like haing an SL-initial unit.
    But do not despair ... some people have hoarded stocks of MBP that can easily run SL because they actually came initally with SL so gray install disks come free.  If you start a post asking who knows these vendors, you should get an answer.
    Also ... with apologies if you did not know this (as if you had no read anythingthing else I wrote) ...
    Lion does not support PPC software anymore because Rosetta is not supported.  Could be higher software replacement costs if you do not intensely look for one of the few SL-initial MBP.
    If you want to and want to avoid Lion (I have no valid opinion on why you should ... just saying if you want to) then start a thread on "Who knows the venors of existing pre-Lion MBP?".
    I only mention the Lion issue because even if you put your old HD into an external enclosure, Lion-ready systems may not boot off that old system with applications you already have installed, and you wold be reloading all apps anyway.
    I will stop so you can catch up, and ask more.
    Or just jump straight to my recommended post and ask your question about saving old HD and SL-ready MBPs.

  • Why the mouse pointer in Logic Pro does not change shape during work in OSX 10.9.1?

    I've a MacBook Pro Retina 15-inch Late 2013 and I'm using two external displays. One connected to to the HDMI port (display 1) the other to thunderbolt (display 2). The MacBook display is closed. I’m working with Logic Pro 9.1.8 (32bit) with OSX 10.9.1
    Why the mouse pointer in Logic Pro does not change shape during work???
    It was already difficult with OSX 10.9 but now after upgrading to 10.9.1 it's game over!
    At least before I could select which display use Logic Pro to have all the shape functions of the pointer. Not in both displays, so to be forced to edit in ONLY ONE of the two displays using this workaround: (right click on Logic icon in Dock: Option --> Desktop on Display 1). Now or I select “Option --> All Desktops” or does not work. However, by selecting all displays you say goodbye to Mission Control. This can’t be a solution!!!
    The amazing thing is that Nuendo has no problem while Logic Pro, Apple's native software, it can't!
    With Nuendo it’s indifferent in which display you are working, the shape of the mouse pointer changes shape depending on the requirement in both displays.
    This thing drives me crazy!
    Solutions?
    Here some ideas in other foums:
    http://www.logicprohelp.com/forum/viewtopic.php?f=1&t=86264
    But this aren't really solutions but workarounds. Use Logic in all desktops makes Mission Control useless!!

    I installed all over again by formatting as suggested by the genes of pro application support. Each plug-in, each virtual instrument, a job that lasted 3 days. And as suggested for each new plug-in I proceeded to check the proper functioning of Logic Pro and did each time a back up with Time Machine.
    The Result:
    Logic works as it should ONLY on the primary monitor and ONLY on the first desktop.
    BUT
    Reason and Nuendo dont' have this issue !!
    I believe that Apple developers are thinking only to mobile phones and things like messages or face time.
    And that's not all!
    After a few weeks, perhaps by installing a version of Adobe Acrobat, I say maybe because I'm not sure, logic has stopped working properly. Again problems with the mouse pointer.
    Luckily I had a back up! But now I'm terrified to install new programs. Thanks Apple!

  • HT3887 why do i keep losing my keyboard, I've changed batteries which are now 100%?

    why do i keep losing my keyboard, I've changed batteries which are now 100%?

    Hello:
    Try a couple of things:
    1.     Reset PRAM.
    2.     Make the device a favorite.
    Barry 

  • Why does the setting of trackpad always changes everytime i turn off my Macbook pro?

    why does the setting of trackpad always changes everytime i turn off my Macbook Pro?

    Sure ,  just refer to:
    http://support.apple.com/kb/ht1379
    http://support.apple.com/kb/HT3964

  • Why is my MacBook Pro **crashing** changing to a blue screen with lines or distorted screen when I open logic or Ableton Live

    Why is my MacBook Pro **crashing** changing to a blue screen with lines or distorted screen when I open logic or Ableton Live. Then I have to restart by long pressing the power button. Can somebody plz help me

    What you describe sounds like a hardware issue. Unfortunately, you'll need to get that checked out by Apple. If you have an Apple Store near you, make an appointment with the Genius Bar and take the machine in for evaluation.

  • My 3 apple products, an imac, a macbook air and a macbook lost their contact with their external hard disks. They were LaCie make. And every time I turn my laptops, I find the positions of the keys on their  keyboards changed.  Why is Apple silent?

    After the latest apple IOS upgrade my 3 apple products, an imac, a macbook air and a macbook, lost their contact with their external hard disks. They were LaCie make. And every time I turn my laptops, I find the positions of the keys on their  keyboards changed.  Why is Apple silent? There are so many people complaining about this issue and expecting Apple to correct this issue that they have created.

    Probably because it's not an Apple issue. I have Lacie EHD's connected to my MBAir and iMac, all work perfectly on Mavericks. In addition I don't have any keyboard issues on any of my Apple products. BTW IOS is only for IOS devices such as iPads, iPods and iPhones, Macs use OS X. The two OS's are seperate  products designed to run on seperate products.

  • How can i change macbook pro a1278 keyboard ?

    how can i change macbook pro a1278 keyboard ?

    Yes. It will be very simple.
    Power down your mac. Hold down the option key on startup.
    You will see disk utility. Go in disk utility and click the erase button for your HDD data.
    Then go into install OS X and install the operating system.
    It will be a completely fresh install ready for selling.

  • Keystation Pro 88 (or other controller) as the Logic Control

    Has anybody got their setup like this? I've been trying to get this to work for the past 6 hours and no luck. Can someone please help me? Just bought Studio 2 days ago and haven't touched it yet cuz I can't get the keyboard to fully work.
    Joined: 17 Jan 2006
    Posts: 55
    Location: Los Angeles
    Posted: Sun Jul 15, 2007 12:03 am Post subject: Keystation Pro 88 (or other controller) as the Logic Control
    I'm sure some of you already know how to do this. I just figured I'd write this up at some point to share with others. The basic idea is to use the Keystaion Pro 88 (or some other MIDI Controller) as an actual Control Surface, or in this case the Logic Control, to have more freedom with the MIDI Controller, i.e. using the group of 8 faders (on the Keystation) to control Volume for tracks 1-8 in the arrange window, and then hitting Bank Right to automatically control tracks 9-16, and as a result making a universal controller not bound by specific channel messages, or MIDI CC Volume messages etc... in short the essence of any Control Surface.
    What I'm describing below is what this app will also do: http://www.opuslocus.com/lcxmu/index.php
    I basically just wanted to avoid using a separate application all together. Keep in mind that the app does simplify the whole process, but Logic inherently can do pretty much everything the app does.
    I recommend reading this in its entirety before attempting.
    KeyStation Pro 88 as Logic Control
    Part One: Add Logic Control as Control Surface
    1. Open Logic.
    2. Preferences / Control Surfaces / Setup...
    3. New / Install / Select your preferred device (in my case Logic Control
    4. Click the icon in the setup window for the Logic Control.
    5. On the left hand side under "Logic Control" you should see an "Out Port:" and "Input:" ... select the desired MIDI in/out through which your device is connected.
    6. Open Preferences / Control Surfaces / Controller Assignments. Make sure you select the "EXPERT VIEW" check box.
    7. You should now see a bunch of different Zones in the Zone column, one of which is "Control Surface: Logic Control"
    8. Create your own Zone, KeyStation Pro 88 (or whatever) using the Plus sign in the bottom left corner of the Controller Assignments window.
    9. Now basically go through the existing parameters already available in the Logic Control Zones, Select what you want. You can select entire Modes or individual Controls / Parameters. You can select multiple values (only multiple Control / Parameters NOT modes) by selecting and dragging or simply with select and holding command.
    10. Command-C the selected Modes and then click back onto you user zone that you created above.
    11. Click inside the Mode column (or Control / Parameter column depending upon what you selected and copied from the Logic Control zones).
    12. Command-V to paste the Modes into your user Zone.
    13. Do this for as many Modes / Controls you want, that your specific MIDI controller interface will be able to handle.
    Part Two: Assigning Input Values
    1. Open Preferences / Control Surfaces / Controller Assignments
    2. Now for each parameter that you copied, you will need to set the input MIDI value from your controller.
    3. Click on your User Zone, then Mode, then the first parameter in the 3rd column.
    4. You should see a "MIDI Input" option (this should already be set correctly as long as you set it earlier in Step 5 of Part One). If it's not set to the correct MIDI input (which I found to be the case sometimes even after Step 5), then change that here.
    5. Next to "Value Change:" you will see a box with MIDI data in it. Delete the existing date by highlight and delete.
    6. Activate "Learn Mode" (bottom right corner of Controller Assignments window) then click within the "Value Change" box, then move the corresponding fader, button etc. The "Value Change" should now show the MIDI data value for that fader. Be careful here, there should only be 3 groups of 2 for data here... if you see 2 groups, of 3 groups, of 2 then typically the FIRST group of 3 should be the value you want here. You can always delete the data, and move the fader again to be sure. The reason for the 2 groups of 3 is not in error: some buttons send TWO MIDI values, one on press and one on release. You can use this to your advantage and assign TWO different functions to these buttons, thus the first (press hold) value can do one thing and the second (release) value can do another. You can also change the MIDI controller to only send 1 message on press and nothing on release, or simply make sure that only the on value is present in the "Value Change" box.
    7. You'll have to do this for all the different knobs / faders etc. on your MIDI controller. There are many shortcuts of course. You can manually type in the Values if you know them. For the Keystation Pro, M-Audio has an app called Enigma that I recommend for changing controller parameters and much more on the Keystation. You can use this app to assign all the actual control data that each button or fader sends to the sequencer, once you know the values you can convert that data to the MIDI data values and enter them into the Value Change box.
    8. Once you're done assigning values to the controllers, you can delete all the Zones except for the user Zone you created earlier. Before you do this, it's a good idea to back up the Control Surface preference file just in case you ever want to grab something else from the Logic Control Zones. You could always add a second Logic Control and copy the Zone from that, but you'd have to reassign all the MIDI Input: values ... short version, just back up the preference file before you delete the Zones. The reason why you want to delete the Zones that you're not using is simply because if you have a controller that happens to send out MIDI data to the sequencer, and the actual Logic Control happens to have that MIDI data value already inherent it it's Zones, then you could be asking for trouble, simply put you'd be sending MIDI data to change Volume and the Logic Control maybe has that MIDI Data Value already assigned to Pan for the existing track.
    The file to backup is located here: ~Users/username/Library/Preferences/Logic/com.apple.logic.pro.cs
    As a precaution I have always backed up my Logic Preference file WITH this .cs file. Technically it's not necessary... for instance: Let's say you trash your preferences and open Logic to find that the Logic Control is missing from the Control Surfaces Setup. So you add it back and now you find out that Logic is missing the User Zone that you created. If you close Logic and copy the .cs file back to the directory above, then upon reopening Logic you should find your User Zone is in place again. But I've had mixed results with that, so just in case I copy over the preference file with the .cs file as a pair. It seems that the Logic pref file only contains information that the Logic Control is a Control Surface on your system and the .cs file is the preferences for that specific Surface.
    Another note: after a recent Logic update, maybe 7.2? ... it was whichever update added support for more Control Surfaces, I can't remember. This update basically erased all the hours of hard work linking the Keystation to Logic as the Logic Control. This only happened with this specific Control Surface update, but not with 7.2.3, probably simply because they didn't make any changes to the .cs pref file.
    Anyhow, when this happens again in the future, there seems to be a quick fix. I take NO responsibility for you somehow crashing Logic on a continual basis after applying the fix. Personally I have seen NO issues by doing this at all. I simply copied a version of the .cs file with the new update missing the Keystation Zone, as well as a version of the .cs file WITH the Keystation Zone, to a PC (I think it was a PC, don't believe I tried it with textedit, although should work as well). I opened both of the files in notepad and compared them. I noticed the word Keystation towards the bottom and realized that most all the data (gibberish) was exactly the same up until a point in which the file with the Keystation data had a group that was absent from the new .cs pref file from the new update. So I basically copied the data from the old .cs pref file, pasted it into the new .cs pref file, saved it and open Logic. Logic warned me that a pref file was corrupt or something of that nature, but loaded fine anyway, and the Keystation Zone was back in Controller Assignments.
    One last thing... the problem that some of you may run into is that by making your MIDI controller a Control Surface, or turning your Keystation Pro into a Logic Control, limits some of the functionality of the MIDI Controller. For instance, a Logic Control's main purpose is to control different faders, knobs and what not of MANY different tracks. When you move a fader for volume on the Logic control, it will move the fader corresponding to the selected track... it's not programed to say change the actual midi CC 7 for Volume, only the actual Fader. Thus, what if you want the MOD wheel to still control modulation and you want the sustatin pedal to continue to act as a sustain pedal. Well, if Logic sees that Port 1 is the input for the Logic Control, but in reality the Keystation, then it's only going to allow specific events through. The way around this issue is by using both the input options that the Keystation has... hook the MIDI out into Logic and use the USB port as well. I run the Keystation as a Logic Control through the USB port, and use the MIDI out for actual MIDI data. But the catch is you have to make sure you only connect the MIDI Port into Logic's sequencer in the environment. Thus open the environment, open Clicks & Ports, Port 1 and Port 2 are the IN/OUT for the USB port. Midi Port is the Keystation's MIDI port. Select and delete the cable for the SUM, and run individual cables for the ports you want to use. Thus, all your other MIDI interface Ports, the Caps Lock keyboard etc. Just be sure that if your using Port 1 (USB Port Out from Keystation) for the fake Logic Control, that it DOES NOT cable into the "Input View" or "to Recording & Thru". This creates yet another issue:
    The controls on the Keystation have to send SOME form of MIDI control message / data to Logic. Well if the faders on the Keystation are preset to send Ch1-9, Volume 0-127 messages, then when you move a fader on the Keystation (as the Logic Control) since the Keystation is still reaching the sequencer from the MIDI port, you will be sending MIDI values that can effect your current track possibly when you don't want to. The work around for this is to be sure that all the faders / knobs that you want to use as your fake Logic Control are sending useless MIDI data... i.e. CC 75, 76, 77, and so on. This way moving faders won't effect playback, although you could still in theory record this MIDI data into your sequencer. You could however filter this events from entering the sequencer input with a transformer since you know precisely what MIDI CC values you are changing. The easy way to assign these values is to use the program Enigma from M-Audio that I mentioned above.
    More discussion specifically related to the Keystation Pro 88:
    You can do a lot using the Controller Assignments and different Zones from the Logic Control. For instance, the real Logic Control has Solo, Mute, and Record buttons for the 8 faders. The Keystation Pro only has 1 button underneath each fader. But you could use one of the other buttons to toggle Solo, Mute, and Record mode so that depending on which mode your in, the buttons underneath each fader will correspond to Mute or Solo etc. By the way, a good setup from my experience is to use the first 8 faders of the Keystation as the track faders, and the final 9th fader for Master Volume. You can then set two of the buttons underneath the Knobs as Bank Left and Bank Right buttons to change the 8 fader tracks to correspond to the onscreen track groups of 8. Also don't forget that you can assign TWO functions to EACH button, since a button press can send a value of 127 and a button release can send a 00 value. So if you press and hold a button it can activate "Shift-select Mode" and until released it can make the buttons under the faders act as Volume to Zero resets or whatever you want. When you release the button it will go back to just Mute mode or Solo mode. The Controller Assignments window has MANY options, and parameters some of which are very confusing and take a lot of trial and error to understand... the manual helps a little but of course isn't perfect.

    I'm thinking about buying a Keystation Pro 88 (2nd hand) so I was googling around and found this:
    http://www.soundonsound.com/sos/Oct04/articles/keystation.htm
    [quote]
    I had some trouble getting the transport controls to work with Emagic's Logic, even when I loaded the 'Pro 88 Logic Preset.LSO' file on the supplied CD-ROM into Logic. I contacted the guys who designed and set up the Keystation here in the UK at the old Evolution offices, and between us we managed to work out what was going wrong. First of all, you need to enter the appropriate MIDI key commands in Logic's user preferences. These cannot be updated with an LSO file, so the commands have to be entered using the Learn Key function in Logic (see the screenshot below for the list we used). Then we discovered that the transport keys were toggling, which meant that only each second press of each key was actually working. It turned out that I had an early version of the Logic preset before this had been fixed, but the more recent one has been put on the M Audio web site for anyone else that needs it. It took about 30 seconds to change the output commands so that the buttons were no longer toggling.[/quote]
    Did you get it to work correctly eventually?

  • Keystation PRO 88

    Greetings, all.
    I recently purchased the Keystation PRO 88. Now, I'm not a village idiot, (some may disagree), but I'm having a heck of a time assigning sliders, controllers, etc.
    I'm going in the following order:
    1. I move a fader on my screen
    2. Logic then asks me to slowly move a hardware fader. I do.
    3. It works ok. I continue the process.
    4. After assigning about three or four faders, my assignments seem to jump all over the place. All of a sudden, I'll have three faders controlling master volume, what I thought was controlling fader 3 is now controlling fader 6, etc.
    BTW, I'm using the #10 generic recall on the Keystation PRO 88.
    I opened up the Logic file that came with the keyboard, but it totally messed with my environment. Naughty, naughty. I've spent enough time setting up my environment.
    Thanks for any insight you all might have.
    Tom

    under the General Preferences for Control Surfaces ... what is your "Resolution for Relative Controls" set to? Default is 128... technically this shouldn't matter or even change anything since the Keystation Pro 88 is not equiped with a high resolution... concerning the faders. But I've had these issues before... I have my resolution set to something like 2000, again probably not actually affecting anything as the keystation sends out only 0-127 values.
    How often does this happen? Is it a few changes here and there? Or is this constant fader crazyness? Could be your controller. Like I said.. I have had similar glitches here and there with my Key Pro 88... but nothing constant.
    The .lso file that comes with the Key Pro 88 is uneccessary as Logic 7 now supports MIDI learn and such. Although, you will find that you cannot assign or 'MIDI Learn' Solo, Record and other "track" functions. Mute, pan and volume work though.
    What I did was add a 'Logic Control' to the controller setup window and assign the MIDI in and out ports to the ports for my Key Pro 88. Then I went into the controller assignments setup and cut all the functions that I wanted to use and pasted them into a new Zone. Then I used the M-Audio program Enigma that works with the Key Pro 88 to change all my buttons / faders to MIDI Control Channel messages... they HAVE to be On/Off messages like press for 127, release is 0... this is how the logic control works. I used all the MIDI CC messages that are unused... for reasons I'll explain later.
    Then you need to know what Hex values the Key Pro 88 is sending for each button / fader... which is simply the hex values of the MIDI CC messages you set above... easiest way to figure this out is to use midi learn and press each button / fader on the Keystation. Unless you know all the MIDI CC hex values (which you can find using the .pdf for the keystation... at the end in the index ... or from plenty of webpages on midi specs). Put these values with their corresponding button number, i.e. C1, C2, in a text file or something.
    Now just paste the correct Hex values in the corresponding 'value' box for each function in the controller assignments window (expert view).
    Also make sure to check the other options below the parameter and value boxes... most of them should be fine.\
    When you're done, exit Logic and backup the com.apple.logic.cs file located in your system library (can't remember exact location.. do a search). This is the full backup with ALL values and functions... even those that you did not assign... but that are left in the controller assignments window because you added a logic control. You should now delete ALL the functions you ARE NOT using from the controller assignments window... just because the logic control actually uses Note On/Off messages and so if you were to play the Keystation's keyboard, you may trigger stop/play or other options. Deleting the unused keys will prevent this. Exit Logic and back up the same file again... after making these changes. If you even want to add a Logic Control function... then use the file with ALL the values, assign what you want and then delete the unused again.
    Last thing to realize is that Logic now sees the Keystation as ONLY a hardware controller.. but you want to use the keyboard for midi as well obviously. Luckily the Keystation has a USB interface for MIDI and a MIDI interface for MIDI. I use the USB for the Logic Control / Hardware controller and then hook up the MIDI for the actual midi keyboard.
    Don't know if you want to do all that... but it works great.
    Hope this helps
    joe

Maybe you are looking for