System overloaded, repeat immediately by batch when triggering event

Hi,
My workflow was working till yesterday. But suddenly today, when I run the same process, event is triggered and I Can see the RFC status 'System overloaded, repeat immediately by batch'. And the workflow is not started.
Can anyone help me in this?
Thanks,
Sivagami R

Hello,
It seems that can happen - an event can be created and the workflow it's supposed to trigger doesn't start.
Was there a system crash? Try looking in tx SM58 for the missed events.
regards
Rick Bakker
Hanabi Technology

Similar Messages

JCoIDoc: "System overloaded, repeat immediately by batch"

The SM58 screen (Transactional RFC status) displays this message for every IDoc sent to a JCoIDoc server application. Function module is IDOC_INBOUND_ASYNCHRONOUS (is this correct for outgoing IDocs?), and Program name is SAPMSED7. RFC comm test works fine.
Michael

Hi, did you ever get an answer to this?

System Overload/Core Audio Error Message when recording/playback

Well ive been experience this problem for a while now but ive read up on it and done some troubleshooting and think i may have found a solution.
Well what happens is ill be recording say one track or 2 tracks in mono or stereo or playing back about 3 or 4 tracks and logic will stop everything and give me an error message which either says system overload or core audio overload or something. Well i figured i was overloading my cpu so what i tried doing was restarting my computer and then only operating logic as the only program. this worked temporarily sometimes but not in the long run. well i did research and came to this.
apparently its too overbearing for my Powerbook processor to record in 24 bit/96 Khz which is kind of a bummer because it was one of my attractions to my i/o box that i could do that. also freezing tracks will help greatly apparently which i have yet to try but hope will work too.
also i recently deleted about half of the stuff on my internal drive and put my 42.41 GB of music onto my external HD so now i have 54.6 GB on my internal HD which holds about 93 GB total. should this help me greatly? or will it only be a minute difference?
well any more solutions/suggestions as to what i can do to better my situation? also am i correct as to why i think i get those error messages.
ps: sorry for the uncapitalization, i got a bit lazy here
thanks
-Mike

Mike,
Bit depth is more important for recording quality than huge sample rates. If you're going to change your settings, I'd stick with 24 bit, but reduce sample rate to 48 kHz.
When you say you've put all your music on the external drive, what exactly do you mean--your Logic files or your mp3/AAC files? Normally you would want to use an external drive to record onto from Logic. That way your internal HD can run the OS and Logic, while the external is free for all the fast recording tasks. (This assumes your external HD is pretty fast, and ideally is firewire.)
Freezing works wonders, too, if you're processing tracks.
-Eric

Repeated crashing of ical when editing events

Hi, new to this but looks good so here it goes. Mac in general seems to be playing up right now but ical in particular is crashing EVERY time I change the calender type (colour) of an event or move it to a new date or 'cut' it. No error message, no being slow just totally shuts down and then does the whole reporting to apple and relaunching business. Can't seem to find anything online that fixes this and has never done it up until maybe a week ago. Also got issues with my PPOE server if that offers any help!?
Thank you in advance!

Find the latest iCal crash report in your Library/Logs/Crash Reporter folder, double click to open it (it should open with console.app) and paste the contents here. While you have console open look in console message to see has iCal posted anything there before crashing - if so, paste that here too.
AK

Quesry: System Overloaded error

Hi,
I have created a copy of the standard workflow ws30000015.
Ii have done some modifications to it to create a custom workflow.
I have event linkage in swetypv in such a way that the custom workflow is triggered instead of the standard workflow. Now, when I create an absence notification, the custom workflow is triggered, but I donu2019t see any workitem.
SWEL shows the following error.
Action: Receiver started correctly
RFC status: System overloaded, repeat immediately by batch.
Please help.

Check this notes.
Note 1025249 - Entries in transaction SM58 "hang"
Thanks
Arghadip

SYSTEM OVERLOAD SOLUTION! MAYBE...

Hi guys!
For everybody who are fighting against this annoying problem!
I read about somewhere here, somebody wote about there is a folder:
Macintosh HD/Library/Audio/Midi Drivers
Somebody has drivers there, and somebody dont have.
In this folder i had two drivers: EmagicUSBMIDIDriver.plugin and EMUMIDIDriver.plugin
I dont know these two drivers are necessary or not, - i have EMU USB 0202 soundcard - but i tried, what will happen, if i take out this two drivers, just like that.
I put these files in a safe folder, in case if something problem would come.
This happened: NO MORE SYSTEM OVERLOAD ANYMORE to me!
All the Logic softwers and plugins works fine, no stopping all the time, no system overloads in every 5 seconds.
Also, often the iTunes running, because i always compare my music with another pro music, and no system overload at all!
=)
Only, when i tried to open Firefox with 12 tabs during playback.
=)
Try this too, and wrote to here, what is the result!
I hope it will stay, and it will help many other users too!

