Replies: 2 comments 5 replies
-
|
I've progressed on this matter so that it can be deployed and running on iOS devices on ARM64 (Apple M processors), see the recipe below. At this point my test app on the iPad starts where it defines a pipeline in which the sink is to an AWS Kinesis video stream that is already created (which I've already verified on my MAC OSx). However, on the iPad it fails due to certificate issues see below:
I'm looking into possibly using the However, this seems to me as heavy handed solution. I'd rather find another option. Any suggestions? Regards, Recipe to get AWS Video Stream AWS Video Stream GStreamer plugin build and deployed for iOS platforms Build the AWS Video Stream GStreamer plugin as a static library libgstkvssink.a as well as all of its dependencies such as:
Adapt the XCode project(s) as to reference as to provide the library folder path(s) to those static libraries and directives for each static library. After which, provide the following code to declare & register the kvssink plugin. This is usually done in the gst_ios_init.m file, see GStreamer's iOS examples. ...
#if defined(GST_IOS_PLUGIN_KVSSINK)
GST_PLUGIN_STATIC_DECLARE(kvssink);
#endif
void
gst_ios_init (void)
{
...
#if defined(GST_IOS_PLUGIN_KVSSINK)
GST_PLUGIN_STATIC_REGISTER(kvssink);
#endif
...
} |
Beta Was this translation helpful? Give feedback.
-
|
I've troubleshooting the issue CA certificates when running on iOS devices. Typically those certificates are stored in Keychain but since iOS 13.0 and the Secure-Transport capabilities is deprecated and to use Network framework instead and thus libCURL doesn't have access the CA certificates stored in the Keychain.
As a workaround, I proceeded to bundle a CA certificates file with the app and for the app to set an environment variable which the AWS Kinesis video streamer code when preparing a CURL request when the certPath variable is undefined or empty. .../libkvscproducer/kvscproducer-src/src/source/Request.c STATUS createCurlRequest(HTTP_REQUEST_VERB curlVerb, PCHAR url, PCHAR body, STREAM_HANDLE streamHandle, PCHAR region, UINT64 currentTime,
UINT64 connectionTimeout, UINT64 completionTimeout, UINT64 callAfter, PCHAR certPath, PAwsCredentials pAwsCredentials,
PCurlApiCallbacks pCurlApiCallbacks, PCurlRequest* ppCurlRequest)
{
...
PCHAR caCertPath = (certPath != NULL && certPath[0] != 0) ? certPath : getenv(CACERT_PATH_ENV_VAR);
if (caCertPath != NULL) {
STRNCPY(pCurlRequest->requestInfo.certPath, caCertPath, MAX_PATH_LEN);
}
...
Unfortunately, I've arrived at the next impediment (issue) where AWS Kinesis Video Producer SDK C++ fails to start the sink. This time the error message is cryptic (at best) with logging set to trace levels.
The value 0x15000020 without a message isn't significant about where to proceed in investigating the cause or causes. I'd appreciate any insight for those whom support this project or from some that has become familiar with the implementation details on how to troubleshoot such issues with this project. Regards, Logged messages... |
Beta Was this translation helpful? Give feedback.
-
|
The status code https://github.com/awslabs/amazon-kinesis-video-streams-producer-c/blob/5fb356e484d734ce3650c751a4469985c488bc1f/src/include/com/amazonaws/kinesis/video/common/Include.h#L49 There are 2 KVS-owned dependent libraries of this C++ producer:
If you're not able to find the definition in this repo, then it's probably in the other two repos. Try printing out the string and make sure it's also properly null terminated. Regarding IoT certs, you can refer to https://docs.aws.amazon.com/kinesisvideostreams/latest/dg/how-iot.html, those are used to obtain temporary access key, secret key, eventually once you get past PoC stage, when you deploy it to actual devices in the field and you don't want to hard-code credentials in your application. |
Beta Was this translation helpful? Give feedback.
-
|
You may also want to double check what these are set to, if any. |
Beta Was this translation helpful? Give feedback.
-
|
I found & resolved which was due to passing a file path of 'ca-bundle.crt' rather than a file path with a '.pem' file extension as you've stated. I appreciate your reply & those references links & these error codes will be handy (hopefully not too often). With that quick correction in place the stream is ready. As before the next impediment is a failure when transitioning the GStreamer pipeline to a PLAYING state due to an internal error. Here is an example pipeline that I'm using. I learnt that the kvssink plugin accepts h264 & h265 as well as avc thus I'm defining the pipeline accordingly. I use GStreamer's test video signal as the source as a baseline to verify that video is streamed to AWS Kinesis video stream. I've also tried with the GStreamer plugin for Apple devices avfvideosrc as the source.
Regards, |
Beta Was this translation helpful? Give feedback.
-
|
Hi, I tried out the pipeline you shared above and it's is working fine on my mac: gst-launch-1.0 videotestsrc is-live=true ! video/x-raw, framerate=10/1, width=640, height=480 ! vtenc_h264_hw allow-frame-reordering=FALSE realtime=TRUE max-keyframe-interval=45 bitrate=500 ! h264parse ! video/x-h264, stream-format=avc, alignment=au, profile=baseline ! kvssink stream-name=demo-streamNote that it does take a little bit to show up in the console playback though. It can load quicker if you reduce the max-key-frame interval in the encoder. I also tried using this pipeline on my Mac, also with success uploading. gst-launch-1.0 avfvideosrc ! vtenc_h264_hw allow-frame-reordering=FALSE realtime=TRUE max-keyframe-interval=45 bitrate=500 ! h264parse ! kvssink stream-name="hi"I'm not sure that the
You can try using the non-hardware version instead: https://gstreamer.freedesktop.org/documentation/applemedia/vtenc_h264.html?gi-language=c Other than that, I don't see anything else obvious in your pipeline. Can you share the error you're seeing? |
Beta Was this translation helpful? Give feedback.
-
|
HI @sirknightj , As you've mention support & GStreamer capabilities running on a MacOS (Sequoia 15.0+) tends to be more complete than with its iOS (18.0+) counterpart. I've got a GStreamer pipeline in which the iPad device to stream video to a video stream endpoint on the AWS Kinesis Video stream. That pipeline consists of using vtenc_h264 + *h264parse in which their properties are set to their default settings. When playing back the video using the Media playback of that video stream's AWS Kinesis Video page, it reports:
To resolve this issue(s), I'll have to adjust the settings provided in the pipeline for the vtenc_h264 + *h264parse and probably kvssink as reduce these occurrences during playback of the video stream from AWS Video Kinesis. Once I find those settings (that is good enough for my use case) I'll post it here. None the less, it's good seeing video being streamed from an iPad device to a video stream running on AWS Kinesis Video service. I appreciate your support and guidance on this matter. Regards, P.S. It's also good to confirm that the Amazon Kinesis Video Streams producer SDK C++ project can be built to run on iOS devices. Albeit that is does require tweaks to make files & an implementation workaround so that libCurl has access the CA certificates in order to authenticate the AWS Kinesis Video service endpoint. |
Beta Was this translation helpful? Give feedback.
-
The GStreamer project supports Apple's iOS platform* such as iPhone and iPad devices whereas the AWS Kinesis Video streams producer SDK project (referred to as this SDK project) already supports Mac OS platform, but I haven't found any documentation/topic about building and deploying the AWS kvssink plugin for iOS platform.
For building this SDK project, I followed the guidelines along with option to build the GStreamer plugin (kvssink). This produces a dynamic library (libgstkvssink.dylib).
I use an iPad app to validate GStreamer in which I can provide a GStreamer pipeline using some of the common GStreamer plugins to ensure that GStreamer on iPad works.
When I include the libgstkvssink.dyilb into the iPad and when I put the kvssink directive into the pipeline, the app fails because it lacks dependencies such libgstreamer-1.0.0.dylib & libgstbase-1.0.0.dylib.
My questions for this discussion group:
I'm reaching out to this group before exploring into other avenues. One of which is to incorporate the kvssink as a GStreamer's subproject is built into GStreamer as a static library. Thus GStreamer iOS package contains the kvssink as static libraries alongside the other common plugins of the other subprojects.
Regards,
Steven Belbin
Beta Was this translation helpful? Give feedback.
All reactions