M3U8 Analysis of the network live TV (Part One)

In the previous article, the m3u8 analysis and the keyword section of the network live TV were described. In this chapter I will enumerate and analyze the m3u8 files of different data sources that I have met.

The first: TS fragment address is a file name: http:\\www.xxx.com\01\xx\1.m3u8

#EXTM3U #ext-x-targetduration:8#ext-x-media-sequence:92595#extinf:8,20121120t182851-04-92595.ts#extinf : 8,20121120t182851-04-92596.ts#extinf:8,20121120t182851-04-92597.ts#extinf:8,20121120t182851-04-92598.ts# Extinf:8,20121120t182851-04-92599.ts#extinf:8,20121120t182851-04-92600.ts#extinf:8,20121120t182851-04-92601.ts #EXTINF: 8,20121120t182851-04-92602.ts

Then get to the 20121120t182851-04-92595.ts fragment address is http:\\www.xxx.com\01\xx\20121120t182851-04-92595.ts.

A similar situation, such as the following:

#EXTM3U #EXT-x-allow-cache:no #EXT-x-targetduration:3 #EXT-x-media-sequence:6198 #EXTINF: 3, Aac749f7425bf07f_ 13b4b0fd1b7_6198.ts?wsapp=hls&wsmonitor=-1&wshost=rtmp.cntv.lxdns.com #EXTINF: 3, Aac749f7425bf07f_ 13b4b0fe1b8_6199.ts?wsapp=hls&wsmonitor=-1&wshost=rtmp.cntv.lxdns.com #EXTINF: 3, Aac749f7425bf07f_ 13b4b0ffa08_6200.ts?wsapp=hls&wsmonitor=-1&wshost=rtmp.cntv.lxdns.com

Another: The TS fragment address is a folder structure: http:\\www.xxx.com\01\xx\1.m3u8.

#EXTM3U #ext-x-allow-cache:no#ext-x-targetduration:10#ext-x-media-sequence:9190381#extinf:10,/timeshift/63/ 20121129165010.ts#extinf:10,/timeshift/63/20121129165020.ts#extinf:10,/timeshift/63/20121129165030.ts

Then get to the /timeshift/63/20121129165010.ts fragment address is http:\\www.xxx.com\01\xx/timeshift/63/20121129165010.ts.

Third: The TS fragment address is a folder structure, but overlaps with the m3u8 folder. As: http:\\www.xxx.com\01\timeshift\63\1.m3u8.

#EXTM3U #ext-x-allow-cache:no#ext-x-targetduration:10#ext-x-media-sequence:9190381#extinf:10,/timeshift/63/ 20121129165010.ts#extinf:10,/timeshift/63/20121129165020.ts#extinf:10,/timeshift/63/20121129165030.ts

Remove the conflicting folder, then get to the /timeshift/63/20121129165010.ts fragment address is http:\\www. Xxx.com\01\xx/timeshift/63/20121129165010.ts.

The fourth type: the TS fragment address is the complete fragment, which is: http:\\www.xxx.com\01\xx\1.m3u8.

#EXTM3U #ext-x-allow-cache:no#ext-x-targetduration:10#ext-x-media-sequence:6297202#extinf:10,http:// 202.108.17.170:80/ipad/160_12784_1758/20121127185340.ts?userid=2221281760225887_160_12784_1758#extinf:10,http ://202.108.17.170:80/ipad/160_12784_1758/20121127185350.ts?userid=2221281760225887_160_12784_1758#extinf:10, http://202.108.17.170:80/ipad/160_12784_1758/20121127185400.ts?userid=2221281760225887_160_12784_1758

In this case there is no need to splice.

live different data to get the fragments also basically maintain these four kinds of situations, of course, the woods are big what birds have. Maybe I'll run into a stranger. Oh ...

Summarize:

1, "http" must be the beginning of the whole, do not need to be splicing processing. Also "two-pole source" will be written as "http" or "http" and so on. So we need to turn it into lowercase to make a match, and of course HTTP needs to be lowercase.

2, with the folder structure of the source, the same some or this "timeshift/63/2012129165020.ts", the Front without "/". Watch out!

M3U8 Analysis of the network live TV (Part One)