New Firewire updates on Motu Site

Discussion of Digital Performer use, optimization, tips and techniques on MacOS.

Moderator: James Steele

Forum rules
This forum is for most discussion related to the use and optimization of Digital Performer [MacOS] and plug-ins as well as tips and techniques. It is NOT for troubleshooting technical issues, complaints, feature requests, or "Comparative DAW 101."
Xzault
Posts: 87
Joined: Sat Nov 18, 2006 4:13 pm
Primary DAW OS: MacOS
Location: California
Contact:

Re: New Firewire updates on Motu Site

Post by Xzault »

ok so i think i had a faulty firewire cable, i will report back if i have the error again, now everything seems solid :)
User avatar
Tobor
Posts: 803
Joined: Mon Jan 31, 2005 10:01 pm
Primary DAW OS: MacOS
Location: Colorado

Re: New Firewire updates on Motu Site

Post by Tobor »

1nput0utput wrote:
Phil O wrote:But I have a question that I've asked in other threads that no one has answered yet. Isn't the MOTU driver specific to MOTU hardware? Is there anything in there that would affect the performance of 7.1 if the user's interface is something other than MOTU's?
Yes, the driver is specific to MOTU FireWire and USB audio interfaces. It does not directly affect Digital Performer, and it should have not effect at all on other audio interfaces.
Thanks for the info. I've been foggy as well re: what's in a driver. I recently went back to my original 828, and reinstalled a driver that has been working well the last couple years, 1.4.20. I've been having a couple issues with DP7.1, but I gather then that as long as the 828 is happy, I might just as well stay with that driver?

I also notice that my MOTU MIDI driver seems to be the same, 1.4.20. The two are installed together as a pair?

Tobor
iMac 2.7 i5, DP 9.5.1, 10.13.3, Apollo Twin, 828, MTPAV, Toontrack, Spectrasonics, BFD3, Drumcore, Reason 10, Live 10, Logic X, Spitfire, Zebra, Miroslav, Waves, Kronos X, MOXF 6, Axiom 49.
Xzault
Posts: 87
Joined: Sat Nov 18, 2006 4:13 pm
Primary DAW OS: MacOS
Location: California
Contact:

Re: New Firewire updates on Motu Site

Post by Xzault »

ok so it is not a bad cable definitely a problem for me with the new driver here is the error code and i am contacting motu,, i can fix the error by just shutting down my 896hd and restarting it then it works no error, this only happens on startup or restart of the computer


motu audio
error code 3 in file devicelmpI896HD.cpp line 217
called from fileL_FWAudio.cpp line 808
b.g.
Posts: 262
Joined: Wed Sep 13, 2006 8:35 am
Primary DAW OS: MacOS

Re: New Firewire updates on Motu Site

Post by b.g. »

Just a note, the updates for PCI and Firewire appear to be one and the same file.
MacBook Pro retina 2015, i7, 16GB, DP 10, M4
User avatar
Shooshie
Posts: 19820
Joined: Sat Oct 16, 2004 10:01 pm
Primary DAW OS: MacOS
Location: Dallas
Contact:

Re: New Firewire updates on Motu Site

Post by Shooshie »

There are actually two installers. One does PCI only, and the other does both, if I recall correctly. I used them both, but chose only Firewire on the 2nd one.

I've heard of problems from other people with the Firewire drivers. Do you have the previous ones? PM me.

Shoosh
|l| OS X 10.12.6 |l| DP 10.0 |l| 2.4 GHz 12-Core MacPro Mid-2012 |l| 40GB RAM |l| Mach5.3 |l| Waves 9.x |l| Altiverb |l| Ivory 2 New York Steinway |l| Wallander WIVI 2.30 Winds, Brass, Saxes |l| Garritan Aria |l| VSL 5.3.1 and VSL Pro 2.3.1 |l| Yamaha WX-5 MIDI Wind Controller |l| Roland FC-300 |l|
1nput0utput
Posts: 1477
Joined: Thu Aug 02, 2007 4:21 am
Primary DAW OS: MacOS
Location: USA

Re: New Firewire updates on Motu Site

Post by 1nput0utput »

Xzault wrote:ok so it is not a bad cable definitely a problem for me with the new driver here is the error code and i am contacting motu,, i can fix the error by just shutting down my 896hd and restarting it then it works no error, this only happens on startup or restart of the computer


motu audio
error code 3 in file devicelmpI896HD.cpp line 217
called from fileL_FWAudio.cpp line 808
I've been using an 896HD with a Mac Pro, but I haven't seen this error message. How do you make it happen?
The leading cause of wrong answers is asking the wrong questions.
Post Reply