MOTU UltraLite, Asus A7N8X, Windows XP

Nevandal · Post by **Nevandal** » Sat Aug 25, 2007 11:15 am

I'm wondering, does anyone have a working setup with an AMD Athlon based system, A7N8X motherboard and a MOTU Ultralite running Windows XP?

Here is a tech support inquiry I recently made to MOTU:

Issue Type:
Hardware

Title/Subject:
UltraLite: Intermittent digital noise burst on all channels

Description of Issue
OS: Windows XP, Service Pack 1
Firewire: ADS Technologies Pyro PCI 64 (Texas Instruments chipset)
Motherboard: Asus Nforce2 A7N8X Deluxe
Processor: Athlon XP 2600+
RAM: 2 GB PC2700 DDR
Graphics Card: ATi X800 XL (256MB, AGP)
MOTU UltraLite: Firmware version 1.15; Driver version 3.6.7.4

I bought the MOTU Ultralite brand new a few weeks ago. I have installed it correctly as per the instructions.

UltraLite works fine for direct monitoring of my Nord Lead 2X.

UltraLite has a problem playing back anything from the computer, either from a music player or DAW.

This problem is intermittent bursts of digital noise coming from all output channels. It happens occasionally when playing back music from Winamp, Windows Media Player, Quicktime, etc.

The problem frequently happens when playing software synthesizers or other plugins in my DAW. I am using FL Studio 6. The problem also happens in Sonar 6 as well as Ableton Live 6. Also, latency seems to be a bigger problem than it should be...my old $30 soundcard currently outperforms the UltraLite in that department.

All settings on the MOTU Ultralite are their default: 44.1k sample rate, 512 sample buffer size, using SPDIF output and Phones output.

I'll start up my DAW, load a software synth, begin to play and usually every 5-10 seconds, playback will stop completely and there will be a crackling sound (almost like vinyl, but digital) coming from ALL outputs, analog and digital for a few seconds, and then it will resume normal function. However, sometimes the digital crackling noise sound will continue until I either exit the DAW program, turn off the UltraLite, or reboot.

This is not a latency issue! I have tried extremely high sample buffer settings and the problems still occur.

I've tried nearly everything, and other people on the Internet report the same or similar problems...some unable to solve the problem, and some have their UltraLites working perfectly.

Please help!

Steps to Reproduce:
1. Install MOTU Ultralite correctly
2. Install any DAW program (FL Studio, Sonar 6, Ableton Live 6)
3. Load up DAW
4. Load up any software instrument or sample
5. Play and hold a note, so that sound is being played
6. Wait 5 to 10 seconds (sometimes 20 seconds)
7. UltraLite outputs digital crackling noise from all channels intermittently (every 5-10 sec) for 2 or 3 seconds at a time. Sometimes it will output noise continuously until the application is exited, computer is rebooted, or UltraLite is turned off and then back on again.

Troubleshooting
1. Tried Service Pack 1 AND 2.
2. Tried Different FireWire card (1 with Lucent chipset and 1 with Texas Instruments chipset)
3. Tried reinstalling Windows from scratch
4. Tried changing BIOS PCI Latency numerous times.
5. Tried disabling 1394 Firewire card as networking device.
6. Tried using different outputs (phones, main outs L+R, SPDIF)
7. Tried using all available sample rate settings
8. Tried using all available sample buffer latency settings
9. Tried both driver versions available for download on the website: 3.6.7.3 and 3.6.7.4
10. Opened Cuemix software while crackling noise problem happened, and it gives this message: "CUEMIX STATE IS NOT IN SYNC BECAUSE THE AUDIO STREAM IS NOT LO--" This error only appears on the screen during the few seconds the crackling is actually being output from the UltraLite. This is a screenshot of the error message: http://img.photobucket.com/albums/v133/ ... ralite.png

11. Tried different Firewire cables

12. Tried updating Firewire card drivers, reinstalling firewire card, etc.

13. Tried this patch from Microsoft: http://support.microsoft.com/kb/885222
when I had Service Pack 2 installed. I currently have Service Pack 1 installed because it is recommended.

14. Tried reinstalling MOTU Ultralite numerous times.

15. Tried reinstalling DAW software and instruments

16. Tried prayer.

Additional File

Uploaded: http://img.photobucket.com/albums/v133/ ... ralite.png

Operating System
Windows XP

OS Version
Home Edition, Service Pack 1

CPU/Motherboard
Asus Nforce2 A7N8X Deluxe motherboard with Athlon XP 2600+ (2.08 GHz) single core processor

Memory (RAM)
2 GB of DDR333, PC2700 RAM

Additional relevant hardware information
OS: Windows XP, Service Pack 1
Firewire: ADS Technologies Pyro PCI 64 (Texas Instruments chipset)
Motherboard: Asus Nforce2 A7N8X Deluxe
Processor: Athlon XP 2600+ (2.08 GHz)
RAM: 2 GB PC2700 DDR
Graphics Card: ATi X800 XL (256MB, AGP)
MOTU UltraLite: Firmware version 1.15; Driver version 3.6.7.4

