Pipe changelog
Pipe changelog
addpipe.com

Separate control of recording options for the desktop and inline recorder

 

New

  

We've heard your requests and we've listened.

Thanks to the new embed code setting, avrec, now you can show or hide the option to record video/audio just like you can show/hide the other options displayed in the initial screen of the recorder.

If the avrec setting is not specified in the embed code or is set to 1, the record video/audio option will be displayed. To hide it, simply set it to 0.

With this newly added setting together with the setting srec and dup, you can now separately show or hide all 3 options in the initial screen of the recorder: record video/audio, screen recording, and upload video/audio.

Additionally to this, we've added a new dropdown in the embed dashboard section that allows you to directly choose what type of recorder you wish to embed.

Screenshot 2021-11-18 122713.png

Of course, having any combination of the 3 options is still possible by manually editing your embed code.

Beta support for Safari on macOS

 

New

  

We are glad to announce that our HTML5 desktop recorder now supports Safari on macOS, although since Safari is still considering its MediaStream Recording API implementation experimental, support will be in beta for a while

To enable recording on Safari with our desktop HTML5 recorder simply take the following steps:

  1. Go to your environment edit dashboard
  2. Scroll down to the Desktop Recording Clients section
  3. Click the Safari support checkmark and then Save environment

Screenshot-2021-10-15-at-12.30.40.png

To find out more about this new release check out our blogpost.

Better German translation

 

Improvement

  

To all our Deutsch speaking friends, you should now rest easy.

After the received feedback and some rounds of German language classes, we have updated our german translation across the board :)

The FPS for video recordings is now configurable

 

New

  

Until now, the FPS (frames per second) that was requested from your users' webcam through our HTML5 desktop recording client was hardcoded to 30.

This has changed, as you can now configure the desired FPS directly from the audio-video XML quality profile. You can set any integer values like 15, 24 or 60, but keep in mind that to achieve higher framerates, you need a more capable camera.

If the requested framerate is not supported, it will default to the nearest supported one.

Added new S3 endpoints

 

Improvement

  

We've updated the S3 endpoints available in the push to S3 section of the Pipe account area and added the following missing AWS regions:

  • Europe (Paris) eu-west-3
  • Europe (Milan) eu-south-1
  • Europe (Stockholm) eu-north-1
  • Asia Pacific (Hong Kong) ap-east-1
  • Asia Pacific (Osaka) ap-northeast-3
  • Africa (Cape Town) af-south-1
  • China (Beijing) cn-north-1
  • China (Ningxia) cn-northwest-1
  • Middle East (Bahrain) me-south-1

Screen recording permissions and UI updates

 

Improvement

 

 

We've made a few changes recently to our screen recording solution.

Now the recorder will first ask permission to use the microphone and then ask permission to record the screen. It used to be the other way around, which caused issues when choosing to record a tab.

Given the fact that recording the screen is a lot more privacy intrusive than recording with a webcam and can pose a security risk, best practices dictate to make sure that the user is the one asking the screen to be recorded and not a malicious actor.

To this extent, we've added an extra step needed to be taken after choosing the [Record Screen] option.

image.png

The [Select screen for capture] is no longer a simple text, but a button that needs to be clicked in order to select the window/screen you wish to capture and ask for permission for doing so.

Full HD resolution option can now be easily enabled from the embed dashboard

 

New

 

 

You can now choose the 1080p resolution option directly when generating your embed code if you wish to record Full HD videos (PRO accounts only).

image.png

Keep in mind that even though you may ask for the 1080p resolution from the camera, not all webcams are Full HD capable, so the browser will default to the nearest resolution supported by the webcam.

Fixed issue with max size value

 

Fix

 

 

Today we've fixed an issue where the max value for our size metadata for both the source file and the processed mp4 was limited to 2GB (or 2147483647 bytes more exactly).

The source file size metadata was shown in the Pipe account area's recordings page. The processed mp4 size metadata, apart from being displayed on the above page, was also used in calculating the bitrate and was available through the REST v1 API and five webhooks.

Screenshot 2021-08-03 at 14.06.32.png

There were only 68 recordings in our database where the source file's size was maxed out and 49 where the processed file's size was maxed out.

Webhooks can now be sent with Content-type: application/json

 

New

 

Improvement

 

 

Until recently, the webhook data was sent only as application/x-www-form-urlencoded.

Now you can choose between sending the data the old way as application/x-www-form-urlencoded OR the new way as application/json.

All new webhooks will default to application/json.

image.png

All existing webhooks will continue to be sent as application/x-www-form-urlencoded, unless you choose to change them.

The content type of the webhook will be reflected in the schedule and logs pages of the webhooks section. Also, the webhook simulator will allow you to test the webhook with both content types.

Fixed issue with the recording not stopping at the maximum recording time (mrt setting) if the recorder was removed from DOM

 

Fix

 

 

Until now, if the Pipe desktop recording client was removed from the DOM before hitting the maximum recording limit, the recording simply continued forever until the user left or closed the webpage on which the Pipe recording client was embedded on.

The issue has been fixed today when we rolled out new, updated client side (pipe.js) files.

This only occurred when the Pipe recording client was removed using custom JS code. Removing the Pipe recorder with the built in remove function worked as expected and is the recommended way to remove Pipe from a webpage.