Emulating a gameboy is a fun project, I highly recommend it.
The most patience testing element of it is you won't really see any direct results for quite a while, but once you get that Nintendo logo scrolling down the screen, achieved from implementing a lot of the core components (cpu, memory, ppu, screen etc) it's almost like magic and extremely satisfying!
The Gameboy sound chip is definitely one of the trickiest part of the console, if only because there are a million tutorials out there on how to start a Gameboy emulator but very few go all the way, and generally the sound chip is what you do last. It's also surprisingly quirky and many games will misbehave if you don't implement some weird edge cases.
It's also annoying to debug because it's not as obvious as video when something is wrong, especially when you've just spent two hours listening to the same chip tune square waves in a row...
I'm interested in writing my own GB emulator mostly because sound is so patchy across all existing JavaScript implementations.
My entrance into the GB scene coincided with my interest in LSDJ, and I really want to write a web app around it[1], but I'm stymied by outdated implementations and my own lack of domain knowledge.
The most thorough reference I've found for the Game Boy SPU is unfortunately the Gambatte source code itself since it's a fairly accurate emulator and open source. Unfortunately it's also not the most human-readable code (due to micro-optimizations and lack of comments, plus it's C++ which is already a -10 handicap in readability).
That's a good introduction. The GameBoy is really a good starting point to get into emulation, I recommend it.
I've been thinking about making my own tutorial for Gameboy/Gameboy Color emulation over the past few months, I've even finished writing the emulator itself: https://github.com/simias/gaembuoy
I've made sure to rebase all of my fixes to have a single, linear, clean commit history that should be easy to follow. It can play most GB and GBC games. Now I just need to make the actual tutorial, but I want to make videos and I know nothing of video editing so I'm afraid that writing the emulator was actually the easy part.
If somebody has tips for video editing on Linux, I'll gladly take them...
Well, talking on the video will be faster than writing out articles but will it result in materials best suited to your intended audience ?
edit: also, video editing is the final process of putting everything together. Which learning style are you going for ? What visuals are you using to support that ? How are you going to assess your audience's progress ?
Pedagogy is a really interesting and rewarding field ! So many ways, so many questions !
I believe it can be, I find that explaining things using animations and being able to use a more casual tone while narrating can be helpful and easier to follow.
I've already tried writing a PlayStation emulation guide: https://github.com/simias/psx-guide (only covers the very basics unfortunately). I found that in order to really get in-depth I had to write big walls of text to explain relatively simple concepts. Being able to talk more casually and expressively over illustrations can be less daunting for somebody looking to get into emulation.
Regarding your edit: I already took a bunch of notes while actually implementing the emulator so I have a fairly clear idea of what my script will look like (i.e. Intro -> CPU instructions -> timings -> basic GPU -> controller input -> sprites -> sync to real time -> etc...). I won't focus on the code too much because it's not a programming tutorial, it's meant to me an emulation tutorial. It would be targeting people who already know how to program but might not be comfortable in the low-level and don't know where to start.
There is OpenShot but I haven’t used it. The main features I tend to miss in the OSS video editors are proxy editing (which is an enormous timesaver) and basic audio features like side-chain compression. You may or may not care about the same features that I do.
I like to record voiceover in a separate audio track and process it separately in post. From what I can tell, OpenShot doesn’t support videos with multiple audio tracks.
thank you so much for doing this! here goes one resolution for 2020! i will be checking the repo.
small side rant: your repo name -- not saying you should change it, you are allowed to use any name you want -- is a good example of google always trying to outsmart users and being frustrating.
it keeps auto-replacing my search for me. i mean i know i can quote the search but i tend to bookmark a lot from my phone. and it's easier to search for sites i know exist than having to type long urls. so frustrating sometimes when it tells me i didn't mean what i meant...
Eh, it's not so much trying to be smart and more trying to be unique I suppose. I guess I could've named it "my-gameboy-emu" but I'm always a bit wary of using copyrighted names in emulation projects, probably more out of superstition than anything else to be honest.
If you have an other proposition I'm all ears, I don't really care for the name to be honest. Open an issue if you want.
I can also highly recommend the PyBoy[0] project for Game Boy emulation. It is written in Python, has an accompanying report for documentation, and is still being developed.
It provides an interesting basis for student projects to work on, such as machine learning on games, rewinding time and replaying (great for machine learning), adding the sound-subsystem, link-cable, and much, much more.
One of the reasons I first got into programming was due to a fascinations with emulators. Several years later, I'm finally working on a Gameboy emulator of my own. It's a really rewarding experience, I had taken a brief look at GB assembly code before and couldn't make head or tails of it, but after implementing the CPU and memory, a lot of the actions taken within code finally make sense.
I'd like to write my own document on emulator development someday, but I need to finish my own first. I'm nearly at the point where I can display a screen, hopefully sometime within the next week.
It's definitely based on the Z80, but it's also different enough that you can't really base yourself on Z80 docs to implement the Game Boy CPU (I learned that the hard way). The flags are different, the timings are different, some instructions are removed, some instructions are added etc...
It's more like a cut-down Z80. Some registers are missing (note the list excludes IX and IY), as are some instructions (but a few others are added) and even some of the status flags.
How long did it take to make? I been thinking about writing my own emulator in JavaScript for a while now. I know there's a lot of great projects out there, but I like to make one myself.
Getting an implementation of the CPU instructions in a high level language with instruction level accuracy and approximately correct timings is a weekend or two project.
Going for extra components like the graphics or audio support, or higher accuracy in terms of cycle counts and timing can make it a lot longer.
The first emulator I wrote in JavaScript for a subset of x86 took a couple hours (maybe 4-6) over the weekend before I could run a `int main() { return 1 + 3; }` program. Like others have mentioned the GB takes longer before you get to the point of something you can see working.
The most patience testing element of it is you won't really see any direct results for quite a while, but once you get that Nintendo logo scrolling down the screen, achieved from implementing a lot of the core components (cpu, memory, ppu, screen etc) it's almost like magic and extremely satisfying!