Whenever the noise problem happens, CueMix shows this warning message:
http://img.photobucket.com/albums/v133/ ... ralite.png

It looks like it says

"CUEMIX STATE IS NOT IN SYNC BECAUSE THE AUDIO STREAM IS NOT LOCKED"

Here is a link to an MP3 recording of the glitching noise:
http://www.wikiupload.com/download_page.php?id=203228

Warning, when it starts to glitch there is a loud part followed by very quiet noise.

I've tried pretty much everything I can think of.

The Ultralite works perfectly fine on a Dell XPS 400 computer I have, which is Intel based.

I am thinking it is a compatibility issue with my motherboard, the Asus A7N8X

The question I am wondering is, is there anyone here running a Windows system and a MOTU UltraLite successfully?

If so, what is your setup?

I'd especially like to know if you have the Asus A7N8X Motherboard in your system and how that is working with your UltraLite, or any other MOTU interface.

Thank you!

monkeymodulator · Post by **monkeymodulator** » Tue Sep 04, 2007 6:41 pm

Hi, I have the same exact problems as you.

My specs

OS - WinXP Pro SP2

Motherboard - MSI K8N Neo4 Platinum nForce4 chipset
CPU - AMD X2 Opteron 180 ( same as X2 4800+ socket 939)
Memory - 2Gb PC3200

Firewire card - tried texas instruments, onboard mobo, and sb audigy ports. all same outcome

Video - EVGA 8800GTS

MOTU Ultralite: tried firmware version 1.00, 1.10, and 1.15, unit came with 1.00 and it will only work with that version. any other version will cause problems with the ultralite's rotary encoders on the unit itself. Software versions make no difference either.

Tried everything that Nevandal tried above with same outcome - digital noise on all channels.

My question is does anyone have these same problems with Windows 2000 Pro? Is this an AMD or nForce problem?

Al

Nevandal · Post by **Nevandal** » Wed Sep 12, 2007 8:45 am

I'm definitely thinking this is an nforce related problem.

Search the net and it seems a lot of people have the same problem with firewire interfaces if their board is NForce4. The wikipedia for NForce2 says it was plagued with crackling problems with the onboard sound (which I DID experience while playing videogames)...however it looks like it wasnt just the onboard sound, it's firewire interfaces too. Honestly I don't know, it's been a headache trying to isolate this and find out what exactly is causing it, but everything leads me to believe this is an NForce related problem.

..you said your MOTU Interface came with 1.00 firmware installed, and it didn't have the issue?

Mine came with 1.15.

I wonder if theres a way to get the older version back on there?

project · Post by **project** » Wed Sep 12, 2007 12:43 pm

i had similar problems with 1.0 but updating to 1.1.5 firmware cured them.
output meters would go crazy with crackles when i switched between apps with cuemix open. but after updating the firmware a few weeks ago the problem is gone.

Nevandal · Post by **Nevandal** » Wed Sep 12, 2007 8:56 pm

Hmm.

I wonder...how often do they update the firmware? I'm wondering, if I wait until new firmware comes out, it may cure the problem?

Nevandal · Post by **Nevandal** » Mon Sep 17, 2007 11:28 am

Soooo..

In a last ditch attempt, here. I figured the only thing I could do is buy a new computer..but since I don't have that kind of money right now, I bought a motherboard.

http://cgi.ebay.com/ws/eBayISAPI.dll?Vi ... 0152441651

Some brandname I've never heard of...but it's like, impossible to find a Non Nforce Socket A motherboard that has what I need for under $40.

They have a 14 day return policy, and the thing was pretty cheap.

It uses the Via KT400 chipset instead of the NForce 2 I have right now, so hopefully that fixes the problem.

monkeymodulator · Post by **monkeymodulator** » Mon Oct 22, 2007 9:03 pm

Just an update..

Tried another system (I think this is system 4 so far) with sp2. Same outcome. Reinstalled xp and kept sp1 and there aren't any problems other than this being a slow socket 462 1700+ system and not my main rig. Anyone hear if the beta driver 3.6.9.190 will work with xp sp2? Still waiting for motu to respond....

arth · Post by **arth** » Tue Oct 23, 2007 5:26 am

I have an nForce 4 socket 939 based system, an UltraLite with firmware version 1.00, Windows XP SP2, and no problems.

Well, except for the crackling you get whenever there's a sample rate conflict (like if a Windows sound plays at 22.05 kHz or 48 kHz while you're using 44.1 kHz, or a game that tries to play two different sample rates simultaneously), but that's independent of what kind of CPU and motherboard you use, and can easily be avoided (e.g. use a different sound card for Windows sounds).

As for why I stay at firmware version 1.00, it's because MOTU doesn't provide release notes for their firmware. If I can't see what's fixed, why should I risk turning the Ultralite into a brick?

Sorry, MOTU, your under par development support, refusal to open the API, and missing documentation and release notes are the main reasons why I'm looking to replace my Ultralite. You really need to hire some competent programmers soon, cause having good hardware won't help if you can't be bothered making it compatible. And the onus for doing that is on you, MOTU, not on the dozens of other companies your drivers need to interoperate with.