Skip to content

Releases: Eyevinn/node-srt

v0.8.3

20 Nov 12:03
fe1d9f9
Compare
Choose a tag to compare

What's Changed

  • Fixes AsyncSRT types and tests, add super() to AsyncSRT constructor by @yaruno in #67

Full Changelog: v0.8.2...v0.8.3

v0.8.2

20 Nov 09:49
cf06fe6
Compare
Choose a tag to compare

What's Changed

  • add event emitter to async class by @yaruno in #64

New Contributors

Full Changelog: v0.8.1...v0.8.2

v0.8.1

19 Sep 21:06
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v0.8.0...v0.8.1

v0.8.0

18 Sep 12:18
Compare
Choose a tag to compare

What's Changed

  • feat: upgrade to libsrt 1.5.2 by @birme in #61

Full Changelog: v0.7.1...v0.8.0

v0.7.1

10 Aug 13:53
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v0.7.0...v0.7.1

v0.7.0

11 Nov 13:15
Compare
Choose a tag to compare

What's Changed

  • Build with version 1.4.4 of libSRT.
  • Verified build with Darwin arm64

New Contributors

Full Changelog: v0.6.0...v0.7.0

v0.6.0

13 May 14:17
Compare
Choose a tag to compare

What's Changed

  • Add support for SRT stats by @jeoliva in #20
  • Fix #17 (work with SRT v1.4.2): Set proper sockaddr_in alloc size & resolve deprecation warning (use srt_create_socket instead srt_socket) by @tchakabam in #21
  • Add support for SRTO_STREAMID by @Morpheus235 in #34
  • node-src.cc: fix erratic value passed to srt_setsockflag for length arg (introduced with PR #34) by @tchakabam in #37

New Contributors

Full Changelog: v0.5.2...v0.6.0

v0.5.2

26 Oct 15:56
Compare
Choose a tag to compare
0.5.2

High-performance Use cases

21 Oct 11:17
Compare
Choose a tag to compare

With a great contribution from @tchakabam the headlines of this release contains the following:

  • Supporting High-performance read/write use-cases
  • Support server/multi-connection implementations

And a bunch of improvements to build process, unit and integration tests, typescript support and much more

Async API

03 Aug 10:17
Compare
Choose a tag to compare

The N-API binding layer to the SRT SDK is such that every native call are blocking I/O and runs synchroneuosly with the wrapping JS function call. This means that these functions are called from the Node.js proc main-thread / event loop. This creates a throughput limit and in general having blocking operations can impact application performance in an unpredictable way. To address this issue we have an "async variant" of the API where the native blocking calls are put on a JS Worker thread instead (big thanks to @tchakabam for this contribution).

The Async API is a candidate to replace the main API in the next major release