MOTU2408 mkii with project 5 audio issue

Have you tried setting latency very high, as an initial test? This is a good way to determine whether you just have a simple performance issue or not. Try a latency of several seconds (not milliseconds) and if the MOTU driver exposes this information double or quadruple your buffer size. If things sound better, see how low you can trim latency back before problems resume.

If you're familiar w/ computer recording and you feel your required latency is too high given the speed of your PC, then consider any other software services that might be running intermittently to slow things down and introduce this noise - i.e. network queries, scheduled antivirus events... even viruses themselves. Windows will get in the habit of juggling lots and lots of balls if left alone for too long. You've got to make a real effort to keep the environment lean.

Just an aside: I stopped using MOTU products (had a 2408 at one time) because I hated their drivers so much. So blaming MOTU as a last resort is not out of the question. You should post your system specs here, and also e-mail them to MOTU tech support.

P.P.S. Just noticed this: "tried every clock source in the studio"
Sounds scary - how many are there?? Step one is to eliminate as many as possible. See whether the PC and MOTU alone exhibit this problem, in the absence of any external timing slaves/masters. Then reintroduce variables until the problem recurrs.

I tried higher latency, but not that high. I will attempt that. My pc has had all the "optimize for audio" steps already. Maybe I will re-install P5. That is one thing I haven't done. Once I do that will my tunes be able to find all their stuff?

I can access the asio panel from p5 audio options. If I increase thebuffer to 2048 then the problem is mostly fixed. That gives me a whoppin 46 ms latency. If I bring the buffer to 1024 for 23 ms, the problem returns. I can't remember now, but I don't think the wdm's worked with p5. I won't be able to use it at 46 ms. Any ideas of where to go from here? background programs again? yee haaaw.


Thanks for the help.

al

Turns out that quicktime was loaded in memory, once I closed that and a browser extension that was also in memory, everything is back to normal. I can't remember if I updated quicktime while installing something else or what really happened...but now it works. Thanks for all the help folks.

back to piling guitar wails on a squeejaw bass line.

al