Forum user: arjen

Hi Andy,

Feel free to send me a private mail at h264@code-shop.com and we'll figure out the configuration issues that you're having. I'll make sure that I'll edit the documentation and post the answer on this forum as well.

Could you start by telling me a bit about your setup/system? That is: your IIS version, your windows version, 32/64 bit, the mod_h264_streaming version (iis5 or iis7), etc...

Hope to hear from you soon,

Arjen

Hi,

The binary (.dll) is now available at

http://h264.code-shop.com/trac/wiki/Mod-H264-Streaming-Internet-Information-Services-IIS-Version2

Regards,

Hi,

The pseudo-streaming modules 'should' set the caching HTTP response headers (ETag, Last-Modified, etc...). If they do that correctly than the next time you play an already fully played movie it will be played from your browser's cache.

Not all pseudo-streaming implementations add these headers though, so YMMV.

Regards,

Hi,

The documentation reads:

'The default parameter the pseudostreaming provider uses for start time is simply start. The value of this parameter holds the seek target keyframe number which is compatible with the server's streaming module.'

For H264 files the start parameters is in seconds, but perhaps for FLV files you need to specify byte offsets instead? Could you try to change the ?start=100 in your not_working example to ?start=15584856 ?

Regards,

Hi Tuanb,

Just remove the 'a' from that line and leave the '}'.

Regards,

Hi,

I've just installed the plugin under Centos52.

sudo yum install httpd-devel
sudo yum install httpd mod_ssl
sudo /usr/sbin/apxs -c -i -a mod_h264_streaming.c moov.c
sudo vi /etc/httpd/conf/httpd.conf
Add the line
'AddHandler h264-streaming.extensions .mp4'
after the line
'LoadModule h264_streaming_module /usr/lib/httpd/modules/mod_h264_streaming.so'
sudo /etc/init.d/httpd start

This gives me a working Apache and a working mod_h264_streaming module.

It's hard to say what's going wrong in your case without seeing the actual commands you are running and its output.

Good luck,

Hi,

The download, installation and configuration instructions are all on that page, so stick to that. Just by following the instructions you should get the plugin up and running.

For example, the first commands listed there get you the necessary source files (including the moov.c file).

cd ~
svn export http://h264.code-shop.com/svn/h264/tags/mod_h264_streaming-2.0/apache apache_http_h264_streaming
svn export --force http://h264.code-shop.com/svn/h264/tags/mod_h264_streaming-2.0/mp4split apache_http_h264_streaming

I hope this helps,

Arjen

Hi Andria,

I assume you have followed the instructions on:http://h264.code-shop.com/trac/wiki/Mod-H264-Streaming-Apache-Version2.

It seems that both the necessary files weren't compiled/linked into the module (you're missing moov.c which defines the mp4_split function).

Could you post (or email to h264@code-shop) the output of the following command:

sudo apxs2 -c -i mod_h264_streaming.c moov.c

Thanks,

Arjen

I've got a simple fix though that solves most problems reported in the forum:

Add the line:

_seekDataStore.prevSeekTime = 0;

at PseudoStreamProvider.as (line 142), just after the '_seekDataStore = DefaultSeekDataStore.create(....) function.

This will fix:

http://www.flowplayer.org/forum/8/15231#post-15232 (click stop, restart) and
http://www.flowplayer.org/forum/8/15231#post-15253 (timer sticks at 0:00)

I've also mailed the developers, so expect this to be fixed soon.

Regards,

Hi,

It's a bug in the current version of the 'pseudo' provider. We've looked at it yesterday and send a fix to the Flowplayer people, so it will probably be fixed soon. If you can't wait, you can use the h264streaming plugin available here http://h264.code-shop.com/trac/wiki/FlowPlayer).

Regards

Hi Chris,

The mod_h264_streaming module for Lighttpd and the plugin for Flowplayer go hand it hand. You need both to allow seeking in not-yet-loaded areas.

I did my best describing how to download/build/install the module, but I can see as well that it's not necessarily the easiest thing in the world. Perhaps you can find someone to help you?

Regards,

Hi Chris,

I hope I'm not suggesting the obvious, but do you have the mod_h264_streaming plugin installed on your webserver (Apache/Lighttpd/Nginx) that serves the mp4 files?

This is a known issue in Flash.

See:http://bugs.adobe.com/jira/browse/FP-794

'Flash Player freeze when reading metadata from 'a large mp4 file'

Hi Niklas,

Just a thought.

You could add a URL rewrite rule to your Apache config that adds an ".mp4" extension to every file in your video directory.

The rewrite guide:http://httpd.apache.org/docs/2.0/misc/rewriteguide.html

Hi,

Just to get an idea of the data it has to transfer. The size of the metadata of the nearly two hour long video-clip (ccc.mp4) is about 4.6MB. At the start of the video the plugin will send out metadata the size of 3.3MB.

The plugin tries to only write the necessary metadata, so when you seek towards the end of the file, it linearly goes down to about a few kilobytes. So seeking towards the end of the file is quicker. :)

Unfortunately 3.3MB is quite a chunk of data and depending on your connection this may take anything between a second and a lot of seconds. It also seems to vary wildly depending on the encoding settings used to transcode the video, but I really haven't had the time yet to try them all and do a quality/size comparison. :)

Regards,