Skip to content

Commit dc4e2be

Browse files
committed
Removed Windows Voice Assistant mentions
1 parent ee75fed commit dc4e2be

6 files changed

+23
-37
lines changed

articles/cognitive-services/Speech-Service/toc.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -424,9 +424,9 @@
424424
items:
425425
- name: Voice assistants FAQ
426426
href: faq-voice-assistants.md
427-
- name: Windows voice assistants
427+
- name: Voice assistants on Windows
428428
items:
429-
- name: What is a Windows voice assistant?
429+
- name: Overview of voice assistants on Windows
430430
href: windows-voice-assistants-overview.md
431431
- name: How-to guides
432432
items:

articles/cognitive-services/Speech-Service/windows-voice-assistants-automatic-enablement-guidelines.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -12,13 +12,13 @@ ms.date: 04/15/2020
1212
ms.author: travisw
1313
---
1414

15-
# Privacy guidelines for Windows Voice Assistants
15+
# Privacy guidelines for voice assistants on Windows
1616

1717
## About voice activation privacy
1818

1919
It's important that users are given clear information about how their voice data is collected and used and important that they are given control over if and how this collection happens. These core facets of privacy -- *disclosure* and *consent* -- are especially important for voice assistants integrated into Windows given the always-listening nature of their use.
2020

21-
Developers creating Windows Voice Assistants must include clear user interface elements within their applications that reflect the listening capabilities of the assistant.
21+
Developers creating voice assistants on Windows must include clear user interface elements within their applications that reflect the listening capabilities of the assistant.
2222

2323
> [!NOTE]
2424
> Failure to provide appropriate disclosure and consent for an assistant application, including after application updates, may result in the assistant becoming unavailable for voice activation until privacy issues are resolved.
@@ -59,4 +59,4 @@ Once these requirements are satisfied, an eligible assistant application will ap
5959
## Next steps
6060

6161
> [!div class="nextstepaction"]
62-
> [Learn about best practices for Windows Voice Assistants](windows-voice-assistants-best-practices.md)
62+
> [Learn about best practices for voice assistants on Windows](windows-voice-assistants-best-practices.md)

articles/cognitive-services/Speech-Service/windows-voice-assistants-implementation-guide.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -42,14 +42,13 @@ The application needs to register itself, its keyword model, and its language wi
4242
Start by retrieving the keyword detector. In this sample code, we retrieve the first detector, but you can select a particular detector by selecting it from `configurableDetectors`.
4343

