arghhhhhhhhhargh

Hey experts,

I've had a frustrating couple days with project5. See, I got a new bunch of equipment, hoping it would take care of this issue but it has not. :( Im turning to this wonderful friendly forum out of desperation.

When using P5, often (especially when I have ANY audio clips) my system will get VERY sluggish, my mouse will get all slow motion, and things will crap out. This is with ASIO, latency doesnt seem to help. I believe it also does this using WDM. Things that trigger the slow death: changing patches, rewinding, doing almost any real time stuff when measure looping. Also, sometimes even when not doing anything, the sound will go SCREEEEEE for a millisecond and then continue. Basic crappiness.

I dont recall this ever being an issue with 1.5. Sad to say that 2.0 just hasnt lived up to its potential for me so far. Has anyone else experienced this?

And just for reference, Ableton 5 (I know I know) runs smoother than a preemee newborns oiled backside, I can do all sorts of scary things and it doesnt hiccup.

system: Athlon64 3000+, 1 gig ram, Presonus firebox, several hard drives but my system drive is a raptor 10000 rpm. I have installed a fairly barebones windows partition, and followed the optimization guide found around the web (background priority, etc)

If this cant get fixed its gonna have to be the dark side for this padewan. :P

thanks,

Eric

This sounds like something i've been experiencing with version 2.0. For no reason, when you load a project up it will start playing in a stuttery slow motion. I found that altering the latency will stop this happening, but what's even stranger is that moving it lower from 40ms to 20ms will cure it or sometimes vice versa. I have an Audigy card so maybe it's a bug involving that particular card.

Definitely sounds like some sort of driver issue with your audio interface. double check and see if it is like that with wdm also. Maybe try out the free asio4all drivers too.

Hey all,

Knowted, Im doubting its tied to the firebox since the problems started before the firebox. Blipp, I also had an audigy and that is why I thought it would get better when I got a new card. I dont have much else on my computer, I DO have a wireless PCI card, I wondered if that might be generating interrupts or some garbage like that. And I have an Nvidia video card. Im guessing lotsof people have those without issues however.

Let me try some more combinations of latancy and driver method, maybe theres something I can find that doesnt do it.

Agincourt, I know what you mean about firewire troubles.. I once had a laptop interface that would NOT read above 128 gigs on my external 200 gig drive, it just would not read those sectors and copying stuff would fail after it got to 128 gigs full :) But when I plugged the drive in via USB2 it was fine. And the same drive works no prob on another firewire interface :P Back to the original point, Im not sure if reinstalling will fix tho, I already did that when I built my stripped-down OS and it still does it. Theres practically nothing else installed. But thats a good Iidea I can try a different firewire port or take out anything else I can thing of that might be interfering.

My machine parts are as follows (maybe some one else with a same part will have this problem and same hardware): MSI Neo Platinum (nforce 350?) mb, Athlon64 3000+, 2x512 ddr2 ram, Dlink G510 wireless card, logitech cordless desktop, XFX Geforce 6800. 3 hard drives, 1 serial ATA rand 2 older IDE drives.

my guess too!

My machine parts are as follows (maybe some one else with a same part will have this problem and same hardware): MSI Neo Platinum (nforce 350?) mb, Athlon64 3000+, 2x512 ddr2 ram, Dlink G510 wireless card, logitech cordless desktop, XFX Geforce 6800. 3 hard drives, 1 serial ATA rand 2 older IDE drives.

I'm not terribly fond of wireless keyboards for DAW work. You might want to find a good 'ol PS2 keyboard and plug it in along with your other troubleshooting.

As a Linux geek, I have seen MANY troubling things go on between dlink wireless interfaces and nforce chipsets. Seems as though they don't like each other much. Linux geeks tend to be up on their hardware, the wrong comination of stuff and your system just comes to a screeching halt.

You mentioned above about installing a minimal Windows partition. What did you mean, PARTITION?? Does this mean somehow you're dual-booting another OS on another partition??? I'm just not sure why you would use that word. Sorry if I'm being nit-picky, but that threw up a red flag for me. Mind you, I'm taking shots in the dark here.

BTW, thanks for the system specs. We (as in the forum) can at least take a stab at an intelligent response when you provide those. You wouldn't believe how many posts that come up where we're constantly asking for specs just so we can take a guess.

Hope you get this figured out, looks like you've got a nice box...

WC

ORIGINAL: wgcabp

I'm not terribly fond of wireless keyboards for DAW work. You might want to find a good 'ol PS2 keyboard and plug it in along with your other troubleshooting.


Hope you get this figured out, looks like you've got a nice box...

WC

not in my case. I'm typing this from my logitech wireless keyboard and no problems at all, with my wireless mouse either. And yeah, hope you get it sorted!

DRILL A HOLE!