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

Similar Messages

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

MIDI problems with M-Audio Keystation Pro 88

I have an M-Audio Keystation Pro 88 MIDI keyboard controller I use with any number of DAW's. Lately the MIDI signals have been acting very strangely when I updated to 10.10. I have updated all the MIDI drivers in my library and since the M-Audio products need no drivers for a MAC, there are never updates in either firmware or MIDI drivers.
Example;
When running any of the DAW's I open Kontakt 5 and assign a VI. I right click the volume knob on the VI and tell it to "learn MIDI" and when I move a fader on the KeyStation it's inverted. No gain is now Hi and vice versa. Anyone else having this issue with MIDI in Yosemite?

Thanks Jord,
I have been trying this out. So i set up a new preset bank and say label it 'Live', in this preset bank i then set up my preset.
Everytime the M-Audio is turned off and on will i have to load the new preset bank 'Live' using Enigma, or will it be stored in its memory

M-Audio Keystation Pro 88 and Garageband.

Hi,
I have noticed that some of the faders on my Pro88 change things like track volume and panning in my Garageband. I think that is wonderful and was wondering how I can go ahead and assign more of these faders to control more tracks as well as the main volume. Also, there are Play, Stop, Record, FFw, Rwd buttons on the Pro88, and I have tried unsuccessfully to link them to my Garageband. Any suggestions?
Thanks.
Powerbook g4 Mac OS X (10.3.9)

Apart from the two controls you have found, I believe the only other controllable features are Garageband's transport controls. You can get GarageBand's transport controls to work with the Keystation Pro 88 by downloading and installing GarageRemote. I saved the advice of Steve McNally from this forum in May 2005. I think that thread has been removed from discussions. Please find his advice below.
"Thanks to GarageRemote and its very helpful developer, I've got the KeyStation Pro 88 working with (i.e. controlling) GarageBand.
Here's what I've got working now in GarageRemote's config:
F0 7F 7F 06 02 F7 - Play / Stop
F0 7F 7F 06 06 F7 - Record
F0 7F 7F 06 05 F7 - Rewind
F0 7F 7F 06 04 F7 - Fast Forward
F0 7F 7F 06 01 F7 - Home / Start of Track(*)
(*) - For this, I used the KeyStation's transport control marked "Stop" since GBand's Play and Stop are the same command toggled."
Hope this helps.

Logic Pro X Interface M-Audio Keystation Pro 88

Before I cut my meals (probably a month of lunches) from my Social Security budget take the plunge into Logic X (much more reasonably priced than even previous upgrades) -- has anyone had tips or problems with interfacing any or all functions with M-Audio's Keystation Pro 88 -- my workhorse? I cannot afford to upgrade there keyboard and software.....period and will stick with my old copy of 9 rather than lose the weight.

M-audio is own by Digidesign (Protools), which is owned by Avid. You wont get their gear working on Leopard without paying. Every time Apple releases a new cat in the wild Avid/Digi makes you pay. Get used to it or find some other hardware that wont take weeks or even months to update a simple driver for that hardware you are married to. I stopped using Protools but i'm stuck with their hardware. Learn from my mistake & find yourself a hardware company that keep up with Apple updates like Motu. My Power Mac G4's built in audio driver goes to 192 khz. What's up with that Digi? all that money for 92 khz.

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.

Mainstage with Keystation Pro 88

Hi all,
i'm having big problem mapping buttons on the Keystation pro 88 to the mainstage, all the buttons seem to function at the same time... i can't assign them individually... i have no idea what i've doen wrong here.... all the knobs and faders were mapped perfectly...apart from the buttons... if anyone has any idea please advise.. also... how do i get the master level map to the VU metre?
thank you in advance...

