Forums
New posts
Articles
Product Reviews
Policies
FAQ
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Menu
Log in
Register
Install the app
Install
Forums
General Discussions
Switcher Hangout (Windows to Mac)
How to fully kill text-to-speech?
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="nuclear.glow" data-source="post: 1224110" data-attributes="member: 199282"><p><em>I have other ideas for your problem, but since they are rather obvious to me, I'll spare insulting you with the suggestions.</em></p><p></p><p>I can play some tapes with fake US talkshow applause if you need cuddling. I translate it as "I have no suggestion, only the illusion thereof". Having said that, my original reply was not right and I ought to be man enough apologise for that, so hereby. I cannot go into the circumstances, but I should have known better than to post after a long day.</p><p></p><p><em>To all others, please don't indulge this troll any further.</em></p><p></p><p>Yes, mein Fuehrer. So glad you take it upon yourself to command the unruly hordes. Anyway, I'll skip this before you trigger any other bad traits in me (I'm only human).</p><p></p><p>There is a subsystem in OSX which one specific App triggers even though disables in the System preferences. This suggests the subsystem remains active, relying on the applications to follow system preferences but not enforcing it. Some people have posted working solutions for OSX 10.5.8, but they do not appear to work for OSX 10.6.7 (which also implies that solving it may only offer temporary relief as 10.7 is around the corner).</p><p></p><p>There are three routes to address it:</p><p></p><p>- get the application to stop calling the subsystem. Reported to the authors, but I don't expect much of it as I found reports of this bug as far back as 2009 which suggests it may be an unwanted interaction which is complex to fix.</p><p></p><p>- enforce the preferences as set in the System Preferences. This gets interesting as there are two locations handling the subsystem, but neither has a kill switch for the functionality (an approach which is strangely MS Windows compatible). There is thus no means to enforce it from a standard UI perspective, but one may exist in command line controls as shown in 10.5.8.</p><p></p><p>- rip out the entire subsystem, leaving in place dummy APIs so apps that do call upon the functionality don't hang or otherwise need changing. In hindsight not possible despite being the best option (you cannot activate what isn't there) as it's IMHO not viable to do this without the potential for future problems.</p><p></p><p>Alternatively, I could avoid using Front Row, of course. I don't use it much, but I wanted to see what it could do as I was considering an Apple TV, which is when I stumbled upon this problem.</p></blockquote><p></p>
[QUOTE="nuclear.glow, post: 1224110, member: 199282"] [I]I have other ideas for your problem, but since they are rather obvious to me, I'll spare insulting you with the suggestions.[/I] I can play some tapes with fake US talkshow applause if you need cuddling. I translate it as "I have no suggestion, only the illusion thereof". Having said that, my original reply was not right and I ought to be man enough apologise for that, so hereby. I cannot go into the circumstances, but I should have known better than to post after a long day. [I]To all others, please don't indulge this troll any further.[/I] Yes, mein Fuehrer. So glad you take it upon yourself to command the unruly hordes. Anyway, I'll skip this before you trigger any other bad traits in me (I'm only human). There is a subsystem in OSX which one specific App triggers even though disables in the System preferences. This suggests the subsystem remains active, relying on the applications to follow system preferences but not enforcing it. Some people have posted working solutions for OSX 10.5.8, but they do not appear to work for OSX 10.6.7 (which also implies that solving it may only offer temporary relief as 10.7 is around the corner). There are three routes to address it: - get the application to stop calling the subsystem. Reported to the authors, but I don't expect much of it as I found reports of this bug as far back as 2009 which suggests it may be an unwanted interaction which is complex to fix. - enforce the preferences as set in the System Preferences. This gets interesting as there are two locations handling the subsystem, but neither has a kill switch for the functionality (an approach which is strangely MS Windows compatible). There is thus no means to enforce it from a standard UI perspective, but one may exist in command line controls as shown in 10.5.8. - rip out the entire subsystem, leaving in place dummy APIs so apps that do call upon the functionality don't hang or otherwise need changing. In hindsight not possible despite being the best option (you cannot activate what isn't there) as it's IMHO not viable to do this without the potential for future problems. Alternatively, I could avoid using Front Row, of course. I don't use it much, but I wanted to see what it could do as I was considering an Apple TV, which is when I stumbled upon this problem. [/QUOTE]
Verification
Post reply
Forums
General Discussions
Switcher Hangout (Windows to Mac)
How to fully kill text-to-speech?
Top