Open jpcima opened 5 years ago
Added a README document which lists current key shortcus.
@Wohlstand a key F2
was added to choose a MIDI port from a dynamic list
for the readme, on latest linux mint, libuv-dev is not present, it seems it's "libuv1-dev" instead
This appears correct thanks, just checked. Not only this, there was the icu requirement recently that was replaced by glib, yet icu has never been mentioned.
Some synthesizers require a ROM or SoundFont to be provided, and specified in the configuration.
How do I provide and specify soundfonts and which formats are supported by each plugin?
; Path of directory opened initially
initial-path =
; Selected device for MIDI output
midi-out-device =
; Selected device for synthesis
synth-device = Fluidsynth
; Sample rate of synthesized audio stream (Hz) [22050:192000]
synth-sample-rate = 44800.000000
; Latency of synthesized audio stream (ms) [1:500]
synth-audio-latency = 50.000000
; Theme of the graphical interface
theme = default
; Force software rendering in case of graphical problems
force-software-renderer = false
; Scale factor of the display
scale-factor = 1
[effects]
Bass Enhance = 0
Bass amount = 50
Bass tone = 50
EQ = 0
EQ Low = 50
EQ Mid-Low = 50
EQ Mid = 50
EQ Mid-High = 50
EQ High = 50
Reverb = 0
Reverb amount = 50
Reverb size = 10
Not seeing plugin soundfont options in the config.
The synth plugins have their own ini files, starting with s
letter.
For instance, fluidsynth is s_fluid.ini
, etc.
More precisely, timidity++ and fluidsynth accept SF2 soundfont files. mt32emu wants the ROMs of Roland MT-32.
adlmidi and opnmidi accept WOPL and WOPN files. See also https://github.com/Wohlstand/OPL3BankEditor https://github.com/Wohlstand/OPN2BankEditor
The synth plugins have their own ini files, starting with s letter.
Good to know. Probably belongs to documentation. Perhaps to the GUI as well…
No DLS soundfont support?
Timidity++ definitely doesn't, Fluidsynth might support it, I've never checked it.
Write documentation on controlling the software. Provide a key description in the software, and also figure out correct usage of keyboard layout with SDL. (currently scancodes are used)