soratach,
I believe I have found the problem. I just recently purchased a Keystation Pro 88, and had the exact same issue, all of the buttons triggered at the same time. The problem lies in the programming of the Keystation Pro, not Mainstage. Try this:
1. On the left side of the Keystation panel, press the button that says "Recall" (it should be the very first one, top left).
2. The internal program number the Keystation is set to will appear as a number between 1 and 10 on the screen. These are the mappings the Keystation comes with from the factory. This mapping can come into conflict with Mainstage's mapping, hence the button problems.
3. Press the number 8 (which is the default program for Logic). You will have to re-learn all of the mapping in your Mainstage concert, but the buttons will function individually now. If that doesn't work, you could also try doing the above but pressing 10, this is the Keystation's factory default for learning.
Hope it works out, man.
Cheers!

OT: Keystation Pro 88 - aftertouch?

Does anyone know if the Keystation Pro 88 has aftertouch? I'm looking at buying an 88 key controller. Thanks.

Does anyone know if the Keystation Pro 88 has
aftertouch? I'm looking at buying an 88 key
controller. Thanks.
The keystation pro does not have aftertouch, and I don't really recommend purchasing it if you are planing to to a lot piano work. The feel is ok, but the velocity respone is terrible. You have to work rather hard to play quiet piano passages. If you are doing more softsynth work than piano, then it might work for you. As for me I'm getting rid of mine ASAP, and going back to a good 'ol yamaha S90ES.
The Knobs and sliders of the Keystation pro are nice, but rather overkill for my work. If budget is a concern, I strongly suggest going to try one out at your local music store if they have them before you purchase one. Also, look into the CME line of controllers. They do have aftertouch, and are only a little bit more money.

Logic pro, Kontakt 2 and keystation pro

When I use an 'instrument bank' in Kontakt 2, I want to controll the different cells (patches) with the buttons B46 to B51 from my M-Audio keystation pro. In Cubase this happens automatically; but what to change in Logic pro to become that result? Now, pressing those buttons in Logic don't change the patches ...
thank you for helping
Dirk

I've forgotten: The recording is ok with FCP

USING GARRITAN JABB WITH LOGIC 8 and KEYSTATION PRO

