[ddots-l] Re: jaws reading sonar wrong
- From: "Gordon Kent" <dbmusic@xxxxxxxxxxxx>
- To: <ddots-l@xxxxxxxxxxxxx>
- Date: Wed, 2 May 2007 17:19:59 -0400
Omar:
Well, call me tomorrow. I want to hear this first hand. You may need to send
David a debug report or something.
Gord
----- Original Message -----
From: Omar Binno
To: ddots-l@xxxxxxxxxxxxx
Sent: Wednesday, May 02, 2007 8:47 AM
Subject: [ddots-l] Re: jaws reading sonar wrong
Gord, I don't have any of the tracks hidden.
Omar Binno
My Space: www.myspace.com/omarbinno
----- Original Message -----
From: Gordon Kent
To: ddots-l@xxxxxxxxxxxxx
Sent: Wednesday, May 02, 2007 12:00 AM
Subject: [ddots-l] Re: jaws reading sonar wrong
Honestly I can't imagine why. Ct is getting its information from the
special accessibility window that cakewalk has given us. Have you accidentally
hidden some tracks or something?
Gord
----- Original Message -----
From: Omar Binno
To: ddots-l@xxxxxxxxxxxxx
Sent: Tuesday, May 01, 2007 5:00 PM
Subject: [ddots-l] jaws reading sonar wrong
Hi:
I've gone through the ct setup for sonar, and have made sure that all the
proper things are checked and unchecked, but sometimes, when I'm using the up
and down arrow keys to go from track 13 to 14 for example, jaws is not reading
things properly. For example, if I'm on track 13, and hit the down arrow, jaws
will say "rapped up to track 12," when it should be saying "track 14." Also, if
I'm on the volume field of track 13, then I hit the down arrow, Jaws will say
"preview mode," or "solo is off." This is not making sense, when it should be
on the volume field of track 14, which I arrowed down to.
Any thoughts as to why this may be happening?
Omar Binno
My Space: www.myspace.com/omarbinno
Other related posts:
