Changelog

Every update to the Pipe platform: new features, improvements and fixes.

Safari Background Blur Fixed

Fix

We fixed a Safari-specific issue where enabling the real-time background blurring effect would result in a “double-image” effect instead of a properly blurred background.

Build slug: 31b7f3c81

Video Preview Reset Fixed During Playback

Fix

We fixed a bug where starting a new recording while a video was playing back would leave the preview video in the bottom-right minified position. The video preview now correctly returns to its original, full-size position when a new recording is started during playback.

Build slug: 3a472ceac

Safari UI Fixes in the Recording Client

Fix

We fixed several Safari-specific UI issues in the recording client. Icons in the bottom menu are no longer cut off, and hover interactions have been fixed to prevent icons from twitching or shifting unexpectedly.

Build slug: b8ae38714

Variable Bitrate in Safari Finally Fixed

Fix

We fixed an issue in Safari on iOS and macOS where video recordings used a hardcoded bitrate of 5Mbps regardless of resolution. This limited video quality when recording at high resolutions. The recording client now applies resolution-appropriate bitrates, ranging from 0.3 Mbps for 240p up to 14 Mbps for 4K recordings. We’ve also updated the documentation to include these bitrates.

Build slug: 4df062d59

Playback Progress on Safari and Save Button Markup Update

Fix
  1. The playback seek bar now accurately reflects the recording’s current playback position on Safari as well.
  2. The save button in the recording client has been updated from an HTML <button> element to a <div> element. This change aligns it with the rest of the recording client buttons, which are all implemented as <div> elements .

Build slug: 7c845b616

Playback Progress and Audio Visualizer Fixes

Fix
  1. The playback seek bar now accurately reflects the recording’s current playback position on Chrome and Firefox. Previously, the progress indicator could reach the end while the playback continued briefly.
  2. When the recording client falls back from video to audio-only mode and then returns to video mode after a camera is reconnected, the audio visualizer waves are now correctly removed from the center of the recording client, preventing them from overlapping the video.

Build slug: 70097637a

Fixed Multiple Recording Starts via JS Control API

Fix

We fixed an issue where triggering the recording start action multiple times simultaneously via the JavaScript Control API would result in the recording data being written multiple times to the same file. The recording client now ensures that a recording starts only once.

Build slug: c5bbaa28b

Playback Stability and Screen Recording Improvements

Improvement Fix

We improved playback stability by adding checks that prevent overlapping play and pause calls, avoiding the DOMException: The play() request was interrupted error.

We fixed an issue where screen recording did not work correctly when the audio-only (pipe-ao) embed code option was enabled.

Build slug: e835f9d2e

Android Bluetooth Disconnection Fix, Log Level Option, and pipe.css Versioning

Fix New
  1. We implemented a mechanism on Android devices to verify whether the selected Bluetooth audio input device is disconnected at recording start, ensuring the recording is initiated correctly.
  2. We removed versioning from pipe.css network requests made by the recording client.

We introduced a new embed option, loglevel, that hides all console logs when set to 1.

Build slug: 41271e501

Performance Improvements When Switching Devices

Fix
  1. We improved the recording client’s overall performance after switching audio and video devices multiple times. This sometime lead to a frozen image on Android devices.
  2. We’ve fixed a minor bug where some error messages, that spanned 2 lines, shown by the recording client were shown collapsed.

Build slug: 875895486

More Accurate Microphone Input Detection

Improvement

The microphone input checks that can trigger the “Your microphone might be muted by your system settings.” warning now use a finer measurement value. This results in more accurate detection of low-level audio input.

Build slug: 23cb53c39

EncodingError Fix, New Audio Warning Option, and Improved Video Quality from Safari

Fix New Improvement

The recording client now correctly handles a new EncodingError message (“The given encoder configuration is not supported by the encoder.”), restoring the fallback behavior on older Android devices. Previously, the monitored message was “Video encoding failed”.

Added a new embed code option called disableaudiowarningmsg to hide the warning message displayed at the bottom of the recording client when no audio is detected.

Video quality on Safari: Switched to a variable video bitrate for MP4 video recordings (Safari on iOS and macOS) for better video quality. The requested bitrate now ranges from 0.3Mbps for 320x240 to 14Mbps for 4k recordings (instead of defaulting to 2.5Mbps).

