EXSP24 is having problems finding the audio files which are in the correct place and named correctly, I read a post not long ago with someone who had the same problem and it was solved by removing a .pkg, the only problem is I cant find the post again and i cant remember which package it was, I think it was something to do with Garage Band but as i say I cant 100% say that is correct. Anyway, if anyone can direct me to the post which i think was in October, or tell me the solution the this annoying problem, i will be very greatfull.

I'm just getting into making a new drum library for the EXS24II (in Logic Pro 7), and I'm a bit confused about what parameters are saved where. For example, the factory 'instruments' displayed in the EXS plugin editor (the instrument drop down above the cutoff knob), but those same factory 'instruments' do not have 'plugin' patches associated with them (in the drop down below the 'bypass' button on the EXS24 plugin). So if I do a search in the finder for the EXS factory instrument "Helicopter Action", all I find is "Helicopter Action.exs". However, if I load several of the factory instruments, I notice that they have different 'plugin' settings (i.e. envelope, cutoff, modulation, etc), but if I search for the names of those instruments in the finder, I only find *.exs files, no *.pst files, which are supposed to be the plugin settings for the EXS24. So it seems that the factory patches are getting different plugin settings from somewhere, but they don't have *pst patches associated with them. Are plugin settings saved in instruments (*.exs files) ?? If so, how come when I create a new instrument and save it, it doesn't save the plugin settings I was using at the time I create the instrument ?? More importantly, how do I manage plugin settings in general, with new patches I create ? If somebody could enlighten me, I'd greatly appreciate it. Thanks. Paul

