MOTU 828x, Drivers, and Windows 10

Moderator: James Steele

Forum rules
Discussion related to installation, configuration and use of MOTU hardware such as MIDI interfaces, audio interfaces, etc. with Windows
Post Reply
tedpiecemcnugent
Posts: 4
Joined: Thu Apr 18, 2019 10:46 pm
Primary DAW OS: Windows

MOTU 828x, Drivers, and Windows 10

Post by tedpiecemcnugent »

Is MOTU ever going to update their drivers for Windows 10 combatibilty? The last update was back in 2015 and it's almost mid 2019. My 828x is becoming useless due to all of the pops and crackles. I've also tried Terry's Voicemeeter workaround, but no luck.
User avatar
terrybritton
Posts: 1117
Joined: Thu Jun 04, 2015 8:45 am
Primary DAW OS: Windows
Location: Elizabeth City, NC
Contact:

Re: MOTU 828x, Drivers, and Windows 10

Post by terrybritton »

Even though you have tried the Voicemeeter trick and presumably the trick of turning off the MOTU Audio Wave for 64 Bit or whatever they call their Windows drivers for that thing, don't stop there. Make sure every Windows Playback device and Recording device is set to the same sample rate in their "Advanced" tab of the Sounds control panel, and use "View/Show hidden" in the device manager and remove any lingering instances (greyed out) of the drivers sitting in the top section, "Audio inputs and outputs". Also, raise your buffer until clicks stop to see if something in the CPU is causing this - some internal DPC latency situation may still be lurking.
https://www.resplendence.com/latencymon

I have an Ultralite mk3 hybrid with equally ancient drivers and it works fine if I follow through with all the necessary protocols.

Terry
Computer: Sweetwater CS400v7 Intel Core i7-10700K CPU @ 3.80GHz | 64Gigs RAM | Windows 11 Pro x64 |
MOTU 828 mk3 hybrid

DAWs & Live: MOTU Digital Performer 11.31 | Cantabile Performer 4
Keyboard Synths: Kawai K5000s, Korg Wavestation
Controllers: NI Komplete Kontrol S-88 Mk3 & S-49 Mk2; Maschine Mk3 & JAM;
Akai MPK249 & 225, Alesis QX49, Behringer BCF2000 & FCB1010
Rack Modules: Ensoniq ESQm, Yamaha TX81Z, Wavestation SR

Tutorials: https://youtube.com/@CreatorsMediaTools
tedpiecemcnugent
Posts: 4
Joined: Thu Apr 18, 2019 10:46 pm
Primary DAW OS: Windows

Re: MOTU 828x, Drivers, and Windows 10

Post by tedpiecemcnugent »

Here are the stats from LatencyMon:

CONCLUSION
_________________________________________________________________________________________________________
Your system appears to be suitable for handling real-time audio and other tasks without dropouts.
LatencyMon has been analyzing your system for 0:11:51 (h:mm:ss) on processors 0,1,2,3,4,5,6 and 7.


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: CRISTIAN-PC
OS version: Windows 10 , 10.0, build: 17763 (x64)
Hardware: MS-7C02, Micro-Star International Co., Ltd, B450 TOMAHAWK (MS-7C02)
CPU: AuthenticAMD AMD Ryzen 7 2700X Eight-Core Processor
Logical processors: 16
Processor groups: 1
RAM: 16334 MB total


_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 3693 MHz

Note: reported execution times may be calculated based on a fixed reported CPU speed. Disable variable speed settings like Intel Speed Step and AMD Cool N Quiet in the BIOS setup for more accurate results.

WARNING: the CPU speed that was measured is only a fraction of the CPU speed reported. Your CPUs may be throttled back due to variable speed settings and thermal issues. It is suggested that you run a utility which reports your actual CPU frequency and temperature.



_________________________________________________________________________________________________________
MEASURED INTERRUPT TO USER PROCESS LATENCIES
_________________________________________________________________________________________________________
The interrupt to process latency reflects the measured interval that a usermode process needed to respond to a hardware request from the moment the interrupt service routine started execution. This includes the scheduling and execution of a DPC routine, the signaling of an event and the waking up of a usermode thread from an idle wait state in response to that event.

Highest measured interrupt to process latency (µs): 79.10
Average measured interrupt to process latency (µs): 5.307458

Highest measured interrupt to DPC latency (µs): 76.40
Average measured interrupt to DPC latency (µs): 3.127009


_________________________________________________________________________________________________________
REPORTED ISRs
_________________________________________________________________________________________________________
Interrupt service routines are routines installed by the OS and device drivers that execute in response to a hardware interrupt signal.

Highest ISR routine execution time (µs): 16.561332
Driver with highest ISR routine execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation

Highest reported total ISR routine time (%): 0.000179
Driver with highest ISR total time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation

Total time spent in ISRs (%) 0.000179

ISR count (execution time <250 µs): 24317
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-999 µs): 0
ISR count (execution time 1000-1999 µs): 0
ISR count (execution time 2000-3999 µs): 0
ISR count (execution time >=4000 µs): 0


_________________________________________________________________________________________________________
REPORTED DPCs
_________________________________________________________________________________________________________
DPC routines are part of the interrupt servicing dispatch mechanism and disable the possibility for a process to utilize the CPU while it is interrupted until the DPC has finished execution.