Anyone out there using Garritan Jazz & Big Band? I can't get any vibrato even though I'm moving the vibrato dial on the screen (this goes for "lite" as well as the regular instruments")
is there some toggle i'm forgetting to use? I do get flutter...
right now pitch bend works, and the mod wheel controls volume.... do i have to assign that wheel or some other dial on my controller to make the other stuff work?

Please check the JABB manual. Although M-Audio's Keystation Pro 88 does not have aftertouch, you can set up any of the Keystation Pro's faders or turn knobs to the CC# that provides the same aftertouch effect. The JABB manual will tell you which CC# to use for aftertouch. (I am away from home and away from my own manual, otherwise I would give you this information.)
Because of all of the CC#'s that are utilized within JABB to help create "real sounding" instruments, I usually do several recordings after the original one for each of the CC#'s that I may use. This includes that "aftertouch" CC# that I've set up on either a fader or turn-knob. This is my work-flow methodology which works well enough for me. Then, I fine-tune the recorded CC#'s information using Hyperdraw.
Without a doubt, this is a labor-intensive process. But with the time and effort put into JABB (and other similar instrumental libraries), comes a more natural-sounding work. At least this is true for my ears, anyway.
Good luck to you!
Ted

Problems with M-Audio Keystation Pro 88

Hello everyone,
I am using a M-Audio keyboard as my controller keyboard in Logic 7.2. I have assigned certain instruments from Logic to differnet zones on the M-Audio. I have done this for four songs hence i have used 4 of the presets on the M-Audio.
What i am experiencing is that some of the faders or knobs have been assigned to certain parameters in Logic. For example the knob B10 controls the pan of the instrument. I thought you had to assign them yourself.
How do i set up my M_audio keyboard so that nothing is assigned to any of the faders, knobs and buttons on the M-Audio.
Cheers

Thanks Jord,
I have been trying this out. So i set up a new preset bank and say label it 'Live', in this preset bank i then set up my preset.
Everytime the M-Audio is turned off and on will i have to load the new preset bank 'Live' using Enigma, or will it be stored in its memory

M-Audio keystation Pro 88 & Leopard?

Contemplating install of OSX to 2nd drive in next week.
Curious if anyone has an M-Audio keyboard working with Leopard? I see their drivers have not been updated yet.

M-audio is own by Digidesign (Protools), which is owned by Avid. You wont get their gear working on Leopard without paying. Every time Apple releases a new cat in the wild Avid/Digi makes you pay. Get used to it or find some other hardware that wont take weeks or even months to update a simple driver for that hardware you are married to. I stopped using Protools but i'm stuck with their hardware. Learn from my mistake & find yourself a hardware company that keep up with Apple updates like Motu. My Power Mac G4's built in audio driver goes to 192 khz. What's up with that Digi? all that money for 92 khz.

Logic Pro 8, Kontakt 2.23 & Memory usage

Hello -
*What type of known memory problems might exist between Logic (Logic 8 in particular) and either Kontakt 2.23 or Kontakt Player 2.23??*
*If there are known memory usage issues, what can be done to help/fix the situation??*
My computer set up is listed below. I have not upgraded to Leopard (but did upgrade to Logic Pro 8). By-in-large, Logic Pro 8 works fine. However, I usually "network" the Logic sequencing projects with Muse Research's Receptor (version B) and/or an aging Dell Precision Workstation 650 using Musiclab's MIDIoverLan CP3. This has proven stable for me. For my most recent project, I decided to see how many instrument plug-ins I can utilize within the Logic Pro 8 program (without benefit of this "network" set-up). For this project, I'm using one instance of MusicLab's RealGuitar and 16 instances of +*Kontakt Player version 2.23*+ for a total of 17 instrumental tracks. The instrument libraries used are Garritan's GPO and JABB. With this many individual (not multi) track instances used, the activity monitor is showing high RAM usage. For some of the instruments, I could not use the KS choices (trumpet, trombone) because the extra RAM caused Logic to crash as I mounted more instruments.
I tried adjusting the DFD. Still, there remained high RAM usage and the occasional crash. For some of the crashes, I either got the endless colored spinning wheel or a message basically stating that there was no memory available for the DFD. I am no expert with the advanced workings of Logic and the DFD associated with the Kontakt plug-ins. But I am surprised that using just 17 instrument tracks with this newer Mac Pro computer (with 5 GBs RAM) is causing problems. Sadly, I am not an expert Apple user to be able to tell whether it's the computer or Logic or Kontakt. I suspect, though, its some kind of issue between Kontakt and Logic.
For my audio, I use MOTU's 2408 MK3. For my midi in-put I use M-Audio's Keystation Pro 88. I do not think either one of these devices are causing the apparent memory problems.
By the way. . . before I purchased my newer MacPro computer, I had a similar instrumental set-up using my aging Dell Precision 650 workstation with 2 GB of RAM using Steinberg's SX 3 program. I used the same GPO and JABB sound libraries. It did "challange" the Dell computer (I had to adjust buffer/latency settings to MOTU's 828 MK2 used with the Dell computer), but the computer didn't crash like what I'm experiencing at present.
I don't mind "networking" my computers together in order to use larger instrumental plug-in tracks. But I would think that given the "power" of my newer MacPro I should be able to handle more than 17 GPO & JABB tracks. Yes? No?
*Given my current computer set-up, how many instrumental tracks (using libraries associated with Kontakt or the Kontakt Player) should I get??*
Thank you in advance.
Ted

