828mkii Sometimes Stops Working |
|
|
|
Mon 19 Feb 2007, 22:45
|
Newbie
Group: Members
Posts: 1
Joined: 19-Feb 07
Member No.: 88,600
|
QUOTE (rbailey @ Sat 17 Feb 2007, 17:29) I was wondering if a solution to this issue was ever found? My MOTU 828 Mk II has worked faithfully for years on a G5. However, I am experiencing the same issues as MatzeMillion with my factory fresh Mac Pro.
.... and I see that MOTU just posted some new drivers on Wednesday...... let see what these bring. Not sure if this all concidence but this past weekend 828 MKII has stopped working me as well on my G5 using Digital performer. There is not output sound coming. If anyone figures out a solution, please tell. This is very frustrating.
|
|
|
|
|
Tue 15 Jul 2008, 03:42
|
Newbie
Group: Members
Posts: 2
Joined: 15-Jul 08
From: San Antonio
Member No.: 102,288
|
Hello I am new to the forum. I have had issues with my 828MKII and my G5,Macbook Pro,Macmini and Mac Pro. So far this is what i did to resolve the problem. I purchased an M-Audio 410 for my Live Kore2 rig and my Macmini. I spent too much time but with this advise I pray some of you get your $ worth from your Motu 828MKII.
I took MatzeMillion's advice. Please see below;
Try a factory reset - push the Setup knob, turn it all the way to the right and follow the directions on the LCD. - Try setting both your Optical Input and Optical Output in the MOTU Console to ADAT. - Try a different Firewire cable. - Try removing all other Firewire devices. - Try different Firewire ports. - Try toggling the red voltage switch on the right side of the unit with the unit OFF. Do this 5 or 6 times, then set it to the correct position and try again. - Try the unit with a different computer, if possible. - If you use a PCI Firewire card, check to make sure your card uses the Texas Instruments or Lucent chipset. - Try reinstalling drivers:
I also did the following; - I reset PRAM -I also repaired my disc permission - I had to re-install the latest driver on Motu's webite 3 times
So far i have did this with my Macbook Pro. I will post new info on the Macmini. It was very unstable but I will check it out soon. I wont install any drivers for my Mac Pro. It is my Pro Tools HD3 rig.
Thanks for taking the time to post this info.
|
|
|
|
|
Tue 15 Jul 2008, 07:00
|
Member
Group: Members
Posts: 57
Joined: 22-Mar 05
From: Cancun - MX
Member No.: 62,788
|
i had a similar problem with my mac book pro and i did everything you did but it would not solve problem i even went and bought a new firewire cable that also did not work what i did to solve the problem was to uninstall a program a program call oss3d (which is a great program) and everything as been running smoothly ever since So your problem may be from some other plugin or software compatibility issue with the motu driver QUOTE (MatzeMillion @ Thu 23 Nov 2006, 04:45) Hi everyone, I have a strange problem with an 828mkII and a MacPro. Sometimes after closing an application with motu sound output (logic, a game, quicktime, etc) the interface stops working. Its still avaliable, but don't play back any sound. Only way to get sound back is a restart. It does happen only with a MacPro. With an Intel MacMini, a MacBook Pro and Powerbook G4 evertything is fine. I tried a complete reinstall, other cable, removing other devices, factory reset, unplugging / reconnecting, switching on/off, unloading/loading kernel extensions, booting the MacPro via firewire from a MacBook Pro, tried an other 828mkII interface, etc. Nothing helps. When it happens, the MOTU Midi interface is greyed out in Audio-Midi-Config. Quicktime is hanging like 10sec when trying to play back sound. Is there anyone with same problem or with a MacPro and no problems? Thanks for any reply!! Matthias MacPro 2,66 GHz, 5GB Ram, X1900XT, OS X 10.4.8, MOTU 828mkII with 1.4.2 driver, LogicPro 7.2.3, Waves 5.9.1 with iLok, Midisport 2x2
|
|
|
|
|
Tue 15 Jul 2008, 14:05
|
Newbie
Group: Members
Posts: 2
Joined: 15-Jul 08
From: San Antonio
Member No.: 102,288
|
I also opened the unit and gently pushed on the "eprom" that holds the firmware. It seemed a little lose so that may have ben the trick. I have done this with other products in the past and it was the fix in the past.
|
|
|
|
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:
|
|
|