Troubleshooting & FAQ

We’ve been made aware that certain audio drivers can cause problems on Windows, even if they have not been selected as active in Sononym.

Affected drivers that we are aware of:

  • MT ASIO Bridge (compatibility driver, installed as part of e.g. Merging Pyramix)
  • Jack Audio Connection Kit

If you know that either of these drivers are installed and you don’t need them, first try uninstalling them. But if there is no uninstaller available, you can also do this manually - instructions are available on the Steinberg website: )

Note that we’ve already decided to replace the driver architecture in Sononym in order to eliminate this annoying issue.

Please get in touch with us and file a bug report - Try to explain how it happened:
if the problem is reproducible, what operating system you’re using - anything that you think might be relevant for solving the issue.


The first time you start the application, each library will be initialized - a process we call the ‘warmup’. Precisely how long this takes depends: most important factor is the amount of files and the speed of your harddrive (SSD is always preferable). Once the warmup is complete, access to libraries should remain fast.

Note: If you have an SSD drive, you might be able to speed up this initial access dramatically -
even when your samples are not actually located on that drive. Read more in this blog article.

These files are used by Sononym libraries to store collected information.
For now, we have decided that it’s better that this information is maintained as you move folders around, or share libraries on external media.

If you absolutely don’t want them around, you can either hide the files (MacOS only), or use symbolic links to offload your database files.

We are considering ways to allow manual editing/tagging, including full metadata support, but currently categories are always a reflection of what the neural network thinks.

No. Your files are left untouched - and folders too, with one exception:
Sononym libraries create a single file called ‘sononym.db’, which contain the collected data
(this file is added to the topmost folder in the library).

See also this entry for more info on sononym.db files

We are planning to increase the number of supported formats - especially open-source ones
but also proprietary instrument/sampler formats, when possible.
You can check if your particular format is supported on this page.

What you see in the sidepanel is not necessarily a complete list of every single library on your computer.

You can attach libraries that were previously removed, simply by dragging them on top of the application or by choosing Create Library from the File menu or Add Library from the sidepanel.

Finally, you can also use the Location > Explore panel to scan for possible libraries throughout your file system. Please see this entry for more information.

No, joining multiple libraries ‘on the fly’ is currently not possible.
Yes - the Explore tab should be helpful here. Start by choosing approximately the location where you think your library was located. The entire path (folders and subfolders) will be scanned, and eventually your library should be shown in the folder tree

Usually, you would use Refresh to scan newly arrived or changed files. But if you want to force a complete rescan of all files, this is possible too:

  • Select the library you want to rescan
  • Right-click and choose “Remove”, and then “Delete” (to remove the database)

Now the library is gone from the list, but its folder is easily found again:
Application Menu > Open Recent Library > [Name of library]

Simply choose your library from this list to begin rebuilding it from scratch.

Yes. You are able to remove entries from the list of libraries
Select your library, choose Right-click > Remove. When doing this, you are given the choice between ‘removing’ and ‘deleting’ the library.
If you choose to just ‘Remove’ then the library is simply pulled from the active list in Sononym -
but the folder will still contain the collected data and can be opened at a later time.
As long as you know where the folder is located and it contains a sononym.db file, you’re good to go.
In order to open the library, you have several options:
1. “Open” a library by choosing “Add” from the Location sidepanel.
2. Choose File > Create Library from the application menu.
3. Drag the folder on top of the application window.

Usually, a library is created from files contained in a specific folder. But, using symbolic links (a feature of your operating system), it’s possible to bring together folders from different places - even different physical media.

The following article demonstrates how this can be achieved: Guide: Using Symbolic Links with Sononym

Sononym is able to index local drives as well as network attached storage (NAS) as long as the folders are not write-protected and are reachable through your OS.

If you absolutely need to index files in a write-protected location, a trick you can perform is to offload the database using symbolic links.


Each library is stored as a SQLite database (a file called sononym.db) in the topmost folder.
A few additional files (e.g. sononym.db-wal or sononym.db-shm) might also be present, depending on whether the database is currently opened, or was left open when the program quit.


The application itself stores files (such as the user configuration, query, log files etc.) in folders specific to the OS you are using.
Please refer to the documentation in order to learn where those folders are located.

No. Simply right-click your library and choose `Refresh (Reindex) -
Refreshing will check for newly arrived and/or changed files, and only analyze those files.
No. This is a planned feature, for which we are gathering input from our users.
Feel free to get in touch if you feel you could contribute to this feature.
Yes. Some of the columns in Sononym are simply hidden by default.
The documentation explains how to configure columns options
This is most likely caused by your audio latency being set too low.
Head into the Audio Configuration to adjust the latency.
Most likely this is caused by a high audio latency.
By default, the application starts with a ‘safe’ value, but you can set it
to a lower value from the Audio Configuration.