I went ahead lowered the safety buffer from 256 to 64 to see if that helps like it has you. Lowering that number does improve latency and the total round trip msec. The tech at MOTU suggested to raise those numbers. So in your system did you definitely see an improvement with lowering the safety buffer? I agree it’s counter-intuitive, yet if it works, then it works.

I just think it seems to work better with certain *combinations* of buffer/safety. This may well be different for different PCs etc, but it's certainly worth playing around with.
 
I guess it's worth trying the MOTU on each of your USB ports too, and try to unload everythign you possibly can from Windows - until you find the culprit.
 

I've done quite a lot of testing and the problem may be solved, since it's been a good while since I got the crackles. I think it was most likely my USB backup HD's that were connected.
 
Jim Roseberry said all those UDB HD's have a sleep mode built-in that you can't program to turn off and sometimes when you record audio to your internal audio HD, it first checks to see if all other HD's are awake, if not that can create a data flow interruption and thus a crackle. No doubt the Ultralite seems pretty finicky when it comes to USB devices. I also disabled Defender, who knows, may that was it. If I get any more crackles I'll post here. 
 
 

I have external USB backup drives too - and I always leave them disconnected, except when I'm backing up to them ;-)
I have a few USB connecterson the fromn of my PC case, so I have the cable sitting right there, and whack it in when I need it. This way I can't screw up anything on the backup drive - because it's not connected.
 
So the moral is - it sounds like a good idea to disconnect these anyway! ;-)
 
I'm glad to hear it's (hopefully) fixed! ;-)

jbraner
I have external USB backup drives too - and I always leave them disconnected, except when I'm backing up to them ;-)
I have a few USB connecterson the fromn of my PC case, so I have the cable sitting right there, and whack it in when I need it. This way I can't screw up anything on the backup drive - because it's not connected.
 
So the moral is - it sounds like a good idea to disconnect these anyway! ;-)
 
I'm glad to hear it's (hopefully) fixed! ;-)

Actually at one time I was very good about keeping the backup HD's disconnected. Mostly because I thought maybe a intense power surge from a lightning strike or something could fry the computer and maybe even the USB HD's connected.
 
Then I guess I got complacent and liked the convenience of accessing those HD's when I'm downstairs using my internet computer and remote desktop.
 
So you're right this is a very good idea for several reasons. I still wonder why Windows 10 wants to wake up HD's that are not being used before writing to my audio HD. To me that seems weird. Why not let the suckers sleep and wake them up wen you need them?
 
Like you suggested, I have been using 64 for safety buffer. And using 256 for buffer setting. Can you tell me what setting you have for buffers? I know you said 64 for safety buffer was better for your system.
 
With the 256 64 setting I get 19 msec total round-trip. For a very long time I had been using 128 128 which gave me 12 msec total round trip. Since I'm a keyboard player I like to keep the latency as low as I can.
 
Every time I got the crackles embedded in the wav file, I was working at low loads, sometimes 1 audio track and no midi tracks, little or no FX. So I’m not sure if the buffer settings could help in this situation, but I'm trying it.

An update. Have not had the problem since last post. I have turned off internet connection and don’t allow even the test for new updates to happen. So far, so good.

Like you suggested, I have been using 64 for safety buffer. And using 256 for buffer setting. Can you tell me what setting you have for buffers? I know you said 64 for safety buffer was better for your system.

I use 128/48 - that gives 10.2ms RTL.
I like to try 64/48 (5.8ms) when I'm tracking guitars and that works if there aren't too many amp sims in use, but 128/48 is always OK.
Then when I'm mixing and have lots of plugins loaded, I go up to buffers of 256 or even 512 because it doesn't matter.

If I said I use safety buffers = 64, that will have been a brain fart (it happens) 😄
Safety buffers = 16 usually works OK too, but I usually leave it at 48.

LLyons
An update. Have not had the problem since last post. I have turned off internet connection and don’t allow even the test for new updates to happen. So far, so good.

So if I understand you correctly. Did you install the latest WUP and then disconnected from the internet? And now everything is working fine?
 
If that's what's happening then it reminds me of what happened last Dec where a WUP messed up many of our computers when running Plat. If I reverted back to an old image file, it would work fine for about 20-30 min then something form the internet corrupted my system and I'd get the errors. As long as I stayed disconnected form the internet, everything worked fine.
 
I found out the MS does do some silent updates without informing us they're doing it. Back then I turned off lots of MS apps that were updating in secret.
 
I wish I knew of a program that would monitor my computer and let me know if an installed program is accessing the internet or sending data. Or if some website is sending a message or data or updates to my computer all without me knowing or giving permission.

jbraner

