https://wiki.archlinux.org/api.php?action=feedcontributions&user=Dragonfi&feedformat=atomArchWiki - User contributions [en]2024-03-29T11:29:18ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=Festival&diff=137388Festival2011-04-15T23:18:04Z<p>Dragonfi: /* Setting default voice */ Corrected command. now it works</p>
<hr />
<div>[[Category:Accessibility (English)]]<br />
{{i18n|Festival}}<br />
[http://www.cstr.ed.ac.uk/projects/festival/ Festival] is a general multi-lingual speech synthesis system developed at CSTR ([http://www.cstr.ed.ac.uk/ Centre for Speech Technology Research]).<br />
<br />
==Installation==<br />
Festival is available in the '''extra''' repository:<br />
# pacman -S festival<br />
<br />
You will also need to install one or more voices because by default there is no voice to speak with.<br />
<br />
===American English===<br />
American English voice:<br />
# pacman -S festival-us<br />
<br />
===British English===<br />
British English voice :<br />
# pacman -S festival-english<br />
<br />
===Other voices===<br />
Other voices are available for Festival; some of them can be found in the [[AUR]].<br />
<br />
==Testing and debugging==<br />
To test festival:<br />
$ echo "This is an example. Arch is the best." | festival --tts<br />
<br />
If your hear all the example text, you sucessfully installed a TTS system.<br />
<br />
If you do not hear anything, hear something strange or just the beginning of the example sentence, continue below.<br />
<br />
===can't open /dev/dsp===<br />
If festival returns the following error message:<br />
Linux: can't open /dev/dsp<br />
<br />
Switch to ALSA output by adding these lines to the end of your .festivalrc file, or to /usr/share/festival/festival.scm ([http://ubuntuforums.org/showpost.php?p=4058268&postcount=16 source]):<br />
(Parameter.set 'Audio_Method 'Audio_Command)<br />
(Parameter.set 'Audio_Command "aplay -q -c 1 -t raw -f s16 -r $SR $FILE")<br />
<br />
===Alsa playing @ wrong speed===<br />
If the solution above gives you Mr. Squeaky Voice, you might want to try:<br />
(Parameter.set 'Audio_Method 'Audio_Command)<br />
(Parameter.set 'Audio_Command "aplay -Dplug:default -f S16_LE -r $SR $FILE")<br />
... instead.<br />
<br />
== Configuration and usage ==<br />
<br />
=== Interactive mode (testing voices etc.) ===<br />
festival has an interactive prompt you can use for testing. Some examples (with sample output)<br />
$ festival <br />
[...]<br />
festival> <br />
List available voices:<br />
festival> (voice.list)<br />
(cstr_us_awb_arctic_multisyn kal_diphone don_diphone)<br />
Set voice:<br />
festival> (voice_cstr_us_awb_arctic_multisyn)<br />
#<voice 0x1545b90><br />
Speak:<br />
festival> (SayText '"test this is a test oh no a test bla test")<br />
inserting pause after: t.<br />
Inserting pause<br />
[...]<br />
id _63 ; name t ; <br />
id _65 ; name # ; <br />
#<Utterance 0x7f7c0c144810><br />
More:<br />
festival> help <br />
"The Festival Speech Synthesizer System: Help<br />
Quit: ctrl+d or<br />
festival> (quit)<br />
<br />
=== Read a text file ===<br />
<br />
festival --tts /path/to/letter.txt<br />
<br />
=== Read a text file to wav ===<br />
<br />
cat letter.txt | text2wave -o letter.wav<br />
<br />
=== Setting default voice ===<br />
You can set a default voice by adding these lines to the end of your .festivalrc file, or to /usr/share/festival/festival.scm:<br />
(set! voice_default 'voice_cmu_us_slt_arctic_hts)<br />
You can also set the default voice in:<br />
/usr/share/festival/voices.scm<br />
You must be root and the voices are at the end of the file. Just switch them around<br />
<br />
=== Applications that can make use of festival ===<br />
<br />
One classic app that can make use of this is ping. Use this script to constantly ping a host, and return ping if success, fail is not:<br />
<br />
#!/bin/bash<br />
while [ 1 = 1 ]; do<br />
ping -c $1 && (echo "Ping" | festival --tts) || (echo "Fail" | festival --tts)<br />
done<br />
<br />
Note that this doesn't really work on multisynth voices, as they take a while to prepare before playing.</div>Dragonfihttps://wiki.archlinux.org/index.php?title=VCS_package_guidelines&diff=134686VCS package guidelines2011-03-25T07:38:02Z<p>Dragonfi: Added tip to remove VCS directories from package.</p>
<hr />
<div>[[Category:Package development (English)]]<br />
[[Category:Guidelines (English)]]<br />
{{i18n|VCS PKGBUILD Guidelines}}<br />
{{Article summary start}}<br />
{{Article summary text|Creating PKGBUILDs for software managed with version control systems.}}<br />
{{Article summary heading|Related}}<br />
{{Article summary wiki|Arch Build System}}<br />
{{Article summary wiki|Arch User Repository}}<br />
{{Article summary wiki|Creating Packages}}<br />
{{Article summary wiki|makepkg}}<br />
{{Article summary wiki|pacman}}<br />
{{Article summary wiki|PKGBUILD}}<br />
{{Article summary end}}<br />
<br />
Guidelines for creating PKGBUILDs for software managed with version control systems.<br />
<br />
== Prototypes ==<br />
<br />
The {{Package Official|abs}} package provides prototypes for cvs, svn, git, mercurial, and darcs PKGBUILDs. When abs is installed, you can find them in {{Filename|/usr/share/pacman}}.<br />
<br />
== Guidelines ==<br />
<br />
* Properly suffix {{Codeline|pkgname}} with {{Codeline|-cvs}}, {{Codeline|-svn}}, {{Codeline|-hg}}, {{Codeline|-darcs}}, {{Codeline|-bzr}} or {{Codeline|-git}}. If the package tracks a moving development trunk it should be given a suffix. If the package fetches a release from a VCS tag then it should not be given a suffix. Use this rule of thumb: if the output of the package depends on the time at which it was compiled, append a suffix; otherwise do not.<br />
<br />
* When [[makepkg]] is run, by default it will check for newer revisions and then update the {{Codeline|pkgver}} in the PKGBUILD. Look at {{Codeline|--holdver}} in [http://www.archlinux.org/pacman/makepkg.8.html man makepkg] if you want otherwise. {{Codeline|--holdver}} only works for cvs and svn, which allow checkout of older revisions.<br />
<br />
* Check for package conflicts. For example ''fluxbox-svn'' will conflict with ''fluxbox''. In this case, you need to use {{Codeline|1=conflicts=('fluxbox')}}.<br />
<br />
* Use the {{Codeline|provides}} field so that packages that require the non-VCS package can be installed ({{Codeline|1=provides=('fluxbox')}}).<br />
<br />
* You should AVOID using {{Codeline|1=replaces=...}} as it generally causes unnecessary problems.<br />
<br />
* When using/defining the cvsroot, use {{Codeline|anonymous:@}} rather than {{Codeline|anonymous@}} to avoid a password prompt and having to enter a blank password ''OR'' use {{Codeline|anonymous:password@}} if a password is required.<br />
<br />
* Though it is often unnecessary to use the {{Codeline|pkgrel}} field when building CVS/SVN/GIT packages (changes to the package are usually often and will be reflected in the {{Codeline|pkgver}}), makepkg will require it.<br />
<br />
* Don't forget to include the appropriate VCS tool (cvs, subversion, git, ...) in {{Codeline|1=makedepends=...}}.<br />
<br />
* To preserve the integrity of the checked-out code consider copying the original build directory if you have to make edits. For example, having checked out source code to {{Filename|src/$_cvsmod}} from {{Filename|$startdir}} you can use:<br />
<br />
mkdir src/$_cvsmod-build<br />
<br />
cd src/$_cvsmod-build<br />
../$_cvsmod/configure<br />
<br />
or:<br />
<br />
cp -r src/$_cvsmod src/$_cvsmod-build<br />
cd src/$_cvsmod-build<br />
<br />
* With the introduction of the [[AUR]], it is most important to avoid using backtick execution to create package variables. makepkg will automatically bump the {{Codeline|pkgver}} anyway when building the package (unless {{Codeline|--holdver}} is used).<br />
<br />
== Tips ==<br />
<br />
* You should make sure that there are no VCS directories and files left over in your package. If there are, you may want to remove them, by adding a command similar to this one at the end of the the package() script:<br />
<br />
rm -rf `find "$pkgdir" -type d -name ".svn"`<br />
<br />
* When using Git, one can speed up the cloning operation using the {{Codeline|1=--depth=1}} parameter. This creates a shallow clone, and has only the last change history - since histories are unimportant for builds most of the time.<br />
<br />
git clone git://hostname.dom/project.git --depth=1</div>Dragonfihttps://wiki.archlinux.org/index.php?title=Laptop_Mode_Tools&diff=127412Laptop Mode Tools2011-01-09T08:25:48Z<p>Dragonfi: /* Hard disks */</p>
<hr />
<div>[[Category:Laptops (English)]]<br />
[[Category:Power management (English)]]<br />
{{Expansion}}<br />
{{Article summary start}}<br />
{{Article summary text|Overview of the Laptop Mode Tools power management suite for notebooks.}}<br />
{{Article summary heading|Related}}<br />
{{Article summary wiki|acpid}}<br />
{{Article summary wiki|cpufrequtils}}<br />
{{Article summary wiki|pm-utils}}<br />
{{Article summary heading|Resources}}<br />
{{Article summary link|Laptop Mode Tools|http://samwel.tk/laptop_mode/}}<br />
{{Article summary link|Mailing List Archives|http://mailman.samwel.tk/pipermail/laptop-mode/ }}<br />
{{Article summary link|Less Watts - Official Site|http://www.lesswatts.org/index.php}}<br />
{{Article summary link|Laptop - ArchWiki|http://wiki.archlinux.org/index.php/Laptop|lll}}<br />
<br />
<br />
{{Article summary end}}<br />
<br />
==Preface==<br />
The Linux kernel, starting from version 2.6.6, contains a feature called ''laptop mode''. This feature is also present in the Linux 2.4 series starting from version 2.4.23. When enabled, the kernel allows the hard drive to spin down more often, resulting in significant power savings. Laptop Mode Tools (LTM) evolved from a simple program that controlled the hard drives to a centralized power saving solution providing a wide selection of options and can perform a number of varying power saving functions across separate subsystems simultaneously. Combined with [[acpid]], [[cpufrequtils]] and [[pm-utils]], LTM provides most users with a complete notebook power management suite.<br />
<br />
==Installation==<br />
{{Package Official|laptop-mode-tools}} is part of the official [[Official Repositories|Arch Linux [extra] repository]].<br />
# pacman -S laptop-mode-tools<br />
<br />
==Configuration==<br />
Add {{Codeline|laptop-mode}} to the {{Codeline|DAEMONS}} array in {{Filename|/etc/rc.conf}}:<br />
DAEMONS=(...laptop-mode...)<br />
<br />
Configuration is handled through the primary configuration file {{Filename|/etc/laptop-mode/laptop-mode.conf}} and through the configuration of dozens of feature-specific files in {{Filename|/etc/laptop-mode/conf.d/*}}. Recent versions of LTM are able to automatically enable commonly used {{Filename|conf.d/*}} settings by way of the {{Codeline|ENABLE_AUTO_MODULES}} variable in {{Filename|/etc/laptop-mode/laptop-mode.conf}}.<br />
<br />
===Disks===<br />
====Hard disks====<br />
Spinning down the hard drive through {{codeline|hdparm -S}} valuessaves power and makes everything a lot more quiet. By using the readahead function you can allow the drives to spin down more often even though you are using the computer. LTM can also establish {{codeline|hdparm -B}} values. 1 is maximum hard drive power saving and 254 is minimum. Set this value to 254 when on AC and 1 when on battery. If you move around a lot when on battery it might be a good idea to set it higher (eg. 128)<sup>[clarifiy]</sup>. {{codeline|hdparm -S}} and {{codeline|hdparm -B}} values are configured in {{Filename|/etc/laptop-mode/laptop-mode.conf}}.<br />
<br />
====HAL polling====<br />
<br />
# hal-polling.conf<br />
# ThinkPad T40/T42/T60 Example<br />
#<br />
DEBUG=0<br />
CONTROL_HAL_POLLING=1<br />
BATT_DISABLE_HAL_POLLING=1<br />
AC_DISABLE_HAL_POLLING=1<br />
HAL_POLLING_DEVICES="/dev/scd?"<br />
<br />
===Processor===<br />
====CPU frequency====<br />
<br />
# cpufreq.conf<br />
# ThinkPad T40/T42/T60 Example<br />
#<br />
CONTROL_CPU_FREQUENCY=1<br />
BATT_CPU_MAXFREQ=fastest<br />
BATT_CPU_MINFREQ=slowest<br />
BATT_CPU_GOVERNOR=ondemand<br />
BATT_CPU_IGNORE_NICE_LOAD=1<br />
LM_AC_CPU_MAXFREQ=fastest<br />
LM_AC_CPU_MINFREQ=slowest<br />
LM_AC_CPU_GOVERNOR=ondemand<br />
LM_AC_CPU_IGNORE_NICE_LOAD=1<br />
NOLM_AC_CPU_MAXFREQ=fastest<br />
NOLM_AC_CPU_MINFREQ=slowest<br />
NOLM_AC_CPU_GOVERNOR=ondemand<br />
NOLM_AC_CPU_IGNORE_NICE_LOAD=0<br />
CONTROL_CPU_THROTTLING=0<br />
<br />
* See [[cpufrequtils]] for details on how to install and configure the {{Package Official|cpufrequtil}} package for use with LMT.<br />
<br />
===Device and bus===<br />
====Intel SATA====<br />
* Enable the Intel SATA AHCI controller Aggressive Link Power Management feature to set the disk link into a very low power mode in the absence of disk IO.<br />
# intel-sata-powermgmt.conf<br />
# ThinkPad T40/T42/T60 Example<br />
#<br />
DEBUG=0<br />
CONTROL_INTEL_SATA_POWER=1<br />
BATT_ACTIVATE_SATA_POWER=1<br />
LM_AC_ACTIVATE_SATA_POWER=1<br />
NOLM_AC_ACTIVATE_SATA_POWER=0<br />
<br />
{{Note|Review the well-documented {{Filename|/etc/laptop-mode/conf.d/intel-sata-powermgmt.conf}} file for additional configuration details.}}<br />
<br />
====USB autosuspend====<br />
# usb-autosuspend.conf<br />
# ThinkPad T40/T42/T60 Example<br />
#<br />
DEBUG=0<br />
CONTROL_USB_AUTOSUSPEND=1<br />
BATT_SUSPEND_USB=1<br />
LM_AC_SUSPEND_USB=1<br />
NOLM_AC_SUSPEND_USB=0<br />
AUTOSUSPEND_TIMEOUT=2<br />
<br />
{{Note|Review the well-documented {{Filename|/etc/laptop-mode/conf.d/usb-autosuspend.conf}} file for additional configuration details.}}<br />
<br />
===Display and graphics===<br />
====LCD brightness====<br />
* Available brightness values for certain laptops can can be obtained by running following two commands:<br />
$ cat /proc/acpi/video/VID/LCD/brightness<br />
<br />
For [http://en.wikipedia.org/wiki/ThinkPad ThinkPad] notebooks, minimum brightness values can be obtained by running one of the following two commands:<br />
$ cat /sys/class/backlight/acpi_video0/brightness<br />
<br />
$ cat /sys/class/backlight/thinkpad_screen/brightness<br />
<br />
* For [http://en.wikipedia.org/wiki/ThinkPad ThinkPad] notebooks, maximum brightness values can be obtained by running one of the following two commands:<br />
$ cat /sys/class/backlight/acpi_video0/max_brightness<br />
<br />
$ cat /sys/class/backlight/thinkpad_screen/max_brightness<br />
<br />
# lcd-brightness.conf<br />
# ThinkPad T40/T42 Example<br />
#<br />
DEBUG=0<br />
CONTROL_BRIGHTNESS=1<br />
BATT_BRIGHTNESS_COMMAND="echo 0"<br />
LM_AC_BRIGHTNESS_COMMAND="echo 7"<br />
NOLM_AC_BRIGHTNESS_COMMAND="echo 7"<br />
BRIGHTNESS_OUTPUT="/sys/class/backlight/thinkpad_screen/brightness"<br />
<br />
# lcd-brightness.conf<br />
# ThinkPad T60 Example<br />
#<br />
DEBUG=0<br />
CONTROL_BRIGHTNESS=1<br />
BATT_BRIGHTNESS_COMMAND="echo 0"<br />
LM_AC_BRIGHTNESS_COMMAND="echo 7"<br />
NOLM_AC_BRIGHTNESS_COMMAND="echo 7"<br />
BRIGHTNESS_OUTPUT="/sys/class/backlight/acpi_video0/brightness"<br />
<br />
{{Note|Review the well-documented {{Filename|/etc/laptop-mode/conf.d/lcd-brightness.conf}} file for additional configuration details.}}<br />
<br />
====Terminal blanking====<br />
<br />
# terminal-blanking.conf<br />
# ThinkPad T40/T42/T60 Example<br />
#<br />
DEBUG=0<br />
CONTROL_TERMINAL=1<br />
TERMINALS="/dev/tty1"<br />
BATT_TERMINAL_BLANK_MINUTES=1<br />
BATT_TERMINAL_POWERDOWN_MINUTES=2<br />
LM_AC_TERMINAL_BLANK_MINUTES=10<br />
LM_AC_TERMINAL_POWERDOWN_MINUTES=10<br />
NOLM_AC_TERMINAL_BLANK_MINUTES=10<br />
NOLM_AC_TERMINAL_POWERDOWN_MINUTES=10<br />
<br />
{{Note|Review the well-documented {{Filename|/etc/laptop-mode/conf.d/terminal-blanking.conf}} file for additional configuration details.}}<br />
<br />
===Networking===<br />
====Ethernet====<br />
# ethernet.conf<br />
# ThinkPad T40/T42/T60 Example<br />
#<br />
DEBUG=0<br />
CONTROL_ETHERNET=1<br />
LM_AC_THROTTLE_ETHERNET=0<br />
NOLM_AC_THROTTLE_ETHERNET=0<br />
DISABLE_WAKEUP_ON_LAN=1<br />
DISABLE_ETHERNET_ON_BATTERY=1<br />
ETHERNET_DEVICES="eth0"<br />
<br />
====Wireless LAN====<br />
Wireless interface power management settings are hardware-dependent, and thus a bit trickier to configure. Depending on the wireless chipset, the settings are managed in one of the following three files:<br />
#{{Filename|/etc/laptop-mode/conf.d/wireless-power.conf}} for a generic method of saving power (using "iwconfig wlan0 power on/off"). This applies to most chipsets (that is, anything but Intel chipsets listed below).<br />
#{{Filename|/etc/laptop-mode/conf.d/wireless-ipw-power.conf}} for Intel chipsets driven by the old ipw driver. This apply to IPW3945, IPW2200 and IPW2100. It currently (as of LMT 1.55-1) uses iwpriv for IPW3945, and a combination of iwconfig and iwpriv settings for IPW2100 and IPW220. See {{Filename|/usr/share/laptop-mode-tools/modules/wireless-ipw-power}} for details. (note that the ipw3945 isn't used anymore, see below)<br />
#{{Filename|/etc/laptop-mode/conf.d/wireless-iwl-power.conf}} for Intel chipsets driven by modules iwl4965, iwl3945 and iwlagn (this latter supports chipsets 4965, 5100, 5300, 5350, 5150, 1000, and 6000)<br />
Note that activating the three of them shouldn't be much of a problem, since LTM detects the module used by the interface and acts accordingly.<br />
<br />
The supported modules for each config file, indicated above, are taken directly from LTM. However, this seems to be a bit out-of-date, since the current 2.6.34 kernel doesn't provide the ipw3945 and iwl4965 modules anymore (3945 chipset uses iwl3945 instead, and 4965 uses the generic module iwlagn). This is only brought here for information, as this doesn't (or shouldn't) affect the way LTM works.<br />
<br />
There is a known issue with some chipsets running with the iwlagn module (namely, the 5300 chipset, and maybe others). On those chipsets, the following settings of {{Filename|/etc/laptop-mode/conf.d/wireless-iwl-power.conf}} :<br />
IWL_AC_POWER<br />
IWL_BATT_POWER<br />
are ignored, because the {{Filename|/sys/class/net/wlan*/device/power_level}} file doesn't exist. Instead, the standard method (with "iwconfig wlan0 power on/off") is automatically used.<br />
<br />
===Audio===<br />
====AC97====<br />
<br />
# ac97-powersave.conf<br />
# ThinkPad T40/T42/T60 Example<br />
#<br />
DEBUG=0<br />
CONTROL_AC97_POWER=1<br />
<br />
====Intel HDA====<br />
<br />
# intel-hda-powersave.conf<br />
# ThinkPad T40/T42/T60 Example<br />
#<br />
DEBUG=0<br />
CONTROL_INTEL_HDA_POWER=1<br />
BATT_INTEL_HDA_POWERSAVE=1<br />
LM_AC_INTEL_HDA_POWERSAVE=1<br />
NOLM_AC_INTEL_HDA_POWERSAVE=0<br />
INTEL_HDA_DEVICE_TIMEOUT=10<br />
INTEL_HDA_DEVICE_CONTROLLER=0<br />
<br />
==Tips and tricks==<br />
===Aliases===<br />
===lm-profiler===<br />
===Disabling===<br />
<br />
==Troubleshooting==</div>Dragonfi