Troubleshooting Routes
attemped to turn on audio_compatible_mode but that wouldn’t work for me ( running without cross origin isolated so maybe thats why )
@vic.yang Thanks… it wasn’t working because when I originally tried audio_compatible_mode the mediaSdkChange wasn’t firing “audio” type on Safari but it was firing “share” so I just added “share” for now to accept that as audio encode/decode on safari ready:
Thank you very much for sharing your concerns about usage.
The media-sdk-change was initially introduced to address issues with legacy Safari. We apologize for the delay in updating our documentation. Subsequently, we have introduced a new audio solution (WebRTC audio , enabled via audio_compatible_mode field in JWT token), which does not have these issues and eliminates the need to listen for the media-sdk-change event.
Is it okay to only set audio_compatible_mode for Safari users and non-Safari run without that turned on?