| Author
|
Overload problems!
|
chillaca
IsraTrance Junior Member
Started Topics :
16
Posts :
19
Posted : Apr 24, 2005 07:50
|
Hi Guys,
so, I´ve been looking for in the search about the Overload Topic, but all what I´ve found, don´t answer my question, so:
I´m having to much troubles with overload in Logic (5.0.1), it says something like "ASIO overload: the audio engine was not able to process...", so, I´d like to know sure, what could be the real solution for this...faster Ram memory, better and bigger HD, better Logic version, better processor chip, I really don´t know, but I suspect about the Ram Memory.
The Logic not even want to play my traxx anymore, I can´t let just one VST opened and it crashes,stop to playback and just restarting the computer to back to life.
PS: Athlon 1700 XP
256 Mb DDR
20 GB Maxtor
M-Audio Ozone, ( soundcard included )
Logic 5.0.1
Thanxx anyway
Chillaca
Trying, Aliving and Learning |
|
|
dma
IsraTrance Junior Member
Started Topics :
18
Posts :
93
Posted : Apr 24, 2005 14:37
|
mate,im with u on this one!!!!
i run logic pro 7.0.1 on a duell 1.8 g5 with 1 gig of ram and 160 gig hard drive....and i still get that fucken error message!!
i think a lot of these stability problems should be resolved in 7.1...that;'s what apple sais anyway,but i guess this wont help u if u run a pc!!
.....here's some info mate...
I/O Buffer Size
This parameter determines the size of the buffer used by the audio hardware—for both input and output. Options range from 1024 down to 32 samples. The smaller the buffer size, the less “latency” you will encounter when monitoring while recording, or using software instruments. Note: There may be a point where the selected I/O Buffer Size is too small for your system, and begins to affect playback. This usually takes the form of clicks, pops, and crackles. You should therefore aim for the lowest possible I/O Buffer Size value that doesn’t introduce these types of artefacts. As this parameter value is reduced, it places a higher strain on the CPU(s) of the system. On current model Macs, you should be able to reduce this value down to its minimum value. As a word of advice, if you find a higher (larger) I/O Buffer Size setting provides suitably low latency during record monitoring and software instrument playback, you should use it. This will minimize the impact on the CPU(s) of your system.
Larger Disc Buffer
This option influences the amount of audio data that is read from the disk in advance. This option is switched off by default, matching the demands of fast hard drives and powerful computers. If you encounter frequent error messages while running Logic in this mode, you should switch this setting on. This will allow you to play back more tracks, achieving higher reliability. Please note that RAM requirements are increased if this option is active.
i tried these thing's and i didnt notice much difference,so it;s got me stuffed....good luck |
|
|
|
UnderTow
Started Topics :
9
Posts :
1448
Posted : Apr 24, 2005 16:31
|
chillaca, Whatever else you do, I would upgrade your memory. 256MB really isn't enough to run a heavy music application like Logic. I would advise having 1Gig of ram.
The harddisk shouldn't be the issue as ASIO doesn't talk directly to your harddisk. Of course, if you can afford it, it is always nice to have a bigger disk. 
You can't upgrade Logic on the PC because PCs arn't supported anymore. If you want more functions you either need to change sequencer or switch to a Mac where you can get a newer version of Logic.
One thing you can try is to increase your audio latency. That should put less strain on your ASIO drivers and CPU. And always check if there are new drivers for your soundcard at M-Audio's website when you run into problems.
UnderTow
|
|
|
|
index
IsraTrance Junior Member
Started Topics :
36
Posts :
548
Posted : Apr 24, 2005 17:58
|
Quote:
|
On 2005-04-24 14:37, dma wrote:
mate,im with u on this one!!!!
i run logic pro 7.0.1 on a duell 1.8 g5 with 1 gig of ram and 160 gig hard drive....and i still get that fucken error message!!
|
|
I mixdown all the time into 5.0 with P4 1,8 and 1024 ddr and where the mix is heard almost cool :
with 6-7 good fx plug ins,
40 audio automated tracks used
No instruments plugged
(total .LSO size 2.5+ mb)
Is your enviroment as heavy as before u upgrated to the Dual G5?
I was thinkin buying a mac only for Logic,but if it cant control totally cpu s
and get that msg,there is no reason to do it.
I ve made a post about "this is not a logic 5 song" msg.
Please response |
|
|
|
chillaca
IsraTrance Junior Member
Started Topics :
16
Posts :
19
Posted : Apr 25, 2005 02:00
|
Hi dudes,
I´ll do your suggestions and I hope that it gets better, I think that you´re right but I don´t know how to change my buffer size in numbers, just clicking to turn on or off...
Thanxx
|
|
|
|
dma
IsraTrance Junior Member
Started Topics :
18
Posts :
93
Posted : Apr 25, 2005 02:51
|
ana3imandros....this is the first time i run under logic,used to use cubase!!!
i must say that i would never go back and that logic is so simple and effective,brilliant layout and tools,heaps of plug's...
i didnt get the error mesage very often before i upgraded to 7.0.1......it seemed fine when it was just 7.0.0...
the performance of a duell g5 is very noticble,that is it's really good!!
i do run like heaps of plug's,well basicly i use only plugs
so in my latest track i am running 29 instances of fx,eg...reverb,compressers,limiters,delays,phaser etc over 20 tracks with some being automated
the synth are
1 rmlv multi channel
2 vanguard
4 albino's
1 es1
im using 7 buses,
t racks full suite on the master and space designer on another bus
now this will run fine,aslong as u dont have to many windows up and synth's open,whilst u are editing and stoping and starting...thats when the audio engine seems to lag and then crash,it;s very temprimental
as for youre song i really dont have any ideas cause ive never xperinced this before ...im sorry
well with a bit of luck it will be fixed in 7.1
and dood go buy a mac,youle love it,i would advise to go for the duell 2.6
.... |
|
|
|
chillaca
IsraTrance Junior Member
Started Topics :
16
Posts :
19
Posted : Apr 25, 2005 05:37
|
hi dma....
for sure I´ll buy a Mac when I can, I love them and I had never one before, but they´re nice and smooth
Luck!!@
Thanxx for the advices
Chillaca |
|
|
|
ben
IsraTrance Junior Member
Started Topics :
16
Posts :
108
Posted : Apr 25, 2005 19:30
|
another thing u could do is bypass all ur fx and vsts, and record all ur synths to audio... it's a pain, kills the flow but there is no other way considering the pc u have...
start with a bass.. record it.. then kick--> record it, etc...
also as undertow said u need more ram...
i used to have 256 and Pentium3 like u and was having a lot of troubles, i could only use like 5 or 6 vsts with fx until it crashed...
then i got a P4 with 1 gig of ram, and now on this last track i got the asio error message when running 17 vsts and about 35 fx.... so it really helps...
another thing u can do is turn off all the pgms u don't need when u make music... turn off the internet, adn anything u don't absolutely need... |
|
|
|
UnderTow
Started Topics :
9
Posts :
1448
Posted : Apr 25, 2005 20:22
|
Quote:
|
On 2005-04-25 02:51, dma wrote:
and dood go buy a mac,youle love it,i would advise to go for the duell 2.6
....
|
|
Obviously if you upgraded from a slow PC to a dual CPU G5 things will be much faster and smoother. But for much less money you could get a dual Xeon or dual Opteron PC that will be just as smooth and fast AND leave change for a UAD-1 and/or powercore DSP card ...
UnderTow |
|
|
|
Aldus B
IsraTrance Junior Member
Started Topics :
10
Posts :
140
Posted : May 15, 2005 09:01
|
|
I think he would probably regret that. Another windows box is not the solution. Get a mac, 2 gigs of ram from crucial or macramdirect and a newer version of logic. Once you have that, freeze tracks whenever you need to and you should never get that error message again. |
|
|
|
Colin OOOD
Moderator
Started Topics :
95
Posts :
5380
Posted : May 17, 2005 02:56
|
|
mubali
Mubali
Started Topics :
71
Posts :
2219
Posted : May 18, 2005 21:26
|
Honestly this is an issue that I have as well. I run logic 5.5 on a 3.06 P4 processor with a gig of ram... My issue comes from the processor overheating (I am using a laptop) but as much as you don't want to, I would suggest bouncing all of your synthlines (leave your kick /bass and drums in midi) and applying the effects to the audio file of the synths.
When I first started having to bounce everything, I really disliked it, but once you get yourself into the routine of making something and then bouncing it, you find that you can make sometimes more complex stuff without having to worry that you are overloading your computer with a multitude of soft synths and fx...
Another thing to keep in mind is using an 3rd party audio editor for all fx that aren't delay or reverb. This will allow you to add some of those more complex fx chains without maxing the cpu in your unit. If you are planning on doing automation on your fx though, doing it in the sequencer is still the best bet...
Most of the time I will lay down the kick and bassline first, and spend a day or two making a whole bunch of random synthlines that might work with that combination. From there once you are arranging the track, it will be a bit easier to hear what you are missing from the soundscape and add in the parts as needed.
Recording vsts to audio really makes you establish a bit of permanency to each part you write. When I first got into writing music, most of the parts I wrote in midi in the beginning would get changed toward the middle or end of the song... This would basically make me take 2 steps back just to take one step forward. Now, I really pay close attention to each synth line as I am writing it and if it doesn't sound like it will work, I won't record it.... Or I will record it and not use it in the song.
If you write a whole bunch of synth lines and find that it doesn't really work for the track, you can always load those synth lines into Ableton Live and use those to add more layers onto a live set without having to worry about programming the vst that you used... Gives you more room to try other things with the processor you save..
 An Eagle may soar, but Weasels don't get sucked into jet engines. |
|
|
|
|
