Page 1 of 1

HTTP Live Streaming -or- HTML5 video streaming [iPad Video]

PostPosted: Wed Apr 20, 2011 4:31 am
by ript
Silly Apple. The iSub developer says he can't get video streaming on iPad to work unless Subsonic adds support for Apple's "HTTP Live Streaming". See his forum for details.

Could we sidestep this issue by using HTML5 video streaming (instead of JwPlayer)? Someone else mentioned this might be possible with help from jQuery. Then we could use Safari... right? Or has Apple fudged that too?

By the way, Skyfire doesn't recognize the stream with it's flash video detection; so, no luck there.

I hope this isn't a horrible repost. I did check the search function...

BTW, can anyone confirm Frash working on older Jailbroken firmware? My iPad 1 was refurbished and came with 4.3 so I've got the dang food.c error.

Re: HTTP Live Streaming -or- HTML5 video streaming [iPad Vid

PostPosted: Thu Apr 21, 2011 1:47 am
by rspeed
ript wrote:Silly Apple. The iSub developer says he can't get video streaming on iPad to work unless Subsonic adds support for Apple's "HTTP Live Streaming". See his forum for details.

Could we sidestep this issue by using HTML5 video streaming (instead of JwPlayer)? Someone else mentioned this might be possible with help from jQuery. Then we could use Safari... right? Or has Apple fudged that too?

By the way, Skyfire doesn't recognize the stream with it's flash video detection; so, no luck there.

I hope this isn't a horrible repost. I did check the search function...

BTW, can anyone confirm Frash working on older Jailbroken firmware? My iPad 1 was refurbished and came with 4.3 so I've got the dang food.c error.


There's a few threads about replacing JW Player with something based on open standards – HTML5 in particular. I haven't looked at Subsonic's code, but it seems like adding support for HTTP Live Streaming wouldn't require any major changes. All of the heavy lifting is done by ffmpeg (to convert the source video to an MPEG-2 Transport Stream) and the tools provided by Apple (to generate the necessary files). A good chunk of the changes necessary would be on the front-end to identify compatible browsers.

Is anyone working on this, or at least looking into it?