Release 2.0.0 (9th Jul 2019)

	License update: KVS SDK and GStreamer kvssink plugin are under Apache 2.0 license now.
	C-Producer - New feature
		Language level is C89. It should work for all GCC versions, tested minimum GCC version is 4.1.
		The Kinesis Video Streams C producer library wraps kinesis-video-pic (Platform Independent Code) with additional layer of API that allows scenario and platform-specific callbacks and events.
		Callbacks for sample retry logic implementation are now supported through C Producer
	CPP Producer - Updates
		Language level is C++11 instead of C++14. Required minimum GCC version is 4.8.
		Kinesis Video Producer CPP (kinesis-video-producer directory) is now revised to a wrapper of C Producer SDK which interfaces with the Platform Independent Repository (PIC, kinesis-video-pic directory).
		Platform Independent Code - New functionality
		Automatic CPD (codec private data) extraction from the stream
		Reset stream and reset connection functionality in PIC - In case of unrecoverable errors users can simply call reset stream; internally SDK will free & create the stream.
		Log level supported in PIC. It can be set in member variable of DeviceInfo.ClientInfo.
	Platform Independent Code - Bug Fixes
		Skip over error fragments - SDK will continue skip any invalid fragments are ingested through SDK earlier and continue streaming with valid ingested fragments. It will not just loop back and keep resending the broken fragment now.
		All unit tests (pic_test, cproducer_test, producer_test) are at C++11 level. Required minimum GCC version is 4.8.

	Please note the following changes if you have customized the SDK for your integration and not using samples directly.

		Changes to utility functions:
		RotatingStaticCredentialProvider is removed from C++ producer. Customer can use StaticCredentialProvider instead.
		CredentialProviderUtil and SerializedCredentials are removed from C++ producer.
		Following functions are removed from DefaultCallbackProvider: sleepUntilWithTimeCallback, shutdownStream, notifyResult, getControlPlaneUri, safeFreeBuffer, getStreamStatusFromString.
	Changes to the object model:
		Following attributes have been added: Version number is added to TrackInfo, Frame, StreamDescription, DeviceInfo, StreamInfo.
		Following attributes have been removed: certPath is removed from DeviceInfo in PIC.

Author: chehefen

.gitignore

@@ -11,3 +11,5 @@ kinesis-video-native-build/start
 kinesis-video-native-build/test_h264_jpg.mkv
 kinesis-video-native-build/test_jpeg.mkv
 test-stream/
+*.key
+*.gpg

README.md

@@ -17,14 +17,32 @@ Amazon Kinesis Video Streams Producer SDK for C/C++ makes it easy to build an on
 Amazon Kinesis Video Streams Producer SDK for C/C++ contains the following sub-directories/projects:
 * kinesis-video-pic - The Platform Independent Codebase which is the basic building block for the C++/Java producer SDK. The project includes multiple sub-projects for each sub-component with unit tests.
 * kinesis-video-producer - The C++ Producer SDK with unit test.
+* kinesis-video-c-producer - The C Producer SDK with unit test.
 * kinesis-video-producer-jni - The C++ wrapper for JNI to expose the functionality to Java/Android.
 * kinesis-video-gst-demo - C++ GStreamer sample application (for webcam, USB camera and RTSP) .
 * kinesis-video-gstreamer-plugin - GStreamer plugin sink element (kvssink) and demo application.
 * **kinesis-video-native-build** - Native build directory with a build script for **Mac OS/Linux/Raspberry PI/Windows**. This is the directory that will contain the artifacts **(executable binaries)** and JNI libraries after the build.
   * This should be your **current working directory** for running the install-scripts.
 
 ----
+### Supported Platforms
+----
+Kinesis Video Streams Producer SDK was tested on following platforms:
+```
+    Ubuntu 16
+    Ubuntu 17
+    Ubuntu 18
+    Raspberry Raspbian
+    MacOS El Captian
+    MacOS Sierra
+    MacOS High Sierra
+    Windows 7 Enterprise
+    Windows 10 Enterprise
+    Windows Server 2012 R2
+    Windows Server 2016
+```
 
+----
 ### Build and install Kinesis Video Streams Producer SDK and sample applications
 ----
 There are few build-time tools/dependencies which need to be installed in order to compile the core producer SDK libraries and the sample applications. Sample applications are provided to demonstrate _**how to send video**_ from **webcam**, **USB camera**, or **IP camera** (RTSP).
