Latency issues with Logic

An area for people to discuss Scope related problems, issues, etc.

Moderators: valis, garyb

Post Reply
User avatar
paulrmartin
Posts: 2445
Joined: Sun May 20, 2001 4:00 pm
Location: Montreal, Canada

Post by paulrmartin »

I find myself with a lot of ASIO overflow errors when running many Audio tracks in Logic during final mixdowns. One way I have found to deal with this problem is to set my ULLI settings to the highest latency in Pulsar.

Does anyone have another solution?
I believe all my driver settings in Logic are optimal...

(Edit)
Maybe I should list my gear:

P III 933Mhz
512M of RAM
ASUS CUSL-2C MOBO i815 chipset
Win 98se(tweaked with help from the optimisation tips listed on this forum)
Pulsar2 (SFP)
_________________
Paul R. Martin

I think I may get the hang of this after all!

<font size=-1>[ This Message was edited by: paulrmartin on 2002-05-17 08:59 ]</font>
subhuman
Posts: 2573
Joined: Thu Mar 29, 2001 4:00 pm
Location: Galaxy Inside

Post by subhuman »

Do you have i815 chipset/IDE drivers installed?

Do you have DMA enabled or Intel Application Accelerator installed?

What speed is your harddisk?

How many channels are you able to play before you get clicks?

For reference, on the exact same system - CUSL2/933mhz, Pulsar1 card, I was able to run 38 channels, with room to spare, at 13ms. When I added a Luna2 card, I could run the whole thing at 7ms. With Logic.
subhuman
Posts: 2573
Joined: Thu Mar 29, 2001 4:00 pm
Location: Galaxy Inside

Post by subhuman »

Also what version of Logic are you using?

And what samplerate/bitdepth?
User avatar
paulrmartin
Posts: 2445
Joined: Sun May 20, 2001 4:00 pm
Location: Montreal, Canada

Post by paulrmartin »

Sorry about not listing my drives.
18 Gig SCSI HD, 10,000 RPM
60 Gig IDE drive used only to store samples.


I run Logic 5.1.2 now.

I don't get clicks, I get a full-stop and the overflow error window popping up.

Perhaps I need more SHARC's...
User avatar
paulrmartin
Posts: 2445
Joined: Sun May 20, 2001 4:00 pm
Location: Montreal, Canada

Post by paulrmartin »

Subhuman, Judging from what you wrote in your first answer, I'm not that far off. I am running a comparable number of tracks. And they DO run at 13ms. I am just trying to see if there is a way around having to change the latency. Maybe I'm just lazy...

<font size=-1>[ This Message was edited by: paulrmartin on 2002-05-17 09:32 ]</font>
summer
Posts: 54
Joined: Sun May 19, 2002 4:00 pm
Location: Berlin, Germany
Contact:

Post by summer »

I don't get it... I had the dropout problem on my p2-400mhz 128mb ramm And now I STILL have it even though I running p4-1.7ghz 512mb ram. all I have to do to get dropouts is to play some midi in logic. no waves beeing played from the HD nor did I have any plugins activated.??? and that's with the low (read: slow) ULLI setting. what's going on here?

Regs.
Summer

<font size=-1>[ This Message was edited by: summer on 2002-05-20 21:21 ]</font>
User avatar
garyb
Moderator
Posts: 23380
Joined: Sun Apr 15, 2001 4:00 pm
Location: ghetto by the sea

Post by garyb »

i don't have those probs w/ 4.81.......
i do have a pulsar1 so 13ms is the lowest latency i can use.i did have an 850mhz athlon which is now upgraded to a 1.8 gig p4. when i had the athlon, asio overflow was more likely,but it took 25 or more tracks and heavy native plug usage.(4 or more plugs avg per track and 5-7 busses w/ 2-3 plugs avg)since v3.0 and the p4,(about the same time)1-2 instances.since sfp,not once.
Tony B
Posts: 516
Joined: Tue Jan 15, 2002 4:00 pm
Contact:

Post by Tony B »

Tracks loaded previously seems to be retained in memory so it would appear to Logic that it is still handling all those tracks with various effects etc added up. A reboot is necessary to clear it up. I upgraded my sys and was getting some asio.
That was my remedy.
Post Reply