Sononym sample management/browser
-
qtheerearranger qtheerearranger https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=325452
- KVRian
- 919 posts since 26 Mar, 2014 from Denver, Co
just gonna say it... this product is amazing at this point - anyone who deals with making a lot of new samples a lot will absolutely love this.
But im a bit worried as this is exactly what logic pro is missing - wouldn't be slightly surprised if apple buys them and we see this in logic eventually. this seems like the exact type of thing apple would buy. but u know i live with the tin foil hat always on
But im a bit worried as this is exactly what logic pro is missing - wouldn't be slightly surprised if apple buys them and we see this in logic eventually. this seems like the exact type of thing apple would buy. but u know i live with the tin foil hat always on
Bitwig 6 • Diva, Dune, Serum, and UVI Falcon are my Daily Drivers • Drum Machines • Harrison 32c + DSM 3 + American Class A Enjoyer • Apple M4 Max • Apollo User • DJ • Dance Music is life
-
- KVRian
- 601 posts since 5 Oct, 2004
As much as i love that there's such a nice update i have to admit that the new version completely destroyed my Sononym library.
So reverted back to v1.5.6 and waiting for support to answer.
MAC OS Sonoma here
So reverted back to v1.5.6 and waiting for support to answer.
MAC OS Sonoma here
Last edited by kinkajou on Wed Nov 26, 2025 7:00 pm, edited 1 time in total.
-
- KVRAF
- 2056 posts since 13 Dec, 2016
Yeah same here. This is a great update but I have to upgrade every single library, which already takes hours despite the program claiming no proper database or version was in use.
I´ve had the latest version installed on my pc
I´ve had the latest version installed on my pc
Its over for Bitwig--CUBASE WON !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
-
Andrei Marchenko Andrei Marchenko https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=312360
- KVRian
- 866 posts since 12 Sep, 2013
Got some interesting issue in the mac os launchpad (Sequoia):


-
- KVRist
- 67 posts since 2 May, 2005
Urgh..what is THAT?Andrei Marchenko wrote: Wed Nov 26, 2025 8:02 pm Got some interesting issue in the mac os launchpad (Sequoia):
![]()
I guess we need to revisit the icon.
-
- KVRist
- 188 posts since 28 Jun, 2013
Agreed, very nice update, thanks.
EDIT: Ah yes, "Failed to upgrade the library - unexpected error type"
EDIT: Ah yes, "Failed to upgrade the library - unexpected error type"
Code: Select all
2025-11-26T20:18:08.806Z - error: [RENDERER] Library failed to mount: Failed to upgrade the library:Unexpected error type (/Users/ffx/sample libraries/sononym.db)
Last edited by ffx on Wed Nov 26, 2025 8:19 pm, edited 1 time in total.
-
- KVRist
- 67 posts since 2 May, 2005
It's being looked into.kinkajou wrote: Wed Nov 26, 2025 6:49 pm As much as i love that there's such a nice update i have to admit that the new version completely destroyed my Sononym library.![]()
So reverted back to v1.5.6 and waiting for support to answer.
MAC OS Sonoma here
For good measure, here are direct links to the previous installers:
https://sononym.net/download/Sononym-1.5.6-arm64.dmg
https://sononym.net/download/Sononym-1.5.6.dmg
https://sononym.net/download/Sononym-1.5.6.exe
https://sononym.net/download/sononym-1.5.6.tar.bz2
On macOS, having multiple versions installed side-by-side is as simple as renaming the application, as they maintain separate configuration files.
-
- KVRian
- 600 posts since 1 Jul, 2009
Looks like there is something wrong with the scanning. It just wrote 500GB on the SSD while scanning ~70GB. It rewrites the sononym.db constantly? Before starting the scan, the total writes on the SSD was 3TB (accumulated in 2 years) now it's 3.5TB after scanning 70%. Thanks, I guess. As soon as I observed this, I closed Sononym and it was still not finished with the scan after 2 hours. I won't open it again until a fix is released...
The scanning was from 0. Deleted the old databases beforehand.
The scanning was from 0. Deleted the old databases beforehand.
-
- KVRist
- 314 posts since 12 Mar, 2004
Not sure if that has been an issue before (never noticed it), but Dropbox seems to block the sononym database file. It seems Dropbox must have finished uploading the sononym databases before the converted ones work properly again in Sononym (after restart).
-
- KVRer
- 4 posts since 12 Aug, 2022
Same error here - "Failed to upgrade the library - unexpected error type".
Can't use Sononym now at all. And the scanning my whole library again would take forever.
Please advise, thanks.
Can't use Sononym now at all. And the scanning my whole library again would take forever.
Please advise, thanks.
-
- KVRist
- 67 posts since 2 May, 2005
When analyzing samples, the data is first dumped in a raw format, which is then consumed by the database when it's not too busy with other things. So yeah, technically the data is written to disk twice. But 500GB written for 70GB - that does sound drastic.anoise wrote: Wed Nov 26, 2025 8:32 pm Looks like there is something wrong with the scanning. It just wrote 500GB on the SSD while scanning ~70GB. It rewrites the sononym.db constantly?
A little unscientific test I did revealed an approximate 1:1 ratio between the size of the samples, and the size of the data being written to disk. This is in line with what I would expect, and acceptable IMHO.
Btw: to reduce the disk activity, there are some possibilities that we haven't explored yet. Most importantly, to insert samples in bulk. We haven't chased this goal yet, as our focus was to improve the user experience (speed!!).
Last edited by danoise on Wed Nov 26, 2025 10:54 pm, edited 1 time in total.
-
- KVRist
- 67 posts since 2 May, 2005
There's some info in the release notes:bnz wrote: Wed Nov 26, 2025 9:31 pm Not sure if that has been an issue before (never noticed it), but Dropbox seems to block the sononym database file. It seems Dropbox must have finished uploading the sononym databases before the converted ones work properly again in Sononym (after restart).
So, it's kind of expected that such a thing could happen. The idea is to handle these situations gracefully, and offer some kind of solution. In this particular case, what error message did you see?New Engine, New Requirements
The new database is optimized for modern hardware, and has some requirements that the previous one didn’t have. Perhaps most importantly, an exclusive lock is required to modify the database. If your file-system (e.g. a NAS or cloud folder) does not have this ability, the application should inform you that the library was opened in read-only mode.
.
Also, I wonder if right-clicking the library and choosing "Use Local Drive For Collected Data" does the trick? Doing this should take your 'sononym.db' out of the dropbox folder.