Configure the Basic Uploader

Configure the Basic Uploader

Configuring the Basic Uploader

Use the following information as a guide to configure how the basic uploader uploads a finished video file. Also see Setting Basic Uploader Properties for other properties you can set to customize the user interface.

Table of Contents

Description of Basic Uploading

The Basic Uploader provides a standard user interface and publishing option using a PUSH or PUT request to upload the video to your backend.

After the user completes a recording they will see an optional form to enter a title and/or description for their recording and an "Upload" button to start the upload.

When the user clicks the "Upload" button the app will make a request to your backend to the URL provided in the basicupload.request.url property using a POST request to send any title/description, or if not collecting title/description, a GET request is made:


The response from the MyUrlProvider script must be a single line of text with a URL where the actual mp4 video should be POSTed (or PUT).  For example if you were using the S3 Amazon Example below then the response returns a presigned Amazon S3 URL where we have permissions to post:

Once the app has this final URL, it will make a POST (or PUT) request with the body of the request being the mp4 file. The body is not encoded (like form data from a browser), but a raw mp4 file.

Take a look at the full list of Basic Uploader Properties to see how to customize branding and message strings in the screen recorder and video editor.

Amazon S3 Upload Example

Here's an example PHP script that you can use to sign a URL and upload directly to Amazon S3.  To use this script you'd set the following properties when launching:  

"basicupload.request.url": "http://.../basicuploadS3Upload.php",

In this case we also need an extra property to set an additional header which is sent to Amazon S3 with the PUT request to mark that this mp4 is publicly readable.

Here's an example basicuploadS3Upload.php which creates a signed URL that we can use to PUT the mp4 file on Amazon S3:

<?php // Requires this php library ( require_once('Crypt/HMAC.php');
// If you are using the title/desc options then this request will be a POST and have these: $title = $_POST['title']; $desc = $_POST['description'];
// The result of this request must be a single string with the real URL to PUT the mp4 video file. // In this example we are going to PUT to s3 bucket and folder: echo createUrl("BUCKET/folder/video_name.mp4","PUT","video/mp4");
// // Functions to create the signed URL to PUT in Amazon S3 button... // function createUrl($object, $method, $contentType) { $S3_URL = ""; $accessIdKey = "YOUR_S3_PUBLIC_KEY"; $accessIdSecret = "YOUR_S3_PRIVATE_KEY"; $expires = time() + 120; // They have 1 minutes to do the upload else this URL will expire
// Note this will upload video with public-read so you can stream from the bucket. $stringToSign = "$method\n\n$contentType\n$expires\nx-amz-acl:public-read\n/$object"; $hasher =& new Crypt_HMAC($accessIdSecret, "sha1"); $sig = urlencode(hex2b64($hasher->hash($stringToSign))); return "$S3_URL/$object?AWSAccessKeyId=$accessIdKey&Expires=$expires&Signature=$sig"; }
function hex2b64($str) { $raw = ''; for ($i=0; $i < strlen($str); $i+=2) { $raw .= chr(hexdec(substr($str, $i, 2))); } return base64_encode($raw); } ?>

Save on Server Upload Example

The following example uses PHP to read the raw input stream of the POST request and writes to a local file.

To use this script you'd set the following properties when launching:  

"basicupload.request.url": "http://.../basicuploadSaveUpload.php",

The basicuploadSaveUpload.php script below reads the mp4 file from the request input stream and saves to a local file in /tmp, but it can be placed anywhere on the server that you have write permission:

    /* data comes in on the stdin stream */
    $putdata = fopen(""php://input"", ""r"");
    $fp = fopen(""/tmp/test.mp4"", ""w"");
    /* Read the data 1 KB at a time and write to the file */
    while ($data = fread($putdata, 1024))
    fwrite($fp, $data);
    /* Close the streams */

Customizing the Success Message

After the upload a message is displayed to the user.  To provide a custom message to your users, change the upload success message by setting this property:

properties: {    
"basicupload.success.message": "Enter a custom html message here"

Turning Off Autodelete

By default the recorder will remove the local recording from the computer after a successful upload.  If you'd like the user to manage their own recordings using the recordings manager then you can disable this feature by setting this property:

properties: {
    "som.*.app.upload.deleteafter": false

Sending the User to a URL

After a successful upload the app can open a URL by setting this property:

properties: {    
"som.*.app.upload.onexit.action": "http://yoururl/"

You can also return a URL as the text result of the PUT/POST upload in which case you can set the value to "gotoplayback" which will open that URL.

When setting this property the app will show a "Continue" button to the user after a successful upload and then open this URL when they click the continue button.

Launching the Editor (Without First Capturing)

To launch the local recordings manager without first doing a screencast, change the behavior of the launcher to open a window showing local recordings on the computer. Do this by adding the property showManager: true to the launch properties. For example:

properties: {
    "showManager": "true",

    • Related Articles

    • Configure the Custom Uploader

      Use the following information as a guide to configure the features of custom publishing. Table of Contents Description Sample Custom Implementation File Specifications Custom Publishing Sample (HTML) ...
    • Basic Uploader Properties

      Basic Uploader Properties Use the following properties to specify the upload of the recorded screen capture. Note that some properties are required and others are optional. Specify any of these by adding them to the launch properties. Table of ...
    • Configure how your video can be viewed and discovered

      You can configure specific settings in your hosting account to control how viewers discover and view your videos and images, including adding security protections. 1. Login to your account and visit MyContent. 2. Visit Details for you video or image. ...
    • Configure your Cloudflare proxy for an SSL certificate

      If you are using Cloudflare and you want to use a custom domain (CNAME) with an SSL certificate to host your content, you need to disable the proxy in your Cloudflare settings. Doing this enables us to successfully issue you an SSL certificate for ...
    • Overview of the Screen Recorder Launcher API

       Overview of the Screen Recorder Launcher API This guide is for customers who have the Enterprise or Solution Builder Plan and want to incorporate the screen recorder software into their network and application(s). The guide can also be used to ...