Paul, The plugin settings are somewhat "ambivalent" when it comes to the EXS. In general, everything done in the EXS editor is saved inside the *.exs files. And, on a sidenote, everything done in the EXS editor *has* to be saved as recalling a song won't do the job (pretty much as stupid as it could get, especially when you're working with "songbased" instruments). Now, everything done on the EXS GUI is saved along with the song and can be saved as a plugin setting. To avoid confusion (as if things weren't confusing enough allready): Nothing done in the EXS editor will be saved with a plugin setting! In addition, you'll get a third option to apply the GUI settings to the *.exs file (found in the GUIs option menu). When to save as what is another question and there's some reasons to do it this or that way: - In older Logic versions there's been a limit of instruments accessable. Should you be using more instruments, saving slight GUI-altered variations of existing ones as plugin settings could've been a good idea. - Not applying any GUI settings to the actual *.exs patch could be of benefits too, as you could adjust the GUI on whatever patch, then call up another instrument and the GUI would just stay as it was on the previously loaded patch. Let's say you had a pad with some nice modulation settings loaded and wanted to transfer those to another pad - impossible in case the other pad had some GUI settings applied allready. Working fine in case there weren't any... Anyways, even if the "GUI copy" thing might be useful at times, generally the approach of having different file types for one plugin is lame. Just as lame as the fact that you have to save each and every instrument, even if you only plan to use it on one particular song. There's no other softsampler requiring such stupid actions. Regards, Sascha

Now I'm confused - aren't these GUI settings retained when you do a "save as instrument", or am I confusing this with something else? I haven't been doing a lot of work with the EXS lately, so I'm a bit hazy on the details. - Lenny Sascha Franck wrote: >Paul, > >The plugin settings are somewhat "ambivalent" when it comes to the EXS. > >In general, everything done in the EXS editor is saved inside the *.exs files. And, on a sidenote, everything done in the EXS editor >*has* to be saved as recalling a song won't do the job (pretty much as stupid as it could get, especially when you're working with >"songbased" instruments). > >Now, everything done on the EXS GUI is saved along with the song and can be saved as a plugin setting. To avoid confusion (as if >things weren't confusing enough allready): Nothing done in the EXS editor will be saved with a plugin setting! > >In addition, you'll get a third option to apply the GUI settings to the *.exs file (found in the GUIs option menu). > >When to save as what is another question and there's some reasons to do it this or that way: > >- In older Logic versions there's been a limit of instruments accessable. Should you be using more instruments, saving slight >GUI-altered variations of existing ones as plugin settings could've been a good idea. > >- Not applying any GUI settings to the actual *.exs patch could be of benefits too, as you could adjust the GUI on whatever patch, >then call up another instrument and the GUI would just stay as it was on the previously loaded patch. Let's say you had a pad with >some nice modulation settings loaded and wanted to transfer those to another pad - impossible in case the other pad had some GUI >settings applied allready. Working fine in case there weren't any... > >Anyways, even if the "GUI copy" thing might be useful at times, generally the approach of having different file types for one >plugin is lame. Just as lame as the fact that you have to save each and every instrument, even if you only plan to use it on one >particular song. There's no other softsampler requiring such stupid actions. > >Regards, >Sascha > > > > >________________________________________________________________________ >EXS Users Group - new web forums! http://logic-users.org/forums/EXS >- To UNSUBSCRIBE: email exs-users-unsubscribe@yahoogroups.com >- Search the entire archive: http://logic-users.org/forums/EXS/search >Yahoo! Groups Links > > > > > > > > > > > > -- ======================================================================== Lenny Stearns lens@planeteleven.net Alexandria, Virginia ========================================================================

I'm using Logic 7.0.1 on 10.4.2, with Pro App Suport 3. When I begin to play the piece, I get the "System Overload" message every few seconds. (The audio engine was not able to process all required data in time. (-10011). In the CPU window, the right column is never active, while the left column mostly says at 1/4, sometimes spiking to 3/4's. I press the "continue" button and begin to play again. The CoreAudio alert repeats a dozen times as I continue through the piece until I reach the last note I've been able to record. Then, I can suddenly play back from the beginning of the song, all the way through without the error message at all. It is as if the computer stops when it tries to process each new sample, but once it has played through all of them, it handles them easily. However, once I can play the whole piece, adding a new sample (a large sample like performance legato) doesn't trigger the alert message. I only get it when I am first beginning to play through the piece. I have an external Firewire HD by LaCie to store my samples, so that on the laptop, 37.91 GB's of 55.76 GB capacity are available. I use EXS 24 samples only, Solo Strings from VSL, with Core Audio (till I get more acquainted with Logic 7 and decide what I need). The piece is a string quartet, so even though I have 80 samples on different tracks, there are only 4 notes playing at once at any time. The only plug ins are platinumverb and gain, and the problem continues with these plug-ins "bypassed." I have been reading the discussion board and took advice given about upgrading to Logic 7.0.1, and getting Pro Application Support 3.1. The problems I experienced have not been corrected. I decided to use CoreAudio until I became more familiar with the program, and I realize with a three year old laptop, I must be pushing the system to the limit. But then again, it plays easily once I have slugged through the error messages. I ereased my HD and reinstalled Logic a few weeks ago. That did not fix the problem either. ( I upgraded to 10.4 to use Toast 7, but then I was unable to use my modem. After 72 hours of Apple support trouble shooting via telephone, I was told to erase my hard drive and reinstall everything. I did so and the problem wasn't fixed. I then talked to someone who knew of a bug in 10.4. I didn't have to erase the HD after all. I was told the bug was fixed in 10.4.2) The second problem involves saving. I save this piece as a "project." I can use the "save" option without a crash, but 99% of the time, if I use the "save as" option, I get the "beach ball of death" and send yet another report to Apple. How is my laptop able to process the data in time once I slog through all the alert messages telling me it cannot? Does anyone know of a "save as" fix? Much Obliged! Billy

Lenny Stearns wrote: > Now I'm confused - aren't these GUI settings retained when you do a > "save as instrument", or am I confusing this with something else? I > haven't been doing a lot of work with the EXS lately, so I'm a bit hazy > on the details. The GUI settings are only saved with the instrument after you performed an "apply settings to instrument" for the first time. After that they'll also be saved along with "save as" actions. - Sascha

> I'm using Logic 7.0.1 on 10.4.2, with Pro App Suport 3. When I > begin to play the piece, I get the "System Overload" message every few seconds. > (The audio > engine was not able to process all required data in time. (-10011). > In the CPU window, the right column is never active, while the left column > mostly says at 1/4, sometimes spiking to 3/4's. I press the "continue" > button and > begin to play again. The CoreAudio alert repeats a dozen times as I > continue through the piece until I reach the last note I've been able to > record. Before you debug your problems, you should buy the $20 upgrade to Logic 7.1. Many bugs were fixed and it is much more stable overall. Your problems might disappear after the upgrade. Even if not, your whole experience using logic will improve. Then when you debug these issues, you know you won't be wasting your time working on something that has already been fixed in an update. - Dave

Has anyone seen this before? After looping an 8 bar group for 7 or 8 passes the drum tracks just stop playing. I've noticed this behavior if the Mac goes to sleep and core audio doesn't reset correctly but this one is new to me. The drums are a simple apple loop that i have repeating while laying down some guitar tracks. hmmm... G5 dual 2.7, 8 gigs ram, dual 250 gig satas. Stumped, S-trump

Sasha, Thanks alot for the explanation. I would have never figured that out from the manual. So its seems like my best bet if I want to save 'plugin' settings with an instrument, is to use the 'save instrument as' command from the options dropdown in the EXS GUI to save plugin settings with my instruments. Thanks again. Paul

--- In exs-users@yahoogroups.com, "sampletrump" <sampletrump@y...> wrote: > > Has anyone seen this before? After looping an 8 bar group for 7 or 8 > passes the drum tracks just stop playing. I've noticed this behavior > if the Mac goes to sleep and core audio doesn't reset correctly but > this one is new to me. I know that with my old hardware sampler, that if I have a sample that was an exact number of bars, that I would have a problem with it triggering properly when I had it looped in a sequence. Try making the loop sample a few samples shorter than the exact bar amount, if that makes sense. Just chop off a couples sames from the end of the sample loop. You won't notice a few samples missing, and it may solve you're problem. Let me know. Paul

Please provide more detail Does the drum track only stop looping, or does all playback-audio stop? Do midi tracks continue to play? Does the song position pointer continue moving? Does the record track continue recording? Does it always stop after the same number of loops? When you say looping, do you mean you are cycling between locators or that you have the drum track set to loop the region? - Dave

I want all the drums from drum machines, keyboards and sound modules in the form of aiff or wav files on a CDROM. I have alot of drum machine drums from some sample CDs called '116 electric drum machines' and 'Dance Mega Drums V1' But I know they are not complete because there are only maybe 60 samples for the Alesis SR16 but when I search the internet for the specs of the Alesis SR16 there are 100s of drum sounds. So the sample CD people are leaving some sounds out. I would like to have a complete collection of drums from all the drum machines except all those analogue cheap sounds which form the bulk of the sample CDs I mentioned. I have bought 2 separate sample CD sets from eBay that boasted to contain all the drums from the Triton, Mo Phatt, Motif, XV5080 etc etc. But both seperate products were absolutely crappy quality. I think they used some sort of automated sampler cause 2 out of 3 files were just silence or a bit of noise. And the recording quality of both products was extremely poor to the point of ridiculousness. I have gained a complete set of drums of a yamaha drum machine (maybe the ry10) or something) which are quality from an akai list members link to downloads. Has anyone bought a quality COMPLETE library of any drum machines, keyboards or modules? Let me know yall. I'd even like the drums from keyboards like Korg M1 etc. Just so I have as many drum sound options as possible. Thanks, Roman Pirie.

