new driver version

[majdid]

any one noticed in the motu site that there is a new MK3 driver version (3.6.8.1400) released on the 12th of march 09? any tests so far?

[VOTIVE]

I'm running that version -no issues.


Finally, MOTU does not hate Windows users.

[TheRealRoach]

What the about the doubling of latency with the 3.6.8.* drivers? Any improvement?

[timizere]

i cant get past 'initializing vst connections' on SX3 without a freeze. same issue on 2 previously stable builds. rollback time!

[majdid]

i cant get past 'initializing vst connections' on SX3 without a freeze. same issue on 2 previously stable builds. rollback time!

same here, can't get cubase sx3 to past that step. any solution?

[dare]

i cant get past 'initializing vst connections' on SX3 without a freeze. same issue on 2 previously stable builds. rollback time!

same here, can't get cubase sx3 to past that step. any solution?

New drivers (1400) are just getting worse and worse! Internal audio routing is a complete mess! When using asio out 1-2, it sends audio on asio 3-4 physical outs, and etc, there is a shift in numbering the channels ! That is really unnecessery bug, besides freeze in Nuendo 3 ! Workaround ? Turn off unit before starting Cubase and then turn it on after start of app. Set up asio driver, but in VST connection panel - DO NOT SET main out as playback channel.

If they continue their course of support, I will be forced to sell this otherwise promising little gadget ! Did they ever hear of BETA driver releasing schemes ? This one wouldn't pass even alpha stage, as far as I am concerned! Like they didn't test it a bit !

[majdid]

i cant get past 'initializing vst connections' on SX3 without a freeze. same issue on 2 previously stable builds. rollback time!

same here, can't get cubase sx3 to past that step. any solution?

New drivers (1400) are just getting worse and worse! Internal audio routing is a complete mess! When using asio out 1-2, it sends audio on asio 3-4 physical outs, and etc, there is a shift in numbering the channels ! That is really unnecessery bug, besides freeze in Nuendo 3 ! Workaround ? Turn off unit before starting Cubase and then turn it on after start of app. Set up asio driver, but in VST connection panel - DO NOT SET main out as playback channel.

If they continue their course of support, I will be forced to sell this otherwise promising little gadget ! Did they ever hear of BETA driver releasing schemes ? This one wouldn't pass even alpha stage, as far as I am concerned! Like they didn't test it a bit !

wow, i though that my issues with motu are gone now that i built a new daw (got rid of SOME of the squeals), but NO! what a mess...
so, you mean that the main output cannot be used now with the new drivers in either nuendo or cubase??? then what is the point of using the MK3 now? time to rollback for me and stick to something that at least doesnt hang out cubase

[rnm]

No problems with these new drivers with my 8-PRE and win XP or Win 7 Beta.

[harleysr]

I just went through the same transposing of outputs with 1400. What a PITA!. I have an 896mk3 with an 8Pre coming into into it via LightPipe (to give the 8Pre inputs the EQ & Comp on the 896 DSP). I use the Main Outs 1-2. Those stopped working, even though they still showed up in Cubase's VST I/O list . All the sound migrated 1 pair to the right, which is to say, it came out of the regular 1-2 outputs. My AES feed also jumped over to the SPDIF. Ridiculous!

In Wavelab, the Main Outs 1-2 still functioned fine. Someone is asleep at the wheel... This should have neve made it out. BTW, does anyone know what this driver was supposed to improve, beyond adding the 96 buffer?

For now, I'm sticking with 1394. It works reasonably well. That being said, I really like the sound of the 896. Pres are very good. Conversion seems reasonable and I love the DSP and functionality. I could live without the attitude and vagueness I get from their tech unit, though. This company is it's own worst enemy.

[dare]

It's me again
I had creamware scope before, and was very upset with the lies they post on their site. They promise new drivers since 2000, but nothing. I sold it and bought something which should be fairly relayable. I discarded m-audio and similar based on reports that they aren't "pro" equipement but this kind of errors on drivers makes me wonder if I decided correctly - I could have bought m-audio profire2626 and would spend a lot less money, yet I would have a working tool. Instead, I fell for the "wonderful" convertors of motu (which aren't even properly documented) and now, I am getting drivers with more bugs with every new revision. It is beyond belief that someone would release such a corrupted driver... Why, o why ! And they haven't corrected it for a week now, although I am convinced that some stupid line of code is misplaced, and it shouldn't have to take a lot of time to debug it...

Anyways...

It seems that there are a lot less BSOD screens with this release (1394 was ok, but I was getting blue screens here and there...) and a new tool is added - under devices (odd enough) Devices -> Oscilloscope.

I hope they will solve this stupid channel issue and give us a proper driver very soon...

[eyeknow]

It's not going to happen though.

I'm old school (traveler) and running 3.6.7.4 with really good results. But that is not going to cut it for the new MkIII systems obviously. In my conversations with motu about all the problems with the 3.6.8.1x drivers (included an 828mk3 I had bought but had to return) they simply reply "we don't support any driver but 3.6.8.1x drivers" Anyways, I'm probably not making sense, but no matter what question or concern I've had, the answer is always "we only support 3.6.8.1x" which means they are not even bothering to read my concerns/questions.

It's a shame, motu hardware is terrific, but this "we hate windows/and won't keep up with drivers across the board" tude just turns me off

[WayneM]

I've got the same problem as some of the other users within this post. When I installed the newest driver Cubase SX 3 would crash on the VST connection Initialization when Cubase first starts to boot. I then tried loaded my VSTI's in standalone without a hitch. So it seems to only effect SX3.

Anyway I fixed the problem by re-installing the driver before and its all working again. The old saying "if it ain't broke don't fix it" rings true again. I never noticed any problems with 32fw-3.6.8.1394 driver so I think I will just resisted the urge to upgrade. Its one of the reasons I have never upgaded from SX3.

[dare]

Yes, but where to find older driver ? I deleted it, and they only offer 3.6.8.1400 So, it means they only offer a malufuncioned driver! Are they not aware of the problem ?!

[rnm]

seems to be an SL/Sx 3 thing, I just tried using SL3 with the new drivers and no sound was produced via my 8-PRE, I don't use this software now as I have Cubase studio 5 which works fine as does cubase studio 4

[audioinjection]

i just installed the new drivers.....i'm using the motu896hd, and now my sound is coming out analog 7-8 instead of the main outs :S