Now it makes sense. While we're remotely on the topic of MBox Pros, mine's b-stock, and has never played nice, and is even worse now. Before I spend money on an avid support code, is there anything I could try to try and reduce buffer underflows when my hw buffer size is at lowest, the headphones sockets not working, and the box refusing to work on Windows in particular after about an hour, as well as VoiceOver having a fit and crackling like mad through it when I quit Pro Tools?
I'm about 97% sure it's the hardware's fault, after 3 installs, and 9 months of it not working, but the company I brought it from are being a little difficult about it. Cheers, On 02/07/2012, Keith Reedy <wa9...@gmail.com> wrote: > Slau, well said and quite correct. > Keith Reedy > Click the link below to download MP3's of Keith Reedy's music as a gift from > Bibles For The Blind. > > http://biblesfortheblind.org/download_music.shtml > > God gives His best to those who leave the choice with Him. J Hudson > Taylor. > > > > > On Jul 2, 2012, at 11:49 AM, Slau Halatyn wrote: > >> In this case, the only signals that are traveling between computer and >> interface are relatively small. The drive needs more of a direct >> connection to the CPU because it's doing more intensive processing. >> Regarding other signals reaching the interface, well, they're going >> directly to the interface via instrument/microphone cable, etc. >> >> Best, >> >> Slau >> >> On Jul 2, 2012, at 10:31 AM, Chris Norman wrote: >> >>> Why is that? >>> From what little I know of cabling, I thought the signal was stronger >>> and less latent the closer to the bus you were? so, with that logic, >>> you should have the audio interface first, so it's signal has less far >>> to travel? >>> >>> I'm obviously wrong with that assumption, but I'm interested as to why. >>> >>> Cheers. >>> >>> On 02/07/2012, Slau Halatyn <slauhala...@gmail.com> wrote: >>>> Yep, that's correct. while the 002 and 003 will work in reverse, at >>>> higher >>>> track counts, it gets hairy. The setup guides recommend the interfaces >>>> be >>>> the last in the chain. Separate busses are preferrable but on single >>>> busses, >>>> that's the deal. >>>> >>>> Slau >>>> >>>> On Jul 2, 2012, at 6:47 AM, Chris Norman wrote: >>>> >>>>> For the purposes of archiving, I'll reply anyways. I'm sure a while >>>>> back, Slau said if you do this, you have to put the hard drive first >>>>> in the chain, then the mBox. >>>>> >>>>> HTH, >>>>> >>>>> On 30/06/2012, Chris Snyder <ch...@chris-snyder.com> wrote: >>>>>> Thanks to Slau, this was solved. >>>>>> >>>>>> Friendly, >>>>>> Chris >>>>>> >>>>>> On Jun 29, 2012, at 12:35 PM, Chris Snyder wrote: >>>>>> >>>>>>> Hi all, >>>>>>> It's been a while since I posted here, but I have a couple of >>>>>>> questions. >>>>>>> I'm using a ProTools 9 MBox setup,. It requires the one firewire >>>>>>> port >>>>>>> on >>>>>>> my Macbook Pro. I have a firewire hard drive which I wish to use to >>>>>>> run >>>>>>> my >>>>>>> sessions. There is an extra firewire port on the back of the MBox. >>>>>>> Can >>>>>>> I >>>>>>> use this to dazychain my hard drive? When I try this, it doesn't >>>>>>> work. >>>>>>> Is >>>>>>> there something I must do to get it to work? >>>>>>> If this can't be done, can I use the USB function on this drive to >>>>>>> run >>>>>>> a >>>>>>> session, or will it be too slow? >>>>>>> >>>>>>> Thanks for your help. >>>>>>> >>>>>>> Friendly, >>>>>>> Chris >>>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Take care, >>>>> >>>>> Chris Norman. >>>>> >>>>> <!-- chris.norm...@googlemail.com --> >>>> >>>> >>> >>> >>> -- >>> Take care, >>> >>> Chris Norman. >>> >>> <!-- chris.norm...@googlemail.com --> >> > > -- Take care, Chris Norman. <!-- chris.norm...@googlemail.com -->
