Freesound Forums

Hi there,

Mixcraft has an option to search the freesound.org database and with the recent server move it no longer works via the Mixcraft client. )=

For example,

https://freesound.org/apiv2/search/text/?query=test&token=&fields=id,name,username,url,created,tags,license,duration,bitdepth,bitrate,samplerate,filesize,channels,num_downloads,avg_rating,num_ratings,previews,analysis,description,&descriptors=rhythm.bpm,tonal.key_key,tonal.key_scale&page=1&page_size=10&sort=

does not work.

However, if I paste this into a browser it shows no errors and seems to behave properly. Is our API key still valid?

Hope you can help! Thank you!

-Joseph

It's worth posting this in the dedicated API communication channel here:

https://groups.google.com/g/freesound-api

Best,
Sam

Ok. Thank you!

Hi Joseph,

The errors you are observing is because the client seems to be using a deprecated API feature which has stopped working after the server migration. It stopped working because the feature relies on a service which was not prioritary and we have not moved (and which we were planning to remove before summer anyways).

You see no errors in the URL you pasted, but bpm and tonality information are not returned as expected, which I guess makes the mixcraft app to fail. Instead of using the combination of "analysis" and "descriptors=rhythm.bpm...", you can now simply add "bpm" and "tonality" in the "fields" parameter. So you would do:

https://freesound.org/apiv2/search/text/?query=test&token=&fields=id,name,username,url,created,tags,license,duration,bitdepth,bitrate,samplerate,filesize,channels,num_downloads,avg_rating,num_ratings,previews,description,bpm,tonality&page=10&page_size=10&sort=

You can find a list of avialable fields in the API documentation (https://freesound.org/docs/api/resources_apiv2.html#sound-sound). That feature was deprecated more than one year ago and we sent emails to owners of API keys who used it, but maybe in your case the email did not reach any relevant mailbox. Ideally you could release an update for the clients, but if this is not feasible, send me a private message and we look into other options. Note that instead of getting "key_key" and "key_scale" you now get the info combined in "tonality".