bmff | ISO Base Media File Format Parsing Library

As about. I want to play a MP4 via Media Source Extensions, but not any MP4 file can play. Please check FLV.js, it works by transmuxing FLV file stream into ISO BMFF (Fragmented MP4) segments, followed by feeding mp4 segments into an HTML5 element through Media Source Extensions API.

So, What is the diference between ISO BMFF and other mp4 format?

Can anyone tell me or point me to a section of the specification(s) that clearly demonstrates how from an elementary stream with a series of NALUs how these should be written into a ISO BMFF mdat?

I can see looking at samples and other code that I should have something like: AUD, SPS, PPS, SEI, VideoSlice, AUD etc etc

Things that are not entirely clear to me:

1. If the SPS and PPS are also stored out of band in the AVCC are they required in the mdat?
2. If they are required in the mdat when/where should they be written? e.g. just prior to an IDR?
3. What is the requirement for AUDs?
4. If I am generating sample sizes for the trun is the calcuation for this? In the example I am working to recreate the first sample in the trun has a size of 22817 however if I look at the first sample in the mdat the NALU size prefix is 22678. The value in the trun appears to be the size of all the NALUs + sizes up to and including the first sample (see my example below)

>

I'm trying to parse the sidx segment to use it on dash streaming! ( I prefer to use javascript for it )

I have the sidx range and I have already buffered it .. but it's all in hexadecimal. . I'm trying to make it as a known object to calculate segments range and buffer it into sourcebuffer.

here's the sidx

I am trying to make iso bmff from raw h264 byte stream for playing through javascript. I am getting data through custom transport container (Not any standard HLS or rtsp packet) where each packet contain a relative timestamp. For example:

chunk1:

Packet1 -- timestamp:100, payload: H264 raw data [Usually single NAL unit]

Packet2 -- timestamp:120, payload: h264 raw data

chunk1:

Packet1 -- timestamp:140, payload: H264 raw data

Packet2 -- timestamp:160, payload: h264 raw data

Since packet timestamp is the relative time in milliseconds so I am considering time scale value is 1000 and calculating DTS from difference of first packet and consecutive packet. For example,

DTS for 1st chunk: 0 [ 100 - 100]

DTS for 2nd chunk: 40 [140 - 100]

But problem is that it is working fine in firefox but chrome just got stuck after first frame.

What cause could be? Am I doing wrong with DTS or time scale?

Noted that I don't have any B frame, so my DTS and PTS value is same