@@ -50,6 +68,32 @@ This library is licensed under the Apache License, 2.0.
 ----
 ### Release notes
 
+#### Release 2.0.0 (9th Jul 2019)
+* License update: KVS SDK and GStreamer kvssink plugin are under Apache 2.0 license now.
+* C-Producer - New feature
+  * Language level is C89. It should work for all GCC versions, tested minimum GCC version is 4.1.
+  * The Kinesis Video Streams C producer library wraps kinesis-video-pic (Platform Independent Code) with additional layer of API that allows scenario and platform-specific callbacks and events.
+  * Callbacks for sample retry logic implementation are now supported through C Producer
+* CPP Producer - Updates
+  * Language level is C++11 instead of C++14. Required minimum GCC version is 4.8.
+  * Kinesis Video Producer CPP (kinesis-video-producer directory) is now revised to a wrapper of C Producer SDK which interfaces with the Platform Independent Repository (PIC, kinesis-video-pic directory).
+* Platform Independent Code - New functionality
+  * Automatic CPD (codec private data) extraction from the stream
+  * Reset stream and reset connection functionality in PIC - In case of unrecoverable errors users can simply call reset stream; internally SDK will free & create the stream.
+  * Log level supported in PIC. It can be set in member variable of DeviceInfo.ClientInfo.
+* Platform Independent Code - Bug Fixes
+  * Skip over error fragments - SDK will continue skip any invalid fragments are ingested through SDK earlier and continue streaming with valid ingested fragments. It will not just loop back and keep resending the broken fragment now.
+* All unit tests (pic_test, cproducer_test, producer_test) are at C++11 level. Required minimum GCC version is 4.8.
+
+* Please note the following changes if you have customized the SDK for your integration and not using samples directly.
+  * Changes to utility functions:
+    * RotatingStaticCredentialProvider is removed from C++ producer. Customer can use StaticCredentialProvider instead. 
+    * CredentialProviderUtil and SerializedCredentials are removed from C++ producer.
+  * Following functions are removed from DefaultCallbackProvider: sleepUntilWithTimeCallback, shutdownStream, notifyResult, getControlPlaneUri, safeFreeBuffer, getStreamStatusFromString.
+  * Changes to the object model:
+    * Following attributes have been added: Version number is added to TrackInfo, Frame, StreamDescription, DeviceInfo, StreamInfo.
+    * Following attributes have been removed: certPath is removed from DeviceInfo in PIC.
+
 #### Release 1.7.9 (13th Mar 2019)
 * Fix memory leak in kinesis_video_gstreamer_audio_video_sample_app.
 

docker_native_scripts/Dockerfile

@@ -1,6 +1,8 @@
-FROM ubuntu:17.10
+FROM ubuntu:18.04
 
+RUN apt-get upgrade
 RUN apt-get update
+
 RUN apt-get install -y git && \
     apt-get install -y vim  && \
     apt-get install -y curl && \

docker_native_scripts/windows/Dockerfile

@@ -1,7 +1,7 @@
 
 # Dockerfile to build Kinesis Video Streams Producer CPP as a Windows container
 
-FROM microsoft/windowsservercore
+FROM mcr.microsoft.com/windows/servercore:ltsc2019
 WORKDIR /opt/
 
 # ================= Install Git ============================================================================

docker_native_scripts/windows/windows-docker-readme.md renamed to docker_native_scripts/windows/README.md

@@ -1,3 +1,4 @@
+
 #### Instructions for installing Kinesis Video Streams Producer SDK on Linux (Ubuntu, Raspberry PI)
 
 ----
@@ -98,6 +99,10 @@ If you are using Raspberry pi, you can also install the `gstreamer1.0-omx` packa
 ```
 sudo apt-get install gstreamer1.0-omx
 ```
+If `make` is not installed already you can install `make` using
+```
+sudo apt-get install make
+```
 Run the build script: (within `kinesis-video-native-build` folder)
 ```
 ./min-install-script
@@ -122,7 +127,8 @@ $ ./java-install-script
 ```
 
 ----
-### Running Examples:
+### How to run sample applications for sending media to KVS using [GStreamer](https://gstreamer.freedesktop.org/):
+
 ##### Setting credentials in environment variables
 Define AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY environment variables with the AWS access key id and secret key:
 
