Pipe changelog addpipe.com

We took advantage of the new retry push to storage mechanism to show a small notification in the account area whenever you have unsuccessful push to storage attempts since your last log in.

Here's how they look:

We've managed to implement a major improvement: the HTML5 recorder will now continue to record if the streaming connection is lost during recording. Once the connection is reestablished, the streaming resumes from where it left off.

More details in the blog post.

We've updated the docs, blog post and region settings in the Pipe account to make it more clear where the EU recording and processing servers are located (Amsterdam) and where we store the resulting files (Frankfurt) when using the EU region.

As part of our Summer Cleanup and of our new 2.0 Embed Code we've taken the time to rewrite and improve large parts of the documentation:

• When and where we store recordings
• CORS headers for recordings stored by us
• Video and audio quality (codecs, rate, channels, etc.)
• Troubleshooting possible Flash and HTML5 client connection problems
• Better JS API examples
• Better PHP webhook receiving script example
• How Pipe handles slow motion and 60 fps videos
• Limiting the length of videos on desktop and mobile
• SFSafariViewController and full-screen app support on iOS
• Customising recorder UI and colors on desktop/mobile
• Clarifications about webcam access over http in Chrome 47+ and 60+
• Added several new images and replaced several old ones
• Rearranged sections in light of the possibility of grouping them by category
• recorderId from the 1.0 embed code is now covered in detail

More details in the blog post.

Our new improved embed code for embedding the Pipe recorder clients in your website or web apps is now available in beta, details in the blog post.

Two times a year we reserve one week for fixing or improving stuff that piles up in our TODO bucket.

Here's what we did during the last week of August:

• accounts created using Google can now set passwords and sign in using their email and password (along with their Google sign in)
• we now log failed sign-in attempts and show them in the sessions page of your Pipe account; we've also added a link to quickly geolocate any IP used to sign in
• bug: fixed a minor issue with the Flash client showing text behind the sound icon when recording audio
• we've switched to using the CDN by default in all the newly generated embed codes
• bug: we've fixed the unclickable upload video icon in the desktop client
• bug: webhook data sent from the Pipe account area using the test webhook form or the retry failed webhook function was not properly urlencoded leading to ampersands in referrer URLs to cause all sorts of problems when receiving the webhook data
• deleting recordings through the REST API is now a lot faster
• the Recording Recovery mechanism which kicks in when a user loses connection without saving the video is now a lot more visible in the Pipe account area and in the documentation
• we've updated the Recording Recovery mechanism to not recover recordings that are empty (0kb), nonexistent or <= 325bytes
• bug: downloading videos through the account area from our US bucket now works as expected
• secret access key for S3 is now hidden in the UI just like a password
• added a direct link to the documentation from the Pipe account area
• S3 logs now include the bucket folder

From the Pipe account area you can now :

• view all S3/(S)FTP/Dropbox logs on an account/environment instead of just the last 100
• filter by recording id to view all the attempts to push a recording to storage
• filter by type (successful or not) to help you identify problems especially when you're processing thousands of recordings per day
• jump from the list of recordings to the S3/(S)FTP/Dropbox logs for a particular recording
• read about each error status code in the legend section at the bottom

The blog post has more information about why this change is great.

We've updated the Pipe account area to show the following information in the list of recordings:

• audio codec
• audio channels
• audio sample rate
• video codec

The information is shown for both the source (recording streamed or uploaded by the user) and for the final .mp4 recording (after being transcoded by Pipe).

This information will make it easier to identify what kind of recordings one receives from the users, the initial audio and video codecs, the number of audio channels and sample rate (directly influences quality) and whether or not transcoding audio/video is needed.

Over the last 2 weeks, we've done a few changes in light of GDPR coming into effect tomorrow the 25th of May.

Changes that help you with your compliance:

• Do Not Store Personal Metadata is a new option made to sit along the existing Do Not Store Files. When turned on we delete all personal metadata related to a recording as soon as we're done processing that recording.
• a new Data Processing Addendum to govern our relationship

Changes that touch on our GDPR compliance:

• Security: the account password is needed when canceling a subscription or deleting an account
• Security: we now collect the sign-up/sign-in IP and user agent. We store this information for up to 1 year after the trial account has expired or the account has been deleted.
• Updated copy around account deletion and subscription canceling to make it more clear what happens when you cancel your subscription or delete your account.
• Our Privacy Policy has been updated
• We've switched our sign up form to add emails to our e-mail list based on explicit consent. We used to rely on legitimate interest and soft opt-in.
• We've stopped collecting personal data from our reseller, Paddle, so we're not showing the email to which the invoices will be sent. The invoices are linked directly from your account area though.
• Changes in the way our website uses non-essential cookies