Universal caching of game / media files
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14.1k
- Forks
- 2.2k
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 51
Description
Universal caching of game / media files¶
Description¶
Currently the RetroArch frontend gives the core the file path of the game / media to play. The core than has to open the media file directly. If the file is stored on a remote filesystem, the increased access time and slow bandwidth could cause slowdowns inside the core.
This proposed project would implement a mechanism to cache those files locally (for example in memory), so that the cores can access the files in a cached manner.
Further readings:
https://github.com/libretro/RetroArch
https://github.com/libretro/RetroArch/tree/master/cores/libretro-ffmpeg
Needed knowledge:
C
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
Start by reading the RetroArch repository structure and the referenced cores/libretro-ffmpeg directory to understand how the frontend passes game and media paths to cores. Trace the existing file-access path and determine the scope of a local caching mechanism; the issue does not specify tests or a concrete completion criterion, so clarify those before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100