New MOTU Firewire/USB 2 Drivers Have been Posted. 3.6.8.1410

[HotShot]

Didn't you read the 1st post?

The lowest sample setting is 64.

[dare]

New driver works wonderfully well. The routing problem has been fixed. The new phase meter is better than what I had envisioned. The diagnostic capabilities are absolutely astounding and I have numerous projects where these will be used.

I have a place I record several times a year and have never been satisfied with the sound due to standing waves and the phase problems these cause. I'll take a speaker there, feed it with white noise, and look at various microphone configurations that will minimize these problems. The MOTU gear is an incredible value! No one else, at any price, provides these capabilities and tools.

Another plus is the way CuemixFX loads when using 3 interfaces. In driver 1400, with Traveler MKIII, original Traveler, and an 8Pre on the Firewire buss, Cuemix nearly choked the computer trying to throw all 3 versions on the screen at once. Driver 1410 loads them 1,2,3 very nicely with no wait for system to stabilize. There's not enough real estate on the monitor to keep all 3 on-screen at once so I keep two minimized but can switch among them very quickly.

You sound like some MOTU promoting guy And buy a 2nd monitor - two 24" wide for example - you can put a lot on a single one . It is much easier working with many VST windows mixers and such...

@someone asked...
By "trying" I mean using them for some time... If they are misrouted don't you think it would be obvious from the first look at them ?!

[Mark S]

Another plus is the way CuemixFX loads when using 3 interfaces. In driver 1400, with Traveler MKIII, original Traveler, and an 8Pre on the Firewire buss, Cuemix nearly choked the computer trying to throw all 3 versions on the screen at once. Driver 1410 loads them 1,2,3 very nicely with no wait for system to stabilize. There's not enough real estate on the monitor to keep all 3 on-screen at once so I keep two minimized but can switch among them very quickly.

Are you doing this in ASIO or WDM?

[APADRecordings]

To Dare

I try to keep it very simple with location recording work. Two monitors would be a real pain to handle. In fact, I don't know where I'd put them! I carry a single Dell 20" in a suitcase along with keyboard, headphones and LED lamp.

To Mark S
I'm using the ASIO drivers with SONY Vegas/Sound Forge/CD-Architect.

And no, I don't work for MOTU but am very appreciative of the capabilities of their packages. I started in this business in 1970 using an AMPEX 351-2, which I still have, (the Ampex met the Army's definition of portable - anything with two handles ) I have hours of razor blade editing and am still awed by what can be accomplished now!

[majdid]

i can confirm, works well in cubase 5. just hoping that there is no misrouting in the 1-8 individual out's or the SPDIF or even the ADAT ones. i am just using the IN's and the main Stereo OUT for now.

[edding]

Working well now on nuendo3.
You must reinit the inputs and outputs in vst audio bay if you come from 3.6.8.1390 or previous version

The only issue i have now is MIDI realibility

[dare]

@ APADRecordings
If you want to be portable then it is ok with a single monitor. 20" is big enough. But I was talking about making music in some studio room with a lot of software plugins... I worked in a room with 2 x 26" flat screen monitors and it was very pleasant experience. I have only one 24" wide screen and it is pretty enough for my needs.

I would say that motu is fairly good, I am not thrilled by it... What I really loved was my old CREAMWARE Scope card which had endless possibilities, but was full of bugs.I loved that concept. Motu is not as routable and flexible as CW but all in all, it is not so bad. Motu has one big advantage - AD/DA converting quality... I would like to have their new XCITE 1 but i bet it will be buggy also, as they update their drivers once in 5 years!

@edding
About that MIDI "realibility" What do you mean by that ? I use my MIDI keyboard to play and record MIDI info,everything seems to be fine, but I am not using some MIDI extensive sysex commands or such...

[Mark S]

To Dare

To Mark S
I'm using the ASIO drivers with SONY Vegas/Sound Forge/CD-Architect.