Have you seen these?
http://support.apple.com/kb/TA24535?viewlocale=en_US
http://support.apple.com/kb/HT3161
Two more tips from me: Be sure to NOT have a Software Instrument track selected when playing back. The instrument then is 'ready to be played' and therefore needs more CPU. If you select an audio track, aux track or a frozen SI track, it is easier on the CPU.
Secondly, set all audio tracks to *No Input*. That has ben reliably reported to make a difference too.
Thirdly (bonus) set the *Process Buffer Range* (in the Audio prefs) to Large.
Also, keep in mind that just muting a in the track header doesn't disable anything, the content is still streamed. Only when you mute the regions, the content is left out of the process.
regards, Erik.

I experience frequent ¨system overload¨when recording.why? andhow can I remedy the problem? thanks max

http://[email protected]
i experience frequent¨system overload¨why? and how do i avoid it? max seiler

If the problem exclusively shows up while recording, my first guess would be to reconfigure the I/O Buffer Size. Just an idea though as long as you do not share some more system details with us.
And also, if you haven't read this:
http://help.apple.com/logicpro/mac/9.1.6/en/logicpro/usermanual/#chapter=44%26se ction=4
Perhaps now's the time?
Have a nice day!

Solution for "Error while trying to synchronize Audio and MIDI" and "System Overload" messages

Article for those who hate Logic error windows
Seen in Logic Pro 9.1.7 on Mac OS X Lion 10.7.4
and Logic Pro 9.0.0 on Mac OS X Snow Leopard 10.6.5
Logic Pro:
System Overload.
The audio engine was not able to process all required data in time.
(-10011)
Error while trying to synchronize Audio and MIDI.
Sample Rate xxxxx recognized.
Check conflict between Logic Pro and external device.
The search in the help given as follows: overload occurs when you use a lot of tracks and a lot of effects on them, and the synchronization is lost when the selected MIDI track for recording or playback. Yes, this is all that is written in the resources. And here are useful tips that have been found:
The Bounce function allows the entire instrument track to be recorded as an audio file. This bounced audio file can then be used (as an audio region) on a standard audio track, allowing you to reassign the available processing power for further software instrument tracks. For more details, see "Bouncing Your Project."
You can also make use of the Freeze function to capture the output of a software instrument track, again saving processing power. For details, see "Freezing Tracks in the Arrange Area."
These tips - about the timing. About overload - there are no tips, except as "reducing the number of plug-ins" and "increasing latency". Zero useful tips - I got two errors in the test project with a blank audio track with no effects, MIDI drums and standard synthesizer, it was no aux buses, and the entire project was only a single plugin in the master track.
Here is the configuration of my computer:
iMac12, 2
CPU: Intel Core i5 3,1 GHz
Memory: 4 GB
And here's a project that almost immediately stops Logic, all instruments and plug-ins with the init-patch, ie not the most demanding settings:
It's sad.
When this happened the first time, I could start the project only if the empty audio track has been selected, a track specially designed so that you can at least start the project. Then, this problem has evaporated along with the changing conditions of work and I forgot about it until the last case.
I was looking for the cause of the problem in the console and the system monitor for two days, and finally I found that Logic ping to the network frequently. I remembered the exact time of occurrence of the problem, and system logs revealed that the problems began immediately, as soon as I deactivate the service of the Internet.
Solution: enable the Internet, or add a new network service on a computer with no Internet. I just created the Ethernet connection to the ip address 1.0.0.0
Logic immediately began to sing.

Hi gabaghoul
Yes, it worked for me on four different OS and Logic versions (10.6 - 10.8 and 9.0 - 9.1.6)
It does not work in some cases, hard enough to tell in which one, but you can try, it very easy: go to the net settings and create new Ethernet connection to the ip address 1.0.0.0 and connect LAN cable to the port.
Also you can try to figure out what happens in your system while Logic error occured - fot that you just start Console and search "logicpro"
Pay attention to repetitive events in a console and events with suitable timing, not so far from error
The problem may be related to the GUI or system memory, sometimes turning off Safari (or Chrome, others browsers) might help.
Message was edited by: spred

"system overload" in logic pro 8 on my Mac Pro with only three tracks

I am running Logic Pro 8, on a 2.66 Quad Core Mac Pro w/ only 1GB of RAM. I have not had the money for the much needed ram upgrade, yet.
The day before yesterday I opened a project I had opened many times, with only three tracks - two audio and a midi synth with only a few notes. These tracks are fairly well plugin-ed up, but this Mac Pro has always eaten them up, no problems. When I tried to play the project, I got system overloads every 2 seconds, rather precisely actually. My CPU usage reads low in logic and with iStat, but suddenly it peaks to 100% on my third core and I get the system overload.
I had my buffer size at 128, so I switched it to 1024, it worked, and then I switched it back again and everything worked like it used to!
But now I have to go through this slightly illogical little procedure everytime I open a project. I have read threads here about this subject before, back I cant seem to apply them / understand them in relation to my particular situation.
any ideas?

