Pipe changelog addpipe.com

New

The users can now remove themselves completely from our News & Product Updates list rather than subscribing and unsubscribing.

New

We now save the User Agent when a password reset was made and we display it in the Account's Sessions to let you see when and from what device was a password reset initiated.

Improvement

On the Dropbox Integration page the user is now able to see which email is connected for each recording environment.

If the user disconnects the Dropbox App, he will see the remaining time it will take for the changes to reflect to our servers, or can manually remove the credentials by pressing a button.

New

Fix

We have updated the Recordings page:

1. Implemented the option for the users to filter their recordings by the UTC date.
2. The Copy and conversion delay is now present for each recording
3. The switching pages of recordings now works properly.

Improvement

We have made a better user experience by making it clearer and notifying the user with an alert that at least one video output should be selected on Transcoding Engine page.

Improvement

We've updated the Singing Webhooks docs with:

1. new info regarding what data needs to be signed (and how to get it) when using application/json instead of application/x-www-form-urlencoded
2. updated PHP code
3. "Signing" instead of "Authenticating"

le: added a new Python & Flask code example

New

We've just released our new integration with Dropbox.

This simplifies the whole process and streamlines the authorization using the industry standard oAuth flow.

If you are using Dropbox to store your Pipe recordings, we encourage you to switch to the new integration.

le: the new integration is covered in this new blog post.

New

We have just launched a feature that allows you to export your recording data.

You can access this new feature by going to: https://dashboard.addpipe.com/export

On this page you will be able to set a date range for the export, select the environments you wish to export data for, and choose whether or not to export additional datasets(personal data, recording output data) alongside the default dataset.

Some example use cases for the exported recording data:

• importing the data into other tools for analyzing
• downloading all the recordings that are stored by Pipe
• review of the PII we process alongside the recordings
• backup

LE: More details on this new feature can be found in the blogpost.

We've now limited access to our EU1 only region option to those environments that already have it selected.

Fix

Fixed an issue where, when there was a queue of recordings that needed to be processed - because of large volumes of incoming recordings - recordings uploaded through our native mobile recording client would be processed after the recordings streamed or uploaded through the desktop recording client.

Historically, recordings streamed or uploaded through our desktop recording client had higher priority.

This also paves the way for a better use of priorities.