If the software is failing to verify its serial number due to folder permission problems, it may be due to a recent OS update, which could have corrupted the folder permissions. Bliss, Discovery Pro, Discovery, or Corona check the serial on the server but do not verify whether the target folder is writable, preventing the software from writing the necessary license key file into the proper folder.

Steps to Resolve

Follow these steps to fix the folder permissions and ensure proper activation:

1. Open Finder: Navigate to the Documents > discoDSP folder on your system.
2. Adjust Folder Permissions:
   • Select the folder and press Command+I to bring up the folder information window.
   • Scroll to the bottom where you see the permissions section.
   • Click the "+" button to add your username to the list of users with access to the folder. Your username should appear followed by "(Me)."
3. Apply Changes to Enclosed Items:
   • Click the "..." button next to the permissions section to apply the changes to all files and folders inside the discoDSP folder.
4. Activate Again:
   • Launch the standalone app and complete the activation process.
   • Verify that a license key file has been created in the config folder.
   • If you continue to experience issues after following these steps, please contact our support team for further assistance.

If you are having trouble with Bliss, Corona, Discovery, Discovery Pro or OB-Xd and seeing a file missing or getting a license invalid error, one possible solution to this issue could be to disable iCloud Documents. This is because it might be interfering with the software's ability to access the necessary files.

Additionally, we recommend checking if there are any files existing at the user's "Documents > discoDSP > Corona / Bliss / Discovery / Discovery Pro / OB-Xd" folders. If the folder is empty or doesn't exist, it could be the reason why the software is not able to locate the assets or the license file.

It's also worth checking that Logic Pro or the DAW app has access to the "Documents" folder under Security settings on your Mac. This can be done by going to System Preferences > Security & Privacy > Privacy, then select the "Files and Folders" tab, and look for the "Logic Pro" or DAW application in the list of apps. Make sure it has permission to access the "Documents" folder.

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 and UVI Workstation. These plugins interfere with the resampling process in Bliss, resulting in truncated notes.

Solution

The solution to this issue is to use a bridge such as DDMF Metasynth to load Kontakt. A bridge acts as a middleman between Bliss and the soundbank, bypassing the offline sampling protection and allowing for a successful resampling process.

How to use DDMF Metasynth

1. Visit the DDMF website and download the free demo of DDMF Metasynth.
2. Install DDMF Metasynth on your computer.
3. Load Kontakt through DDMF Metasynth instead of loading it directly into Bliss.
4. Try resampling the soundbank again. The truncated notes should no longer be a problem.

Conclusion

By using DDMF Metasynth as a bridge, you can successfully resample soundbanks with Bliss, even if they were previously truncated. Give it a try and let us know if it works for you. 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.