Repository navigation
Releases
v1.2.1
Outpace 1.2.1
For publication status and downloads, see the
GitHub Release.
These notes accompany the reviewed release commit; source documentation can precede publication.
Outpace 1.2.1 is a patch release. It fixes casting to DLNA/UPnP renderers so that a failed play
can no longer leave a TV playing a stream the engine has forgotten. It changes no defaults and
needs no configuration change.
Fixes
-
A failed cast no longer leaves the TV playing
(#497,
#498). Whenplayfailed after the
renderer could already have acted on it, for example when the TV did not answer in time, Outpace
forgot the cast but sent noStop, and the stream response the TV had already opened kept
serving. Now:- a
playfailure that may have started playback is followed by one best-effort SOAPStop
(5-second timeout). Only a UPnP fault in answer toSetAVTransportURIis taken as a definite
refusal and gets noStop; - a stream response the TV has open ends when its cast is stopped, fails, or is replaced by a new
playto the same TV, so a TV that ignoresStopstops receiving data.
A failed
playcan take up to 5 seconds longer to answer. Only casting changes; it stays off
unlessOUTPACE_ENABLE_CAST=1. See
Casting. - a
Distribution
Targets, packages, images and signer identity are unchanged from
1.0.2.
Images are published to ghcr.io/outpace-stream/outpace-engine (1.2.1, 1.2.1-minimal,
latest, minimal).
Upgrade and rollback
Upgrading from 1.2.0 needs no configuration change. Restart, then check /healthz and playback.
Keep the 1.2.0 binary or image for rollback.
Validation and limits
The fix is covered by unit tests against a fake renderer (a non-fault Play error, a lost
SetAVTransportURI reply, a refused URI, replacement and the MIME retry) and by an HTTP test
checking that a real /cast/s/{token}.ts response ends after stop, which fails without the fix.
No hardware TV, multi-hour soak or hardware qualification was performed for this release.
What's Changed
- docs(release): publish 1.2.0 pins by @jamezrin in #496
- fix(ace-engine): stop the TV when a cast play fails by @jamezrin in #498
- chore(release): prepare 1.2.1 by @jamezrin in #500
Full Changelog: v1.2.0...v1.2.1
v1.2.0
Outpace 1.2.0
For publication status and downloads, see the
GitHub Release.
These notes accompany the reviewed release commit; source documentation can precede publication.
Outpace 1.2.0 is a minor release. It adds opt-in casting to DLNA/UPnP renderers and an opt-in
SOCKS5 outbound proxy, reports why a stream start is slow or failed, refuses VOD downloads that
would fill the disk, and paces DHT lookups by replies. Both new features are off by default. The
native start routes now return a JSON error body; their status codes are unchanged.
Features
- Casting to DLNA/UPnP renderers
(#488, closes #484). With
OUTPACE_ENABLE_CAST=1,GET /cast/targetsdiscovers media renderers on the LAN with one SSDP
search (cached for 60 s), andPOST /cast/targets/{target}/playstarts a live stream and points
the renderer at a per-cast URL that serves the shared session.stopandstatuscomplete the
API. Live streams only.OUTPACE_BINDmust be reachable from the renderer; a loopback bind
answers409 loopback_bind. A renderer that refusesvideo/mp2tis offeredvideo/mpegonce.
At most 16 renderers and 16 concurrent casts; a new cast at capacity is refused rather than
evicting one. Control routes reject cross-site browser requests. See
Casting. - Optional SOCKS5 outbound proxy
(#492, closes #486).
OUTPACE_PROXY=socks5://[user:password@]host:portwithOUTPACE_PROXY_MODE=off|on|fallback
(defaultoff). Outgoing peer connections and catalog/search requests useCONNECT; UDP
trackers useUDP ASSOCIATEor are disabled, never sent direct; DHT is off while the proxy is
active.onturns inbound serving and port mapping off (an explicit1for either is a startup
error) andoutpace broadcastrefuses to run.fallbackconnects directly and switches
engine-wide, until restart, the first time a live start finds no peers or none connects within
10 seconds. Credentials never reach logs, errors or status. Stream status reports
network_path, andGET /network-policygains aproxyobject. See
Outbound Proxy. - Stream start phase and typed failure codes
(#487,
#493, closes #483).
GET /streams/{network}/{id}/statusaddsphase(resolving,connecting,buffering,
playing,failed) anderror, and answers200for a start that is still resolving or
failed in the last 60 seconds. Codes arenot_found,no_peers,network,unresolvable,
protected,capacity,no_spaceandinternal. - VOD free-space check (#489,
closes #485). WithOUTPACE_CACHE_TYPE=disk, a VOD start that would not fit on the cache
filesystem is refused with507 Insufficient Storageand codeno_space. The new
OUTPACE_VOD_DISK_RESERVE_BYTES(default 256 MiB) sets the space to leave free. A download that
hitsENOSPCorEDQUOTmid-way stops and answers507on later range requests.
Changes
- Native start errors are JSON.
/streams/{network}/{id},.tsand.m3u8return
application/json{"error":{"code","message"}}instead of a bodiless404or a plain-text
422, as do/vod/...errors and native audio-normalization start failures. Status codes are
unchanged. The compatibility/ace/*and/server/apisurfaces are unchanged. Clients that
parsed the old plain-text body should readerror.messageinstead. - Faster DHT lookups (#490). A
DHT walk keeps up to 8 queries in flight and sends the next one as soon as a reply, a BEP-5
error or a 1.5 s slot timeout frees a slot, instead of waiting out a fixed 1.5 s round. A
four-hop offline fixture fell from 4.5 s to under a millisecond; a silent frontier keeps the
old pace. Thetimeoutsfield of the[dht] walk done:log line now counts silent queries,
not silent rounds. - A cancelled start whose provider then fails is no longer reported as
failedby the status
route (#493).
Distribution
Targets, packages, images and signer identity are unchanged from
1.0.2.
Images are published to ghcr.io/outpace-stream/outpace-engine (1.2.0, 1.2.0-minimal,
latest, minimal). The Compose file does not forward OUTPACE_ENABLE_CAST or the proxy
variables; casting from a container also needs --network host.
Upgrade and rollback
Upgrading from 1.1.0 needs no configuration change. Restart, then check /healthz and playback.
Update clients that read the plain-text body of a native start error. Keep the 1.1.0 binary or
image for rollback; 1.2.0 writes no new state to the data directory.
Validation and limits
The new features are covered by unit and HTTP tests: SSDP, device-description, SOAP and URL
parsing and the cast lifecycle; SOCKS5 negotiation, credential redaction and the fallback window;
start-phase transitions and error mapping; the free-space fit and the mid-download ENOSPC path;
and DHT slot pacing on loopback fixtures. Casting was exercised against a software renderer during
review. The DHT pacing was compared on live public channels during review (#490). No hardware TV
matrix, no proxy soak, no multi-hour playback soak and no hardware qualification was performed for
this release.
What's Changed
- docs(release): publish 1.1.0 pins by @jamezrin in #482
- Report stream start phase and typed failure codes by @jamezrin in #487
- perf(ace-swarm): pace DHT walk by responses by @jamezrin in #490
- fix(ace-engine): start-error follow-ups by @jamezrin in #493
- feat: cast live streams to DLNA/UPnP renderers by @jamezrin in #488
- feat: optional SOCKS5 proxy for peer and tracker connections by @jamezrin in #492
- chore(release): prepare 1.2.0 by @jamezrin in #495
Full Changelog: v1.1.0...v1.2.0
v1.1.0
Outpace 1.1.0
For publication status and downloads, see the
GitHub Release.
These notes accompany the reviewed release commit; source documentation can precede publication.
Outpace 1.1.0 is a minor release. It adds an opt-in AceStream identity profile and brings a few
always-on peer and DHT details closer to the original engine. The new profile is off by default,
and no existing default changes.
Features
- Opt-in AceStream identity
(#476). With
OUTPACE_ACESTREAM_IDENTITY=1, the values Outpace shows on the public network match one
official Linux engine profile: peer handshakes, search requests, catalog requests, UPnP mapping
labels and broadcast descriptors. The local API, metrics, logs and startup lines stay Outpace's.
OUTPACE_ACESTREAM_IDENTITY_VERSION,_PLATFORM,_DEVICE_ID,_HARDWARE_KEY,_ASN,
_COUNTRYand_USER_AGENToverride parts of the profile; they are validated at startup and
ignored while the switch is off. See
Engine Camouflage.- The first start with the profile on writes a random device id to
acestream-device-idin
OUTPACE_DATA_DIR(mode0600on Unix). Keep the data directory or volume to keep the id. - When
_ASNand_COUNTRYare not both set, Outpace makes one HTTPS lookup to RIPEstat
(stat.ripe.net) after two distinct peers report the same public address. Redirects are not
followed. Setting both variables skips the lookup. - Compose does not forward these variables; set them in a Compose override.
- The first start with the profile on writes a random device id to
Changes with the profile off
- DHT messages carry the engine's client version tag, use one node id for the whole process so
tokens from aget_peerswalk stay valid for the announces that follow, and send an explicit
portwithoutimplied_port. - Peer handshakes advertise the real listen port and host uptime.
- Catalog responses sent gzip-encoded are decoded, bounded by the same response size limit.
Distribution
Targets, packages, images and signer identity are unchanged from
1.0.2.
Images are published to ghcr.io/outpace-stream/outpace-engine (1.1.0, 1.1.0-minimal,
latest, minimal).
Upgrade and rollback
Upgrading from 1.0.3 needs no configuration change. Restart, then check /healthz and playback.
Keep the 1.0.3 binary or image for rollback. A rollback leaves acestream-device-id in the data
directory, where 1.0.3 ignores it.
Validation and limits
The profile is covered by unit tests for settings validation, the engine-shaped search, catalog
and handshake encodings, device id persistence, the shared search response budget, and
public-address corroboration by distinct peers. The DHT wire shapes are checked byte for byte
against the engine's. No live search, catalog or playback check with the profile on, no multi-hour
soak and no hardware qualification was performed for this release.
What's Changed
- Add an opt-in AceStream identity by @jamezrin in #476
- docs(release): publish 1.0.3 pins by @jamezrin in #479
- fix(deps): update rust crate n0-mainline to v0.7.2 by @renovate[bot] in #480
- chore(release): prepare 1.1.0 by @jamezrin in #481
Full Changelog: v1.0.3...v1.1.0
v1.0.3
Outpace 1.0.3
For publication status and downloads, see the
GitHub Release.
These notes accompany the reviewed release commit; source documentation can precede publication.
Outpace 1.0.3 is a patch release. Live streams whose peers hold less history than the startup
buffer target now start in a few seconds instead of waiting for the 15-second startup deadline. It
changes no defaults and needs no configuration change.
Fixes
- Short live backlogs no longer wait for the startup deadline
(#474,
#475). When the peers of a live
stream held less history thanOUTPACE_PREBUFFER_MS(30 seconds by default), Outpace downloaded
all of it in about a second and then held it untilOUTPACE_PREBUFFER_TIMEOUT_MS(15 seconds)
expired. The startup buffer now releases as soon as every piece up to the live edge has arrived,
and the[prebuffer]log line reportsreason=BacklogExhausted. In a side-by-side comparison on
such a stream, the first byte arrived after about 2 seconds instead of about 16, within a second of
the original engine. The trade-off is that such a stream starts with the lead its peers hold
rather than whatever the deadline would have accumulated; the original engine behaves the same
way. Streams whose peers hold the full target still release onTargetDurationas before, and
VOD is unchanged.
Documentation
- A new Android TV page walks
through sideloading Outpace onto an Android TV box, including wireless adb pairing and checksum
tools for verifying the download
(#472). - Troubleshooting,
Configuration and
HLS Output describe the new
release reason.
Distribution
Targets, packages, images and signer identity are unchanged from
1.0.2.
Images are published to ghcr.io/outpace-stream/outpace-engine (1.0.3, 1.0.3-minimal,
latest, minimal).
Upgrade and rollback
Upgrading from 1.0.2 needs no configuration change. Restart, then check /healthz and playback.
Keep the 1.0.2 binary or image for rollback.
Validation and limits
The new release reason is covered by unit tests for an exhausted and an outstanding backlog,
position updates that arrive after the last chunk, media still readable behind an exhausted
position, sources without live position stats, and an empty buffer. Simultaneous live comparisons
against the original engine 3.2.11 were run on two short-backlog streams and one healthy stream, as
recorded in #475. No new multi-hour
soak or hardware qualification was performed for this release.
What's Changed
- docs(release): publish 1.0.2 pins by @jamezrin in #471
- docs: add an Android TV sideload use case by @jamezrin in #472
- fix(ace-engine): release startup buffer on exhausted live backlog by @jamezrin in #475
- chore(release): prepare 1.0.3 by @jamezrin in #478
Full Changelog: v1.0.2...v1.0.3
v1.0.2
Outpace 1.0.2
For publication status and downloads, see the
GitHub Release.
These notes accompany the reviewed release commit; source documentation can precede publication.
Outpace 1.0.2 is a patch release and the first one published from the
outpace-stream organization. It fixes the warm peer cache on
Android and other hosts whose data directory sits under an execute-only parent, and bounds the
opt-in /metrics endpoint. It also adds a best-effort 32-bit Android archive. It changes no
defaults and needs no configuration change.
Fixes
- The warm peer cache now opens under execute-only parent directories
(#456,
#464). On Android, apps can traverse
but not list directories such as/data, so the cache was never reached. Every start was cold
and the log showed[ace] warm peer cache I/O failed; streaming continues without durable hints.
Termux and any Linux deployment with an execute-only ancestor were affected the same way. On
Linux and Android the cache path is now traversed withO_PATH. Ownership and mode checks,
symlink rejection and the exclusive writer lock are unchanged. Other Unix platforms keep their
previous behavior. GET /metricsscrapes are bounded
(#466,
#468). WithOUTPACE_METRICS=1, at
most two scrapes collect a snapshot at the same time, and each has two seconds. A scrape over
either limit gets503 Service UnavailablewithRetry-After: 1and an empty body, which
Prometheus records as a failed scrape rather than partial values. A normal scrape interval from
one or two Prometheus servers never reaches these limits. Nothing changes with metrics off.
Distribution
- Organization paths. The repository is now
outpace-stream/outpace-engine, and images are
published toghcr.io/outpace-stream/outpace-engine(1.0.2,1.0.2-minimal,latest,
minimal). Images up to 1.0.1 atghcr.io/jamezrin/outpacestay available for rollback but
receive no new tags. The Homebrew tap and Scoop bucket moved to
outpace-stream/homebrew-outpaceandoutpace-stream/scoop-outpace. Archive and package names
are unchanged. - Provenance. 1.0.2 archives, packages and images are attested by
outpace-stream/outpace-engine. Verify a downloaded file with
gh attestation verify <file> --repo outpace-stream/outpace-engine, and an image with
gh attestation verify oci://ghcr.io/outpace-stream/outpace-engine:1.0.2 --repo outpace-stream/outpace-engine.
Releases up to 1.0.1 keep
their original signer identity; see
Installation. - 32-bit Android. A best-effort
armv7-linux-androideabiarchive is published next to
aarch64-linux-android
(#459,
#462), for Android TV boxes that run
a 32-bit userland. Like the 64-bit Android archive, it is optional: a failed Android build never
blocks the release. - Arch Linux. The community AUR packages
outpace-binandoutpace-gitare now documented on
the Installation
page.
Targets, packages and service integrations are otherwise unchanged from
1.0.0.
Upgrade and rollback
Upgrading from 1.0.1 needs no configuration change. If you pull images, switch the image name to
ghcr.io/outpace-stream/outpace-engine:1.0.2. If you installed with Homebrew or Scoop before the
move, re-add the tap or bucket from its new repository. Restart, then check /healthz and
playback. Keep the 1.0.1 binary or image for rollback.
Validation and limits
The cache fix is covered by a regression test that writes, reopens and reads a cache beneath an
execute-only parent, which failed with EACCES before the fix. CI now checks that this test runs as
a normal user instead of skipping
(#469), and cache test fixtures wait for
the real load instead of a 100 ms best-effort window. The metrics bounds are covered by unit tests
for refusal, timeout and the 503 response. No new multi-hour soak, live comparison or hardware
qualification was performed for this release. Preparation checks and candidate CI are recorded in
the release PR.
What's Changed
- chore(github): add issue forms and security policy by @jamezrin in #455
- docs(release): publish 1.0.1 pins and verified status by @jamezrin in #458
- Migrate repositories to Outpace organization by @jamezrin in #460
- Publish best-effort 32-bit Android engine archives by @jamezrin in #462
- chore(hygiene): use the shared identifier hygiene action by @jamezrin in #463
- fix(ace-swarm): traverse execute-only cache ancestors by @jamezrin in #464
- docs: add Arch Linux AUR installation by @jamezrin in #465
- fix(ace-engine): bound /metrics scrapes by @jamezrin in #468
- test(ace-swarm): wait for real warm-peer cache load by @jamezrin in #469
- chore(release): prepare 1.0.2 by @jamezrin in #470
Full Changelog: v1.0.1...v1.0.2
v1.0.1
Outpace 1.0.1
For publication status and downloads, see the
GitHub Release.
These notes accompany the reviewed release commit; source documentation can precede publication.
Outpace 1.0.1 is a patch release. It fixes live audio normalization (OUTPACE_LIVE_AUDIO_NORMALIZE
and OUTPACE_HLS_AUDIO_NORMALIZE), which could end live streams or refuse common AC3 sources.
It adds no features and changes no defaults. Users who leave normalization off are only affected
by the AC3 track handling described below.
Fixes
- Normalization no longer ends live streams on ordinary source behavior
(#447,
#449):- Each new conversion generation looked for fresh PAT/PMT tables and the next video access point
within 1 MiB, so a generation starting mid-GOP on a high-bitrate source failed with
input_overflow. Classification now has its own 16 MiB evidence bound, and scanned bytes
are discarded rather than retained. - A single source chunk larger than the 1 MiB input budget failed with
input_overflow.
Views above 512 KiB are now read in place. - Upstream reconnects every 15 to 30 seconds used up the limit of three recoveries per minute
and ended the session withrecovery_limit. A restart no longer counts toward the limit when
the output before it had been playing for at least 10 seconds. - Normalization failures and recoveries are now logged under
[audio]with their reason code.
- Each new conversion generation looked for fresh PAT/PMT tables and the next video access point
- AC3 signalled as ATSC stream type
0x81is now converted
(#448,
#451). FFmpeg's MPEG-TS muxer writes AC3
this way by default. Previously only DVB signalling (stream type0x06with an AC-3 descriptor
or registration) was recognised, and such sources were refused with422and
normalization.failure = "unsupported". ATSC E-AC3 (0x87) is now recognised too: it is
skipped when a convertible track is present and refused when it is the only audio. A codec
descriptor contradicting the stream type still refuses the stream.
Behavior change with normalization off
The default native HLS output already keeps only the first AAC track when a stream has one, and
drops DVB-signalled AC3 and E-AC3 tracks. ATSC 0x81 and 0x87 tracks are now dropped in the same
way. Streams without an AAC track, and direct MPEG-TS output, are unchanged.
Distribution
Targets, packages, images, provenance and service integrations are unchanged from
1.0.0. A build-dependency update (cc 1.11.2) is included.
Upgrade and rollback
Upgrading from 1.0.0 needs no configuration change. Pin the 1.0.1 image or binary, restart,
then check /healthz and playback. Keep the 1.0.0 binary or image for rollback.
Validation and limits
The fixes are covered by unit tests, a synthetic PAT/PMT vector and the opted-in FFmpeg
acceptance suite, including FFmpeg's default AC3 mux on both the HLS and shared live TS routes.
The 0x81 conversion path has not yet been exercised live against a real AC3 source. No new
multi-hour soak, live comparison or hardware qualification was performed for this release.
Preparation checks and candidate CI are recorded in the release preparation PR.
What's Changed
- docs(release): finalize 1.0.0 publication by @jamezrin in #446
- fix(ace-engine): stop live audio normalization ending streams by @jamezrin in #449
- chore(deps): update rust crate cc to v1.11.2 by @renovate[bot] in #450
- fix(ace-media): recognise ATSC AC3 stream type 0x81 by @jamezrin in #451
- chore(release): prepare 1.0.1 by @jamezrin in #452
Full Changelog: v1.0.0...v1.0.1
v1.0.0
Outpace 1.0.0
For publication status and downloads, see the
GitHub Release.
These notes accompany the reviewed release commit; source documentation can precede publication.
Outpace 1.0.0 brings the features merged since 0.9.0 to release binaries and multi-architecture
images. It supports public, unencrypted live and single-file VOD playback, reciprocal seeding,
signed MPEG-TS broadcasting and the documented AceStream-compatible HTTP subset. Premium
content, accounts and a bundled player/UI remain permanent non-goals.
Features
- In-memory live HLS timeshift (
OUTPACE_HISTORY_*), with per-viewer rewind and bounded
per-source and shared memory budgets. It is not persistent recording. - HLS-origin descriptors and opt-in managed relay (
OUTPACE_MANAGED_HLS), including gzip
playlists, connection reuse,X-Outpace-Upstream-Statusand qualifying origin replay. - Shared live audio normalization (
OUTPACE_LIVE_AUDIO_NORMALIZE) before TS/HLS/support
fan-out. FFmpeg is required when enabled; it is not bundled in published images. - Outbound-only private peer mode, local descriptor aliases and
/network-policy
(OUTPACE_PRIVATE_PEERS,OUTPACE_PRIVATE_DESCRIPTORS). - Support sources kept active without viewers (
OUTPACE_SUPPORT_SOURCES) and/support. - Optional encrypted SRT ingest in native Linux builds with
--features srtand an
encryption-enabled libsrt 1.5.7 or newer. Standard release archives and images omit SRT. - Separate, default-off service-backed
/search(OUTPACE_COMPAT_ACESTREAM_SERVICES).
It uses external plain-HTTP services and bounded signed-response adaptation; search data
is not proof of a verified playback descriptor. Reverse infohash-to-content-ID lookup is
unsupported. Client endpoint/parser integration and deployed scraper qualification are
not established by the local adapter tests. - Opt-in Prometheus
/metrics(OUTPACE_METRICS=1), disabled by default.
Fixes
- Ended HLS sources close playlists with
#EXT-X-ENDLISTrather than returning503forever. - Live
get_media_filesreports MPEG-TS MIME and a display filename. - The prebuffer deadline is absolute from the first media byte; source gaps cannot restart it.
- Shutdown ends viewer responses before draining HTTP; idle cleanup remains responsive when
another stream's cleanup is stuck. - CLI compatibility parsing rejects duplicate query keys and unsupported file selections;
HTTP compatibility still accepts the Android SDK's duplicated descriptor parameters.
Distribution
- Ten required binary targets: Linux musl x86_64, ARM64, ARMv7, ARMv6 hard-float and RISC-V 64;
macOS Intel and Apple silicon; Windows x86_64 and ARM64; FreeBSD x86_64. - Debian/Ubuntu
.deband Fedora-family.rpmpackages for x86_64, ARM64 and ARMv7, with a
systemd service and configuration file. Installation does not start the service. - Debian-based and minimal
scratchimages for linux/amd64, linux/arm64 and linux/arm/v7.
Minimal images useoutpace healthcheckand have no shell, curl or package manager. - Signed build provenance for standard archives, packages and release images. Verify with
gh attestation verify; useSHA256SUMSfor archive/package integrity. - Windows service management, a macOS LaunchAgent, a FreeBSD rc.d script and an OpenWrt
installer/procd service. Consult the wiki before installing on a router or firewall. - Best-effort Android ARM64 archive for Termux, uploaded separately after core publication.
It may be absent if its build fails and uses its own.sha256, notSHA256SUMS. - Homebrew/Scoop definitions use the published release checksums. The active
.env.example
image pin targets 1.0.0. - Standard release binaries use the size-optimized
distprofile; source--releaseand
edge builds keep their existing profile. See the merged profile work in
#429 for its measurements.
Upgrade and rollback
Back up the data directory (including node identity and broadcast keys), pin the release tag,
recreate the container or restart the service, then check /healthz and playback. Keep the old
binary/image and configuration for rollback. Stop active broadcasts deliberately before an
upgrade. The release preparation itself changes no listener, seeding, caching or opt-in defaults.
Timeshift, managed relay, private peers, support sources, shared normalization, external search
and metrics retain their documented opt-in settings. Private peers restrict discovery and inbound
behavior; search is rejected in that mode. Review the
wiki configuration reference
before enabling them. /healthz is liveness, not proof of media delivery.
Deferred scope
The maintainer explicitly deferred the following for 1.0.0 on 2026-11-13:
- #79: multi-file/selected-file VOD.
Multi-file descriptors remain rejected; verified layout/schema evidence is required before
implementing offsets and selection. Single-file playback remains supported. - #269: optional broadcast discovery
and metadata wire fields. Recovered key/accessor/conversion evidence does not prove the full
producer-to-consumer chain, endpoint policy, persistence or advertisement semantics. No new
metatracker/startup-node or tags/logo/description options are adopted. - #272: original-engine HLS transport
origination/support parity. Native TS-to-HLS packaging and managed upstream relay are supported
subsets, not proof of original-engine HLS peer/discovery/origination interoperability. New
origination requires protocol evidence, URL/DNS/redirect policy, sequence/discontinuity rules,
cancellation/cache bounds and synthetic topology tests before implementation.
#128 remains a conditional enhancement:
VOD HLS uses approximate byte-based segmentation without PCR/keyframe-aligned media-time seeking.
Schedule that work after a demonstrated player/interoperability failure. This release does not
promise a DHT keyword crawler or aggregate playlist; known-hash DHT peer discovery is supported.
Validation and limits
The #195 acceptance reconciliation
records a reviewed 7,500-second matched observation with more than 7,200 sampled active seconds
per player, plus separate recovery, integrity and resource-admission evidence. The maintainer
recorded production-replacement sign-off on 2026-11-12.
This was human acceptance, not a new passing soak of the final 1.0.0 candidate.
The historical stale-reconnect stall #246
was closed as not reproduced/inconclusive, not as causally fixed. Retain failed observations;
reopen with timestamped private diagnostics if it recurs. Reference-relative latency to live
remains unmeasured. Sampled decode progress does not prove sub-poll smoothness, identical bytes,
24/7 availability or leak-free behavior. Session admission is configurable and unlimited by
default; there is no new aggregate seed-store byte budget.
Preparation checks and final candidate CI results are recorded in
release PR #444. The
release workflow completed
successfully on 2026-11-13. All ten required archives and six packages matched SHA256SUMS,
and their attestations verified against the source tag and commit. The optional Android archive
also matched its separate checksum.
Both standard and minimal image indexes contain linux/amd64, linux/arm64 and linux/arm/v7;
latest and minimal match their respective versioned digests. Image provenance, source/version
labels, local x86_64 version output and daemon health checks passed. The downloaded Linux x86_64
binary reports outpace 1.0.0. These publication checks are not a new live comparison, multi-hour
soak or hardware qualification. They do not establish behavior on every listed operating system
or on 16 KiB-page ARM hardware. Android remains best-effort for future releases.
What's Changed
- fix(abcompare): preserve precise observation endpoint by @jamezrin in #308
- test(ace-swarm): verify fresh selection attempt budgets by @jamezrin in #309
- feat(abcompare): add bounded timestamped VLC diagnostics by @jamezrin in #310
- docs: point README roadmap at milestones by @jamezrin in #311
- docs: add engine migration guide by @jamezrin in #312
- feat(abcompare): add opt-in diagnostic verbosity by @jamezrin in #313
- fix: refuse protected descriptors before playback by @jamezrin in #314
- perf(ace-peer): avoid receive-buffer copies by @jamezrin in #315
- perf(ace-engine): scan startup packets by slice by @jamezrin in #316
- perf(ace-swarm): share internal serving payloads by @jamezrin in #317
- perf(ace-swarm): borrow live chunk payloads by @jamezrin in #318
- perf(ace-wire): remove temporary frame allocations by @jamezrin in #319
- test(dht): qualify lookup candidates offline by...
Outpace v0.9.0
Outpace 0.9.0
This release improves live protocol compatibility, verified piece serving and bounded actor responsiveness. It does not establish 24/7 production readiness.
- Include optional live descriptor hash fields while preserving legacy wrapped VOD identities.
- Avoid bounded peer-channel deadlocks through credit-based request admission and nonblocking command delivery.
- Publish and serve only complete accepted pieces, with bounded memory and disk lifetimes.
- Add shared configurable session admission.
OUTPACE_MAX_SESSIONSunset or zero remains unlimited; positive values cap provider resources while existing sessions remain joinable. - Keep pool control and cancellation responsive during gossip, publication, reciprocal reads, activation writes and output backpressure; use bounded incremental statistics.
- Strengthen HTTP recovery, decoder and owned VLC validation tooling and lifecycle cleanup.
Validation limits
Reviewed changes passed their repository tests and CI. Bounded deployed comparisons demonstrated sampled decode progress, but the latest long matched observation stopped on both player progress watchdogs before its required sustained window. The underlying cause remains unresolved; shared failure does not establish a source-wide outage. No automatic live retry was performed.
The sustained-validation, startup/parity and historical recovery investigations remain open. The milestone remains open. This release is not a production signoff, playback-quality guarantee, memory-leak exclusion or claim that the historical stall is fixed. Official playback redirect ownership relies on the operator-approved API contract; internal ownership was not independently proven. Existing deployment routing and configuration were preserved.
What's Changed
- fix: preserve early upstream Unchoke state by @jamezrin in #275
- feat: diagnose upstream handshake reply progress by @jamezrin in #276
- fix: recover from empty initial discovery by @jamezrin in #277
- fix(ace-media): bound access detection to PES payload by @jamezrin in #278
- fix(ace-swarm): bound startup pool progress by @jamezrin in #280
- fix(compat): share trusted catalog resolution by @jamezrin in #281
- fix(ace-swarm): select resumable reconnect peers by @jamezrin in #282
- fix(ace-swarm): retain structured peer window progress by @jamezrin in #283
- docs: record 2026-10-27 architecture review by @jamezrin in #289
- fix(ace-wire): include optional live hash fields by @jamezrin in #290
- test(ace-engine): cover HTTP recovery boundaries by @jamezrin in #291
- fix(ace-swarm): bound peer command admission by @jamezrin in #292
- fix(ace-swarm): publish live pieces after acceptance by @jamezrin in #293
- feat(ace-engine): add optional provider session limit by @jamezrin in #294
- chore(ace-swarm): extract live pool actor by @jamezrin in #295
- chore(ace-swarm): isolate bounded gossip from pool progress by @jamezrin in #296
- fix(ace-swarm): keep pool responsive during publication by @jamezrin in #297
- fix(ace-swarm): keep reciprocal reads off pool loop by @jamezrin in #298
- test(ace-engine): decode recovered HTTP video by @jamezrin in #299
- fix(ace-swarm): keep activation writes off pool loop by @jamezrin in #300
- fix(ace-swarm): keep output backpressure off pool loop by @jamezrin in #301
- refactor(ace-swarm): group output step context by @jamezrin in #302
- feat(abcompare): accept caller-owned playback URLs by @jamezrin in #303
- fix(abcompare): retain cancellation through VLC cleanup by @jamezrin in #304
- chore(abcompare): retain monotonic observation origin by @jamezrin in #305
- docs(gateway): clarify validation and cleanup evidence by @jamezrin in #306
- chore(release): prepare v0.9.0 by @jamezrin in #307
Full Changelog: v0.8.0...v0.9.0
v0.8.0
Outpace 0.8.0
Since v0.7.0, Outpace adds managed HTTP broadcast sources, immutable broadcast startup profiles, and a default per-stream inbound admission cap.
Broadcast origination
- Pull HTTP(S) MPEG-TS through PUT/GET/DELETE
/broadcast/{name}/sourceorOUTPACE_BROADCAST_SOURCES. A managed worker reconnects with bounded backoff and discards incomplete reconnect tails. Startup declarations reattach after restart; API-only attachments are process-local. Raw PUT, RTMP and pull share exclusive producer ownership (#267). - Signing indexes are reserved in persistent 128-piece blocks before publication. Restart skips unused reservations; malformed identity state fails closed. Shutdown and deletion retain fences for unfinished persistence work. One daemon must exclusively own its data directory. Windows protects process-crash/ordinary restart while OS/filesystem state survives; system crash or power loss can roll back reservations, lose identities or resurrect deleted records. Linux/macOS guarantees also depend on filesystem/storage sync semantics. Older binaries ignore reservations: before rollback, stop origination and deliberately remove the old identity, then originate a fresh identity. Restoring old signing state can reuse indexes.
OUTPACE_BROADCAST_OPTIONSsupplies immutable named profiles for title, bitrate in bytes/second, piece length, quality and ordered categories across PUT, RTMP, pull and CLI origination. Stored transport bytes and identity remain authoritative; conflicting explicit options fail. Resume announcements now use stored trackers, so changingOUTPACE_TRACKERSaffects fresh identities only. Store budgets must fit a complete piece, including declared profiles and valid stored broadcasts (#273).
Deployment impact
- New default:
OUTPACE_MAX_INBOUND_PER_STREAM=16caps combined media/metadata admissions per canonical stream. The 17th admission closes before a handshake reply. Set0to restore global-only admission, then restart/recreate; Compose needs an explicit service environment override. The global retained-connection default remains 64. This bounds occupancy, not bandwidth, equal service or session lifetime (#268). - Both broadcast JSON settings default to
{}. Profiles have no hot reload and do not create broadcasts by themselves; invalid/conflicting configuration can fail startup. Fresh unprofiled defaults remain title from path, bitrate 8375 bytes/s, piece length 65536, qualityauto, categories["other"]. - Pull access to non-global sources stays off unless the operator sets exactly
OUTPACE_ALLOW_NON_GLOBAL_BROADCAST_SOURCE=1. Fetches validate/pin DNS and verify TLS; redirects and proxies are disabled. Transport URL fetching now also ignores proxy environment settings. Source routes use the existing native listener policy; protect mutation access with a firewall/authenticating proxy. No new authentication framework or listener exposure is added. Compose examples forward source declarations and the source address opt-in; profiles require explicit forwarding.
Evidence and remaining scope
#205 records signed playback by actual official-engine and Outpace consumers in isolated synthetic Linux windows, with separate restart, load and RTMP evidence. Both consumers had corrupt-frame episodes; strict raw-byte continuity and an RTMP status predicate remained unmet. This establishes bounded local origination/playback, without establishing error-free playback, WAN/NAT reachability, public deployment, whole-stream byte identity or long-term reliability.
Optional discovery/metadata wire fields (#269), autonomous support nodes (#270), private peer policy (#271) and HLS transport/support parity (#272) remain follow-ups. Native MPEG-TS-to-HLS packaging does not establish HLS origination parity.
All eight local workspace packages move to 0.8.0. Release preparation changes version metadata only; it does not upgrade dependencies or change the existing seven-archive/checksum and multi-platform container workflows. See the native API and deployment guidance for configuration and persistence limits.
v0.7.0
Outpace 0.7.0
This release brings together the completed v0.6.0 media/VOD and v0.7.0 Ace HTTP milestones. The previous published release was v0.5.0; no v0.6.0 release was published. The milestone acceptance audits are recorded in #199 and #201.
Media and single-file VOD
- Live HLS retains the existing preference for a declared ADTS AAC track, shipped in v0.5.0 (#249). An optional FFmpeg adapter now converts selected AC3 or MPEG Layer II/III audio to stereo AAC-LC, 48 kHz, 128 kbit/s, while copying video. Native AAC and video-only streams stay on the native path. This bounded live-HLS option is not a general transcoder (#257).
- MPEG-2 I-picture access-point detection improves HLS segmentation when the transport random-access flag is absent. Detection is packet-local; split headers retain the existing fallback (#258).
- Single-file VOD distributes work across up to four peers and verifies pieces before ordered output (#259). Original-engine exported metainfo and original disk descriptors are supported (#260, #261). Controlled original-engine tests with generated media established exact downloaded bytes and piece hashes, full HTTP GET, cross-piece and final-piece suffix ranges, and invalid-range responses (#262). This evidence does not qualify public catalog or public swarm operation.
Supported Ace HTTP subset
The opt-in Ace HTTP adapter now has a canonical operator support contract, including routes, selectors, response envelopes, errors, lease ownership, and VLC/JSON examples (#264). Both /server/api and /webui/api/service expose the supported control subset. Client response fixes cover the sampled healthcheck JSON and absolute compatibility-HLS segment URLs (#263). Bounded local acceptance exercised actual VLC playback through a separate peer receiver and the published JSON playback/stat/stop flow. This does not establish complete third-party application or official-engine API parity.
Lazy leased-TS playback now distinguishes backend and metadata start failures with generic 502/422 responses while preserving retryable leases. Upstream operational diagnostics report completed-attempt connection, handshake and live-window phases; these diagnostics do not establish the cause of public-source failures.
Deployment migration
- Compatibility remains off by default. Enable it on the serving daemon with
OUTPACE_ACE_COMPAT=1; use0to explicitly disable it. The canonical variable always takes precedence when present, including false.OUTPACE_EXPERIMENTAL_ACE_COMPATremains a deprecated fallback only when the canonical variable is absent. The selected value must be exactly1,true,0, orfalse; empty or invalid selected values fail startup. Rename the legacy setting, restart the daemon, and recreate Compose services withdocker compose up -d --wait(#265). - Audio normalization remains off by default (
OUTPACE_HLS_AUDIO_NORMALIZE=false). Enabling it requires an operator-supplied FFmpeg executable viaOUTPACE_FFMPEG_PATH(defaultffmpeg) with the documented codecs and pipe support. FFmpeg is not bundled in the supplied container images; enabled container deployments need an operator-built image containing it. Startup checks reject unsuitable executables. Native raw TS and VOD audio behavior are unchanged.
Limits carried forward
Safari/iOS playback, public catalog authentication/availability, full Ace API or application parity, and 24/7 reliability are not qualified by this release. #195 and #246 remain open. Multifile VOD and PCR-based, keyframe-aligned VOD HLS seeking remain deferred. There is no general video transcoder or bundled player/web UI.
All eight workspace packages, including the non-published swarmtest tool, move to 0.7.0 through the shared Cargo version. Release preparation changes only version metadata and the corresponding local lockfile entries, with no dependency upgrades or workflow changes. The existing tag workflow builds seven platform archives with SHA256SUMS, followed by multi-platform GHCR publication; publication alone does not establish playback or soak qualification.