Repository navigation
feat(video): decode PyroWave on the console - #19
Merged
Merged
Conversation
The monorepo writes empty bindings for pyrowave-sys on Horizon, so the PyroWave lane has no C API on the console. The leg is the crate at PUNKTFUNK_REV with a Horizon arm: newlib's missing dlfcn.h and clock_nanosleep come from horizon/, and RenderDoc's header learns __SWITCH__. The leg goes once the monorepo builds the crate for Horizon. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The console build turns the PyroWave lane on, offered only where the device probe finds its compute features; the host picks it only when the player asks for it. Each picture is waited on before it is published, so a pyrowave[10s] line logs parse, record and GPU time. Automatic's ceiling stays at 20 Mb/s on the console whatever the lane. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The title's link failed with posix_memalign (Granite's aligned allocator) and dlclose (libloading) undefined. newlib declares the first and devkitA64's libc leaves it out, so it goes through memalign; the dl calls fail every load, as Horizon has no dynamic loader. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The first console launch aborted on an instruction fetch at the start. volk defines a global function-pointer variable under each Vulkan command's name, NVK the functions under the same names, and the title's vkGetInstanceProcAddr bound to volk's variable, so the first Vulkan call jumped into data. The leg renames volk's 767 globals to pf_volk_* in every archive of the crate, so their own references still meet and the vk names are NVK's again. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Opening a PyroWave stream faulted in Granite's first thread_local store, set_thread_logging_interface. cmake-rs replaces the flags of devkitPro's Switch.cmake, which carry -ftls-model=local-exec, and under -fPIC with -mtp=soft the store came out as `str x1, [x0, x0]`, the variable's offset lost to the thread pointer. The leg puts the model back on the C and C++ flags. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The pin moved to 0fc1b6c, version 0.47.0, and the leg kept 0.46.0. The crate itself is unchanged between the two revs; the leg takes the new version and names the rev. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
broslife
force-pushed
the
feat/pyrowave
branch
from
November 19, 2026 00:56
ace001e to
18dc025
Compare
broslife
marked this pull request as ready for review
November 19, 2026 01:28
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Plan D14 and §10: PyroWave on NVK, measured against the X1's GPU before it is offered to players.
What changes
toolchain/patches/pyrowave-sys, a new crate leg. The monorepo writes empty bindings forpyrowave-syson Horizon, so the PyroWave lane had no C API on the console. The leg is the crate atPUNKTFUNK_REVwith a Horizon arm:dlfcn.hwhose lookups all fail (only volk includes it; Granite takes the title'svkGetInstanceProcAddr);clock_nanosleep, which newlib lacks, for Granite's timer;__SWITCH__in RenderDoc's platform check.The leg goes once the monorepo builds the crate for Horizon (
LEG.md).The console build turns the lane on beside NVDEC (
pf-nx-platform/src/console/pyro.rs). The codec row offers PyroWave only where the device probe finds its compute features, and the host picks it only when the player asks for it, so Automatic stays on NVDEC.A
pyrowave[10s]log line: pictures, Mb/s, and parse, record and GPU time, each mean and max, plus the decoder's own stage times. Each picture is waited on before it is published so that the GPU time is measured.Automatic's ceiling stays at 20 Mb/s on the console whatever the lane, so HEVC's Automatic does not change.
Checked
scripts/cargo-nx.sh check -p pf-nxin the toolchain image, withpyrowave-sysbuilt through CMake and bindgen for Horizon.cargo fmt --check, clippy on the workspace and onpf-nx-host --features pyrowave, andcargo test --workspace.Not yet
pyrowave: lane built, device capable …line, then thepyrowave[10s]lines.