<frederic.f...@gmail.com> wrote:

> You will also see that other clients have not been updated since the last
> api release. We are on the process of rethinking a bit the implementation of
> the api clients (specially the as3 and javascript) because we believe they
> could be much more simpler, so we will be informing about that. However, it
> is very easy to hack the clients and have access to these new
> funcionalities, and if you are in trouble just write to this list!

On Wednesday, March 21, 2012 7:22:28 AM UTC-5, frederic wrote:

> Dear Freesound Api hackers,

> if you have a look at the Api documentation<http://www.freesound.org/docs/api/>you'll see we have added a couple of new functionalities that can be useful
> to you.

> 1) New 'sounds_per_page' parameter in any request returning a paginated
> list of sounds: now you can specify the number of sounds you get in every
> page of the response. For the moment there is a maximum of 100 sounds per
> page (we don't want to saturate our servers!). The idea of this parameter
> is to use it together with the 'fields' parameter (which allows you to ask
> only for certain sound properties in the response, so you can say "give me
> only sound preview urls" and then increase the number of sounds per page so
> the overall volume of information is kept low). This way you can speed up
> some tasks!

> 2) Bookmarks! now you can also get the list of sounds that a user has
> bookmarked and its bookmark categories. This can be useful for example if
> you want to create particular sets of sounds for you application and have
> an easy way to access them (instead of saving a list of ids or something
> like this).

> Regarding the api clients, you'll have seen through this mailing list that
> we now have a new php client implemented by nocive<https://github.com/nocive>(
> http://www.freesound.org/docs/api/client_libs.html). Thank you very much
> for the contribution!

> You will also see that other clients have not been updated since the last
> api release. We are on the process of rethinking a bit the implementation
> of the api clients (specially the as3 and javascript) because we believe
> they could be much more simpler, so we will be informing about that.
> However, it is very easy to hack the clients and have access to these new
> funcionalities, and if you are in trouble just write to this list!

> Finally, we have many ideas of new functionalities for the api but don't
> hesitate to send any ideas or comments to the list!

> frederic
> Freesound team

> The 'sounds_per_page' parameter has been very useful to me thanks for this
> addition. I've noticed however, that the 'next' field in the response does
> not seem to work with this paremeter.

> For example, If I request

> http://www.freesound.org/api/packs/9133/sounds?api_key=...&sounds_per...

> then it seems the 'next' url in the response should be...

> http://www.freesound.org/api/packs/9133/sounds?api_key=...&sounds_per...

> but instead it is...

> http://www.freesound.org/api/packs/9133/sounds/?p=2

> I was hoping to use the 'next' url to traverse each page and collect sound
> id's and then download them.

> Thanks,

> Kevin

> On Wednesday, March 21, 2012 7:22:28 AM UTC-5, frederic wrote:

>> Dear Freesound Api hackers,

>> if you have a look at the Api documentation<http://www.freesound.org/docs/api/>you'll see we have added a couple of new functionalities that can be useful
>> to you.

>> 1) New 'sounds_per_page' parameter in any request returning a paginated
>> list of sounds: now you can specify the number of sounds you get in every
>> page of the response. For the moment there is a maximum of 100 sounds per
>> page (we don't want to saturate our servers!). The idea of this parameter
>> is to use it together with the 'fields' parameter (which allows you to ask
>> only for certain sound properties in the response, so you can say "give me
>> only sound preview urls" and then increase the number of sounds per page so
>> the overall volume of information is kept low). This way you can speed up
>> some tasks!

>> 2) Bookmarks! now you can also get the list of sounds that a user has
>> bookmarked and its bookmark categories. This can be useful for example if
>> you want to create particular sets of sounds for you application and have
>> an easy way to access them (instead of saving a list of ids or something
>> like this).

>> Regarding the api clients, you'll have seen through this mailing list
>> that we now have a new php client implemented by nocive<https://github.com/nocive>(
>> http://www.freesound.org/**docs/api/client_libs.html<http://www.freesound.org/docs/api/client_libs.html>).
>> Thank you very much for the contribution!

>> You will also see that other clients have not been updated since the last
>> api release. We are on the process of rethinking a bit the implementation
>> of the api clients (specially the as3 and javascript) because we believe
>> they could be much more simpler, so we will be informing about that.
>> However, it is very easy to hack the clients and have access to these new
>> funcionalities, and if you are in trouble just write to this list!

>> Finally, we have many ideas of new functionalities for the api but don't
>> hesitate to send any ideas or comments to the list!

>> frederic
>> Freesound team