No MOTU audio devices detected....

whentomorrowfails · Post by **whentomorrowfails** » Sat Jul 21, 2007 11:25 pm

okay, so I got a traveler a few weeks ago, and the set-up was a bit rocky at first as far as the software and drivers go. but i got through it just fine. then the other day, i decided that i wanted to rearrange some things to make my working environment a little more ergonomical with less hassle to get to things. after my "operation rearrange" i went to run cuemix and it said "no MOTU audio devices detected". then i start trying to open the other things such as motu audio and i get "no motu device detected, make sure your motu audio device is connect, powered on, and that the drivers are installed". then i go to the "smpte" and i get "the audiowire driver was not found".

i am not sure what the hell could've happened, but i have uninstalled/reinstalled at least a dozen times and i get the same result every time. looking in my device manager i see "This device cannot start. (Code 10)" the firewire card is an "IEEE 1394 (Firewire) 2-Port PCIMCIA Card " found at the following address: http://www.dynexproducts.com/p-507-dyne ... -card.aspx

but there is nothing listed from motu, and if i am not mistaken there was when it was working properly.

i am running:
sony vaio VGN-FS750P laptop
Intel(R) Pentium(R) M
1.86 GHz
504MB of RAM
120 gig hdd
dual layer dvd/cd burner

does anyone have ANY ideas? i am at a complete loss as to what happened. the only thing i did was take the card out, after shut down. i didn't do anything to the software or anything i just physically rearranged the placement of stuff.

rnm · Post by **rnm** » Sat Jul 21, 2007 11:36 pm

Sounds like you firewire card has gone tits-up, try a different one with a TI chipset if you can

whentomorrowfails · Post by **whentomorrowfails** » Sun Jul 22, 2007 5:58 am

it's not that, it recognizes the card. if i put it in the "found new hardware" thing pops up and everything, so i don't think it's the card.

rnm · Post by **rnm** » Sun Jul 22, 2007 7:33 am

The found new hardware thing should only pop up when you put the card in for the first time when the computer looks for drivers, after that you should only get a beep when the card initializes, if it happens every time you put it in then you have a driver problem for the firewire card. I should try your Motu on a different computer if possible.

whentomorrowfails · Post by **whentomorrowfails** » Sun Jul 22, 2007 8:38 am

no, that's what it does it does that beeping noise and when i click on the little icon thingy for added hardware it's in there and knows what it is.

rnm · Post by **rnm** » Sun Jul 22, 2007 9:15 am

I've just looked at the manual for the card you have ,it has a VIA chipset, these can be flakey when it comes to audio hardware try to find a card with a TI chipset, I use a Belkin card,

rverne10 · Post by **rverne10** » Sun Jul 29, 2007 12:33 pm

