MOTU & Windows XP

  • Thread starter Thread starter Steve Henningsgard
  • Start date Start date
Steve Henningsgard

Steve Henningsgard

New member
Note: I know there are a few threads here and elsewhere detailing this issue, but they are anywhere from a few months to a few years old, and they all seem to disappear without any firm resolution on the subject.

Background: I've been building, repairing, and troubleshooting computers for over 7 years, 3 professionally. I've been recording on computers for nearly as long. Previous to this unit, I've had absolutely no trouble with several Creative Soundblaster cards, an M-Audio MobilePre, and more recently an M-Audio Delta 1010 card. I've used the firewire port for transferring video, and for interfacing with my iPod. This is a known-working, well-built, well-maintained machine we're talking about here.


--------------------------------------------

For those unfamiliar with the issue, I'll re-iterate: MOTU's recording interfaces, specifically the firewire-based variety, have anywhere between sub-par and nearly non-functional drivers for Windows users. I recently purchased a MOTU 896 (non-HD) for use in my home studio. I'm using a fast, home-built, Windows XP SP2-based machine, with a standard PCI firewire card.

My issues include the following:

Problem #1: In a normal windows environment, the card must be switched to a 256 buffer vs. a 512 buffer needed for multi-track recording in Sonar. In order to switch between the two, one must open up the included software, which doesn't recognize the 896 as being connected.

Problem #2: In all windows applications, the card is either not recognized, or is recognized as "MOTU Analog". Unless the buffer is switched to 256, all windows audio will have crackling and skipping and generally be completely useless. However, the aforementioned problem #1 prevents me from changing any options whatsoever unless I open Sonar and access the "Asio Panel" from there.

Problem #3 (intermittent): When starting up windows, the MOTU outputted an extremely loud, extremely high-pitched squeal through my powered monitors.


These issues, combined with those described in countless other threads, seem to point to MOTU using some sort of hacked-together, marginally-functional driver for Windows users, and claiming Windows XP support. I think this is completely ridiculous, as I have wasted several hours of my life troubleshooting what should be a simple, easy-to-use device.

I emailed MOTU's customer support yesterday afternoon with a non-hostile, well-worded letter, so we will see what response (if any) I receive and what their take on the matter is.

Please post any advice or personal experience (good or bad) with MOTU's hardware & windows machines! I know there are many out there who have had nothing but good experiences with these units, and I'd like to hear from them as well :)
 
Last edited:
Mark of the Who-nicorn?

This past christmas I received a Motu 8pre as a present. A very nice present, I was really excited. The set up on my desktop computer went fairly smoothly and everything was working as planned with little to no troubleshooting.

I also have a laptop that I intended to record on using my 8pre to serve as a semi-mobile recording studio. I have ran into nothing and I mean NOTHING but trouble. I havent had any success getting my motu 8pre working on my laptop. I bought a PCI card to establish a Firewire connection to my Laptop. ( Please note that I followed MOTU's directions and bought a PCI card with Texas Instrument drivers which should be more compatible with my windows set up.)
Of course I spent an extra pretty penny to get this specified card which would work well with my motu.

So there I am with my new PCI card installed on my laptop and nothinworking. I have been troubleshooting over and over and over again with any way I can think of. I had gotten as far as the motu actually communicating with my computer. Playing music for about 10 seconds with intense crackles then exploding into blaring white noise.

I have no idea what the heck I should do because I dont know if its the PCI card and if it is ... well then excuse my french but why the fuc'k would you recommend that specific kind?

But I will admit that I DO like my motu on my desktop and that set up went smoothly and I DO like the product.

I contacted tech support about my firewire card hoping theyd be able to point me in the right direction ... but they never responded. MOTU's got its up and downs. I want to say more downs than ups but I'm just a consumer .. what do I matter?

I want to hear your stories as well.


(Edit:May I add that I have successfully captured video footage using the Firewire Port on my PCI card.)
 
My setup is a Gateway XP laptop with 2Gb ram, a Motu828mkII interface, a MidisportUSB2x2 midi interface, a Glyph firewire drive for audio projects and a Seagate USB2/Firewire drive for samples & video editing projects (I do a LOT of video editing).

ZERO PROBLEMS.

The drivers are NOT the problem. You using a TexasInstruments or Lucent firewire chipset card??? Motu demands it...says so right in the documenation and website.

Motu bad on Windows is garbage....
 
2 alesis hd24's, motu 2408 mk3, windows xp,sonar 5 producer, 2 uad cards , no problem. Talk to Motu if you have issues, they can be very helpful. Go to motu audio console and check settings. Check clock sourse, and configure Interface. You may have to refresh them and then shut off motu, then restart motu for it to lock. You should be having this problem. Motu is very xp friendly and stable.
Jim
 
Not to hijack the thread, but does anyone know if it is safe to remove SP2? Or would that entail a full reinstall?
 
lumbago said:
Use XP SP1 - as SP2 is not optimized for firewire - it cripples firewire.
So I've heard: however, I bought XP late in the game and my version comes with SP2.

lumbago said:
And I bet you haven't disabled your USB ports, disabled services, and optimized XP for recording

Why the hell would I disable USB? I've got a usb keyboard/mouse and I routinely use a USB hard drive and memory stick. As for services & such, none of those things have anything to do with my problem and you know it.
 
steve.h said:
Note: I know there are a few threads here and elsewhere detailing this issue, but they are anywhere from a few months to a few years old, and they all seem to disappear without any firm resolution on the subject.

Background: I've been building, repairing, and troubleshooting computers for over 7 years, 3 professionally. I've been recording on computers for nearly as long. Previous to this unit, I've had absolutely no trouble with several Creative Soundblaster cards, an M-Audio MobilePre, and more recently an M-Audio Delta 1010 card. I've used the firewire port for transferring video, and for interfacing with my iPod. This is a known-working, well-built, well-maintained machine we're talking about here.


--------------------------------------------

For those unfamiliar with the issue, I'll re-iterate: MOTU's recording interfaces, specifically the firewire-based variety, have anywhere between sub-par and nearly non-functional drivers for Windows users. I recently purchased a MOTU 896 (non-HD) for use in my home studio. I'm using a fast, home-built, Windows XP SP2-based machine, with a standard PCI firewire card.

My issues include the following:

Problem #1: In a normal windows environment, the card must be switched to a 256 buffer vs. a 512 buffer needed for multi-track recording in Sonar. In order to switch between the two, one must open up the included software, which doesn't recognize the 896 as being connected.

Problem #2: In all windows applications, the card is either not recognized, or is recognized as "MOTU Analog". Unless the buffer is switched to 256, all windows audio will have crackling and skipping and generally be completely useless. However, the aforementioned problem #1 prevents me from changing any options whatsoever unless I open Sonar and access the "Asio Panel" from there.

Problem #3 (intermittent): When starting up windows, the MOTU outputted an extremely loud, extremely high-pitched squeal through my powered monitors.


These issues, combined with those described in countless other threads, seem to point to MOTU using some sort of hacked-together, marginally-functional driver for Windows users, and claiming Windows XP support. I think this is completely ridiculous, as I have wasted several hours of my life troubleshooting what should be a simple, easy-to-use device.

I emailed MOTU's customer support yesterday afternoon with a non-hostile, well-worded letter, so we will see what response (if any) I receive and what their take on the matter is.

Please post any advice or personal experience (good or bad) with MOTU's hardware & windows machines! I know there are many out there who have had nothing but good experiences with these units, and I'd like to hear from them as well :)

