@chief.ahusaka @dawnbreaker1883 Thanks for following up on this 414 error and missing soundset issue.
I spent some time digging through older backups today and I did find the “element dump” soundset (in a 16 March backup). I have restored it to production just now. It certainly was large with >200 elements, >1,400 samples, and >3,000 records in the database.
I do not know how it came to be deleted, and I do not think the 414 error or soundset size is related to the deletion. However, I am glad that I was able to locate and restore it.
Unfortunately I was still unable to locate the “witchwood 19” soundset. Perhaps it was both created AND deleted in between backups. Do you know roughly when it was created and last accessed?
The 414 error though was related to soundset size. One of the requests the master interface makes on navigating into a soundset is to fetch sample data by passing IDs as query string parameters in the URL. In this case, the URL was >20,000 characters long with >1,400 IDs.
I have updated the code to send the IDs another way to avoid this web server limitation. However, this is still a LOT of data and we really do recommend working with smaller sized soundsets.
I will add an issue to our backlog to consider how we manage soundset size moving forward, and also the ways in which a soundset may be deleted.
If anyone does experience an unexplained data loss issue, please contact support@syrinscape.com right away and let us know:
- The name, type, ID of the deleted content.
- The date when you think it was last still available in the system.
- The date when you first noticed it was missing.
If there are any data loss bugs, we will absolutely work hard to squash them and recover any lost data.