# Version 2.28.0 and 3.28.0
<a name="rn-2-28-0"></a>

This release includes AWS Elemental Live and AWS Elemental Statmux version 2.28.0, and AWS Elemental Conductor Live version 3.28.0.

## New features in version 2.28.0
<a name="rn-2-28-0-new-features"></a>

This release includes the following new features:

Security updates  
This release includes updates that address potential security issues.

## Resolved issues in Elemental Live 2.28.0
<a name="rn-2-28-0-resolved-live"></a>

The following table lists the issues that are resolved in Elemental Live 2.28.0.


| Key | Topic | Description | 
| --- | --- | --- | 
| P412200249 | Audio | Previously, the ARIB audio mode did not function correctly. This issue has been fixed. | 
| V2135638170 | Captions | Previously, captions upconverted from CEA-608 to CEA-708 could be truncated. This issue has been fixed. | 
| EML-7888 | Captions, DVB subtitle | Previously, DVB subtitles could produce timestamp (PCR/PTS) violations that affected downstream compliance. This issue has been fixed. | 
| TDP-137 | Captions, TTML | Previously, TTML and EBU-TT-D caption documents could be produced without the required XML namespace, causing some players to fail to display captions. This issue has been fixed. | 
| CAPYBARA-526 | Event processing | Previously, long-running events could experience timing calculation errors that disrupted output. This issue has been fixed. | 
| EML-7746 | Event processing | Previously, very short inputs could trigger a race condition that disrupted event processing. This issue has been fixed. | 
| P372006366 | Event processing | Previously, a rounding error could cause inaccurate event duration calculations. This issue has been fixed. | 
| V2141850574 | Event processing | Previously, audio timing and frame capture could be inaccurate on certain events. This issue has been fixed. | 
| V2176365863 | Event processing | Previously, an orphaned persistent input could continue processing unnecessarily after it was no longer needed. This issue has been fixed. | 
| P388173493 | Inputs, CMAF | Previously, CMAF ingest could fail when its file cache became full. This issue has been fixed. | 
| GLV-6034 | Inputs | Previously, changes to the perpetual decode state of the active input might not take effect, and scheduled input changes could be applied out of order. This issue has been fixed. | 
| P416253718 | Inputs, audio | Previously, an external audio input could encounter a buffering error during demultiplexing. This issue has been fixed. | 
| V2215729395 | Inputs, Event processing | Previously, rapidly switching between inputs could cause the channel to fail. This issue has been fixed. | 
| P434947261 | Inputs, ingest | Previously, the ingest process could leak a small amount of memory over time. This issue has been fixed. | 
| P447628360 | Inputs, MP4 | Previously, MP4 inputs stored in Amazon S3 could fail to start when S3 returned throttling responses. This issue has been fixed. | 
| P405611279 | Inputs, RTMP | Previously, stopping an RTMP input could cause a crash. This issue has been fixed. | 
| V2166482033 | Inputs, RTMP | Previously, RTMP inputs could leak thread resources over time. This issue has been fixed. | 
| P411050851 | Inputs, SRT | Previously, RTP headers on an SRT input were not detected and removed, which could disrupt input processing. This issue has been fixed. | 
| P408608297 | Inputs, ST 2110 | Previously, stopping an ST 2110 ingest job could cause the input to hang. This issue has been fixed. | 
| P381798055 | Output locking | Previously, stale video frames could be emitted when output locking started. This issue has been fixed. | 
| CAPYBARA-527 | Outputs | Previously, output duration could be miscalculated during extended events. This issue has been corrected. | 
| CAPYBARA-532 | Outputs, CMAF | Previously, during very long-running events, output segment numbering could overflow and disrupt CMAF outputs. This issue has been fixed. | 
| P410447465 | Outputs, CMAF | Previously, unpausing a CMAF Ingest Output that started paused could cause segments to not be ingested by MediaPackage. This issue has been fixed. | 
| P420036263 | Outputs, CMAF | Previously, certain HTTP Headers were not sent with CMAF Ingest Outputs to MediaPackage following long interruptions. This issue has been fixed. | 
| P408261903 | Outputs, CMAF | Previously, caption burn-in and embedded captions were not supported for CMAF Ingest outputs. This issue has been fixed. | 
| V2197580307 | Outputs, frame capture | Previously, frame capture segments were not delivered to additional configured destinations. This issue has been fixed. | 
| EML-7575 | Outputs, HEVC | Previously, HEVC profile compatibility flags could be encoded incorrectly. This issue has been fixed. | 
| P432431410 | Outputs, HLS | Previously, HLS segment uploads that were still in progress could be dropped when a channel was stopped. This issue has been fixed. | 
| P429140724 | Outputs, HLS | Previously, SCTE-35 markers in HLS manifests could be placed with small timing rounding errors. This issue has been corrected. | 
| V2177494908 | Outputs, muxers | Previously, MPEG-2 Transport Stream and RTP output timestamps did not continue to advance while a pipeline was paused. This issue has been fixed. | 
| P410568201 | Outputs, SRT | Previously, establishing an SRT output connection could temporarily block other processing. This issue has been fixed. | 
| P438126855 | Outputs, TS | Previously, transport stream outputs using constant bitrate could experience timing drift that caused output segments to grow without bound. This issue has been fixed. | 
| CAPYBARA-234 | Platform | Previously, an internal numeric calculation could overflow and produce incorrect values under certain conditions. This issue has been fixed. | 
| P418771308 | SCTE-35 | Previously, SCTE-35 markers could be lost following an input switch. This issue has been fixed. | 
| P425577949 | SCTE-35 | Previously, ad avail durations could be reported as negative after a timestamp rollover. This issue has been fixed. | 
| V2204798551 | SCTE-35 | Previously, SCTE-35 timing could drift on SDI inputs after an internal timing counter rolled over. This issue has been fixed. | 
| P406855452 | User Interface | Previously, edits to a schedule's 'Repeat Until' setting were not saved. This issue has been fixed. | 

## Resolved issues in Statmux 2.28.0
<a name="rn-2-28-0-resolved-statmux"></a>

There are no resolved issues in this release.

## Resolved issues in Conductor Live 3.28.0
<a name="rn-2-28-0-resolved-cl3"></a>

The following table lists the issues that are resolved in Conductor Live 3.28.0.


| Key | Topic | Description | 
| --- | --- | --- | 
| V2176216624 | Platform | Previously, a database connectivity failure could leave Conductor connections in an unusable state. This issue has been fixed. | 
| V2239399109 | Platform | Previously, shadow and backup input associations could be incorrectly included in channel provisioning. This issue has been fixed. | 
| GLV-7218 | User Interface | Previously, valid Conductor template variables could be incorrectly rejected in certain URL fields. This issue has been fixed. | 
| V2239390785 | User Interface | Previously, configured device display names were not shown in the channel parameters. This issue has been corrected. | 

## Newly identified issues in version 2.28.0 and 3.28.0
<a name="rn-2-28-0-new-issues"></a>

There are no newly identified issues in Elemental Live, Statmux, or Conductor Live in this release.