MIDI data isn't recorded when capturing using RetroArch's built-in recording functionality.
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
Research direction
The report describes missing MIDI data in RetroArch's built-in recording, using the PrBoom core and Libretro FM synth; it names no source files or tests. Start by tracing the recording path and how it handles MIDI output, then reproduce with the reported setup. Done means a recording captures the MIDI data along with the other recorded output.
Written by the indexing model from the issue text.
Description
https://github.com/user-attachments/assets/2c9c6f5f-5bcf-40c3-9b08-4e29c8d539b1
I'm noticing a problem with MIDI data being unrecorded when using RetroArch's recording function. This is using the Libretro FM synth (transitioning from the OPL2 emulator; I mentioned implementing an OPL3 emulator in one of the PrBoom issues, as, for example, Freedoom's GENMIDI relies on OPL3, and sounds incorrect on an OPL2 chip), and the core is PrBoom (I sent an issue request on the RA-PrBoom repo for online play functionality) with the IWAD being a beta version of Freedoom Phase 2 0.14.0.
Addendum: My log... if it's any useful, but I don't think it's that useful, but I'm sure it might have some use. retroarch__2026_10_27__14_40_15.log
- Dominant language
- C
- Stars
- 14.6k
- Forks
- 2.4k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 63
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from libretro/RetroArch
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
libretro/RetroArch#20108 · 3 comments ·
Maintainers usually reply within 2 days
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
libretro/RetroArch#20061 · 3 comments ·
Maintainers usually reply within 2 days
-
[Feature Request] [UX] Improve descriptions for "Rewind Buffer Size" and "Rewind Buffer Size Step"Openfeature request
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
libretro/RetroArch#19915 · 2 comments ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 2 days
All issues in libretro/RetroArch
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
schrodinger/pymol-open-source#532 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
facebookexperimental/hermit#347 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 86/100
CTSRD-CHERI/cheribsd#2769 ·
Maintainers usually reply within 2 days
-
good first issue not started
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
CU-Robotics/firmware#257 ·
-
documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 82/100