I'm assuming you've tried asking about this on the jSonar list? Not suggesting it's jSonar causing this, but they're a pretty knowledgeable bunch of chaps over there from what I've seen.
Other than that, just to reiterate what others are saying about Jaws being evil at times. I realise you're gonna have issues using jSonar with another screen reader, but grabbing a demo of version 10 could do you no harm. If nothing else, it'll let you say with absolute certainty that it's not freedom scientific's fault, and using that phrase with proof makes you a bit exclusive lol. Scott On 1/29/09, Scott Howell <[email protected]> wrote: > I agree, I think I'd try another screen reader just to see what happens. > Scott Howell > [email protected] > > > > On Jan 29, 2009, at 5:36 PM, Karen Lewellen wrote: > >> actually given how finicky Jaws can be in general, it is highly >> possible that the older edition is creating the conflict, making >> the suggestion very relevant indeed. >> Unless you know others running the exact same setup using this >> edition of jaws, why is the suggestion of an upgrade unimportant? >> it looks like you are using hardware and configurations that are >> more recent than the screen reader. >> >> Karen >> >> On Thu, 29 Jan 2009, Cameron wrote: >> >>> Hi. Not sure what that has to do with this particular issue, >>> however, since >>> you brought it up, I did call freedom sscientific about that last >>> week and >>> they said they can only upgrade me to the latest version, ten, >>> which would >>> cost me approx $550. That ended the call pretty freaking quickly. >>> >>> Cameron. >>> >>> >>> >>> >>> >>> -----Original Message----- >>> From: [email protected] >>> [mailto:[email protected]] On Behalf Of David >>> Poehlman >>> Sent: Thursday, January 29, 2009 6:45 AM >>> To: General discussions on all topics relating to the use of Mac OS >>> X by the >>> blind >>> Subject: Re: issues with mac book pro and Tascam FW1884 running win >>> xp pro >>> sp3,jaws, sonar 6pe, with bootcamp. >>> >>> one thing you need to do is upgrade your jaws to at least 8. >>> >>> On Jan 29, 2009, at 1:26 AM, Cameron wrote: >>> >>> Hi everyone. This is driving me insane. I am out of ideas on what >>> to >>> do. >>> Any tips would be greatly appreciated. >>> >>> >>> >>> Here is my setup. Mac book pro, 2.4ghz intel core 2 duo processor, >>> 200gb >>> hd, 2gb ddr 2 ram, texas instruments firewire chipset, using bootcamp >>> to run >>> windows xp pro service pack 3. I am using the Tascam FW1884 in >>> native >>> mode >>> in sonar 6 producer edition, and I am using jaws seven. >>> >>> >>> >>> Now, I sold my white mac book recently due to the lucent chipset not >>> being >>> compatible with various firewire audio interfaces etc. >>> >>> >>> >>> All signs pointed to the mac book pro with the ti firewire chipset >>> being the >>> solution. >>> >>> >>> >>> This is not the new aluminum series mac book pro by the way, it's an >>> early >>> 08 model. >>> >>> >>> >>> I've been doing a lot of research and was aware of the speed issue >>> with the >>> combination 400/800 firewire port in win xp sp2 and sp3. I managed >>> to >>> edit >>> the chipset device properties in the registry an the sidspeed is now >>> set at >>> 2, which is the default for a firewire 400 device. >>> >>> >>> >>> I also went into the device manager and disabled wireless, the >>> firewire >>> network adaptor, and Bluetooth. >>> >>> >>> >>> According to the posts I've read on various forums, this should have >>> solved >>> my problem. >>> >>> >>> >>> After resetting the sidspeed, I get audio playback, of a stereo >>> file in >>> winamp for example. However, when I open a sonar session, even when >>> there >>> are just say four or six audio tracks, it takes about ten seconds for >>> playback to begin. Also, I am getting many instances of jaws >>> freezing. >>> Like the soft synth gets stuck. >>> >>> >>> >>> Everything in sonar is set as it should be and I selected acio >>> drivers >>> instead of wdm. >>> >>> >>> >>> However, when I closed sonar and relaunched it, it said that my bit >>> rate and >>> sample rate have been reset to 16 bit 44.1k because the settings were >>> not >>> compatible with the device drivers. >>> >>> >>> >>> In the tascam's control panel I seem to need the latency at 100 >>> percent or >>> at least above fifty or I get dropouts every few seconds. >>> >>> >>> >>> And yes, I have the latest firmware installed for the fw1884 and I >>> have the >>> latest sonar driver installed for it. >>> >>> >>> >>> This is driving me insane. >>> >>> >>> >>> I am running out of things to try. >>> >>> >>> >>> Any help would be greatly appreciated. Please feel free to forward >>> this to >>> anyone who may have a solution. >>> >>> >>> >>> Thanks, >>> >>> >>> >>> Cameron. >>> >>> >>> >>> >>> >>> >> > > >
