Is there any way to stream rtmp to HLS (m3u8 live stream) through crtmpserver
发自我的 iPhone
You received this message because you are subscribed to "C++ RTMP Server" mailing list.
To post to this group, send email to c-rtmp...@googlegroups.com
To unsubscribe from this group, send email to
c-rtmp-serve...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/c-rtmp-server?hl=en
Good luck with killing your hard drive with this schema.
You received this message because you are subscribed to "C++ RTMP Server" mailing list.
To post to this group, send email to c-rtmp...@googlegroups.com
To unsubscribe from this group, send email to
c-rtmp-serve...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/c-rtmp-server?hl=en
> Hello Max,
> Don't worry.
> use RAM Disk.
Yes, this is very important piece of information. Max was right. I personally killed an SSD drive but not with this schema. I was doing VOD on a production server using SSD as storage. The poor disk didn't last for more than 3 weeks. I was having between 200-300 concurrent connections and people connecting were doing quite a lot of indirect seeks on the disks, especially with bad formatted media files (mp4) in which instead of interleaving the audio and video tracks, there were put in a totally separate file regions. So, the server was seeking inside the file back and forth way too many times to serve adjacent audio and video frames. They should be put close together inside the mp4 file, not in different regions.
Again, the mp4 file(s) structure was "legally" correct, but not optimized :(
Rule of thumb... Be careful with disks if you are not going to serve the files in an orderly fashion (starting from beginning of the file and never go back)
Cheers,
Andrei
------
Eugen-Andrei Gavriloaie
Web: http://www.rtmpd.com
> Eugen. Am I right, that it is basically a good idea to reorganize mp4
> in sorted DTS mode?
Definitely! It will work much faster and relief the HDDs from such big stress.
Usually, this "bogus" mp4 files are resulted from recording live sources. The app doing the recording, because it doesn't know when the file ends, it creates multiple fixed-length mp4 files with fixed regions for audio and video tracks. What that app should do after closing a file, is to re-organize it, not leaving it like that. The second approach is to just use MOOF atoms (movie fragments), instead of MOOV atoms
Cheers,
Andrei
It is very bad. Erlyvideo recorder dumps frame by frame and only after
records moov atom.