We're excited to announce that we've updated how we publish our Node.js packages: going forward, all our packages will be published under the @eyeson organization scope on npm.

What's Changing?​

Previously, our packages were named like this:

• eyeson
• eyeson-node

Now, they'll be published like this:

• @eyeson/js
• @eyeson/node

This change only affects the package names — all functionality remains the same, and you can continue using our libraries as usual with a small update to your package.json.

The Eyeson API provides a powerful way to forward the stream of any meeting client in real-time and at its original quality to your desired destination for further processing.

This feature forms the backbone of the Eyeson AI Adatpter.

For full API documentation, visit https://docs.eyeson.com/docs/rest/references/forward.

The API layers endpoint now supports SVG images. This comes with great advantages for developers.

The power of SVG​

SVG is an XML-based vector image format, where XML is human-readable text.

Define drawing objects and use it with the Eyeson API. The actual image is created on our server, so the whole process of creating, sending and drawing the overlay is way faster than before.

In other words:

• Significantly smaller file sizes
• Text-based format that can be edited with code editors
• Original quality in contrast to compression of PNG, WebP, etc.

Eyeson is excited to announce a significant improvement to our video conferencing platform with the migration from VP8 to VP9 as our default video codec. This upgrade will automatically enhance your video conferencing experience without requiring any action on your part.

The audio passthrough option allows for greater preservation of audio received from your microphone without using Eyeson's echo cancellation and audio filters.

This is ideal if your microphone or sound equipment has these features built-in or if you want to preserve the full range of sound from a musical instrument.

We've made changes to the API playbacks layout that you need to be aware of!

Virtual situation rooms are a quick way to build a command and control structure, and since they are virtual, they do not require physical space and can be created in large numbers to give teams room to collaborate.

Welcome to a series of posts​

I will guide you through creating a virtual situation room in this series. It will have the following episodes.

1. Creating a virtual situation room Creating rooms, different kinds of users
2. Connecting the virtual situation room Inviting participants, adding sources
3. Optimize the layout Custom Layout
4. Permalink rooms Different usage, standard ops only?

In the first part, we looked at creating the virtual situation room. Further, we looked at the authentication and users. We will now consider bringing the participants into the room and adding sources.

In Part 3 of our Series, we will look at the layout functionalities of the Eyeson One View API. Since Eyeson is built on top of a next-generation MCU, you can be sure that everyone sees the same things at the same time. So, the Layout is applied by the MCU and can not be changed individually.

Permalinks in Eyeson allow developers to create pre-defined meeting rooms with shareable and permanent guest links, enabling meeting setup and invitation distribution before the actual meeting starts.