@pkw
somehow I've just looked at your #fluidsynth + #midi / #midi #cffi #lisp stuff. Thank you for doing this!
https://codeberg.org/pkw/midi9000
https://codeberg.org/pkw/midi-synth
#openBSD #C #CommonLisp #musicproduction
@pkw
somehow I've just looked at your #fluidsynth + #midi / #midi #cffi #lisp stuff. Thank you for doing this!
https://codeberg.org/pkw/midi9000
https://codeberg.org/pkw/midi-synth
#openBSD #C #CommonLisp #musicproduction
The built-in virtual keyboard in Ardour replaces 4 Linux applications.
#VMPK is Virtual MIDI Piano Keyboard is a MIDI events generator and receiver. VMPK uses the modern Qt5 framework.
#Qsynth is a #fluidsynth GUI front-end application written in C++ around the Qt framework using Qt Designer.
#QjackCtl is a simple Qt application to control the JACK sound server daemon.
#QJackRcd is a simple QT application to record JACK server outputs using QJackCtl.
@cymplecy @diyelectromusic @bromagosa -- I've used #FluidSynth for years and it has served me well. https://www.fluidsynth.org/
Anyway I spent the time and I got my Arturia Keystep to play MIDI through the raspberry pi using #fluidsynth!
If you zoom in you can see the exceedingly dusty raspberry pi.
Next steps are me doing research into USB audio sound cards for the pi, as well as headless control options.
I want time to think about the control options, so I don’t know when I’ll be doing another update. MIDI on pi is very idiosyncratic and confusing.
DOSBox Staging Basics
Today: FluidSynth Reverb and Chorus
Due to the introduction of mixer-level reverb and chorus effects, the FluidSynth reverb and chorus config parameters have been renamed to fsynth_reverb and fsynth_chorus, respectively.
To maintain backward compatibility with existing configurations, the FluidSynth reverb and chorus effects are enabled by default, so all your SoundFonts will sound just like in previous DOSBox versions. If you enable the mixer-level reverb (or chorus) as well (e.g. by putting reverb = on in the [mixer] section), you would get a second round of reverb (or chorus) processing on the FluidSynth output. This is by design as it allows users the greatest level of control over customising SoundFonts (e.g. some would sound best with the FluidSynth reverb only, some with both, etc.)
Note
In the SF2 format the reverb and chorus amounts are specified on a per-instrument basis, while the mixer-level effects are applied “globally” to all instruments in the summed FluidSynth output. Therefore, what works best really depends on the particular SoundFont in question and on individual user preference (see this discussion for further technical details).
DOSBox Staging Basics
Today: Audio mixer signal flow diagram
Thanks to @johnnovak!
#dosbox #dosgaming #msdos #emulation #retrogaming #linuxgaming #macgaming #foss #audio #Fluidsynth #MT32 #MT-32 #Innovation #pcspeaker #tandy #GUS #gravis #opl #opl3
DOSBox Staging Basics
Today: Configuring MIDI device
DOSBox Staging supports the following MIDI devices for music playback:
-System/Host MIDI (default)
-FluidSynth for using SoundFonts
-mt32emu/MUNT for emulating Roland MT-32, CM-32L and LAPC-I synthesizer modules.
DOS-Retro-Sound with Roland MT-32 (Part 1/3)
(german video, translation available through YouTube)
https://www.youtube.com/watch?v=cKkjSfy4mic
"Unmissable MT32 experiences" thread on Vogons.org
https://www.vogons.org/viewtopic.php?f=62&t=77567
Phils ultimate MT-32 video, running time 3,5 hours!
https://www.youtube.com/watch?v=OLvsaJ4h-VY
See our WIKI for more information and setup guides
https://github.com/dosbox-staging/dosbox-staging/wiki/MIDI
#dosbox #dosgaming #msdos #emulation #retrogaming #linuxgaming #macgaming #foss #MIDI #Fluidsynth #mt-32 #mt32 #Munt #Soundfont #philscomputerlab #vogons
Recommended #FluidSynth #MIDI soundfonts are now squeezed down to five. Every one of these should offer a good experience:
https://github.com/dosbox-staging/dosbox-staging/wiki/MIDI#soundfonts
I have several old ONScripter-EN and KiriKiri visual novels that use MIDI files for sound. I thought I had resolved my difficulties on Linux, but I had an issue where sound would work running the games under WINE but not when running the native Linux versions of ONScripter-EN games (note the KiriKiri games have no Linux version). Back into the Arch Wiki I went... I eventually resolved the issue with a proper Fluidsynth configuration and loading three kernel modules. This is the long saga (note I did this on EndeavourOS, but the issues should be generally applicable for those of you interested in the issue on Linux).
https://thenewleafjournal.com/midi-sound-for-games-on-arch-based-distro/
(Note all of these steps are in the Arch Wiki. To the extent this is a "guide" -- consider it one only in that I highlight an issue and point people to where I found the solution.)
Some fun progress today.
I got an older Raspberry Pi operational with the Bullseye version of the Raspbian OS, then successfully got #FluidSynth installed and running with a #MIDI keyboard.
Impressive sound - can certainly do something with that.
Contemplating the obvious: a standalone box to work with keyboard as a digital piano, with just on/off control req'd to work. ie no console interaction.
Surely someone else has already done that, no? Must search a bit, I guess.
My intent after upgrading my older RPi board is to install #FluidSynth which sounds like it will provide digital synth sounds for a MIDI keyboard.
Hoping this decouples a keyboard from my laptop for a more portable electric piano use around the house. Then I won't be hogging it as much.
Qsynth is a fluidsynth GUI front-end application written in C++ around the Qt framework using Qt Designer. Eventually it may evolve into a softsynth management application allowing the user to control and manage a variety of command line softsynth but for the moment it wraps the excellent FluidSynth. FluidSynth is a command line software synthesiser based on the Soundfont specification.
Tip for anyone composing in #Frescobaldi:
If you want to use MIDI input but get errors about an "invalid running status" when you attach a physical MIDI instrument, your instrument or interface may be generating SysEx messages that Frescobaldi can't understand. To work around this, you can use an app like #VMPK - in VMPK's "Connections" menu, set the input to your MIDI hardware; and in Frescobaldi's "Preferences" dialogue, set the input to VMPK. This makes your instrument change the internal state of VMPK's keyboard, and VMPK then generates appropriate MIDI events reflecting those changes. Since it's tolerant of SysEx messages in its input but won't generate them in its output, this effectively filters the stream to make it safe for Frescobaldi to consume.
As a bonus, you can see the keys light up on the VMPK interface to reflect the notes currently sounding, which may be more intuitive than reading the #Lilypond source Frescobaldi generates. If you also set something like #FluidSynth as the output in the "Connections" menu, you'll be able to hear what you're playing, too.