Rhapsody
A plugin and standalone application for launching your Libre Wave instruments.
Download for your OS
Linux
Version 1.1.0
MacOS
Version 1.1.0
Windows
Version 1.1.0
Installation
Once the download completes just double click the installer to install Rhapsody.
If you’re on Linux there is no installer. Just extract the compressed files to your preferred location.
Minimum Requirements
OS: Debian 9+, Windows 7+, MacOS 10.14+
Disk Space: 100MB
RAM: 2GB
Plugin host that supports VST3 or AU
AAX (Pro Tools) is not supported
CPU: Intel/AMD/Apple Silicon
Install new libraries in 3 steps
1. Launch Rhapsody and click the plus button below the library column.
2. Select one of the Libre Wave instrument archives you’ve downloaded.
3. Choose a location to install the samples and click install.
FAQ
As a VI user myself I understand the frustration.
Wouldn’t it be nice if all developers could use a single sampler plugin so we didn’t need to have all these different “players”?
The problem with a single player is it is controlled by a single entity. Kontakt by NI, Falcon by UVI, Halion by Steinberg, etc. and they are all closed source.
This greatly restricts what VI developers are able to do. We have no ability to innovate beyond the bounds of the host player. We are at the mercy of the player’s “owners” to decide which features will be added, which bugs will be fixed, which operating systems will be supported, etc.
Rhapsody is open source and built with HISE which is also open source. So anyone can make a VI in HISE that will load in Rhapsody if they wanted to.
In my opinion the closest thing we have to an ideal VI format is SFZ. SFZ files can be loaded into any compatible player and anyone is free to make their own player that follows the standard.
The problem with SFZ currently is it doesn’t have a scripting language. This prevents us being able to create libraries with innovative features like polyphonic legato, strumming, chord detection, realistic portamento, etc.
However if the day arrives that SFZ is able to overcome these limitations then I would definitely consider using that format.
Wouldn’t it be nice if all developers could use a single sampler plugin so we didn’t need to have all these different “players”?
The problem with a single player is it is controlled by a single entity. Kontakt by NI, Falcon by UVI, Halion by Steinberg, etc. and they are all closed source.
This greatly restricts what VI developers are able to do. We have no ability to innovate beyond the bounds of the host player. We are at the mercy of the player’s “owners” to decide which features will be added, which bugs will be fixed, which operating systems will be supported, etc.
Rhapsody is open source and built with HISE which is also open source. So anyone can make a VI in HISE that will load in Rhapsody if they wanted to.
In my opinion the closest thing we have to an ideal VI format is SFZ. SFZ files can be loaded into any compatible player and anyone is free to make their own player that follows the standard.
The problem with SFZ currently is it doesn’t have a scripting language. This prevents us being able to create libraries with innovative features like polyphonic legato, strumming, chord detection, realistic portamento, etc.
However if the day arrives that SFZ is able to overcome these limitations then I would definitely consider using that format.
The Libre Wave website is the only official source of Rhapsody instruments.
Once you’ve made your purchase you will find download links available under the library tab of the My Account page.
Once you’ve made your purchase you will find download links available under the library tab of the My Account page.
An active license key is required to download your purchased instruments from Libre Wave.
If you deactivate your license or transfer it to someone else you will no longer have access to those files.
The license key is not needed inside Rhapsody itself and there is no form of DRM.
If you deactivate your license or transfer it to someone else you will no longer have access to those files.
The license key is not needed inside Rhapsody itself and there is no form of DRM.
Yes, Rhapsody will run in FL Studio. If you notice an issue please file a support ticket.
No and it probably never will. The AVID SDK and DRM is not compatible with Rhapsody’s software license.
It is still possible to use Rhapsody with Pro Tools by running the plugin in an external host.
It is still possible to use Rhapsody with Pro Tools by running the plugin in an external host.
Yes. Rhapsody is released under the GNU GPL. You can find a link to the git repository in the website footer.
The Rhapsody name is a registered trademark. If you fork Rhapsody for your own derivative work you will need to give it a new name and logo.
The Rhapsody name is a registered trademark. If you fork Rhapsody for your own derivative work you will need to give it a new name and logo.
When an instrument update is available an email will be sent to your registered email address to notify you.
You can then login to your account, download the latest files, and install them via Rhapsody’s standard installation process.
Rhapsody does not currently include a built in updater. In fact it doesn’t connect to the internet for any purpose.
I may add an optional update notifier in the future if this is something users desire.
You can then login to your account, download the latest files, and install them via Rhapsody’s standard installation process.
Rhapsody does not currently include a built in updater. In fact it doesn’t connect to the internet for any purpose.
I may add an optional update notifier in the future if this is something users desire.
There are a few things I’d like to improve but as far as I’m aware there are no show stoppers.
The transpose controls don’t affect the visual playable range of the keyboard.
The factory presets can be overwritten. I’d like them to be read-only so that updates don’t overwrite your changes.
If any more are brought to my attention I’ll add them here.
The transpose controls don’t affect the visual playable range of the keyboard.
The factory presets can be overwritten. I’d like them to be read-only so that updates don’t overwrite your changes.
If any more are brought to my attention I’ll add them here.