TASEmulators / TASEmulators/BizHawk
Keyframe savestates versus "P-frame" savestates
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 2.8k
- Forks
- 468
- PR merge metrics
- No merged PRs in 30d
Description
Just jotting down something zero was talking about on IRC a few days ago: The idea would be to have savestates behave like frames in video encoding systems. A "keyframe" state would be directly loadable in emulator cores, but a "p-frame" state would require the previous keyframe to be available to load.
This has huge potential size savings for waterbox cores, but unfortunately requires a lot of front end cooperation.
Contributor guide
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.
Research direction
No files, tests, or entry points are named, so begin by locating the savestate and emulator-core interfaces and the frontend code that loads states. Define completion around directly loadable keyframe states, dependent P-frame states that require a previous keyframe, and the required frontend cooperation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100