A replacement for the native SimplePeer / EasyRTC A/V client in FoundryVTT. The module uses LiveKit platform to provide Audio & Video communication between players.
⚠️ SSL is still requiredThe LiveKit AVClient does not remove the need for SSL (https) on your Foundry server. Even if you use one of the hosted solutions below, all modern browsers require that the page that A/V is viewed on be secured. You can follow the following guide to set up SSL on your Foundry server: Foundry VTT - SSL & HTTPS
Note: At the moment, there are no free public LiveKit servers. You must configure a custom signaling server under Audio/Video communication or use one of the following options:
At the Tavern is providing access to a multi-region LiveKit server cluster that we maintain to anyone who subscribes to our Patreon at at least a $5 USD per month level. The fee is used to cover the cost of the server cluster and contribute toward further development of this module.
Forge users can make use of the Forge's LiveKit servers with no additional configuration required.
LiveKit Cloud provides a free tier, for a limited number of minutes/bandwidth per month. It may not be suitable for larger games or frequent use.
You can install this module by using the following manifest URL: https://github.com/bekriebel/fvtt-module-avclient-livekit/releases/latest/download/module.json
Install & enable the module then configure for your LiveKit instance under Audio/Video Configuration:
LiveKit Server: Select an available option or Custom for your own server
LiveKit Server Address: rtc.example.com <Your LiveKit server address>
LiveKit API Key: ABCDEFGHIJ12345 <Your LiveKit API Key>
LiveKit Secret Key: **************** <Your LiveKit Secret Key>
LiveKit AVClient provides a number of features beyond the A/V option built into Foundry:
- Uses a Selective Forwarding Unit (SFU) architecture instead of Mesh. This means each user only has to send their their audio and video once instead of needing to connect to every other user in the game.
- LiveKit server connections work in more network environments.
- Breakout Rooms allow you to split the party!
- Adaptive Streaming and Dynamic Broadcasting reduce bandwidth and CPU usage based on video window size and available system resources.
- Opus DTX reduces bandwidth used by audio tracks when a user isn't speaking.
- A Connection Quality Indicator shows if a user's connection is having trouble.
- An optional external web client can be used to open audio and video in a separate tab, or even separate device (including mobile).
- The ability for individual users to disable receiving video in case they are on very limited connections.
- The ability to individually hide or mute users only for yourself.
- Audio Music Mode to tune audio publishing settings for audio streamed by your account.
- Actively maintained and tested against the latest versions of FoundryVTT.
- Additional features planned for future releases!
A GM can now split the party!
To start a breakout room, right-click on the player you would like to break out in the player list and select Start A/V breakout. You will join a different A/V session with that user. You can now right-click on other users and pull them into the breakout room, or start yet another breakout room with another user.
Though the GM will always join the breakout room on creation, they can leave the breakout room themselves by right-clicking on their own username and selecting Leave A/V Breakout. Users can also leave a breakout at any time by right-clicking on their own name, and the GM can end all breakout rooms by selecting End all A/V breakouts.
There are several examples available for launching your own livekit server:
- User created guides for FoundryVTT
- LiveKit Getting Started
- Deploy to a VM (GCP/AWS/Digital Ocean/Linode/Vultr/etc)
- Deploy to Kubernetes
Though newer versions may work, the current recommended LiveKit server version is v0.15.6. This has had the most extensive testing done with the module and matches the current client SDK version that the module is using.
⚠️ Duck DNS and Ad blockers: Several ad blockers seem to block websocket connections to Duck DNS URLs. If you are using Duck DNS for your LiveKit Server domain name, you and your users may need to whitelist the domain name in ad blocking extensions.
By default, debug logs are disabled. If additional logs are needed for troubleshooting, Enable debug logging can be turned on under the module settings. For even more logging of the LiveKit connection, LiveKit trace logging can be enabled after debugging logging is turned on by setting Enable LiveKit trace logging under module settings.
See CHANGELOG
