• 2026-10-15DOCS Five-tool multilingual manuals and MUCVOICE v0.5beta
• 2026-10-13UPDATE SCC/SSG, PCMInvert, performance fixes and MUCVOICE
• 2026-10-04SAMPLES Snatcher — 44 MUC songs added to the samplesNEW
• 2026-10-03RELEASE MucoMSX v0.81-beta released
• 2026-10-03DOCS mucomDotNET extension command guide published (한국어 · 日本語 · English)
• 2026-09-25SAMPLES The Maze of Galious — 15 MUC songs added to the samples

About 프로젝트 소개 · 概要

MUCOMSX brings MUCOM88 — the FM music toolchain Yuzo Koshiro (古代祐三) developed for the YM2203 and YM2608 (Sound Board II) of the NEC PC-8801mkⅡSR and later — to the MSX. The whole cycle runs on the machine itself: write MML, compile it, hear it, export it, without ever moving a file to a PC.

See it working 시연 영상 · デモ動画

Short demonstrations of the editor and the standalone player running on MSX.

Thumbnails load from YouTube; the player itself is only loaded once you press play.

The toolchain 구성 도구 · ツール構成

Five programs cover the whole workflow. Every manual is available in Korean, Japanese and English.

Which tool should I use?

File formats

How a song moves through the tools 작업 흐름 · 作業の流れ

There are two routes from source to song: an interactive one you work in, and a batch one you script.

   ┌─────────────┐
   │  SONG.MUC   │   MML source — write it in MUCEDIT, or any text editor
   └──┬───────┬──┘
      │       │
      │       └──────────────────────────────┐
      │                                      │  MUC2MUB SONG.MUC
      │  MUCPLAY /LOAD → /COMPILE            │  (one shot, no session,
      │  (or F1→2 inside MUCEDIT)            │   no sound hardware)
      ▼                                      │
   ┌─────────────┐                           │
   │   session   │  compiled song, resident  │
   └──┬───┬───┬──┘  in mapper RAM            │
      │   │   │                              │
  /PLAY  /MUB  /VGM        (F1→3, F1→4, F1→5)│
      │   │   │                              │
      ▼   ▼   ▼                              ▼
   listen  SONG.MUB   SONG.VGM           SONG.MUB
              └────────────┬─────────────────┘
                           ▼
                  MUBPLAY SONG.MUB

The batch route has no such state. MUC2MUB always reads the .MUC as saved on disk — so if the editor still holds unsaved changes, it will not see them.

Requirements 동작 환경 · 動作環境

Quick start 빠른 시작 · クイックスタート

Just listen to a song

CD SONG
MUCPLAY SONG.MUC

Press any character key or Esc to stop.

Edit, hear, repeat

MUCEDIT SONG.MUC

Inside the editor: F1 2 to compile → read the result → F1 3 to play. Like what you hear? Ctrl+S to save. You do not have to save before compiling — MUCEDIT compiles the buffer in memory.

Work from DOS and export

MUCPLAY /LOAD SONG.MUC      ← read the source into memory
MUCPLAY /COMPILE            ← compile it (nothing is written to disk yet)
MUCPLAY /PLAY               ← listen
MUCPLAY /MUB SONG.MUB       ← export compiled song data
MUCPLAY /VGM SONG.VGM       ← export a chip-command log
MUCPLAY /RELEASE            ← free the session when you are done

Edited the .MUC in another editor? Run /LOAD again — /COMPILE alone recompiles the copy already in memory.

Convert without playing — one song, or a whole album

MUC2MUB SONG.MUC              ← writes SONG.MUB
MUC2MUB SONG.MUC TEST.MUB     ← or name the output yourself

For a whole album, let DOS drive it. Put this in BUILD.BAT:

@ECHO OFF
MUC2MUB SONG01.MUC
MUC2MUB SONG02.MUC
MUC2MUB SONG03.MUC

MUC2MUB returns 0 on success and 1 on failure, so a shell can check each song. It does not stop the batch by itself when one song fails — and a .MUB left over from an earlier run will still be sitting there, so never count files to decide whether a batch succeeded.

MML at a glance

FM is not a continuous run from A to F — D, E, F are SSG, and FM continues at H.

#mucom88 1.7
#title First Steps
#composer ToughkidCST

D T120 C128 o4 l8 v10 q0 cdef gab>c4 r4
E C128 o3 l4 v8 c r g r c r g r
F C128 o2 l2 v7 c g c g

Case matters: c is a note but C sets the base clock; t225 is a raw Timer-B value while T120 is BPM.

Two gotchas worth knowing up front

/L does not mean the same thing everywhere.

Source, editor, page and total DATA limits are separate. These are the current extended-build limits; adding RAM does not automatically raise them.

A 40 KiB source is within the editor's size limit. Macro expansion can still exceed a page or total DATA limit. Ordinary songs retain MUB8; OPNA extensions use muPb 0100, native MSX targets use msPb0100, and SCC/SCC+ SSG extension uses msPb0101. A–K each support pages 0–9 sharing one physical YM2608. A 512 KiB mapper does not guarantee that every large song fits with other sessions resident.

Documentation 문서 · ドキュメント

Every manual is available in all three languages. The MUCEdit manual is the broadest introduction — the editor, the MML syntax, every compile error code, the source warnings, and troubleshooting. The MUC2MUB manual goes deepest on the compiler itself: the full error and warning reference, filename and memory rules, and safe saving and recovery. No MD5 calculation or verification is required or provided.

Wiki — writing the music 음악 만들기 · 音楽づくり

The manuals describe the tools. The wiki describes the music — how MUCOM88 MML is actually written, and how the voices, rhythm patterns and PCM banks a song depends on are prepared. MUCVOICE edits FM and SCC/SCC+ voices on the MSX; WAV conversion and PCM-bank construction remain PC tasks.

Read the mucomDotNET command guide, native MSX targets, SSG extension, MUCVOICE guide and memory and file limits.

Downloads 다운로드 · ダウンロード

Find downloads on the releases page. The current package layout is MucoMSX_YYMMDD.zip for all five tools, factory voices and quick help, plus MucoMSX_Docs_YYMMDD.zip for complete Korean, English and Japanese manuals. Optional .sha256 files check download integrity. Earlier releases may contain only the original four tools; check each release's contents.

Related, from the original PC-8801 project

Questions & issues 문의와 제보 · 質問と報告

Found a bug, hit something the manuals don't cover, or have an idea for the tools? Please open a ticket on the repository's issue tracker. Search the existing issues first — someone may have hit the same thing. Korean, Japanese and English are all welcome.

What to include in a playback or compile report

License 라이선스 · ライセンス