Historical:Webcams - Revision history

C256zhao: C256zhao moved page Webcams to Historical:Webcams

2026-03-24T13:22:18Z

C256zhao moved page Webcams to Historical:Webcams

← Older revision	Revision as of 08:22, 24 March 2026
(No difference)

Ztseguin: Office webcam feed is no longer available

2016-06-28T19:48:28Z

Office webcam feed is no longer available

← Older revision		Revision as of 14:48, 28 June 2016
Line 1:		Line 1:
	~~A [http://csclub.uwaterloo.ca/office/webcam~~ live webcam feed] of the office is ~~available~~ ~~online~~.		The live webcam feed of the office is no longer available.

			See the previous history of this page for historical information about the webcam feed.
	== Operation ==

	We use [http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome Motion] to serve this webcam feed. It uses video4linux to read from the webcam, and pushes frames to the client (who maintains an HTTP connection). Frames are pushed when a certain amount of motion has detected, or a set maximum amount of time has passed since the last frame. One of these runs on each of our webcam hosts ([[Machine_List#maltodextrin\|maltodextrin]] and [[Machine_List#bit-shifter\|bit-shifter]]). Motion includes a builtin tiny HTTP server (running on port 8081 in our case) which serves a sequence of JPEG images to the browser. An ordinary <tt><img></tt> tag is embedded in the web page, and browsers will update the image when they receive a new one over the HTTP connection.

	The Motion documentation is fairly self-explanatory, but here are the options we use for the webcam server part:

	webcam_port 8081
	webcam_quality 30
	webcam_motion on
	webcam_maxrate 5
	webcam_localhost off
	webcam_limit 1000


	We also have a couple of udev rules to map the camera devices to a constant location and to disable any on-camera mice. These rules exist at /etc/udev/rules.d/99-csc-webcams.rules on the right machines.

	=== maltodextrin cam ===

	# Create symlink for camera device at /dev/csc/malto-cam
	SUBSYSTEMS=="usb", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="0808", ATTRS{serial}=="714B8C60", ATTRS{bInterfaceClass}=="0e", SYMLINK+="csc/malto-cam", GROUP="motion"

	# Disable the cam's mic
	SUBSYSTEMS=="usb", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="0808", ATTRS{serial}=="714B8C60", ATTRS{bInterfaceClass}=="01", ATTR{authorized}="0"

	=== bit-shifter cam ===

	# Create symlink for camera device at /dev/csc/bitshifter-cam
	SUBSYSTEM=="video4linux", SUBSYSTEMS=="usb", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="082c", ATTRS{serial}=="AF2F2AD0", SYMLINK+="csc/bitshifter-cam", GROUP="motion"

	== Webcam Counter ==

	Also known as the "implicit consent sign". The sign is connected via serial to bit-shifter. Associated scripts which update the counter are found in /opt/camcount/ on bit-shifter.

	If the counter isn't working, /opt/camcount/daemon likely needs to be restarted.

	== Hardware ==

	=== Logitech QuickCam Messenger ===
	* USB IDs: 046d:08da
	* Kernel module: gspca (gspca-source)
	* Max resolution: 640x480

	=== Logitech QuickCam Zoom ===
	* USB IDs: 046d:08b3
	* Kernel module: pwc
	* Max resolution: 640x480

	=== Logitech QuickCam Web ===
	* USB IDs: 046d:0850
	* Kernel module: quickcam (qc-usb-source package)
	* Max resolution: 480x360

	=== Logitech QuickCam Chat ===
	* USB IDs: 046d:092c
	* Kernel module: gspca (gspca-source)
	* Max resolution: 480x360

	[[Category:Hardware]]

Laden: /* bit-shifter cam */

2014-10-01T16:45:21Z

bit-shifter cam

← Older revision		Revision as of 11:45, 1 October 2014
Line 28:		Line 28:

	# Create symlink for camera device at /dev/csc/bitshifter-cam		# Create symlink for camera device at /dev/csc/bitshifter-cam
	SUBSYSTEMS=="usb", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="082c", ATTRS{serial}=="AF2F2AD0", SYMLINK+="csc/bitshifter-cam", GROUP="motion"		SUBSYSTEM=="video4linux", SUBSYSTEMS=="usb", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="082c", ATTRS{serial}=="AF2F2AD0", SYMLINK+="csc/bitshifter-cam", GROUP="motion"

	== Webcam Counter ==		== Webcam Counter ==

Laden: /* Operation */

2014-09-29T16:03:11Z

Operation

@@ Line 13: / Line 13: @@
  webcam_localhost off
  webcam_limit 1000
 == Webcam Counter ==

Jladan at 02:46, 30 May 2013

2013-05-30T02:46:27Z

← Older revision		Revision as of 21:46, 29 May 2013
Line 13:		Line 13:
	webcam_localhost off		webcam_localhost off
	webcam_limit 1000		webcam_limit 1000

			== Webcam Counter ==

			Also known as the "implicit consent sign". The sign is connected via serial to bit-shifter. Associated scripts which update the counter are found in /opt/camcount/ on bit-shifter.

			If the counter isn't working, /opt/camcount/daemon likely needs to be restarted.

	== Hardware ==		== Hardware ==

Jbroman at 13:41, 5 September 2010

2010-09-05T13:41:38Z

← Older revision		Revision as of 08:41, 5 September 2010
Line 3:		Line 3:
	== Operation ==		== Operation ==

	We use [http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome Motion] to serve this webcam feed. It uses video4linux to read from the webcam, and pushes frames to the client (who maintains an HTTP connection). Frames are pushed when a certain amount of motion has detected, or a set maximum amount of time has passed since the last frame. One of these runs on each of our webcam hosts ([[Machine_List#maltodextrin\|maltodextrin]] and [[Machine_List#bit-shifter\|bit-shifter]]~~, though the latter isn't working most of the time~~). Motion includes a builtin tiny HTTP server (running on port 8081 in our case) which serves a sequence of JPEG images to the browser. An ordinary <tt><img></tt> tag is embedded in the web page, and browsers will update the image when they receive a new one over the HTTP connection.		We use [http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome Motion] to serve this webcam feed. It uses video4linux to read from the webcam, and pushes frames to the client (who maintains an HTTP connection). Frames are pushed when a certain amount of motion has detected, or a set maximum amount of time has passed since the last frame. One of these runs on each of our webcam hosts ([[Machine_List#maltodextrin\|maltodextrin]] and [[Machine_List#bit-shifter\|bit-shifter]]). Motion includes a builtin tiny HTTP server (running on port 8081 in our case) which serves a sequence of JPEG images to the browser. An ordinary <tt><img></tt> tag is embedded in the web page, and browsers will update the image when they receive a new one over the HTTP connection.

	The Motion documentation is fairly self-explanatory, but here are the options we use for the webcam server part:		The Motion documentation is fairly self-explanatory, but here are the options we use for the webcam server part:

Jbroman at 20:48, 22 May 2010

2010-05-22T20:48:19Z

← Older revision		Revision as of 15:48, 22 May 2010
Line 3:		Line 3:
	== Operation ==		== Operation ==

	We use [http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome Motion] to serve this webcam feed. It uses video4linux to read from the webcam, and pushes frames to the client (who maintains an HTTP connection). Frames are pushed when a certain amount of motion has detected, or a set maximum amount of time has passed since the last frame. One of these runs on each of our webcam hosts ([[Machine_List#maltodextrin\|maltodextrin]] and [[Machine_List#bit-shifter\|bit-shifter]], though the latter isn't working most of the time). Motion includes a builtin tiny HTTP server (running on port 8081 in our case) which serves a sequence of JPEG images to the browser. An ordinary <img> tag is embedded in the web page, and browsers will update the image when they receive a new one over the HTTP connection.		We use [http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome Motion] to serve this webcam feed. It uses video4linux to read from the webcam, and pushes frames to the client (who maintains an HTTP connection). Frames are pushed when a certain amount of motion has detected, or a set maximum amount of time has passed since the last frame. One of these runs on each of our webcam hosts ([[Machine_List#maltodextrin\|maltodextrin]] and [[Machine_List#bit-shifter\|bit-shifter]], though the latter isn't working most of the time). Motion includes a builtin tiny HTTP server (running on port 8081 in our case) which serves a sequence of JPEG images to the browser. An ordinary <tt><img></tt> tag is embedded in the web page, and browsers will update the image when they receive a new one over the HTTP connection.

	The Motion documentation is fairly self-explanatory, but here are the options we use for the webcam server part:		The Motion documentation is fairly self-explanatory, but here are the options we use for the webcam server part:

Jbroman: how the webcam works (adapted from a syscom email in April)

2010-05-22T20:47:34Z

how the webcam works (adapted from a syscom email in April)

← Older revision		Revision as of 15:47, 22 May 2010
Line 1:		Line 1:
			A [http://csclub.uwaterloo.ca/office/webcam live webcam feed] of the office is available online.
⚫	== Logitech QuickCam Messenger ==

			== Operation ==

			We use [http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome Motion] to serve this webcam feed. It uses video4linux to read from the webcam, and pushes frames to the client (who maintains an HTTP connection). Frames are pushed when a certain amount of motion has detected, or a set maximum amount of time has passed since the last frame. One of these runs on each of our webcam hosts ([[Machine_List#maltodextrin\|maltodextrin]] and [[Machine_List#bit-shifter\|bit-shifter]], though the latter isn't working most of the time). Motion includes a builtin tiny HTTP server (running on port 8081 in our case) which serves a sequence of JPEG images to the browser. An ordinary <img> tag is embedded in the web page, and browsers will update the image when they receive a new one over the HTTP connection.

			The Motion documentation is fairly self-explanatory, but here are the options we use for the webcam server part:

			webcam_port 8081
			webcam_quality 30
			webcam_motion on
			webcam_maxrate 5
			webcam_localhost off
			webcam_limit 1000

			== Hardware ==

		⚫	=== Logitech QuickCam Messenger ===
	* USB IDs: 046d:08da		* USB IDs: 046d:08da
	* Kernel module: gspca (gspca-source)		* Kernel module: gspca (gspca-source)
	* Max resolution: 640x480		* Max resolution: 640x480

	== Logitech QuickCam Zoom ==		=== Logitech QuickCam Zoom ===
	* USB IDs: 046d:08b3		* USB IDs: 046d:08b3
	* Kernel module: pwc		* Kernel module: pwc
	* Max resolution: 640x480		* Max resolution: 640x480

	== Logitech QuickCam Web ==		=== Logitech QuickCam Web ===
	* USB IDs: 046d:0850		* USB IDs: 046d:0850
	* Kernel module: quickcam (qc-usb-source package)		* Kernel module: quickcam (qc-usb-source package)
	* Max resolution: 480x360		* Max resolution: 480x360

	== Logitech QuickCam Chat ==		=== Logitech QuickCam Chat ===
	* USB IDs: 046d:092c		* USB IDs: 046d:092c
	* Kernel module: gspca (gspca-source)		* Kernel module: gspca (gspca-source)

Mspang at 04:39, 12 May 2010

2010-05-12T04:39:08Z

← Older revision		Revision as of 23:39, 11 May 2010
Line 1:		Line 1:
	The CSC owns a few webcams.

	As far as I can tell, gspca only supports v4l2 in recent kernels.
	Camserv only supports v4l1 though, so to get it to work, need to
	export LD_PRELOAD=/usr/lib/libv4l/v4l1compat.so in the environment
	that camserv runs.

	== Logitech QuickCam Messenger ==		== Logitech QuickCam Messenger ==
	* USB IDs: 046d:08da		* USB IDs: 046d:08da

Jbroman: add to Hardware category

2010-03-23T00:22:08Z

add to Hardware category

← Older revision		Revision as of 19:22, 22 March 2010
Line 25:		Line 25:
	* Kernel module: gspca (gspca-source)		* Kernel module: gspca (gspca-source)
	* Max resolution: 480x360		* Max resolution: 480x360

			[[Category:Hardware]]