I’m looking to use the Meetin Service Live Streaming interface when building an app that uses raw audio data via the live streaming (NOT local recording) channel.
In windows world, this seems to exist in the meeting_service_components tree:
When I modify the URL to ‘linux’, I do see a result:
However, this does not appear to be a valid entry in the file list.
Does anyone have context here? Does meeting_live_stream_interface.h exist for Linux? If not, has it ever existed or is it planned to be implemented? Seems odd that this page would exist otherwise.
meeting_recording_interface.h exists for both Windows and Linux - it’s just live streaming that’s the issue and this is the preferred channel for managing all things raw audio.
Hey @bstrelko, you’ve hit on a really common point of confusion when working with the Zoom Meeting SDK for Linux and raw audio – it’s a bit different than on Windows, and that meeting_live_stream_interface.h link can definitely be misleading.
While that specific “live stream” header doesn’t directly apply to how you’d get raw audio/video on Linux, you can access the raw audio data in real-time, which sounds like what you’re looking for.
Linux uses the raw data within the meeting SDK where you are receiving the raw audio/video stream directly from the meeting.
Alternatively, you can easily and quickly get the raw audio/video streams to/from a Zoom call using a third party service like Recall.ai! It’s a universal meeting API that lets you send a bot to a meeting and send in or receive audio/video data!
Thanks, Amanda - the issue is that StartRawRecording seems to be the only way to get this data via the Linux SDK (based on the link you provided), while Windows allows StartRawRecording OR StartRawLiveStream.
From an administration perspective, there is a strong preference to allow Live Streaming and keep Local Recording disabled on host accounts, but it doesn’t look like this is possible.
Also still curious about why the linux page for the live stream header exists and if there’s any historical context there.
@bstrelko it might have been mistakenly added to the api reference docs. linux meeting sdk does not support this functionality, the windows meeting sdk does.
