Home |
Search |
Today's Posts |
#1
![]()
Posted to rec.audio.pro
|
|||
|
|||
![]() The MOTU package is SIXTEEN times larger, yet, as far as I can tell, both do essentially the same thing. This is called "code bloat", and there are a number of reasons for it: 1. Big libraries linked in that contain extraneous code. 2. A universal driver is fitted with a "wrapper", so that it can be used on both Mac and Windows. 3. Inefficient development environment. 4. Skill. Some programmers are coding geniuses. Some are just very competent. There are no dumb guys in this business. 5. Money. The more perfect the driver, the more it costs. I would not be too hard on MOTU for not having the best driver team in the business. In the right machine, it's solid. Their hardware requirements seem a bit optimistic, as I see no way a 1 GHz machine could work with the Traveler without severe impairment. The MOTU driver is not aware of what it needs to work. Bob Morein In a way, it's surprising it works at all on a Windows machine. MOTU has always been a Mac-oriented company, & their drivers have been flawless in that environment. It's unfortunate that they haven't been able to do Windows very well & I suspect they would just as soon have nothing to do with the Windows environment, but for the need to have a wider market base than Macs alone can provide. Hope it works for you. If you know how to fix the driver issues, MOTU does have a suggestion box somewhere on their site. I'm sure they'd like to hear what would improve things. Scott Fraser |
Reply |
Thread Tools | |
Display Modes | |
|
|
![]() |
||||
Thread | Forum | |||
MOTU 8 pre and traveler | Pro Audio | |||
Motu Traveler | Pro Audio | |||
MOTU Traveler | Pro Audio | |||
MOTU Traveler | Pro Audio |