@@ -141,7 +147,7 @@ the LD_LIBRARY_PATH as below:
 ```
 export LD_LIBRARY_PATH=/opt/awssdk/amazon-kinesis-video-streams-producer-sdk-cpp/kinesis-video-native-build/downloads/local/lib:$LD_LIBRARY_PATH
 ```
-* (Skip this if you installed gstreamer using apt-get) The `gst-launch-1.0` and `gst-inspect-1.0` binaries are built inside the folder `<YourSdkFolderPath>/kinesis-video-native-build/downloads/local/bin`. You can either run the following commands from that folder using `./gst-launch-1.0` or you can include that in your **PATH** environment variable using the following export command and run `gst-launch-1.0`
+* (Skip this if you installed GStreamer using `apt-get`) The `gst-launch-1.0` and `gst-inspect-1.0` binaries are built inside the folder `<YourSdkFolderPath>/kinesis-video-native-build/downloads/local/bin`. You can either run the following commands from that folder using `./gst-launch-1.0` or you can include that in your **PATH** environment variable using the following export command and run `gst-launch-1.0`
 ```
 $ export PATH=<YourSdkFolderPath>/kinesis-video-native-build/downloads/local/bin:$PATH
 ```
@@ -150,7 +156,7 @@ $ export PATH=<YourSdkFolderPath>/kinesis-video-native-build/downloads/local/bin
 $ export GST_PLUGIN_PATH=<YourSdkFolderPath>/kinesis-video-native-build/downloads/local/lib:$GST_PLUGIN_PATH
 ```
 
-###### Discovering available devices.
+###### Discovering audio and video devices available in your system.
 Change your current working directory to `<YourSdkFolderPath>/kinesis-video-native-build/downloads/local/bin`;
 then run the `gst-device-monitor-1.0` command to identify available media devices in your system. An example output as follows:
 ```
@@ -182,15 +188,15 @@ Device found:
 	gst-launch-1.0 v4l2src device=/dev/video4 ! ...
 ```
 
-###### Running the `gst-launch-1.0` command to start streaming from RTSP camera source.
+###### Running the `gst-launch-1.0` command to start streaming from a RTSP camera source.
 ```
-$ gst-launch-1.0 -v rtspsrc location=rtsp://YourCameraRtspUrl short-header=TRUE ! rtph264depay ! video/x-h264, format=avc,alignment=au ! kvssink stream-name=YourStreamName storage-size=128
+$ gst-launch-1.0 -v rtspsrc location=rtsp://YourCameraRtspUrl short-header=TRUE ! rtph264depay ! video/x-h264, format=avc,alignment=au ! h264parse ! kvssink stream-name=YourStreamName storage-size=128
 ```
 
 **Note:** If you are using **IoT credentials** then you can pass them as parameters to the gst-launch-1.0 command
 ```
 $ gst-launch-1.0 -v rtspsrc location="rtsp://YourCameraRtspUrl" short-header=TRUE ! rtph264depay ! video/x-h264, format=avc,alignment=au !
- kvssink stream-name="iot-stream" iot-certificate="iot-certificate,endpoint=endpoint,cert-path=/path/to/certificate,key-path=/path/to/private/key,ca-path=/path/to/ca-cert,role-aliases=role-aliases"
+ h264parse ! kvssink stream-name="iot-stream" iot-certificate="iot-certificate,endpoint=endpoint,cert-path=/path/to/certificate,key-path=/path/to/private/key,ca-path=/path/to/ca-cert,role-aliases=role-aliases"
 ```
 You can find the RTSP URL from your IP camera manual or manufacturers product page.
 
@@ -206,7 +212,7 @@ $ gst-launch-1.0 -v v4l2src device=/dev/video0 ! h264parse ! video/x-h264,stream
 ###### Running the `gst-launch-1.0` command to start streaming from camera source in **Raspberry-PI**.
 
 ```
