Demo versions are restricted to non-commercial use only. Registered products have no commercial usage limitations.

Most products now include built-in registration and update checking. Simply register your demo and check for updates directly from the plugin menu to get downloads instantly. You can also download updates from any product page or check your licenses and activations in your Members Area.

Each purchase includes 2 years of standard support from the date of purchase. Beyond this period, support availability for current active versions depends on the nature of your request and version status until end of life.

For end-of-life products, support and downloads have ended. However, all existing license activations remain active and functional. If you weren't able to download an EOL product before support ended, you can request temporary download links by submitting a request via our contact form.

License transfers are available for a one-time fee of $29 and can only be performed once per license. To initiate a license transfer, please contact our support team, and we'll guide you through the process.

Each license allows activation on up to three computers owned by the same license holder. This supports our macOS, Windows, and Linux builds.

All minor updates (e.g., v1.0 to v1.x) are provided free of charge. Major version releases (e.g., v1.0 to v2.0) may require a paid upgrade. Upgrade pricing is only available to eligible customers within a time window from the new version release.

Our products use serial number authentication with one-time internet verification during activation. After that, your license is stored locally on your computer as a .key file in your Documents > discoDSP > Product name folder (or ~/Library/Application Support/discoDSP/ on macOS), and tied to your main hardware ID (CPU/motherboard), not to accessories or hard disks. This means the software works completely offline after activation, you can backup and restore your license file without reactivating, your license survives system backups and restores, and there are no constant internet checks or tracking.

First Solution

Try rebooting your computer. This can often resolve any software conflicts or issues that may be preventing your plugins from appearing in Logic Pro.

Second Solution

Open Terminal and use the command:

sudo killall -9 AudioComponentRegistrar

This command will force quit the AudioComponentRegistrar process, which is responsible for managing audio units in macOS. Killing the AudioComponentRegistrar process is a temporary solution used to avoid the need for a reboot. It should not have any significant impact on the system. However, it's always recommended to reboot and avoid force quitting system processes.

Third Solution

1. In Finder, go to Go > Go to Folder in the menu bar at the top.
2. Copy-paste the following path and click Go: ~/Library/Caches
3. Delete any folder named AudioUnitCache.
4. Delete any file named com.apple.audiounits.cache.
5. Reboot the system.

Fourth Solution

1. In Finder, go to Go > Go to Folder in the menu bar at the top.
2. Copy-paste the following path and click Go: ~/Library/
3. After opening the library, navigate to the locations listed below and move the specified files to the Trash:
   • ~/Library/Caches/com.apple.logic10/ (Files: Cache.db, Cache.db-shm, Cache.db-wal)
   • ~/Library/Preferences/ (File: com.apple.logic.pro.cs)
   • ~/Library/Preferences/ (File: com.apple.logic10.plist)
4. Once the files are moved, empty the Trash.
5. Finally, restart your Mac for the changes to take effect.

Note: Ensure you're logged in as an Admin account to perform these steps, or you might not have the necessary permissions.

In some cases, the document folder path may not be set properly on your Linux distribution, which could cause the GUI not to load or LUA scripts to fail to import files in Bliss.

Problem

The application needs to access files in your Documents folder via $(xdg-user-dir DOCUMENTS) but the xdg-utils package might not be installed on your system.

Solution

Install the xdg-utils package using your distribution's package manager:

sudo apt install xdg-utils

After installing, you can verify the Documents path is correctly detected by running:

xdg-user-dir DOCUMENTS

If you still encounter issues, you may need to set the path manually by editing ~/.config/user-dirs.dirs and adding:

XDG_DOCUMENTS_DIR="$HOME/Documents"

After saving the changes, log out and log back in to apply them.

Conclusion

Installing xdg-utils is the simplest solution for most Linux users. This package provides the standard tools needed for applications to locate your Documents folder correctly.

If you've tried to resample soundbanks with Bliss and found that some notes appear truncated or incorrectly rendered, you're not alone. Many users have reported this issue while trying to resample plugins like Kontakt, UVI Workstation or Cherry Audio. In this article, we'll explore the cause of this problem and provide a solution to resolve it.

Cause of the Problem

The cause of the truncated notes issue lies in some kind of offline sampling protection implemented by Kontakt, UVI Workstation, and other virtual instruments. These plugins interfere with the resampling process in Bliss plugin versions, resulting in truncated notes.

Solution

The Bliss standalone application now includes automatic hardware sampling capabilities. You can route audio and MIDI virtually on your system to sample from any hardware synth or DAW running virtual instruments, effectively bypassing offline sampling protection.

macOS Setup

Bliss standalone on macOS includes a built-in virtual MIDI output port. For virtual audio routing, use BlackHole, a free open-source virtual audio driver:

1. Download and install BlackHole from https://existential.audio/blackhole/
2. In your DAW, set BlackHole as the audio output device
3. In Bliss standalone, set BlackHole as the audio input device
4. Use Bliss's built-in virtual MIDI output to send MIDI to your DAW's virtual instrument
5. Start the automatic sampling process in Bliss standalone

Windows Setup

For Windows, you'll need both virtual MIDI and virtual audio cable software to route between Bliss standalone and your DAW:

Virtual MIDI (free options):

• loopMIDI by Tobias Erichsen - Creates virtual loopback MIDI ports
• LoopBe1 by Nerds.de - Free for personal use, supports up to 8 applications

Virtual Audio (free options):

• VB-Audio Virtual Cable - Free virtual audio cable
• VoiceMeeter by VB-Audio - Free virtual audio mixer with routing capabilities

1. Download and install loopMIDI and VB-Audio Virtual Cable (or VoiceMeeter)
2. Create a virtual MIDI port in loopMIDI
3. In your DAW, set VB-Cable as the audio output and the loopMIDI port as MIDI input
4. In Bliss standalone, set VB-Cable as audio input and loopMIDI as MIDI output
5. Start the automatic sampling process in Bliss standalone

Alternative: You can also use a physical external audio interface with two computers - one running your DAW with the protected virtual instruments, and another running Bliss standalone, connected via audio and MIDI cables.

Conclusion

Using Bliss standalone with virtual routing effectively bypasses offline sampling protection and offers the most flexibility. If you're still facing issues, feel free to reach out to us for further assistance.

If you are having trouble using SoundFont2 files in the Wave oscillator of your Discovery Pro, Corona or Bliss plug-ins, there may be an issue with the format of the SF2 file. Some SF2 files may contain multiple programs within them, which can cause the software to not recognize or use the file correctly.

To resolve this issue, you can use a SF2 editor to extract the desired program from the SF2 file and save it as a single program. This will allow the Discovery Pro software to recognize and use the program correctly.

One popular SF2 editor we recommend is Polyphone. It is a free and open-source software that allows you to edit, create, and convert SoundFont files. You can download it from their website at https://www.polyphone-soundfonts.com

Here are the steps you can take to use Polyphone and fix the issue with your SF2 files:

1. Download and install Polyphone from https://www.polyphone-soundfonts.com
2. Open the SF2 file that you wish to use in Polyphone.
3. In the "Presets" tab, select the program you wish to use and right-click it.
4. Select "Export Soundfonts" from the context menu.
5. Save the new SF2 file that contains only the desired program.
6. Place the SF2 into Documents > discoDSP > Discovery Pro > Waves or Documents > discoDSP > Corona > Waves > folder.
7. In Discovery Pro, go to the Wave oscillator and select the newly created SF2 file. In Corona, use the oscillator drop down menu.
8. The program should now be recognized and usable.

Additionally, on step 5, you can also export as SFZ and import the WAV files instead of dropping them into the GUI. They will be copied to Waves > User.dwb folder.

If you have any other questions or if there is anything else we can assist you with, please reach out to the support team.

Installing discoDSP plugins on Debian-based Linux systems is straightforward using the provided .deb package. The installation automatically sets up the standalone application and plugins for use in your DAW.

Installation

Install the package using your package manager or the command line:

sudo dpkg -i ProductNameLinux.deb

sudo apt-get install -f # Fix any dependency issues

The package installs all files to /opt/productname/ and creates a terminal shortcut for easy access.

What Gets Installed

The installation includes:

1. Standalone application in /opt/productname/
2. VST2 plugin (.so file) in /opt/productname/
3. VST3 plugin (.vst3 folder) in /opt/productname/
4. Desktop menu entry for launching the standalone
5. Terminal command symlink in /usr/local/bin/

You'll need to configure your DAW to scan /opt/productname/ for plugins.

Using Your Plugins

Standalone Application

Launch the standalone application from your application menu or by running:

productname

For example: highlife, obxd, corona, vertigo, etc.

In Your DAW

To use the plugins in your DAW:

1. Add /opt/productname/ to your DAW's VST2/VST3 scan paths
2. Rescan for plugins in your DAW
3. The plugins should now appear in your plugin list

Troubleshooting

DAW Doesn't Detect Plugins

If your DAW doesn't detect the plugins:

1. Verify the plugins are installed: ls /opt/productname/
2. Add /opt/productname/ to your DAW's VST plugin search paths
3. Check that your DAW supports VST2 (.so) or VST3 (.vst3) format
4. Manually rescan plugins in your DAW settings

Uninstallation

To remove the package:

sudo apt-get remove productname

This removes all system files from /opt/productname/ and the terminal symlink. User presets in ~/Documents/discoDSP/ are preserved.