Re: speechSynthesizer willSpeakWord trouble
Re: speechSynthesizer willSpeakWord trouble
- Subject: Re: speechSynthesizer willSpeakWord trouble
- From: Andy Lee <email@hidden>
- Date: Sat, 7 Jul 2007 01:43:02 -0400
On Jul 6, 2007, at 10:19 PM, Paul Bruneau wrote:
On Jul 6, 2007, at 8:22 PM, Ricky Sharp wrote:
Output (I'm limiting this to only the last word) is:
Range: {15, 11}
Speaking: (null)
willSpeakPhoneme 33
willSpeakPhoneme 8
<7 more opcodes snipped>
willSpeakPhoneme 32
willSpeakPhoneme 0
didFinishSpeaking YES
the "willSpeakWord" delegate should have been given strings of
"Test", "Speech" and "Synthesizer".
Ricky, thank you so much! My concern in this was that I was doing
something wrong. I was only experimenting with these methods
because it was fun and I wanted to make sure I was doing things
(mostly) right.
When the problem first showed up, I actually thought to myself "I
bet I could stash the spoken string somewhere and retrieve it to
use with the correctly-returned NSRange" but I didn't want to work
around my own mistake.
I didn't see the sample code that you referred to, but I'll look
for it. Interesting that they worked around the situation with
their own sample code! Why did they make the parameter if they were
just going to leave it nil I wonder?
Probably a bug, not deliberate. I haven't looked at the sample code,
but if they were working around a known bug they SHOULD have said so
in a comment. I reproduced it too, and I agree with Ricky: file a
bug on this (both the sample code needing a comment, and the bug
itself), and maybe post on the speech-dev list in case it's a known
issue or there's some sensible explanation other than a bug (which I
doubt).
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden