AVLD - Another Video Loopback Device - Revision history

Luxigo: /* avld-0.13 patches */

2008-09-20T00:49:15Z

avld-0.13 patches

← Older revision		Revision as of 00:49, 20 September 2008
Line 86:		Line 86:
	v4l palette names:		v4l palette names:

	1 RGB24		0 RGB24 (default)
	2 GREY		1 GREY
	3 HI240		2 HI240
	4 RGB565		3 RGB565
	5 RGB24		4 RGB24
	6 RGB32		5 RGB32
	7 RGB555		6 RGB555
	8 YUV422		7 YUV422
	9 YUYV		8 YUYV
	10 UYVY		9 UYVY
	11 YUV420		10 YUV420
	12 YUV411		11 YUV411
	13 RAW		12 RAW
	14 YUV422P		13 YUV422P
	15 YUV411P		14 YUV411P
	16 YUV420P		15 YUV420P
	17 YUV410P		16 YUV410P

Luxigo: /* avld-0.13 patches */

2008-09-20T00:47:50Z

avld-0.13 patches

← Older revision		Revision as of 00:47, 20 September 2008
Line 82:		Line 82:


	And I did add "palette" to the list of the avld module expected arguments, it accepts now a v4l palette name or a v4l palette number, as in linux/videodev.h:		And I did add "palette" and "depth" to the list of the avld module expected arguments, it accepts now a v4l palette name or a v4l palette number, as in linux/videodev.h:

	v4l palette names:		v4l palette names:

Luxigo: /* avld-0.13 patches */

2008-09-20T00:47:20Z

avld-0.13 patches

← Older revision		Revision as of 00:47, 20 September 2008
Line 82:		Line 82:


	And I did add "palette" to the list of the avld module expected arguments, it ~~expects~~ now a v4l palette name, as in linux/videodev.h:		And I did add "palette" to the list of the avld module expected arguments, it accepts now a v4l palette name or a v4l palette number, as in linux/videodev.h:

	v4l palette names:		v4l palette names:

	RGB24		1 RGB24
	GREY		2 GREY
	HI240		3 HI240
	RGB565		4 RGB565
	RGB24		5 RGB24
	RGB32		6 RGB32
	RGB555		7 RGB555
	YUV422		8 YUV422
	YUYV		9 YUYV
	UYVY		10 UYVY
	YUV420		11 YUV420
	YUV411		12 YUV411
	RAW		13 RAW
	YUV422P		14 YUV422P
	YUV411P		15 YUV411P
	YUV420P		16 YUV420P
	YUV410P		17 YUV410P

Luxigo: /* Helper scripts */

2008-09-20T00:17:46Z

Helper scripts

← Older revision		Revision as of 00:17, 20 September 2008
Line 43:		Line 43:
	http://community.elphel.com/files/avld/avldplay		http://community.elphel.com/files/avld/avldplay

	For skype, use avldfeed options WIDTH=640 HEIGHT=480 FPS=25 FORMAT=uyvy FILTER=~~"scale=640:480"~~,		For skype, use avldfeed options WIDTH=640 HEIGHT=480 FPS=25 FORMAT=uyvy DEPTH=24 SCALE=sntsc FILTER=none,
	but generally FORMAT is bgr24		but generally FORMAT (mencoder notation for palette) is bgr24

	Usage: avldfeed [ -h ] [ <configuration_file> ] [ <OPTION=value> ... ]		Usage: avldfeed [ -h ] [ <configuration_file> ] [ <OPTION=value> ... ]
Line 55:		Line 55:
	HEIGHT=<value>		HEIGHT=<value>
	FPS=<-1\|0\|value>		FPS=<-1\|0\|value>
	FORMAT=<bgr24\|uyvy>		FORMAT=<bgr24\|uyvy\|...> (mencoder notation for v4l PALETTE)
	PALETTE=<0\|1> (overriden by FORMAT)		PALETTE=<RGB24\|UYVY\|...> (overriden by FORMAT)
	SCALE=<none\|qntsc\|qpal\|ntsc\|pal\|sntsc\|spal>		SCALE=<none\|qntsc\|qpal\|ntsc\|pal\|sntsc\|spal>
	FILTER=<none\|mencoder_filter_chain>		FILTER=<none\|mencoder_filter_chain>
			DEPTH=<value>

	avldfeed send the specified video stream to the avld video device.		avldfeed send the specified video stream to the avld video device.
Line 66:		Line 67:
	configuration file as first command argument (it will		configuration file as first command argument (it will
	replace ~/.avldfeed)		replace ~/.avldfeed)


	== avld-0.13 patches ==		== avld-0.13 patches ==

Luxigo at 00:13, 20 September 2008

2008-09-20T00:13:31Z

← Older revision		Revision as of 00:13, 20 September 2008
Line 13:		Line 13:


	After loading the AVLD module:		After loading the AVLD module, indicating the maximum frame size you will use:

	modprobe avld width=1440 height=896 fps=0		modprobe avld width=1440 height=896 fps=0
Line 71:		Line 71:


	http://community.elphel.com/files/avld/avld_0.13-VIDIOCGWIN_null_framesize+skype_compatibility+palette_change.patch		http://community.elphel.com/files/avld/avld_0.13-VIDIOCGWIN_null_framesize+skype_compatibility+palette_change+depth_change+more.patch

	(apply with "patch -P0 < filename.patch" in the avld sourcecode directory)		(apply with "patch -P0 < filename.patch" in the avld sourcecode directory)
