|
Avid Pro Audio CommunityHow to Join & Post • Community Terms of Use • Help Us Help YouKnowledge Base Search • Community Search • Learn & Support |
#21
|
||||
|
||||
Re: Firewire 410 is a failure
Quote:
|
#22
|
||||
|
||||
Re: Firewire 410 is a failure
Quote:
|
#23
|
|||
|
|||
Re: Firewire 410 is a failure
Quote:
Do you mind me asking how you have your 410 and hard drive connected on your setup? I have tried chaining everywhich way and have either had the 410 become unresponsive or have experienced the annoying 6101 cpu overload error. The way that I have them now seems the best, but I hate having to use the wall wart for the 410, and I'd like to not have to use the siig card. Thanks for your help, at least someone is trying to figure this stuff out J |
#24
|
|||
|
|||
Re: Firewire 410 is a failure
[QUOTE]
Quote:
Still experiencing no audio, right channel no audio, or distorted audio with digital heterodyning-type distortion almost every time after restart (until I open the control panel SW for the FW410 and either diddle the sync to digital and back to internal, or reset, usually various times required and/or a restart of PT or the entire CPU). Once it's working, occasional brownouts in input/recorded signal accompanied by distortion, and/or digital blurps. In seeming contrast to speculation by some of the other posters in this thread, I had no such problem with a FW1814 on this same rig -- but that was a while ago, and no doubt was some previous version of the M-Audio drivers (and PT 7.0). Sometimes, opening a 44K session will pop the FW410 back into life for 48K sessions I open subsequently; sometimes not. |
#25
|
|||
|
|||
Re: Firewire 410 is a failure
Ok guys, it hasn't been long enough for me to tell if it is going to work long term or not, but I came across something today that I had never read before and thought, what the heck I'll try it out.
Go into your System Preferences>Network. Click the drop down bar by Show, and select network configuration. Make sure that all firewire networking is turned off, this includes expresscards if you still need to use it after this. Anyway, I made these setting changes and then connected my 410 to the MBPs firewire port and chained my external drive to the interface.....you know, like I used to do on the PC without any problems So far I have rebooted a couple of times, completely disconnecting the 410 or leaving it and restarting, no issues at all so far. Also recorded 2 tracks of audio in a session with the following tracks/plugins, all at a buffer setting of 128: 1) Bass - with EQ, Massey Comp, D-verb 2) Drums L - with bmb fact comp, EQ 3) Drums R - with same as above 4) Ld Gtr - none 5) Ld Gtr clean - none 6) Ld Solos - none 7) Rh Gtr fr - none 8) Rh Gtr rear - none 9) Vocals1 - Dverb, comp/lim 10) Vocals2 - Dverb, comp/lim 11) Vocals Hr - Dverb, comp/lim 12) new - none 13) new -none All of this done with Bluetooth and internet connected.....and a WD Mybook firewire drive, which also always worked fine on the PC. Anyway, something to try. I'll keep it like this and report back if I have any issues. I would still like to hear from DigiSupprt as to how he has his MBP/interface/HD set up and what kind of track counts/plugins are possible.... J |
#26
|
|||
|
|||
Re: Firewire 410 is a failure
Quote:
Thanks. Will report back again, after working through various reboots and launches of PT sessions to confirm that today's behavior hasn't been merely a fluke. |
#27
|
|||
|
|||
Re: Firewire 410 is a failure
Awesome! I hope that this helps some of the people plagued with fw410 issues. So far the 2 issues that I had previously experienced are not appearing again....yet:
1) fw410 becoming unresponsive 2) PTs throws 6101 cpu overload errors J |
#28
|
||||
|
||||
Re: Firewire 410 is a failure
Quote:
As for my configuration - MacBook Pro-->FW410 (or 1814)--->hard drives (between 2 and 4). All connected via FW400 in a chain. Track counts - I get the max (48), though I have to split them between 2 drives. |
#29
|
|||
|
|||
Re: Firewire 410 is a failure
Quote:
Maybe this is something that should be added to the Troubleshooting or Optimization links? J |
#30
|
|||
|
|||
Re: Firewire 410 is a failure
Quote:
J |
|
|
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 |