Unique segment numbering

  • Segments generated by the encoder must be created with sequentially increasing segment numbers such as 1, 2, and 3.

    For example:

    http://p-ep{stream_id}.i.akamaientrypoint.net/<stream_id>/<uniquesourcename>/<sessionID>/<bitrateID>/<OPTIONAL_PATH>/<somename>_<sequence#>.ts
    http://p-ep{stream_id}.i.akamaientrypoint.net/<stream_id>/<uniquesourcename>/<sessionID>/<bitrateID>/<OPTIONAL_PATH>/segment_0001.ts
    http://p-ep{stream_id}.i.akamaientrypoint.net/<stream_id>/<uniquesourcename>/<sessionID>/<bitrateID>/<OPTIONAL_PATH>/segment_0002.ts
    http://p-ep{stream_id}.i.akamaientrypoint.net/<stream_id>/<uniquesourcename>/<sessionID>/<bitrateID>/<OPTIONAL_PATH>/segment_0003.ts
  • The segment number must be extractable from the upload URL using regex. Ensure that you separate the string and the numbers of a segment. Segment names can contain alphanumeric characters and the hyphen (-) as delimiters. Other special characters are not supported. The last item before the prefix must be a unique, sequentially increasing number. You cannot use symbols, special characters, or alphabets.

    For example:

    bitrate1000-00012.ts

    <sessionId>/bitrateA_12.ts

    <sessionId>/1-123.ts

    <sessionId>_1_123.ts

    <sessionId>/P2-2-1001.ts(with directory rollover)

The path and segment number must be treated as one entity; therefore, they must not repeat. Archived data becomes corrupted when the encoder restarts and attempts to use the previous sequence number and path.