> I'm using Logic 7.0.1 on 10.4.2, with Pro App Suport 3. When I > begin to play the piece, I get the "System Overload" message every few seconds. > (The audio engine was not able to process all required data in time. (-10011). > In the CPU window, the right column is never active, while the left column > mostly says at 1/4, sometimes spiking to 3/4's. I press the "continue" > button and begin to play again. The CoreAudio alert repeats a dozen times as I > continue through the piece until I reach the last note I've been able to > record. This is fairly typical if you're using a lot of sample ram...for your system. I used a laptop for years and this was the way of things...don't worry...You can make great music on a laptop...but...you can finally get to where you overload the system entirely. But sounds like you're working within what you're system can do. If you get to the point where the song won't play....you can always bounce tracks or freeze tracks to relieve the load. Bouncing seemed to work best for my laptop. hope this helps julie www.julielarson.net

--- In exs-users@yahoogroups.com, David Gordon <music-pro@c...> wrote: > > Please provide more detail > > Does the drum track only stop looping, or does all playback-audio > stop? Only the drum track which is an apple garage band drum loop Do midi tracks continue to play? Yes > > Does the song position pointer continue moving? Yes Does the record track continue recording? Yes > > Does it always stop after the same number of loops? I don't know that yet. I'm trying to set up a control test environment. > > When you say looping, do you mean you are cycling between locators or > that you have the drum track set to loop the region? I have set an 8 bar region for all to repeat. the drum track is pulled from a one bar loop to repeat for the 8 bars. This is a strange behavior indeed. I can't consistently reproduce the error but it has happened on two uniquely different projects at different times. All of a sudden that drum track just stops working. It has only been the drums too; not a bass line or an audio region. As i'm typing this it has looped a hundred times with no problems. I also shut logic down and restarted fresh. Weird. > > - Dave > Thanks Dave. Trump

