A reference list for the cores that AVFoundation fails to record, a note on OpenGL's failure to have video encoded and a request for FFmpeg to be brought back.

Open
#19,927 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
c, ios

Research direction

Start by reading RetroArch's iOS recording and video driver entry points; the issue does not name specific files or tests. Check how AVFoundation handles NXEngine and Anarch recording, how OpenGL GPU recording behaves, and where FFmpeg support was removed. Done means recording works for the reported cores and the requested FFmpeg fallback is restored.

Written by the indexing model from the issue text.

Description

I'm putting this list down so that the maintainer and any contributors know what cores and drivers don't work with AVFoundation; I'm limited to the TestFlight builds, so no, for example, Dolphin or Flycast tests (there are optimised builds of both cores (iCube for GCN/Wii and iFly for Dreamcast, both by Joseph Mattiello, Virtual Jaguar's maintainer), it'd be nice to have both as RetroArch cores, but it's up to others, like Apple and Flycast's developers; that deserves their own issues/discussions on their own repos).


From what I have tested, and so far, there are two cores that AVFoundation doesn't encode. Those are NXEngine and Anarch (both fail to encode anything). FFmpeg recorded the coreswithout issue, but FFmpeg is now gone. For now, until the maintainers fix AVFoundation and add an RTMP client, I request that FFmpeg be brought back. In addition, there are bugs in relation to GPU recording with the OpenGL video driver (black screen, for instance).


Note: Other cases of OpenGL, like using OpenGL itself, OpenGL-based cores, do not work properly on iOS, and doukutsu-rs doesn't record at all (it has its own sorts of quirks). Both deserve their own issues (on their own repos, where applicable), as they are out of scope for this issue.

Dominant language
C
Stars
14.6k
Forks
2.4k
Avg merge
2d 5h
Merged PRs (30d)
63

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from libretro/RetroArch

All issues in libretro/RetroArch

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.