New Drivers : 06/08/2010 : Installer 100802 Vn: 4.0.42546

[RonaldDumsfeld]

New Drivers : 06/08/2010 : Installer 100802 Vn: 4.0.4254

As per usual no indication from MOTU what issues this release addresses.

So if you have installed these drivers please report back your impressions.

Do they fix any problems you know about. Did the install proceed as a expected. What new bugs have been introduced. etc etc.

Thx.

[mandobilly64]

New Drivers : 06/08/2010 : Installer 100802 Vn: 4.0.4254

As per usual no indication from MOTU what issues this release addresses.

So if you have installed these drivers please report back your impressions.

Do they fix any problems you know about. Did the install proceed as a expected. What new bugs have been introduced. etc etc.

Thx.

You had me all confused with your dating system, in US we date with m/d/year, so this looked like June 8th.
Hmm, I'll have to give them a try.

[jason12]

New Drivers : 06/08/2010 : Installer 100802 Vn: 4.0.4254

As per usual no indication from MOTU what issues this release addresses.

So if you have installed these drivers please report back your impressions.

Do they fix any problems you know about. Did the install proceed as a expected. What new bugs have been introduced. etc etc.

Thx.

The issue fixed: CueMix would not start. Even on SP3 machine.

After installation I was getting clicks (with different buffer sizes). Then all of a sudden they stopped (again with different buffer sizes).

Cycling power on MOTU box would cause occasional drivers not being loaded. First it all appeared that the system recognized the MOTU box. And after 2 minutes it dropped it.

I am using Traveler with latest firmware.

[rnm]

Installed, no problems so far with Win XP SP3 and Win 7 32bit using a Motu 8-pre.

[torrentg]

Installed a few days ago. Previous bsod issue fixed with last driver seems to continue to be fixed. No issues to speak of and everything is perfectly well.

[RonaldDumsfeld]

nudge, nudge.

I installed this p.m. No changes noticed so far.

[j_e_f]

I can definitely confirm one bug fix. When used with a kernel streaming program, the driver no longer crashes the system when the program shuts down. (Before it crashed the system hard. Not even a blue screen of death. The computer would completely reboot).

Now for the really bad news. The Windows 7 drivers are in really bad shape. I'm running Win7 64-bit, and doing some programming with the MOTU. With the 64-bit drivers, the MOTU is limited to 16-bit input/output. It can't do 24-bit.

Furthermore, they did some hack to make programs, using the old Windows audio API, tricked into using the new audio API called WASAPI, which features a really low latency scheme known as WaveRT (where the RT means "real-time"). The problem is that this hack totally interferes with new programs that actually _do_ use WASAPI, and those new programs won't work. You have to go into the "MOTU audio console" and uncheck that box labeled "WaveRT" (under "Use for Windows Audio"). Only then will audio programs specifically written for Win7 work.

But what bothers me more is that our 24-bit audio device turns into a 16-bit device under Windows 7 (although I'm testing only the 64-bit Win7. I do know MOTU hardware doesn't have this limitation under XP 32-bit, which doesn't have WASAPI/WaveRT). Now, Microsoft's WASAPI requires an audio card to be designed in a certain way to support the new low latency WaveRT operation. I certainly hope MOTU didn't say something like "Um, our hardware will work with WaveRT only if we restrict the driver to 16-bit input/output. Let's do it just so we can say we support WaveRT, and just not tell customers they're buying a 24-bit card that can't actually do 24-bit on Win7 (or later)". And yet, I'm thinking they may have done just that. In order for a device to work in 24-bit, it must accept a 32-bit sample point (and ignore 8 of the bits). MS set this hardware limitation because Intel/AMD CPUs can't write 24-bit values. Those CPUs work with 8, 16, 32, and 64 bit values. But if MOTU's hardware actually accepts only 24-bit values in 24-bit operation, then this won't work with WaveRT.

If my suspicions are correct, MOTU needs to remove this "half-way" WaveRT support from their drivers _immediately_, and go backto supporting 24-bit operation. Restricting a 24-bit device to only 16-bit operation is really bad. I'd rather have working 24-bit operation than support for WaveRT. I can always tweak a system to improve latency. But I can't do anything about a driver that "disables" my 24-bit operation.

[TonyBy]

Now for the really bad news. The Windows 7 drivers are in really bad shape. I'm running Win7 64-bit, and doing some programming with the MOTU. With the 64-bit drivers, the MOTU is limited to 16-bit input/output. It can't do 24-bit....... But I can't do anything about a driver that "disables" my 24-bit operation.

Hi j_e_f
Like you, I'm using Windows 7 64bit.
Not sure what Motu Unit you use .. mines a Traveler mk3.
I use Steinberg software (C5 & WL6)and ASIO drivers only.
Your post had me worried, so I did some tests here.
I am using the Motu Drivers labelled 4.0.4.2114.
I'm sending digital audio into the Traveler over stereo Toslink via a sample rate converter, that allows me to set the desired output bit depth.
I can then record & analize the data in Wavelab, which has a bit depth meter.
I played the audio, and switched the bit depth to all available positions, while recording this as a 24bit Wav file, in WL.
Although resulting wav is of course 24bit, the bit depth meter in WL shows the "Apparent" bit depth on playback (how many of the 24 bits are actually doing anything).
On playback I saw exactly what I had hoped .. with the SRC set to o/p 16bits, the meter in WL showed 16 apparent bits. When the SRC switched to 20 bit so did the WL meter, and again at 24 bits.
In short, as far as I can tell, it all seems OK here.

Possibly, you're talking about only the latest drivers ?? Or possibly you're not using asio ??

Just wondering how you're testing this ?? Analog in/outs or Digital or all ??