Open jgcodes2020 opened 2 months ago
I'm not sure what kinda features you're planing to add or where, could you clarify it a little?
I'd also like to mention that RMG uses upstream mupen64plus-core mainly, though sometimes I merge pending PRs for RMG myself while we wait for the slow upstream maintainers to merge it.
If you're talking about adding UI features to RMG then I wouldn't mind including those optionally behind a compile time option, though there will need to be some form of discussion.
I'm not sure what kinda features you're planing to add or where, could you clarify it a little?
Basically, the things I mentioned above:
RMG-Audio
to extract audio data. I'd also need to depend on FFmpeg for the video encoding functionality.RMG-Scripting
or the like.Those general ideas sound fine to me, as long as they're a compile time build option I won't have an objection to having it upstream here as long as you're not expecting me to maintain those parts by myself which is hopefully understandable!
The SM64 TASing community currently uses this to make TASes: mkdasher/mupen64-rr-lua-
The features we've added over the emulator include:
We've been considering rebasing our tools on Mupen64Plus for a while now; this seems like a good base for it. Is this project willing to take such features upstream, or should they stay in a fork?