Do not issue any bug reports against versions earlier than 3.5.4 they will be closed.
Furthermore, we cannot accept bugs about metadata or art handling in 3.5.4 due to the large number of bugs that have been fixed since then. 3.5.4 in general is becoming less supportable, and it is suggested to try to reproduce the bug in the latest nightly.
Before submitting a bug please read http://ampache.org/wiki/support:bugs failure to do so may delay resolution of your report.
Furthermore, we cannot accept bugs about metadata or art handling in 3.5.4 due to the large number of bugs that have been fixed since then. 3.5.4 in general is becoming less supportable, and it is suggested to try to reproduce the bug in the latest nightly.
Before submitting a bug please read http://ampache.org/wiki/support:bugs failure to do so may delay resolution of your report.
FS#45 - Pure Random via API
Attached to Project:
Ampache
Opened by Bryce Geiser (bjgeiser) - Saturday, 13 March 2010, 14:27 GMT-8
Last edited by Karl Vollmer (vollmerk) - Saturday, 13 March 2010, 17:50 GMT-8
Opened by Bryce Geiser (bjgeiser) - Saturday, 13 March 2010, 14:27 GMT-8
Last edited by Karl Vollmer (vollmerk) - Saturday, 13 March 2010, 17:50 GMT-8
|
DetailsMy mobile application was using a hack to do pure random, changes in 3.5.4 appear to have broken that hack. My hack was to build the streaming URL used for pure random during a web session to provide the same functionality in my application.
http://<server>/ampache/play/index.php?ssid=4223efbc609976bf0b6428c8571b4f18&random=1&type=default&uid=2 The hack is that I replaced the ssid with my api auth code and it worked until 3.5.4, also since the API has no UID I left that off. My question is would be possible to allow the api auth code access to stream from this path again, or preferably come up with some similar functionality for the API. This is the most efficient way to do pure random I can think of. |
This task depends upon
Comment by Karl Vollmer (vollmerk) -
Saturday, 13 March 2010, 17:51 GMT-8
This will be done with a call in the 3.6.x API. This will not be added to 3.5.x (it's too late)