Validate paired idle-anchor sprite loops on Apple Silicon/MLX
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 28/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- javascript
- Domain
- computer-graphics, testing-qa
Research direction
Read the paired-render workflow in server/services/sprites/localAnimationRender.js, walk.js, and animationTrackWorkflow.js, then inspect the sprite walk and track authoring cards. Run directional-walk and non-walk pairs on a provisioned Apple Silicon/MLX H3 host with matched settings and inputs; inspect source clips and packaged loops for end-pose recovery, identity drift, and retained motion. Done when a private evidence report records settings and a pass/fail conclusion for each pair.
Written by the indexing model from the issue text.
Description
Split from #13648 at the user's request to make independent hardware targets routable. This successor owns only Apple Silicon/MLX; the sibling's result is not a prerequisite for executing or completing this issue. Original implementation #13615 merged in #13649 (be4220487480b8aeb714493dfa725aded7182428); original provenance and discussion remain in #13648.
The implementation for #13615 adds opt-in first/last-frame conditioning to local sprite loops. Deterministic tests can prove that both endpoints use the same prepared chroma-backed input, but cannot establish end-pose recovery, identity drift, or whether useful interior motion survives.
Current blocker: the available install's animation-provider readiness endpoint reports no local MiniMax H3 build. No full-model clip has been rendered or inspected for this change. The existing LightX2V hardware issue #13637 concerns a different sampler/adapter contract and does not cover endpoint pinning.
Chosen next step: an operator with a provisioned Apple Silicon/MLX H3 host run paired stock-image/paired-endpoint sprite renders through the normal authoring UI. Keep prompt, source anchor, seed where available, model, canvas, clip frames and postprocessing geometry identical within each pair. Use already accepted model terms and installed weights; this task does not authorize purchases or downloads.
Affected areas: server/services/sprites/localAnimationRender.js, walk.js, animationTrackWorkflow.js, and the sprite walk/track authoring cards.
Acceptance criteria:
- Record the exact PortOS revision, model/runtime revision, conditioning mode, both prepared input hashes, render settings and hardware class, without private instance records or machine identifiers.
- Inspect source clips and packaged loops for end-pose recovery, identity drift and retained interior gait/action; matching still endpoints alone are insufficient.
- Exercise at least a directional walk and a non-walk loop on this runtime. Record any static-loop, chroma, cycle, baseline or atlas rejection without weakening those gates.
- Keep outputs private and attach a redacted evidence report with a pass/fail conclusion for each pair. File or fix any reproduced defects.
- Remove blocked only when the required hosts, runtimes and weights are available. Close only after this runtime's report exists; deterministic mocks do not satisfy this hardware evidence.
Hardware owner / help wanted: operators of the Apple Silicon/MLX H3 host. Their actual hardware runs are needed to judge runtime-specific motion fidelity. This is blocked on hardware/runtime availability, not a design decision.
Dispatch: model:medium for routine platform-specific workflow execution and visual comparison; effort:medium for assessing the paired clips against several existing quality gates without designing a new rendering algorithm.
Related to #13615.
- Dominant language
- JavaScript
- Stars
- 38
- Forks
- 32
- Avg merge
- 44m
- Merged PRs (30d)
- 990
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from atomantic/PortOS
-
area:media blocked cuda effort:high enhancement help wanted model:medium plan windows
Difficulty 4/5 3-5 days Newbie friendliness 35/100
atomantic/PortOS#13683 · 1 comment ·
Maintainers usually reply within 1 day
-
apple-silicon area:media blocked effort:high enhancement help wanted macos model:heavy plan
Difficulty 5/5 Over a week Newbie friendliness 20/100
atomantic/PortOS#13682 · 1 comment ·
Maintainers usually reply within 1 day
-
area:media blocked cuda effort:medium help wanted model:medium plan windows
Difficulty 3/5 1-2 days Newbie friendliness 35/100
atomantic/PortOS#13681 · 1 comment ·
Maintainers usually reply within 1 day
-
area:media blocked effort:high model:medium plan planner:gpt-6-1-sol
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
area:media blocked effort:xhigh model:heavy plan planner:gpt-6-1-sol
Difficulty 5/5 Over a week Newbie friendliness 25/100
Maintainers usually reply within 1 day
All issues in atomantic/PortOS
Similar issues
-
area: apple-music area: build-release bug effort: small priority: high
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
ChristianTabor/Argon#32 ·
Maintainers usually reply within 1 day
-
0️⃣ phase/new
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Link Checker ReportOpenautomated issue report
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
good first issue tests
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day