Line 82:		Line 82:


	And I did add "palette" to the list of the avld module expected arguments.		And I did add "palette" to the list of the avld module expected arguments, it expects now a v4l palette name, as in linux/videodev.h:

			v4l palette names:

			RGB24
			GREY
			HI240
			RGB565
			RGB24
			RGB32
			RGB555
			YUV422
			YUYV
			UYVY
			YUV420
			YUV411
			RAW
			YUV422P
			YUV411P
			YUV420P
			YUV410P


			'''It could break compatibility with applications using an older module version''' since "palette" and "depth" are now mandatory when changing the module parameters. But it avoid scanning twice the video buffer and remove the necessity to reload the module when those parameters must be changed.

	'''It could break compatibility with applications using an older module version''' since "palette=0\|1" is now mandatory when changing the module parameters. But it avoid scanning twice the video buffer and remove the necessity to unload the module when the palette must be changed.		Applications that are unaware of avld and aren't changing the avld parameters themselves are not affected.
	Applications that aren't changing the avld parameters themselves are not affected.


	AVLD homepage: http://allonlinux.free.fr/Projets/AVLD/		AVLD homepage: http://allonlinux.free.fr/Projets/AVLD/

Luxigo at 14:58, 15 September 2008

2008-09-15T14:58:09Z

← Older revision		Revision as of 14:58, 15 September 2008
Line 8:		Line 8:

	and CPU usage is 'only' 20-25% per core		and CPU usage is 'only' 20-25% per core


	~~I could not test beyond the screen and the specific camera/sensor capabilities :)~~


Line 89:		Line 86:

	'''It could break compatibility with applications using an older module version''' since "palette=0\|1" is now mandatory when changing the module parameters. But it avoid scanning twice the video buffer and remove the necessity to unload the module when the palette must be changed.		'''It could break compatibility with applications using an older module version''' since "palette=0\|1" is now mandatory when changing the module parameters. But it avoid scanning twice the video buffer and remove the necessity to unload the module when the palette must be changed.
	Applications that ~~doesnt change~~ the avld parameters themselves are not affected.		Applications that aren't changing the avld parameters themselves are not affected.


	AVLD homepage: http://allonlinux.free.fr/Projets/AVLD/		AVLD homepage: http://allonlinux.free.fr/Projets/AVLD/

Luxigo at 14:56, 15 September 2008

2008-09-15T14:56:57Z

← Older revision		Revision as of 14:56, 15 September 2008
Line 89:		Line 89:

	'''It could break compatibility with applications using an older module version''' since "palette=0\|1" is now mandatory when changing the module parameters. But it avoid scanning twice the video buffer and remove the necessity to unload the module when the palette must be changed.		'''It could break compatibility with applications using an older module version''' since "palette=0\|1" is now mandatory when changing the module parameters. But it avoid scanning twice the video buffer and remove the necessity to unload the module when the palette must be changed.
	~~But applications~~ that doesnt change the avld parameters themselves are not affected.		Applications that doesnt change the avld parameters themselves are not affected.


	AVLD homepage: http://allonlinux.free.fr/Projets/AVLD/		AVLD homepage: http://allonlinux.free.fr/Projets/AVLD/

Luxigo at 14:56, 15 September 2008

2008-09-15T14:56:25Z

← Older revision		Revision as of 14:56, 15 September 2008
Line 88:		Line 88:


	'''It ~~breaks~~ compatibility with applications using an older module version''' since "palette=0\|1" is now mandatory when changing the module parameters. But it avoid scanning twice the video buffer and remove the necessity to unload the module when the palette must be changed.		'''It could break compatibility with applications using an older module version''' since "palette=0\|1" is now mandatory when changing the module parameters. But it avoid scanning twice the video buffer and remove the necessity to unload the module when the palette must be changed.
			But applications that doesnt change the avld parameters themselves are not affected.


	AVLD homepage: http://allonlinux.free.fr/Projets/AVLD/		AVLD homepage: http://allonlinux.free.fr/Projets/AVLD/

Luxigo at 14:50, 15 September 2008

2008-09-15T14:50:36Z

← Older revision		Revision as of 14:50, 15 September 2008
Line 88:		Line 88:


	'''It breaks compatibility with applications using an older module version''' since "palette=0\|1" ~~MUST be specified with the other parameters~~ when changing the parameters ~~writing to the video device~~. But it avoid scanning twice the video buffer and remove the necessity to unload the module when the palette must be changed.		'''It breaks compatibility with applications using an older module version''' since "palette=0\|1" is now mandatory when changing the module parameters. But it avoid scanning twice the video buffer and remove the necessity to unload the module when the palette must be changed.



	AVLD homepage: http://allonlinux.free.fr/Projets/AVLD/		AVLD homepage: http://allonlinux.free.fr/Projets/AVLD/

Luxigo at 14:45, 15 September 2008

2008-09-15T14:45:02Z

← Older revision		Revision as of 14:45, 15 September 2008
Line 65:		Line 65:
	avldfeed send the specified video stream to the avld video device.		avldfeed send the specified video stream to the avld video device.

	Previous parameters are saved in ~~/home/guest~~/.avldfeed so that you can		Previous parameters are saved in ~/.avldfeed so that you can
	run the command again with no parameters or a subset, or with a		run the command again with no parameters or a subset, or with a
	configuration file as first command argument (it will		configuration file as first command argument (it will
	replace ~~/home/guest~~/.avldfeed)		replace ~/.avldfeed)