Skip to content

Add Namco WSG family support - #151

Open
cam900 wants to merge 3 commits into
ValleyBell:masterfrom
cam900:namcowsg
Open

Add Namco WSG family support#151
cam900 wants to merge 3 commits into
ValleyBell:masterfrom
cam900:namcowsg

Conversation

@cam900

@cam900 cam900 commented Apr 4, 2026

Copy link
Copy Markdown
Contributor

This PR add support of:

  • Namco WSG (Standard 3 voice discrete WSG, some hardware has compatible sound generator with RAM)
  • Namco Pole Position WSG (8 voice quadraphonic WSG used for pole position series)
  • Namco C15 (aka 15XX, 8 voice mono WSG)
  • Namco C30 (aka CUS30, 8 voice mono/stereo WSG with noise generator and RAM)

All of these cores are based on MAME namco.cpp core.

Header size is increased for allow more chip support (its size is placeholder)

Related MAME branch: https://github.com/cam900/mame/tree/mao_vgm

cam900 added 2 commits April 4, 2026 20:49
This PR add support of:
- Namco WSG (Standard 3 voice discrete WSG, some hardware has compatible sound generator with RAM)
- Namco Pole Position WSG (8 voice quadraphonic WSG used for pole position series)
- Namco C15 (aka 15XX, 8 voice mono WSG)
- Namco C30 (aka CUS30, 8 voice mono/stereo WSG with noise generator and RAM)

All of these core is based on MAME namco.cpp core.

Header size is increased for allow more chip support (its size is placeholder)
@ValleyBell

Copy link
Copy Markdown
Owner

small note: The reason I haven't merged this so far is, that I'm very split about whether or not I want WSG support in the VGM format due to the very small number of games that use each variant of the chip.

I haven't ruled it out, but I also don't feel like adding even more chips right now.

@superctr

Copy link
Copy Markdown
Contributor

One compromise could be to add the chips to libvgm's emu library without adding them to the VGM format.

@ValleyBell

Copy link
Copy Markdown
Owner

Oh, that's a good point!
I would merge this instantly in that case.

@DeltaRazero

DeltaRazero commented Aug 28, 2026

Copy link
Copy Markdown

At that point I'd expect the PR's author to state their plans regarding the added emulation (which at this point is meant for in .vgm).
If it's going to be used in a separate player: that's fine. If it's going to end up unused, I'd say don't bloat libvgm with it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants