Segmenter Configuration

The segmenter service must be configured in your applications red5-web.xml configuration file. Below is a sample showing the segmenter service bean.

    <bean id="segmenter.service" class="org.red5.service.httpstream.SegmenterService">
        <property name="muxService" ref="mux.service" />
        <property name="segmentExecutor" ref="segmentExecutor" />
        <property name="segmentTimeLimit" value="10000" />
        <property name="memoryMapped" value="false" />
        <property name="segmentDirectory" value="webapps/hlsapp/WEB-INF/segments/" />
        <property name="maxSegmentsPerFacade" value="8" />           
        <property name="outputAudioCodec" value="libvo_aacenc" />        
        <property name="outputVideoCodec" value="libx264" />     
    </bean>

Available properties

• Mux service - performs audio muxing
• Thread executor - threading functions
• Segment time limit - length of an individual segment in milliseconds
• Segment storage type - whether to store segments in memory or on disk
• Segment storage directory - directory where segments and playlist files are stored
• Maximum segments - maximum number of segments to keep per stream
• Audio codec - codec to use for audio output; the following two codecs are usually available:
• libvo_aacenc - provides AAC encoding
• libmp3lame - provides MP3 encoding
• Video codec - codec to use for video output; normally libx264 will be available to provide h.264 encoding

Additional information

The segment directory property may be configured with a full path to where your segments will be written if you are using file-based segments. If the "%s" is present when this is parsed, it will be replaced with your applications directory.

A full example application is included in the repo: https://github.com/Red5/red5-hls-plugin/tree/master/example