Highest DPC routine execution time (µs): 297.142161
Driver with highest DPC routine execution time: ntoskrnl.exe - NT Kernel & System, Microsoft Corporation

Highest reported total DPC routine time (%): 0.003569
Driver with highest DPC total execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation

Total time spent in DPCs (%) 0.012062

DPC count (execution time <250 µs): 329504
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 1
DPC count (execution time 1000-1999 µs): 0
DPC count (execution time 2000-3999 µs): 0
DPC count (execution time >=4000 µs): 0


_________________________________________________________________________________________________________
REPORTED HARD PAGEFAULTS
_________________________________________________________________________________________________________
Hard pagefaults are events that get triggered by making use of virtual memory that is not resident in RAM but backed by a memory mapped file on disk. The process of resolving the hard pagefault requires reading in the memory from disk while the process is interrupted and blocked from execution.

NOTE: some processes were hit by hard pagefaults. If these were programs producing audio, they are likely to interrupt the audio stream resulting in dropouts, clicks and pops. Check the Processes tab to see which programs were hit.

Process with highest pagefault count: amd ryzen master.exe

Total number of hard pagefaults 1351
Hard pagefault count of hardest hit process: 795
Number of processes hit: 12


_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 3.915235
CPU 0 ISR highest execution time (µs): 16.561332
CPU 0 ISR total execution time (s): 0.020361
CPU 0 ISR count: 24317
CPU 0 DPC highest execution time (µs): 183.326835
CPU 0 DPC total execution time (s): 1.276757
CPU 0 DPC count: 300248
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 0.586028
CPU 1 ISR highest execution time (µs): 0.0
CPU 1 ISR total execution time (s): 0.0
CPU 1 ISR count: 0
CPU 1 DPC highest execution time (µs): 7.464121
CPU 1 DPC total execution time (s): 0.000105
CPU 1 DPC count: 39
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 0.601962
CPU 2 ISR highest execution time (µs): 0.0
CPU 2 ISR total execution time (s): 0.0
CPU 2 ISR count: 0
CPU 2 DPC highest execution time (µs): 27.982941
CPU 2 DPC total execution time (s): 0.004055
CPU 2 DPC count: 1691
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 0.754102
CPU 3 ISR highest execution time (µs): 0.0
CPU 3 ISR total execution time (s): 0.0
CPU 3 ISR count: 0
CPU 3 DPC highest execution time (µs): 14.557541
CPU 3 DPC total execution time (s): 0.000104
CPU 3 DPC count: 66
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 0.690062
CPU 4 ISR highest execution time (µs): 0.0
CPU 4 ISR total execution time (s): 0.0
CPU 4 ISR count: 0
CPU 4 DPC highest execution time (µs): 29.355538
CPU 4 DPC total execution time (s): 0.003923
CPU 4 DPC count: 1649
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 0.757424
CPU 5 ISR highest execution time (µs): 0.0
CPU 5 ISR total execution time (s): 0.0
CPU 5 ISR count: 0
CPU 5 DPC highest execution time (µs): 28.523964
CPU 5 DPC total execution time (s): 0.001088
CPU 5 DPC count: 305
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 0.818608
CPU 6 ISR highest execution time (µs): 0.0
CPU 6 ISR total execution time (s): 0.0
CPU 6 ISR count: 0
CPU 6 DPC highest execution time (µs): 297.142161
CPU 6 DPC total execution time (s): 0.086823
CPU 6 DPC count: 25425
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 0.773358
CPU 7 ISR highest execution time (µs): 0.0
CPU 7 ISR total execution time (s): 0.0
CPU 7 ISR count: 0
CPU 7 DPC highest execution time (µs): 36.719469
CPU 7 DPC total execution time (s): 0.000345
CPU 7 DPC count: 82
_________________________________________________________________________________________________________
tedpiecemcnugent
Posts: 4
Joined: Thu Apr 18, 2019 10:46 pm
Primary DAW OS: Windows

Re: MOTU 828x, Drivers, and Windows 10

Post by tedpiecemcnugent »

Just sent it in today for a replacement.
klosar666
Posts: 9
Joined: Thu May 16, 2019 2:31 am
Primary DAW OS: Windows

Re: MOTU 828x, Drivers, and Windows 10

Post by klosar666 »

Hi, did you find any solution?
Please let me know, thanks
nordlead26
Posts: 13
Joined: Tue Sep 29, 2020 5:22 am
Primary DAW OS: Windows

Re: MOTU 828x, Drivers, and Windows 10

Post by nordlead26 »

its 2020 and we still with 2015 drivers and without windows support for MOTU 828x... only Mac have 2020 drivers for this unit... it is terrible, so many issues by using AMD and MOTU...
mpax21
Posts: 3
Joined: Wed Mar 24, 2021 9:54 am
Primary DAW OS: Windows

Re: MOTU 828x, Drivers, and Windows 10

Post by mpax21 »

Same thing... 1 year with 828x and i get crackles every time i hear what i recorded... 800euros for noting, well done motu
, i7 :vomit: :vomit: :vomit: :vomit:
Post Reply