Thanks for the reply. I have been unable to get my 8pre and 896 hd working together in asio mode. Motu tells me they won't because of the asio limitation to one instance of the driver. I'd always been lead to believe that since BOTH units are using the same driver I was good to go. This gives me more to look into, though WDM is working just fine.

Another fine strike out for Motu tech support. They are fools.

[resistor]

this is great news for all. cant wait to test it out tonight.
ive only had my mk3 for a month now (PC with Cubase5)
all been good so far, no major issues.i feel like one of the lucky ones thats for sure.
the only problem ive had is cu-mix wont extend view. and i do get squeeling if i run any other gear on the same PCI-usb/firewire card.
if i dedicate the card to the motu, it works fine.
hopefully these small gitches wont be there with the new drivers.

peace.

Phill

[resistor]

this is great news for all. cant wait to test it out tonight.
ive only had my mk3 for a month now (PC with Cubase5)
all been good so far, no major issues.i feel like one of the lucky ones thats for sure.
the only problem ive had is cu-mix wont extend view. and i do get squeeling if i run any other gear on the same PCI-usb/firewire card.
if i dedicate the card to the motu, it works fine.
hopefully these small glitches wont be there with the new drivers.

peace.

Phill

Installed the new drivers lastnight. works perfect. No glitches ,pops or squeels to report.
pretty surre the cue-mix window is suppposed to extend by dragging the bottom right corner, which it still doesnt.
minor problem anyway. at least its stable at last and sounds great.

[robleighton22]

ok these drivers are bad for me. very bad, has anyone got the version before at all?

not only are the dropouts more frequent, sometimes the sound drops out completely and won't come back. i can't be dealing with this ••••. i hate motu drivers, why can't they sort there act out.

got windows 7 rc1, 2gb ram, 2.2ghz intel dual core, geforce 8600gs

if anyone has the driverset before this release, please please let me know.

many thanks

[tricky]

Hi guys i hope you can help me i have the original Traveler with 1.07 firmware and i saw these latest drivers 3.6.8.1410 on the MOTU website, my question is are these drivers suitable for the original traveler or are they only for the MK2 / MK3 Traveler. Also do i have to uninstall the previous drivers or do i just install if there suitable. Many thanks

[HotShot]

Hi tricky:

The word out is that if you don't have a mk3 model, you might want to stick with an older driver such as 3.6.7.4. because the newer drivers have introduced higher latency to accomadate for the onboard DSP effects of the mk3 units. The newest driver does add new audio analysis tools (posted in my 1st post of this thread), but some non-mk3 users rather stick with the older driver (2.6.7.4) because the lowest hardware buffer size is 32, in contrast, the newest driver has 64 as the lowest hardware buffer size.

It's always best to uninstall the older driver before installing a new driver.

[tricky]

Hi there Hotshot thanks for your speedy and prompt reply, very helpfull, higher latency is something i dont want the lowest i can obtain at present is 11 ms which is fine , would you by any chance know if 3.6.7.4 are the latest drivers for the mk1 traveler it's just that sometimes my system crashes and i'm quite sure it's the traveler doing it. cheers

[HotShot]

I have the UltraLite-mk3. I'm not sure if the 3.6.7.4 is the best driver for the Traveler, but I have read good reports about that driver version.
You can install the new driver (3.6.8.1410) for the Traveler. It's just some are concerned about keeping the driver version that has the 32 hardware buffer size option, and the 3.6.7.4 has that size.

At a 44.1 sample rate, 11ms latency would mean that the hardware buffer is set at 512 samples and the latency will be a smaller size at higher sample rates.

So with the new driver's lowest hardware buffer setting of 64 samples. you will have a 1.5ms latency reading at a 44.1 sample rate. With a hardware buffer setting of 64 used, SONAR reports that the ASIO reported total round trip latency is 6.1ms. In my opinion, that's not bad, but not as low as the total round trip latency that is possible with non-mk3 units and the 32 hardware buffer size selected.

Hope this helps.