|Nils 7c235268f5 Update documentation and info files||1 week ago|
|desktop||9 months ago|
|documentation||1 week ago|
|engine||1 week ago|
|qtgui||1 week ago|
|template||1 week ago|
|.gitignore||2 years ago|
|CHANGELOG||1 week ago|
|LICENSE||7 months ago|
|README.md||1 week ago|
|__main__.py||3 weeks ago|
|configure||1 week ago|
|fluajho||3 weeks ago|
Program version 1.6.2
“Fluajho” (with jh as in pleasure) means fluid in Esperanto. It is a simple sf2 soundfont host/player for Linux. Behind the scenes the Fluidsynth library is at work, hence the name.
.sf2 is an old file format for making MIDI signals audible through virtual instruments, although it is still in moderate use today.
Why does Fluajho exist? There are many soundfont players for Linux, most of them even based on Fluidsynth. Fluajho was written for a clearly defined use case: Load an .sf2 in the New Session Manager (Agordejo) and save the soundfont in the session directory. This makes it possible to archive the session, for example as a backup or to share it.
You can load one soundfont file per Fluajho instance. Each instance holds 16 of the soundfonts instruments that can be assigned to 16 MIDI channels. Finally connect external sequencers, such as Laborejo, Patroneo or Vico, through JACK-Midi to play the instruments.
This README is just a short introduction. Consult the manual (see below) for more information.
If the latest release is not available through your package manger you can build it yourself: Download the latest code release on https://www.laborejo.org/downloads and extract it.
It is possible to clone a git repository.
git clone https://git.laborejo.org/lss/fluajho.git
./configure --prefix=/usr/local make sudo make install
There are multiple ways to run Fluajho which should give you the flexibility to configure your system as you want.
We make no distinction if you installed Fluajho yourself or through the distributions package-manager.
The differences are: With or without Agordejo, with or without sound, installed or from the source dir.
Starting Fluajho through Agordejo after you installed fluajho system-wide
is the recommended and only supported way. Start agordejo and load or create a new
session. Then use the program launcher to add
It should appear with an icon in the list and open its GUI.
If you start fluajho directly it will present you with a dialog to choose your session directory.
You can also start fluajho from a terminal (or create a starter script).
fluajho --save DIRECTORY
Uses the given directory to save. The dir will be created or loaded from if already present. Use the applications file menu to save (Ctrl+s).
You can use this to load and save the files from an existing NSM session. If you create a new directory you can copy it manually to an NSM session directory, but that requires renaming the directory to append the unique ID provided by NSM.
Sending SIGUSR1 to the program in this mode will trigger a save.
Closing through your window manager in this mode will actually quit the application without a prompt to save changes.
You can run Fluajho after extracting the release archive or cloning from git, without installation.
“Calfbox” is the name of our internal realtime midi/audio python module.
make calfboxwithout subsequent install, which creates a
sitepackagesdirectory in the source dir. You can then run
./fluajhodirectly from the source.
./fluajho --mutewhich runs without sound at all and does not need calfbox.
The developer uses this way to develop and use the software, so it will always be as stable as the compiled version. But it is a bit less performant than building and installing it.
After extracting the release archive create a symlink from
fluajho into your PATH. e.g. /usr/bin
or ~/bin, if that exists on your system.
If you compiled without installing you can also symlink to
./fluajho --save (see above). If you compiled without installing you can also run
Combining the above options you can start the program directly after unpacking or cloning from git:
./fluajho --save /tmp --mute
Or even shorter:
./fluajho -s /tmp -m
This is the minimal run mode which is only useful for testing and development. But if you only want to look at the GUI and are not in the mood to install anything -including dependencies-, go ahead.