PxS v2.6

New Features

  • Browse and Upload feature.
  • PixelStrings managed storage.
  • ProRes clap option.
  • Retiming start/end timecodes and black detection threshold.

General Updates

  • Updated PixelStrings subscriptions.
  • Improved assets page UI.
  • Updated Cinnafilm image processing libraries.
  • Various bug fixes and enhancements.

Known Issues

  • Cannot process input files with non-SMPTE standard resolutions.
  • If using the retime in/out timecode function with a ProRes output target, output file length may be incorrect.

PxS v2.5

New Features

  • ExtremeMotion Motion Compensation Settings.
  • BasicSpacial Noise Reduction.
  • SmoothSpacial Noise Reduction.
  • Source resolution crop.
  • Validate Job feature.
  • Netflix compliant workflows.
  • IMF 101 White Paper resource.
  • PixelStrings Subscription plans.

General Updates

  • Significant speed increase to some processes.
  • HDR Tab with overview of the upcoming feature.

PxS v2.4.3.3

General Updates

  • Updated timecode handling for test clips.
  • Fixed bug with some longer running transcodes.

PxS v2.4.3.2

New Features

  • ProRes custom channel mapping.
  • Audio Retime Audio Layout configuration

General Updates

  • Re-enabling of Audio Retiming.

PxS v2.4.3.1

Known Issues

  • Audio Retime processing is unavailable.
    Issue: Certain channel mappings cause audible errors during Retiming jobs.
    Status: Retiming jobs for Video ONLY can still be submitted for processing by setting 'Enable Audio Retime' to OFF. Please note that only ProRes, DNxHD and H.264 codecs support 'Enable Audio Retime' in the OFF position. MXF wrapper codecs (XDCam HD and XAVC 4K) do not support this configuration.

PxS v2.4.3

New Features

  • Transcode-only Mode. An option for cost-senstive users who want to use PixelStrings to transcode assets to a different codec or container without enabling image processing (Tachyon and Dark Energy) or retiming (Wormhole) features.
  • Configuration Wizard for Tachyon conversion settings. Select input framerate or specific input asset, output field order, and optionally an input field order override, and the wizard determines the correct Tachyon conversion settings and automatically saves the settings to your workflow.

General Updates

  • Improved error messaging for problematic input files
  • Modified Workflow API structure (see API documentation for more info)
  • IMF support in Azure will be added upon customer request. IMF output format in AWS has been supported and will continue to be available.

Known Issues

  • For input assets in Azure Blob storage, PixelStrings will not list an asset whose filename contains whitespace characters. We recommend replacing whitespace with underscores.

Upcoming Changes

  • In the UI walk-thru, add detailed descriptions for Create a Workflow, Broadcast Compliance, and Re-Timing.
  • For IMF outputs, fix mismatched audio and image track durations in both input and output clips. An output mismatch can occur due to a mismatch inherent in the input clip itself, and can also be introduced by a framerate conversion due to frame duration quantization (mismatches due to frame rate conversions is a general issue, not specific to PixelStrings).
  • Retiming (Wormhole) is currently available only in cloud regions based in Oregon; update cloud resources in other regions to support retiming.

PxS v2.4.2

New Features

  • Certified Apple ProRes output format added
  • Receipts get emailed from Stripe after you purchase PixelStrings processing credits
  • Tooltips ('flyouts') for Retime and Legalizer tabs

General Updates

  • Fixed Convert/Fix bug that was incorrectly interpreting source field order that resulted in incorrect de-interlacing.
  • Fixed bug that would not allow some input assets to be displayed.
  • Made user email non-case sensitive for login.

Known Issues

  • For input assets in Azure blob storage, PixelStrings will not list an asset if its filename contains whitespace. We recommend that you replace whitespace with underscores.

Upcoming Changes

  • In the UI walk-thru, add detailed descriptions for Create a Workflow, Broadcast Compliance, and Re-Timing.
  • For IMF outputs, correct mismatched audio and image track durations in both input and output clips. An output mismatch can occur due to a mismatch inherent in the input clip itself, and can also be introduced by a framerate conversion due to frame duration quantization (mismatches due to frame rate conversions is a general issue, not specific to PixelStrings).
  • IMF support is being added for Azure users

PxS v2.4.1

New Features

  • Password reset. Click “Reset password”, check your email for a reset token, enter the token and new password. If you haven't yet verified your email, you'll need to first verify your email, then you can reset your password.
  • “Release Notes” modal in the Support page.
  • In the “Ledger” page: New “Refresh” button for manual ledger table updates, Mouse-over ledger entry details, Styling & animations.

General Updates

  • You can now submit a job before PixelStrings has extracted the input clip’s metadata, which includes the clip’s total run time. We use a default run time value to estimate your job’s cost; your final cost will be adjusted once the actual run time is known.
  • Tweaked colors in “Dark UI” theme.
  • More descriptive transcode error messages.
  • Updated on-line API spec (accessible to our API partners).
  • Fixed test clip accounting and submission logic.
  • Previously, H.264 output used level 4.0 for all output frames rates, forcing the output resolution to 1366x768 for frame rates 50 fps and up. Now we use a default level of 4.1, but we set the level to 4.2 when the output frame rate is 50 fps or higher.
  • Fixed calculation for Test Mode job costs.

Known Issues

  • In “Retiming” subtab, value for “Target Duration” doesn’t get saved with Workflow (but other options do get saved).
  • For input assets in Azure blob storage, PixelStrings will not list an asset if its filename contains whitespace. We recommend that you replace whitespace with underscores.

Upcoming Changes

  • Generate Stripe receipt for credit purchases.
  • In the UI walk-thru, add detailed descriptions for Create a Workflow, Broadcast Compliance, and Re-Timing.
  • For IMF outputs, correct mismatched audio and image track durations in both input and output clips. An output mismatch can occur due to a mismatch inherent in the input clip itself, and can also be introduced by a framerate conversion due to frame duration quantization (mismatches due to frame rate conversions is a general issue, not specific to PixelStrings).
  • IMF support is being added for Azure users.

PxS v2.4

New Features

  • Added Azure compatibility
  • https://app.pixelstrings.com is now a landing page where you choose between AWS and Azure. Clicking “AWS” takes you to https://aws.pixelstrings.com; clicking “Azure” takes you to https://azure.pixelstrings.com.
  • Added Cinnafilm Wormhole™ for global retiming (single clip). Retimes video, captions, and audio, where audio pitch is preserved.
  • New output codec: H.264 (CBR and VBR)
  • For API partners only: new API based on JSON-RPC and HTTPAPI endpoints for AWS and Azure usersOnline API documentationSample API client app (Python source code) available
  • Email verification for password changes

General Updates

  • Improved interactive UI walk-through tutorial
  • Better verification of cloud storage settings when you click “Save” in the Settings page
  • IMF JPEG 2000 profile level change to comply with SMPTE IMF specification and satisfy Netflix requirements. Note: J2K is output as a part of an IMP (IMF Master Package)
  • Various bug fixes and enhancements

Known Issues

  • After you buy credits, your balance is immediately updated in the backend database, but you need to reload the webpage to see your new balance displayed.
  • For input assets in Azure blob storage, PixelStrings will not list an asset if its filename contains whitespace. We recommend that you replace whitespace with underscores.

Upcoming Changes

  • PxS will correct mismatched audio and image track durations in the output clip. An output mismatch can occur due to a mismatch inherent in the input asset itself, and can also be introduced by a framerate conversion due to frame duration quantization ( mismatches due to frame rate conversions is a general issue, not specific to PixelStrings).
  • IMF support is being added for Azure users