Reply to thread

Message

<blockquote data-quote="cheezey" data-source="post: 680752" data-attributes="member: 10350">Re: Re : iPiMP 5.1.0 is releasedHave a read of this <a href="http://smoothstreaming.code-shop.com/documentation/usp_whitepaper.pdf" target="_blank">document</a>, it is a good explanation of the Unified Streaming Platform from CodeShop that iPiMP is using, explains the differences between Apple's, MicroSoft's &amp; Flash's streaming solutions and how USP manages to do all three from one source. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />) I sound like a salesman!)The ismv file is a fragmented MP4 container containing multiple video(h264)/audio(aac) streams (iPiMP only has one video stream at the moment - if we want to do true adaptive bitrate we'd add more of these through additional --newvideo ffmpeg command line parameters)The ism file is a manifest file detailing the contents of the ismv file.The db3 file is a sqlite DB used by USP (not sure what for).The ismv doesn't do segmented files', it keeps writing to the ismv file, which is why you see it continually growing. USP generates an m3u8 file on the fly which, instead of listing the individual filenames of segmented files, lists the start/stop positions of segments in the ismv file - so mimics segments.&nbsp; If you look in Apache\logs\access.log you'll see these requests.</blockquote>

[QUOTE="cheezey, post: 680752, member: 10350"] [b]Re: Re : iPiMP 5.1.0 is released[/b] Have a read of this [URL="http://smoothstreaming.code-shop.com/documentation/usp_whitepaper.pdf"]document[/URL], it is a good explanation of the Unified Streaming Platform from CodeShop that iPiMP is using, explains the differences between Apple's, MicroSoft's & Flash's streaming solutions and how USP manages to do all three from one source. (:) I sound like a salesman!) The ismv file is a fragmented MP4 container containing multiple video(h264)/audio(aac) streams (iPiMP only has one video stream at the moment - if we want to do true adaptive bitrate we'd add more of these through additional --newvideo ffmpeg command line parameters) The ism file is a manifest file detailing the contents of the ismv file. The db3 file is a sqlite DB used by USP (not sure what for). The ismv doesn't do segmented files', it keeps writing to the ismv file, which is why you see it continually growing. USP generates an m3u8 file on the fly which, instead of listing the individual filenames of segmented files, lists the start/stop positions of segments in the ismv file - so mimics segments. If you look in Apache\logs\access.log you'll see these requests. [/QUOTE]

Verification