Logic Pro Midi Kontakt Issue...

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

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

Similar Messages

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

  • Logic Pro Midi Keyboard Randomly Stops

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

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

  • Problem with working: logic pro x & kontakt 5

    My logic pro x bounces o.k (with the mini mac that i use), but it can not bounce well when i creat a project that uses the kontakt 5 instruments
    why?
    thanks

    Hi
    You can check the version numbers various ways:
    Open Logic Pro X:Preferences:Audio Units Manager:  This lists all AU plugins and their versions
    Open Kontakt, click the NI logo top right: the version is displayed top left of the splash screen
    CCT

  • Macbook 1,83 Quatafire 610 Logic Pro Midi Problem

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

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

  • Logic Pro 9 - Sustain Issue

    Hey people,
    I wondered if any of you could shed some light on an issue I am having in Logic Pro 9.
    I am using the EVP88 plug-in and the problem I am having is that continuously played notes / chords are cancelled out whilst the sustain pedal is pressed down.  What I mean is; some notes are received and some are not.  Does anyone know if the EVP88 plug-in has limitations in this area? Or whether it is a problem with my setup?
    Thanks
    Dubitup.

    You mean, you a play note while pressing sustain and play the same note again and the result is a thud or an unexpectedly loud note? That's what a Rhodes does, too. Since the EVP88 is model-based, re-striking a sounding note can result in cancellation or overly loud notes. If you think Rhodes, in the case of cancellation the tine is moving towards the hammer and the hammer strike cancels the tine's inertia. If the tine moves away from the hammer, the strike accelerates the tine, leading to a bigger  amplitude. Sample based electric pianos don't do that. But the evp88 does.
    Best,
    DaCaptain

  • Logic pro 8 score issues

    Logic pro 8 is not accurately converting midi notes to the score.  If I hold down one piano key while recording and intermittantly hit another key, only the "another" key shows up on the score from the time I hit it,  though it exists in the piano roll.  Anyone else experience this?  Don't want to upgrade to 9 in the middle of a large project. 

    Hi
    1st: No need to upgrade to Logic 9 to fix this. Logic has worked this way forever.
    2nd: To get the notation to look right you have 2 choices
    a) In the Score Inspector, turn off the 'No Overlap' function. (This will display all the notes but probably with an ugly set of tied notes)
    b) Choose a Polyphonic Staff Style (eg Piano 1+2/3) and assign the notes to different voices within the Style. This can be done by changing the MIDI channel of the notes belonging to the second voice (Voice Separation Tool, Event list, key commands etc etc etc.)
    More info in the manual :-)
    CCT

  • Logic Pro X Fades Issue?

    Trying my first pre-mastering attempt in Logic Pro X. I decided the best way to work was to create "Alternative" mixes for each track on the album totalllying 13, ordering each song as a region. So I went track by track and did my processing and added my in and out fades. Saved each time I switched alternatives to work on the next song.
    On return, I opened each alternative and started boucing out. Check the bounced Wavs and three or four tracks had a weird "ghost" of material from other regions  in the session. Reopened the Logic session to find that where my fades were, a little nugget of sound was playing from another region in the session.,
    Simply altering the fades in any way took care of the problem, but it's not the most elegant solution with an anxious client (eager to hear your awesome masters) next to you and the Discmaker's upload page on the other computer;)
    Anyone run into this yet?

    May I have your attention, Apple Logic Pro X developers/programmers:
    Please explain if this is a bug, or if there is a setting I´ve missed somewhere? I have now Googled and checked every possible function in Logic, to no avail. I´ll blow some dust off my Logic 9 box in the meantime.
    Note: Logic's Dev are not here.. This is a user community mainly 'staffed' by other users like yourself...
    Why doesn't Apple answer the questions that we ask about Logic Pro?
    Additional: I cannot reproduce this issue here.. under 10.10.2 and LPX 10.1  I tested on both my testbed Macs and on both of them... Single clicking on the ruler moves the Playhead as normal.
    Make sure you are single clicking below the numbers in the ruler....
    Failing that.....
    Delete both the main Logic prefs and the CS prefs....using these instructions. Please do exactly what they say in the same order.
    Delete the user preferences
    You can resolve many issues by restoring Logic Pro X back to its original settings. This will not impact your media files. To reset your Logic Pro X user preference settings to their original state, do the following:
    Quit Logic Pro
    In the Finder, choose Go to Folder from the Go menu.
    Type ~/Library/Preferences in the "Go to the folder" field.
    Press the Go button.
    Remove the com.apple.logic10.plist file from the Preferences folder. Note that if you have programmed any custom key commands, this will reset them to the defaults. You may wish to export your custom key command as a preset before performing this step. See the Logic Pro X User Manual for details on how to do this. If you are having trouble with a control surface in Logic Pro X, then you may also wish to delete the com.apple.logic.pro.cs file from the preferences folder.
    If you have upgraded from an earlier version of Logic Pro, you should also remove ~/Library/Preferences/Logic/com.apple.logic.pro.
    Restart the computer.
    Note. If you cannot find any of these files you didn't follow the instructions exactly as written

  • Logic pro 9 Instrument issues/ weird sound occurring!!

    Hi guys,
    I need some help here, I think I have a big issues here with my logic instruments. I just installed Logic pro 9 about a week ago, it's working fine until...
    today when I load some of the Logic instruments (such as EFM 1 Synth, ES2, ES2 syth, or any other sytnh) from the library, there're some kind of strange/weird sound, kind of growling synth sound going on (weeeewww gurrrrrrrrt!), the volume level is also peaking out because of it. I still could play the instruments, but the weird growling sound doesn't stop, & the volume peak out even more!. the only logic instruments that works fine are Evb3 tonewheel organ, Utrabeat & Ev88 Electric piano.
    Same things happen with most of my ESX24 instruments ( such as pop horns, guitar, orchestral, etc) weird growling sound (wew grrrrt).
    Does anyone know what's happening???
    Thank you

    Hi Eriksimon,
    Yes, indeed the noise stop when I bypass the instrument.
    Yes the noise seems to have a steady defined pitch & the character of the noise is the same as the affected instruments.
    No I haven't try to load different presets at that time (it freaks me out already!)
    No I don't think I've made any tweaks/ adaptation to the environment (could you give me example?).
    *But Just now, at this moment, I just try to open & run my Logic 9 again & load the problematic instruments, The Noise's gone, I tried every instrument that has that noise problem (try different presets now) , it works fine, the noise gone (it surprise me). BUT STILL I'm afraid that this noise will occur again.
    Do you have any idea ?,
    Thank you

  • Logic Pro midi start/stop remote

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

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

  • Macbook Pro Mid 2012: Issues with Yosemite update, graphics, and hard drive.

    MacBook Pro (15-inch, Mid 2012)
    Processor: 2.3 GHz Intel Core i7
    Memory: 4 GB 1600 MHz DDR3
    Graphics: Intel HD Graphics 4000 1024 MB
    I've used 192.8 GB
    Operating System: 10.10.1 (14B25) YOSEMITE UPDATE
    I've been experiencing problems with my Macbook Pro shortly after the two year mark of when I've purchased it. There are a few things that are going on. I recently verified my Macintosh HD disk through disk utility and it stated in red that there was an incorrect number of file hard links & then error: This disk needs to be repaired and to restart and then press "R". However, everything before that seemed to have passed. I have everything backed up on an external hard drive and use the time machine frequently. Another thing that has been happening, usually when I'm opening one my adobe programs, is that my screen will go white for a minute along with unidentifiable pink glitchy shapes that don't move. My computer has not been running like it used to and is running slow, freezing, and periodically going white --- as I just mentioned before. I just know that something isn't it right. I've been having to restart my computer by manually pressing the power button more than I've ever had over the past two years. I always work on my computer on a hard surface in a cool area & my fans seem to behaving okay. I also recently installed the Yosemite update for the mac sometime during this past November too and noticed slower running speed, more freezing, and longer times to boot up afterwards. Please speak up if you're experiencing problems with your 2012 Macbook pro too and especially after downloading the Yosemite upgrade. I don't see how it's in any way acceptable that I should have to deal with issues pertaining to my graphics card. Sorry for this post being a little all over the place.

    Hello brousch,
    Thanks for using Apple Support Communities.
    From your post I see that your Mac is spontaneously restarting whenever you see a certain animation on your screen.  This indicates your Mac is getting a kernel panic caused by that animation.  If you'd like to learn more about kernel panics, including how to troublshoot them, please take a look at the information in the link below.
    OS X: When your computer spontaneously restarts or displays "Your computer restarted because of a problem." - Apple Support
    Have a great weekend,
    Alex H.

  • Logic Pro: Midi note key command

    Hi all.
    Does anyone know if there is a key command that allows you to set the length of a midi note in the piano roll? The example in particular I am looking for is if your chord takes up exactly one bar...yet one or two notes within the chord are slightly over (as a result of them being played in not programmed in), is there a key command that will automatically shorten said notes to one bar. At the moment I resort to cutting them or manually shortening them. I was just wondering if a short cut exists?
    D

    Result!
    This works perfectly...Thank you so much for that info!
    All the best
    D

  • Logic Pro 9 lags on Lion, even in 64-bit

    I recently upgraded to Lion because of my side-activities as an aspiring iOS developer (no iOS5.1 SDK on Snow Leopard).
    Since then, I noticed that Logic Pro MIDI reactiveness has hit the bottom: hitting a key on my keyboard doesn't take effect as soon as expected, making it impossible to play live.
    I went to Logic and Reason and made them run in 64-bit mode, this kinda improved the situation but it still is non playable.
    Has anyone some idea of how I could make Logic Pro fly like... one week ago, in 32-bit mode on Snow Leopard?
    For info, my sound card is an M-Audio Fast-Track Ultra, and I use a CME UF8 USB as a master keyboard, as well as an Akai MPD-26 controller.

    Hi
    What audio I/O buffer are you using?
    (Preferences:Audio:Devices)
    CCT

  • Mainstage always crashes before even start after I upgraded to OSX Mountain Lion. Doesn't matter if I use 32bit or 64bit mode. What to do? I bought Logic Studio 9 as a hard box at a retail store (including Logic Pro 9, Mainstage, Soundtrack Pro, Compresso

    Mainstage always crashes after I upgraded to OSX Mountain Lion. Doesn't matter if I choose 32bit or 64bit mode. I sent all the error reports to Apple but no help from there. I heard rumours that Mountain Lion creates the problem. With Lion I had no problem. Logic Pro runs without issues. So what can I do now? Do I have to reinstall Logic Studio and then download all the updates again? Hopefully not.. Any advice? Thanks to all! Ben

    Try delete the mainstage preferences
    from USER/library/preferences   com.apple.mainstage.plist
    even if you are running mainstage 2.1.3 and not 2.2.2  it should work with mountain lion

  • Logic Pro slower on 2011 MBP than 2008 MacBook? Especially with NI Kontakt

    Hi I just got a new MacBook Pro, late 2011 model, and I was really stoked but I've come to find Logic Pro runs slower in general than on my old MacBook (not pro, mid-2008 model).  I know the MBP is a faster computer but I can't figure out why Logic is so slow and I was wondering if you guys could help me out with some optimization or answers.  The main issue lies in Kontakt, which I was able to run far more instances of on my old macbook than my new MBP.  I frequently get system overload despite having more cores on the CPU and the same memory.
    Below are the differences:
    2011 MBP (stock)    
    Logic Pro 9.1.6 64-bit
    NI Kontakt 5 (4-8 instances)
    NI Pro-53 (2-3 instances) through 32-bit AU bridge
    NI Massive through 32-bit AU bridge
    2008 MB (stock, except 4GB memory upgrade)
    Logic Pro 9.1.0 (32-bit)
    NI Kontakt 4 (8+ instances no problem)
    NI Massive (2-6) instances

    I'd also add that when running large native instrument sample libraries, they advise (in the start up guide) to install large sample libraries on a dedicated hard drive. If you have a FireWire 400/800 drive, it might be worth it to install kontakts huge library on there and see if that frees up some CPU. Trying to run logic / the plugin applications, the sample libraries and your recorded audio/logic files on one drive will severely hurt your CPU performance.
    I know is doesn't really answer why you'd be faster/more stable on your old Mac, but might help you get the most out of your new machine.
    Cheers!

Maybe you are looking for