1.0.0-beta.16 (2024-04-11)
Features Added
Audio
GetAudioTranscription()
now supports word-level timestamp granularities viaAudioTranscriptionOptions
:- The
Verbose
option forResponseFormat
must be used for any timing information to be populated TimestampGranularityFlags
accepts a combination of the.Word
and.Segment
granularity values in
AudioTimestampGranularity
, joined when needed via the single-pipe|
operator- For example,
TimestampGranularityFlags = AudioTimestampGranularity.Word | AudioTimestampGranularity.Segment
will request that both word-level and segment-level timestamps are provided on the transcription result
- For example,
- If not otherwise specified,
Verbose
format will default to using segment-level timestamp information - Corresponding word-level information is found on the
.Words
collection ofAudioTranscription
, peer to the
existing.Segments
collection - Note that word-level timing information incurs a small amount of additional processingly latency; segment-level
timestamps do not encounter this behavior
- The
GenerateSpeechFromText()
can now useWav
andPcm
values fromSpeechGenerationResponseFormat
, these new
options providing alternative uncompressed formats toFlac
Chat
ChatCompletions
andStreamingChatCompletionsUpdate
now include the reportedModel
value from the response- Log probability information is now included in
StreamingChatCompletionsUpdate
whenlogprobs
are requested on
GetChatCompletionsStreaming()
- [AOAI] Custom Blocklist information in content filter results is now represented in a more structured
ContentFilterDetailedResults
type - [AOAI] A new
IndirectAttack
content filter entry is now present on content filter results for prompts
Breaking Changes
- [AOAI]
AzureChatExtensionMessageContext
'sRequestContentFilterResults
now uses the new
ContentFilterDetailedResults
type, changed from the previousIReadOnlyList<ContentFilterBlockListIdResult>
. The
previous list is now present onCustomBlockLists.Details
, supplemented with a newCustomBlockLists.Filtered
property.
Bugs Fixed
- [AOAI] An issue that sometimes caused
StreamingChatCompletionUpdates
from Azure OpenAI to inappropriately exclude
top-level information likeId
andCreatedAt
has been addressed