I have always figured that a single thread would be enough for handling speech output, simply because the output itself is serial in nature. I would, however, think that this single thread should be a thread unto itself and not the same as an application main thread. In your analogy, there is only one microphone by which an order can be relayed from the customer counter to the cooks in the back. In that case, adding more customer service people really won't help much, because they will each then have to wait for a free moment on the mic to say something. To make this as similar to our real case as possible, customers convey their orders by entering them on devices that place the requests on a back-facing screen for the customer service person, or persons, to read. It's fine for there to be five devices, but the amount of work required to read a device aloud is so small as not to warrant having five people to do it. I say this is parallel to our actual case, because the work required to request that a phrase be spoken is similarly small as far as I know.
On Mon, Jun 30, 2025 at 09:22:11PM +0530, Krishnakant Mane wrote: So here’s a simple analogy. You are in a hotel and want to order something. There are other customers too. There is only one waiter and he is busy taking some order. Until he finishes taking that order you will not be able to place yours. Meaning one task has to complete before other comes in. So everyone is in queue . But if there are more than one voters then you have a fair chance of giving your order as well at the same time. Also imagine from the waiter’s end, Until he takes the first order, he is not going to listen to you, rather he will not be able to. So in this case Voice over is in that same situation. There are quick inputs coming to VoiceOver from several apps, many actions in that app and other stuff. If tasks happen very fast then VoiceOver is able to take the next set of commands and process them very quickly. But a few micro seconds here and there and a lag is obvious. If this propagates then those micro seconds will build up and at the end vo is going to be very very angry and go on a strike (I can’t take these many orders at once ). But if VO works in multiple threaded mode, meaning it can spin two or more vaiters at a time (this usually is default case with all apps because they can use multiple processors or some other technique ), then it can take in more orders and work fast and efficient. Right now that’s not the case so quick switching of apps and having less processing power will make it slow. Imagine a difference between m1 and m3 as the space between tables for the waiter to pass. If it is narrow then waiter will take more time to reach other tables, add to the fact that he is alone. Now I hope you get it. Regards. > On 30 Jun 2025, at 8:54 PM, E.T. <[email protected]> wrote: > > Please explain single threaded. Appreciate it. > > > From E.T.'s Keyboard... > Reality.sys corrupted. Universe halted. Reboot(Y/N) ? > > My e-Mail: > [email protected] > > On 6/30/2025 8:14 AM, Krishnakant Mane wrote: >> It is highly possible because M1 is a bit old for this OS. >> Add to it the fact that VoiceOver is still single threaded. >> I don’t face this on M3 with 16 gb ram at all, so I guess it’s the >> performance lag plus the single threaded nature. >> Regards. >> >>> On 30 Jun 2025, at 7:47 PM, 'Andrew' via MacVisionaries >>> <[email protected]> wrote: >>> >>> Hi, >>> >>> Sincee the latest update to Sequoia 15.5, Voiceover often crashes >>> unexpectedly. I lose speech and I have to restart Voiceover or even >>> brutally shut down my macbook air and reboot in order to regain voiceover >>> functionality.. Has anybody else experienced this behaviour? I am not >>> sure what causes it but sometimes I have a feeling that if I do something >>> quickly on my macbook air like switch from one application to another, or >>> open and close a Mail message quickly, this might result in Voiceover crash. >>> >>> Andrew -- Doug Lee [email protected] http://www.dlee.org "Sometimes I think my learning curve is a circle." -- David Andrews -- The following information is important for all members of the Mac Visionaries list. If you have any questions or concerns about the running of this list, or if you feel that a member's post is inappropriate, please contact the owners or moderators directly rather than posting on the list itself. Your Mac Visionaries list moderator is Mark Taylor. You can reach mark at: [email protected] and your owner is Cara Quinn - you can reach Cara at [email protected] The archives for this list can be searched at: http://www.mail-archive.com/[email protected]/ --- You received this message because you are subscribed to the Google Groups "MacVisionaries" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/macvisionaries/20250630164226.dttx5a5bujduqcqk%40dlee.org.
