828mkII on Vista???

[caffeinated]

Hi,

Has anyone been able to get their 828mkii to work on Vista with the new drivers? I just recieved a new pc, dual core, vista ultimate 64bit, etc... and while the drivers appear to be working and the device installed, the only audio I can get out of it is very, very poor, crackled, with a little delay. I have tried changine the bit rates, buffer size with no avail. I have tried the built-in firewire, plus I bought a TI based PCI firewire card, but the response is the same, barely audible.

The device works fine on my crappy xp pro laptop.

Any ideas? It seems like the tech # for MOTU is perpetually busy, and the switchboard operator at the other number could care less.

[BradLyons]

stay off Vista..... I just can't recommend Vista for anything audio at this time.

[Hard2Hear]

I agree with Brad.

I have a Vista test box with an 828mkII and a RME Fireface800, arguably 2 of the best firewire devices on the market. They both have very poor performance compared to in XP. Anyone saying otherwise is just trying to make a buck off of you.

[caffeinated]

to anyone else who finds this...

As of June 18th, 2007, the MOTU Firewire driver does not work with 4 GB of RAM, it works fine with 2 or 3 GB. MOTU Tech support acknowledged this problem, and told me they are working on it.

Good Luck.

[BradLyons]

WindowsXP doesn't work with 4gb of RAM anyway, it only sees about 3.5 - 3.75gb.

[AgincourtDB]

I'm having this problem also with my new build.

Actually, the problem I'm having is, I get no sound at all. None. I've installed Project 5. I haven't bothered to install Sonar yet. The sample projects sound great through the onboard sound, but with the 828mkii I see meter activity in the P5 GUI, but there's nothing getting to or through the MOTU when MOTU ASIO or MOTU ASIO4ALL is selected (it won't let me choose WDM.)

x2 6000+
Asus M2N SLI Deluxe
4G DDR2 800

[caffeinated]

MOTU's suggestion was to use 2GB of RAM. I found it also worked on Vista with 3.

Good Luck.

[systema]

my 828 mk2 keeps on giving me blue screens when i switch to other apps, thou they give me plenty of warning before hand by giving out some clicking noise when it's about to crash (so that I can save whatever that I'm working on). Shouldn't be a hardware issue as it was fine in xp, kinda sad as I know the motu people are working quite hard on the vista driver.

[Hard2Hear]

Actually, that will depend on the setup.

I have 8GB of RAM on my Vista development machine and the 828 works as well as the RME FF800. The performance is just poor compared to XP.

[Jensen]

I'm experiencing the exact same problem. I was starting to wonder if it was I that started the post without remembering because my problems are not only similiar, they are identical!

I have coresponded with MOTU techlink and they have given me no good explanation. They suggested to try a TI firewire card, but now they I've read that you've allready tried it, I'm not going to bother.

I also have XP x32 installed and it works flawlessly so for now I'm going to stick with that untill MOTU finally recognize the problem and provides new drivers that fix the problem.

I have 4GB of RAM and the techlink representative didn't suggest to try it with 2GB of RAM as I've read on this forum, but I'm definetively going to try it. If this actually works, the MOTU guys really have to put their act together because this was the reason I moved over to Vista x64. I need my 4GB of RAM!! 2GB is not going to cut it since my drumkit alone uses 1300-1500MB of RAM. At least in XP, I'm able to utilize 3GB of my 4GB...

Unfortunately I'm at work for the moment, 10.000km away from home so I won't be able to test it for 3 more weeks, but I'll keep a close eye on this forum and hope to read good news before I travel home.

[Hard2Hear]

I also have XP x32 installed and it works flawlessly so for now I'm going to stick with that untill MOTU finally recognize the problem and provides new drivers that fix the problem.

This is a Microsoft problem, NOT a MOTU problem.

If you moved to Vista64 for audio before ANY professional studios started using it and ANY Pro DAW builders started suggesting it, then fully expect to spend your time testing and troubleshooting and not making music. This is not MOTUs fault.

[AgincourtDB]

This is a Microsoft problem, NOT a MOTU problem.

Sorry, but drivers are the hardware manufacturer's responsibility, as we all well know.

[Hard2Hear]

No, writing an os kernel that hampers pro audio manufacturers from developing low latency performance, thats MS fault and thats the problem.

If everyone BUT MOTU had working low latency drivers for Vista, then you could say blame it on MOTU. But as of right now there are no drivers by any pro company that perform well in Vista. Microsoft has even acknowledged the problem and said it would be addressed in the first service release. Ive done testing with 7 different manufacturers drivers in Vista and MOTU is clearly in the top two with RME.

[fwmusician75]

agreed, you can't just choose an OS because it's new and expect everything to be fine.

[AgincourtDB]

No, writing an os kernel that hampers pro audio manufacturers from developing low latency performance, thats MS fault and thats the problem.

If everyone BUT MOTU had working low latency drivers for Vista, then you could say blame it on MOTU. But as of right now there are no drivers by any pro company that perform well in Vista. Microsoft has even acknowledged the problem and said it would be addressed in the first service release. Ive done testing with 7 different manufacturers drivers in Vista and MOTU is clearly in the top two with RME.

Nobody has working low latency drivers because nobody has drivers that use the new audio driver model. The true test of the OS will be pro/proaudio cards with WaveRT drivers. Everything else is testing for the wrong thing.