Sadly, I can chime in with the same basic problem. Namely, that
Kontakt2 seems to leak ram. I've watched the activity monitor show
an increase in ram allocation to logic if i simply LOOK at a kontakt
instance. Just clicking on the instance causes ram to be allocated, and no matter how much I purge samples, I just can't retrieve that ram. Once 2 gigs are sent to logic, crash.
The only solution I've found is to save & restart before it climbs too high. I can then work for an hour or so until the ram overflows again. This is obviously a major bug, and I agree that Logic doesn't appear to be the culprit.
Have either of you tried K3? I wonder if the problem is more under control there? There's no way Kontakt will bother to fix this bug
in v2.23 with v3 on the shelves. The question is, how do we know that v3 fixes it without buying it? I've heard reports that v3 is even
more bloated than v2.
I've recently done a clean install of leopard on a blank drive, and
i'm patiently waiting until NI updates the installers for K2.
Then, i'll have a clean OS, clean newly installed logic 8, and
a cleanly installed K2. Maybe that will help mitigate, if not solve the problem.
I'm almost sure that Kontakt is the source of the problem, but
I've also been told that Intels have serious flaws in their ram
allocation WITH TIGER.
Some people with G5's have reported having access to 3.5 gigs ram.
Intells can only use 2 gigs with any one app. This was thought to be a problem with Tiger and and Intels. So maybe Leopard will expand the RAM wallet, and then we just have to wait for Kontakt to stop spending so much.

52 ms input latency on X-Fi Elite pro card/Midi controller prob

Hi, I don't know if someone can help me about this but I just bought an M-Audio keystation pro 88 midi controller and I can't get it to work well with my vst instruments(on my x-fi elite pro card). There is a very noticable delay until I hear the notes I'm playing on the keyboard with non-so-demanding VSTIs.
I noticed that with the creative asio driver selected in nuendo, it has a 52ms input latency which I know is too high. I don't know if that's the answer to my problem but if I trust creative, i should be able to have asio latency as low as one millisecond. So that's already a problem midi controller or not.
I'm sure that these problems can be fixed(asio or controller latency)because I'm able to have no noticeable latency at school with the same vsts and outdated computers way slower than mine connected via midi cables which are also supposed to also be slower than the usb cable I use for my controller.
I thank you for your help if you are to reply to this post and I just want to have a decent sound(not soundblaster synth A or B which are about the only ones i'm able to use in real time)for my expensi've 88 notes hammer action midi controller. I will be very grateful of all the help anyone's going to give me.
EDIT: I don't know why my post can be seen double on the forum index
ps.
I think my question is specific enough to post in a new thread because I already searched the forum for my answer and I haven't found it.Message Edited by Goshyouidiot on -06-200707:38 AM

Are they not just recording audio signals there? The strange thing is that not a single software can detect any midi device on my computer, although there is a midi input in the front panel of the audio card. So this is the way i've done it with windows XP. Just installing drivers from the cd, running auto update and everything worked so fine (memorieeees...) and now I'm not able to record midi signals in cubase?or any other software because the creative vista drivers do not support the midi input of the frontpannel (thats what i think)
I just tried a japanese version of the creative software cd which was modified to work under windows vista. I installed everything that came with this software package, but still no luck. When i plug in a Midi to USB interface, it works fine, but not so with the creative front pannel. So i'm going to take a look on the soundcard to get its "hardware id number" so that i can write an email to the creative support. I just can't find any other threads where x-fi elite pro users are able to record midi via the front pannel on vista 64.
I was soooo in love with this soundcard as long as?i used windows xp. It was a perfect solution to combine gaming with music recording (i used different soundcards for both issues before, but it was just not so comfortable than just using one card for both) But then i finally was brave enough to get a windows vista and there it goes -.- nothing but trouble and wasting time and money since then....(new mainboard, new midi interface, tried dozens of different modified drivers to fix the crackling sound issue that come up with nforce mainboards and so on...) If i wouldn't need all of my 4 GB ram,?i would get back to?my good old?windows XP 32 bit version.
Greetings

Keystation PRO 88

Similar Messages

Maybe you are looking for