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!

Similar Messages

Importing Previous Logic Projects

Is it possible to import previous Logic projects in to Logic X?
I have lots of 7.3 projects that I would like to re-visit and wondered if it's possible.
Thank you.
D

Hi
Provided that the project was made (or has been opened in LP7.2(ish) if it was made with an even earlier version) it should open fine.
CCT

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

Do I need to uninstall previous version of Logic Pro before I install Logic Pro X?

Basically what it says above!?

You don't need to delete the previous Logic Pro version before installing Logic Pro X. Logic Pro X is a new version and won't replace the old Logic Pro version, so if you like Logic Pro X and that's what you need after testing it, remove the old Logic Pro

Logic Pro 9 Says Not For ReSale On Title Window

Everytime i open logic pro 9 it always say not for resale on title windows I put the right serial key in. I purchased it from the Apple Store. Please help its annoying.

divyesh.tailor1 wrote:
I meant its a proper logic pro 9 cd bought from the shop.
Yes, but you had a pirated version before the legit (proper) one you purchased correct?
The App store version does not require or ask for a serial number unless you've had a another version of the program installed.
The App store version is reading the preferences/install files of the previous version, even though you may have deleted the previous Logic application the preference/install files are still there.
Delete the User Preferences
You can resolve many issues by restoring Logic Pro back to its original settings. This will not impact your song files. To reset your Logic Pro user preference settings to their original state, do the following:
In the Finder, choose Go > Go to Folder from the menu.
Type ~/Library/Preferences in the "Go to the folder" field.
Press the Go button.
Remove the com.apple.logic.pro.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 User Manual for details on how to do this. If you are having trouble with a control surface in Logic Pro, then you may also wish to delete the com.apple.logic.pro.cs file from the preferences folder.
If you have upgraded from Logic Pro 7, you may also need to remove ~/Library/Preferences/Logic/com.apple.logic.pro
You may also want to go into Root/Library/Preferences and delete the.. com.apple.RegLogicStudio.plist

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

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?

What is wrong with logics timing and playback and midi

hi all,
i recently bought logic x and there seems to be a lot of problems im having. first off i noticed that when i am editing whilst looping what im working on it doesn't allways register my changes untill i stop and play again. this is especially true when making fades. it makes it very awkward to make changes in realtime and slows me down a lot. is this a new feature of logic lol or is this a problem with previous logics aswell. is anyone else having this problem and does anyone know if apple are working to fix this? its not my computer as its hi spec 12 core. running 10.8.5.
next problem im having is nothing short of insane. i have my mbase 11 being triggered by midi in logic and playing through an audio channel in logic from my apogee duet. this works fine but only when audio track is selected which is annoying. trouble im having though is when i select another track it seems the midi for the mbase is doing something to the selected track. either triggering extra notes or delaying and playing extra notes. im not sure but it is mental and it means i have to open up the fx i want to edit and then deselect the track. anyone have any ideas if this is something i can fix or if apple know ect?
thanks for reading, any help would be most appreciated
Rhys

Fades can't be edited in real time, Logic creates a fade file after you edited the region, then you press start and voila, it's always been like that.

Multiple panels per logical page

I am working on a customer statement report. It has one logical page with three panels(physical pages). The records on third panel will expand to the next logical page at runtime. I thought it could continue to show on the first panel of the next logical page, but they are showed on the third panel which is at the same level of the previous logical page. The first and second panels of the second logical page are blank. How can I remove the blank pages and move the continuing records start from the first panel of the next logical page.
Your help will be highly appreciated.
It is urgent, please help!

Hi there Otto... If I understand you correctly, you might need to look into the LEAD function.
Here's an example:
with table1 as
(SELECT ROWNUM rn, 'Line ' || ROWNUM text
FROM all_objects
WHERE ROWNUM <= 10)
SELECT *
FROM (SELECT rn, text AS text_col1,
LEAD (text, 1) OVER (ORDER BY rn) AS text_col2,
LEAD (text, 2) OVER (ORDER BY rn) AS text_col3
FROM table1)
WHERE MOD (rn, 3) = 1
outputs
RN,TEXT_COL1,TEXT_COL2,TEXT_COL3
1,Line 1,Line 2,Line 3
4,Line 4,Line 5,Line 6
7,Line 7,Line 8,Line 9
10,Line 10
Cheers,
Vidar

Disk is too slow or system overload error with Logic 9.1.4

