Talk:Live CD - Revision history

Polto at 19:39, 25 November 2007

2007-11-25T19:39:41Z

← Older revision		Revision as of 19:39, 25 November 2007
Line 144:		Line 144:

	--[[User:Andrey.filippov\|Andrey.filippov]] 11:53, 29 November 2005 (CST)		--[[User:Andrey.filippov\|Andrey.filippov]] 11:53, 29 November 2005 (CST)


			to upgrade if we continue to maintain [[User_Documentation]]

			--[[User:Polto\|Polto]] 20:34, 25 Nov 2007 (GMT)

			to restore / upgrade and point to both Knoppix & Ubuntu based CD/DVD
			--[[User:Polto\|Polto]] 20:39, 25 Nov 2007 (GMT)

87.74.41.127: /* 2GB limit for avi */

2005-12-05T16:01:44Z

2GB limit for avi

← Older revision		Revision as of 16:01, 5 December 2005
Line 109:		Line 109:

	--[[User:Khlut\|Sergey Khlutchin]] 00:16, 18 November 2005 (CST)		--[[User:Khlut\|Sergey Khlutchin]] 00:16, 18 November 2005 (CST)
			----

			I emailed my contact on the mplayer team, and he told me the 2GB limit is no longer an issue in mplayer, since mplayer now supports openDML (an extension to avi which supports larger files).

			I think this support is automatic in the latest version of mplayer/mencoder.

			For older versions of mencoder, you can use:
			mencoder -saveidx <index_file>

			and then:
			mplayer -loadidx <index_file>

			This will save/load the index from a separate file, thus getting around the 2GB limit.

			--[[User:Salsaman\|Salsaman]] 05/12/05

	== Timestamps ==		== Timestamps ==

Andrey.filippov: /* Dump mencoder and write a separate stream recorder? */

2005-11-29T17:53:51Z

Dump mencoder and write a separate stream recorder?

← Older revision		Revision as of 17:53, 29 November 2005
Line 128:		Line 128:
	The DVR software should also provide capabilities to split recording in multiple files (with no time gaps - overlap is acceptable), support pause, support Apple Quicktime (.mov) format in addition to (or instead of) the Microsoft .avi one. Anyway standard Windows player does not support AVI with Motion JPEG inside (at least it did not work for me) so it is better to provide .mov container that will be played as is by the Apple Quicktime.		The DVR software should also provide capabilities to split recording in multiple files (with no time gaps - overlap is acceptable), support pause, support Apple Quicktime (.mov) format in addition to (or instead of) the Microsoft .avi one. Anyway standard Windows player does not support AVI with Motion JPEG inside (at least it did not work for me) so it is better to provide .mov container that will be played as is by the Apple Quicktime.

	--[[User:~~198~~.~~60.22.24~~\|~~198.60.22~~.24]] 11:51, 29 November 2005 (CST)		--[[User:Andrey.filippov\|Andrey.filippov]] 11:53, 29 November 2005 (CST)

198.60.22.24: /* Dump mencoder and write a separate stream recorder? */

2005-11-29T17:52:19Z

Dump mencoder and write a separate stream recorder?

← Older revision		Revision as of 17:52, 29 November 2005
Line 120:		Line 120:
	Nice - probably it will be easier to add timestamp in the driver where it calculates pointers in the DMA buffer (put it just ahead of the frame length).		Nice - probably it will be easier to add timestamp in the driver where it calculates pointers in the DMA buffer (put it just ahead of the frame length).

	===Dump mencoder and write a separate stream recorder?===		==Dump mencoder and write a separate stream recorder?==

	I'm not sure mecoder (contrary to Mplayer) works well just for the RTP stream recording. Even it's name includes "encoder" - the main purpose of this program is to re-code from one format to the another.		I'm not sure mecoder (contrary to Mplayer) works well just for the RTP stream recording. Even it's name includes "encoder" - the main purpose of this program is to re-code from one format to the another.

198.60.22.24 at 17:51, 29 November 2005

2005-11-29T17:51:51Z

← Older revision		Revision as of 17:51, 29 November 2005
Line 119:		Line 119:

	Nice - probably it will be easier to add timestamp in the driver where it calculates pointers in the DMA buffer (put it just ahead of the frame length).		Nice - probably it will be easier to add timestamp in the driver where it calculates pointers in the DMA buffer (put it just ahead of the frame length).

			===Dump mencoder and write a separate stream recorder?===

			I'm not sure mecoder (contrary to Mplayer) works well just for the RTP stream recording. Even it's name includes "encoder" - the main purpose of this program is to re-code from one format to the another.

			What is important for us - the DVR function, just saving the RTP incoming stream(s) as is(are), avoiding frame drops and using as low resources as possible and being able to serve as many cameras in parallel as possible. In some cases the same computer will be used to visualize the stream(s) - likely with reduced resolution/frame rate and with lower priority - only using resources that are left free by the recording.

			The DVR software should also provide capabilities to split recording in multiple files (with no time gaps - overlap is acceptable), support pause, support Apple Quicktime (.mov) format in addition to (or instead of) the Microsoft .avi one. Anyway standard Windows player does not support AVI with Motion JPEG inside (at least it did not work for me) so it is better to provide .mov container that will be played as is by the Apple Quicktime.

			--[[User:198.60.22.24\|198.60.22.24]] 11:51, 29 November 2005 (CST)