Hmmmm.... sampling and selling drum samples from current products like the Motif, Triton, etc., you refer to is dodgy and will almost certainly be frowned on by the manufacturer to the point of legal action (especially Roland who are particularly strict!). Even giving them away free is not on either - the same as lifting and giving away samples from a commercial sound library! Samples from older, discontinued products such as the M1 or an old LinnDrum, whatever, is not so dangerous (although some will not allow even that if the manufacturer is still in business). For this reason, you are unlikely to find any commercial products with the drum sounds you require. It could be argued that if you borrow/hire the original and sample themselves for your own use, that would be ok but, in fairness, that's the same as borrowing, say, Garritan Personal Orchestra and sampling that - it's a lost sale for the manufacturer who is trying to recoup costs from sales (as well as paying staff, etc.). The only kosher variation would be if you personally owned the products in question and sampled them purely for your own use (like copying a CD onto cassette for use in the car, whatever). As for stuff on eBay... don't get me started! Largely sub-standard shite made by cowboys to make a few bucks. I've not bought any but I know loads of people who have and almost all are utter rubbish. Many are also totally illegal (not that eBay give a fish's arse about that... as long as they get their commission!!!). Best regards, Steve http://www.hollowsun.com

Powerbook G4 1.67ghz 1.5 gig ram Logic Pro 7.1 After recently installing Logic pro 7.1, I'm now finding that the EXS24 sampler can't find the preset samples. When I go to Load setting and select the sampled instruments folder, all the instruments in each sub folder are non selectable. I can see them all there but they are just dimmed out. Any ideas anyone?

Of course it would help if I read the manual first before posting stupid questions.

>After recently installing Logic pro 7.1, I'm now finding that the >EXS24 sampler can't find the preset samples. When I go to Load setting >and select the sampled instruments folder, all the instruments in each >sub folder are non selectable. I can see them all there but they are >just dimmed out. Any ideas anyone? and then: >Of course it would help if I read the manual first before posting >stupid questions. :-) There are no stupid questions - only stupid answers. Just for the record, if you ever REALLY can't load instruments or stuff seems prohibited, look immediately at your permissions. I recently installed a Palm Desktop update which totally screwed with my permissions systemwide. I constantly find folders which are read only and belong to System that I'm locked out of until I manually re-configure them. Wholesale pain in the butt. Anyone know of an app that can do bulk/batch permission changes.....? Regards - Colin

Hi Trump Since you can't reproduce this error every time, it's hard to debug. One thing you can try as a workaround or alternate test is to change the way you are looping the drum region. Here are a couple ideas: - instead of pulling the loop graphically, turn on loop-region with the checkbox in the parameter box or the key command - instead of looping, use aliases or copies of the region Also, make sure the region is completely within the looped cycle. If you are using an audio Apple loop, make sure it starts right on the one beat and not before it. If you are using a MIDI Apple loop, make sure the first MIDI not does not occur before the 1 beat of the first bar of the cycle. Next time you have the error, jot down how long the looping worked OK. Keep notes of the behavior and try and find a pattern. Good luck! - Dave

Hi Check out MODARCHIVE.Lots of samples plus you can download all as bit torrent file. JON

Hi family, I own a Hohner Blues Harp in C, hardly played, from the 50's and so brown it makes me shiver... Any ideas how to transform this beauty to exs, I'm willing to post the files. Scheduled to 12/31/05, sorry, eBay then

> Anyone know of an app that can do bulk/batch permission changes.....? Sure...batchmod http://macchampion.com/arbysoft/ best, Jeff

haraldschneller wrote: > Hi family, > I own a Hohner Blues Harp in C, hardly played, > from the 50's and so brown it makes me shiver... > Any ideas how to transform this beauty to exs, I'm willing to post the files. > Scheduled to 12/31/05, sorry, eBay then Just sample as many sustained (or not sustained) notes you can get out of it. Plain notes, bends, squeals, whatever. Then post the wavefiles somewhere and let's see what we can come up with. Just make sure the plain notes are long enough to add some useful loop points. Cheers, Sascha

Hi I'm trying to convert a large sample library for on Emu IV to exs format on a mac using Translator. The library is currently on magneto-optical discs in EMU format on a Sony SMO-S501A-11 drive which doesn't seem to be recognised by my old scsi G3. Any suggestions? TIA John

At 11:45 AM 10/27/2005 +0100, you wrote: >I'm trying to convert a large sample library for on Emu IV to exs format on >a mac using Translator. >The library is currently on magneto-optical discs in EMU format on a Sony >SMO-S501A-11 drive which doesn't seem to be recognised by my old scsi G3. Make an Image of it first, put that image file in the Images folder in the Translator folder, and then open Translator, it will show in the Images section on the left. You can make an Image usually by using Toast (Device Copy), or by Disk Utility in OSX Panther or DiskCopy in Jaguar. (Note: you can put aliases in the images folder too to access the image.) Garth Hjelte Sampler User