-$ gst-launch-1.0 -v v4l2src do-timestamp=TRUE device=/dev/video0 ! videoconvert ! video/x-raw,format=I420,width=640,height=480,framerate=30/1 ! omxh264enc periodicity-idr=45 inline-header=FALSE ! h264parse ! video/x-h264,stream-format=avc,alignment=au ! kvssink stream-name=YourStreamName access-key="YourAccessKey" secret-key="YourSecretKey"
+$ gst-launch-1.0 -v v4l2src do-timestamp=TRUE device=/dev/video0 ! videoconvert ! video/x-raw,format=I420,width=640,height=480,framerate=30/1 ! omxh264enc periodicty-idr=45 inline-header=FALSE ! h264parse ! video/x-h264,stream-format=avc,alignment=au ! kvssink stream-name=YourStreamName access-key="YourAccessKey" secret-key="YourSecretKey"
 ```
 or use a different encoder
 ```
@@ -320,7 +326,7 @@ You can also choose to use other video devices by doing
 
 `export AWS_KVS_VIDEO_DEVICE=/dev/video1`
 
-If no `AWS_KVS_VIDEO_DEVICE` environment variable was detected, the sample app will use the default video device.
+If no `AWS_KVS_VIDEO_DEVICE` environment variable was detected, the sample application will use the default video device.
 After the environment variables are set, launch the sample application with a stream name and it will start streaming.
 ```
 AWS_ACCESS_KEY_ID=YourAccessKeyId AWS_SECRET_ACCESS_KEY=YourSecretAccessKey ./kinesis_video_gstreamer_audio_video_sample_app <my-stream>
@@ -330,6 +336,15 @@ AWS_ACCESS_KEY_ID=YourAccessKeyId AWS_SECRET_ACCESS_KEY=YourSecretAccessKey ./ki
 
 Refer the **README.md** file in the  *docker_native_scripts* folder for running the build and RTSP demo application within Docker container.
 
+### How to run sample applications for sending H264 video files to KVS
+
+The sample application `kinesis_video_cproducer_video_only_sample` sends h264  video frames inside the folder `kinesis-video-c-producer/samples/h264SampleFrames` to KVS.
+The following command sends the video frames in a loop for ten seconds to KVS.
+`./kinesis_video_cproducer_video_only_sample YourStreamName 10`
+
+If you want to send H264 files from another folder (`MyH264FramesFolder`) you can run the sample with the following arguments
+`./kinesis_video_cproducer_video_only_sample YourStreamName 10 MyH264FramesFolder`
+
 ##### Additional examples
 
 For additional examples on using Kinesis Video Streams Java SDK and  Kinesis Video Streams Parsing Library refer:
@@ -339,14 +354,23 @@ For additional examples on using Kinesis Video Streams Java SDK and  Kinesis Vid
 ##### [Kinesis Video Streams Android SDK](https://github.com/awslabs/aws-sdk-android-samples/tree/master/AmazonKinesisVideoDemoApp)
 ----
 
-##### Running C++ Unit tests
+##### Running C++ unit tests
 
-The executable for **unit tests** will be built in `./start` inside the `kinesis-video-native-build` directory. Launch it and it will run the unit test and kick off dummy frame streaming.
+**Note:** Please set the [credentials](https://github.com/awslabs/amazon-kinesis-video-streams-producer-sdk-cpp/blob/master/install-instructions-linux.md#setting-credentials-in-environment-variables) before running the unit tests.
+
+The executable for **unit tests** will be built as `./producer_test` inside the `kinesis-video-native-build` directory. Launch it and it will run the unit test and kick off dummy frame streaming.
+
+##### Running C unit tests
+
+The executable for **unit tests** will be built as `./cproducer_test` inside the `kinesis-video-native-build` directory.
+
+##### Running PIC unit tests
+
+The executable for **unit tests** will be built as `./pic_test` inside the `kinesis-video-native-build` directory.
 
 ##### Enabling verbose logs
 Define `HEAP_DEBUG` and `LOG_STREAMING` C-defines by uncommenting the appropriate lines in CMakeList.txt in the kinesis-video-native-build directory.
 
-
 ----
 #####  How to configure logging for producer SDK sample applications.
 

install-instructions-linux.md

@@ -48,7 +48,7 @@ The bulk of the **install script** is building the open source dependencies. The
 
 First make sure that the following libraries have been installed using Homebrew
 ```
