[MacPorts] #67181: solfege: Alternative for qtplay
MacPorts
noreply at macports.org
Tue Apr 4 00:46:17 UTC 2023
#67181: solfege: Alternative for qtplay
-------------------------+----------------------
Reporter: ryandesign | Owner: (none)
Type: defect | Status: assigned
Priority: Normal | Milestone:
Component: ports | Version:
Resolution: | Keywords:
Port: solfege |
-------------------------+----------------------
Comment (by ryandesign):
The upstream solfege project doesn't use qtplay, but it does need ''some''
program to play audio files, and it has a configuration file where you
specify which program to use for different types of files. The solfege
port contains a patch that modifies the config file to use qtplay for all
the file types that it can.
/usr/bin/afplay exists on Mac OS X 10.5 and later, based on what I could
find, so we could have the solfege port use that instead of qtplay on 10.5
and later, except that the port currently configures solfege to use qtplay
for MIDI files and afplay doesn't support MIDI files. I don't know how
important it is that solfege be able to play MIDI files. If it is, we need
another solution for that. FluidSynth is in MacPorts and seems to be able
to play a sample MIDI file but even with the `-q` flag it prints useless
output to the terminal that might be annoying. Timidity is another option
that might be suitable (it's what the config file was set up for before we
patched it) but it's not in MacPorts yet; see #51842.
--
Ticket URL: <https://trac.macports.org/ticket/67181#comment:2>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list