User Manual

The UpStage V2.1 User Manual on Floss Manuals (June 2011)

Installation Manuals

UpStage v2.4.2 Installation Manual – coming soon … (August 2012)

UpStage v2.1 Installation Video (June 2009)

How to Install the Unstable version 2.4.0

UpStage Developer Documentation

• Some hints on how to use Subversion for UpStage development

Other UpStage Documentation

• Blog article on how to accelerate an UpStage installation using a reverse proxy (January 2012)
• Streaming Audio Report, prepared by the AUT 2008 team to assess the feasability of streaming audio via UpStage.
• Gnash Compatability Report, prepared by the AUT 2007 team to assess whether Gnash (an open source alternative to Flash) would be compatible with UpStage. The report concludes that at this stage, it would compromise UpStage’s functionality to an extent that makes it not a good alternative.
• Linux tips for those who are about to install UpStage on a Linux (Debian Etch) server; AUT student team, August 2007.
• Setting up an UpStage Debian Etch Server for Windows Users, AUT student team, August 2007.
• Setting up an UpStage Linux server for Windows users, doocumentation from the AUT student project group, May 2006 (PDF 208 KB) – this refers to UpStage 1 but may still be useful for UpStage 2.
• Links to articles, book chapters, academic thesis and online resources that feature UpStage are available on the research page of the UpStage web site.

Cmu Voices:

wget -c https://www.speech.cs.cmu.edu/cmu_arctic/packed/cmu_us_awb_arctic-0.90-release.tar.bz2

wget -c https://www.speech.cs.cmu.edu/cmu_arctic/packed/cmu_us_bdl_arctic-0.95-release.tar.bz2

wget -c https://www.speech.cs.cmu.edu/cmu_arctic/packed/cmu_us_clb_arctic-0.95-release.tar.bz2

wget -c https://www.speech.cs.cmu.edu/cmu_arctic/packed/cmu_us_jmk_arctic-0.95-release.tar.bz2

wget -c https://www.speech.cs.cmu.edu/cmu_arctic/packed/cmu_us_rms_arctic-0.95-release.tar.bz2

wget -c https://www.speech.cs.cmu.edu/cmu_arctic/packed/cmu_us_slt_arctic-0.95-release.tar.bz2

UpStage version numbering system

We are using a three-number version system, which is based on this formula: baseversion.x.y, where x denotes a feature change and y denotes bug fixes.

Every commit to SourceForge should involve a number change, that relates to whether features have been added or bugs fixed.