Third Party 1394 bus controller drivers for XP and Vista

[TheRealRoach]

Hi pmd,

You should take a close read to this article that I posted previous to this one. Here it is:

http://www.motunation.com/forum/viewtop ... 14&t=31518

[pmd]

Hi Mike,

thanks for the link, but I decide to install AVT 1394 Bus Driver installer for test:

- I install my Ti chipset Firewire PCI Card controller
- I disconnect my motu 828mk2 fw
- I uninstall motu driver 3.6.7.4, I reboot, I clean up registry with Ccleaner
- I reboot
- AVT driver were already installed,
- I run AVT 1394 Bus Driver installer, Texas Instruments is recognized, I switch to Intek
- I Install motu driver 3.6.7.4, I stop my computer
- I connect my motu 828mk2, I start my computer
- Waiting boot is finished, I switch on my motu 828mk2, nothing, My soundcard is not detected?

--> What's wrong ?

(of course if I switch to microsoft 1394 driver on AVT 1394 Bus Driver installer, the soundcard is recognized ...

Regards

[pmd]

I know what's wrong!

I installed "AVT universal Package v1.0" instead of "1394 Bus Driver Package v1.0" !!!

Just after the end of install "1394 Bus Driver Package v1.0",
- I run "Install or remove 1394 driver"
- I switch to AVT 1394 bus driver, waiting about 10 seconds ...
- and my soundcard was detected

I'm going to test now about latency, buffers... And tell you, if you interested in, about results.

Regards

[pmd]

Hi,

It's working perfectly for 2 days with avt driver and a TI chipset Firewire PCI card controller

I could decrease now buffer size without any problem, from 1024 to 128, without pops & clics or something else bizar!

Really, really happy to discover with your help this solution ...

THANKS !
Hope it will save life to a lot of people!

[TheRealRoach]

Hey pmd,

Congrats on getting things working. One suggestion that I strongly encourage is to create a bootable drive-image recovery disc for your system. My system is backed-up in this way and the restoring process takes about 20 minutes instead of at least a full afternoon.

[noisegate95]

As I said way back. One should not have to work this hard to get a $900 sound interface operational. My new interface purchased 6 months ago to replace this POS MOTU has been nothing but inspirational. Works with Windows 7 64 native firewire drivers, no bs, no inf. editing, no camera drivers, right outta the box hot. I'll prolly be banned from board but hey this is my last post. Focusrite Saffire Pro 40. Good luck to all you MOTU users! You'll need it! L8ter

[drhardlove]

Since I still have a few minor issues with my two 828mk2's in FW daisy, I'm now considering trying to go ahead with the AVT thing too, just to see if I can achieve better buffer size at larger projects, but maybe I'm asking to much of my system.

Anyway, is there any place where this is thoroughly described, except from what PMD has written in these last posts here? Did I miss out on some central information, regarding this possible fix?

Is there reason to believe that I might get a better fix from this than my already helpful SP1 driver change, within SP3?

Thanks for all help and direction

[pmd]

Hi drhardlove,

I think you do not have to be afraid of giving a try to AVT drivers, because in case of problem, you still have the possibility to switch back to microsoft 1394 bus driver.

For more information you could have a look to Allien Vision Tec website.

Regards

[pmd]

Hi drhardlove,
here a clear method (with help & advices from TheRealRoach) who still rocks for me since a month now :

- Install Ti chipset Firewire PCI Card controller.
- Disconnect your motu 828mk2 fw (yes, it's important!).
- Uninstall your motu driver, reboot, clean up registry with Ccleaner.
- Reboot your computer.
- Install motu driver 3.6.7.4 (the more stable for win XP), stop your computer.
- Connect your motu 828mk2, restart your computer.
- Switch on your motu, driver's install is processed...
- (restart your computer if asked).
- Install "AVT 1394 Bus Driver Package v1.0".
- Run "Install or remove 1394 driver" from AVT 1394 Bus Driver Package v1.0, just installed.
- Switch to AVT 1394 bus driver, around 10 seconds after...soundcard is detected ... Have fun now !

For info:
You can also (but not compulsory) have a look to "PCi Latency tool" (http://downloads.guru3d.com/PCI-Latency ... d-951.html) that allows you to set your PCI latency for example give more access to your sound card and less to your video card.
Read carefully infos on the web before use.

Regards

[James Steele]

As I said way back. One should not have to work this hard to get a $900 sound interface operational. My new interface purchased 6 months ago to replace this POS MOTU has been nothing but inspirational. Works with Windows 7 64 native firewire drivers, no bs, no inf. editing, no camera drivers, right outta the box hot. I'll prolly be banned from board but hey this is my last post. Focusrite Saffire Pro 40. Good luck to all you MOTU users! You'll need it! L8ter

Why would you be banned from this board? Your kind is what makes things amusing around here. Every one can have an opinion... doesn't matter how credible it is.

[Ratona]

Hey James,

Put a smile on your photo. Just a thought.

Ratona

[RoswellKing]

Hey Guys ,
Having a little issue here and I am fairly sure it is the firewire driver.
Context: Installing Motu 896mk3 on HP dv7 w/ 1.6 ghz i7 ,6gb of ram.
Windows 7 home 64bit

I installed the software ,switched to the leagcy driver after it wouldn't work with the stock driver and I am having a weird problem.

I have no audio I/o at all , But I can control cuemix (even though I have no levels).
I tried to record something to see if it was just not showing meters and nothing.
Funny thing Cue mix works great I tested making changes in all the ctagories and they were reflected in the sound of the signial and in the meter on the 896mk3. Test making changes directly on the unit and they were reflected on the cue mix pc panel.

Crazy.....

Any help is appreciated .

[DevSpo]

I have the exact same HP dv7 rig but using MOTU 828. Using legacy OHCI 1394 driver gives me about 30 seconds of audio before it drops off the face of the earth. have tried everything. Why cant the device driver engineers at Motu get this right? Did they even bother to look up the spec http://www.microsoft.com/whdc/connect/1 ... dows7.mspx" onclick="window.open(this.href);return false;
Shoddy workmanship is the only possible explanation. Now I have to apparently go and look for a TI chipset express card. Any recommendations here? thinking of using http://www.amazon.com/2-Port-Expresscar ... 17&sr=8-13" onclick="window.open(this.href);return false;
Any help here would be much appreciated.

[Aerogroove]

I'm using legacy firewire drivers with a VIA chipset under windows 7 with an ultralite and I wanted to know if alternative drivers could lead to better performance in terms of getting a lower round trip latency or a lower buffer size. Can anyone inform me about this?

I downloaded the AVT driver but it wasn't available in a 64-bit version so I was unable to test that. I did however find a 64-bit version of the Thesycon driver. The thesycon driver installed fine and my interface was detected, but I noticed no performance gain, seemed on par with the included window driver. After reading some documentation that came with the driver, the TI chipset is mentioned but not explicitly recommended in preference of another chipset. Is it possible that the driver is optimized to work with a TI chipset? And also, regardless of whether or not I stick to the windows driver, could switching to a TI chipset improve my round trip latency?