It would be nice if munt could read the
midi data from stdin and output the PCM
sound to stdout. Currently this doesn't seem
to be supported.
The is a simple replacement for the C library
API, which doesn't compile at the moment
AFAIK.
This way seems to be a convenient usage for clients who does not require any special features. All the synth engine variables that may be changed through the library API seem to only be configured at the startup by providing a command line options.
However, this kind of setup should already be possible with mt32emu-qt. It features both OSS MIDI-IN interface (which can be a FIFO) and RAW audio file writer (which can also be a FIFO). Available command-line option -profile allows to specify a customised set of synth engine settings. Although, OSS MIDI handler is currently provided for UNIX-like platforms only.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
OK, thanks for explanation.
As the C interface now compiles fine,
I do no longer need this functionality.
Still I would note that:
1. qt frontend is not what I was asking for. I needed a GUI-less mode for this.
2. OSS midi-in probably stands for OSS sequencer protocol, which is not for the
raw midi stream. It accepts either midi events in an oss-specific format with
imestamps, or raw midi bytes, each prepended by OSS-specific byte that indicates
that the raw midi byte follows. So while it can be used, it would require additional
data stream mangling.
Currently I use mt32emu_parse_stream_at() for raw midi stream.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
At the moment, mt32emu-qt is not a frontend but a UI-enabled synth application. I'm already considering switching to core/CLI/GUI design for that stuff but it will anyway be based on Qt.
FYI, OSS MIDI these days implies access to exactly raw MIDI ports bypassing sequencer stuff. The OSS MIDI driver included in mt32emu-qt supports both, though support for old OSS 3 sequencer is very limited.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This way seems to be a convenient usage for clients who does not require any special features. All the synth engine variables that may be changed through the library API seem to only be configured at the startup by providing a command line options.
However, this kind of setup should already be possible with mt32emu-qt. It features both OSS MIDI-IN interface (which can be a FIFO) and RAW audio file writer (which can also be a FIFO). Available command-line option -profile allows to specify a customised set of synth engine settings. Although, OSS MIDI handler is currently provided for UNIX-like platforms only.
OK, thanks for explanation.
As the C interface now compiles fine,
I do no longer need this functionality.
Still I would note that:
1. qt frontend is not what I was asking for. I needed a GUI-less mode for this.
2. OSS midi-in probably stands for OSS sequencer protocol, which is not for the
raw midi stream. It accepts either midi events in an oss-specific format with
imestamps, or raw midi bytes, each prepended by OSS-specific byte that indicates
that the raw midi byte follows. So while it can be used, it would require additional
data stream mangling.
Currently I use mt32emu_parse_stream_at() for raw midi stream.
At the moment, mt32emu-qt is not a frontend but a UI-enabled synth application. I'm already considering switching to core/CLI/GUI design for that stuff but it will anyway be based on Qt.
FYI, OSS MIDI these days implies access to exactly raw MIDI ports bypassing sequencer stuff. The OSS MIDI driver included in mt32emu-qt supports both, though support for old OSS 3 sequencer is very limited.