v14.0.0 release

Author: bustardcelly

CHANGES.md

@@ -1,5 +1,11 @@
 # Changes
 
+## 14.0.0
+
+- fix: publish codec listings. (Todd Anderson)
+- fix: viewless subscriber for WHEPClient. (Todd Anderson)
+- feat: codec init param support for WHIP and RTC publishers. (Todd Anderson)
+
 ## 13.0.0
 
 - fix: removal of SharedObject functionality. (Todd Anderson)
@@ -22,13 +28,12 @@
 - Fix for connectionParams tacked on WHIP/WHEP calls. (Todd Anderson)
 - Fix for Firefox issue with Bundle order (Todd Anderson)
 
-    > The issue was that the offer provided by the server has a BUNDLE order of 0 1
-    > 2. When the WHEP client set that as their remote SDP and generated an offer,
-    > the BUNDLE order changed to 2 1 0 in the answer SDP. This would cause
-    > subscription issues and non-existant candidates.
+  > The issue was that the offer provided by the server has a BUNDLE order of 0 1 2. When the WHEP client set that as their remote SDP and generated an offer,
+  > the BUNDLE order changed to 2 1 0 in the answer SDP. This would cause
+  > subscription issues and non-existant candidates.
 
-    > Solution was the munge in the incoming offer BUNDLE line order to that of the
-    > answer.
+  > Solution was the munge in the incoming offer BUNDLE line order to that of the
+  > answer.
 
 - Using host query param when Location provided to WHIP/WHEP clients. (Todd Anderson)
 - Fix for live seek fullURL switching. (Todd Anderson)
@@ -48,7 +53,7 @@
 - using Hls.js fallback for Safari and seek feature. (bustardcelly)
 - Allow playback on scrub when unpublish (bustardcelly)
 
-    > If the live stream becomes unpublished, but the video has been scrubbed to VOD time segment, then we want to allow for playback until the end of the live stream termination.
+  > If the live stream becomes unpublished, but the video has been scrubbed to VOD time segment, then we want to allow for playback until the end of the live stream termination.
 
 ## 10.6.0
 
@@ -101,16 +106,16 @@
 - Fix for flash stalled playback. (bustardcelly)
 - Added notifications for RTCPeerConnection open event. (bustardcelly)
 
-    > This will allow for clients to recognize when they can start using peer connection APIs such as mute/unmute.
+  > This will allow for clients to recognize when they can start using peer connection APIs such as mute/unmute.
 
 - fix for HLS socket authentication failure capture. (bustardcelly)
 - Fix for Safari Publisher issue. (bustardcelly)
 
-    > When `gUM` returns with `video` track listed before `audio`, there is an issue on delivering the media to the server. Most likely due to mismatched candidates.
+  > When `gUM` returns with `video` track listed before `audio`, there is an issue on delivering the media to the server. Most likely due to mismatched candidates.
 
 - Fixed improper spelling of `productInstallUrl` config option. (bustardcelly)
 
-    > Is now `productInstallURL` for both rtmp publisher and subscriber.
+  > Is now `productInstallURL` for both rtmp publisher and subscriber.
 
 - fix for unpublish not resolving if not currently publishing. (bustardcelly)
 - API update to allow for providing MediaStream for publish to bypass gUM in SDK internally. (bustardcelly)
@@ -130,9 +135,9 @@
 - fix for bandwidth inject in latest chrome browser. (bustardcelly)
 - adding notification and retry support for autoplay restriction of subscribers. (bustardcelly)
 
-    > * WebRTC, RTMP and HLS Subscriber support
-    > * muteOnAutoplayRestriction configuration property added
-    > * Additional subscriber events for client-side notifications of autoplay restrictions
+  > - WebRTC, RTMP and HLS Subscriber support
+  > - muteOnAutoplayRestriction configuration property added
+  > - Additional subscriber events for client-side notifications of autoplay restrictions
 
 - allowing for decoupled socket for sharedobject connections. (bustardcelly)
 
@@ -153,10 +158,10 @@
 - fix for DOM cleanup on unsubscribe. (bustardcelly)
 - Adding `rtcConfiguration` support (bustardcelly)
 
