GITNUXSOFTWARE ADVICE
Technology Digital MediaTop 8 Best Iptv Transcoder Software of 2026
Top 10 Iptv Transcoder Software ranked for technical buyers, with comparisons of tools like AWS Elemental MediaConvert and Azure Media Services.
How we ranked these tools
Core product claims cross-referenced against official documentation, changelogs, and independent technical reviews.
Analyzed video reviews and hundreds of written evaluations to capture real-world user experiences with each tool.
AI persona simulations modeled how different user types would experience each tool across common use cases and workflows.
Final rankings reviewed and approved by our editorial team with authority to override AI-generated scores based on domain expertise.
Score: Features 40% · Ease 30% · Value 30%
Gitnux may earn a commission through links on this page — this does not influence rankings. Editorial policy
Editor’s top 3 picks
Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.
Cloudflare Stream
Stream API driven stream creation with configurable transcoding outputs and managed playback endpoints.
Built for fits when teams need API-driven media ingestion and consistent derivatives for IPTV-style playout..
AWS Elemental MediaConvert
Editor pickMediaConvert job templates with CreateJob and GetJob APIs for repeatable output ladder configuration.
Built for fits when teams need API-driven, repeatable IPTV transcodes with governed IAM access..
Azure Media Services
Editor pickMedia Services job API supports parameterized transforms tied to assets and streaming endpoints.
Built for fits when IPTV transcoding needs API-driven automation with Azure identity and governance controls..
Related reading
Comparison Table
This comparison table evaluates IPTV transcoder software across integration depth, data model design, and the automation plus API surface used for provisioning and workflows. It also compares admin and governance controls such as RBAC, configuration management, and audit log coverage. Readers can map each platform’s schema choices to throughput and extensibility tradeoffs for their deployment model.
Cloudflare Stream
managed transcodingManaged media ingestion and transcoding with configurable delivery for live and on-demand video workloads.
Stream API driven stream creation with configurable transcoding outputs and managed playback endpoints.
Cloudflare Stream performs the core transcoding job by accepting uploads and producing playback-ready outputs that work with adaptive streaming. Integration depth is driven by Cloudflare account routing, edge delivery, and the ability to apply content controls tied to the same administrative surface. The data model is based on stream objects that store source assets, transcode states, and playback endpoints that downstream applications can reference. Automation is available through an API surface for provisioning and lifecycle actions around stream creation and playback configuration.
Automation and API surface are strongest when media pipelines need repeatable provisioning, such as generating consistent derivatives for multiple channels. A tradeoff is that the transcoding and packaging choices are mediated through Stream’s configuration model rather than exposing a fully custom codec pipeline. This matters when teams require strict control over encoder settings, GOP structure, or proprietary mezzanine handling beyond Stream’s supported options.
- +Transcoding and adaptive playback generation handled server-side
- +API enables stream provisioning and lifecycle automation
- +Edge integration reduces client transcoding and distribution complexity
- +Centralized account permissions support governance across content operations
- –Encoder control is limited to Stream’s supported configuration knobs
- –Custom packaging or codec workflows require fitting into Stream’s schema
Best for: Fits when teams need API-driven media ingestion and consistent derivatives for IPTV-style playout.
More related reading
AWS Elemental MediaConvert
cloud transcoderBatch and workflow media transcoding service with preset-based output formats and detailed encoding controls.
MediaConvert job templates with CreateJob and GetJob APIs for repeatable output ladder configuration.
Teams use MediaConvert to turn input streams into multiple delivery renditions by submitting job settings through the service API. The data model centers on job creation with inputs, outputs, output groups, and codec and container configuration, which keeps configuration reviewable in change control. Automation is driven through API calls that create, update, and poll jobs, with permissions enforced through IAM. Integration depth is strongest when MediaConvert is paired with S3-based staging, event-driven triggers, and AWS managed identity patterns for controlled access.
A key tradeoff is that MediaConvert configuration is job-driven, so complex, stateful per-channel logic usually requires orchestration outside the service. The best usage situation is an IPTV workflow where each channel has predictable inputs and repeatable output ladders, and where operators need job templates and API-driven provisioning for new channels. Another good fit is when delivery constraints require consistent segmenting and packaging across many endpoints, because output group settings can be reused with controlled changes.
- +Job templates enable consistent IPTV ladder generation across many channels
- +Job-centric API supports automation via create, poll, and notifications workflows
- +IAM permissions and RBAC patterns restrict who can submit and manage jobs
- +Multi-output settings support repeatable packaging and rendition formats
- –Stateful logic per channel requires orchestration outside MediaConvert
- –Large configuration changes can increase review burden across output groups
Best for: Fits when teams need API-driven, repeatable IPTV transcodes with governed IAM access.
Azure Media Services
media encodingMedia encoding and packaging capabilities for converting source assets into streaming-friendly formats with job-based workflows.
Media Services job API supports parameterized transforms tied to assets and streaming endpoints.
Azure Media Services exposes a management API for job submission, asset lifecycle, and streaming endpoint configuration, which makes it usable from automation scripts and CI systems. The core objects are jobs, assets, and streaming endpoints, with transforms that can be parameterized to match target codecs and packaging layouts used for IPTV delivery. Integration depth is strongest when platform teams already standardize on Azure resource provisioning patterns and identity controls.
A tradeoff is that the operational model is split across Media Services resources and the surrounding Azure services that host authentication, secrets, and telemetry routing. This adds integration work for IPTV pipelines that expect a single local transcoder with file-based inputs and minimal cloud control-plane dependencies. A common fit is server-side batch transcoding into consistent HLS or DASH outputs, followed by endpoint provisioning and automated job chaining.
- +Job and asset lifecycle exposed through a management API for repeatable provisioning
- +Transform configuration supports codec and packaging outputs used in IPTV workflows
- +Streaming endpoint configuration enables consistent delivery targets for downstream systems
- +Azure RBAC and audit logging integrate governance for media pipeline administrators
- –Control-plane resource split can increase integration overhead for simple workflows
- –Operational debugging spans job states and Azure telemetry sources
- –Near-real-time ingest to output requires careful orchestration of job scheduling
Best for: Fits when IPTV transcoding needs API-driven automation with Azure identity and governance controls.
Google Cloud Video Intelligence API
cloud video stackVideo processing capabilities combined with encoding pipelines in Google Cloud for analysis and delivery-oriented workflows.
Timestamped video annotations with structured OCR and shot boundary detection returned per analysis job.
Google Cloud Video Intelligence API integrates media analysis into Google Cloud workflows through a REST API and event-driven pipelines. The data model returns structured annotations such as labels, shot boundaries, OCR text, and speech transcripts tied to timestamps.
Automation typically involves provisioning requests via API clients, batching long-form operations, and writing results to downstream stores for IPTV transcoder governance. Admin and governance rely on Google Cloud IAM roles, audit logging, and project-scoped access controls for repeatable deployments.
- +REST API returns timestamped labels, OCR, and speech transcripts
- +Long-running analysis operations fit asynchronous IPTV workflows
- +Works with Cloud Storage inputs for repeatable provisioning pipelines
- +IAM RBAC and audit logs support operational governance needs
- –Media analysis output does not generate IPTV transcode artifacts
- –Throughput depends on request sizing and job concurrency limits
- –Schema complexity increases integration work for downstream mapping
Best for: Fits when teams need automated visual, OCR, and audio metadata extraction alongside IPTV processing pipelines.
Vdocipher Platform
streaming preparationPlatform that supports adaptive streaming preparation with transcoding workflow support for video delivery pipelines.
Provisioning API plus job configuration schema that drives end-to-end IPTV transcode and packaging runs.
Vdocipher Platform performs IPTV and OTT transcoding orchestration by handling codec, packaging, and delivery workflows across endpoints. The integration depth centers on an API and automation hooks that feed channel and asset metadata into a defined processing pipeline.
Its data model tracks provisioning inputs such as source references, output renditions, and delivery constraints, which supports repeatable runs. Governance is handled through admin controls tied to access management, auditability, and permissioned operations.
- +API-driven provisioning of transcode jobs with repeatable configuration inputs
- +Data model captures source, renditions, and packaging targets for predictable outputs
- +Automation surface supports batch orchestration across multiple channels
- +Admin controls map operational access to transcoding and management actions
- –Complex job schemas can raise setup time for first pipeline definitions
- –High-throughput scenarios require careful configuration of endpoints and concurrency
- –Debugging failures can be slow when job steps produce sparse diagnostics
- –Governance needs disciplined provisioning to prevent misrouted outputs
Best for: Fits when teams need API automation and governance controls for IPTV transcoding workflows.
Zencoder
transcoding APITranscoding-as-a-service offering batch encoding workflows for converting source media into streaming-ready outputs.
Job-based API with preset parameters for repeatable IPTV encoding runs.
Zencoder is a media transcoding service with a job-centric API surface that supports repeatable workflow automation for IPTV encodes. Its data model centers on transcoding jobs, preset inputs, and output targets, which enables deterministic provisioning across channels.
Integration depth shows up through REST-driven submission and status polling, plus parameterized job configuration that maps to throughput-oriented batch processing. Governance is handled through account-level access and job ownership boundaries, but it offers limited RBAC granularity and audit export compared with enterprise media control planes.
- +REST job submission supports scripted IPTV transcode pipelines
- +Preset-based configuration reduces per-job encoding drift
- +Deterministic job status and outputs simplify downstream automation
- +Batch-friendly job model suits channel and asset fan-out
- –RBAC and role separation are limited for multi-team operations
- –Audit log export and admin governance controls are minimal
- –Extensibility is mostly configuration driven, not workflow orchestration
- –Throughput tuning requires external scheduling rather than in-product controls
Best for: Fits when teams automate IPTV transcodes via API with preset-driven, job-level control.
Kaltura Capture and Kaltura Video Platform
video platformVideo platform services that include transcoding and publishing workflows for converting inputs into multiple renditions.
API-driven entry provisioning with processing workflow configuration in Kaltura Video Platform.
Kaltura Capture and Kaltura Video Platform combine client-side capture with a shared content backend that supports automated workflows for streaming and ingest. The data model ties media assets, entry processing, and metadata to Kaltura Video Platform services, which helps integration depth for IPTV transcoding pipelines.
API-driven provisioning and extensibility support automation of ingestion, workflow configuration, and RBAC-aligned governance. Audit and administrative controls in the platform support operational oversight across capture, processing, and delivery stages.
- +Single backend ties capture outputs to entries and processing states
- +API supports provisioning, metadata updates, and workflow configuration
- +RBAC and roles support governance across ingest and admin operations
- +Extensibility supports custom automation through documented service endpoints
- –Capture client and platform backend require coordinated integration work
- –Complex workflow configuration can increase operational overhead
- –Transcoding behavior depends on how processing profiles map inputs
- –High-scale throughput requires careful orchestration of ingest and processing
Best for: Fits when media teams need API automation across capture, ingest, and transcoding for IPTV workflows.
Encoding.com
encoding APICloud encoding service that converts input media into streaming outputs using API-driven transcoding jobs.
REST API job orchestration with configurable transcoding settings and output artifacts per job.
Encoding.com focuses on API-first IPTV transcoding workflows, with programmable presets, jobs, and outputs wired into an automation-friendly data model. It supports integration patterns that map cleanly to provisioning, including job submission, status tracking, and retrieval of results artifacts.
Admin governance is handled through account-level configuration and access controls that affect who can create jobs and manage credentials. Throughput control is driven by batch job design, deterministic transcoding settings, and queue-oriented execution rather than manual UI operations.
- +API-driven job submission and status polling for automation at scale
- +Preset-driven configuration keeps transcoding outputs consistent across pipelines
- +Clear job and artifact lifecycle supports idempotent workflow design
- –RBAC granularity is not visibly exposed in public operational documentation
- –Schema flexibility for custom metadata can require extra wrapper services
- –Debugging failed transcoding jobs can require correlating multiple identifiers
Best for: Fits when IPTV delivery teams need deterministic transcoding automation with an API-centric integration model.
How to Choose the Right Iptv Transcoder Software
This buyer’s guide covers IPTV transcoder software with an emphasis on integration depth, automation and API surface, and admin plus governance controls. The tools covered include Cloudflare Stream, AWS Elemental MediaConvert, Azure Media Services, Google Cloud Video Intelligence API, Vdocipher Platform, Zencoder, Kaltura Capture and Kaltura Video Platform, and Encoding.com.
Each section maps evaluation criteria to concrete mechanisms from these tools, including job templates, parameterized transforms, REST job orchestration, and timestamped annotations that can feed IPTV processing pipelines. The guide also lists common implementation pitfalls such as limited encoder controls, high orchestration burden outside the transcoder service, and RBAC granularity gaps.
IPTV transcode orchestration software that turns inputs into governed renditions
IPTV transcoder software converts incoming video into streaming-ready derivatives with repeatable output schemas for IPTV-style playout. It solves pipeline problems like generating transcode ladders across many channels, enforcing consistent packaging outputs, and coordinating job lifecycles through APIs.
In practice, tools like AWS Elemental MediaConvert drive repeatable job definitions with CreateJob and GetJob patterns, while Cloudflare Stream provides Stream API driven stream creation with configurable transcoding outputs and managed playback endpoints. Other tools like Azure Media Services expose job, asset, and streaming endpoint lifecycles through an automation-friendly management API.
Evaluation criteria for API-first IPTV transcoding and governed delivery
The right IPTV transcoder tool matches the organization’s automation pattern, either by letting workflows submit and monitor jobs through APIs or by tying transcoding outputs to a higher-level media data model. Integration depth matters because downstream systems need stable identifiers, predictable output schemas, and lifecycle states they can poll or receive notifications for.
Admin and governance controls matter because channel pipelines often span multiple teams and operators. The most practical evaluation checks focus on RBAC and IAM governance, auditability, and how much of the workflow is expressed in a tool-owned schema versus bolted on externally.
API-driven job orchestration and status lifecycle
Cloudflare Stream supports API-driven stream creation with managed playback endpoints, which reduces custom endpoint wiring. AWS Elemental MediaConvert exposes job-centric APIs such as CreateJob and GetJob to make recurring transcode automation and monitoring straightforward.
Parameterized transforms and output ladder consistency
Azure Media Services ties parameterized transforms to assets and streaming endpoints, which helps keep output schemas deterministic across runs. AWS Elemental MediaConvert reinforces this with job templates and multi-output settings designed for consistent rendition and packaging formats.
Managed data model for assets, renditions, and delivery targets
Vdocipher Platform uses a job configuration schema that captures source references, output renditions, and delivery constraints for repeatable end-to-end IPTV transcode and packaging runs. Kaltura Video Platform ties entry processing state and metadata to backend processing steps, which aligns transcode outputs to a single content model for IPTV workflows.
Throughput-friendly batch and fan-out execution patterns
Zencoder provides a batch-friendly job model with preset-based configuration that supports channel and asset fan-out with deterministic outputs. Encoding.com uses REST API job orchestration with an artifact lifecycle designed for queue-oriented batch execution.
Governance via IAM and role separation controls
AWS Elemental MediaConvert pairs its job APIs with IAM governance patterns that restrict who can submit and manage jobs, including RBAC-aligned permissions boundaries. Azure Media Services integrates Azure RBAC and audit logging for media pipeline administrators across job and asset operations.
Auxiliary media intelligence to drive downstream processing rules
Google Cloud Video Intelligence API returns timestamped labels, OCR, speech transcripts, and shot boundary detection per analysis job. This makes it useful when IPTV processing needs metadata extracted through REST APIs and then mapped into transcoding or packaging governance logic outside the transcoder itself.
Decision framework for selecting IPTV transcoder software by integration and control needs
Start with the orchestration shape that fits existing systems and team roles. Services like AWS Elemental MediaConvert and Encoding.com emphasize job-centric REST automation that supports recurring schedules and scripted transcode pipelines, while Cloudflare Stream focuses on API-driven stream creation tied to managed playback.
Then confirm how much control and governance the tool provides inside its own schema. Azure Media Services and Vdocipher Platform express more of the pipeline as job and transform configurations tied to managed entities, while Zencoder and Encoding.com place more workflow assembly responsibility on external scheduling around their job models.
Map the required automation surface to the tool’s job or stream APIs
Choose Cloudflare Stream when workflow automation needs API-driven stream creation with configurable transcoding outputs and managed playback endpoints. Choose AWS Elemental MediaConvert or Encoding.com when automation needs job submission plus status polling with deterministic job and artifact lifecycle objects.
Check whether output ladders and packaging rules are template-driven or job-by-job
Use AWS Elemental MediaConvert when repeated IPTV ladder generation must be consistent across many channels via job templates and multi-output settings. Use Azure Media Services when parameterized transforms must attach to specific assets and streaming endpoints for deterministic output schemas.
Validate how the tool represents sources, renditions, and delivery targets
Select Vdocipher Platform when a provisioning API plus job configuration schema must capture source references, output renditions, and delivery constraints in one place. Select Kaltura Capture and Kaltura Video Platform when the pipeline needs capture outputs tied to entry processing states and shared content metadata under a single backend.
Confirm governance controls align to operational roles and audit needs
Use AWS Elemental MediaConvert when IAM and RBAC patterns must restrict job submission and management per operator role. Use Azure Media Services when Azure identity and audit logging need to cover asset and job lifecycles for media pipeline administrators.
Identify where transcoding ends and orchestration must begin
Plan for orchestration outside the transcoder service when custom encoder workflows exceed supported configuration knobs in Cloudflare Stream. Plan external workflow logic when channel-specific state and review burden must be managed outside MediaConvert job templates, since changes across output groups can increase operational review work.
Add metadata extraction only if it is required by IPTV governance rules
Use Google Cloud Video Intelligence API when timestamped OCR, shot boundaries, and speech transcripts must feed downstream IPTV processing rules. Skip it when transcoding outputs are the sole requirement, because Video Intelligence API produces structured annotations rather than IPTV transcode artifacts.
Teams that should match IPTV transcoding software to their automation and governance model
Different IPTV environments need different integration depth and control depth. The best-fit tool depends on whether transcoding orchestration is managed as a job API, a stream API with managed playback, or a content backend model that ties capture and processing together.
Governance needs also shape selection because IAM, RBAC, and audit logging dictate who can submit jobs and manage outputs across multi-team pipelines.
Media operations teams building API-driven IPTV transcode ladders at scale
AWS Elemental MediaConvert fits because job templates and job-centric APIs like CreateJob and GetJob support repeatable ladder generation with IAM governance for who can manage jobs. Encoding.com also fits when deterministic transcoding automation depends on REST job orchestration and artifact retrieval for queue-oriented batch execution.
Platform teams that want managed delivery endpoints tied to transcoding configuration
Cloudflare Stream fits when teams need Stream API driven stream creation plus managed playback endpoints that reduce custom delivery wiring. Its centralized account permissions support governance across content operations, which helps when playout teams want consistent derivatives for IPTV-style delivery.
Enterprises standardizing on Azure identities and audit logging for media pipeline administration
Azure Media Services fits because it supports job and asset lifecycles through a management API with Azure RBAC and audit logging integrated for operational governance. It also supports parameterized transforms tied to assets and streaming endpoints for deterministic output schemas.
Media workflow teams that need a unified content and processing data model across capture, ingest, and transcoding
Kaltura Capture and Kaltura Video Platform fit because the data model ties capture outputs to entries and processing workflow configuration within one backend. This reduces cross-system mapping when IPTV workflows depend on metadata updates and processing states.
Studios and broadcasters needing automated visual and text metadata alongside IPTV processing
Google Cloud Video Intelligence API fits when pipelines require timestamped labels, OCR, shot boundaries, and speech transcripts that can feed downstream IPTV governance rules. It complements IPTV transcoding tools because it provides metadata outputs rather than transcode artifacts.
Common implementation pitfalls in IPTV transcoding tool selection and integration
Many IPTV transcoding failures come from mismatches between workflow requirements and what the tool can express in its schema. Other problems come from underestimating how much orchestration must exist outside the transcoder platform even when the transcoder offers job templates.
Governance and control mistakes also appear when role separation requirements are more granular than the platform exposes. Debugging and debugging-time correlation failures also happen when tool artifacts and identifiers are not mapped cleanly into downstream systems.
Assuming encoder flexibility matches custom codec and packaging workflows
Cloudflare Stream limits encoder control to supported configuration knobs, which can break custom packaging or codec workflows unless the pipeline can fit Stream’s schema. AWS Elemental MediaConvert and Azure Media Services usually handle structured output ladder configuration more directly via job templates and parameterized transforms.
Underestimating external orchestration needs for per-channel state and review
MediaConvert can require orchestration outside the service for stateful per-channel logic, and large configuration changes across output groups can raise review burden. Vdocipher Platform also needs careful configuration of endpoints and concurrency for high-throughput scenarios, so orchestration responsibilities still matter.
Picking a tool without enough RBAC granularity for multi-team operations
Zencoder and Encoding.com have limited visibility into RBAC granularity in public operational documentation, which can force wrappers to enforce role boundaries. AWS Elemental MediaConvert and Azure Media Services integrate IAM and Azure RBAC plus audit logging patterns that better match governed media pipeline administration.
Treating metadata extraction as a substitute for transcoding artifacts
Google Cloud Video Intelligence API returns structured annotations like OCR and shot boundaries but it does not generate IPTV transcode artifacts. It must be paired with a transcoder like AWS Elemental MediaConvert or Azure Media Services to deliver actual renditions.
Building workflows without a stable artifact and identifier lifecycle
When job debugging needs correlation across multiple identifiers, Encoding.com failures may require correlating multiple identifiers to diagnose. Zencoder and MediaConvert work best when job status polling and deterministic outputs are wired into downstream identifiers so artifacts can be mapped to the right channel and schedule.
How We Selected and Ranked These Tools
We evaluated Cloudflare Stream, AWS Elemental MediaConvert, Azure Media Services, Google Cloud Video Intelligence API, Vdocipher Platform, Zencoder, Kaltura Capture and Kaltura Video Platform, and Encoding.com by scoring feature fit, ease of use, and value using criteria tied to the tools’ described APIs, job or stream models, and governance controls. The overall rating uses a weighted average where features carry the most weight at 40% and ease of use and value each account for 30%. This editorial research relies on the provided review information about integrations, data models, automation surfaces, and admin controls rather than on hands-on lab testing or private benchmark experiments.
Cloudflare Stream set itself apart through Stream API driven stream creation with configurable transcoding outputs and managed playback endpoints, which directly improved the features score by connecting transcoding configuration to a managed delivery artifact. That same Stream-centered API surface also supported higher ease-of-use scoring because automated provisioning could map more directly to downstream playback without extra integration glue.
Frequently Asked Questions About Iptv Transcoder Software
Which IPTV transcoder tools expose a job API that supports fully automated pipelines?
How do Cloudflare Stream, AWS Elemental MediaConvert, and Azure Media Services differ in how outputs are configured for IPTV playback?
Which platform is better for teams that need deterministic provisioning driven by templates or a defined data model?
What integration pattern works best when an IPTV workflow needs media analysis metadata like OCR or scene boundaries?
Which tools support extensibility when transcoding logic must be altered per channel without rebuilding the whole pipeline?
How do governance and access control models typically differ across Cloudflare Stream, Zencoder, and AWS Elemental MediaConvert?
Which toolchain fits best when the transcoding workflow must be driven by channel and asset metadata already stored in an internal system?
What common failure mode affects automated IPTV transcoding, and how do specific tools expose diagnostics?
Which platforms are better aligned to high-throughput batch processing with deterministic settings rather than manual encoding steps?
Conclusion
After evaluating 8 technology digital media, Cloudflare Stream stands out as our overall top pick — it scored highest across our combined criteria of features, ease of use, and value, which is why it sits at #1 in the rankings above.
Use the comparison table and detailed reviews above to validate the fit against your own requirements before committing to a tool.
Tools reviewed
Primary sources checked during evaluation.
aws.amazon.comReferenced in the comparison table and product reviews above.
Keep exploring
Comparing two specific tools?
Software Alternatives
See head-to-head software comparisons with feature breakdowns, pricing, and our recommendation for each use case.
Explore software alternatives→In this category
Technology Digital Media alternatives
See side-by-side comparisons of technology digital media tools and pick the right one for your stack.
Compare technology digital media tools→FOR SOFTWARE VENDORS
Not on this list? Let’s fix that.
Our best-of pages are how many teams discover and compare tools in this space. If you think your product belongs in this lineup, we’d like to hear from you—we’ll walk you through fit and what an editorial entry looks like.
Apply for a ListingWHAT THIS INCLUDES
Where buyers compare
Readers come to these pages to shortlist software—your product shows up in that moment, not in a random sidebar.
Editorial write-up
We describe your product in our own words and check the facts before anything goes live.
On-page brand presence
You appear in the roundup the same way as other tools we cover: name, positioning, and a clear next step for readers who want to learn more.
Kept up to date
We refresh lists on a regular rhythm so the category page stays useful as products and pricing change.