Join the club...wait for them to patch/update it.
I've tried the various work arounds, sometimes they work temporarily, sometimes not at all.
For the overloads the most reliable "work around" is to select each track, open the VI/FX modules associated with that track, then close them, go to the next track and repeat the process. OR, if you know all the modules (VI/FX) you're using, just open each one. This will "initialize" their existance BEFORE the audio engine hits them in playback.
My guess is LP8 tries to reduce it's memory foot print and does NOT initialize all the VI/FX in a saved project that is just opened until it actually needs to use them -- a good idea one would think. However, when you do your playback and it hits the VI/FX for the first time (after you just opened your saved project) it appears the audio engine stalls waiting for the VI/FX to initialize the 1st time around and hence the overloads error. Obviously I can't prove this since I don't have access to the code, but I'm a developer and this would be my logical guess based on the evidence at hand.
I can reproduce the problem consistently:
1. Start LP8
2. Open existing project with 3 tracks (staggered to start a different times) with different VI on each track
3. Have 3 buses with a different FX on each bus
4. Do nothing other than hit Play
Overload when it hits start of 1st track VI, stop, restart, overloads when it hits start point of 2nd track VI, stop restart, overloads when it hits start point of 3rd track.
Why wasn't something this obvious caught in testing? Good question.
Rob.
Message was edited by: Rob A.

Disk is too slow or System Overload. (-10009)

Hello all,
I'm running a G4 PowerBook, with 1.67 GHz, and 1.5 GB DDR SDRAM. My Logic set-up is Logic Pro 7 and a Motu 828mkII.
My present Logic project contains 7 tracks, with EXS24 through 6 tracks and Sculpture through the last. The instruments were triggered through a midi keyboard.
While trying to score a short film, I keep running into the following error:
CoreAudio: Disk is too slow or System Overload. (-10009). The error happens while recording and during playback only. There are times when I do not recieve the error message, but playback is terribly jerky and I'm unable to clearly see exactly where I am on the timeline.
I have searched for similar errors on this site and cannot seem to find an answer. I imagine the solution is changing the way I have my I/O setting in the CPU usage. Am I on base?
I'd appreciate any help,
Kris

Hey Cyril and 25G's,
Well I went out and bought a OWC Mercury Elite Pro Firewire 800 with Oxford 912. I transferred the EXS Factory Sample files to the OWC drive. Then I deleted the EXS Factory Sample files on the OS hard disk. Then I created the alias for the Samples and placed the alias back in the Logic file under Application Support on the OS hard disk.
The alias' seem to be working because the Logic project works. The only problem is that it is still terribly jerky.
The CPU is maxing out while the I/O meter is not responding at all. Could this be the clue to my problem?
(Also, Cyril, call me stupid, but I cannot find the Virtual Memory portion in the EXS Preferences.)
Thank you for all your help. (I am a bit slow myself when it comes to Logic and the proper steps to de-bugging a problem. So, very detailed explanations are appreciated)

System Overload & "Save as" crashes

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

I'm not sure if you have this, and mis-typed or something, but Logic 7.1 (the update you pay for) and the 7.0.1 and Pro App Support solved this problem for me. However, we installed them all at once so I don't know which fixed the "Save As..." glitch....
Regarding the other query, I sometimes get this too - the computer seems to think there's too much information even though it's already been playing it all, and even if you mute all but one of the channels! (in fact - I think I recall it refusing to play even when all tracks are muted... christ...)
Generally I have to restart the app (and maybe the computer). This always does the trick for me.
Hope this helps,
Best,
Mickey.

"Disk too slow or System Overload" ... hardly

Hi all!
I hung onto my 2007 MacPro until just before summer when I upgraded to be on the safe side. I do orchestral work and have been accustomed to running heavy VSL projects on one single machine pretty effortlessly. On my new 12 MacPro, things are working even smootherEXCEPT for this "Disk too slow or System Overload" happening from time to time on fades. The projects in hich I experience this behaviour are audio only, orchestral mixes of between 60 and 70 audio tracks and I get the message when executing fades on all tracks simultaneously. I can't remember getting this on my old MacPro which had a fraction of the cpu-power and not nearly as much ram.
My specs are 2x2.66 6-Core w/32GB ram, and all audio files, fade files and othe project files, are written to two 2 TB 7200 disks in the internal disk slots, configured as striped RAID. This gives more than enough speed and I still have 1,64 TB of free space on the RAID set.
This issue comes and goes and I can't seem to figure out what triggers Logic's problem to read fades fast enough. Just now I had some corrupted fade ailes, rebuildt them and now Logic can't get past the fades at all unless I start playing in the middle of them.
I can't understand why this problem should be introduced on a configuration much, much faster than my previous MacPro where this problem hardly ever occured. I even doubled the I/O buffer from 512 that I was using on my old mac, to 1024 with no difference at all. Increasing Process buffer size to "Large" doesn't have any affet either.
Any clues anyone?
Best regards,
Ginge

