Re: [Emacspeak] Any solutions for the queuing issue in Swiftmac?

[Jerry Sievers <gsievers19@xxxxxxxxxxx>]

Daniil, et al; A few followup remarks inline starting a couple
paragraphs down.

"Daniil Gusev" (via emacspeak Mailing List) <emacspeak@xxxxxxxxxxxxx>
writes:

> Jerry, thank you for such a detailed review, it is truly valuable.
>
> I will try to reproduce that inconsistency in page voicing you mentioned and fix it if possible.
> It would be amazing if you could describe step by step what actions
> you take, what result you expect to hear, and what actually
> happens. This would help a lot in figuring it out.

Thus far I have not had the time or focus to retest again the nsspeaker
but am still planning to do so.

After my last update, I did enable it again and ran for a few hours to
observe that for some reason the absence of full page reading when
navigating in info mode buffers did *not* occur.  So that was good but
puzzling.

I can only describe that particular test in general terms which follow.

Compared to SwiftMAc, nsspeaker is much better behaved in regards to
timeliness of queue flushing on rapid navigation.  (But that was already
reported.)

ON more extended use, I noted that the pitch rise on capital letters and
such was too faint to be easily noticeable, and that there seemed to be
far less auditory icon and tonal activity.

Indeed the 2-channel feature is useful and perhaps near essential on
modern Emacspeak.

Bottom line...  nsspeaker in spite of its strengths, seems to be lacking
enough at the same time as to prevent it from being a strong adoption
candidate.

Keep the faith!!  I intend to post again with the details you are
wishing for.

I'd be curious to know what tools/methods you employed in developing
nsspeaker.

Thanks again 

> As for side-channel notifications, so far I haven't been able to find
> information about this in the emacspeak documentation to understand
> what it represents, how it should work, and how to implement it in the
> code.
> If I end up finding nothing, I will look into the source code of one
> of the existing speech servers and, if such an option might be in
> demand, implement something similar.
>
> Regarding distribution via homebrew, there is absolutely no obstacle
> to this for nsspeaker either, but I suppose it makes sense to first
> make sure the tool is actually useful, more or less stable, and has
> all the necessary functionality, after which adding convenient
> distribution methods won't take much time.
>
> It will be very interesting to hear about your further observations
> and experiments with nsspeaker, and thank you once again for taking
> the time for this.
>
> Daniil
>
> Emacspeak discussion list -- emacspeak@xxxxxxxxxxxxx
> To unsubscribe send email to:
> emacspeak-request@xxxxxxxxxxxxx with a subject of: unsubscribe