X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=include%2Fnewopen-session-dialog.html;h=15cbeb42cc3f3e68fa926b9113bc76c5c08804e2;hb=081e7af0b6f6dec0ca685d3a538eacf20394c2cc;hp=e62ec7e2a08a4865e57387dad1c9491467c867ed;hpb=bf25b41536e78a945358a9525093a5f394d81d99;p=ardour-manual diff --git a/include/newopen-session-dialog.html b/include/newopen-session-dialog.html index e62ec7e..15cbeb4 100644 --- a/include/newopen-session-dialog.html +++ b/include/newopen-session-dialog.html @@ -37,31 +37,63 @@ + +
This page allows to type in the name of a session, select a folder to save it in, and optionally use an existing template.
- Under Advanced Options, some fine tuning can be done, like selecting - whether Ardour should create a Master Bus, or a Control Bus, and how many channels - the output should have. + The different templates, both the "factory" ones and the ones created by the user, + are easily available on the left-side panel. Depending on the chosen template, + a specific Template Settings window may be shown, allowing the user to fine-tune + the details of the template and/or choose between the different options of the + template. +
+ ++ Templates can be huge time savers when working on similar projects, or on + usual projects, as they allow to preset and tweak a lot of the session properties, (like the + availability of a monitoring section, + connection to a Master Bus, etc.), and handle the creation of tracks of any kind. +
++ The Empty Template preset allows to create a session + "from scratch". Everything a session template does can be done manually + —albeit more tediously— and the resulting sessions will not differ + whatsoever.
- Other options also decide whether Ardour should automatically connect all inputs - to the hardware's physical ports. Ardour will do so - sequentially and in round-robin fashion, connecting the first track's - input to the first input of the hardware and so on. When Ardour has used - all available hardware inputs, it will begin again with the first physical - input. + As of Ardour 5.12, which introduced the new template dialog, the factory templates are:
+ +Empty Template | +Creates an empty session with no tracks and no monitoring. A stereo Master Bus is created, and any track created defaults to output on this bus. |
---|---|
Advanced Session | +Like the Empty Template, but adds the ability to easily manage the Master bus (channels, hardware connection, and track autoconnection), and the creation of a monitoring section. |
Recording Session | +Like the Empty Template, but allows the fast creation of a number of tracks, optionnaly ready to record. |
Live Band | +Fast tracks the creation of usual tracks for a band setup (vocals, guitars, piano, ...), and optionnaly adds usual effects on these tracks. |
- The number of hardware channels used by Ardour can also be limited. + Selecting a template will display its description in the right-side pannel, while + hovering over a template name will show a tooltip indicating if it is a factory + template, or, if it is a user-created one, which version of Ardour was used to + create it.
- By default Ardour will connect all tracks and busses to the Master Bus if - there is one. However, it can also be told to automatically connect each - output to the physical outputs of the interface or sound card, and limit - the number of physical outputs used, as above. + Whether or not a template is used, and before the "Template Setup" dialog, the + Audio/MIDI Setup will be shown.