Logic presets unavailable

Hello
So recently I was at a 1 to 1 appointment and was expeirementing with the strings presets in logic 9 (staccato, vabrato, etc)
But when I went on my own computer the presets were not available or even located in my files or in logic.
I was wondering if that is a preset or sample pack i must purchase or if it is an update to logic.
Ps. I use the version of logic that was available in March of 2012. I have not updated it

Hi
Did you download all the additional content via the Logic Pro menu?
CCT

Similar Messages

  • Develop presets: "Unavailable Preset"

    When I enable the library filter Develop Presets I see three instances of "Unavailable Preset" with counts of 1, 23, and 323. In detail these are
    (1) no presets at all, just a Clarity adjust. Click on import, then back on the Clarity --> applies correctly. Then when I refer back to the Develop Presets filter the count has changed from one to zero.
    (23) these images all reference a long-used and active preset that is just Clarity + Vibrance. Clicking on the image history shows that the final image is correct, and the before/after preset results are correct. But after cross-checking several images this way the count has now been reduced from 23 to xxxxxxxxxx
    (323) these images all reference a preset created today that I accidentally mis-applied to those images. (I'll refer to the mis-applied preset as GOOFY -- more on this below). Sampling some of these 323 images I see that the GOOFY preset is correctly applied. When I click on the previous history step, then GOOFY the "Unavailable Preset" count is decremented and a new "Custom" preset is incremented. I have never seen "Custom" preset before today.
    Now, the story of the GOOFY preset. When I could find nothing in the documentation, forum or web, I decided to try disabling the unwanted preset by these steps at the Mac OS Finder level:
    - duplicate GOOFY to GOOFY-2
    - delete GOOFY file (I hoped LR3 would remove the references to the deleted GOOFY)
    - in grid view mass-apply GOOFY-2 to the correct images
    - quit, restart LR3
    I've forgotten exactly what happened next, but for sure LR3 did not remove the non-existant preset links. For some reason I decided to rename the duplicated GOOFY-2 back to GOOFY. Now the images that correctly referenced GOOFY have two references to presets named GOOFY the oldest one is a NO-OP (does nothing), the latest one works as expected.
    Any advice would be appreciated:
    ** how to mass-delete an unwanted preset reference from a selection of images?
    ** how to clean up the above "Unavailable Preset" errors?

    When a preset is created, it stores the current level of the chosen parameters at the time of creation; in the example below, the preset which will be named CurrentPreset1 will store the current levels applied to the selected photo at the time the preset was created, and in this case will only store values corresponding to Color, Lens Corrections, and Process version.
    To update the values recorded in a preset, the various levels must be changed on the currently selected photo and then the "Update with current settings" must be selected on the preset to update. The "Update with current settings" therefore updates the preset itself with new values corresponding to the values set in the current photo and has nothing to do with how it was applied to photos in the past. A preset is not related in any way to photos on which it is applied; a preset simply applies the set values recorded in the preset on the selected photo as if these same values would be manually entered for the selected photo.

  • Previous Logic Presets

    I want to recreate a track I made using a previous version of Logic. I used a couple of distinctive presets from the ES2 on, I think, Logic 7, which Im having a hard time replicating. The sounds were not included on recent Logic versions. What is the best way for me to go about getting presets from Logic 7 in my current library?

    When I installed Logic 9 is did a full install so it should be there. My ES2 only goes to 13, no legacy presets. I have just moved house and haven't got my Logic DVD with me at the moment but i will get it on the weekend and do what you said.
    I can't remember the names of the sounds. The one i really need was in the rhythm section. Just haven't been able to replicate it to my satisfaction!

  • Logic Pro unavailable!

    I've tried to download my regularly purchased Logic Pro 9 from the Apple Store.
    Some time has passed since the last time I've used, but now I'd need to get it again.
    The store now says it's unavailable! Weird, less than a year has passed since then.
    I've contacted the support, surprisingly I've been told I could not get what I've paid for!
    Not I'm eligible for a refund nor to get an upgrade to Logic X. Nothing, that's it!
    I've paid 179,99 euros and I've nothing in my hands, thanks a lot Apple!

    Theodore,
    Sign out of the Mac App Store
    Quit the Mac App Store Application
    Quit ALL apps so only Finder is running... including Safari, iTunes, Mail etc...
    Relaunch the Mac App Store application
    Sign In to the Mac App Store again using the Apple ID you used to purchase LP9
    Wait a couple of minutes... (Important!)
    Check that a new 'terms and conditions' window didn't pop up..for you to agree to...
    Go to the Purchases tab and look for the Install/Download Button to the far right of the LP9 entry and click on it...
    Following these steps exactly...  normally fixes this issue.
    Cheers..
    Nigel

  • Printing Presets unavailable?

    There seems to be some presets missing from my print dialogue when in Photoshop.
    In the print dialogue for the printer (that shows up after Photoshop's print dialogue) I expand the dialogue to show the presets. The drop down menu that includes "layout" "paper handling" "cover page" "scheduler" also includes an option "hp deskjet PDE" that is crossed out. Choosing this option produces the following message:
    The bundle "hp deskjet PDE" could not be loaded because it does not contain a version for the current architecture.
    Contact the bundle's creator listed here for the latest version.
    hp deskjet PDE v2.7.1
    As far as I've seen, this only happens in Photoshop. I've tried printing with preview, and iphoto and they both display a full set of presets for this printer.
    The computer I'm working with is new and I just discovered this problem. So it's not a case of "it worked before and it doesn't now."
    I'm a little confused as to where to go from here. Any help is appreciated, thank you!

    Your are running a PPC version of PhotoShop. You need a UB version of the HP Printer driver. Or the other way around. Somehow you did not get the full sent of drivers pre-installed from Apple. Two choices: Upgrade to 10.5.4 and then use the new HP Drivers posted on Apple Software Updates. Or download the UB driver from HP web site.

  • Standardise definition & selection method for ALL third party plugin presets!!!

    Over at LogicProHelp there is a very useful topic relating to Logic presets - in which many users have spent time saving individual third party plugin settings as LOGIC presets... which is enormously helpful when selecting instruments etc because they can be selected using a keystroke etc and found within the Logic Library browser window - which is of course searchable!
    These presets have then been uploaded to the forum for others to download.
    http://www.logicprohelp.com/viewtopic.php?p=367267#367267
    I posted on the topic recently and thought it worth mentioning over here on the Apple forum.
    Here's what I said - does anyone agree/disagree? Is this something that Apple should work on? For me it's a no brainer but I'd like to know what others think....
    "MO 3rd party instruments that rely on mouse-clicks or anything more than one button press to change a preset are incredibly badly designed. It's massively frustrating and impedes creative flow to have to use a mouse, or press several keyboard buttons just to move from one sound to another. Native Instruments interfaces are amongst the worst offenders - you even have to MANUALLY specify what presets you want to use with specific MIDI Program Change messages - because the latter are the only way I know of using anything other than the NI interface to change sounds in their plugins.
    The Logic Channel Strip settings saved along with 3rd party Plugin settings saved as Logic Presets have proved a recent revelation for me.
    Now I can change instrument presets using a keystroke, a midi message, almost anything I want.
    And then there's the Logic Library browser - now that so many sounds are saved as Logic Presets, the Logic browser window has become really powerful - being able to search my entire library for "bass" or a particular instrument name - REGARDLESS of which third party plugin is required to play the sound - IT JUST LOADS AND PLAYS!
    Maybe I'm in the minority but I think of a sound I want first, NOT which instrument I should load and then browse through - the latter is kind of backwards for me.
    I really think that we users should pressure Apple and plugin developers to provide Logic (and indeed other DAWs) presets with ALL of their products because the amount of effort on their part is minimal compared with countless end-users doing this task manually over and over. The current situation is ridiculous.
    DAWs are incredibly powerful these days but the lack of a plugin preset/sound library definition standard is quite crippling to work flow.
    I mean if there were a STANDARD LIBRARY DEFINITION such as with Native Instrument libraries or Apple loops where sounds are defined universally and supplied as such in a common preset it would revolutionise sound discovery/selection within DAWs.
    Kind of like a document management system that applies to ALL plugins, by ALL developers and the installer for a plugin would then add all its presets to the management system/common library"

    Sid Merrett wrote:
    Can you give me an example of a plugin that doesn't work with the Logic save preset function?
    Sure, I could give you lists of plugins for each of those particular scenarios I addressed.
    In that specific case, for one example, Spectrasonics instruments for a few years did not support the hosts' save/recall settings function (at least in Logic), and when contacting them and asking why Stylus RMX could not recall settings saved via Logic's preset system I was given the explanation that it wasn't supported for technical reasons.Basically, it only save/recalled a small handful of settings, the rest were lost, meaning it was impossible for quite some time to use the Logic's save/load settings feature to save user presets, you had to use the plugin's own internal save features. (Yes, the instrument's state was saved in the song, but *wasn't* able to be saved via the preset handling, for technical reasons).
    A year or so later, and later Logic versions, they finally got round to making it work as the varioous parts of the host and instruments were upgraded to handle larger data requirements. Spectrasonics instruments are examples of instruments with very specific, custom browser features, many of which you lose if you save data using Logic's functionality - not to mention the effort of saving, naming and organising 8000+ patches per instrument. Plus you have many levels of data - you often load a loop into a part, and a part into a group of parts, and they are different types of data. The hosts save/load feature only saves the state of the plugin - it can't be used to load Loop 14 into part 2, for example. It's the whole plugin, or nothing. More workarounds in terms of how you organise your loading/saving of different types of data.
    There are other instruments too, and ones I've beta tested where I've got into the technical details and had to have the preset format changed or simplified because hosts had difficulties storing the data correctly. It's quite a complex thing, in the main, and different instruments implentation of preset handling mean that the whole thing is full of workarounds, compromises, or plain failure to use the feature completely.
    Other instruments, such as Minimonsta, lose functionality when saving via the host - for example, you only get the meta patches and patch morphing functions when saving via the plugin's own file format, and that stuff doesn't happen when saving via the host.
    I could go on and on about this - every develop has different requirements and they mostly all either do it very basically and rely on the host, or bypass the hosts save/load functionality and implement their own which they can be in control of and that will work across hosts and across platforms. For instance, there is little point having a beautifully organised Oddity library if all those sounds are now unavailable to me if I choose to work in Live...
    That's why the whole preset thing is a complicated mess and isn't liable to be sorted soon.
    There is a developer over on the PC trying to make a system to unify this stuff between plugins - it's PC only right now, and I forget the details this second, but it's acknowledgement that people recognise this whole thing is a mess and looking at ways to improve the situation.
    Sid Merrett wrote:
    I hadn't spotted that - thanks. You can't use the Logic Library window to search for Plugin Settings, only Channel Strip Settings.
    You *can* use it to search for plugin presets, but only within the context of a single plugin. Ie, if I select the ES2, I can see, and search, the ES2 plugin settings. But often I want "a bass sound", I don't necessarily know that I was an "ES2 bass sound", or a "Minimonsta bass sound" or whatever.
    The point being, I just want a sound that will work, and I don't know where it will come from. Forcing me to choose and instrument first can be counter productive. How many times have you needed a sound, and you go "Ok, there might be something in pluginX that'll work?" - you load up pluginX, flip through the sounds, don't find anything useful, then go "Ok, let's try pluginY", no... pluginZ etc etc
    I miss Soundiver in many ways. *Ideally*, I'd like one central method of storing my presets which will work cross-plugin, cross-host, cross-format and cross-platform that is a standard that all developers and hosts support, and that offers the main core features that developers need, from simple, single patches with names, up to full meta data, cataloging, organising, author and notes tagging and so on. You can still give the users a choice to use the individual plugin and individual plugin's gui for patch selection, but you can get far more standardised if you want, with the advantages that gives - and you don't have to export patches into the system, as it's developer supported, all presets for your instruments would be instantly available in the library, just as they are in the instrument directly.
    But it's difficult to get developers to agree on much, these days - the most likely thing to happen is someone somewhere creates a cross-platform standard for this that gains momentum and that developers and hosts want, or *need* to support.

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

  • Third party presets for battery 3 migrate to battery 4

    I own battery 3 and logic 9 and Made presets of kits all for my BATTERY 3 in logic so theyre right there in my lib in Logic 9 .... Now i got into this battery 4 as well as LOGIC X..... all i want to do it make my battery 3 logic presets work for battery 4 .... I found the B3 presets and put them in a folder that seemed to have battery 4 see the presets but when i UPLOADED the battery 3 presets in battery 4 . The battery 4 would crash the program everytime when trying to load a B3 third-party preset in B4..... is there any converting i neeed to do the files from b3-b4 does anyone know anyway or even if its compatible to do such things... again incase i am unclear.... I want Battery3 third party presets that i made in logic 9 to now work and be accesed on logic X and battery 4....i know this is not a battery forum or native instruments forum... so for the people who want to help by saying oh i logic not battery.... atleast tell me where the third party presets folder "path" would be for Battery 4  when making presets in logic x ..... soo please let me rock out with this logic x and use my presets that i spent dys n days making.... as it is i cnt use jalf my plug ins with this 64 bit deal.... ATLEAST  someone help me to get my battery 4 to open the same ish as my battery 4 ...Again please some help here... 

    Anand,
    regarding the third-party tools:
    SAP-AutoCAD Integration is developed by the SAP development partner CIDEON.
    CIDEON also provides a direct integration for Microstation.
    Please find here all needed information:
    Overview: http://www.cideon.de/cideon/en/so/produkte/sap_cad_integration/index.php
    AutoCAD: http://www.cideon.de/cideon/en/so/produkte/sap_cad_integration/cadintegr/index.php
    Microstation: http://www.cideon.de/cideon/en/so/produkte/sap_cad_integration/microstationintegr/index.php
    If you have further questions, please don't hesitate to contact me directly.

  • Importing .pst files into Logic

    I have downloaded ES2 presets that are mostly .pst files. I was wondering how do I get them into Logic and more specifically the ES2 menu? When I click on them I get the 'ol "There is no default application to open the specified document..." I also tried dragging files into ES2 library and drop down menu. What's next?

    Hi
    Logic presets and Channel Strips can 'live' in 2 places:
    Either:
    Library:Application Support:Logic:Plug-In Settings
    Library:Application Support:Logic:Channel Strip Settings
    Or
    <User>:Library:Application Support:Logic:Plug-In Settings
    <User>:Library:Application Support:Logic:Channel Strip Settings
    Note that there are sub-folders inside each!.
    HTH
    CCT

  • ES1 & ES2 presets missing?

    Is it just me or have they removed the drums category on both the ES1 & ES2? The analog drum kit I seem not to be able to find.

    if you need preset from Logic 7 or previous versions you can find it on ald installation CDs...
    I have all Logic presets... including SpeceDesigner Ir that comes with Logic
    Platinum 6!
    Many presets has been changed but all of the old presets are compatible with LP8
    ... I'm busy for recording session in those days, but if need I can put some of the old patches on my web site ftp server on free time.
    just email me.
    fermusic

  • Loading Channel Presets

    I need to load presets for individual channels. The presets are saved on my drive, but I cannot navigate to the presets when I click on the channel settings button, I only get the default Logic presets and folders, nowhere do I see an option to load from disk.
    Any ideas?
    -p

    Logic loads channel strip presets from the Library Channel Strips folder, and your own Channel Strips from the User Library Channel Strips folder.
    So you need to copy your Channel Strips to:
    /Users/you/Library/Application Support/Logic/Channel Strip Settings/
    ...to the appropriate instrument, track, output etc subfolder depending on where the channel strip settings should show up.

  • Upgrading from Emagic Logic 5?

    Hey there,
    I recently moved from Windows to Mac, and therefore my old Logic Xskey suddenly looks very interesting again. Since Logic was unavailable to me for quite some time I moved to Cubase, but I never really liked it. Now I am on a Mac I tried to figure out how I can upgrade my old Logic 5 Gold license, but I can only see that there is an upgrade path from Logic Audio 5 to Logic Express, not to Pro or Studio. Is there a direct upgrade path as well, or do I have to get Express first and then move on from there?
    Regards
    Thomas

    I'm not sure where on the site they say this, but I do know that this is exactly what I did. I upgraded from Logic Audio 6 to Logic Express 7, skipping Express 6, using the upgrade package.
    When you buy the upgrade, you get the DVD with Logic Express 7, and after you install it, you need your XSKey to authorize it the first time. Then you put in the serial number that comes with it, and you're off, never to need your XSKey again, unless you want to use the EXS24 editor in Logic 6.
    Don't worry -- it will work.

  • Logic 8 with I/O on aux, blips/bleeps/chirps - Help? Please?

    Hi Guys,
    I realize now and after performing some more diagnostics last night how to further narrow down my issue.
    First of all, here is my Setup:G5 Quad 2.6ghz (I think), 6G RAM, 3 HD's (one is empty), a 4th external for time machine.
    MOTU 828 MK2 firewire (all 8 analog I/O loaded with something - compressor, filter, EQ, 2 pedals). The firewire had to convert from 400 to 800 at the G5 because they no longer ship with FW400. Midi controller is an Evolution Mk449C (again, I think, I'm away from comp.)
    Here's my issue:
    1) I'll start off with a multi-out Utrabeat or what-have-you.
    2) Then I'll put the Kick, snare and HH, to their own Aux channels, and assign the UB outs accordingly.
    3) Then I'll use the I/O plugin on say the snare, and set the input/output appropriately.
    * Everything works fine - The snare, for example, makes no weird chirping/blipping sounds.
    4) HOWEVER when I add any other track after this, the channel with the I/O goes blippy/chirppy . . . added to this, the timing on the snare goes WAY out of wack. This also occurs when I run the outputs of several channels to an Aux, and set an I/O on that Aux channel. From what I can tell it only happens with Aux channels, and happens with any of the outboard gear I use..
    What I have tried so far:
    - Resetting the MOTU with the FW cable unplug. ( There's a way you can do this.)
    - Moving the logic preferences files to my desktop.
    - Increasing my buffer size to 1024 - this works to get rid of the the bleepy sound, however the time delay on the snare is still totally screwed.
    - I have also tried using a logic preset template, and it still does this. ARghhh!!!!
    * My computer at home is without internet, so I will also try to DL the MOTU updater at work and burn to a disc on the weekend.
    - Anothe odd point is that this has only been happening as of a week or so ago . . .
    Could someone PLEASE help me shed some light on this?
    I am not sure if it's Logic, my MOTU or my comp? I do think it's weird that such a string computer could have this sort of trouble???
    Thank you in advance,
    Tyler.

    I should also point out:
    Two things that only serve as small fixes.
    1) I can jack my I/O buffer size to 1024, that gets rid of the sound, but the midi response is terrible afterwards.
    2) I can bounce out the midi as audio however I've just spent $4000 on my new G5 to avoid having to do this. See first post. Apart from this it makes the signal uneditable later on.
    Of course, this has only just started happening these past couple weeks. If I purchase Logic 9, would this fix my problem? Also - I'm not 100% but my suspicion is the problem lies in Logic, not my Motu828. I've reinstalled the MOTU software, and reset the inteface. I suppose I should also point out that working with auc channels like this has always been a huge part of my work flow, so again I find it odd that it's just started to get like this.
    Again, here is the scoop -I'll start with any multi-out pluign (UB, EXS24, etc), and then assign sounds to discrete aux channels. I'll set the input of the aux channels to correspond with the appropriate source.
    Now I'll use an I/O plugin to to get an analog filter (for example), on my snare. EVERYTHING is fine until . . . . I make a new instrument track. The aux channel that the I/O on it sounds like a burst of PCM noise. Very digital, almost like it's been pitched WAY up.
    Guys I'm not trying to be a pain here, that's the last thing I want, but this has been killing me for the past couple of weeks. So could someone PLEASE help me out?
    Thank you!
    Tyler.

  • Finding good plugin settings

    After purchasing Logic Pro, I was surprised the setting choices that came with plugins (EQ, Space Designer, etc...) were not very realistic. A Piano in a Space Designer "Piano Concert Hall" sounds more like it's in outer space. The EQ setting for piano also sounds muffled and unrealistic. I've been able to play around with the settings to make them more realistic, but I was wondering if there is a forum somewhere where people post their plugin settings. It would be nice to share in all the hard work it takes to fine-tune these settings.
    Anyone know what I'm talking about?

    We have never sent an email to any of our registered members unless contacted first by the member. No spam here.
    I did take the time to visit the spamgourmet site and have to say it really sounds like a great idea!
    But anyway yes, we welcome all of your Logic presets: plug-ins, channel strips, Environments or song templates... and we already have about 40 of those files posted by members. I'd actually like to hear your enhanced piano sound preset.
    David.
    G5 Dual 1.8GHz - Logic Pro 7.1   Mac OS X (10.3.5)  

  • The ever popular newbie EQ issue

    Hi all... as an experienced musician who's been dabbling in the DAW world for about a year I thought I'd share my EQ learning experience with my fellow newbies (pros, feel free to laugh! I can take it.)
    Anyway, I spent many months rendering my brilliant noodlings into absolute mud through complete lack of knowledge of what all them knobs and waves meant But now I;m now getting tracks that to my ears (and people other than my mom) sounds pretty good -- sounds the way I want it -- and getting mixes that sound fairly clear, at least not totally chaotic and muddy.
    As Bee Jay pointed out earlier, there is no "right" set of EQ settings that will work for every song (unless you can afford the Awesomizer!). But there's general frequency bands in which instruments (and I'm thinking of basic rock and roll instrumentation, eg Zeppelin, Sabbath, loud English-American blues) live the best, those are the bands where to begin EQing the signal.
    "The Mixing Engineer's Handbook" breaks out this info pretty well, I think. It also includes helpful interviews with a lot of well-known pros, and describes how they build their mixes. The book also describes places to cut and boost for each instrument that tend to have worked in the past -- and explains why those tried and true methods work. it helps one understand why the Logic presets are the way they are. I'll use those bands as a starting point, then tweak from there, depending on the composition.
    As for doing the actual EQing, I can't praise PSP Audio's MasterQ highly enough. It's a parametric EQ with a great interface (knobs for freg/Q/gain) and a nice big graphical display. What I will do, when EQing kick/snare/bass is have each channel's MasterQ instance simultaneously on my screen to ensure they're not crowding each other out. (Also highly recommend PSP's MixPressor and Vintage Warmer, and their Neon Linear Phase EQ!)
    So it's not totally mysterious... you just have to arm yourself with a bit of theory and get a EQ that functions and communicates in a way that's good for you. And futzing around, a lot.

    I find the best tool in this respect is the analyser, plus your ears of course.
    My latest remixes on Peter Gabriel"s Real World Website:
    http://www.realworldremixed.com/remixer.php?remixer_id=oqkx--xChQR1ZrHX8kI.

Maybe you are looking for

  • How do i copy a dia show on cd?

    how do i copy a dia show on cd?

  • ACH register

    Frnds I am trying to pull up some inforamation related to payements we made. As when we pay by check, we can look up all the details related to check in check register (fchn), we can see vendor, payment amount, and lot of things at line item level. B

  • Drill Down Report - On Drill Click, Tablix Expands to right.

    Hi All          I created an RDL File(Drill Down) in SSRS and consumed the same in aspx page, changing its extension to rdlc. Drill Down is working well in local. But When it is hosted in server, On drill Click tablix expands to right.  Awaiting for

  • HT1923 An update to i tunes on my Windows 7 computer caused i tunes to no longer open.

    I have searched the web for solutions, including this site.  I have followed all the uninstalling and reinstalling 3 different times, each time rebooting between uninstalling and reinstalling.  Still will not open.  Started out as MSVCR80.dll issue. 

  • XML serialization vs. normal serialization

    Hey all, Great to see the forums in use! :) One thing I've never been quite clear on -- when does it make sense to use Coherence's XML serialization vs normal object serialization? Any tips would be appreciated. Thanks, Matt