New

Fix

Chrome 111 was released Tuesday, March 7, 2023, and it introduced a breaking MediaRecorder API change which resulted in corrupt recordings made by the Pipe recorder.

We've caught the bug quickly and implemented a workaround in our code in pipe.js (embed code v1.0 and v2.0) to circumvent the issue until Chrome fixes it.

If you are using a self-hosted version of pipe.js we strongly recommend that you update it, or better still, use the one delivered by Pipe to ensure you have access to the latest features and fixes soon as they are released.

New

We've just rolled out a new feature in the Beta phase that allows you to whitelist the hosts where the Pipe embed code can be added. This is useful to prevent abuse from malicious users that could embed your generated Pipe embed code on other websites.

The whitelist can be set up at the environment level so that you can have specific whitelists for each of your environments that could be related to different websites.

Access the new Whitelisted hosts section by editing any of your environments and add the hosts you want to whitelist.

The list will be empty by default, meaning any host will be allowed.

For more information about this new feature, you can read the documentation.

Improvement

We have reviewed and updated our webhook documentation and the webhook simulator data from the account dashboard.

1. Aligned the docs and simulator examples with the actual webhook data fired in production (added missing elements, removed excess elements, aligned data types, corrected lowercase/uppercase values)
2. Used real data instead of some placeholders for the webhook simulator & docs (md5 & sha-1 values, region, bucket name, etc.)
3. Clarified the moment when the video_recorded webhook is sent
4. Clarified that the video_converted webhook is not sent if the mp4 output is disabled in the Transcoding Engine
5. Clarified all the possible values for the type parameter that's present in many webhooks
6. Removed cutToLength parameter from the video_converted webhook examples and parameters explanations (it does not exist in the actual webhook body)
7. The storedStatus parameter, part of video_copied_pipe_s3 webhook, is now covered in the docs
8. application/json is now the principal webhook type in the docs

Fix

We fixed a bug in the Pipe Account Dashboard's Transcoding page that resulted in an error (500 HTTP status code) when an account with a Standard subscription made any changes to the settings available on the Transcoding page.

There are currently 2 settings available on the Transcoding page available to accounts with Standard subscriptions:

1. enable "Cut to length" (it is disabled by default)
2. disable ".jpg snapshot output" (it is enabled by default).

This issue affected all Standard users.

Fix

We fixed a bug that caused the webhook signature to be generated incorrectly by Pipe in cases where the custom payload parameter value contained a + character.

New

Our FTP implementation has been updated with support for Explicit FTP over SSL/TLS. The recording files can now be securely pushed to your storage through FTPS.

Details in the blog post @ https://blog.addpipe.com/ftps/ .

Improvement

We have expanded our Amazon S3 Storage with three more regions:

1. Zurich (eu-central-2)
2. Jakarta (ap-southeast-3)
3. UAE (me-central-1)

Improvement

The object URLs for files pushed to your S3 storage will be available regardless of the canned ACL used in the upload process. These URLs are visible in the account dashboard's s3_logs page and are sent with the videocopieds3 webhook.

The blog post goes into detail.

https://blog.addpipe.com/s3-object-urls/

New

Improvement

We have aligned the FTP behavior between the FTP test and the actual FTP push attempts with various FTP folder values (empty string, /, or any other folder value).

Changes to Dashboard FTP test

• More descriptive log messages.
• We stopped trying to make active FTP connections.
• We now print the connection timeout and connection established times.
• The file which is uploaded during the test is now removed from your FTP server at the end of the test.
• The FTP test's timeout value is now aligned with the actual FTP push attempt's timeout (10 seconds instead of 20 seconds).

Changes to actual FTP push attempt

• We stopped trying to make active FTP connections.
• As a result, we have stopped pushing the addpipe-ftp-test.test file with every group of recording files. The file was pushed in an attempt to test if the passive connection mode succeeded.
• We added e new error code, FTP_PASV_FAILED.

New

You can now test your SFTP connection and credentials from the Pipe Account Dashboard.

Now you will be able to test if the connection goes through, if the credentials are correct, if the folder provided exists and if the user has write permission.

The test will also print the timeout value and the working folder and warns you if the user has shell access.

The test will upload a file named addpipe-sftp-test.test.

For the SFTP test to succeed, the port 22 needs to be opened for our account dashboard IP (116.203.232.162).