Supporting Safari 14.0.2 on macOS and an inline desktop recorder for Safari on iOS 14.3+ (just like the one we have for Chrome on Android) were some of our bigger efforts during this past month. Work continues on a few quirks. We hope to have a public beta available soon.
REST API v2
We're preparing for it's launch. We've worked on the documentation, stress testing and prepared for eventually closing down the existing REST API v1.
1080p video option
You can now choose the 1080p resolution option directly in the Pipe account area's embed section. Not all webcams support this resolution, so you might get videos of different resolutions even if you're asking for 1080p.
New S3 endpoints
- Europe (Paris)
- Europe (Milan)
- Europe (Stockholm)
- Asia Pacific (Hong Kong)
- Asia Pacific (Osaka)
- Africa (Cape Town)
- China (Beijing)
- China (Ningxia)
- Middle East (Bahrain)
Cleaned up the .xml video quality profiles
The Pipe HTML5 desktop recording client uses a .xml file to load the desired configuration for the video stream (things like resolution). These .xml files are inherited from the period when our main recording client was Flash-based. We've now cleaned them up and left only the resolution and fps.
You can now configure the desired fps for your video recordings
Until recently, the fps requested from your users' webcam through our HTML5 desktop recording client was hardcoded to 30. Through the above mentioned cleaned up .xml video quality profiles, you can now change the value to 15, 24 or any other integer. Some webcams even support 60fps.
Screen recording updates
Screen recording is again available as an option in the embed section of Pipe's account area. On top of that, when screen recording, the microphone permission is now requested 1st (to avoid unnecessary clicks when recording tabs). There's also a new Safari proof button to trigger the screen recording permission/choose screen prompt.
Correct size and bitrate for recordings over 2GB
A change that we made back in August. Sizes and bitrates for recordings larger than 2GB are now correct. The info is shown in the account area and available through the REST API.