I see them, but have not tested them. I would suggest that the amount of grief that they can cause at this early stage of HTTP Live Streaming will not be worth it. There are several resources available to use to try to solve problems with it.
If you want to go cheap, you can try:
$ 50: Apple Compressor. Encodes and segments all in one if you have a MAC
$ 25: Markelsoft HLS Segmenter: you may need to play with some X.264 settings to get the final product, and although it segments (a lot of work), it does not create a variant list. You can do it manually using notepad. it is not a big job.
If you want completely free, you have:
Coding: Handbrake, MeGui, whatever you want. Just follow Android encoding specifications. Use H264 and AAC. DO NOT use progressive download settings / presets. Use CBR not VBR and make sure the frame rate is constant, not variable. Choose a frame rate that can be easily used when multiplying, so you can ensure that the keyframe is in the segment.
Use Apples Free tools: mediafilesegment, variantplaylistcreator, etc. Mediafilesegmenter will ask you how big a segment you want. The default value is 10 seconds. In this case, you set the key frame of the decoder so that each segment starts with a key frame.
I will give two examples.
Example 1:
- Segmentation Size: 10 seconds
- Framerate: originally variable 29.97, encode to 30 fps constant
- Keyframe distance in frames: 30 x 10 seconds = 300 frames. You need a keyframe every 300 frames.
- Recommended keyframes for adaptation: every 2 seconds
Setting the keyframe 2 * 30 = 60 frames. Every fifth keyframe (5 * 60) leads a segment
Example 2:
- Framerate: originally variable 23.97, encoding up to 24 fps constant
- Segment size: 8 seconds
- The key frame needed for the segment: 8 * 24 = 192
- Recommended for adaptation 2 seconds = 2 * 24 = 48
- Every fourth keyframe (4 * 48) leads a segment
source share