Check that the plugin is looking for the samples in the right location. You can do this in the Engine tab of the plugin’s settings screen. If the location is wrong you can redirect the plugin by clicking the Change sample folder location button.
The first time you launched the plugin you should have been prompted to either install the samples or locate them on your system. If you chose to locate rather than install the plugin will not function correctly. You’ll need to remove the plugin’s configuration files, relaunch the plugin, and the prompt to install the samples will reappear.
You can choose to scale the GUI up or down in the Engine section of the settings screen.
Hanging notes
If you find a situation that triggers hanging notes there is probably a sneaky bug in the script which I have missed. Legato scripting is the place where such bugs are often found hiding and I would not be surprised if some edge cases bring them to the surface.
Please create a MIDI file, as short and simple as possible, that consistently triggers the hanging notes. Send this to me attached to a support ticket along with other useful information such as the name of the plugin, the plugin version, the DAW you’re using, your operating system, the OS version, if possible a small mp3 file that demonstrates the issue, and anything else you think is relevant.
The download links you receive allow you to attempt the download 10 times before they expire. If you need to re-download your order after the links have expired you will need to open a support ticket. I cannot re-issue download links for products that are no longer for sale on this website so please make your own back-up copy.
If you’d like to build my software from source you’ll first need to build HISE which is the development environment I use to create my software. The HISE GitHub page has instructions for how to build it on different operating systems so please follow those. I recommend you use my fork of HISE rather than the upstream as I have made some modifications.
Building HISE from source rather than using the prebuilt binaries serves two purposes. Firstly it ensures that you are using the most recent version of HISE. Secondly it guarantees that you have the correct environment setup to build my software.
If you need assistance with building HISE please ask on the HISE forum.
Getting the source code
At the moment my source code is a little fragmented as I’m transferring from GitHub to Codeberg. You can find my GitHub repo here here and my Codeberg repo here.
For Rhapsody instruments you will need to download the necessary code from both repos.
You can download the source code as a zip file by clicking the Clone or Download button and selecting Download Zip. Once downloaded you should extract the zip file, which contains the HISE project folder for the product. Alternatively, if you are familiar with git, you can clone the repository and make a local git repo on your system for the product’s HISE project folder.
The GitHub repositories contain only the source code, they do not include any audio samples.
My HISE scripting framework
Downloading from GitHub
My scripting framework is an ever changing collection of script libraries, modules, and other stuff that I use across most of my HISE projects. In order to build any of my projects you will need the correct version of the framework for that particular project added to the project’s scripts folder. It’s very important that you use the correct framework version for the project you wish to build as the code in the framework varies between projects and a different version may not be compatible.
If you setup the project folder by downloading the source code zip file from GitHub you will need to go back to the GitHub page. Once there go into the Scripts folder, then into the HISE-Scripting-Framework folder (the folder name will also contain an @ symbol and some numbers), this will take you to the correct version of the framework for that project. Download the framework as a zip file the same way you downloaded the source code. Once downloaded open the zip file, inside will be a single folder with the same name as the framework folder on GitHub, take the contents of this folder and place it inside the /Scripts/HISE-Scripting-Framework/ folder inside the project folder.
If you cloned the project folder as a local git repository then all you need to do is import the framework as a git sub-module inside the project’s Scripts folder.
Opening the project
HISE’s File Menu
In HISE go to the File menu, click Load Project, and point the file browser that opens to the source code folder you downloaded earlier. Click ok when HISE asks if you would like to load the project’s .xml file. If HISE doesn’t prompt you to load the .xml file you can do it manually by opening the File menu, clicking Open XML, and then selecting the .xml file in the project’s XmlPresetBackups folder.
Preferences
In HISE go to the File menu and select Preferences. Scroll down to the Compiler Settings section and click the browse button in the HISE Path field. A file browser will appear, use this to select the folder on your computer that contains the HISE source code. Alternatively you can enter the path manually into the HISE path field. This path should point to the HISE source code, not the source code of the Libre Wave project you want to build.
Compiler settings
In the Compiler Settings section you can also select the version of Visual Studio you will be using to compile the project if you are using Windows.
Export
HISE’s Export Menu
Go to the Export menu and select an export option; for virtual instruments select either Export as Instrument (VSTi / AUi) plugin or Export as Standalone Application, for effects select Export as FX plugin. Click Cancel if HISE prompts you to check sample references, then select the export format from the drop-down menu that appears. The choice of export formats will vary depending on your operating system. Click ok on any further prompts that appear.
GNU/Linux
After a moment HISE will generate a build file and open the project’s Binaries directory. Open a terminal, cd to the Binaries folder and run the batchCompileLinux.sh file in that folder. This will start the build process and once complete the exported files will be placed in the following directories:
HISE will automatically generate the build files, a terminal window will pop-up, and the compilation process will start. Once the compilation is complete the output files will be placed in the following directories:
I don’t want my software to take away your freedom so unless otherwise stated all Libre Wave software is released under the GPLv3 license and all audio samples are released under a Creative Commons Plus license. The complete license document combining the GPL, Creative Commons, and CC+ license is available here.
Why not release the samples under the GPL too?
The GPL license is intended for software and one of its requirements is that the user must have access to the software’s source code. Samples are audio files and don’t provide anything that is equivalent to source code, so the GPL is not really appropriate for samples. In addition to this the GPL requires all derivative works to be released under the same license, so providing GPL samples would require users to release their compositions under the GPL too.
Once your order status has changed to completed your download links will be activated. You’ll receive an email containing the links and they’ll also be available from your account dashboard.
If you don’t see the email in your inbox please check your junk mail and spam mail folders and make sure the librewave.com domain is on your spam filter’s white-list.
If you don’t see your download links in either your account or your email please open a support ticket.
If you’re unable to access your account then please contact me and provide your order details. It’s also important that you provide at least one alternative email address or other method by which I can contact you – because if you haven’t received your order email then it’s unlikely you’ll be able to receive any other emails from me at the email address you used when you placed your order.
If you’ve purchased a product the best way to contact me is by opening a support ticket.
If you emailed me using the contact form on this website then you can be almost 100% sure that I have received the message. If it’s been more than a few days since you sent your message it’s possible that my response has gone to your junk mail folder or when you contacted me there was a typo in your email address and my reply is lost in cyberspace.
The first thing to do is check the junk mail or spam folder of your web-mail host (or desktop client if you use one). If you find my reply there you can move it to your inbox and add librewave.com to your safe senders white list.
If there is no reply from me in your junk mail folder then send me another message through the contact form making sure your email address is entered correctly. It would also be good to include an alternative contact method in your message so that I have more ways of responding to you and ensuring my reply reaches you.
Before you contact me for support please check the Knowledge base to see if your question has already been answered.
Support is only provided for verified purchases from Libre Wave or affiliated resellers. If your purchase was made through this website you should open a support ticket.
If you purchased through an affiliated reseller please use the contact form and include your order ID or transaction reference so that your purchase can be verified.
I usually respond to support requests pretty quickly (within hours) but sometimes it can take me a little longer. Don’t forget to check your junk/spam email folder in case my reply has got lost on the way to you.
If there is a problem with the contact form you can email directly: support@librewave.com.