Like you suggested, I have been using 64 for safety buffer. And using 256 for buffer setting. Can you tell me what setting you have for buffers? I know you said 64 for safety buffer was better for your system.

 
I use 128/48 - that gives 10.2ms RTL.
I like to try 64/48 (5.8ms) when I'm tracking guitars and that works if there aren't too many amp sims in use, but 128/48 is always OK.
Then when I'm mixing and have lots of plugins loaded, I go up to buffers of 256 or even 512 because it doesn't matter.
 
If I said I use safety buffers = 64, that will have been a brain fart (it happens) 😄
Safety buffers = 16 usually works OK too, but I usually leave it at 48.

 
 
So do you use 64/48 because you're using real time FX and they don’t sound right at higher latencies? Do you get crackles? So why do you use 256 or 512 for buffers? Do you get dropouts or crackles if you don’t raise the buffers in a heavy load situation?

gmp

jbraner

Like you suggested, I have been using 64 for safety buffer. And using 256 for buffer setting. Can you tell me what setting you have for buffers? I know you said 64 for safety buffer was better for your system.

I use 128/48 - that gives 10.2ms RTL.
I like to try 64/48 (5.8ms) when I'm tracking guitars and that works if there aren't too many amp sims in use, but 128/48 is always OK.
Then when I'm mixing and have lots of plugins loaded, I go up to buffers of 256 or even 512 because it doesn't matter.

If I said I use safety buffers = 64, that will have been a brain fart (it happens) 😄
Safety buffers = 16 usually works OK too, but I usually leave it at 48.

So do you use 64/48 because you're using real time FX and they don’t sound right at higher latencies? Do you get crackles?

I like the lower latency if possible. Sometimes with my headphones on, I can hear the difference between hitting a string, and the sound coming in to the headphones.
(BTW - I'm not sure if this is caused by PDC for my amp sims etc, rather than the latency caused by the MOTU)
If I have 5 or 6 tracks running amp(and speaker) sims, I start to get crackles at 64/48.
 
 

So why do you use 256 or 512 for buffers? Do you get dropouts or crackles if you don’t raise the buffers in a heavy load situation?

Because, when I'm mixing, I start to load up some reverbs and lots of eq/compressor etc plugins. This brings up CPU usage on my 5 year old PC, so I get "hifg CPU" crackles ;-)
It (buffer settings and latency) doesn't matter when you're mixing - only when you're playing a KB or guitar etc.
 

jbraner

gmp

jbraner

Like you suggested, I have been using 64 for safety buffer. And using 256 for buffer setting. Can you tell me what setting you have for buffers? I know you said 64 for safety buffer was better for your system.

I use 128/48 - that gives 10.2ms RTL.
I like to try 64/48 (5.8ms) when I'm tracking guitars and that works if there aren't too many amp sims in use, but 128/48 is always OK.
Then when I'm mixing and have lots of plugins loaded, I go up to buffers of 256 or even 512 because it doesn't matter.

If I said I use safety buffers = 64, that will have been a brain fart (it happens) 😄
Safety buffers = 16 usually works OK too, but I usually leave it at 48.

So do you use 64/48 because you're using real time FX and they don’t sound right at higher latencies? Do you get crackles?

I like the lower latency if possible. Sometimes with my headphones on, I can hear the difference between hitting a string, and the sound coming in to the headphones.
(BTW - I'm not sure if this is caused by PDC for my amp sims etc, rather than the latency caused by the MOTU)
If I have 5 or 6 tracks running amp(and speaker) sims, I start to get crackles at 64/48.
 
 

So why do you use 256 or 512 for buffers? Do you get dropouts or crackles if you don’t raise the buffers in a heavy load situation?

Because, when I'm mixing, I start to load up some reverbs and lots of eq/compressor etc plugins. This brings up CPU usage on my 5 year old PC, so I get "hifg CPU" crackles ;-)
It (buffer settings and latency) doesn't matter when you're mixing - only when you're playing a KB or guitar etc.
 

Thanks what you said makes sense. I don't like the input monitoring in Sonar, because it does sound weird at times. I suppose because of the latency. It may be that you have to use it if you have FX on that track which you need to hear in real time.
 
All of my analog inputs first go into my analog recording console, I route them with busses to the AVB and then Plat, back to the AVB analog outs and back into my analog mixer. I do all my input monitoring using the routing and mixer settings inside the AVB box.
 
It's  a pretty complicated routing and mixer setup, but yet the basic idea is fairly simple. I use the Aux sends to route the input signal on the Analog 1 input to the Analog 1 output and do this for all inputs. If you're interested in this, I don't mind sending you my Device Preset and my personal notes on how it works.