clicks and clock adjustment too large

Mike56 · Mar 1, 2025

I have used REW successfully in the past, am of limited knowledge and recently changed computers.
This is to measure and create filters for my MiniDSP Flex, using UMIK 1.
The old (microsoft surface on windows 10) works fine, the new (vivobook on windows 11) produces a few clicks and pops on each sweep and frequently displays "clock adjustment too large"
I think i am using identical settings and all the hardware is identical apart from the laptops.
I have spent hours checking threads and solutions but not found the problem.
All ideas most welcome please, for a not very knowledgeable user.

John Mulcahy · Mar 1, 2025

This thread has some tips. A recent Windows 11 update has also been reported as causing problems with USB audio output. Make sure you use the device names that start "EXCL" to access the WASAPI Exclusive drivers.

Mike56 · Mar 2, 2025

Thanks so much for that feedback John, frustrating isn't it? new computer= new problems not better results!
I immediately tried three things, switched off WIFI and Bluetooth, maximum buffer, all in exclusive choice of devices. unfortunately the result is the same, occasionally a sweep without audible clicks and no clock warning.
I have read the rest and don't understand much! - but i will keep looking
Thanks again
Mike

Mike56 · Mar 2, 2025

This is the only output device that runs a clean sweep, everything else crackles to a lesser or greater degree, and this is the computer speakers, all ideas welcome!

John Mulcahy · Mar 2, 2025

Although unrelated to your problem, it isn't a good idea to use such a large input device buffer. 16k is usually fine. The LatencyMon tool linked in that other thread can help diagnose what is causing the dropouts that produce the clicks.

Mike56 · Mar 2, 2025

Not sure i will master that, its a bit complicated for me! - but i shall take a look and see thanks

Mike56 · Monday at 11:57 AM

Thanks again John for your previous attention, its much appreciated, particularly as its nothing to do with your program which has always worked just fine!
i surprised myself and ran the latencyMon tool successfully, twice. First time it quite quickly decided the system was inadequate and recommended a solution which i googled on and disabled the power saving throttling mode in control panel, it ran a bit longer second time which is the screenshot attached. I tried some REW measurements for intersest and found half of them would run woithout warning boxes, not great but perhaps an improvement. Nevertheless i am now stumped again as i am not sure about disabling throttling in BIOS successfully.........
(whilst i was there i reduced the buffer again, thanks)

John Mulcahy · Monday at 3:05 PM

If you have already gone into System - Power and battery and selected Best performance as the power mode that's probably all you can do. The BIOS includes thermal throttling to prevent the CPU from overheating, disabling that risks hardware damage. There's much more on the various kinds of throttling here.

Mike56 · Tuesday at 2:14 AM

Another good read thanks John.
continuing to read and think, i guess the next best thing as a simple user might be to give the activities priority in CPU usage in device manager which is suggested to be simple.
I am not yet sure what i am looking for to make my Flex and its operating drivers have the priority it needs, but will keep going on that route.
Is this caused by using the Flex's new driver perhaps?
Underlying this is a reason why my old MS surface with i7 works fine and my new Vivobook with i9 wont. i just need to find and fix it, it should be an easy load! its not unreasonable to play music (and REW) down a USB these days!

John Mulcahy · Tuesday at 3:49 AM

Could be the Windows bug.

Mike56 · Tuesday at 10:31 AM

Could be the windows bug indeed.
However.........
Meanwhile i reset the priority of Mini DSP and REW in CPU management and got a bug free report and operation as attached.
However, switch off and start again and it doesn't seem to retain the changed priority, so if i could solve that, maybe i would be close!
I don't know what else might be involved in music playing that i should add to the list.

Mike56 · Tuesday at 10:45 AM

I see there is a way to set the affinity so it stays on one core with nothing else, but not certain about that!
M

John Mulcahy · Tuesday at 12:37 PM

You can try editing the target of the REW shortcut (right click on it) to:

"C:\Windows\System32\cmd.exe" /c start /high "current REW path"

where "current REW path" is the target before you start editing it.

Mike56 · Wednesday at 2:12 AM

Thanks for that suggestion John, i haven't made that work, but looking it up i find this; which i shall try later. i perceive it does the same thing.
I have a desktop shortcut for both Mini DSP device console and REW so hope i can execute that for both and have a permanent solution.

phofman · Thursday at 12:40 AM

It looks MS messed up something around their USB stack, breaking flow of isochronous transmissions (people seem to complain about webcams etc.). Probably just a temporary situation, it is a major issue as modern motherboards increasingly use onboard USB audio instead of HDA.

Mike56 · Thursday at 1:50 AM

Interesting, although i didn't set out to learn anything about how computers work it will be satisfying if (with all this outside help!! - thanks again) i can resolve this, there are still a few bits i feel ill at ease about in the settings. Is the proposed command line a replacement for the one the computer adopted on installation? Although i can see how to set affinity and priority i am not sure what to set them to! - priority maybe High, affinity no idea.
I am not interested to run anything else when i use REW or play music, i just want them perfect.

Mike56 · Thursday at 1:51 AM

And yes, i would have thought that folk would have complained their audio was inconsistent, or is it only me, playing it through the Mini DSP driver that causes the problem?

Mike56 · Thursday at 2:03 AM

Definitely a bit more to comprehend about
1. exactly what i will put into the shortcut path box in comparison with what is already there
2. where i set priority after that
3. where i set affinity and to what, if it matters.
4. understanding resetting the icon

Mike56 · Thursday at 3:31 AM

First look, there is no .exe file.....i guess it will be one of the others!

John Mulcahy · Thursday at 3:35 AM

You don't need to do anything with the miniDSP code, the driver already runs at very high priority. Ignore affinity.

Mike56 · Thursday at 4:07 AM

Thanks John, so now i am puzzled again, (which isnt difficult) it was changing the priority of miniDSp here below that got things working, but it reverts always, i was now looking to make that permanent with the shortcut?

John Mulcahy · Thursday at 4:22 AM

Odd, drivers should run at much higher priority. I'll let miniDSP know.

Mike56 · Thursday at 4:28 AM

That would be great if they did it with the driver so i don't have to understand code changes!
M

clicks and clock adjustment too large

Registered

REW Author

Registered

Registered

Attachments

REW Author

Registered

Registered

Attachments

REW Author

Registered

REW Author

Registered

Attachments

Registered

REW Author

Registered

Attachments

Member

Registered

Registered

Registered

Registered

REW Author

Registered

Attachments

REW Author

Registered

Popular tags