Khlut: /* 2GB limit for avi */

2005-11-18T06:17:49Z

2GB limit for avi

← Older revision		Revision as of 06:17, 18 November 2005
Line 106:		Line 106:
	----		----

	Yet ~~enother~~ solution is to hack mencoder such that it itself splits video to files with given number of frames. It will be faster without creation of new process and opening new rtsp session.		Yet another solution is to hack mencoder such that it itself splits video to files with given number of frames. It will be faster without creation of new process and opening new rtsp session.

	--[[User:Khlut\|Sergey Khlutchin]] 00:16, 18 November 2005 (CST)		--[[User:Khlut\|Sergey Khlutchin]] 00:16, 18 November 2005 (CST)

Khlut at 06:16, 18 November 2005

2005-11-18T06:16:51Z

← Older revision		Revision as of 06:16, 18 November 2005
Line 104:		Line 104:
	It will bi nice to have a timestamp for each frame (FPGA now supports precise timing and it should not be very difficult to add code to add timing data to the beginning of each frame by FPGA) but it is likely that MJPEG RTP stream format has no room for such info.		It will bi nice to have a timestamp for each frame (FPGA now supports precise timing and it should not be very difficult to add code to add timing data to the beginning of each frame by FPGA) but it is likely that MJPEG RTP stream format has no room for such info.
	When splitting stream we need to start new seccion first, and end the previous one later)		When splitting stream we need to start new seccion first, and end the previous one later)
			----

			Yet enother solution is to hack mencoder such that it itself splits video to files with given number of frames. It will be faster without creation of new process and opening new rtsp session.

			--[[User:Khlut\|Sergey Khlutchin]] 00:16, 18 November 2005 (CST)

	~~----~~		== Timestamps ==
	RTP standard common header has 32 bit field for timestamp in 1/90000 of second from some base time.		RTP standard common header has 32 bit field for timestamp in 1/90000 of second from some base time.
	So maximum time is 47721 seconds or 13 hours.		So maximum time is 47721 seconds or 13 hours.

Khlut: TOC added

2005-11-15T18:09:32Z

TOC added

← Older revision		Revision as of 18:09, 15 November 2005
Line 1:		Line 1:
	{{en\|ru=Talk:Live_CD_ru\|cn=Talk:Live_CD_cn}}		{{en\|ru=Talk:Live_CD_ru\|cn=Talk:Live_CD_cn}}
			__TOC__
	I'm confused about "netcamconfig" and "netcardconfig".		I'm confused about "netcamconfig" and "netcardconfig".

Andrey.filippov at 17:57, 15 November 2005

2005-11-15T17:57:37Z

← Older revision		Revision as of 17:57, 15 November 2005
Line 111:		Line 111:

	--[[User:Khlut\|Sergey Khlutchin]] 11:22, 15 November 2005 (CST)		--[[User:Khlut\|Sergey Khlutchin]] 11:22, 15 November 2005 (CST)

			Nice - probably it will be easier to add timestamp in the driver where it calculates pointers in the DMA buffer (put it just ahead of the frame length).

Khlut at 17:22, 15 November 2005

2005-11-15T17:22:10Z

← Older revision		Revision as of 17:22, 15 November 2005
Line 103:		Line 103:
	It will bi nice to have a timestamp for each frame (FPGA now supports precise timing and it should not be very difficult to add code to add timing data to the beginning of each frame by FPGA) but it is likely that MJPEG RTP stream format has no room for such info.		It will bi nice to have a timestamp for each frame (FPGA now supports precise timing and it should not be very difficult to add code to add timing data to the beginning of each frame by FPGA) but it is likely that MJPEG RTP stream format has no room for such info.
	When splitting stream we need to start new seccion first, and end the previous one later)		When splitting stream we need to start new seccion first, and end the previous one later)

			----
			RTP standard common header has 32 bit field for timestamp in 1/90000 of second from some base time.
			So maximum time is 47721 seconds or 13 hours.
			Now this field I calculate in the streamer on frame per second value and errors is summed. I can take it from a special field in the camera frame buffer.
			We can send base time in special packet or with http and rtsp.

			--[[User:Khlut\|Sergey Khlutchin]] 11:22, 15 November 2005 (CST)