For my current tests in C, I ported the code back to neslib examples and I'm using, I think, NROM (128/256). For now the code and data fits in 32k and I have no issue but once I switch back to my target mapper I need to decide how to manage it.
For my test, since I was not able to convert the song to famitome (for this project is not big deal), I decided to try the example by Shiru that uses famitracker for music and a trimmed down version of famitone for sound fx and it's working quite well. My old ft3.0 data converted to 4.6 got trimmed by at least 1k so there was some good things out of it.
As you can imagine, those 2 engines put together will take a lot of space. From my map file, both combined seems to takes around 177E bytes, which is almost a bank on mmc3.
How would you manage such a big engine and the music data on an MMC3? Would you keep the engine in the locked banks or switch them when necessary?
For testing code only, everything is the same bank is more than enough but it will become an issue to fix so I should start to migrate the code as soon as possible.
For my test, since I was not able to convert the song to famitome (for this project is not big deal), I decided to try the example by Shiru that uses famitracker for music and a trimmed down version of famitone for sound fx and it's working quite well. My old ft3.0 data converted to 4.6 got trimmed by at least 1k so there was some good things out of it.
As you can imagine, those 2 engines put together will take a lot of space. From my map file, both combined seems to takes around 177E bytes, which is almost a bank on mmc3.
How would you manage such a big engine and the music data on an MMC3? Would you keep the engine in the locked banks or switch them when necessary?
For testing code only, everything is the same bank is more than enough but it will become an issue to fix so I should start to migrate the code as soon as possible.