Good point, nice link!
But the thing is I'm not using any software instruments and apart from one EQ on a track here and there, two Tube tech plugs and two sends to Altiverb (of which one is inactive). This kind of load was not a problem on the old heap and shouldn't be a challenge for a 12-core... Also, without changing anything apart from the move above, it is now playing with only one pixel-high movement on the meter, like you would expect it to do.
BTW the quirk is now back on the project that was fixed. I did new fades at another position and CPU 1 is now maxing out again. A new set of fades means equal fades on regions on 63 tracks playing simultaneously.
As I'm writing I'm becoming aware of one interesting aspect: the project files contains imported aaf data and to save space I'm leaving the media-files at the original location where it was put by Pyramix who exported the aaf. I figure there shouldn't be a difference if the audio files reside in a folder called "Media files" or "Audio files". These folders are sitting on the same disk albeit not in the same subfolder. If anything, I'd assume it would minimize potential for error caused by having several copies of files with identically names on different locations on the disks. But now it seems the issue is less likely to appear if I save the project including assets, copying external audio files (on any disk), or at least that is how it looks like right now. New fades are working fine after I've done this.
Doesn't make sense to me but it seems to make a difference...
Ginge

System Overload ...i know ..I'm not the 1st ...

_History Below_
Topic : System Overload ...i know ..I'm not the 1st ...
This topic has been archived - replies are not allowed.
Your question is not answered.
Mark as answered.
Use the "helpful" or "solved" buttons to award points to replies.
Subscribe to this Topic Back to Topic List
Replies : 10 - Pages : 1 - Last Post : Aug 10, 2009 12:04 PM by: Pancenter
4feet4
Posts: 17
From: Pasadena
Registered: Mar 12, 2009
System Overload ...i know ..I'm not the 1st ...
Posted: Aug 9, 2009 7:52 PM
Any quick tips on what to do? My project is small - while monitoring my CPU usage it never goes above 30 while running the project - I've got 2.78 GB of free disk space - 4Gig Ram - I dont use my IMAC OSX 10.5.5 for anything but Logic? Hoping to get around this CONSTANT issue - thanks for your help.
Imac Mac OS X (10.5.5)
Larry Mal
Posts: 654
From: Saint Louis, Missouri
Registered: Sep 27, 2007
Re: System Overload ...i know ..I'm not the 1st ...
Posted: Aug 9, 2009 9:48 PM in response to: 4feet4
Well, if you are saying you have only 2.78 GB's of space on your hard drive, then you'll want to have more. You should leave about 10-15% of your drive free.
dual 2.8GHz Mac Pro, Macbook Pro 2.16 GHz Mac OS X (10.5.6) 2 GB RAM
4feet4
Posts: 17
From: Pasadena
Registered: Mar 12, 2009
Re: System Overload ...i know ..I'm not the 1st ...
Posted: Aug 9, 2009 10:51 PM in response to: Larry Mal
I'm running LP8 - I have an IMAC OSX 10.5.5 - 2.4 processor - 4 GB RAM - M-Audio Fast Track Pro interface (USB direct to MAC) - I do NOT have an external hard drive ( sounds like I should ? - although I was told by others my system would be sufficient) - I use ALL instruments/track options ( midi etc) and will need to in the future - I want to be able to run a full music project 10-15 tracks. So far I'm running 4-5 tracks -(1) midi - the rest are audio with little to no effects ( in one project I'm using an LP8 template but deleted most of the tracks to cut down on the load ). Don't know if I can freeze these tracks-I'm new to this - thats why I'm looking for options ........ i was also using a 3rd party software in the project - Steinberg Groove Agent 3 (drums) but it was giving me the same error ..even when it was the ONLY track in the project....(its not fully compatible) - however I was finally able to create a full drum track with GA3 - play the midi data back - and record it to an audio track - therefore deleting the midi data I was having issues with and keeping the drums.... hope this helps?
Imac Mac OS X (10.5.5)
4feet4
Posts: 17
From: Pasadena
Registered: Mar 12, 2009
Re: System Overload ...i know ..I'm not the 1st ...
Posted: Aug 10, 2009 6:39 AM in response to: 4feet4
Updated
Imac Mac OS X (10.5.5) 2.4 Processor, 4 GB RAM, M-Audio Fast Track Pro Interface, No External HD
Larry Mal
Posts: 654
From: Saint Louis, Missouri
Registered: Sep 27, 2007
Re: System Overload ...i know ..I'm not the 1st ...
Posted: Aug 10, 2009 7:54 AM in response to: 4feet4
Perfect. Well here are some suggestions:
1) Logic 7, 8 and 9 all have a "freeze" function. Logic 9 has a new "bounce in place" function which I haven't used yet. These will make temporary audio files of your MIDI instruments so that you are able to play them as finished audio for the most part and free up CPU power. ( I haven't yet used "bounce in place", I just got Logic 9.) This will help with MIDI instruments quite a bit, and you can still go back and change them by un-freezing... I guess "thawing" would be the proper term.
2) The reason I was asking about your audio interface is because I was wondering what you had available. You very definitely want to record to a non-system (on that Logic nor your operating system are on) drive. Firewire is much superior to USB, which is why I'm glad to hear you are using USB as your audio in. By using Firewire in and Firewire out, on an iMac, you would be halving the bandwidth. In your case you are not.
You will add very much stability to your Logic work by adding an external Firewire drive and recording audio to it, and working on Logic projects there! If you have the money, I'd go with Firewire 800, which is frankly overkill, but why not. Firewire 400 drives will work fine for you. Add one and many of the overload messages will disappear, simply because right now you are pulling information from (in the form of calculating what the virtual instruments and Logic are doing) and writing information to (in the form of writing what those instruments and Logic are resulting in) to the same disk.
Try these two things and get back to us. I think you'll be very happy with the results.
It's also important to pay attention to your buffer size. When it is not important for you to play with it in real time, you want to make it be 1024. Otherwise as low as possible. So when you are recording audio to a MIDI drum track, you'd want it to be very low so you can play along accurately. When you have all that done, and are editing MIDI only, then put the buffer higher. When mixing, put it higher.
Let me know how this works, good luck, L
dual 2.8GHz Mac Pro, Macbook Pro 2.16 GHz Mac OS X (10.5.6) 2 GB RAM
4feet4
Posts: 17
From: Pasadena
Registered: Mar 12, 2009
Re: System Overload ...i know ..I'm not the 1st ...
Posted: Aug 10, 2009 9:10 AM in response to: Larry Mal
Ok Great - Thanks - makes sense - I was using a Lacie with Protools an my PC ( it recently crashed) - I was under the impression I would have enough processing power with out it on the MAC.
Looks like I can pick one up for just a little over $100 ( I'm rolling in that kind of cash) ... please clarify though - you stated: "Firewire is much superior to USB, which is why I'm glad to hear you are using USB as your audio in. By using Firewire in and Firewire out, on an iMac, you would be halving the bandwidth. In your case you are not" ....are you GLAD to hear I am using USB as in - We may have found the problem .... go external to free up processing ? Please confirm.
Thanks again
Imac Mac OS X (10.5.5) 2.4 Processor, 4 GB RAM, M-Audio Fast Track Pro Interface, No External HD
CCTM
Posts: 249
Registered: Mar 11, 2007
Re: System Overload ...i know ..I'm not the 1st ...
Posted: Aug 10, 2009 9:28 AM in response to: 4feet4
4feet4 wrote:
Ok Great - Thanks - makes sense - I was using a Lacie with Protools an my PC ( it recently crashed) - I was under the impression I would have enough processing power with out it on the MAC.
As stated in an earlier reply, if you only have 2 or 3 gigs of free space on your Mac hard drive, processing power is NOT the problem. Your boot disc is way too full. You should have at least 20-30GB free.
Running a second drive for the audio side will, of course, help, but you MUST clear out the main hard drive (or fit a larger one) before you run into even more serious problems.
HTH
CCT
Larry Mal
Posts: 654
From: Saint Louis, Missouri
Registered: Sep 27, 2007
Re: System Overload ...i know ..I'm not the 1st ...
Posted: Aug 10, 2009 9:37 AM in response to: 4feet4
Well, you have enough processing power, that isn't the issue. All the processing power in the world won't matter if you have 64 megabytes of RAM, there will be a bottleneck. Another bottleneck is with data transference. Like I said, when using a single drive to transfer date from as well as to- which is what you are doing when you are using Logic, running within the scope of the operating system, and hosting virtual instruments, all of which is writing the resulting audio information to the same drive, at the same time, then you are creating another problem. But you don't have to do that, by sending the audio written to another drive other than the one the audio is being generated from.
In other words, your processing power is both faster than and irrelevant to the physical limitations of the hard drive itself.
Another bottleneck would be if you were recording tracks on a Firewire in, and sending that to and external Firewire drive out. This is one of the limitations of the iMac, there is no way to add what is called another bus, which is simply another pipeline for data transference. You can get around that with a Mac Pro, in which you add another internal hard drive, which connects directly to the motherboard, and has its own bus. Or by adding another Firewire PCIe card, which will add another Firewire bus, again, with its own data transference. On an iMac, you have one Firewire bus, and one USB bus.
Clear? You can imagine these as pipes of water. The more pipes you have leading to and from a location the faster it will go.
USB, in your case, is a dedicated pipeline in. Nothing (well, your mouse, maybe a flash drive) is using that pipeline. Your Firewire is a pipeline out, in this case- you could reverse this, it doesn't matter*. If you use Firewire in and out, then you are sending water flowing in both directions in the same pipe. It will work, but not as well. By adding a dedicated bus, you would be adding another pipe to flow in one way, while the original flowed the other way. No impedances.
I don't see why you can't use the Lacie drive you already have, though. It's quite likely your crash wasn't due to it. No need to buy another drive, if it's Firewire, anyway. Just give it a shot- this isn't a cure all, but just good audio practice. Let me know how it pans out. Good luck, L
*Firewire is better than USB in all situations. But you seem to be going a track or two of USB audio in, so I'd use USB for that. For light use it's fine. Then you can use your superior Firewire bus to write the audio to the external Firewire drive.
dual 2.8GHz Mac Pro, Macbook Pro 2.16 GHz Mac OS X (10.5.6) 2 GB RAM
4feet4
Posts: 17
From: Pasadena
Registered: Mar 12, 2009
Re: System Overload ...i know ..I'm not the 1st ...
Posted: Aug 10, 2009 11:12 AM in response to: Larry Mal
L - Thanks for laying that out in simple terms - learning a ton and loving it ( when things work) - I will pick up another Lacie - my old Lacie for my PC crashed - I'm better off starting from scratch ( I'm still trying to retrive some data of the old one) ... I'll let you know how it works. I would have got an external drive outright but the Logic Certified guys at Apple told me I would not need one - sounds like this is the big problem. I'll use the freeze method when needed also....... maybe I'll have better luck with Groove Agent 3 with the external drive.
Much appreciated-
(TBD)
Imac Mac OS X (10.5.5) 2.4 Processor, 4 GB RAM, M-Audio Fast Track Pro Interface, No External HD
Larry Mal
Posts: 654
From: Saint Louis, Missouri
Registered: Sep 27, 2007
Re: System Overload ...i know ..I'm not the 1st ...
Posted: Aug 10, 2009 11:39 AM in response to: 4feet4
And free up some room on that system drive.
dual 2.8GHz Mac Pro, Macbook Pro 2.16 GHz Mac OS X (10.5.6) 2 GB RAM
Pancenter
Posts: 3,306
From: Southwest U.S.
Registered: Apr 22, 2007
Re: System Overload ...i know ..I'm not the 1st ...
Posted: Aug 10, 2009 12:04 PM in response to: 4feet4
4feet4 wrote:
L - Thanks for laying that out in simple terms - learning a ton and loving it ( when things work) - I will pick up another Lacie - my old Lacie for my PC crashed - I'm better off starting from scratch ( I'm still trying to retrive some data of the old one) ... I'll let you know how it works. I would have got an external drive outright but the Logic Certified guys at Apple told me I would not need one - sounds like this is the big problem. I'll use the freeze method when needed also....... maybe I'll have better luck with Groove Agent 3 with the external drive.
Groove Agent 3 loads samples into memory so I doubt if your luck will change.
The -first- thing I would do is clear some space on your hard drive, my feeling is that OSX is writing swap files and the drive head is working overtime to try and find free space to write. That in itself could cause an overload.
Free drive space now or expect more problems than you're currently experiencing.
pancenter-
Power Mac G5 1.8GHz Dual, 4GB RAM Mac OS X (10.5.5) RME Audio - MOTU MIDI, Mac (Logic 8.02), Intel/XP-Pro Quad Core PC