4444
```csharp
45-
private static async Task<ActivationSignalDetector> GetFirstEligibleDetectorAsync(
46-
string dataFormat)
45+
private static async Task<ActivationSignalDetector> GetFirstEligibleDetectorAsync()
4746
{
4847
var detectorManager = ConversationalAgentDetectorManager.Default;
4948
var allDetectors = await detectorManager.GetAllActivationSignalDetectorsAsync();
5049
var configurableDetectors = allDetectors.Where(candidate => candidate.CanCreateConfigurations
5150
&& candidate.Kind == ActivationSignalDetectorKind.AudioPattern
52-
&& (string.IsNullOrEmpty(dataFormat) || candidate.SupportedModelDataTypes.Contains(dataFormat)));
51+
&& (candidate.SupportedModelDataTypes.Contains("MICROSOFT_KWSGRAPH_V1")));
5352

5453
if (configurableDetectors.Count() != 1)
5554
{

articles/cognitive-services/Speech-Service/windows-voice-assistants-overview.md

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title:
33
Voice Assistants on Windows - Overview
44
titleSuffix: Azure Cognitive Services
5-
description: An overview of the Windows voice assistant platform, including capabilities and development resources available.
5+
description: An overview of the voice assistants on Windows, including capabilities and development resources available.
66
services: cognitive-services
77
author: cfogg6
88
manager: trrwilson
@@ -13,9 +13,7 @@ ms.date: 04/15/2020
1313
ms.author: travisw
1414
---
1515

16-
# Overview
17-
18-
## Voice Assistants on Windows
16+
# Voice Assistants on Windows
1917

2018
On Windows 10 version 2004 and up, voice assistant applications can take advantage of the Windows ConversationalAgent APIs to achieve a complete voice-enabled assistant experience.
2119

@@ -29,5 +27,5 @@ On Windows 10 version 2004 and up, voice assistant applications can take advanta
2927
## Getting Started
3028

3129
- **Review the design guidelines:** Our [design guidelines](windows-voice-assistants-best-practices.md) lay out the key work required to provide the best possible experiences for voice activation on Windows 10.
32-
- **Visit the Getting Started Guide:** Start [here](windows-voice-assistants-get-started.md) for the steps to begin implementing voice assistants on Windows, from setting your development environment through an introduction to the UWP Voice Assistant Sample.
30+
- **Visit the Getting Started Guide:** Start [here](how-to-windows-voice-assistants-get-started.md) for the steps to begin implementing voice assistants on Windows, from setting your development environment through an introduction to the UWP Voice Assistant Sample.
3331
- **Try out the sample app**: To experience these capabilities firsthand, visit the [UWP Voice Assistant Sample](windows-voice-assistants-sample-info.md) page and follow the steps to get the sample client running.

articles/cognitive-services/Speech-Service/windows-voice-assistants-sample-info.md

Lines changed: 5 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -15,19 +15,14 @@ ms.author: travisw
1515

1616
# The UWP Voice Assistant sample
1717

18-
## Overview
18+
The UWP Voice Assistant sample is a voice assistant on Windows that serves to
1919

20-
The UWP Voice Assistant sample is a Windows Conversational Agent application that serves to
21-
- demonstrate the use of the Windows Conversational Agent SDK
20+
- demonstrate the use of the Windows ConversationalAgent APIs
2221
- display best practices for a voice agent on Windows
2322
- provide an adaptable app and reusable components for your MVP agent application
24-
- show how to use Direct Line Speech together with the Windows Conversational Agent system for an end-to-end voice agent experience
23+
- show how Direct Line Speech, along with Bot Framework or Custom Commands, can be used together with the Windows ConversationalAgent APIs for an end-to-end voice agent experience
2524

2625
The documentation provided with the sample app walks through the code path of voice activation and agent management, from the prerequisites of startup through proper cleanup.
2726

28-
## Links
29-
[The UWP Voice Assistant Sample](https://aka.ms/MVA/sample)
30-
31-
[Readme with startup instructions](https://github.com/Azure-Samples/Cognitive-Services-Voice-Assistant/blob/master/clients/csharp-uwp/README.md)
32-
33-
["Docs" folder with additional documentation]()
27+
> [!div class="nextstepaction"]
28+
> [Visit the Github repo for the UWP Sample](https://aka.ms/MVA/sample)

articles/cognitive-services/Speech-Service/windows-voice-assistants-voice-activation.md

Lines changed: 8 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -13,48 +13,42 @@ ms.date: 04/15/2020
1313
ms.author: travisw
1414
---
1515

16-
# Voice Activation
17-
18-
## Walk through of voice activation
16+
# Walk through of voice activation
1917

2018
Windows supports voice activation for UWP applications. The following summarizes the steps of the voice activation process, including the steps an application must take to register as activatable by voice.
2119

22-
### Agent Activation Runtime
20+
## Agent Activation Runtime
2321

2422
The Agent Activation Runtime (AAR) is the ongoing process in Windows that manages application activation on a spoken keyword or button press. It starts with Windows as long as there is at least one application on the system that is registered with the system. Applications interact with AAR through the ConversationalAgent APIs in the Windows SDK.
2523

26-
### Registration
24+
## Registration
2725

2826
The first time a voice activated application is run, it registers its app id and keyword information in a global signal configuration mapping through the ConversationalAgent APIs. Keyword information includes the location of the keyword model file, the language the keyword is in, and an ID to assign to the keyword. AAR registers all configurations in the global mapping with the hardware or software keyword spotter on the system, allowing them to detect the application's keyword.
2927

3028
The application also [registers with the Background Service](https://docs.microsoft.com/windows/uwp/launch-resume/register-a-background-task), another process within Windows.
3129

3230
Note that this means an application cannot be activated by voice until it has been run once and registration has been allowed to complete.
3331

34-
### Activation
32+
## Activation
3533

3634
When the user speaks a keyword, the software or hardware keyword spotter on the system notifies AAR that a keyword has been detected, providing a keyword ID. AAR in turn uses the keyword ID to look up the ActivationSignalDetectorConfiguration application ID in its mapping. To activate the app, AAR sends a request to BackgroundService to start the application with the corresponding application ID.
3735

38-
### Receiving an activation
36+
## Receiving an activation
3937

4038
Upon receiving the request from AAR, the Background Service launches the application. The application receives a signal through the OnBackgroundActivated life cycle method in App.xaml.cs with a unique event argument. This tells the application that it was activated by AAR and should act accordingly.
4139

42-
### Keyword verification
40+
## Keyword verification
4341

4442
The keyword spotter that triggered the application to start has achieved low power consumption by simplifying the keyword model. This allows the keyword spotter to be "always on" without a high power impact, but it also means the keyword spotter will likely have a high number of "false accepts" where it detects a keyword even though no keyword was spoken. This is why the voice activation system launches the application in the background: to give the application a chance to verify that the keyword was spoken before interrupting the user's current session. AAR saves the audio since a few seconds before the keyword was spotted and makes it accessible to the application. The application can use this to run a more reliable keyword spotter on the same audio.
4543

46-
### Foreground Activation
44+
## Foreground Activation
4745

4846
If the application successfully verifies the keyword, it can make a request to be shown in the foreground and display UI.
4947

50-
### Voice activation while app is active
48+
## Voice activation while app is active
5149

5250
AAR still signals active applications when their keyword is spoken. Rather than signalling through the life cycle method in App.xaml.cs, though, it signals through an event in the ConversationalAgent APIs.
5351

54-
## Voice Activation Example
55-
56-
For a walk through of example code that completes registration and handles voice activation and keyword verification, visit the [UWP Voice Assistant Sample App](windows-voice-assistants-sample-info.md).
57-
5852
## Next steps
5953

6054
> [!div class="nextstepaction"]

0 commit comments

Comments
 (0)