Logic Pro 9 Cavern kit issue

Hi. I recently downloaded LP9 from the app store. When I try to load the "cavern kit" I get an error message which says: Audio file "DNA W Ht Open m Fr.aif" not found! Any ideas? Thanks!

Have you checked to make sure the file actually exists on your system?
You should find it inside of;
Macintosh HD/Library/Application Support/GarageBand/Instrument Library/Sampler/Sampler Files/Cavern Kit
(Replace Macintosh HD with the name of your System drive if you didn't use the default....)
Note: This file is not located in your User Library but in the System Library found in the Root of your System HD
If it is not there then...
Did you download all additional content via the Logic Pro menu bar...  Logic Pro/Download Additional Content and made sure it all downloaded/installed correctly?
Did you try and remove GarageBand at any time? (That particular file is actually one that is instaled with Garageband.. )

Similar Messages

  • 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 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 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 9 MIDI issues with sustaining notes

    I'm a little new to Logic 9 but please bear with me. I have connected my keyboard via MIDI to USB to my Mac and the computer recognizes it perfectly but when I try to play some software instruments it many times continues to play a certain note even after I depressed it. I am not holding down my sustain pedal yet Logic still continues to play a certain note. It does not seem to be a slow fade out or anything like that but rather it seems to be stuck. It does not seem to be really any given note, since it happened to me on different notes. The only way for me to stop Logic from playing is either to switch instruments of reset the MIDI by going to the control panel at the bottom and clicking repeatedly there on MIDI in.
    Could someone clue me in on what to do to remedy this issue?

    sounds like either logic is not seeing the note off command from the keyboard or the keyboard is not sending it properly. try playing the note that is sticking down and up again and see if the stuck note stops. or take a look at the midi i/o window in the transport at the bottom of the arrange page when you press the note it will show the note and when you let off, it should read off.
    Also you may want to limit some info coming into logic and see if that make a difference. go to, project settings>midi>input filter, and check the aftertouch and polyphonic aftertouch, and maybe system exclusive, so that it is filtered out and see if that helps

  • 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

  • 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

  • Performance issues with Logic Pro 9

    Hi,
    I'm experiencing quite big performance issues with Logic Pro 9:
    bad midi timing and sync, user interface is kinda slowing and less reactive, ...
    Mac Pro 2x2.26 Ghz Quad, 4Gb ram, early 2009, shipped with 10.5.6 now upgraded to 10.5.8
    Should I upgrade to 10.6.2?
    Thanx

    Hi,
    I'm using the same machine ...
    I never get any performance issues
    I bought my mac in March 2009 and I was ben ready to work in less that 3 days without issue...
    so more details about your setup are required to answare!
    4GB ram???
    I suggest to check your ram!!!
    Ram must be compatible with Xeon Nehalem Try specification!
    if you add 1GB of ram from nor clear manufactor.. i suggest to disconnect the addition 1GB RAM
    G

  • Latency issue Logic pro 9.1.3.

    Hey,
    At the same time as upgrading to Logic from Garageband
    I bought a Cakewalk Roland UA25EX ext usb soundcard because i was told
    i'd have latency issues if i used the caps lock keyboard for midi
    or direct input thru the input jack of
    my MacBookPro
    (5,3 Intel Core 2 Duo 2.8 GHz)
    Sometimes i use the caps lock keyboard to sketch in midi ideas and mostly it's ok.
    Other times it's delayed and there's no smile on my face.
    When recording with guitars/303/generators DI thru the soundcard
    I have latency issues that don't seem to be very regular.
    Sometimes it's worse than others.
    I make sure i have nothing else running on the computer,
    just Logic Pro 9.1.3, so it's not like i'm overloading macbrains.
    I have tried all the rebooting, i/o buffer size changing (down to 256), headfones from the mac output/headfones from the soundcard/ etc
    but still no luck.
    I can record with the low latency button on
    and it's kind of better, nearly, but that means i don't get to record with the effects on the channel strip
    that affects the recording/playing quite a lot, as i'm used to recording with effects/guitar amps if i go DI.
    This was the selling point - that i could record DI wthout disturbing Thee Neighbours.
    It seems to have gotten worse recently.
    I wonder if it's been corrupted somehow because it also has been acting funny when i bounce down -
    the play head is set to 1111 and i save - then in the bounce window
    the start position says a silly random number and it takes a few attempts of fiddly changes to get it to stay at 1111...frustration!
    Is there something i can do or is this normal? -
    it seems weird that a Pro app that cost me so much £s wouldn't work in a simple recording/bounce down set up?
    or has anyone else had this problem and fixed it?
    If i wipe Logic and install again would i have to go from my Logic Express and then up to my Logic Pro upgrade/extension again?
    Any pointers would be greatly appreciated.
    Thanks in advance

    Hey Fox,
    Thanks for that info -well umm, yes i installed the correct drivers.
    I use just the AU plugins or the basic logic ones on the channel strip
    but even when i was going in dry there was still a delay.
    I had experimented with the buffer size, as mentioned, but not gone down that low cus
    last time i tried that i had other strange things happen!
    But i will try again.
    Sample rate was at zero, btw. Always says zero.
    But today, when i just opened logic, the sample rate had changed. Strange. I need to understand this side of things so i'm gonna read up.
    Also, if plugins are involved, i installed some novation bass station and some freeware TAL bass synth
    stuff recently but don't have them up when i'm recording.
    Maybe they sit there quietly and interfere just by their facial expressions or sumthing!!
    I booted Mr MBP just now and i pulled out the USB and he's shining me a big ole red optical light
    out of his output jack!!
    In SysPrefs it has only optical digital as an output option.
    In the last few days as i was playing around trying to correct the latency issue i noticed that the output options had changed to the UA25 and the 'digital optical' options - rather than the UA25 and 'line out'.
    I'm off to go and read up on how to get my line out back, and try this buffer thing again.
    Thanks again
    Gravity

  • "Mouse Over" issues in Logic Pro - Mountain Lion

    Hi,
    Since I upgraded to Mountain Lion, I spotted an issue with Logic Pro (Logic 9).
    In the Arrange window, when pointing the mouse at the end of a region, the pointer icon doesn't change to the looping (upper right corner of the region) or resize (lower right corner) icon.
    As a result, those functionalities (looping and resizing regions) are gone.
    Anyone having the same issue?
    Is there a way to solve this or do we need to wait for a Logic Pro update to get these back?
    Thanks in advance,
    A nice day everyone,
    Vince

    Vlvl wrote:
    As it's the only problem I have noticed since the upgrade, and as I mentioned in my last post, looking like a minor problem to me, I will keep Mountain Lion.
    But anyway, thanks for the advice, Ivan.
    Vince
    No problem, as a professional musician using Logic I learned that lesson the hard way first time around. Hard as it was to not have the toys I soon learned that stability ruled the day....

  • Ultrabeat in Logic Pro X is missing drum kits

    Hi,
    So recently, I got Logic Pro X because I've been meaning to try producing house music with it. I was introduced to Ultrabeat in some tutorials saying to click the dropdown menu (at the top) and select 01 drum kits and choose Trance Kit 02. However, when I click the dropdown menu, I seem to only have 8 samples in the drum kit and none of them sound good at all. Why do I have only 8? I've seen other discussions where people have up to 25+, is this something that I can download from the additonal content? And if so, what is it called?
    Many Thanks!
    MChen.

    Try Drum Machine
    ....and also the Logic Studio 2 Compatibility Sounds and Instruments found under the Legacy entry.... along with the GB 11 Sounds and instruments.. and finally the Instruments found under Jam pack 1, Jam Pack Remix and Jam Pack Rhythm,
    Also make sure the Essential Sounds and Instruments set has downloaded completely too...
    Personally, if you have the space, I'd download all the content...  as there is so much on offer for free... that you may find useful in the future.

  • Why do all of the drum kits in Logic Pro X have a delay? All of my drum hits (drum kits only, not drum machine) are behind the beat.

    When I turn on the metronome, it's in sync with EVERYTHING except the drum kits.
    Is anyone else having this problem?
    When I change the plugin on the these tracks to a LPX drum machine or to a 3rd party drum plugin  the problem goes away.

    Is Plug-in Latency Compensation enabled?
    Logic Pro X>Preferences>Audio>General

  • Logic Pro X and Yosemite issues

    It seems I have some very basic issues with Logic Pro X 10.0.7 after upgrading to Yosemite OS on my MacBook Air:
    1. Zooming the main window by swiping two fingers apart or together on the mouse pad does not work anymore.
    2. Adjusting the length of audio regions in the main window does not work anymore. It works as usual on midi tracks, but when I hover the end of an audio region the brackets just do not appear. I have now used automation to silence the bit that I wanted to shorten, but that is more of a hassle.
    I have tried restarting Logic Pro X, restarting the MacBook and looked for any settings that may have been changed, but to no avail.
    Do these issues sound familiar to anyone? Any thought on how to fix?

    1) Zooming
    the zooming with the swipe gesture was always problematic, but it is now only happening in the Audio FIles Editor and to some extend in the Score Editor. All the other windows work fine on my machine.
    2) Resize Tool
    Works fine without a problem in the Main Window and the Editor windows. Of course, you can resize in the Audio FIles Editor.
    Hope that helps
    Edgar Rothermich
    http://DingDingMusic.com/Manuals/
    'I may receive some form of compensation, financial or otherwise, from my recommendation or link.'

  • Logic Pro 9.1.1 AU third-party plug-ins ongoing issue for many

    Where is the Logic development team on this? Nearly all third-party AU plug-ins produce random pops and clicks at the beginning of playback and on occasion randomly during playback but before audio regions in tracks with these plug-ins installed. These pops and clicks are even visible in the track's meter. http://www.gearslutz.com/board/music-computers/482381-logic-3rd-party-plugs-pop- click-nightmare-how-does-rest-world-do.html How many people need to complain? Is Logic Pro considered production software?

    I can't imagine a more textbook and apple-friendly environment than what I have. 32-bit is not the problem. I don't believe logic runs at 64 until you're on os 10.6 and I'm still on 10.5.8. My entire rig is what you'd see in an apple store logic demo. I've tried nearly everything:
    1) All standard optimization tips including but not limited to no date/time updates, no airport/wi-fi, no bluetooth
    2) I have a ultra high-quality external fw drive by G-drive
    3) Standard issue ensemble with updated firmware
    4) Moving AU component files from system library to user library
    If you look at the number of people commenting on the GS thread as well as other forums – the problem is common and needs to be fixed. I'm not the only logic user plagued by this issue:
    http://www.logicprohelp.com/viewtopic.php?t=43306
    http://www.logicprohelp.com/viewtopic.php?t=50030
    I really believe it has something to do with how many third-party plug-ins handle AU's reset or initialize callbacks; somewhere in between. This bug is clearly affecting many users and I'm coming close to starting a petition and devoting some serious time to making a big dorky stink about it on youtube.
    Either the AU spec needs to be updated to clarify some tricks (or hacks) specific to Logic's on-demand DSP usage or the logic team needs to publish a notice to all "Logic" AU developers. Optionally, if Logic had a preference to turn OFF on-demand AU DSP (so that plug-ins are always-on like in every other DAW or...ugh...outboard gear). Logic's on-demand AU DSP handling is outdated considering the processing power available in ANY apple computer made within the last 3 years. My CPU meter in Logic barely even lights up. On-demand DSP is overkill and antiquated and the least Logic can do is provide production or mission-critical users the ability to opt-out if they have the CPU power to do so.
    Having said all that; I hope I'm wrong about something and can come back here to eat my words and feel very embarrassed about my rant. I'm going to keep digging for solutions – hopefully, I'll find out the secret to whatever it is the few of you are doing to keep your third-party AU plugs quiet before an audio region starts.
    Also; Scott at Stillwell Audio has graciously begun trying to track down this very issue and is one of the few DSPers who has taken interest in helping Logic folk.

Maybe you are looking for