[sib-access] Re: NumPad Reporting Issues
- From: Kevin L Gibbs <kevjazz@xxxxxx>
- To: sib-access@xxxxxxxxxxxxx
- Date: Fri, 02 Mar 2012 16:01:50 -0600
I doubt it's in the Sib manual. It's something that only relates to us.
Remember that, in the case of the tie, the tie is actually inserted, even
though the user is one position to the right of the note to which the tie has
been appended. I have just tested the sharp scenario as you describe. In this
case, unlike the case of the tie, I have enough vision to report that the sharp
actually is not inserted even though JAWS reports the presence or absence of a
sharp alternately. No idea why I don't see a sharp but do see a tie.
Best,
Kevin
On Mar 2, 2012, at 3:57 PM, Farfar on a Friday wrote:
> Kevin,
>
> Exactly what I get, also. In fact if you experiment with entering a note and
> then pressing 8 for a sharp, it will say "sharp" but one will not be
> applied. That's even more confusing in my mind. You have to go back to the
> note and press sharp before it actually gets applied.
>
> This must all stem (pardon the pun) from a note entry as being an incomplete
> action until we move off the note, and that articulations and accidentals
> don't get added until we land on a completed entry.
>
> Of course if I had just entered an A# note instead of A then # I would have
> had what I wanted in the first place.
>
> Good observation, Kevin. I'll see if there is some deeper explanatory text
> in the manual.
>
>
> Dave Carlson
> Tastefully composed and transmitted from somewhere in the Western United
> States, using a Dell Latitude E6520 and Windows 7
>
>
> ----- Original Message -----
> From: "Kevin L Gibbs" <kevjazz@xxxxxx>
> To: <sib-access@xxxxxxxxxxxxx>
> Sent: Friday, March 02, 2012 13:49
> Subject: [sib-access] Re: NumPad Reporting Issues
>
>
> Dave,
> I think I've come up with the reason why at least some of us have this bogus
> report of no tie when the tie is, in fact inserted where you want it. I
> have enough vision to have tested this and I have found the results
> consistent.
> 1. Play a note on your MIDi keyboard and then immediately after playing
> that note, press the numpad enter button for a tie in the common notes
> template. when I say immediately, I merely mean that the tie command should
> be your next keystroke. Feel free to allow as much time to elapse as you
> wish between playing the note and pressing the tie. JAWS will say "No Tie."
> In fact, the tie is inserted. However, because the insertion point has
> moved to the next note entry position, JAWS correctly reports that you can't
> insert a tie without a note.
> 2. However, if after inserting your note, you then immediately left arrow
> once so that you are actually on the note instead of having moved to the
> next entry position, pressing the numpad enter key will consistently report
> tie or no tie correctly depending on the actual state of things at that
> position. Everybody should check this out and see if the results I'm
> describing are what you experience. If you do get the results I've
> described, consistently, then all is working well.
> Kevin
> On Mar 1, 2012, at 5:43 PM, Farfar wrote:
>
>> I'm thinking along the lines more and more that the problem being reported
>> is graphics or color related, due to display settings on specific
>> machines.
>>
>> The reason I think this is because of the old Sibelius 3 and the
>> SibSpeaking
>> interface. For those of you who remember setting up SibSpeaking, there was
>> a
>> large amount of time spent in training SibSpeaking to correctly recognize
>> all the numpad graphics and their on/off states.
>>
>> When one of the numpad keys is pressed, a graphic changes color or shape,
>> or
>> something, and Sib Access is somehow reading this change and reporting the
>> new state. Unless Dan Rugman has come up with a very different approach,
>> this dependency on correctly reading the graphics may still be necessary.
>>
>> In fact, it's not only when pressing one of the keys, but also when
>> navigating through the score, that Sib Access is reading note durations
>> and
>> other enhancements via graphics on the keypad changing. At least I'm
>> presuming this.
>>
>>
>> One idea I have for you to try (for those with this problem) is to make
>> sure
>> you've not only run your registry keys again, but that you've also made
>> sure
>> you copied all the JAWS files to the correct folder (your Settings/ENU
>> folder for your user settings). I think Dan provided a graphics identifier
>> file (Perhaps .JGF) with all the secrets contained there.
>>
>> Add this to my earlier tips on screen resolution and color settings, and
>> that should keep you busy trying out different permutations.
>>
>> Maybe Dan will chime in to put me straight.
>>
>>
>> Dave Carlson
>> Tastefully composed and transmitted from somewhere in the Western United
>> States, using a Dell Latitude E6520 and Windows 7
>>
>> If you wish to unsubscribe, send a blank message
>> with the single word, unsubscribe - in the Subject line to:
>> sib-access-request@xxxxxxxxxxxxx
>
> If you wish to unsubscribe, send a blank message
> with the single word, unsubscribe - in the Subject line to:
> sib-access-request@xxxxxxxxxxxxx
>
> If you wish to unsubscribe, send a blank message
> with the single word, unsubscribe - in the Subject line to:
> sib-access-request@xxxxxxxxxxxxx
If you wish to unsubscribe, send a blank message
with the single word, unsubscribe - in the Subject line to:
sib-access-request@xxxxxxxxxxxxx
Other related posts:
