Developer Program

The Developer Program allows third-party developers to get access to earlier builds of upcoming VMS releases. Nx Meta exists to allow developers to create integrations and products with the core VMS software before official VMS releases — it will usually have experimental features that aren’t yet available in the official VMS release. The Developer Program is essential for long-term development as you’ll be able to test product features at earlier stages in the development; allowing you to release your integration at the time of product releases. 

You will also be able to provide us feedback on features we are currently developing; features you would like to see in the platform; and how we can improve your development experience with us overall. We take your feedback seriously, and as you have earlier access to builds — it can be possible for us to implement your suggestions in time before Nx Meta releases. You can also ask for feedback/support on your development from our engineering team and our developer community. Visit the Developer Forum to make your post.

Create an account on the Nx Meta Developer Portal to get access to

• the latest patches and releases of Nx Meta,
• licenses for developers,
• SDKs,
• Integrations Marketplace, and
• feedback on your development.

Nx Meta Release Process FAQ

Q: What is an Nx Meta release?

A: Nx Meta releases are preliminary releases of the core VMS software (like alpha or beta versions). These builds are created specifically for developers and partners to develop integrations with the software before the official release.

Q: How often do we make Nx Meta releases?

A: There is no predefined schedule for Nx Meta releases. We make the decision to roll out a new version primarily based on two considerations:

1. Are there any specific support tickets that we need to address?
2. Do we have enough changes which affect partners and require them to update their code base?

Once we decide to make a release, it contains all the changes accumulated up until that point. It is possible to influence a Nx Meta release by creating a support ticket or a discussion on the Developer Forum, where you can explain your issue or proposition. All requests are considered, and if possible, addressed in future Nx Meta releases. 

Q: Are Nx Meta releases stable?

A: No. An Nx Meta release cannot be considered stable, because it always contains untested changes in the core of the software. Every time we release an Nx Meta update, we test and try to stabilize only the most essential features, allowing our partners to continue their development.

You should always use the latest build because every version introduces new capabilities for developers or some changes in the SDK. Check the release notes to see a list of important changes.

Q: What do we test before a new Nx Meta release?

A: Before a new Nx Meta release is launched, we perform two tests (commonly called a "smoke check"):

• Core software features test — including live streams, archive playback, setting dialogs, web admin interface, and Cloud connectivity.
• Development-related features test — including stub plugin with events, objects and settings, SDK compiling, searching through the analytics database, and documentation changes.

These tests are performed on three platforms: Windows, Ubuntu x64, and ARM64.

Each new Nx Meta release is bundled with release notes. This contains a comprehensive list of changes, bug fixes, and known issues. If a known issue from the previous release is fixed, we list it as a “Fixed Issue” in the current release.

If an Nx Meta release contains some important new features (e.g., fixes for support tickets, etc.), they are tested immediately before or during the smoke check.

Q: Is it expected that the new Nx Meta release might break plugin compatibility with the VMS?

A: Yes. Moreover, 3rd-party developers have to change their code accordingly because the primary goal for a plugin is to be compatible with the upcoming major VMS release.