Tim Mayberry
56e384349b
additions. Add dbhelper.vim key stroke mappings I use for working with docbook source. There are no xsl or css files for customizing the html output so it will look really boring...this will only be temporary. Support for content localization and generation of pdf's is planned. git-svn-id: svn://localhost/ardour2/trunk@1405 d708f5d6-7413-0410-9779-e7cbd77b26cf
39 lines
1.4 KiB
XML
39 lines
1.4 KiB
XML
<?xml version="1.0" standalone="no"?>
|
|
|
|
<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
|
|
|
|
]>
|
|
|
|
<section id="sn-working-with-ranges">
|
|
<title>Working with Ranges</title>
|
|
<para>
|
|
This section doesn't really exist it yet, but is a placeholder for the
|
|
following
|
|
</para>
|
|
|
|
<section id="bounce-range">
|
|
<title>Bounce Range</title>
|
|
<para>
|
|
Currently, when bouncing a range to disk, files corresponding to each
|
|
channel of the range's output are created. The file names begin with Audio,
|
|
then the track number followed by ".1." Then, a 0 or 1 is added, depending
|
|
on the channel. Finally, the file extension is added. The file type is
|
|
determined by the native format selection in the options editor (the
|
|
Paths/Files tab).
|
|
</para>
|
|
|
|
<para>
|
|
In a future version, "bounce range" will replace the range with a new
|
|
region based on the bounced audio file which will include track FX, etc.
|
|
Currently, no dialog box is offered to allow the user to name the bounced
|
|
file or choose its location on disk. The bounced audio is just placed in
|
|
the sounds directory of the project directory. There is currently no visual
|
|
feedback that the bounce has been accomplished.
|
|
</para>
|
|
</section>
|
|
<!--
|
|
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
|
|
href="Some_Subsection.xml" />
|
|
-->
|
|
</section>
|