Pipe changelog addpipe.com

Fix

Finally managed to pinpoint the cause of the issue.

The culprit for the resulting low audio was the audio constraint echoCancellation when set to false. Setting it to true solved the issue.

Here is a quick overview of what audio constraints were being set and what is being set now:

So to sum it up, we've decided to remove echoCancellation altogether and rely on the browser defaults which is echoCancellation set as true for Chrome, Safari, and Firefox.

New

To take full advantage of our two existing US regions, we've implemented a fallback mechanism at the recorder level, that springs into action if one of the US regions is down.

This new mechanism applies to both the recordings made with the HTML5 recorder via streaming and to uploads from desktop and the mobile native recorder, but each works a little differently.

Fallback for streaming

The HTML5 streaming recorder will automatically fallback to the other US recording server if the initial connection to the assigned US recording server fails to connect in a timeframe of 10 seconds. Once a successful connection is established, the recorder will stick to that connection. If any other disconnects occur, the reconnect attempts will be made to the same US server.

Fallback for uploads

When it comes to uploads from desktop or the mobile native recorder, the recorder will have 3 attempts to connect to the assigned US recording server and if all of them fail, it will automatically fallback to the other US recording server and retry the upload. Again, once a successful connection is established, the recorder will stick to that connection.

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.

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

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

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

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 :)

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.

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

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.

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.

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).

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.

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.

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.