-    > * WebRTC Publisher
-    > * WebRTC Subscriber
-    > * defaults to `iceServers` if rtcConfiguration is undefined
-    > * Provides a default rtcConfiguration
+  > - WebRTC Publisher
+  > - WebRTC Subscriber
+  > - defaults to `iceServers` if rtcConfiguration is undefined
+  > - Provides a default rtcConfiguration
 
 ## 5.2.0
 
@@ -168,8 +173,8 @@
 - remove of duplicate event handler. (bustardcelly)
 - Adding check for empty candidate from server (bustardcelly)
 
-    > * Server at times (depending on client) will send a `candidate` object as empty during the negotiation process.
-    > * A new event type has been added to notify listeners of this empty candidate
+  > - Server at times (depending on client) will send a `candidate` object as empty during the negotiation process.
+  > - A new event type has been added to notify listeners of this empty candidate
 
 - Pub/Sub support for mobile device orientation recognition. (bustardcelly)
 
@@ -178,7 +183,7 @@
 - removing onbeforeunload hook to dismantle sockets. (bustardcelly)
 - Allowing for auth/validation on HLS Subscribers (bustardcelly)
 
-    > Enabling auth/validation using connectionParam options on HLS Subscribers. This will internally attempt to make a connection on a WebSocket using the connection parameters. If the socket is opened, it is considered successful validation. If rejected, the client is shutdown.
+  > Enabling auth/validation using connectionParam options on HLS Subscribers. This will internally attempt to make a connection on a WebSocket using the connection parameters. If the socket is opened, it is considered successful validation. If rejected, the client is shutdown.
 
 - fix for mutiple property updates on shared object integration. (bustardcelly)
 - offload translation logic for orientation to focus on dynamic layout updates. (bustardcelly)
@@ -187,8 +192,8 @@
 - removal of unnecessary bandwidth config prop on subscribers. (bustardcelly)
 - Exposing autoLayoutOrientation (bustardcelly)
 
-    > Defaulted to true.
-    > When set to false, it is up to the developer to assign transitions as related to orientation of broadcasts.
+  > Defaulted to true.
+  > When set to false, it is up to the developer to assign transitions as related to orientation of broadcasts.
 
 ## 4.5.0
 
@@ -249,7 +254,6 @@
 
 ## 3.4.3
 
-
 - fix for test of `srcObject` in video element. (bustardcelly)
 - fix for subscriber.stop event dispatch. (bustardcelly)
 
@@ -259,12 +263,10 @@
 - offloading subscriber start event to websocket notification. (bustardcelly)
 - Update for API change in browsers. (bustardcelly)
 
-    Though latest adapter.js should handle, adding for legacy and new browsers.
-
+  Though latest adapter.js should handle, adding for legacy and new browsers.
 
 ## 3.4.0
 
-
 ## 3.3.0
 
 - using std camera sizes for RPRO-3787 (bustardcelly)
@@ -279,4 +281,3 @@
 
 - proper removal of child in flash embed. (bustardcelly)
 - support for IE and remove element on flash fallback. (bustardcelly)
-

CONFERENCE_PARTICIPANT_README.md

@@ -23,7 +23,7 @@ The 3 audio tracks are considered the "loudest talkers" minus the current audio
 
 The 1 video track is a video composite of the video streams of all the `RTCConferenceParticipant`s in the group conference. Because of this, integrating a `RTCConferenceParticipant` into your application will most likely require a Mixer Node.
 
