This release provides internal bug and security fixes. It is recommended that customers on previous releases upgrade to this version.
This release makes changes to the buffer when sending AddAudio messages. If an AudioAdded message is now sent, it means that the audio is definitively ready for transcription. The Real-time Container has a buffer of up to 10 seconds of speech, or 500 add Audio messages. If this buffer is exceeded, no further AudioAdded messages messages will be returned from the Container until the buffer has capacity. Please ensure any integration you have to the Real-time Container is able to tolerate this buffer by ensuring that sending and receiving messages runs in another thread or uses some other mechanism to avoid getting blocked. For the Real-time virtual Container where audio is sent faster than real-time, it is recommended to use a semaphore of size 500 or audio length of 10 seconds to avoid any unnecessary memory consumption.
It is recommended to run Speechmatics containers on processors that support Advanced Vector Extensions 2 (AVX2) in order to take advantage of latest performance optimisations.
Internal bug and security fixes
The following are known issues in this release:
| Issue ID | Summary | Detailed Description and Possible Workarounds |
|---|---|---|
| REQ-10634 | Putting "-" as an item in additional vocab configuration will cause the container to fail | Do not enter just a "-" on its own in Custom Dictionary either as an additional vocab item or in the sounds_like property. Hyphens are still supported when entered as part of phrases or words |
| REQ-13240 | Chinese (cmn) container crashes occasionally when using certain additional vocabulary | Do not use whitespace characters in additional vocabulary sounds_like |
| REQ-16256 | Audio Swapping between 8kHz and 16kHz causes memory leak | Repeatedly audio swapping between 8kHz and 16kHz files can cause an increase in memory over very long periods that causes the container to crash. If memory usage in this scenario becomes excessive it is recommended to restart the container |
| REQ-17771 | Wide-space Unicode characters in Custom Dictionary cause a jobs to fail | This is now fixed and wide-spaced characters should be accepted |
The following is a list of any resolved issues within this release
The following issues are addressed since the previous release:
| Issue ID | Summary | Resolution Description |
|---|---|---|
| REQ-11135 | Unwanted hesitations in transcripts. | For the English language pack Speechmatics now tags hesitation words ('umm') with a metadata tag of "disfluency". Users can use this tag for post-processing to filter or analyze such words. This work does not make disfluencies better or more poorly recognised in transcript output |
| REQ-11136 | Transcripts are direct written to the Real-time Virtual Appliance and Container logs | Transcripts are no longer written directly to the logs or persisted to disk, even temporarily, for security reasons. |
| REQ-14795 | Configuration information was not written to logs in StartRecognitionMessage | Transcription Configuration information is now logged as part of th StartRecognitionMessage. Individual custom dictionary entries are redacted |
| REQ-15515 | Internal buffer limit of 500 AddAudio messages/10 seconds of audio | The Container now has a buffer. If you are sending audio faster than real-time and send more than 500 AddAudio messages of 10 seconds of Audio you will not receive an audioAdded response until there is capacity again. Please ensure your client connection is resilient to avoid audio being dropped |
These are the General Availability (GA) release notes for the Real-time ASR container images. Following languages are supported:
Container images are labelled using the following scheme, where language codes adhere the ISO-639 standard:
rt-asr-transcriber-<language>:<version>
For example,
rt-asr-transcriber-en:1.3.1
Docker 17.06.0+
Pull the container image from the Speechmatics Docker registry.