LinuxSampler vs Source-to-Image
LinuxSampler
linuxsampler.orgSource-to-Image
github.comSide by side
| Figure | LinuxSampler | Source-to-Image |
|---|---|---|
| Price from | Free | Free |
| Free plan | Yes | Yes |
| Free trial | — | — |
| Open source | — | Yes |
| Windows | Yes | Yes |
| macOS | Yes | Yes |
| Linux | Yes | Yes |
| API | Yes | — |
| Self-hosted | Yes | Yes |
| Plans published | 1 | 1 |
| Spec score · Sampler Software | 8.1 (#7) | 8.2 (#6) |
| Purpose | LinuxSampler is a free, streaming-capable open-source software audio sampler designed for high stability, efficiency, very low latency and professional-grade features. | Source-to-Image is a toolkit and workflow for building reproducible container images from source code. |
Plans
In their own words
LinuxSampler
LinuxSampler is free, open-source audio sampler software for loading and playing sampled instruments. Its engine runs as a separate backend process from its user interfaces, and the project describes it as streaming-capable. It supports GigaStudio/GigaSampler, SoundFont, and SFZ formats, and can run on Linux, Windows, and Mac OS X. Users can operate it standalone or as a plugin in sequencers and DAWs including Cubase, Logic, Ardour, QTractor, and Reaper.
Supported plugin formats include VSTi, Audio Units, DSSI, and LV2. Listed audio and MIDI drivers include ALSA, JACK, CoreMIDI, MidiShare, MME, ASIO, CoreAudio, and audio over Ethernet. The engine can be controlled through a native C++ API or LSCP, an ASCII network interface; frontends can also connect remotely. Gigedit can create and edit GigaStudio/Gigasampler instruments, with changes audible during playback. QSampler lacks some engine features, including instruments-database support, while JSampler supports all currently available engine features. Commercial use of the source, libraries, or applications in hardware or software requires prior written authorization.
Source-to-Image
Source-to-Image is a free, Apache-2.0 toolkit for building reproducible container images from source code. It places source in a builder image, lets that container prepare the application, and outputs a ready-to-run image. A documented workflow can build from a Git repository without a Dockerfile. Builder images may provide assemble and run scripts, plus optional scripts for saving artifacts and explaining usage. Compatible builders can reuse artifacts from an earlier output when incremental settings and scripts are supplied. A .s2iignore file filters source files and directories, while .s2i/environment defines build variables that also appear in the output image. S2I can use an OnBuild strategy with images containing Dockerfile ONBUILD instructions. Examples cover Docker, OpenShift, UBI, Ruby, and WildFly. It runs on Linux, macOS, and Windows, with Docker 1.6+ and Go 1.7.1+ listed as dependencies.