Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update TTS guide related to completed callback #1917

Merged
merged 3 commits into from
May 17, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
19 changes: 18 additions & 1 deletion docs/application/dotnet/guides/uix/tts.md
Original file line number Diff line number Diff line change
Expand Up @@ -243,7 +243,24 @@ Event handlers can be set for the following events of the [Tizen.Uix.Tts.TtsClie

- Utterance started or completed

If you add text in TTS, that text is handled as an utterance and it obtains its own ID. After you request the TTS process to start, the text is synthesized by an engine and played. To get a notification when an utterance is started or completed, register event handlers for the `UtteranceStarted` and `UtteranceCompleted` events, respectively:
If you add text in TTS, that text is handled as an utterance and it obtains its own ID. After you request the TTS process to start, the text is synthesized by an engine and played. Each event handler is invoked in the following cases:

| Event handler | Invoked when | TTS state |
| :------------------: | :---------------------------------------: | :-------: |
| `UtteranceStarted` | Playing the synthesized audio is started | `Ready` > `Playing` |
| `UtteranceCompleted` | Playing the synthesized audio is finished | `Playing` (The state is NOT changed until `Stop()` is called.) |

> [!NOTE]
> `UtteranceCompleted` is NOT invoked when the following occurs:
>
> (1) Your application calls `Stop()`.
>
> (2) Playing the synthesized audio is stopped by another application.
>
> Although the `UtteranceCompleted` event handler is not invoked, a `StateChanged` event handler will be invoked. (The state will be changed from `Playing` to `Ready`.)


To get a notification when an utterance is started or completed, register event handlers for the `UtteranceStarted` and `UtteranceCompleted` events, respectively:

```csharp
/// Utterance started event handler
Expand Down
19 changes: 18 additions & 1 deletion docs/application/native/guides/text-input/tts.md
Original file line number Diff line number Diff line change
Expand Up @@ -262,7 +262,24 @@ To set and unset callbacks, follow these steps:

- Utterance started or completed

If you add text in TTS, that text is handled as an utterance and it obtains its own ID. After you request the TTS process to start, the text is synthesized by an engine and played out. To get a notification when an utterance is started or completed, set the respective callbacks:
If you add text in TTS, that text is handled as an utterance and it obtains its own ID. After you request the TTS process to start, the text is synthesized by an engine and played out. Each callback is invoked in the following cases:

| Callback | Invoked when | TTS state |
| :--------------------------: | :---------------------------------------: | :-------: |
| Utterance started callback | Playing the synthesized audio is started | `TTS_STATE_READY` > `TTS_STATE_PLAYING` |
| Utterance completed callback | Playing the synthesized audio is finished | `TTS_STATE_PLAYING` (The state is NOT changed until `tts_stop()` is called.) |

> [!NOTE]
> Utterance completed callback is NOT invoked when the following occurs:
>
> (1) Your application calls `tts_stop()`.
>
> (2) Playing the synthesized audio is stopped by another application.
>
> Although the utterance completed callback is not invoked, a state changed callback will be invoked. (The state will be changed from `TTS_STATE_PLAYING` to `TTS_STATE_READY`.)


To get a notification when an utterance is started or completed, set the respective callbacks:

```cpp
/* Started callback */
Expand Down