_History Below_
Topic : System Overload ...i know ..I'm not the 1st ...
This topic has been archived - replies are not allowed.
Your question is not answered.
Mark as answered.
Use the "helpful" or "solved" buttons to award points to replies.
Subscribe to this Topic Back to Topic List
Replies : 10 - Pages : 1 - Last Post : Aug 10, 2009 12:04 PM by: Pancenter
4feet4
Posts: 17
From: Pasadena
Registered: Mar 12, 2009
System Overload ...i know ..I'm not the 1st ...
Posted: Aug 9, 2009 7:52 PM
Any quick tips on what to do? My project is small - while monitoring my CPU usage it never goes above 30 while running the project - I've got 2.78 GB of free disk space - 4Gig Ram - I dont use my IMAC OSX 10.5.5 for anything but Logic? Hoping to get around this CONSTANT issue - thanks for your help.
Imac Mac OS X (10.5.5)
Larry Mal
Posts: 654
From: Saint Louis, Missouri
Registered: Sep 27, 2007
Re: System Overload ...i know ..I'm not the 1st ...
Posted: Aug 9, 2009 9:48 PM in response to: 4feet4
Well, if you are saying you have only 2.78 GB's of space on your hard drive, then you'll want to have more. You should leave about 10-15% of your drive free.
dual 2.8GHz Mac Pro, Macbook Pro 2.16 GHz Mac OS X (10.5.6) 2 GB RAM
4feet4
Posts: 17
From: Pasadena
Registered: Mar 12, 2009
Re: System Overload ...i know ..I'm not the 1st ...
Posted: Aug 9, 2009 10:51 PM in response to: Larry Mal
I'm running LP8 - I have an IMAC OSX 10.5.5 - 2.4 processor - 4 GB RAM - M-Audio Fast Track Pro interface (USB direct to MAC) - I do NOT have an external hard drive ( sounds like I should ? - although I was told by others my system would be sufficient) - I use ALL instruments/track options ( midi etc) and will need to in the future - I want to be able to run a full music project 10-15 tracks. So far I'm running 4-5 tracks -(1) midi - the rest are audio with little to no effects ( in one project I'm using an LP8 template but deleted most of the tracks to cut down on the load ). Don't know if I can freeze these tracks-I'm new to this - thats why I'm looking for options ........ i was also using a 3rd party software in the project - Steinberg Groove Agent 3 (drums) but it was giving me the same error ..even when it was the ONLY track in the project....(its not fully compatible) - however I was finally able to create a full drum track with GA3 - play the midi data back - and record it to an audio track - therefore deleting the midi data I was having issues with and keeping the drums.... hope this helps?
Imac Mac OS X (10.5.5)
4feet4
Posts: 17
From: Pasadena
Registered: Mar 12, 2009
Re: System Overload ...i know ..I'm not the 1st ...
Posted: Aug 10, 2009 6:39 AM in response to: 4feet4
Updated
Imac Mac OS X (10.5.5) 2.4 Processor, 4 GB RAM, M-Audio Fast Track Pro Interface, No External HD
Larry Mal
Posts: 654
From: Saint Louis, Missouri
Registered: Sep 27, 2007
Re: System Overload ...i know ..I'm not the 1st ...
Posted: Aug 10, 2009 7:54 AM in response to: 4feet4
Perfect. Well here are some suggestions:
1) Logic 7, 8 and 9 all have a "freeze" function. Logic 9 has a new "bounce in place" function which I haven't used yet. These will make temporary audio files of your MIDI instruments so that you are able to play them as finished audio for the most part and free up CPU power. ( I haven't yet used "bounce in place", I just got Logic 9.) This will help with MIDI instruments quite a bit, and you can still go back and change them by un-freezing... I guess "thawing" would be the proper term.
2) The reason I was asking about your audio interface is because I was wondering what you had available. You very definitely want to record to a non-system (on that Logic nor your operating system are on) drive. Firewire is much superior to USB, which is why I'm glad to hear you are using USB as your audio in. By using Firewire in and Firewire out, on an iMac, you would be halving the bandwidth. In your case you are not.
You will add very much stability to your Logic work by adding an external Firewire drive and recording audio to it, and working on Logic projects there! If you have the money, I'd go with Firewire 800, which is frankly overkill, but why not. Firewire 400 drives will work fine for you. Add one and many of the overload messages will disappear, simply because right now you are pulling information from (in the form of calculating what the virtual instruments and Logic are doing) and writing information to (in the form of writing what those instruments and Logic are resulting in) to the same disk.
Try these two things and get back to us. I think you'll be very happy with the results.
It's also important to pay attention to your buffer size. When it is not important for you to play with it in real time, you want to make it be 1024. Otherwise as low as possible. So when you are recording audio to a MIDI drum track, you'd want it to be very low so you can play along accurately. When you have all that done, and are editing MIDI only, then put the buffer higher. When mixing, put it higher.
Let me know how this works, good luck, L
dual 2.8GHz Mac Pro, Macbook Pro 2.16 GHz Mac OS X (10.5.6) 2 GB RAM
4feet4
Posts: 17
From: Pasadena
Registered: Mar 12, 2009
Re: System Overload ...i know ..I'm not the 1st ...
Posted: Aug 10, 2009 9:10 AM in response to: Larry Mal
Ok Great - Thanks - makes sense - I was using a Lacie with Protools an my PC ( it recently crashed) - I was under the impression I would have enough processing power with out it on the MAC.
Looks like I can pick one up for just a little over $100 ( I'm rolling in that kind of cash) ... please clarify though - you stated: "Firewire is much superior to USB, which is why I'm glad to hear you are using USB as your audio in. By using Firewire in and Firewire out, on an iMac, you would be halving the bandwidth. In your case you are not" ....are you GLAD to hear I am using USB as in - We may have found the problem .... go external to free up processing ? Please confirm.
Thanks again
Imac Mac OS X (10.5.5) 2.4 Processor, 4 GB RAM, M-Audio Fast Track Pro Interface, No External HD
CCTM
Posts: 249
Registered: Mar 11, 2007
Re: System Overload ...i know ..I'm not the 1st ...
Posted: Aug 10, 2009 9:28 AM in response to: 4feet4
4feet4 wrote:
Ok Great - Thanks - makes sense - I was using a Lacie with Protools an my PC ( it recently crashed) - I was under the impression I would have enough processing power with out it on the MAC.
As stated in an earlier reply, if you only have 2 or 3 gigs of free space on your Mac hard drive, processing power is NOT the problem. Your boot disc is way too full. You should have at least 20-30GB free.
Running a second drive for the audio side will, of course, help, but you MUST clear out the main hard drive (or fit a larger one) before you run into even more serious problems.
HTH
CCT
Larry Mal
Posts: 654
From: Saint Louis, Missouri
Registered: Sep 27, 2007
Re: System Overload ...i know ..I'm not the 1st ...
Posted: Aug 10, 2009 9:37 AM in response to: 4feet4
Well, you have enough processing power, that isn't the issue. All the processing power in the world won't matter if you have 64 megabytes of RAM, there will be a bottleneck. Another bottleneck is with data transference. Like I said, when using a single drive to transfer date from as well as to- which is what you are doing when you are using Logic, running within the scope of the operating system, and hosting virtual instruments, all of which is writing the resulting audio information to the same drive, at the same time, then you are creating another problem. But you don't have to do that, by sending the audio written to another drive other than the one the audio is being generated from.
In other words, your processing power is both faster than and irrelevant to the physical limitations of the hard drive itself.
Another bottleneck would be if you were recording tracks on a Firewire in, and sending that to and external Firewire drive out. This is one of the limitations of the iMac, there is no way to add what is called another bus, which is simply another pipeline for data transference. You can get around that with a Mac Pro, in which you add another internal hard drive, which connects directly to the motherboard, and has its own bus. Or by adding another Firewire PCIe card, which will add another Firewire bus, again, with its own data transference. On an iMac, you have one Firewire bus, and one USB bus.
Clear? You can imagine these as pipes of water. The more pipes you have leading to and from a location the faster it will go.
USB, in your case, is a dedicated pipeline in. Nothing (well, your mouse, maybe a flash drive) is using that pipeline. Your Firewire is a pipeline out, in this case- you could reverse this, it doesn't matter*. If you use Firewire in and out, then you are sending water flowing in both directions in the same pipe. It will work, but not as well. By adding a dedicated bus, you would be adding another pipe to flow in one way, while the original flowed the other way. No impedances.
I don't see why you can't use the Lacie drive you already have, though. It's quite likely your crash wasn't due to it. No need to buy another drive, if it's Firewire, anyway. Just give it a shot- this isn't a cure all, but just good audio practice. Let me know how it pans out. Good luck, L
*Firewire is better than USB in all situations. But you seem to be going a track or two of USB audio in, so I'd use USB for that. For light use it's fine. Then you can use your superior Firewire bus to write the audio to the external Firewire drive.
dual 2.8GHz Mac Pro, Macbook Pro 2.16 GHz Mac OS X (10.5.6) 2 GB RAM
4feet4
Posts: 17
From: Pasadena
Registered: Mar 12, 2009
Re: System Overload ...i know ..I'm not the 1st ...
Posted: Aug 10, 2009 11:12 AM in response to: Larry Mal
L - Thanks for laying that out in simple terms - learning a ton and loving it ( when things work) - I will pick up another Lacie - my old Lacie for my PC crashed - I'm better off starting from scratch ( I'm still trying to retrive some data of the old one) ... I'll let you know how it works. I would have got an external drive outright but the Logic Certified guys at Apple told me I would not need one - sounds like this is the big problem. I'll use the freeze method when needed also....... maybe I'll have better luck with Groove Agent 3 with the external drive.
Much appreciated-
(TBD)
Imac Mac OS X (10.5.5) 2.4 Processor, 4 GB RAM, M-Audio Fast Track Pro Interface, No External HD
Larry Mal
Posts: 654
From: Saint Louis, Missouri
Registered: Sep 27, 2007
Re: System Overload ...i know ..I'm not the 1st ...
Posted: Aug 10, 2009 11:39 AM in response to: 4feet4
And free up some room on that system drive.
dual 2.8GHz Mac Pro, Macbook Pro 2.16 GHz Mac OS X (10.5.6) 2 GB RAM
Pancenter
Posts: 3,306
From: Southwest U.S.
Registered: Apr 22, 2007
Re: System Overload ...i know ..I'm not the 1st ...
Posted: Aug 10, 2009 12:04 PM in response to: 4feet4
4feet4 wrote:
L - Thanks for laying that out in simple terms - learning a ton and loving it ( when things work) - I will pick up another Lacie - my old Lacie for my PC crashed - I'm better off starting from scratch ( I'm still trying to retrive some data of the old one) ... I'll let you know how it works. I would have got an external drive outright but the Logic Certified guys at Apple told me I would not need one - sounds like this is the big problem. I'll use the freeze method when needed also....... maybe I'll have better luck with Groove Agent 3 with the external drive.
Groove Agent 3 loads samples into memory so I doubt if your luck will change.
The -first- thing I would do is clear some space on your hard drive, my feeling is that OSX is writing swap files and the drive head is working overtime to try and find free space to write. That in itself could cause an overload.
Free drive space now or expect more problems than you're currently experiencing.
pancenter-
Power Mac G5 1.8GHz Dual, 4GB RAM Mac OS X (10.5.5) RME Audio - MOTU MIDI, Mac (Logic 8.02), Intel/XP-Pro Quad Core PC

