Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
New in version 1.4.4
Digital silence detection
We've added the digitalSilenceDetected() callback function, called when DAXKit detects 1/3 second of digital silence during recording (only zeros in the audio stream).
DAXKit issues a notification when digital silence has been detected, but it continues recording. You can choose whether to stop the recording in response to the notification. We recommend interrupting the recording and displaying an alert to the user.
Known issues
If another application calls
AVAudioApplication.shared.setInputMuted(true)and never unmutes the input, then most other applications including DAXKit will receive digital silence unless an application callsAVAudioApplication.shared.setInputMuted(false).A workaround for this is for your app to call
AVAudioApplication.shared.setInputMuted(false)immediately before you call DAXKit'ssession.startRecording(). This call will be included in an upcoming DAXKit release, so partner apps won't need to call this.This behavior has been filed as a bug to Apple.
When a user on the Canadian system updates from 1.2.1 to 1.4.x, they can't add recordings to any previous encounters that were created in 1.2.1. Mitigation step: Complete all encounters on 1.2.1 before upgrading to 1.4.x.
When the phone is connected via USB, DAXKit sometimes fails to create a transcript. [2078490]
When updating to DAXKit 1.4.2 from any version earlier than 1.4.0, QA and staging users from previous versions will lose any recordings that weren't uploaded to the servers. Mitigation step: Inform QA and staging users that they should confirm they have uploaded all recordings they want to save before updating the app. [1941109]
When updating to DAXKit 1.4.2 from any version earlier than 1.4.0, QA and staging users can't add to existing encounters. Recordings won't get uploaded. Mitigation step: Inform QA and staging users that they can only test this scenario in production.