Maybe with MMC3.PRG bankswitching ?
And, I plan to add a DMC music/sfx example.
And, I want to do a much better SMB3/Metroid bi-directional platformer with better physics.
Moderator: Moderators
Maybe with MMC3.PRG bankswitching ?
linkmikejmoffitt wrote:Your blog made front-page on Hacker News!
Done.mikejmoffitt wrote:Your blog made front-page on Hacker News!
Do you have any plans on discussing PRG bankswitching techniques from a C context?
.I do usually suggest to think about writing the interrupt handler completely in assembler
Yeah. An additional problem with IRQ handlers written in C is that you can't rely on the timing of the C code very much.dougeff wrote:I was hoping to write the IRQ code in C, so people could read it more easily. But, I guess it should probably be written in ASM, for stability. Otherwise, I would have to copy all the zeropage C variables, at the start of the IRQ and replace them at the end of the IRQ.
When you record form a keyboard, I agree it's a good idea to quantize the notes. I also agree keeping the MIDI channels monophonic is a requirement to get meaningful results in the FamiTracker import.dougeff wrote:I added a tutorial on 'Importing a MIDI file to Famitracker' [...] If anyone has a better method, please let me know - or any specifics on how to do this with any other software, thanks.
I'm still working on ways to import MIDI to Famitracker. My first tests, with BPM at 120 in Reaper, import with WAY too many ticks per note. So, I did a few tests, recording with BPM (in Reaper) set to 12 (while I play the notes at 120 BPM) gets it very close to what I want. With 5 ticks per note in Famitracker. Changing the project BPM to 100 and then forcing the MIDI track to 125 (125/100 = 5/4)...imports with 4 ticks per note.Can you tell more about why you set the project tempo to 12 BPM before recording, then later set the project tempo to 100 BPM and the MIDI track tempo to 125 BPM?
To make sure we're talking about the same thing, perhaps you mean "rows" instead of "ticks"? (That is, your 1st test yielded many rows per note, 2nd test 5 rows per note, and 3rd test 4 rows per note?) In FamiTracker and other trackers, rows are what you see on the screen -- each line is a row. Ticks are sub-units of a row that you hear when you use arpeggios and other effects commands in the last three character columns of each channel. (In FamiTracker, go to the Help menu and choose "Effect table" to see the effects commands.)dougeff wrote:My first tests, with BPM at 120 in Reaper, import with WAY too many ticks per note. So, I did a few tests, recording with BPM (in Reaper) set to 12 (while I play the notes at 120 BPM) gets it very close to what I want. With 5 ticks per note in Famitracker. Changing the project BPM to 100 and then forcing the MIDI track to 125 (125/100 = 5/4)...imports with 4 ticks per note.