Logic error-hard drive too slow or system overload (new macbook!)

have made a few short tracks with logic with no probs. when i have tried to play the demo songs which have many tracks, i get an error msg saying hd too slow or system overload. i have a new macbook, 2.4, 2mb ram, 250 gb hd (with loads space left). airport turned off when using logic. what gives???

Samples that I am using are located on a 7200 external HD.
Is your external formatted for Mac? If you didn't buy it from a store that sells mac drives specifically, it's probably formatted for windows. You must reformat for Mac or you'll have a lot of performance issues.
I've a Macbook 2,2 Ghz Core 2 DUO with 2Go of RAM.
You should get more Ram, it's really cheap these days.
Airport is disconnected. My AUdio Buffer is 1024 in the Logic preferences.
Make sure the I/O Safety Buffer is OFF, and then set the buffer size at 256 or 512.

How to change availability date of a batch when doing GR for order in MIGO

Hi all,
We are not able to find any exit or BADI to change availability date of batch when doing goods receipt for a order.
Exits and BADIs are available for other dates but not for availabiliy date.
One Exit that is available for available date but is not triggered while doing GR for an order.
Please let me know how to achieve this.
Thanks and Regards,
Taranam

Hi,
You can use the remodelling here with the option " Replace Characteristics" with Customer exit. It will allow you to write an exit and change the value. Find more here:
http://www.scribd.com/doc/7882193/Remodeling-in-BI-70-Using-Customer-Exit
Thanks...
Shambhu

System overloaded, repeat immediately by batch when triggering event

Similar Messages

Maybe you are looking for