API Feature Request - Stream: Setting[n] To Use

[Matma]

This may be possible but i cant see how or where to do it but i would ideally like to be able to request a specific transcoding setting be used when i call the "Stream" (http://your-server/rest/stream.view) api call.

why? well if i could do that i could setup specific transcoder settings for specific devices and request the appropriate transcode be returned to the browser. i.e. for iphone/android/safaru i would "ask" for the H.264+AAC+MP4 and for IE, Firefox, Opera i would ask for the WebM transoded version etc etc...

That way i dont have to modify the original source of subsonic in any way, i can just add the transcoders/settings and adjust the request made from the browser based on the browser type/version.

even the simplest solution would do me for now, an extra param on the call of the settings array index or name or whatever works.

Please let me know if this is possible or of interest.
Thanks
Matt

p.s. does anyone know if using HTML5 <video> tag ignores the iphones 10minute time limit thingy? i cant find what to search for in google...

[sindre_mehus]

Yes that would be a nice extension.

I think the best solution would be a new parameter "format" to the "stream" api method. This parameter would contain the target format of the preferred transcoding to use (in case there are more than one eligible transcodings). For instance "format=mp4" or "format=flv".

Would this work in your case?

[Matma]

Yeah that would work.

There is one other thing i can see being useful and that is size, in so much as i could call
stream&id="123"&format="MP4"&size="320x480" <- iphone 3
stream&id="123"&format="MP4"&size="640x960" <- iphone 4
stream&id="123"&format="MP4"&size="XxY" <- some other device...

With that and html5 i could use newly created MP4, OGG and WebM transcodings and just ask for mobile device sizes/resolutions and leave desktops to use the defaults. Dont know how feasible this is but it would proably complete the puzzle for me. For now the target format will do but if you could add size too that would be great.

I know its a bit premature to ask when we would be likely to see an implementation of this but if you could have a think and drop me a ball park timeline, (1-2 months? 6-12?).

Thanks
Matt

[sindre_mehus]

Yes, a "size" parameter would be useful and easy to implement.

1-2 months is realistic.

Thanks

[Matma]

Awesome, i see this has been added to the latest beta thanks.

I'll give it a run today and post an update of the c# wrapper since I've not committed in a while.