Ssl write failed

Server NGINX
41

FLV streaming module will not work correctly with h.264 FLV files. In a
h.264 file, you can’t just jump to a keyframe, it also requires an AVC
sequence header (which is the avcC box in an mp4 file) and an AAC
sequence
header.
The change required to make the FLV streaming module work with h.264 flv
files is not big, the sequence header will be the first video frame and
the
first audio frame in the FLV.

Sergej

42

Actually it is not recommended by Adobe to use h.264 inside an flv
file, one should instead use f4v which was made for that, I guess that
at the time of writing only Adobe Media Encoder can do that. Otherwise
there is the mp4 module developed by Peng Wu.

43

They are not exactly the same thing: an f4v can be streamed
out-of-the-box whereas an mp4 requires you to move some of its data
around before being able to stream it.

44

No. The format specfication does not specify the placement of the moov
box
(the metadata). Most encoders place it at the end, because it’s easier.

Sergej

45

f4v, m4v and mp4 is the exact same thing, just a different file
extension.
Not to mention .mov and .3gp which is practically the same thing.
Why Adobe decided to add to the confusion with an additional name is a
mistery

Sergej

46

that’s great for content distribution.

2008/10/12 ÎéÅô [email protected]:

My situation is that we have some data centers across country, and each data center has some servers to provide video clips to our users. >Because we want to simplify the management of the storage and video files synchronization problem, we maintain only one central storage. >The servers on edge data centers should cache the most visited video clips based on LRU algorithm.
Peng Wu
2008-10-12

–
Best Regards,

Ѧ ÓÂ

QQ:312200

e-mail:[email protected]
MSN:[email protected]

47

You should share the scripts and such :slight_smile:

48

Dear mike,

You should share the scripts and such :slight_smile:
ohh,it is quite simple:
#!/bin/bash
find /your/proxy/store/path -atime 1 -type f | xargs rm -f
#this will delete any file more than a day no access

Dear all,

I have implemented an H.264 pseudo streaming module. And now I want to add cache feature to this module.
Forget it!
I made a silly mistake, after reading docs over and over and now I realize this is unnecessary.
Using proxy module’s proxy_store directive and some scripts, I can do everything I want.
No new code should be written.
Nginx is a great product, it has almost every feature I want. I love it.
Thank you Igor.

Peng Wu
2008-10-16

49

Hi Peng,

Were you able to get your hands on a testing machine? I’d like to use
your module in my development environment. I own a PowerPC G4 so it
might be complicated to make it work on that platform.

50

Dear all,

I have implementated an H.264 streaming module, you can download it from
http://218.244.191.134:8081/mp4.tar.bz2
The source code has been moved to http://211.100.49.134:8081/mp4.tar.gz
the old server 218.244.191.134 is not available.

install & compile

  1. wget http://211.100.49.134:8081/mp4.tar.gz
  2. tar xfj mp4.tar.bz2
  3. mv mp4 your_path/nginx-0.7.22/src/http/modules
  4. cd your_path/nginx-0.7.22/src/http/modules
  5. ./configure --with-http_flv_module --add-module=src/http/modules/mp4
  6. make
  7. make install
    8.sample configure:

location ~ .mp4$ {
mp4;
#limit_conn one 2;
#limit_rate 512k;
}

location ~ .flv$ {
flv;
#limit_conn one 2;
#limit_rate 300k;
}

Enjoy!