-brew install pkg-config openssl cmake gstreamer gst-plugins-base gst-plugins-good gst-plugins-bad gst-plugins-ugly log4cplus
+brew install pkg-config openssl cmake gstreamer gst-plugins-base gst-plugins-good gst-plugins-bad gst-plugins-ugly log4cplus gst-libav
 ```
 
 After all required libraries have been installed, run
@@ -111,14 +111,14 @@ Device found:
 ###### Running the `gst-launch-1.0` command to start streaming from RTSP camera source.
 
 ```
-$ gst-launch-1.0 rtspsrc location=rtsp://YourCameraRtspUrl short-header=TRUE ! rtph264depay ! video/x-h264, format=avc,alignment=au ! kvssink stream-name=YourStreamName storage-size=128 access-key="YourAccessKey" secret-key="YourSecretKey"
+$ gst-launch-1.0 rtspsrc location=rtsp://YourCameraRtspUrl short-header=TRUE ! rtph264depay ! video/x-h264, format=avc,alignment=au ! h264parse ! kvssink stream-name=YourStreamName storage-size=128 access-key="YourAccessKey" secret-key="YourSecretKey"
 ```
 
 **Note:** If you are using **IoT credentials** then you can pass them as parameters to the gst-launch-1.0 command
 
 ```
 $ gst-launch-1.0 rtspsrc location=rtsp://YourCameraRtspUrl short-header=TRUE ! rtph264depay ! video/x-h264, format=avc,alignment=au !
- kvssink stream-name="iot-stream" iot-certificate="iot-certificate,endpoint=endpoint,cert-path=/path/to/certificate,key-path=/path/to/private/key,ca-path=/path/to/ca-cert,role-aliases=role-aliases"
+ h264parse ! kvssink stream-name="iot-stream" iot-certificate="iot-certificate,endpoint=endpoint,cert-path=/path/to/certificate,key-path=/path/to/private/key,ca-path=/path/to/ca-cert,role-aliases=role-aliases"
 ```
 You can find the RTSP URL from your IP camera manual or manufacturers product page.
 
@@ -219,6 +219,17 @@ AWS_ACCESS_KEY_ID=YourAccessKeyId AWS_SECRET_ACCESS_KEY=YourSecretAccessKey ./ki
 ##### Using Docker to run the sample application
 Refer the **README.md** file in the  *docker_native_scripts* folder for running the build and **RTSP sample application** to start streaming from **IP camera** within Docker container.
 
+### How to run sample applications for sending H264 video files to KVS 
+ 
+The sample application `kinesis_video_cproducer_video_only_sample` sends h264  video frames inside the folder `kinesis-video-c-producer/samples/h264SampleFrames` to KVS.
+The following command sends the video frames in a loop for ten seconds to KVS. 
+you can run `./kinesis_video_cproducer_video_only_sample YourStreamName 10`
+`./kinesis_video_cproducer_video_only_sample YourStreamName 10`
+ 
+If you want to send H264 files from another folder (`MyH264FramesFolder`) you can run the sample with the following arguments
+`./kinesis_video_cproducer_video_only_sample YourStreamName 10 MyH264FramesFolder`
+
+
 ##### Additional examples
 For additional examples on using Kinesis Video Streams Java SDK and  Kinesis Video Streams Parsing Library refer:
 
@@ -228,7 +239,19 @@ For additional examples on using Kinesis Video Streams Java SDK and  Kinesis Vid
 -----
 
 ##### Running C++ Unit tests
-The executable for **unit tests** will be built in `./start` inside the `kinesis-video-native-build` directory. Launch it and it will run the unit test and kick off dummy frame streaming.
+
+**Note:** Please set the [credentials](https://github.com/awslabs/amazon-kinesis-video-streams-producer-sdk-cpp/blob/master/install-instructions-macos.md#setting-credentials-in-environment-variables) before running the unit tests. 
+
+The executable for **unit tests** will be built as `./producer_test` inside the `kinesis-video-native-build` directory. Launch it and it will run the unit test and kick off dummy frame streaming.
+
+##### Running C unit tests
+
+The executable for **unit tests** will be built as `./cproducer_test` inside the `kinesis-video-native-build` directory. 
+
+##### Running PIC unit tests
+
+The executable for **unit tests** will be built as `./pic_test` inside the `kinesis-video-native-build` directory. 
+
 
 ##### Enabling verbose logs
 Define `HEAP_DEBUG` and `LOG_STREAMING` C-defines by uncommenting the appropriate lines in CMakeList.txt in the kinesis-video-native-build directory.