-> Read more about the [Red5 Pro Mixer](https://www.red5pro.com/docs/special/mixer/using-mixer/#gatsby-focus-wrapper).
+> Read more about the [Red5 Pro Mixer](https://www.red5.net/docs/special/mixer/using-mixer/#gatsby-focus-wrapper).
 
 * [Requirements](#requirements)
 * [Configuration Parameters](#configuration-parameters)
@@ -34,7 +34,7 @@ The 1 video track is a video composite of the video streams of all the `RTCConfe
 
 ## Mixer Node
 
-Because the video delivered to each `RTCConferenceParticipant` is a composite of all participants in the conference group, you will most likely need to deploy a [Red5 Pro Mixer] (https://www.red5pro.com/docs/special/mixer/using-mixer/#gatsby-focus-wrapper) as part of your solution.
+Because the video delivered to each `RTCConferenceParticipant` is a composite of all participants in the conference group, you will most likely need to deploy a [Red5 Pro Mixer] (https://www.red5.net/docs/special/mixer/using-mixer/#gatsby-focus-wrapper) as part of your solution.
 
 ## Group Provision
 
@@ -51,7 +51,7 @@ Here is an example of a provision to POST to the server:
   isRestricted: false,
   parameters: {
     group: 'webrtc',
-    audiotracks: 3, 
+    audiotracks: 3,
     videotracks: 1
   },
   restrictions: [],

PUBLISHER_README.md

@@ -25,9 +25,9 @@ This document describes how to use the Red5 Pro WebRTC SDK to start a broadcast
 
 # Requirements
 
-The **Red5 Pro WebRTC SDK** is intended to communicate with a [Red5 Pro Server](https://www.red5pro.com/), which allows for broadcasting and consuming live streams utilizing [WebRTC](https://developer.mozilla.org/en-US/docs/Web/Guide/API/WebRTC) and other protocols, including [RTMP](https://en.wikipedia.org/wiki/Real_Time_Messaging_Protocol) and [HLS](https://en.wikipedia.org/wiki/HTTP_Live_Streaming).
+The **Red5 Pro WebRTC SDK** is intended to communicate with a [Red5 Pro Server](https://www.red5.net/), which allows for broadcasting and consuming live streams utilizing [WebRTC](https://developer.mozilla.org/en-US/docs/Web/Guide/API/WebRTC) and other protocols, including [RTMP](https://en.wikipedia.org/wiki/Real_Time_Messaging_Protocol) and [HLS](https://en.wikipedia.org/wiki/HTTP_Live_Streaming).
 
-As such, you will need a distribution of the [Red5 Pro Server](https://www.red5pro.com/) running locally or accessible from the web, such as [Amazon Web Services](https://www.red5pro.com/docs/server/awsinstall/).
+As such, you will need a distribution of the [Red5 Pro Server](https://www.red5.net/) running locally or accessible from the web, such as [Amazon Web Services](https://www.red5.net/docs/server/awsinstall/).
 
 > **[Click here to start using the Red5 Pro Server today!](https://account.red5.net/login)**
 
@@ -92,7 +92,9 @@ _It is *highly* recommended to include [adapter.js](https://github.com/webrtcHac
 | onGetUserMedia | [-] | [see below](#using-mediaconstraints-and-ongetusermedia) | An override method for performing your own `getUserMedia` request. |
 | signalingSocketOnly | [-] | `true` | Flag to indicate whether the `WebSocket` should only be used for signaling while establishing a connection. Afterward, all data between client and server will be sent over an `RTCDataChannel`.
 | dataChannelConfiguration | [-] | `{name: "red5pro"}` | An object used in configuring a n `RTCDataChannel`. _Only used when `signalingSocketOnly` is defined as `true`_ |
-| forceVP8 | [-] | `false` | Flag to force VP8 as the encoder for the outgoing stream. |
+| forceVP8 | [-] | `false` | Flag to force VP8 as the encoder for the outgoing stream. _Marked for Deprecation._ |
+| videoEncoding | [-] | `undefined` | `PublishVideoEncoder` enum: `VP8` | `H264` | `H265` . _Replacement of `forceVP8`._ |
+| audioEncoding | [-] | `undefined` | `PublishAudioEncoder` enum. |
 | endpoint | [-] | `undefined` | The full URL of the endpoint to stream to. **This is primarily used in Stream Manager 2.0 integration for clients.** [Refer to the Stream Manager 2.0 Section](#stream-manager-20)
 
 ## WebRTC Example

SUBSCRIBER_README.md

@@ -32,9 +32,9 @@ This document describes how to use the Red5 Pro WebRTC SDK to subscribe to a bro
 
 # Requirements
 
-The **Red5 Pro WebRTC SDK** is intended to communicate with a [Red5 Pro Server](https://www.red5pro.com/), which allows for broadcasting and consuming live streams utilizing [WebRTC](https://developer.mozilla.org/en-US/docs/Web/Guide/API/WebRTC) and other protocols, [HLS](https://en.wikipedia.org/wiki/HTTP_Live_Streaming).
+The **Red5 Pro WebRTC SDK** is intended to communicate with a [Red5 Pro Server](https://www.red5.net/), which allows for broadcasting and consuming live streams utilizing [WebRTC](https://developer.mozilla.org/en-US/docs/Web/Guide/API/WebRTC) and other protocols, [HLS](https://en.wikipedia.org/wiki/HTTP_Live_Streaming).
 
-As such, you will need a distribution of the [Red5 Pro Server](https://www.red5pro.com/) running locally or accessible from the web, such as [Amazon Web Services](https://www.red5pro.com/docs/server/awsinstall/).
+As such, you will need a distribution of the [Red5 Pro Server](https://www.red5.net) running locally or accessible from the web, such as [Amazon Web Services](https://www.red5.net/docs/server/awsinstall/).
 
 > **[Click here to start using the Red5 Pro Server today!](https://account.red5.net/login)**
 
@@ -190,7 +190,7 @@ Provide an optional `options` configuration that will be assigned untouched to t
 
 Flag to use the default playback controls of the SDK to play, pause, live scrub, and additional actions. If setting this to `false`, you will need to create and manage your own controls to interact with the live and VOD content.
 
-> You can also provide your own custom controls and/or class declarations easily following this [guideline](https://www.red5pro.com/docs/development/playbackcontrols/overview/).
+> You can also provide your own custom controls and/or class declarations easily following this [guideline](https://www.red5.net/docs/development/playbackcontrols/overview/).
 
 #### Video Encoding Configuration
 
@@ -437,7 +437,7 @@ As such, specific failover targets - such as HLS - require native browser suppor
 
 It is entirely possible to playback streams in HLS using a 3rd-Party library (such as [VideoJS](https://videojs.com/)), but you will not be able to do so while utilizing the Red5 Pro WebRTC SDK.
 
-> For more information on how to playback HLS in browsers without native support, please refer to the *Using VideoJS for Playback* section of the [Migration Guide](https://www.red5pro.com/docs/streaming/migrationguide.html#migrating-from-350-to-400).
+> For more information on how to playback HLS in browsers without native support, please refer to the *Using VideoJS for Playback* section of the [Migration Guide](https://www.red5.net/docs/streaming/migrationguide.html#migrating-from-350-to-400).
 
 ## Initialization
 
@@ -656,7 +656,7 @@ The `4.0.0` release of the SDK introduces Playback API and Default Controls for
 
 ## Autoplay Restrictions
 
-In an attempt to provide a more pleasing user experience and reduce data consumption on mobile devices, browsers are continuing to evolve their `autoplay` policies. While generally and attempt to keep websites (read: *ads*) from playing back unwanted and/or unsolicited video and audio, these policies also affect those sites in which the sole intent _is to_ playback video and/or audio - such as from a conference web application built utilizing [Red5 Pro](https://red5pro.com).
+In an attempt to provide a more pleasing user experience and reduce data consumption on mobile devices, browsers are continuing to evolve their `autoplay` policies. While generally and attempt to keep websites (read: *ads*) from playing back unwanted and/or unsolicited video and audio, these policies also affect those sites in which the sole intent _is to_ playback video and/or audio - such as from a conference web application built utilizing [Red5 Pro](https://red5.net).
 
 Naturally, this can cause some confusion and frustration as `autoplay` may have worked as expected prior to latest browser updates. Thankfully, you do have options when using the *Red5 Pro WebRTC SDK* to provide a better user experience.
 

package.json

@@ -1,6 +1,6 @@
 {
   "name": "red5pro-webrtc-sdk",
-  "version": "13.0.0",
+  "version": "14.0.0",
   "description": "Red5 Pro HTML SDK",
   "main": "red5pro-sdk.min.js",
   "scripts": {