Hi all I am new here, Thank you for that great SDK!

Hey everyone, I can’t believe it’s been a year since the first release of LiveKit on GitHub! Learning about (and supporting) all the incredible projects folks have shipped and are building is really energizing for the core team. LiveKit wouldn’t have the same quality or momentum without the efforts this community has put into submitting PRs, SDKs, bug reports, feature requests, and feedback. Thank you so much! 🙏🏽❤️ Some of you may know that since late last year, we’ve been working on a cloud-managed version of LiveKit. One of our goals was to make it really simple for folks to get up-and-running with a multi-region, production-ready deployment of LiveKit — without having to worry about load balancers or SSL certs (unless of course, you want to 😅). As we inch our way towards a public launch of this new service, we’d love to open up early access to the LiveKit community. Your feedback will be super helpful as we continue to iterate and improve our offering. If you’re interested, please fill out this quick survey. Over the next few weeks, @bright-scooter-10854 and I will schedule a quick call to meet, learn more about what you’re building, and help get you onboarded. Looking forward to supporting y’all! ☁️🛠️🚀

This message was deleted.

👋 Hi everyone!

Hi

Hi, Best Regards.

This message was deleted.

Hi all

This message was deleted.

This message was deleted.

LiveKit looks really great, but we'd have to solve this problem before we could consider moving.

This message was deleted.

This message was deleted.

This message was deleted.

👋 Hi everyone!

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

I note in the docs for server wrapper, that it shows an example of listing all rooms, calling a server name :

const livekitHost = '<https://my.livekit.host>';

Given that this is my server running, and I dont see an address specified - is this livekithost a built in default, or should I be calling with the IP address specifically (this is a dev test running on local windows machine)

This message was deleted.

Client running on a Node js server - hi there - Unless I am reading this wrong, the LiveKit Server does not allow me to receive data from a "room" - only sendData to all? My use case has a requirement for an app running in a server environment, which can send and receive data to the room and or individual participants. When trying to build this in Node.js, i get the following error, which comes from the fact this is not running in a browser:

C\Users\mrbre\source\repos\IMP\demo repo\WEBRtcSamples\IMServerSlotBase\node modules\livekit client\src\room\track\utils.ts109 const AudioContext = window.AudioContext || window.webkitAudioContext; ^ ReferenceError: window is not defined at getNewAudioContext (C\Users\mrbre\source\repos\IMP\demo repo\WEBRtcSamples\IMServerSlotBase\node modules\livekit client\src\room\track\utils.ts109:24) at Hs.acquireAudioContext (C\Users\mrbre\source\repos\IMP\demo repo\WEBRtcSamples\IMServerSlotBase\node modules\livekit client\src\room\Room.ts927:17) at Promise.finally.connectFuture (C\Users\mrbre\source\repos\IMP\demo repo\WEBRtcSamples\IMServerSlotBase\node modules\livekit client\src\room\Room.ts229:12) at new Promise (<anonymous>) at Hs.connect (C\Users\mrbre\source\repos\IMP\demo repo\WEBRtcSamples\IMServerSlotBase\node modules\livekit client\src\room\Room.ts220:28) at C\Users\mrbre\source\repos\IMP\demo repo\WEBRtcSamples\IMServerSlotBase\src\worldspace\slotServer.tsx98:24 at Generator.next (<anonymous>) at C\Users\mrbre\source\repos\IMP\demo repo\WEBRtcSamples\IMServerSlotBase\src\worldspace\slotServer.tsx8:71 at new Promise (<anonymous>) at __awaiter (C\Users\mrbre\source\repos\IMP\demo repo\WEBRtcSamples\IMServerSlotBase\src\worldspace\slotServer.tsx4:12)

Is there anyway to avoid this etc? Thanks for your help

It should be noted that I am only looking to transmit data from this Server based CLIENT - so in the error above, I am not even trying to use audio/video etc

BTW - I just build the client from source and in Room.ts line 235ish... I just wrapped the aquireAudioContext() call with the isWeb() and it appears to work fine: