Changelog - Storm Streaming Server

Below you will find a list of the latest software updates with a detailed changelog.

3.0.0

New dedicated server Control Panel — allows previewing performance parameters and enables creating and editing applications, streams, and the entire cluster.
The structure of the preferences.xml file has been heavily rebuilt, including new options and application types.
FFMPEG-based transcoding now runs through internal Storm processes.
Ability to generate thumbnails on the fly (or create them on demand). Size and frequency are configurable.
LIVE application type is now called MONO.
New Ingest configuration settings for MONO and ORIGIN application types.
New Security settings — domain-level whitelist/blacklist can now be defined.
New REST API (over 120 endpoints). Authentication now works via X-API-KEY.
Cluster node communication runs through a proprietary protocol to increase security, reduce latency, and improve stability.
New Generic HLS module supporting multi-quality streams (when transcoding is active).
New transcoding preset system that can be applied per application. Added support for NVENC, AMF, and QSV encoding.
Dedicated installers for the most popular platforms, including Windows, macOS, and Linux (GUI/Console).
Support for environment variables in preferences.xml via ${EV:YOUR_VARIABLE_NAME}. Variables are automatically detected and replaced with their corresponding values.
Added limits for number of streams and viewers per application, as well as a maximum number of active transcoding jobs.
Streams and viewers now include health scores composed of multiple underlying metrics.
Added new cluster application type: TRANSCODE. Enables transcoding streams from origin servers. ClusterManager can automatically select streams for transcoding.
Added viewer preview inside ClusterManager, including statistics such as latency, buffer size, transmission time, and more.
Ability to publish a cluster stream to multiple origin servers and manage their priorities (also works as a failover mechanism).
Real-time server logs are now available in the Control Panel.
Control Panel login is based on users defined in preferences.xml.
Ability to preview server (machine) parameters both in the panel and via REST API.
Added viewer geolocation support (preview available in the Control Panel).
New stream recording options — ability to define maximum duration, file size, and automatic deletion of old files.
Support for a dedicated streamer powered by WebCodecs technology.

2.4.0

Improved cluster handling, including operation of multiple ClusterManager instances within a single cluster.
Added the AutoPublishStream parameter to RTMP settings — incoming streams can be paused in NOT_PUBLISHED mode until they are manually published.
Fixed a bug with the configuration for Edge-type applications (previously required a specified access path).
Communication between cluster elements now uses a proprietary data protocol that reduces latency and increases the stability of the entire system.
The server now supports an unsubscribe method, which removes all listeners created by the player (requires Storm Library version 5.x.x).
All viewer connections now report a wide range of connection data such as browser, operating system, and the latency achieved.

2.3.0

Bug fix for calculating transcoded video width.
Bug fix for restoring playback when stream has been stopped.
Playback will automatically restore for streams with no auth management (if stream key matches).
ThreadPool settings now work in either automatic or manual mode.
Minor changes to REST API.

2.2.0

New updated cluster model with ClusterManager has been introduced.
Server Load tab in Control Panel has been updated (incoming & outgoing bandwidth for the whole server).
New ClusterManager tab in Control Panel has been added, which includes server/app list and stream list.
Messages and logs for issues regarding licensing have been improved.
Minor changes in authorization module for better OpenJDK compatibility.
Minor changes to REST API.

2.1.0

Startup parameter -configRootDir is now optional — the server will pick the JAR root directory by default.
Default logging settings were improved. Default logging directory will be assigned automatically.
Environment variables can now be used to generate a default preferences.xml file.
If the width of a transcoding preset is not specified, it will be calculated based on original stream proportions.
New startup & shutdown scripts for macOS/Linux & Windows.
New parameters for recording video.
Improved H.265 and AV1 support.

2.0.1

Minor improvements to transcoding task management.
Minor improvements to RTMP Client.
Minor improvements to MSE Client.

2.0.0

RTMP protocol support has been rewritten from scratch. Push and pull streams are now supported. Restreaming to another RTMP-compatible server is also possible. Authentication support has been added, along with Enhanced-RTMP capabilities (H.265 & AV1 codecs).
Entirely new client-server protocol for Storm Library & Player. Thanks to "states," each player instance will be notified whenever a stream has started, been published, or ended.
Storm now supports transcoding through FFMPEG (must be installed separately). Transcoding options can be further tuned via the preferences.xml file.
Sockets can now be opened on multiple hosts & ports for specified protocols. RTMPS support has been added along with a new SSL engine.
Socket restart functionality has been introduced — if a socket is already taken, the server will try to claim it at a specified interval.
New application types have been introduced: live (standard single application group of streams), origin (allows for pushing streams but not for viewing, designed for redistributing streams to other Storm instances), and edge (does not allow for pushing streams but pulls streams from specified origin applications).
New authorization types for applications: free (no authorization required), managed (a stream with credentials must be created first via API or Control Panel), and list (utilizes XML lists with credentials).
Stream recording received additional options: maximum storage for a specific folder can be specified, and whether to remove old files when the folder limit is reached.
Support for classic HLS/HLS-LS/MPEG-DASH has been introduced (works with third-party players).
The threading component has been rewritten from scratch. The server is more efficient and uses 30% less RAM compared to version 1.x.
A simple Control/Dev Panel has been introduced, allowing for basic server management including killing or registering streams & connections.
The RESTful API has been rewritten.
The logger has been updated to Log4j2. Coloring is now supported and enabled by default.

1.5.0

REST API has been greatly expanded — full control over all applications, streams, and auth users.
New SSL engine for SSL connections.
RTMPS is now fully supported.
Thread pools have been unified for all active socket listeners.
RFC 7692 WebSocket protocol is now supported (works alongside RFC 6455).
Redesigned cluster mechanics for better performance.
Major improvements in memory management.

1.4.0

Application settings VariableFPS & KeyFrameCompensation can now work in autodetect mode (new property value: auto).

1.3.1

Minor improvements to memory management.

1.3.0

DVR functionality on iOS was greatly improved.
Improved thread management.

1.2.3

A bug allowing for application duplication was fixed.

1.2.2

Log4j library was updated to the latest version.

1.2.1

A minor bug in connection timeout was fixed.

1.2.0

Stream recording functionality has been added to the server (can be configured via preferences.xml).

1.1.5

Minor bug fixes to External RTMP Module (Wowza WebRTC compatibility).

1.1.4

Minor improvements to WebSocket protocol.

1.1.3

Docker config bug has been fixed.

1.1.2

LL-HLS/HLS improvements for iOS 15 and Safari.

1.1.1

Bug fix for RTMP internal connection source spamming errors after deleting a stream.
VariableFPS parameter in application settings allows deciding whether Storm should adjust for variable frame rate sources.
KeyFrameCompensation parameter in application settings forces the packetizer to add missing keyframes.

1.1.0

REST module has been completely rewritten.
New authentication system for REST.
RTMP Client has been greatly improved.

1.0.1

Fixed a bug where the client was not informed about a source that had been closed/ended.
License type has been removed from the preferences.xml file.

1.0.0

Initial release.

Downloads

Visit stormstreaming.com/downloads for the latest version.