Skip to content

Releases

FooMidi Multi-Port Community Preview 3.2.3.10 (CLAP MU maps)

Choose a tag to compare

@OnjLouis OnjLouis released this 20 Nov 09:05

The MU map setting now works with compatible native CLAP instruments, including the S-MU2000 use case requested in issue #1. It continues to work with VST instruments.

In Preferences > Playback > Decoding > MIDI Player, select the CLAP instrument and choose MU80 / Basic or MU100 / Native under MU map (Alt+M). Apply the change, then stop and restart playback. Do not send (use MIDI file) is still the default. The map is separate from MIDI Flavor and does not modify the file or move its notes or SysEx to different ports.

Install foo_midi.fb2k-component through Preferences > Components, then restart foobar2000. The package contains both 32-bit and 64-bit builds. No synth or ROM is included.

This is a community preview. Basic, Native and the default were checked with a CLAP test instrument in foobar2000. Listening checks with S-MU2000 and its ROMs are still welcome, especially on a file that does not select its own MU map. The previous 3.2.3.9 preview remains available for rollback.

MIDI Player Multi-Port Community Preview 3.2.3.9 (CLAP)

Choose a tag to compare

@OnjLouis OnjLouis released this 19 Nov 07:14

Native multi-input CLAP support in the FooMidi Multi-Port Community Build. One CLAP instrument can receive up to eight MIDI 1.0 inputs without a VST wrapper. Notes, controllers, program changes and SysEx go to the corresponding input, even when the MIDI file skips a port. Single-input instruments still play the first logical port only.

  • Supports headless instruments and those without the optional CLAP Voice Info extension.
  • Corrects channel mute and song-end event timing on files with multiple inputs.
  • Keeps the existing external MIDI output and Roland GS routing options.

Download foo_midi.fb2k-component and install it through Preferences > Components, then restart foobar2000. The package includes both 32-bit and 64-bit builds. Set your CLAP folder under MIDI Player > Paths, then select the CLAP instrument under MIDI Player. The instrument must match the bitness of foobar2000.

This is a community preview. Native playback and byte-for-byte port routing were tested with a CLAP test instrument in foobar2000. The official Windows x64 S-MU2000 binary exposed its five MIDI inputs in a separate discovery test; playback with its ROMs and with headless 88emu still needs feedback. No third-party instrument or ROM is included. Please report results on issue #1.

The previous 3.2.3.7 preview is still available for manual rollback.

Multi-Port Community Build 3.2.3.7

Pre-release

Choose a tag to compare

@OnjLouis OnjLouis released this 08 Nov 10:55

Multi-Port Community Build 3.2.3.7

This Windows community preview can play a two-port MIDI file through two
different external MIDI outputs. It also adds optional Roland GS setup
adaptation for two separate Sound Canvas or GS-compatible synths. The existing
software synthesizer options are unchanged.

Install and configure

Download foo_midi.fb2k-component and install it through
File > Preferences > Components > Install, then apply and restart. The same package supports
32-bit and 64-bit foobar2000 2.0 or later. Back up your profile and previous
component first. This replaces foo_midi; keep only one copy installed.

Under Playback > Decoding > MIDI Player (Multi-Port Community Build), choose
MIDI output (external device) and open Configure. Select the primary
output (Alt+P) and, for two-port files, a different secondary output (Alt+S).
Apply the settings and start the track again. Single-port files use only the
primary output. With secondary set to None, two-port files stop with an error
before sending MIDI. They are not merged or played partially.

Roland GS playback

For two separate GS-compatible synths, enable Adapt Roland GS for separate
synths
(Alt+G). Recognized shared setup, such as reset and effects settings,
goes to both outputs. SC-88 mode changes become GS resets without changing
either synth's mode. Part-specific messages stay on the intended synth. Both
units must accept the file's GS device ID.

For one Sound Canvas with native A/B inputs, leave adaptation off to send
the file's original messages unchanged. Adaptation is off by default and never
changes single-port playback. It does not recreate a shared effects processor
or translate arbitrary SysEx.

Testing and feedback

Both architectures passed the automated regression suites. Offline routing
checks covered seven original Roland two-port demos, including the SC-88,
SC-8820 and SC-8850, and verified that single-port Zero88 retained all its SysEx.
The build also passed initial listening on the maintainer's setup. More hardware
and screen-reader testing is welcome. Please report the file and passage, both
devices and drivers, whether GS adaptation was enabled, and whether the issue
occurred on first play or after pause or seek.

