samplv1 vs Source-to-Image
samplv1
samplv1.sourceforge.ioSource-to-Image
github.comSide by side
| Figure | samplv1 | Source-to-Image |
|---|---|---|
| Price from | Free | Free |
| Free plan | Yes | Yes |
| Free trial | — | — |
| Open source | — | Yes |
| Windows | — | Yes |
| macOS | — | Yes |
| Linux | Yes | Yes |
| Self-hosted | — | Yes |
| Plans published | 1 | 1 |
| Spec score · Sampler Software | 7.3 (#20) | 8.2 (#6) |
| License | The project describes the software as free and open source under GNU GPL version 2 or later. | The repository is released under the Apache License 2.0. |
Plans
In their own words
samplv1
samplv1 is a free, open-source, all-digital polyphonic sampler synthesizer for Linux with stereo effects. It runs as a standalone JACK client with JACK-session and NSM session management, accepting MIDI through JACK MIDI or ALSA MIDI. It is also available as an LV2 instrument plugin. The project is licensed under GNU GPL version 2 or later, and its listed free plan costs nothing. The home page lists version 1.5.0, released September 15, 2026, with a package for factory and community presets and updated theme options. Qt and libsndfile are required to build and run it. JACK, ALSA, LV2, FFTW3, Rubber Band, and liblo are optional build components; liblo is needed for NSM support. CMake instructions cover building from the source tarball, using /usr/local by default. User settings are stored in $HOME/.config/rncbc.org/samplv1.conf. The project says bugs remain but considers the software production and stable. Development matters go through its SourceForge project page.
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.