![]() ![]() To align the implementation fields of the same dynamic library in the Video and Audio SDKs, this release changes the implementation fields of the following dynamic libraries: Dynamic libraries ![]() app) file to specify the desired dynamic libraries. When you integrate the Android SDK with Maven Central, you can reduce the size of your app after integrating the SDK by modifying the implementation field in dependencies in the /Gradle Scripts/adle(Module. Changes to the implementation fields of dynamic libraries For the description of the JND library, see extension libraries.Ģ. ![]() If you have integrated the JND library, remove the JND extension library from your project dependencies and recompile your project when upgrading to v3.7.0. Compatibility changes Īs of v3.7.0, the JND library is statically compiled in the SDK by default and no longer provided as an extension library. This release fixed echoes and compatibility issues that occasionally occurred on some devices. Native clients saw video freeze on web clients when web clients published H.264 video streams.Compiling or running a project failed after you integrated the screen sharing extension AgoraScreenShareExtension and set targetSdkVersion as 31.VBS_STATE_REASON_INSUFFICIENT_PERFORMANCE(4).SR_STATE_REASON_INSUFFICIENT_PERFORMANCE(4).When the local user shared audio played by a third-party app using the screen sharing feature, remote users heard echoes.Occasionally, it took users longer than normal to join a channel for the first time.The uplink network quality reported by the onNetworkQuality callback was inaccurate for the user who was sharing a screen.gatewayRtt reported by the onRtcStats callback was inaccurate when the network latency was too high or the router did not respond to ICMP packets.The local user received the onRemoteAudioStateChanged(2,6) callback after disconnecting from and reconnecting to a network even though the remote user had not changed the audio state.When the local user switched the front and rear cameras after enabling image enhancement, remote users occasionally saw the local user's video upside down for an instant.The captured volume was too low on specific devices such as Samsung Galaxy S20+ and Note10+.This release enhances the connection mechanism between the SDK and the server of co-hosting across channels and therefore reduces the failure rate. For other requirements, see the enableRemoteSuperResolution documentation. SR_MODE_AUTO(1): Enables super resolution for the remote user corresponding to the largest rendering window in the channel.īefore using super resolution, ensure that you have integrated the libagora_super_resolution_extension.so dynamical library.SR_MODE_MANUAL(0): Enables super resolution for the remote user you specify.If the original resolution of a remote user's video is a × b, the local user's device can render the remote video at a resolution of 2a × 2b after you enable this feature.Ĭompared to the deprecated method, the new enableRemoteSuperResolution method adds a parameter mode that can be set as either of following values: This release deprecates the previous enableRemoteSuperResolution method, and adds a method with the same name to support super resolution. You need to catch and handle the exceptions yourself otherwise, it can cause a crash. To facilitate troubleshooting, as of this release, the SDK no longer catches exceptions that are thrown by your own code implementation when triggering callbacks in the IRtcEngineEventHandler class. ![]() When you called setAudioMixingPosition to set the position of the music file to play at 36 minutes or later, the music started playing from the beginning instead of from the specified position.Crashes occurred when you called playEffect multiple times to play audio effects, each time the soundId value increased progressively, and each time you did not call stopEffect or stopAllEffects to stop playing the audio effects.Occasionally, the onFacePositionChanged callback reported empty data after you called enableFaceDetection to enable the local face detection.In the communication channel profile, when a user who was using a Bluetooth headset for a call left and then rejoined a channel, the sound was played through the speaker instead of the Bluetooth headset.The virtual metronome did not perform as expected for example, audio in the MP3 format was not supported, and the beats played were sometimes incorrect. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |