-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sample doesn't work with new SDK verison #6
Comments
@SergeyGalaxyOrsik could you share some of the errors here? |
Hey @SergeyGalaxyOrsik, if you're facing issues compiling the sample with the latest SDK version, you might want to check out the Recall.ai API. It’s a simple 3rd party API that lets you use meeting bots to get raw audio/video/metadata from meetings without you needing to spend months to build, scale and maintain these bots. Here are the API docs: https://docs.recall.ai/page/tutorials |
hello, I got errors compiling version 6.1.10 made both on visual studio (windows) and vscode on a linux ubuntu 22 and ubuntu desktop 24. Build was ok:
Then when make it: /home/--/Documents/repos/meetingsdk-linux-raw-recording-sample/demo/meeting_sdk_demo.cpp: In function ‘void JoinMeeting()’: In file included from /home/--/Documents/repos/meetingsdk-linux-raw-recording-sample/demo/meeting_sdk_demo.cpp:30: In file included from /home/--/Documents/repos/meetingsdk-linux-raw-recording-sample/demo/meeting_sdk_demo.cpp:38: Many thanks. |
hi @jeirix , The current version which you are using requires 6.1.0 I'm using a Windows Machine to compile this project |
Hello @tanchunsiong many thanks for this update, I could successfully build and compile 6.1.10 without errors. I provided all the information inside config.txt ( meeting_number, token ( generated by Server-To-Server OAuth), meeting_password) it works only with JWT definitively. |
I tried to compile sample with new version of SDK v5.17.10.3562, but when I do
make
in/demo/build
directory I have many errors. I tried start sample with SDK v5.17.5.2561 and all work wellThe text was updated successfully, but these errors were encountered: