Source-to-Image
7.2#2 in sampler softwareFree planFree planLinuxmacOSSelf-hostedWindows
VisitSource-to-Image vs Subsample
What both publish
| Fact | Source-to-Image | Subsample |
|---|---|---|
| Integrations | The README documents use with Docker and gives examples using OpenShift, UBI, Ruby, and WildFly images. | It supports standard and virtual MIDI input, OSC sender and receiver, and MIDI control including Program Change and CC bindings. |
| License | The repository is released under the Apache License 2.0. | Subsample is released under AGPLv3, which requires modified versions used as network services to make source code available to users. |
| Platforms | Installation instructions cover Linux, Mac, and 64-bit Windows releases. | It runs on Linux and macOS; Windows support is through WSL2 and native Windows is not tested. |
| Purpose | Source-to-Image is a toolkit and workflow for building reproducible container images from source code. | Subsample cuts separate sounds from live input or recordings, sorts them by sound, and plays them from MIDI. |
Source-to-Image plans
- Source-to-ImageFree
Subsample plans
- Subsample (AGPLv3)Free
Pick Source-to-Image if…
S2I suits developers who want a repeatable way to turn source into runnable container images, including workflows that build from Git without a Dockerfile. Teams can also use its builder-image scripts and supported incremental builds to customize that process.
Pick Subsample if…
Subsample suits musicians and audio users comfortable configuring a terminal-based sampler. It may be useful for workflows that need automatic sample mapping and multichannel routing.