|
Avid Pro Audio CommunityHow to Join & Post • Community Terms of Use • Help Us Help YouKnowledge Base Search • Community Search • Learn & Support |
#31
|
||||
|
||||
Re: Firewire 410 is a failure
Quote:
It's strange that they're coming with it enabled. I wonder if this is something new - I haven't seen this enabled by default on new machines in our department. |
#32
|
|||
|
|||
Re: Firewire 410 is a failure
Quote:
J |
#33
|
|||
|
|||
Re: Firewire 410 is a failure
Quote:
I also continue to intermittently get recordings with digital blips in them, mic input 1 (but interestingly, not input 2) will occasionally "brown out" with a level drop and digital noise for few seconds only to be OK the next time I restart recording, and playback in general will have occasional random pops in the analog ouput (which don't appear in bounced files). These problems persist whether a FW hard drive is connected to the system (G4 dual 1.25, OS 10.4.9) at all, and whether my LaCie 250GB is connected to the FW 800 or 400 port (where it remains, until I complete the troubleshooting process or ditch this unit and install a Digidesign interface with PT-LE, which never gave me any problems on this same CPU). I have no other FW peripherals connected, no additional PCI cards in the computer, no background processes like energy savers, Internet time servers, screen savers, anti-virus scanning, or any of that obvious stuff going on). With PT-MP 7.3.1 in particular, I have noticed that the wierd bad clock-sync sound and no-audio output problem at startup (which is usually, but not always, accompanied by no activity showing on the level meter of the Master Fader) are SOMEWHAT less frequent if the first PT session I open is 44.1, rather than 48 kHz. I haven't tried downgrading to the 1.7.4 driver (from 1.8.2, which I have redownloaded/reinstalled twice now), but... can anyone tell me any issues I should be aware of, before trying this? |
#34
|
|||
|
|||
Re: Firewire 410 is a failure
That is a bummer to hear SoundWrangler! Mine has been working very well, which doesn't really make you feel any better I am sure. Could it be something silly like the cable? Maybe you actually have a defective unit? I think at this point I would contact M-Audio and see about getting it serviced or replaced.
J |
#35
|
||||
|
||||
Re: Firewire 410 is a failure
no its not a bad unit. I had many of the same symptoms, the same digital noise and no audio etc.
__________________
2012 mac pro PT 2018 Presonus Studio 192 |
#36
|
|||
|
|||
Re: Firewire 410 is a failure
Quote:
My interface is connected to the fw 800 port with a 800 to 400 Belkin cable (paid for it might as well use it), and then the WD HD is chained through the 410 with a standard 6 pin fw cable. I am using the bluetooth keyboard and mouse with no issues, and it doesn't seem to make a hill of beans whether or not I have wireless on or not. Spotlight, sleep, safe sleep, and Dashboard are all disabled. Running 10.4.11, 1.8.2 M-Audio driver, and 7.3.1 cs5. J |
Thread Tools | Search this Thread |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Digi 002Rack FireWire failure | LiamSlack | 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Win) | 27 | 11-15-2011 02:40 PM |
Is The Firewire Bridge Failure A Common Digi 002R Problem? | epu | 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Win) | 25 | 11-01-2010 02:14 PM |
digi 002 Rack Firewire connex failure | lekkerville | 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Mac) | 2 | 11-22-2006 12:49 PM |
Digi Rack002 Failure/Firewire Reset | maimkill | 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Mac) | 1 | 05-22-2005 11:45 AM |
Firewire Failure . . . Digi 002 Rack | Jhon Of The Zone | 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Win) | 2 | 01-14-2005 10:05 PM |