[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Speechsc] Ambiguous description of BARGE-IN-OCCURRED in section 8.8
Hi,
I am reading draft-18 and I find description of BARGE-IN-0CCURRED
method hard to understand.
> 8.8. BARGE-IN-OCCURED
There is a typo.
> If a "SPEAK" request is active with kill-on-barge-in enabled, and the
> BARGE-IN-OCCURRED event is received, the synthesizer MUST immediately
> stop streaming out audio.
Must the synthesizer stop streaming out audio if a "SPEAK" request is
in "PAUSED" state?
I couldn't find a definition of "active SPEAK request". I guess it is
a current processed "SPEAK"?
> It MUST also terminate any speech requests
> queued behind the current active one, irrespective of whether they
> have barge-in enabled or not.
Does this statement depend on previous one? I.e. must the synthesizer
terminate all speech
requests queued behind the current one regardless of kill-on-barge-in
enabled in active "SPEAK"?
> If a barge-in-able "SPEAK" request was
> playing and it was terminated, the response MUST contain the an
> active-request-list header listing the request-ids of all "SPEAK"
> requests that were terminated. The server generates no
> "SPEAK-COMPLETE" events for these requests.
That sounds good. However, example in section 14.1 says something different:
> C->S: MRCP/2.0 289 SPEAK 543259
> Channel-Identifier:32AECB23433801 at speechsynth
> Kill-On-Barge-In:true
> Content-Type:application/ssml+xml
> Content-Length:418
> Content-Length:...
[...]
> S->C: MRCP/2.0 52 543259 200 IN-PROGRESS
> Channel-Identifier:32AECB23433801 at speechsynth
> Speech-Marker:timestamp=857207696314
[...]
> C->S: MRCP/2.0 69 BARGE-IN-OCCURRED 543259
> Channel-Identifier:32AECB23433801 at speechsynth
> Proxy-Sync-Id:987654321
>
> S->C: MRCP/2.0 72 543259 200 COMPLETE
> Channel-Identifier:32AECB23433801 at speechsynth
> Active-Request-Id-List:543258
> Speech-Marker:timestamp=857206096314
>
> S->C: MRCP/2.0 73 SPEAK-COMPLETE 543259 COMPLETE
> Channel-Identifier:32AECB23433801 at speechsynth
> Completion-Cause:001 barge-in
> Speech-Marker:timestamp=857207685213
Moreover, request BARGE-IN-OCCURRED has the same request-id
as previous SPEAK. Is this correct?
--
Slawomir Testowy