[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Traverso-commit] traverso/doc/manual/en cdburning.tex installati...
|
From: |
Remon Sijrier |
|
Subject: |
[Traverso-commit] traverso/doc/manual/en cdburning.tex installati... |
|
Date: |
Sat, 16 Jun 2007 15:32:29 +0000 |
CVSROOT: /sources/traverso
Module name: traverso
Changes by: Remon Sijrier <r_sijrier> 07/06/16 15:32:29
Modified files:
doc/manual/en : cdburning.tex installation.tex mixing.tex
recording.tex setup.tex traverso-manual01.tex
Log message:
doc update
CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/traverso/doc/manual/en/cdburning.tex?cvsroot=traverso&r1=1.1&r2=1.2
http://cvs.savannah.gnu.org/viewcvs/traverso/doc/manual/en/installation.tex?cvsroot=traverso&r1=1.1&r2=1.2
http://cvs.savannah.gnu.org/viewcvs/traverso/doc/manual/en/mixing.tex?cvsroot=traverso&r1=1.1&r2=1.2
http://cvs.savannah.gnu.org/viewcvs/traverso/doc/manual/en/recording.tex?cvsroot=traverso&r1=1.1&r2=1.2
http://cvs.savannah.gnu.org/viewcvs/traverso/doc/manual/en/setup.tex?cvsroot=traverso&r1=1.1&r2=1.2
http://cvs.savannah.gnu.org/viewcvs/traverso/doc/manual/en/traverso-manual01.tex?cvsroot=traverso&r1=1.1&r2=1.2
Patches:
Index: cdburning.tex
===================================================================
RCS file: /sources/traverso/traverso/doc/manual/en/cdburning.tex,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- cdburning.tex 24 May 2007 21:45:34 -0000 1.1
+++ cdburning.tex 16 Jun 2007 15:32:28 -0000 1.2
@@ -1,5 +1,5 @@
\section{Requirements}
-This chapter describes how to arrange and write a Red Book compatible audio
CD. Traverso uses \texttt{cdrdao} to actually write the CD, so this program
must be installed on the system. \texttt{cdrdao} is available from the official
repositories of all major and up-to-date Linux distributions, it is thus
recommended to install it via the distribution's package manager. It is also
available for Microsoft Windows and Apple OS X (via fink and the MacPorts), but
it requires some more effort to get installed on these systems. You can easily
check if the tool is already installed by entering \texttt{cdrdao} on a
console. If you get an output like this, you are ready to proceed:
+This chapter describes how to arrange and write a Red Book compatible audio
CD. Traverso uses \texttt{cdrdao} to actually write the CD, so this program
must be installed on the system. \texttt{cdrdao} is available from the official
repositories of all major and up-to-date Linux distributions, it is thus
recommended to install it via the distribution's package manager. The Windows
and Mac OS X installer takes care of installing cdrdao for you, so if you are
on one of these platforms, you skip this section!
\footnotesize
\begin{verbatim}
@@ -19,7 +19,7 @@
\end{verbatim}
\normalsize
-If the command was not found, the following sections explain how to install
\texttt{cdrdao} on various platforms.
+If the command was not found, the next section explains how to install
\texttt{cdrdao} on the Linux platform.
\subsection{Linux}
Installing \texttt{cdrdao} on Linux is straight forward, since it is part of
all major distributions. Use your distribution's package manager (e.\,g.
Synaptic or Adept on (K)Ubuntu, Yast on SuSE), search for \texttt{cdrdao} and
install the binary package. Alternatively, you can install it from a terminal.
The commands will differ depending on the distribution. For (K,X)Ubuntu, enter
the following lines in a terminal:
@@ -29,38 +29,23 @@
sudo apt-get install cdrdao
\end{verbatim}
-\subsection{Apple OS X}
-Note: The installation on OS X requires a working internet connection, and the
user must be allowed to get administrator privileges. You can install
\texttt{cdrdao} from the MacPorts, but it can happen that only a source package
is available for your version of OS X. First install MacPorts from
\cite{macports}. Then open a terminal and enter:
-
-\begin{verbatim}
-sudo /opt/local/bin/port install cdrdao -v
-\end{verbatim}
-This will take a while, because several dependencies will be installed, too.
But after the process has finished, you should be able to run \texttt{cdrdao}
by entering:
-
-\begin{verbatim}
-/opt/local/bin/cdrdao
-\end{verbatim}
-which should give the same output as shown above. If something went wrong,
please seek help from the MacPorts community.
-
-\subsection{Microsoft Windows}
-Traverso will install everything necessary to burn CDs automatically,
including cdrdao. A working internet connection is required, because the latest
cd-writing driver will be downloaded during the installation.
\section{Tracks and Markers}
-There are basically two ways of defining tracks for a CD. Each song can be a
track, or the entire CD can be arranged in the timeline of a song and tracks
are defined by markers. Combinations of the two ways are also possible. Let's
have a closer look at these two concepts.
+There are basically two ways of defining tracks for a CD. Each sheet can be a
track, or the entire CD can be arranged in the timeline of a sheet and tracks
are defined by markers. Combinations of the two ways are also possible. Let's
have a closer look at these two concepts.
-\subsection{A Song is a CD-Track}
-As you may have noticed, Traverso allows to have several songs in a project.
Some people like this feature, as one can combine all songs of an album in one
project, and still focus on one song at a time. If you want to write a CD
containing all songs of your project, make sure you check the ``All Songs''
button in the export dialogue. Each song will be rendered to a track, from
position 00:00:00 up to the end of the last audio clip, and consequently each
song will become a track on the CD.
+\subsection{A Sheet is a CD-Track}
+As you may have noticed, Traverso allows to have several sheets in a project.
Some people like this feature, as one can combine all sheets of an album in one
project, and still focus on one sheet at a time. If you want to write a CD
containing all sheets of your project, make sure you check the ``All sheets''
button in the export dialogue. Each sheet will be rendered to a track, from
position 00:00:00 up to the end of the last audio clip, and consequently each
sheet will become a track on the CD.
\subsection{CD in a timeline}
Sometimes it is important to fine-tune the transition from one track to the
next, e.\,g. by adding a little bit of silence in between, or by fading the
previous track into the next one. In that case it can be easier to arrange the
entire CD in one timeline and split it into tracks using markers. Let's look at
an example in order to show how this works. (Look at \FigT~\ref{fig_markers01}
if you get lost with the explanations.) Open or create a project with only two
audio clips. Suppose we want clip 1 to be track 1 on the CD, and clip 2 will be
track 2. Position them on the first and maybe second track, starting at
position 00:00:00, as you want to hear them on the CD. Leave some silence
between the end of clip 1 and the beginning of clip 2. To get Traverso to start
a new CD track there, position the mouse cursor on the gap between the two
clips, and press \sact{M}. This adds a small triangle to the timeline at the
position of the mouse cursor, and two more at position 00:00:00 and at the end
of clip 2. The latter one is labelled ``End'', and it marks the end of the CD.
You can shift it a bit further back if you don't want the CD to stop right
there (remember you can have reverb tails extending beyond the last audio
sample, which you don't want to cut off).
\begin{figure}[t]
\centering\includegraphics[width=\textwidth]{images/markers01}
- \caption{If a CD is arranged in one song, markers can be used to define CD
tracks. Always keep the ones at position 00:00:00 and at the end.}
+ \caption{If a CD is arranged in one sheet, markers can be used to define CD
tracks. Always keep the ones at position 00:00:00 and at the end.}
\label{fig_markers01}
\end{figure}
-These triangles are CD track markers, and they can be moved, added, and
deleted freely (press \sact{Q} on the timeline to list all available
functions.) However, it is also possible to create setups which don't make
sense. E.\,g. only having one track marker in the timeline. In such cases,
Traverso tries to guess the most sensible solution, and adds markers on the fly
at positions it considers appropriate (which is usually at position 00:00:00
and after the last sample of the song containing audio data). Traverso also
supports CD-text, which can be entered in the marker dialogue ``Views
$\rightarrow$ Marker Dialog'' (\FigB~\ref{fig_marker-editor}). It is also
possible to export the table of contents of the CD as an HTML file from this
dialog. Album-wide CD-text can be entered in the project settings, opened from
``Project $\rightarrow$ Project Manager'', in the tab ``CD Text''.
+These triangles are CD track markers, and they can be moved, added, and
deleted freely (press \sact{Q} on the timeline to list all available
functions.) However, it is also possible to create setups which don't make
sense. E.\,g. only having one track marker in the timeline. In such cases,
Traverso tries to guess the most sensible solution, and adds markers on the fly
at positions it considers appropriate (which is usually at position 00:00:00
and after the last sample of the sheet containing audio data). Traverso also
supports CD-text, which can be entered in the marker dialogue ``Views
$\rightarrow$ Marker Dialog'' (\FigB~\ref{fig_marker-editor}). It is also
possible to export the table of contents of the CD as an HTML file from this
dialog. Album-wide CD-text can be entered in the project settings, opened from
``Project $\rightarrow$ Project Manager'', in the tab ``CD Text''.
\begin{figure}[ht]
\centering\includegraphics[width=0.45\textwidth]{images/marker-editor}
@@ -68,15 +53,15 @@
\label{fig_marker-editor}
\end{figure}
-Once the CD is laid out to your satisfaction, press \dact{RETURN} on the song
to open the export dialogue (\FigB~\ref{fig_exportdlg}). You can either choose
to export the project as audio files to the harddisk, or burn a CD. If you want
to export to harddisk, you can choose between several audio formats. The most
common one is WAVE, and depending on your plans with the exported files, you
can use different sample formats (bit depths). 16 bit is ideal if you want to
burn the files on CD later on. If you want to go on processing the files, use
32 bit float format instead. If you want to archive the files, use the FLAC
codec, which is a lossless compression format.
+Once the CD is laid out to your satisfaction, press \dact{RETURN} on the sheet
to open the export dialogue (\FigB~\ref{fig_exportdlg}). You can either choose
to export the project as audio files to the harddisk, or burn a CD. If you want
to export to harddisk, you can choose between several audio formats. The most
common one is WAVE, and depending on your plans with the exported files, you
can use different sample formats (bit depths). 16 bit is ideal if you want to
burn the files on CD later on. If you want to go on processing the files, use
32 bit float format instead. If you want to archive the files, use the FLAC
codec, which is a lossless compression format.
-If you want to burn a CD, you must also decide if you want to burn the current
song (using markers to define CD tracks), or the entire project (each song
becomes a track). If you check ``Export to disk only'', no CD will be written,
but only a *.toc file and *.wav files for \texttt{cdrdao}.
+If you want to burn a CD, you must also decide if you want to burn the current
sheet (using markers to define CD tracks), or the entire project (each sheet
becomes a track). If you check ``Export to disk only'', no CD will be written,
but only a *.toc file and *.wav files for \texttt{cdrdao}.
Note for OS X users: CD writing support is still experimental. You can choose
between several burning devices: IODVDServices, IODVDServices/2,
IOCompactDiscServices, IOCompactDiscServices/2. These are hard-coded, so you
probably don't have all of them installed. IOCompactDiscServices should only be
used for old drives without DVD reading support. If you have multiple DVD
drives, use IODVDServices or IODVDServices/2 to access the first and the second
drive. In most cases IODVDServices will be the only working solution.
\begin{figure}[t]
\centering\includegraphics[width=\textwidth]{images/exportdlg}
- \caption{\dact{RETURN} opens a dialogue to export the project (either the
current song or the entire project) to audio files, or burn a CD.}
+ \caption{\dact{RETURN} opens a dialogue to export the project (either the
current sheet or the entire project) to audio files, or burn a CD.}
\label{fig_exportdlg}
\end{figure}
Index: installation.tex
===================================================================
RCS file: /sources/traverso/traverso/doc/manual/en/installation.tex,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- installation.tex 24 May 2007 21:45:35 -0000 1.1
+++ installation.tex 16 Jun 2007 15:32:28 -0000 1.2
@@ -1,16 +1,16 @@
-The most convenient way to install Traverso is to use precompiled packages.
For Traverso \Version\ binary packages are available for several popular Linux
distributions. However, in the fast-living open source world, things can change
rapidly. It is thus recommended to refer to the Traverso homepage in order to
find up-to-date information on binary packages. Alternatively, compilation from
source is the second best option, and explained here in detail. It's actually
quite simple as you will see! The last option if the former two don't work, is
to download the ``ready to run binary'', which is usually provided for the i386
platform on the Traverso website \cite{trav-hp}. Traverso successfully builds
and runs on i386, ia64, and ppc platforms.
+The most convenient way to install Traverso is to use one of the available
installers. For Traverso \Version\ binary packages are available for several
popular Linux distributions. However, in the fast-living open source world,
things can change rapidly. It is thus recommended to refer to the Traverso
homepage \cite{trav-hp} in order to find up-to-date information on binary
packages. Alternatively, compilation from source is the second best option, and
explained here in detail. It's actually quite simple as you will see! Traverso
successfully builds and runs on i386, ia64, and ppc platforms.
\section{Binaries}
The precompiled binaries are available from the following locations:
\begin{description}
- \item [(K)Ubuntu:] add the reference given in \cite{trav-repo} to your
/etc/apt/sources.list, then run ``sudo apt-get update \&\& sudo apt-get install
traverso''.
+ \item [(K)Ubuntu:] The download page at \cite{trav-hp} has a debian
package.
\item [Gentoo:] Traverso is part of the official distribution. New
versions of Traverso appear in the Pro-Audio overlay first. You'll find more
info at \cite{pro-audio-wiki}.
- \item [SuSE:] Unofficial packages are available from \cite{jacklab-ref}
+ \item [SuSE:] Packages are available from \cite{suse-ref}
\end{description}
\section{Compiling from Source}
-This section describes how to compile Traverso from source on a (K,X)Ubuntu
\Ubuntu\ system. For other distributions, the package names may be somewhat
different, but you should be able to identify the correct package with your
distributions package manager. Note that Traverso depends on the Qt library
version 4.2.3 or newer (4.3 recommended).
+This section describes how to compile Traverso from source on a (K,X)Ubuntu
\Ubuntu\ system. For other distributions, the package names may be somewhat
different, but you should be able to identify the correct package with your
distributions package manager. Note that Traverso depends on the Qt library
version 4.2.3 or newer (4.3.1 recommended).
First you will need to make your system fit to compile Traverso. And while
we're at it, install some more useful things. Use your favorite package manager
(like synaptic or adept) to install the following packages:
Index: mixing.tex
===================================================================
RCS file: /sources/traverso/traverso/doc/manual/en/mixing.tex,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- mixing.tex 24 May 2007 21:45:35 -0000 1.1
+++ mixing.tex 16 Jun 2007 15:32:29 -0000 1.2
@@ -1,7 +1,7 @@
-Mixing features in Traverso \Version\ currently include gain, panorama,
different fade shapes for fade-in and -out, trimming, splitting, moving of
audio clips, and gain curves. An infrastructure for effect plugins using the
LV2 standard is implemented, but development of Traverso \Version\ is a bit
ahead of LV2, hence no plugins are available at the moment of writing. Starting
from version 0.40.0, Traverso has basic support for using Sox to process audio
clips.
+Mixing features in Traverso \Version\ currently include gain, panorama,
different fade shapes for fade-in and -out, trimming, splitting, moving of
audio clips, and gain curves. An infrastructure for effect plugins using the
LV2 standard is implemented, but development of Traverso \Version\ is a bit
ahead of LV2, hence plugin availability is still limited. Starting from version
0.40.0, Traverso has basic support for using Sox to process audio clips.
\section{Moving, trimming, splitting}
-Clips can be moved freely by holding \hact{D} and moving the mouse. If
snapping is active (\sact{S~N}), both ends of the dragged clip will snap to the
beginning of the song, edges of other clips, and to the work cursor.
+Clips can be moved freely by holding \hact{D} and moving the mouse. If
snapping is active (\sact{S~N}), both ends of the dragged clip will snap to the
beginning of the sheet, edges of other clips, and to the work cursor.
Move the mouse cursor on a clip, hold \hact{E}, and move the mouse
horizontally to drag the edge of the clip which is nearest to the mouse
position. If snapping is active, the edge will snap to the positions described
above.
@@ -25,7 +25,7 @@
\end{figure}
\subsection{Linear}
-Linear fades are a straight line between the start and end point. The control
knots can't be changed. Linear fades tend to sound rather abrupt at the
low-level end of the fade, and are thus not the preferred mode for long
fade-outs, e.\,g. at the end of a song.
+Linear fades are a straight line between the start and end point. The control
knots can't be changed. Linear fades tend to sound rather abrupt at the
low-level end of the fade, and are thus not the preferred mode for long
fade-outs, e.\,g. at the end of a sheet.
\subsection{S-shaped}
The S-shaped mode starts with a horizontal tangent, is steep a the center, and
passes into a horizontal tangent again. The beginning and end are very smooth,
but the center part can sometimes change too quickly in short S-fades. The
``strength'' parameter can be used to soften the center part and make the
volume change less obvious. The ``bending'' factor should usually remain
between linear and horizontal tangents, however, vertical tangents can be used
for effects.
@@ -34,7 +34,7 @@
The bended mode acts similar to the S-shaped mode, but the control knots point
to the same side. This mode can be used to achieve a very fast volume drop at
the beginning of the fade-out, and very soft towards the end. Both control
parameters are useful to find the best balance between a beginning that is not
too fast, and an ending that is still slow enough for a soft fade-out effect.
\subsection{Long}
-The long mode only allows to change the control knot at the low-level end of
the fade. This mode is often used for very smooth fade-outs, e.\,g. at the end
of a song. The high-level end changes fastly, but the low-level tail is very
soft. The long mode often sounds more musical than a similar bended mode.
+The long mode only allows to change the control knot at the low-level end of
the fade. This mode is often used for very smooth fade-outs, e.\,g. at the end
of a sheet. The high-level end changes fastly, but the low-level tail is very
soft. The long mode often sounds more musical than a similar bended mode.
\section{Gain curve}
Gain curves are a powerful feature to change the gain of an audio clip in the
time line. The curves are child elements of audio clips, therefore their
\emph{relative} position to the audio clip will always stays the same. To
change to effects mode, select the entry ``Mode: Effects'' from the dropdown
menu in the menu bar (\FigB~\ref{fig_gcurve01}). To change back to edit mode
``Mode: Edit''. A default curve node is added automatically at the beginning of
the clip at 0~dB. Additional nodes can be created by \dact{C} at the position
of the mouse cursor. Nodes can also be dragged (\hact{D}) and removed
(\dact{R}). These actions always apply to the node closest to the mouse cursor,
which is indicated by a different colour.
@@ -46,7 +46,7 @@
\end{figure}
\section{Plugins}
-Traverso supports the LV2 plugin interface, which is the successor of the
LADSPA standard. Plugins can be added to tracks by pressing \sact{F5}, which
opens a list of all LV2 plugins installed on the system
(\FigB~\ref{fig_pluglist}). Active plugins will be shown as semi-transparent
fields in the track view. These fields have their own context menu; just try it
out by holding the mouse on them and pressing \sact{Q}. Pressing \sact{E} will
open a generic dialog, which allows to adjust the plugin parameters. Plugins
can also be bypassed (\sact{B}) and removed (\dact{R}). Version 0.40.x inserts
all plugins post-fader. More flexible solutions will follow in upcoming
versions.
+Traverso supports the LV2 plugin interface, which is the successor of the
LADSPA standard. Plugins can be added to tracks by pressing \sact{F5}, which
opens a list of all LV2 plugins installed on the system
(\FigB~\ref{fig_pluglist}). Active plugins will be shown as semi-transparent
fields in the track view. These fields have their own context menu; just try it
out by holding the mouse on them and pressing \sact{Q} or \sact{Right Mouse
Button}. Pressing \sact{E} will open a generic dialog, which allows to adjust
the plugin parameters. Plugins can also be bypassed (\sact{B}) and removed
(\dact{R}). Version 0.40.x inserts all plugins post-fader. More flexible
solutions will follow in upcoming versions.
\begin{figure}[t]
\centering\includegraphics[width=0.6\textwidth]{images/plugin-list}
Index: recording.tex
===================================================================
RCS file: /sources/traverso/traverso/doc/manual/en/recording.tex,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- recording.tex 24 May 2007 21:45:36 -0000 1.1
+++ recording.tex 16 Jun 2007 15:32:29 -0000 1.2
@@ -1,5 +1,5 @@
\section{Creating a new project}
-To make some test recordings we first create a new project. Start Traverso and
select ``New\dots''. Enter a name, set the number of songs to 1, the number of
tracks to 2, and leave the rest empty. Then press ``OK'' to create the project
and show it's first song. Note: All recorded audio data will be stored in
\texttt{project\_dir/project\_name/audiosources}, so if you followed our advice
and selected a project directory on a pratition with lots of free space, you
shouldn't run out of disk space now.
+To make some test recordings we first create a new project. Start Traverso and
select ``New\dots''. Enter a name, set the number of sheets to 1, the number of
tracks to 2, and leave the rest empty. Then press ``OK'' to create the project
and show it's first sheet. Note: All recorded audio data will be stored in
\texttt{project\_dir/project\_name/audiosources}, so if you followed our advice
and selected a project directory on a pratition with lots of free space, you
shouldn't run out of disk space now.
\section{Setting up the driver}
To set up the driver backend, open the preferences dialog by clicking
``Settings $\rightarrow$ Preferences\dots'' (\FigB\ \ref{fig_driversettings}).
Which driver is appropriate for your system is described in chapter
\ref{sect_setup}. In the driver configuration one can chose the sampling rate,
and Traverso always uses the sampling rate of the driver backend for its
recordings. Traverso's audio engine works entirely in 32 bit floating point
precision, and it uses standard wave files with 32 bit float precision to store
recorded audio data.
Index: setup.tex
===================================================================
RCS file: /sources/traverso/traverso/doc/manual/en/setup.tex,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- setup.tex 24 May 2007 21:45:36 -0000 1.1
+++ setup.tex 16 Jun 2007 15:32:29 -0000 1.2
@@ -4,7 +4,7 @@
\begin{figure}
\centering\includegraphics[width=\textwidth]{images/sshot06.png}
- \caption{Interface elements of Traverso: 1 Track panel: If the mouse cursor
is hovering over this area, all key actions apply to the track beneath it; 2
Audio clip: Key actions apply to the audio clip; 3 Time line: Key actions apply
to markers in the time line; 4 Dock window / Dock widget; 5 Fade out; 6 Work
cursor; 7 Play head; 8 Song area.}
+ \caption{Interface elements of Traverso: 1 Track panel: If the mouse cursor
is hovering over this area, all key actions apply to the track beneath it; 2
Audio clip: Key actions apply to the audio clip; 3 Time line: Key actions apply
to markers in the time line; 4 Dock window / Dock widget; 5 Fade out; 6 Work
cursor; 7 Play head; 8 Sheet area.}
\label{fig_gui01}
\end{figure}
@@ -17,7 +17,7 @@
\end{figure}
\section{The Driver Backend}
-Four driver backends are supported to date: The Null driver, ALSA, the jack
soundserver, and Port Audio (on Windows and Mac OS X). Let's have a look at all
of them, what the advantages and disadvantages are, and how to set them up
correctly. The currently loaded driver is displayed in the menu bar.
+Four driver backends are supported to date: The Null driver, ALSA, the jack
soundserver, and Port Audio (on Windows and Mac OS X). Let's have a look at all
of them, what the advantages and disadvantages are, and how to set them up
correctly. The currently loaded driver is displayed in the menu bar.
\subsection{Null Driver}
The Null driver is a fallback solution which is set if no other driver is
available, but you won't hear any output as long as the Null Driver is loaded.
Hence there's hardly a situation where you want to load it manually. To select
a valid driver, click on the \emph{Null Driver} label in the menu bar to open a
configuration dialog (\FigB\ \ref{fig_driverconf}).
Index: traverso-manual01.tex
===================================================================
RCS file: /sources/traverso/traverso/doc/manual/en/traverso-manual01.tex,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- traverso-manual01.tex 24 May 2007 21:45:37 -0000 1.1
+++ traverso-manual01.tex 16 Jun 2007 15:32:29 -0000 1.2
@@ -134,7 +134,7 @@
\bibitem{trav-hp}http://www.traverso-daw.org
\bibitem{trav-repo}deb http://www.traverso-daw.org binary-i386/
\bibitem{pro-audio-wiki}http://proaudio.tuxfamily.org/wiki/
- \bibitem{jacklab-ref}http://jacklab.net
+ \bibitem{suse-ref}http://packman.links2linux.org/package/traverso
\bibitem{macports}http://www.apple.com/downloads/macosx/unix\_open\_source/macports.html
% \bibitem{savannah-ref}http://savannah.nongnu.org/projects/traverso/
\bibitem{ml-archive}http://lists.gnu.org/archive/html/traverso-devel/
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Traverso-commit] traverso/doc/manual/en cdburning.tex installati...,
Remon Sijrier <=