VOGONS


88Emu is out (Roland SC-88/Pro/50 Emulator)

Topic actions

Reply 60 of 66, by daveiver

User metadata
Rank Newbie
Rank
Newbie
Karmeck wrote on 2026-10-06, 05:56:

it works but 88emu does not recognize it, probably a md5 mismatch. But hanks for letting me know.

I found that 88emu 2.2.25 will still take the rom as long as it's named "sc8820_internal.bin". The warning it displays is purely informational, it will still load it and work correctly in my testing. This dump is so new it happened after the 2.2.25 release, the new MD5 will need to be added to 88emu to get rid of the warning (and allow any filename) for the next release.

Karmeck wrote on 2026-10-06, 05:56:

But really, about the missing roms aspect, are they really missing, like really, or just not easy to access? because, if you have the md5 value, that file is out there.

I think not easy to access since the hashes are known as you pointed out. Hopefully more surfaces soon, but we are in a pretty good spot with true SC-8820, JV-1080 and XV-3080 being shared now.

Reply 61 of 66, by zaphod77

User metadata
Rank Member
Rank
Member

still need the g-800, though. That one has actually working sc55 backwards compatibility (they didn't have to cut samples), as well as some unique samples added to the sc88 map (like StikyRhodes).

The other two (a waveblaster sc55 daughterboard and a sc88 pro daughterboard) are quite a bit less essential.

Reply 62 of 66, by Admiral_MIDI

User metadata
Rank Newbie
Rank
Newbie

I have downloaded all the available roms but the JV-1080 and XV-3080 are not showing up, everything else is working. What am I missing???

Reply 63 of 66, by zaphod77

User metadata
Rank Member
Rank
Member

did you extract the "not a 1080 or 3080" zip file?

Reply 64 of 66, by yes

User metadata
Rank Newbie
Rank
Newbie
Admiral_MIDI wrote on Today, 00:38:

I have downloaded all the available roms but the JV-1080 and XV-3080 are not showing up, everything else is working. What am I missing???

They're known by their code names as NU-10B (JV-1080) and MIIG5 (XV-3080) .

Reply 65 of 66, by Karmeck

User metadata
Rank Member
Rank
Member
daveiver wrote on 2026-10-06, 20:32:
I found that 88emu 2.2.25 will still take the rom as long as it's named "sc8820_internal.bin". The warning it displays is purel […]
Show full quote
Karmeck wrote on 2026-10-06, 05:56:

it works but 88emu does not recognize it, probably a md5 mismatch. But hanks for letting me know.

I found that 88emu 2.2.25 will still take the rom as long as it's named "sc8820_internal.bin". The warning it displays is purely informational, it will still load it and work correctly in my testing. This dump is so new it happened after the 2.2.25 release, the new MD5 will need to be added to 88emu to get rid of the warning (and allow any filename) for the next release.

Karmeck wrote on 2026-10-06, 05:56:

But really, about the missing roms aspect, are they really missing, like really, or just not easy to access? because, if you have the md5 value, that file is out there.

I think not easy to access since the hashes are known as you pointed out. Hopefully more surfaces soon, but we are in a pretty good spot with true SC-8820, JV-1080 and XV-3080 being shared now.

Seems the 8820 rom situation is even more advanced. There seems to be be misconceptions about the ROMs correct size.

https://github.com/dsp56300/gearmulator/pull/315

Reply 66 of 66, by daveiver

User metadata
Rank Newbie
Rank
Newbie
Karmeck wrote on Today, 09:54:

Seems the 8820 rom situation is even more advanced. There seems to be be misconceptions about the ROMs correct size.

https://github.com/dsp56300/gearmulator/pull/315

Yes, this was uncovered after looking at the real cpu rom dump that was just made available the other day. My PR was merged yesterday to add the new MD5 (no more warning with real rom) and this new PR will fix the remaining issue with CPU and rom size assumptions. The next release will have these fixes, but if you don't want to wait or can't build yourself, you can still load the real rom in the current release (2.2.25) by naming the file correctly and it will work just fine (although CPU will be SH7017 instead of SH7016 without this fix, but that shouldn't affect accurracy).