See Readme.html for transport limitations and rollback instructions.
Updates are manual. The package contains no commercial MIDI demos or synth ROMs.

Multi-Port Community Build 3.2.3.5

Pre-release

Choose a tag to compare

@OnjLouis OnjLouis released this 02 Nov 23:34

Multi-Port Community Build 3.2.3.5

This community preview adds playback through a selected Windows MIDI output.
Browse your foobar2000 playlist and press Enter to play a MIDI file through a
connected instrument or a virtual MIDI port feeding another application.

Download foo_midi.fb2k-component, install it through File > Preferences >
Components > Install
, apply and restart. One package supports both 32-bit and
64-bit foobar2000 2.0 or later on Windows. Back up your profile and previous
component first. This replaces foo_midi; do not load two copies together.

Selecting an output

Open Playback > Decoding > MIDI Player (Multi-Port Community Build).
Select MIDI output (external device), choose Configure, select your
output, then accept both dialogs and restart the track. Alt+O focuses the port
list. A missing or ambiguous saved output produces an error, not a fallback
to another device.

Listen through the receiving instrument or host. Foobar's audio volume, mute,
equalizer and audio effects do not control external MIDI audio. Software
synthesizer playback remains available by selecting that player again.

Playback and testing

MIDI delivery follows the playback transport rather than decoder prefetch.
Bank/program changes, controllers, pitch bends and complete SysEx messages
retain file order, including custom-voice dumps later in a song. Pause, stop
and track changes silence the previous playback. Seek and resume restore the
earlier state and restart notes still held at the selected position.

Live Sound Canvas testing covered SysEx-heavy Roland demos including Zero88,
pause/resume, forward/backward seeking and changing files, without reported
stuck notes or missing parts. A further test confirmed that resuming restored
the MIDI's SysEx and patches after another application had sent a GS reset.
Both architectures build successfully and pass seven automated regressions
each, covering the parser, VST bridge and external MIDI timeline, worker and
mock-driver buffer ownership.

Limits and updates

External output currently supports one logical MIDI port. Multi-port files are
rejected rather than merged. It plays one pass plus the configured decay time;
internal loop/fade settings and software-synth flavor/MU-map/filter overrides
are not applied. Conversion and ReplayGain require a software player.

Seek/resume restarts note attacks; it is not sample-accurate audio seeking.
Large state dumps may delay restoration. Not every physical instrument, MIDI
driver or long-running workload has been tested. Native labelled Windows
controls are used; broader screen-reader testing is welcome.

Updates are manual through this repository's releases. Before reverting to a
version without external output, select a software player, then install your
retained earlier component and restart. Do not overwrite unrelated settings.

The existing multi-port VST routing and optional MU voice-map selection are
retained. No synthesizer ROMs, commercial instrument files, MIDI songs, user
profiles or credentials are included. Upstream credits and bundled dependency
licence notices remain included. See Readme.html for the complete guide.

Multi-Port Community Build 3.2.3.4

Pre-release

Choose a tag to compare

@OnjLouis OnjLouis released this 01 Nov 09:26

Multi-Port Community Build 3.2.3.4

This public community preview adds an optional Yamaha MU voice-map selection
for VST instruments. Thanks to Yamamoto for the suggestion and detailed reports.

Download foo_midi.fb2k-component, install it using foobar2000's
File > Preferences > Components > Install, apply and restart. The same
package supports 32-bit and 64-bit foobar2000 2.0 or later on Windows. It
replaces the existing foo_midi component; do not install a second MIDI decoder.
Back up your profile and previous component before updating.

New MU map preference

Open MIDI Player (Multi-Port Community Build) preferences, under
Playback > Decoding in current foobar2000 versions. Alt+M focuses
MU map (VST):

  • Do not send (use MIDI file) is the default and adds no map-selection message.
  • MU80 / Basic sends Yamaha's MU Basic voice-map selection.
  • MU100 / Native sends Yamaha's MU Native voice-map selection.

Apply your choice, stop playback and start the MIDI again from the beginning.
Pausing and resuming is not sufficient. The preference is independent of
Flavor: it does not force XG or GS mode and does not rewrite the MIDI file.
It applies to the VST backend, including the optional VST instrument used for
XG files; other backend types are unaffected.

The selection reaches declared VST instances at startup, including a host
restart after a backwards seek. Recognized GM, GM2, GS and XG resets reapply
the selected map to their actual destinations at the reset timestamp.
Recognized explicit MU map messages in files now reach all declared contexts,
preserving their original device number. Explicit file messages can override
the preference until a subsequent reset reapplies it.

Testing and limitations

Both Win32 and x64 parser, port-routing, MU-map and real VST-host regression
suites pass, and both complete component builds pass. Tests cover default-off
behaviour, invalid settings, exact map bytes, reset ordering and destinations,
explicit file overrides, unknown-message preservation and existing host IPC.
The installed 64-bit component loads successfully; its native control exposes
a useful accessible name and value, and a non-default map setting has been
observed persisted during local testing.

Audible map fidelity against hardware is not yet independently confirmed.
Please compare Basic and Native using a file that does not select its own MU
map. PhoenixA and PhoenixB from the reported demos are suitable candidates;
F-Cool and R-love explicitly select Native and can override Basic. Not every
voice differs between maps. Report the MIDI, passage, selected map, host and
instrument version, and any reference comparison through this fork's issue
tracker.

This is not full MU80 emulation or a fix for the reported organ clicking or
different pan transition speeds. No synth samples, DSP, effects or gain were
changed. Separate VST instances still do not reproduce one hardware module's
shared effects, polyphony or all cross-port behaviour. The included HTML guide
explains the scope and manual update/rollback procedure.

No ROMs, commercial synth DLLs, MIDI songs, user profiles or private maintainer
tools are included. Existing third-party licences and upstream credits are
retained. Thanks to Peter Stuer and Christopher Snowhill for the original work.

Component source and issue tracker
and parser source. Clone with submodules
for the complete development tree; GitHub's automatic source ZIPs omit their
contents. Updates to this fork remain manual through the community release page.

Multi-Port Community Build 3.2.3.3

Pre-release

Choose a tag to compare

@OnjLouis OnjLouis released this 06 Oct 10:29

Multi-Port Community Build 3.2.3.3

First public community preview of this foo_midi fork. Download
foo_midi.fb2k-component below, install it through foobar2000's
File > Preferences > Components > Install, apply and restart. One package
supports both 32-bit and 64-bit foobar2000 2.0 or later on Windows.

This replaces the existing foo_midi component, rather than adding a second
MIDI decoder. Back up your profile and old component first. The component
identifies itself as MIDI Player (Multi-Port Community Build). Download
Readme.html for an accessible installation and scope guide.

Added routing

  • Standard MIDI Port and Yamaha sequencer port events, including mid-track changes.
  • Up to four independent VST instrument instances: 64 port/channel pairs.
  • Conservative Roland SC-88 and SC-8820 A/B track-layout recognition where
    explicit routing is absent; explicit metadata always wins.
  • Destination-aware Yamaha multi-part and Roland alternate-group SysEx, with
    local-part rebasing, Roland checksum recalculation, and recognized global
    reset/effect distribution.
  • The same SysEx policy for VST and Secret Sauce; Secret Sauce retains three ports.
  • Lazy extra-instance creation and corrected queued SysEx cleanup.

Verification and scope

Win32 and x64 parser and VST-bridge regression suites pass, including timing,
reset cycles, saved state, independent channel groups, later port changes,
unsupported ports and byte-preserving MIDI round trips. Routing audits covered
255 Roland SC files and 28 additional Roland files; one pre-existing malformed
checksum was preserved, not silently repaired. Listening checks confirmed the
SC-88 demos and the corrected Yamaha multi-port percussion case.

This is a community preview, not an official upstream release or an emulation
of one shared hardware module. Separate instances do not share hardware global
effects, polyphony or cross-port receive-channel reassignment. Unknown bulk dumps
remain on their declared port. Missing ports are not invented; event ports
outside a backend's capacity are not merged into another port. Please test
additional files, instruments and systems and report reproducible differences.

No synthesizer ROMs, commercial instrument DLLs, MIDI songs or user settings
are included. Updates to this fork are manual through this release page; the
upstream component catalogue does not track this community build.

Thanks and source

Thanks to Peter Stuer for foo_midi and
libmidi, and Christopher Snowhill for the
original component. Upstream credits and
licences are preserved. This build is based on upstream foo_midi 3.2.3.0;
no upstream pull request has been submitted.

Community component source and
parser source. Clone with submodules
for the complete development tree; GitHub's automatic source ZIPs do not
include submodule contents.

Please use this fork's issue tracker for community-build reports, including
the foobar2000 version/bitness, backend, instrument and reproducible passage.
Share MIDI material only when you have permission.