If the FFF bank I uploaded a few days ago produces decent MIDI quality, then it may have something to do with the ROMMaker's down-sampling feature. What do you think of producing a ROM file with just enough instruments to play a few MIDI files, without converting to 8-bit , and giving that a try …

That's bad! I knew before I suggested it that the "bow glass" is not in the ROM, but was hoping the piano might at least be sane. There also seems to be (too much) of some sort of echo (or bad reverb) effect. If you load the 16-bit, 2 MiB FFF version of the bank into RAM, is MIDI at least half sane? …

Bad news: Sounds quite broken ... this is canyon.mid played back under windows https://drive.google.com/open?id=0B9WAZV_Pqo7gcnMzNFBUZzg0MjA ... General MIDI via SBOS/MegaEM sounds similarly wrong. That's sounds so bad it's almost comical, except that we have to figure out how to fix it. I can …

There is a certain amount of old cruft in the code, and some other general sloppiness. The global variable rom_size is set to 2 initially, then it even looks like the size can be set using a command-line argument. The only problem is that it is never used; the line that used to refer to it in WPATCH …

This is somewhat peculiar. All of the important files were included in the archive I uploaded. IWSBOS.INI is the ROM configuration file I used, and rom_size is set to 1048576. There were no splits; just a single ROM file generated. If you have a hex editor handy, can you post just the first 172 …

At least that tells us that we can produce usable ROMs. Now that we're sure of that, we can put some effort into tweaking the results. I'm not quite sure where the 2 came from, but I intentionally used obvious values in the ROM configuration file to see how they were treated. If you wanted to see …

Just for some context, have a look at the typical footprint of a more modern flash chip. It's not impossible to solder by hand, but it's not the easiest thing to do for beginners, either. Flash Chip.jpg Personally, I would prefer the option to have two or even three such footprints on the board, to …

If anyone has the time or inclination to test, I have attached a ROM file, along with the ROMMaker ROM configuration file and source FFF/DAT banks. The banks are exactly the 2 MiB files generated from the Pro Patches Lite (PPLT) 1.61 set (using the old Gravis GIPC tool). The ROM file contains the 8- …

As far as I understood, there is hardware possibility to put a 4Mb ROM chip instead of the 1Mb one without any major modifications into the design. By far more problematic is the driver itself as it has to be somewhat modified in order to take the 4Mb ROM image. Yes, according to the Programmer's …

I got a little bit more work done with the software. The first thing I did was write a simple tool that can produce a valid sboslyrs.ini file given a ROM configuration file (as used by ROMMaker). It is important to notice that I said "valid"; the results won't necessarily sound good on the first try …

To my knowledge the drivers in the SDK are outdated. Since the target for the card is to remain compatible with the formerly distributed GUSPnP drivers there's no need for a custom built driver from the SDK ... having someone figure out how exactly the ROMMaker tool works would be awesome tho. I …

This is quite an interesting project shock__ has started! I haven't read the entire thread yet, but I'm getting through it. I have taken quite an interest in the SDK package linked earlier, and have been working to get everything to build more consistently. So far, I have reproduced enough of the …