From owner-svn-doc-head@FreeBSD.ORG Mon Apr 21 15:54:17 2014 Return-Path: Delivered-To: svn-doc-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D01B377A; Mon, 21 Apr 2014 15:54:17 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BB6051637; Mon, 21 Apr 2014 15:54:17 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.8/8.14.8) with ESMTP id s3LFsH1E002421; Mon, 21 Apr 2014 15:54:17 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.8/8.14.8/Submit) id s3LFsH42002420; Mon, 21 Apr 2014 15:54:17 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201404211554.s3LFsH42002420@svn.freebsd.org> From: Dru Lavigne Date: Mon, 21 Apr 2014 15:54:17 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r44614 - head/en_US.ISO8859-1/books/handbook/multimedia X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Apr 2014 15:54:17 -0000 Author: dru Date: Mon Apr 21 15:54:17 2014 New Revision: 44614 URL: http://svnweb.freebsd.org/changeset/doc/44614 Log: Editorial review of Scanners chapter. Sponsored by: iXsystems Modified: head/en_US.ISO8859-1/books/handbook/multimedia/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/multimedia/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/multimedia/chapter.xml Mon Apr 21 12:24:37 2014 (r44613) +++ head/en_US.ISO8859-1/books/handbook/multimedia/chapter.xml Mon Apr 21 15:54:17 2014 (r44614) @@ -5,19 +5,19 @@ $FreeBSD$ --> - - - Multimedia + Synopsis @@ -92,26 +92,28 @@ - + Marc Fonvieille - Enhanced by in September 2004 + + Enhanced by - - --> - - Setting Up the Sound Card + PCI sound cards @@ -385,18 +387,19 @@ pcm7: <HDA Realtek ALC889 PCM #3 Digi - - Utilizing Multiple Sound Sources + It is often desirable to have multiple sources of sound that are able to play simultaneously. &os; uses Virtual @@ -435,19 +438,20 @@ pcm7: <HDA Realtek ALC889 PCM #3 Digi - + - Setting Default Values for Mixer Channels The default values for the different mixer channels are hardcoded in the source code of the &man.pcm.4; driver. While @@ -467,19 +471,19 @@ pcm7: <HDA Realtek ALC889 PCM #3 Digi - - - --> - - MP3 Audio + This section describes some MP3 players available for &os;, how to rip audio CD tracks, and @@ -554,13 +558,13 @@ MPEG 1.0 layer III, 128 kbit/s, 44100 Hz &prompt.root; cdda2wav -D 0,1,0 -B The - indicates the SCSI device 0,1,0, + indicates the SCSI device 0,1,0, which corresponds to the output of cdrecord -scanbus. cdda2wav will support ATAPI (IDE) CDROM drives. To rip from an IDE drive, specify the - device name in place of the SCSI unit numbers. For example, + device name in place of the SCSI unit numbers. For example, to rip track 7 from an IDE drive: &prompt.root; cdda2wav -D /dev/acd0 -t 7 @@ -711,19 +715,20 @@ MPEG 1.0 layer III, 128 kbit/s, 44100 Hz - - - --> + - Video Playback Before configuring video playback, determine the model and chipset of the video card. While @@ -1158,26 +1163,28 @@ zoom=yes - - - --> - - TV Cards + TV cards @@ -1359,49 +1366,51 @@ bktr0: Pinnacle/Miro TV, Philips SECAM t - - - --> - - Image Scanners + image scanners - In &os;, access to image scanners is provided by the - SANE (Scanner Access Now Easy) - API available through the &os; Ports - Collection. SANE will also use + In &os;, access to image scanners is provided by + SANE (Scanner Access Now Easy), which + is available in the &os; Ports Collection. + SANE will also use some &os; device drivers to provide access to the scanner hardware. - &os; supports both SCSI and USB scanners. Be sure the + &os; supports both SCSI and + USB scanners. Depending + upon the scanner interface, different device drivers are + required. Be sure the scanner is supported by SANE prior - to performing any configuration. Refer to the - supported devices list for more information about + to performing any configuration. Refer to + http://www.sane-project.org/sane-supported-devices.html + for more information about supported scanners. - - Kernel Configuration - - Both SCSI and USB interfaces are supported. Depending - upon the scanner interface, different device drivers are - required. + This chapter describes how to determine if the scanner has + been detected by &os;. It then provides an overview of how to + configure and use SANE on a &os; + system. - - USB Interface + + Checking the Scanner - The GENERIC kernel by default - includes the device drivers needed to support USB scanners. + The GENERIC kernel + includes the device drivers needed to support USB scanners. Users with a custom kernel should ensure that the following lines are present in the custom kernel configuration file: @@ -1411,31 +1420,27 @@ device uhci device ohci device ehci - Plug in the USB scanner. Use &man.dmesg.8; to determine + To determine if the USB scanner is + detected, plug it in and use dmesg to determine whether the scanner appears in the system message - buffer: + buffer. If it does, it should display a message similar to + this: ugen0.2: <EPSON> at usbus0 - These messages indicate that the scanner is using - either /dev/ugen0.2 or - /dev/uscanner0, depending on the &os; - version. For this example, a - &epson.perfection; 1650 USB scanner was used. - - - - SCSI Interface - - If the scanner uses a SCSI interface, it is important to - know which SCSI controller board it will use. Depending - upon the SCSI chipset, a custom kernel configuration file + In this example, an &epson.perfection; 1650 + USB scanner was detected on + /dev/ugen0.2. + + If the scanner uses a SCSI interface, it is important to + know which SCSI controller board it will use. Depending + upon the SCSI chipset, a custom kernel configuration file may be needed. The GENERIC kernel - supports the most common SCSI controllers. Refer to + supports the most common SCSI controllers. Refer to /usr/src/sys/conf/NOTES to determine the correct line to add to a custom kernel configuration - file. In addition to the SCSI adapter driver, the following - lines are needed in the kernel configuration file: + file. In addition to the SCSI adapter driver, the following + lines are needed in a custom kernel configuration file: device scbus device pass @@ -1448,9 +1453,9 @@ pass2: <AGFA SNAPSCAN 600 1.10> Fi pass2: 3.300MB/s transfers If the scanner was not powered-on at system boot, it - is still possible to manually force the detection by - performing a SCSI bus scan with the &man.camcontrol.8; - command: + is still possible to manually force detection by + performing a SCSI bus scan with + camcontrol: &prompt.root; camcontrol rescan all Re-scan of bus 0 was successful @@ -1458,7 +1463,7 @@ Re-scan of bus 1 was successful Re-scan of bus 2 was successful Re-scan of bus 3 was successful - The scanner should now appear in the SCSI devices + The scanner should now appear in the SCSI devices list: &prompt.root; camcontrol devlist @@ -1468,22 +1473,24 @@ Re-scan of bus 3 was successful <PHILIPS CDD3610 CD-R/RW 1.00> at scbus2 target 0 lun 0 (pass2,cd0) Refer to &man.scsi.4; and &man.camcontrol.8; for more - details about SCSI devices on &os;. - + details about SCSI devices on &os;. - SANE Configuration + <application>SANE</application> Configuration The SANE system is split in two parts: the backends (graphics/sane-backends) and the - frontends (graphics/sane-frontends). The - backends provide access to the scanner. The - SANE's supported - devices list specifies which backend will support the - image scanner. The correct backend is needed in order to use - the scanner. The frontends provide the graphical scanning - interface, xscanimage. + frontends (graphics/sane-frontends or + graphics/xsane). The + backends provide access to the scanner. Refer to + http://www.sane-project.org/sane-supported-devices.html + to determine which backend supports the + scanner. The frontends provide the graphical scanning + interface. graphics/sane-frontends + installs xscanimage while + graphics/xsane installs + xsane. After installing the graphics/sane-backends port or package, use sane-find-scanner to check the @@ -1498,44 +1505,33 @@ found SCSI scanner "AGFA SNAPSCAN 600 1. The vendor and the product model may or may not appear. - Some USB scanners require firmware to be loaded. Refer - to &man.sane-find-scanner.1; and &man.sane.7; for + Some USB scanners require firmware to be loaded. Refer + to sane-find-scanner(1) and sane(7) for details. Next, check if the scanner will be identified by a - scanning frontend. By default, the - SANE backends come with a command - line tool called &man.scanimage.1;. This command can be used + scanning frontend. The + SANE backends include + scanimage which can be used to list the devices and perform an image acquisition. Use - to list the scanner devices: - - &prompt.root; scanimage -L -device `snapscan:/dev/pass3' is a AGFA SNAPSCAN 600 flatbed scanner - - Here is the output for the USB scanner used in : + to list the scanner devices. The first + example is for a SCSI scanner and the + second is for a USB scanner: &prompt.root; scanimage -L +device `snapscan:/dev/pass3' is a AGFA SNAPSCAN 600 flatbed scanner +&prompt.root; scanimage -L device 'epson2:libusb:/dev/usb:/dev/ugen0.2' is a Epson GT-8200 flatbed scanner - In this output, + In this second example, 'epson2:libusb:/dev/usb:/dev/ugen0.2' is - the backend name (epson2) and the device - node (/dev/ugen0.2) used by the + the backend name (epson2) and + /dev/ugen0.2 is the device node used by the scanner. - - No output or a message saying that no scanners were - identified indicates that &man.scanimage.1; is unable to - identify the scanner. If this happens, edit the backend - configuration file in /usr/local/etc/sane.d/ - and define the scanner device used. - - In the above example, the USB scanner is perfectly - detected and working. - - To determine if the scanner is correctly - identified: + If scanimage is unable to + identify the scanner, this message will appear: &prompt.root; scanimage -L @@ -1544,44 +1540,36 @@ check that the scanner is plugged in, tu sane-find-scanner tool (if appropriate). Please read the documentation which came with this software (README, FAQ, manpages). - Since the scanner is not identified, edit - /usr/local/etc/sane.d/epson2.conf. In - this example, the scanner model is - &epson.perfection; 1650 and it uses the - epson2 backend. When editing, read the - help comments in the backend configuration file. Line - changes are simple: comment out all lines that have the - wrong interface for the scanner. In this example, comment - out all lines starting with the word scsi - as the scanner uses the USB interface. Then, at the end - of the file, add a line specifying the interface and the + If this happens, edit the backend + configuration file in /usr/local/etc/sane.d/ + and define the scanner device used. For example, if the undetected scanner model is + an &epson.perfection; 1650 and it uses the + epson2 backend, edit + /usr/local/etc/sane.d/epson2.conf. + When editing, add a line specifying the interface and the device node used. In this case, add the following line: - usb /dev/uscanner0 + usb /dev/ugen0.2 Save the edits and verify that the scanner is - identified: + identified with the right backend name and the device node: &prompt.root; scanimage -L -device `epson:/dev/uscanner0' is a Epson GT-8200 flatbed scanner - - The `epson:/dev/uscanner0' field now - gives the right backend name and the device node. - +device 'epson2:libusb:/dev/usb:/dev/ugen0.2' is a Epson GT-8200 flatbed scanner Once scanimage -L sees the scanner, the - configuration is complete and the device is now ready to - scan. + configuration is complete and the scanner is now ready to + use. - While &man.scanimage.1; can be used to perform an image + While scanimage can be used to perform an image acquisition from the command line, it is often preferable to use a graphical interface to perform image scanning. The graphics/sane-frontends package or port installs a simple but efficient graphical interface, xscanimage. - Xsane, which is installed with + Alternately, xsane, which is installed with the graphics/xsane package or port, is another popular graphical scanning frontend. It offers advanced features such as various scanning modes, color @@ -1590,34 +1578,33 @@ device `epson:/dev/uscanner0' is a Epson - Giving Other Users Access to the Scanner + Scanner Permissions In order to have access to the scanner, a user needs read and write permissions to the device node used by the - scanner. In the previous example, the USB scanner uses the + scanner. In the previous example, the USB scanner uses the device node /dev/ugen0.2 which is really a symlink to the real device node /dev/usb/0.2.0. The symlink and the device node are owned, respectively, by the wheel and - operator groups. Adding the user to - these groups will allow access to the scanner. However, for - security reasons, always think twice before adding a user - to any group, especially wheel. A better - solution is to create a group to make the scanner device + operator groups. While adding the user to + these groups will allow access to the scanner, it is considered insecure to + add a user + to wheel. A better + solution is to create a group and make the scanner device accessible to members of this group. This example creates a group called - usb using - &man.pw.8;: + usb: &prompt.root; pw groupadd usb Then, make the /dev/ugen0.2 symlink and the /dev/usb/0.2.0 device node accessible to the usb group with write - permissions of (0660 or - 0664. All of this is done by adding the + permissions of 0660 or + 0664 by adding the following lines to /etc/devfs.rules: