-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding another platform #15
Comments
Hi, this is great, I was planning to port Stage on the PicoSystem myself, as soon as I got my hands on one. There is only one "real" You can have a If you want to implement your own way of making sounds, that is incompatible with all the other boards that use Stage, I would recommend doing that as a completely separate library, and letting the game author choose (for example, they could then try to import your library, and if that fails, fall back to Stage's audio object). I haven't seen your Let me know if I can help in any way. |
I can certainly make that happen sooner rather than later if you want to play.
I completely missed this! And - of course - completely broke it when hacking on a copy of stage.py for picosystem.
I'll look into it! Thank you. In the mean time, enjoy your vacation! |
How would I go about adding PicoSystem as an additional platform to ugame? I started by copying and pasting one of the existing platforms and making some minor tweaks therein, and that seems to work.
However, it looks like there are distinct
stage.py
files for each platform. Which one is the source of truth?In my case I'll probably also need to shim out a custom audio engine, since the tiny piezo doesn't quite handle PWM audio and is better driven with a simple single-tone PWM. Is within ugame the right place to do this?
Am I even barking up the right tree?
Edit: I've raised a PR adding DisplayIO to the PicoSystem board in CircuitPython here - adafruit/circuitpython#5398
The text was updated successfully, but these errors were encountered: