[MacPorts] #71006: qsynth: Issues with MIDI Bank select
MacPorts
noreply at macports.org
Wed Oct 2 13:09:24 UTC 2024
#71006: qsynth: Issues with MIDI Bank select
-----------------------+-----------------------------
Reporter: Sixty4ce | Owner: RJVB
Type: defect | Status: assigned
Priority: Normal | Milestone:
Component: ports | Version: 2.3.4
Resolution: | Keywords: monterey x86_64
Port: qsynth |
-----------------------+-----------------------------
Comment (by Sixty4ce):
Replying to [comment:3 RJVB]:
> Why does the screenshot say `QSynth2` while the version in MacPorts
(0.5.7) says `QSynth1` for me? You mention WINE, are you in fact running
an MSWin version of QSynth under that emulator?
No, I'm definitely using the MacPorts version of Qsynth. It's just that
Qsynth lets you run more than one synth engine. On Linux, I have Qsynth1
set up with a Microsoft GS replica soundfont, and Qsynth2 is set up with
that extracted soundfont. I thought that maybe using the soundfont on a
second synth engine would make it work better, but that was quite a silly
long shot (Qsynth1 is muted and unused at the moment on macOS). I am
running TMIDI (Tom's MIDI Player) in WINE though, which I also do on Linux
(TMIDI in WINE with Linux Qsynth) because it's got the best support for
niche MIDI features like SysEx that are crucial for old Roland/Yamaha
boxes and their related emulators, plus it's very stable and doesn't have
any lag issues. I have absolutely no compatibility issues with this Linux
Qsynth/WINE TMIDI combo on Linux, so I presumed the problem to be with the
MacPorts version in particular.
> What happens if you point the fluidsynth executable itself to the
soundfont and MIDI file in question?
I wouldn't know, because I actually don't know where that would be stored.
If you could give me a file location to look in, that'd be fantastic
thanks!
> Anyway, this has to be an issue with either qsynth or fluidsynth, and
ought probably be reported upstream. And I'm sure I've said this before: I
never understood the point of qsynth, probably because the GUI isn't
intuitive to me. So TBH I am not even certain what the preset dialog is
supposed to show - the local presets or whatever is defined in the MIDI
file.
It's meant to show what the MIDI file is specifying, and the fact that
it's not means that Qsynth is ignoring it. Right now, it means that every
synth in the song that I'm playing (from Mario Kart DS) is mapped to a
lead synth, when there's also supposed to be drums, bass, piano, organs,
etc. The dialogue there is meant to illustrate that Linux shows them all
mapped correctly, with their corresponding program change numbers as
defined by the MIDI, but the MacPorts version does not.
I also wasn't sure if I should report it upstream, given that the MacPorts
version is, just that, a port, a community-maintained project and probably
not supported by the Qsynth dev(s). But if it is, and they're willing to
listen, then I might shoot them a message about it as well. But I thought
it better safe than sorry to leave a ticket here first just in case.
--
Ticket URL: <https://trac.macports.org/ticket/71006#comment:4>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list