Pipe changelog addpipe.com

• I think it's safe to pull our 2nd gen HTML5 recorder out of beta after 1.3M videos recorded through it (the getUserMedia() logs is also a big reason)
• Our US region is also way overdue too after 1 year of being heavily used
• File uploads from desktop gets the green flag too

Pipe will now connect to FTP in passive connection mode and then fall back to active connection mode if passive is not supported.

Aaand liftoff, we have successfully launched the Transcoding Engine!

The Transcoding engine gives you control over the output of the Pipe platform.

Whether you need to change the aspect ratio and resolution of your videos, have the snapshot taken in different sizes, keep copies of the original recordings or generate a filmstrip to quickly scan the contents of a video, the Trancoding Engine has your back :)

You can use the S3 push feature to push recordings to your DigitalOcean Space so we've made small copy changes to the account area to align the wording.

Browser versions in the recordings list are now a bit more accurate. Ohh and we've added the OS version as well!

• screen recording now works in both Chrome 72+ and Firefox 66+.
• screen recording now works without an extension

Thus you can now enable screen recording from the options menu in the Embed section of your dashboard:

Once enabled, the Record Screen button will show and you can start capturing the screen right away.

Check out the blog post for detailed info.

We've just launched a new Logs section that gives you access to all the successful and failed attempts to access the camera and microphone with getUserMedia().

This section is a very useful tool to help you give better customer support, get accurate analytics and look up user attempts to grant access to their camera and microphone.

You can find out more details in the blog post.

2 updates to the Recordings section:

• you can search recordings by the device IP
• you can filter and show only Recovered recordings (recordings for which the connection was interrupted mid-recording and auto save was ON).

No longer will you need to sift through pages to find the elusive recordings :)

We've implemented a catch all mechanism for all of the situations that were producing 0 byte recordings coming from the HTML5 desktop recorder.

Previously, when a 0 byte file was made, the user that made the recording had no idea.

Now the user experience is much better. After clicking the record button if no incoming data is detected:

1. For the first 2 seconds the message Waiting for data... is shown and the recording counter does not start, because nothing is actual recording.
2. After 2 seconds if there is still no incoming data, the message Device error: no audio or video data is shown and the UI is reset, so that you can retry to record.
3. The failed recording is not saved.

The messages that we were showing when our HTML5 desktop recorder was requesting camera and microphone access needed an improvement.

• We've updated the messages to be in line with the text used by the browsers. Words like access and webcam were replaced by the keywords use and camera respectively.
• When requesting access, we've added the domain name of the website in which Pipe is embeded in, for a better understanding of the context.
• In case the user blocks the camera and/or microphone, an additional message is shown which informs the user how to unblock the devices.
• Now when you record audio only, the messages refer just to the microphone device, in order to avoid any kind of confusion.