I have am running Logic 9.1.4 on a MacPro 2 X 2.8 Ghz (Intel) with 8GB of RAM running OS X 10.6.7.
I recently updated to Logic 9.1.4 and was trying to record one track of vocals on a session on which I had previously worked on a few weeks earlier with no issues.
But today I got this error over and over again:
Disk is too slow or System Overload.
Occasionally I would get the message below with the error, but not always:
The Sudden Motion Sensor may have parked the hard drive head, or the disk performance is not sufficient to read or write all audio tracks, or the system was not able to process all data in time.
I don't have a lap top and tried a few fixes found here (buffer size increase ,rebooting etc.). Again, I recorded several tracks of vocals on other days with absolutely no problems. But today couldn't record more than a few seconds at a time without getting this error. The only difference I can think of is that I updated to the latest version of Logic 9 (9.1.4) rather than whatever the previous Logic 9 version was.
Any help at all would be greatly appreciated.

ISSUE RESOLVED!
So after messing around with this for over 4 hours today, I think I have resolved the issue.
The issue seems to have been primarily with my main vocal track, which was frozen while I was recording a harmony vocal. The main vocal track was actually made up of about 20-30 take folders which I had swiped to make one good take. I was hoping to take a good hard listen at my swipes during mixing once all recording was done, so I had never merged into one audio track. Besides, like I said, this track was frozen so I figured it was already playing back as though it was one audio file.
So I just merged all the takes in this track into one file. Counterintuitively, unfreezing about 10 tracks also seemed to improve performance in the meters. Which makes me wonder whether I should use freezing at all? Both these things together seem to have made all the difference.
In the process, I also learned how to run Logic 9 in 64-bit mode, although this (at least by itself) didn't seem to make any difference other than making AmpliTube inoperable.
So the lesson here: don't have too many take folders going at once. And freezing tracks with take folders doesn't seem to come close to being the same thing as playing back one single merged audio file.

Deletion of logical system

hi friends ,
i created a logical system long back and i have sent idocs succesfully from crm system to Tibco System , recently i have deleted this logical system and i created a new logical system , now the problem is if i trigger an idoc , two idocs are getting generated one with previous logical system and another with new logical system , but the previous logical system is not visible in SALE OR BD54 can u please suggest me how it is getting trigered or i need to delete it at some other tcode please suggest
please help me it is very urgent
with Regards
abaper

hi dilip ,
thanks for your reply ,
actually i deleted the old logical system because it is assigned to a client , and added a new one with out assigning to the client and i have changed in we20 also , and its working fine but the thing is that it triggering two idocs one for the new logical system with status 03 and with 0ld with status 29 or 37 with standard message type CRM_XIF_PARTNER_SAVE AND WITH OLD LOGICAL SYSTEM so please suggest me how can i restrict the older one , and i am unable to know where the system is picking the older logical system even thought i have deleted in SALE
PLEASE REVERT ME YOUR SUGGESTIONS
THANKS,
SRINIVAS

Trying to use flex pitch with logic pro 9 session in 192k crashes program

i try to use flex pitch with a previous logic 9 session and and soon as i switch to flex pitch it just crashes no matter what session i bring up in 192k, i dont have any 96k files to test but is flex pitch non-caompatible with 192k sessions

JofishSamuel wrote:
Okay? Sorry, I have no experience with .mid files as I've never exported or imported them or moved them before... or even highlighted one before!
Two ideas, have your friend check and make sure the mid file plays on his/her system.
and/or
If the mid file checks out good on his/her system have them compress (ZIP) the file and resend as it could have become corrupted during transfer. It can happen.
Your description of the file (zero length) sounds like it missed the last few bytes.
pancenter-

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.

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.

Concerned about losing 7 Express files when installing Logic 8

Will my Logic Express 7 files be deleted or corrupted when I install Logic 8?
From, "Before You Install Logic Studio":
WARNING: If you have installed Logic Express or Logic Pro 7 on your computer, the Logic Studio installer will delete some of the files in the Logic 7 factory content folder: Files with names identical to the default Logic 7 factory content files are deleted. Files with different names are moved to a new folder, called Previous Logic Settings. Logic Studio uses a new location for impulse response settings; Logic Pro 7 impulse response files remain unaffected. An existing installation of the Logic Express or Logic Pro 7 application will not be deleted by Logic Pro 8, allowing you to continue working with it.

Corrupted? I don't see why it would corrupt files per se. But if you want to be totally safe about things, make a backup first. Don't just install the new software and "hope for the best", cuz Murphy's Law is guaranteed to take effect. Back up first, install new software, play around with it. If something ends up sounding funky or whatever you can always access your original files from the backup.

Previous Logic Presets

Similar Messages

Maybe you are looking for