This still looks like a setup issue to me. When Im mixing I go to 2408 buffer, if Im tracking I go to 512 so timing is good. If Motu isnt recognized, go to audio console and take a look. Service pack 2 should have an effect. Do you have the latest drivers? I would call Motu. I have in the past and they have been more than helpful. If Sonar is open you will have to close it to change buffer settings.
 
TimOBrien said:
My setup is a Gateway XP laptop with 2Gb ram, a Motu828mkII interface, a MidisportUSB2x2 midi interface, a Glyph firewire drive for audio projects and a Seagate USB2/Firewire drive for samples & video editing projects (I do a LOT of video editing).

ZERO PROBLEMS.

The drivers are NOT the problem. You using a TexasInstruments or Lucent firewire chipset card??? Motu demands it...says so right in the documenation and website.

Motu bad on Windows is garbage....

Check out this forum:

http://www.unicornation.com/phpBB2/viewforum.php?f=14

There are several people who beg to differ. Just 'cause you've had good experiences doesn't mean there aren't problems.
 
Ive installed tens (not hundreds) of MOTU devices on XP with SP2. Zero issues with any of them really. You've GOT to use TI Firewire with MOTU Firewire, and I havent seen where you said what chipset you were using. Also, audio optimizations do really help. You dont need to disable usb, but do disable your unused ports like serial and parallel and your onboard audio. Leaning up the system helps no matter what interface. But its totally unnecessary to use pre SP2 XP.

Most problems with MOTU are people using cheap crappy computers in the first place. Not all, most.
 
I have disabled all unused legacy ports/onboard sound/etc, yes. I'm honestly not sure what chipset the firewire card is using, so I just purchased a TI-based card. If this solves the issue, I'll be somewhat happy (except it *should* work with *any* firewire card: it's not much to ask...).

I'll keep everybody updated.
 
steve.h said:
(except it *should* work with *any* firewire card: it's not much to ask)

No, its in the minimum requirements list. That means youre lucky if it happens to work on something else.
 
Ran an 828mkII on 2 different desktops and 3 different notebooks with no problems whatsoever. Was running Win XP SP2 with no audio optimizations, no changing of buffers, etc. Everything was entirely plug-n-play. All of the computers had TI firewire chipsets.

Isn't it amazing how well stuff works when you give it what it needs to run?
 
Hard2Hear said:
No, its in the minimum requirements list. That means youre lucky if it happens to work on something else.

That's not what I'm saying. What I'm saying is firewire is an IEEE standard and, thus, any device built to interface using the IEEE1394 standard would work with any host controller. NOW!!! I realize that standards can sometimes be less-than-perfect, and that cheaper controllers probably ride the edge pretty hard standards-wise. Whereas TI and Lucent are well-known, high-quality chip manufacturers (and, thus, are usually used in higher-dollar, nicer devices/cards).

I'm just saying it sucks that the standards are apparently so lax :(
 
Supercreep said:
................rtfm?

Bought used, no manual. I don't usually assume hardware built to use a standard interface protocol needs a specific fucking chipset to function. Would you read the manual on a printer you're about to buy to see if it needs a specific chipset for USB? No? Oh really, why is that? 'Cause every fucking USB-capable piece of gear is made to run on every USB-capable machine... thus, "Universal" Serial Bus.
 
Back
Top