3 ms·

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

• BubRoss 7y ago
  Video editing is trivial compared to writing an emulator. Get davinci resolve. Anything else will just crash and lag.
  • simias 7y ago
    Thank you for the tip, ideally I'd prefer an open source solution but I realize that might be asking for too much. I'll give it a try.
    • klodolph 7y ago
      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.
    • BubRoss 7y ago
      How much pain are you willing to take for your ideals? If you need something super simple you might be able to just use ffmpeg.
    • sgrove 7y ago
      Depending on what type of video you're trying to do, Komposition might hit the spot https://owickstrom.github.io/komposition/ https://owickstrom.github.io/komposition/
    • kick 7y ago
      OpenShot is really nice, and stays out of your way enough to where you'll be able to edit quickly.
• johnchristopher 7y ago
  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 !
  • simias 7y ago
    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 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.
• blondin 7y ago
  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...
  • simias 7y ago
    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.