You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/ai-services/speech-service/personal-voice-create-consent.md
+47-1Lines changed: 47 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ author: eric-urban
6
6
manager: nitinme
7
7
ms.service: azure-ai-speech
8
8
ms.topic: how-to
9
-
ms.date: 12/1/2023
9
+
ms.date: 1/10/2024
10
10
ms.author: eur
11
11
---
12
12
@@ -28,8 +28,54 @@ You can get the consent statement text for each locale from the text to speech G
28
28
"I [state your first and last name] am aware that recordings of my voice will be used by [state the name of the company] to create and use a synthetic version of my voice."
29
29
```
30
30
31
+
## Add consent from a file
32
+
33
+
In this scenario, the audio files must be available locally.
34
+
35
+
To add consent to a personal voice project from the URL of an audio file, use the `Consents_Create` operation of the custom voice API. Construct the request body according to the following instructions:
36
+
37
+
- Set the required `projectId` property. See [create a project](./personal-voice-create-project.md).
38
+
- Set the required `voiceTalentName` property. The voice talent name can't be changed later.
39
+
- Set the required `companyName` property. The company name can't be changed later.
40
+
- Set the required `audiodata` property with the consent audio file.
41
+
- Set the required `locale` property. This should be the locale of the consent. The locale can't be changed later. You can find the text to speech locale list [here](/azure/ai-services/speech-service/language-support?tabs=tts).
42
+
43
+
Make an HTTP POST request using the URI as shown in the following `Consents_Create` example.
44
+
- Replace `YourResourceKey` with your Speech resource key.
45
+
- Replace `YourResourceRegion` with your Speech resource region.
46
+
- Replace `JessicaConsentId` with a consent ID of your choice. The case sensitive ID will be used in the consent's URI and can't be changed later.
You should receive a response body in the following format:
53
+
54
+
```json
55
+
{
56
+
"id": "JessicaConsentId",
57
+
"description": "Consent for Jessica voice",
58
+
"projectId": "ProjectId",
59
+
"voiceTalentName": "Jessica Smith",
60
+
"companyName": "Contoso",
61
+
"locale": "en-US",
62
+
"status": "NotStarted",
63
+
"createdDateTime": "2023-04-01T05:30:00.000Z",
64
+
"lastActionDateTime": "2023-04-02T10:15:30.000Z"
65
+
}
66
+
```
67
+
68
+
The response header contains the `Operation-Location` property. Use this URI to get details about the `Consents_Create` operation. Here's an example of the response header:
In this scenario, the audio files must already be stored in an Azure Blob Storage container.
78
+
33
79
To add consent to a personal voice project from the URL of an audio file, use the `Consents_Create` operation of the custom voice API. Construct the request body according to the following instructions:
34
80
35
81
- Set the required `projectId` property. See [create a project](./personal-voice-create-project.md).
Copy file name to clipboardExpand all lines: articles/ai-services/speech-service/personal-voice-create-voice.md
+50-7Lines changed: 50 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ author: eric-urban
6
6
manager: nitinme
7
7
ms.service: azure-ai-speech
8
8
ms.topic: how-to
9
-
ms.date: 12/1/2023
9
+
ms.date: 1/10/2024
10
10
ms.author: eur
11
11
---
12
12
@@ -18,24 +18,67 @@ To use personal voice in your application, you need to get a speaker profile ID.
18
18
19
19
You create a speaker profile ID based on the speaker's verbal consent statement and an audio prompt (a clean human voice sample between 50 - 90 seconds). The user's voice characteristics are encoded in the `speakerProfileId` property that's used for text to speech. For more information, see [use personal voice in your application](./personal-voice-how-to-use.md).
20
20
21
-
## Create personal voice
21
+
> [!NOTE]
22
+
> The personal voice ID and speaker profile ID aren't same. You can choose the personal voice ID, but the speaker profile ID is generated by the service. The personal voice ID is used to manage the personal voice. The speaker profile ID is used for text to speech.
22
23
23
-
To create a personal voice and get the speaker profile ID, use the `PersonalVoices_Create` operation of the custom voice API.
24
+
## Create personal voice from a file
24
25
25
-
Before calling this API, please store audio files in Azure Blob. In the example below, audio files are https://contoso.blob.core.windows.net/voicecontainer/jessica/*.wav.
26
+
In this scenario, the audio files must be available locally.
27
+
28
+
To create a personal voice and get the speaker profile ID, use the `PersonalVoices_Create` operation of the custom voice API.
26
29
27
30
Construct the request body according to the following instructions:
28
31
32
+
- Set the required `projectId` property. See [create a project](./personal-voice-create-project.md).
33
+
- Set the required `consentId` property. See [add user consent](./personal-voice-create-consent.md).
34
+
- Set the required `audiodata` property. You can specify one or more audio files in the same request.
35
+
36
+
Make an HTTP PUT request using the URI as shown in the following `PersonalVoices_Create` example.
37
+
- Replace `YourResourceKey` with your Speech resource key.
38
+
- Replace `YourResourceRegion` with your Speech resource region.
39
+
- Replace `JessicaPersonalVoiceId` with a personal voice ID of your choice. The case sensitive ID will be used in the personal voice's URI and can't be changed later.
Use the `speakerProfileId` property to integrate personal voice in your text to speech application. For more information, see [use personal voice in your application](./personal-voice-how-to-use.md).
61
+
62
+
The response header contains the `Operation-Location` property. Use this URI to get details about the `PersonalVoices_Create` operation. Here's an example of the response header:
In this scenario, the audio files must already be stored in an Azure Blob Storage container.
72
+
73
+
To create a personal voice and get the speaker profile ID, use the `PersonalVoices_Create` operation of the custom voice API. Construct the request body according to the following instructions:
74
+
29
75
- Set the required `projectId` property. See [create a project](./personal-voice-create-project.md).
30
76
- Set the required `consentId` property. See [add user consent](./personal-voice-create-consent.md).
31
77
- Set the required `audios` property. Within the `audios` property, set the following properties:
32
78
- Set the required `containerUrl` property to the URL of the Azure Blob Storage container that contains the audio files. Use [shared access signatures (SAS) SAS for a container](/azure/storage/blobs/sas-service-create-dotnet-container#create-a-service-sas-for-a-container) with both read and list permissions.
33
79
- Set the required `extensions` property to the extensions of the audio files.
34
80
- Optionally, set the `prefix` property to set a prefix for the blob name.
35
81
36
-
> [!NOTE]
37
-
> The personal voice ID and speaker profile ID aren't same. You can choose the personal voice ID, but the speaker profile ID is generated by the service. The personal voice ID is used to manage the personal voice. The speaker profile ID is used for text to speech.
38
-
39
82
Make an HTTP PUT request using the URI as shown in the following `PersonalVoices_Create` example.
40
83
- Replace `YourResourceKey` with your Speech resource key.
41
84
- Replace `YourResourceRegion` with your Speech resource region.
0 commit comments