REST:stream.view - estimateContentLength not working

[rich600]

Hi,

I'm trying to get an estimated content length from stream.view using the REST API.

Here's an example URL :

http://<myserver>:4040/rest/stream.view?v=1.8.0&c=me&u=me&p=enc:<me>&id=42418&estimateContentLength=true&format=mp3&maxBitRate=0

I've tried this with a maxBitRate of 160 too, to force transcoding, and still nothing. The track plays fine.

When I look at the response in the browser, there are no response headers, but I'm expecting a content-length header.

I'm using SS 5.1 (non-beta).

Anyone else got this issue?

Thanks
Rich

[rich600]

Anyone ?!

[rich600]

I notice that when I put the URL into safari, although it downloads the video, it cannot estimate the size of the download - just showing ?

Looks like a bug.

Cheers
Rich

[acroyear]

I commented on the API pages at Google Groups.

I found that same problem of not getting content length when coming from the Fire Stick (but I *do* get it when coming from Desktop Chrome). It turns out that (at least in 5.0), the audio tag and/or audio player needs to send the "Range:" header in order for subsonic to return the content length tags. If you omit the range, it omits the content length and I can't find any way to resolve that without going into the source codes.

Whether or not html5 audio sends the Range is extremely browser-specific...and sometimes broken. It *was* working in Chrome 38 and 39 for Android, for example, but has stopped working in 40. It doesn't in the bundled browser for Android 4.2 but does in Android 4.4.I'm having no problems that I know about on Firefox (or Thunderbird) at this time.

There is no way to override the html5 audio tag's behavior in this to force it to send the header.

[acroyear]

I can't speak for video. I have no need of it (I use plex for my video services).

[rich600]

Hi

thanks for the tip about the range. My player, when playing from the start, didn't send a range, so SS never sent back a content-length. I've changed it so that it sends a range of "0-" if playing from the start, and now the content-length is sent back correctly.

It would probably be better for SS to assume that no range effectively means "0-" and set the content-length appropriately.

Cheers
Rich