^le: A separate 5Mbps limit remained in place until we removed it in this build.

Microphone Input Warning: Switched to checks every 1 second (instead of 2) when we detect a microphone with no input. We mark an input device as having sound right away (without waiting for 15 seconds as in the initial implementation).

Build slug: fd21de285

Versioning Support Added to the 2.0 Recording Client

New

The 2.0 recording client now fully supports versioned builds, allowing you to lock your integration to a specific version.

For full details on how versioning works, selecting a version, and best practices, please refer to our documentation.

Below are the currently available builds, along with their build slugs and release dates:

Local Playback After Recording

Improvement

Our main audio, video and screen recording client now plays back recordings directly from a local in-memory blob, eliminating the need to fetch files from the ingestion server over HTTPS. This is how the existing download function works. This improvement enables instant playback and seeking. The improvement will be visible especially to users on slow or unstable connections like mobile connections.

Build slug: 9249ecb2d

Improved Handling of EncodingError During Screen Recording

Fix Improvement

When recording screens with very high resolutions (above 4K), some browsers could trigger an EncodingError, preventing the recording from starting.

The recording client now includes a fallback mechanism: if an EncodingError occurs during screen recording initialization, it will automatically retry using the VP8 codec and attempt to restart the recording instantly.

Build slug: 2706f69e8

Improvements to the account dashboard

Improvement Fix

We’ve made the following improvements to the account dashboard:

  • The storage logs pages now show the upload bitrate value for successful uploads (the bitrate covers the main recording output file);
  • The recordings page now calculates the bitrate value correctly (decimal value was not taken into consideration);
  • The bitrate value is displayed in a more human-readable format;
  • The rotation value is now correctly shown just for recordings that have it;
  • The daily recordings limit section is now also shown in the account page;
  • The recording client is now shown centrally on mobile devices on the public pages generated from the dashboard;
  • The correct unit of measure for size (MiB instead of MB) is now shown in the subscription page;
  • The subscription page has new information about the maximum number of concurrent recordings processed during load per region.

Concurrency Limit for Processing Recordings During High Load

New

We’ve implemented a new concurrency limit mechanism that activates ONLY when a processing server hits a certain threshold considered a high load.

It works in the following way

The concurrency limit means only a specified number of recordings may be processed at a time per account by our processing servers. Each account has a concurrency limit value based on the account type:

  • Trial accounts: 1 maximum number of concurrent recordings processed during load
  • Standard/Creator accounts: 2 maximum number of concurrent recordings processed during load
  • PRO accounts: 4 maximum number of concurrent recordings processed during load

The above limits will be enforced when more than half of the available processing workers on the server are in use at any given moment. Otherwise, the per-account limits are ignored, and accounts can ‘burst’ and use more workers than their limit allows for recording processing.

Things to note

  • The concurrency limits are individually enforced for each recording region. This means, for example, that you may go over the limit on the US1 region but still be under the limit on US2.
  • Any recording that will be denied being processed because of going over the limit will be retried by our retry mechanism.

Better Rotation Information

Improvement

The recordings list in the Pipe account dashboard now displays rotation information for all recordings, including those made from mobile devices through streaming - they carry rotation information too - and those made natively on mobile devices but uploaded from a desktop device.

Full Keyboard Accessibility for the Recording Client

Improvement

Our recording client is now fully accessible via keyboard navigation. All interactive elements can be reached and operated using standard keyboard controls, improving accessibility for end users.

Screen Recording Fixes and Improvements

Fix Improvement Other

Fixed an issue on Safari where starting a screen recording could fail with the error message InvalidStateError occurred.

Added support for screen recording without microphone or microphone access.

When screen sharing, you’ll now choose the screen sharing surface 1st and then you’ll be asked for microphone access.

Change Screen Share Source

New

Two important updates to our recording client when used for screen sharing & recording:

  • You can now change the screen sharing surface after initializing the recording client. You can now select a new screen, window, or browser tab to record by using the icon in the bottom menu.
  • The recording client now automatically detects when end users end a screen sharing session by closing the shared window/tab or by using the system/browser Stop Sharing button (browser support might vary).

For more information, please refer to this blog post.