singin' the blues bout device not recognized?- (I think I'll write a tune on this theme)
I have always found that when ever there is any doubt about a setup, that a clean install will often work.
Sometimes, in the desperate darkness of the night when the 'no-audio- gear' blues set in, I've reformatted the hard drive and reinstalled the operating system from scratch.
However, I would not, (repeat, do not reinstall your operating system, step away from the computer, place your hands over your head . . .) do such a thing now.
Here's a tip from Echo and Cakewalk techies: (not available from MOTU, or maybe ask them), do a clean sweep of the original install by removing all new files that were installed when you pushed the install button.
So here's the recipe:
1. Run uninstall (obviously),
2. then run a utility program like Registry Mechanic (don't have it?, tut, tut, do you have a credit or debit card with $30.00 on it? Move back towards the computer, slowly place your hands on the keyboard . . . . .)
3. Then take the list of programs from the manufacturer that are not often removed by uninstall but that ARE part of the install (they may be in the DLL inner chamber of the Windows file), seek down those little gnats and rename them. Oh, you say MOTU does not have such a list?
(Again, move slowly towards the computer) . . . Well ring up.and ask MOTU techs about doing a clean install by removing, with a list they will supply (and they do have it), those pesky little gnats that are making Windows go shizoid.
By the way, the sign of quality support is the willingness to be upfront on this issue, Echo is ( every box they sell comes with a clean sweep utility built into the install), Cakewalk is and (dare I say the name?) Roland is.
So is Microsoft: read these files very carefully and follow intrepidly where so few dare to go.

Write down everything you do on the way to following the steps-it really helps.
Do a clean sweep of your computer
How to safely remove software and files from your PC
http://support.microsoft.com/?kbid=322205
After you install a new hardware device or new software, Windows XP may continuously restart, or you may receive an error message on a blue screen
http://www.microsoft.com/athome/moredon ... sweep.mspx

whentomorrowfails · Post by **whentomorrowfails** » Sun Jul 29, 2007 2:43 pm

so, after going through the reg and cleaning out EVERY single MOTU file i could find, doing a clean install of the software, AND buying a new "TI" chipset firewire card for my laptop, it still DID NOT work. after going through all of that, my father and i decided that he should take it home and try it on his 4 computers that he has, and it loaded right up on ALL of them, so we've come to the conclusion that we are having a conflict somewhere or another, and we're not sure where at, but we think it might be my wireless logitech mouse (we decided this after he took it home and it worked) we haven't yet tried to get rid of the drivers for the mouse yet, but probly will this week or something.

as an update though: EVERYTHING was recognized, but the MOTU itself, it did recognize both cards that were used, but we couldn't get the software to sync up with the hardware. so, conflict somewhere? hope so.

emulatorloo · Post by **emulatorloo** » Sun Jul 29, 2007 2:45 pm

rnm wrote:I've just looked at the manual for the card you have ,it has a VIA chipset, these can be flakey when it comes to audio hardware try to find a card with a TI chipset, I use a Belkin card,

As rnm states -- you need a diff firewire card with a CHIPSET that is supported by MOTU. VIA is not good for this. You need TI or Lucent.

http://www.motu.com/techsupport/technot ... mcia-cards

MOTU FireWire audio interfaces and PCI/PCMCIA FireWire card chip sets

MOTU recommends using strictly FireWire PCI/PCMCIA cards based on the Texas Instrument chipset.

There's an incompatibility between the NEC chip found in some FireWire cards and the MOTU FireWire line of interface.

If the FireWire installer warns you that you're running a FireWire card with the NEC chip, you should replace said card with a card that uses the TI (Texas Instruments) or Lucent chip. Keyspan, Sonnet, Miglia, and ADS are a few of the many brands using the TI or Lucent FireWire chips.

Please check with the manufacturer of the FireWire card before purchasing it to ensure it has the TI or Lucent chip. Note that nearly all combo USB/FireWire cards do not a use TI or Lucent chip, so you will need a dedicated FireWire card.

For additional considerations about FireWire cards when using the Traveler or UltraLite, please see this tech note.

---------------------------------------------------------------
SEE ALSO:

http://www.motu.com/techsupport/technot ... Wire-Power

I'm having trouble powering my Traveler or UltraLite via FireWire

There are some considerations when powering the Traveler or UltraLite via the FireWire bus.

The Traveler or UltraLite can draw its power from the computer via the FireWire bus. If you're using FireWire bus power on the Traveler you must set the Bus Power switch on the right side of the unit is to "On".

There are some additional considerations when using FireWire bus power when your FireWire ports are on a PCI or PCMCIA card. PCI cards must have a direct connection to the power supply harness inside the computer, and PCMCIA cards must have an external power supply (most commonly a DC power adapter that plugs into an AC power outlet). Keep in mind that we strongly recommend using a PCI or PCMCIA card with a Texas Instrument or Lucent FireWire chip set with all of our FireWire interfaces (see this technote for details).

The Traveler and UltraLite cannot be powered via the FireWire bus when using a 4-to-6 pin FireWire cable. The unit will function properly in all other manners, but you will need to use DC or battery power instead of FireWire.

Also, when powering the Traveler or UltraLite via the FireWire bus, we do not recommend daisy-chaining other FireWire devices on the same bus. In general, daisy-chaining FireWire bus powered devices is not recommended.

For more info on powering the Traveler or UltraLite via DC adapter, please see this technote.

whentomorrowfails · Post by **whentomorrowfails** » Mon Jul 30, 2007 1:39 am

as i stated, we went and got a ti chipset card, and it still didn't work on my computer, but BOTH the via and ti worked on all of my dad's computers, or which ever ones he tried anyway. and i was not using the bus power, i have no need to use it.

thanks for the help though

emulatorloo · Post by **emulatorloo** » Mon Jul 30, 2007 10:14 pm

whentomorrowfails wrote:as i stated, we went and got a ti chipset card, and it still didn't work on my computer, but BOTH the via and ti worked on all of my dad's computers, or which ever ones he tried anyway. and i was not using the bus power, i have no need to use it.

thanks for the help though

Let us know if it was the mouse drivers then.

00

whentomorrowfails · Post by **whentomorrowfails** » Tue Jul 31, 2007 1:06 am

most certainly will do!

MOTUnation.com

No MOTU audio devices detected....

No MOTU audio devices detected....

Reinstalling got you down?

allllllllll riiiiighty then...