I know an acquaintance, whose name I will protect, who uses “
Garage Band” on his Mac, but who has a hard time imagining that there exist many, many different programs like it, for other platforms, and that there must exist such, in order for professional musicians also to have access to a great array of such tools.
Of greater relevance is the fact, that such software exists under Linux as well – not just on Macs or PCs – as well as under Android.
And there is one observation which I would like to add, about what form this takes if users and artists wish to do audio work using Free, Open-Source applications.
Typically, we can access applications that do most of the work that polished, commercial examples offer. But one area in which the free applications do lag behind, is in the availability of sample packs – aka loops – which some artists will use to construct songs.
If Linux developers were to offer those, they would probably also need to ask for money.
Garage Band has it as a specific advantage, that if such loops are simply dropped into the project, this program has the tempo stored, with which that loop was playing by default, in addition to which all DAWs have the tempo of the project set and available.
Garage Band will automatically time-stretch the loop, to adapt to the project tempo. Most of the DAW programs I know, do not do this automatically.
A common ability the open-source applications offer though, is to time-stretch the sample manually after importing it, which can be as easy as shift-clicking on one of the edges of the sample and dragging it.
In order for this to be intuitive, it is helpful if the sample has first been processed with a
Beat Slicer, so that the exact size of the rectangle will also snap into place with the timing marks on the project view, and the sample-tempo will match the project-tempo.
So what I felt I needed to do tonight, was install the
Beat Slicer named “
Shuriken“, as well as the sound-font converter / editor named “
Polyphone“, on the laptop I name ‘Klystron’.
Shuriken was a custom-compile, but
Polyphone needed to be installed as a .DEB package, which did not come from the package manager.
Shuriken has the ability to detect tempo and also chop input samples, and then to export those samples as .WAV Files in turn, or as .SFZ Sound Fonts, the latter of which might be a bit tricky to work with. The idea is that the output sound font can then be played via a MIDI sampler. But, most applications expect Sound Fonts to be .SF2 Files, not .SFZ . What I hear about that is that SFZ is good, but poorly supported. So, the application
Polyphone seemed like an important tool to add, because it allows us to open an SFZ File, and then to export the Sound Font it contains as an SF2.
When installing the
Polyphone package, some anxiety came over me, because this package is actually configured to reinstall dependencies, which are already installed. But I still felt that this was still a relatively safe thing to do, because my KDE tool for doing so will always install the dependencies from the same repositories, which they came from anyway. Yet, such a misconfiguration of the unsigned package, was a bit unsettling.
Klystron still works fully.
My reasoning for installing the ability, to turn custom recordings into loops, is the fact that under Open-Source practices, I am not buying loops, and would therefore want to be able to use custom samples as such, provided they have been formatted for this use first.
Otherwise I would have no guarantee, that the exact length of an imported sample, was a whole number of beats or bars of its music. Which in turn would make it awkward, to time-stretch the loop using the mouse.
Finally, I installed yet another DAW named “
Ardour“, which again, was a custom-compile.
The site that makes
Ardour available, asks users to donate money, in order simply to receive the binary package. Yet, because
Ardour is under the GPL, users like me may download the source code for free and then custom-compile it – a task which the paid-for version takes off the hands of users.
I configured the project with the command
./waf configure --docs --with-backends=alsa,jack ./waf su (...) ./waf install
This replaces the usual commands
./configure make su (...) make install
that I am used to.
This project-supplied, ‘
./waf‘ command actually starts a multi-threaded compile by default, on multi-core CPUs.
What I find for the moment, is that everything was a successful project.
When using Ardour, we invoke Tempo-Stretching of the Region / Sample, by clicking on the small tool icon at the top of the application window, that puts the program into “Time-Stretching Mode”, where it defaults to “Grab Mode”, and then just normally clicking on the sample in question, and optionally dragging it. Either way, a dialog box opens, which shows is the percentage already stretched by, and which allows us to enter a different percentage as a number, if we would like to.
Near the center of this thin toolbar is also a button, to set the “Snap Mode” to “Grid”.
Perhaps I should also mention, that the way I compiled it,
Ardour offers support for
DSSI plug-ins. These differ from
LADSPA plug-ins, in that the
DSSI act as instruments by default, thus receiving MIDI input and outputting sound.
To allow for their support to be compiled, only the package ‘
dssi-dev‘ really needs to be installed from the package manager, which includes the necessary header file. Source code implementing the host belongs to
Ardour, and source code implementing the instrument belongs to the plug-in. Both need to include this header file.
When adding a
DSSI plug-in to our
Ardour project, we select that we wish to add a track, and then in the ensuing dialog, we select a MIDI track, instead of an Audio track. This enables the field which allows us to select an Instrument, where by default it says ‘a-Reasonable Synth’. Instead, detected
DSSI Instruments will appear here.
Some confusion can arise, over how to get these virtual instruments to display their GUI. Within the Editor view, all we seem to see belonging to the track, is the Automation button, from which we can select parameters to be controlled by a MIDI controller.
In order to see the full GUI of the instrument, we need to click on the second button in the upper-right corner, which shows us the Mixer view. From there, each track will be shown with a possible set of plug-ins, and because we chose the instrument plug-in from the creation-time of the track, the instrument plug-in will also appear logically before any effect plug-ins. By default the instrument will be shown in a different color as well.
Here, we can double-click on the instrument plug-in widget, thus displaying the full GUI for that plug-in.
And, I did not compile my version of
Ardour, to have
Wine support, for the purpose of loading
Windows-VST plug-ins. The closest I have to that are the native
As an alternative to letting the user create a MIDI track, to be controlled with a MIDI keyboard, the application offers an Import command from the Session Menu, which displays a large dialog box, from which the user can either select an Audio File or a MIDI File, and which will again allow him to associate the MIDI File with an Instrument selection. When this has succeeded,
Ardour 5.3.0 will act as a sequencer.
However, some conflict can be expected from certain MIDI Files, which try to sequence multiple instruments…
In my limited experience, those types of MIDI Files are best Imported at the beginning, before most of the project is set up, so that they can result in multiple tracks being created, from which point on the project can be modified.
Further, because in the Mixer view the sequence in which plug-ins are applied to each track can be changed again by dragging them, it is also possible to add instrument plug-ins to each track from there, that must appear before any effect plug-ins in order to work.