Hi Folks...
Has anybody else had issues of clicks and pops with driver 4.0.4.3553 when the buffer is set low (under 256).
I was running our 828mk3 with no problems till I installed this driver the other day... now I am getting clicks and pops - they are subtle but there. I had to pump it up to 1024 to get our current projects done. I will roll back once these time sensitive projects are complete.
But I wanted to see if anybody else has had this problem? I am running the same driver with our TravelerMk3 and I have not noticed the problem there (yet).
Any one else?
Cheers,
Chris
Clicks and Pops with driver 4.0.4.3553
Moderator: James Steele
Forum rules
Discussion related to installation, configuration and use of MOTU hardware such as MIDI interfaces, audio interfaces, etc. with Windows
Discussion related to installation, configuration and use of MOTU hardware such as MIDI interfaces, audio interfaces, etc. with Windows
-
streamworksaudio
- Posts: 2
- Joined: Tue Feb 02, 2010 12:55 am
- Primary DAW OS: Unspecified
-
juanjotristan
- Posts: 5
- Joined: Fri Jan 07, 2011 5:58 pm
- Primary DAW OS: MacOS
- Location: Spain
- Contact:
Re: Clicks and Pops with driver 4.0.4.3553
Hi, I have the same problem. I'm thinking about to install an older version of the drivers.
MOTU 896 MK3.
DAW: Cubase 5.5.2
PC laptop: Win7 64bit + intel core i7 720 1,66Ghz + 8GB RAM + NVIDIA® GeForce® GT 335M 1 GB DDR3.
Firewire ExpressCard: Sweex FW022 (chipset VIA)
DAW: Cubase 5.5.2
PC laptop: Win7 64bit + intel core i7 720 1,66Ghz + 8GB RAM + NVIDIA® GeForce® GT 335M 1 GB DDR3.
Firewire ExpressCard: Sweex FW022 (chipset VIA)
Clicks and Pops with driver 4.0.4.3553
I've noticed a lot of clicks and pops recently - but I'm not sure what driver I have.
John
John
MacBook Pro (Retina, 15 inch, Early 2013)
2.7 GHz Intel Core i7
16 GB 1600 MHz DDR3
Digital Performer 8.05
UltraLite (2007)
Komplete 7, Omnisphere, IvoryII, and other VIs
2.7 GHz Intel Core i7
16 GB 1600 MHz DDR3
Digital Performer 8.05
UltraLite (2007)
Komplete 7, Omnisphere, IvoryII, and other VIs
Clicks and Pops with driver 4.0.4.3553
Just realized this is a Windows forum, and I have a Mac - but I've been noticing more pops and other audio problems lately! 
MacBook Pro (Retina, 15 inch, Early 2013)
2.7 GHz Intel Core i7
16 GB 1600 MHz DDR3
Digital Performer 8.05
UltraLite (2007)
Komplete 7, Omnisphere, IvoryII, and other VIs
2.7 GHz Intel Core i7
16 GB 1600 MHz DDR3
Digital Performer 8.05
UltraLite (2007)
Komplete 7, Omnisphere, IvoryII, and other VIs
-
juanjotristan
- Posts: 5
- Joined: Fri Jan 07, 2011 5:58 pm
- Primary DAW OS: MacOS
- Location: Spain
- Contact:
Re: Clicks and Pops with driver 4.0.4.3553
I'm working on Win7 64bits. Intel Core i7. 1'66Ghz, 8GB RAM
MOTU 896 MK3.
DAW: Cubase 5.5.2
PC laptop: Win7 64bit + intel core i7 720 1,66Ghz + 8GB RAM + NVIDIA® GeForce® GT 335M 1 GB DDR3.
Firewire ExpressCard: Sweex FW022 (chipset VIA)
DAW: Cubase 5.5.2
PC laptop: Win7 64bit + intel core i7 720 1,66Ghz + 8GB RAM + NVIDIA® GeForce® GT 335M 1 GB DDR3.
Firewire ExpressCard: Sweex FW022 (chipset VIA)
Re: Clicks and Pops with driver 4.0.4.3553
If you're using Win7, and Windows software that uses old driver support (ie, ASIO, DirectSound, or the legacy WAVE API -- not the new WASAPI or WAVE RT), then you can try the following:
1). Run the "MOTU Audio Console" application.
2). Flip to the second page (ie, not the "General" page), and checkmark the box labeled "Enable WAVE RT support for Windows audio" or "Wave support for legacy software" (or something like that. MOTU don't proofread their docs too well, and often change the software labels without changing the early beta pics in their docs).
3). Reboot your system.
Tech explanation what this does: It sort of fools old software using DirectSound, ASIO, and the legacy Wave API to use Win7's new low latency WASAPI or WAVE RT support in the MOTU Win7 driver. WASAPI allows software to output directly to the MOTU's hardware buffers. It's sort of ASIO on steroids, and yields the lowest possible latency you can get on Windows. The caveat: Your software must be playing/recording CD quality (16-bit, 44KHz) audio for this to work correctly. If you're doing 24-bit or 32-bit audio, this MOTU driver hack will introduce audible distortion as it downsamples the 24/32 bit audio to 16-bit. The hack will also mess up any new software that is written to specifically use WASAPI. That's why MOTU says "don't use it unless you're using only legacy software". But for 16-bit legacy audio playback/recording, it can reduce latency.
1). Run the "MOTU Audio Console" application.
2). Flip to the second page (ie, not the "General" page), and checkmark the box labeled "Enable WAVE RT support for Windows audio" or "Wave support for legacy software" (or something like that. MOTU don't proofread their docs too well, and often change the software labels without changing the early beta pics in their docs).
3). Reboot your system.
Tech explanation what this does: It sort of fools old software using DirectSound, ASIO, and the legacy Wave API to use Win7's new low latency WASAPI or WAVE RT support in the MOTU Win7 driver. WASAPI allows software to output directly to the MOTU's hardware buffers. It's sort of ASIO on steroids, and yields the lowest possible latency you can get on Windows. The caveat: Your software must be playing/recording CD quality (16-bit, 44KHz) audio for this to work correctly. If you're doing 24-bit or 32-bit audio, this MOTU driver hack will introduce audible distortion as it downsamples the 24/32 bit audio to 16-bit. The hack will also mess up any new software that is written to specifically use WASAPI. That's why MOTU says "don't use it unless you're using only legacy software". But for 16-bit legacy audio playback/recording, it can reduce latency.