diff options
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/CMakeLists.txt | 12 | ||||
| -rw-r--r-- | doc/de/.gitignore | 0 | ||||
| -rw-r--r-- | doc/en/CMakeLists.txt | 12 | ||||
| -rw-r--r-- | doc/en/headers-and-unicode-lyrics.png | bin | 0 -> 17800 bytes | |||
| -rw-r--r-- | doc/en/index.docbook | 6885 | ||||
| -rw-r--r-- | doc/en/rg-audiofilemanager.png | bin | 0 -> 24939 bytes | |||
| -rw-r--r-- | doc/en/rg-audiomixer.png | bin | 0 -> 19108 bytes | |||
| -rw-r--r-- | doc/en/rg-bankeditor.png | bin | 0 -> 45639 bytes | |||
| -rw-r--r-- | doc/en/rg-button-bar-time.png | bin | 0 -> 141 bytes | |||
| -rw-r--r-- | doc/en/rg-button-from-end.png | bin | 0 -> 209 bytes | |||
| -rw-r--r-- | doc/en/rg-clefdialog.png | bin | 0 -> 8510 bytes | |||
| -rw-r--r-- | doc/en/rg-coda.png | bin | 0 -> 495 bytes | |||
| -rw-r--r-- | doc/en/rg-colours.png | bin | 0 -> 18181 bytes | |||
| -rw-r--r-- | doc/en/rg-cursors.png | bin | 0 -> 64750 bytes | |||
| -rw-r--r-- | doc/en/rg-devicemanager.png | bin | 0 -> 21216 bytes | |||
| -rw-r--r-- | doc/en/rg-eraser.png | bin | 0 -> 339 bytes | |||
| -rw-r--r-- | doc/en/rg-eventfilter.png | bin | 0 -> 18877 bytes | |||
| -rw-r--r-- | doc/en/rg-eventlisteditor.png | bin | 0 -> 27310 bytes | |||
| -rw-r--r-- | doc/en/rg-gridquantizer.png | bin | 0 -> 21058 bytes | |||
| -rw-r--r-- | doc/en/rg-guitarchorddialog.png | bin | 0 -> 24359 bytes | |||
| -rw-r--r-- | doc/en/rg-guitarchordeditordialog.png | bin | 0 -> 12376 bytes | |||
| -rw-r--r-- | doc/en/rg-ipb-audio.png | bin | 0 -> 7232 bytes | |||
| -rw-r--r-- | doc/en/rg-ipb-midi.png | bin | 0 -> 16274 bytes | |||
| -rw-r--r-- | doc/en/rg-ipb-synth.png | bin | 0 -> 7320 bytes | |||
| -rw-r--r-- | doc/en/rg-keysigdialog.png | bin | 0 -> 45792 bytes | |||
| -rw-r--r-- | doc/en/rg-loadpreset.png | bin | 0 -> 31466 bytes | |||
| -rw-r--r-- | doc/en/rg-mainwindow.png | bin | 0 -> 70700 bytes | |||
| -rw-r--r-- | doc/en/rg-markerloop.png | bin | 0 -> 1318 bytes | |||
| -rw-r--r-- | doc/en/rg-matrixview.png | bin | 0 -> 116002 bytes | |||
| -rw-r--r-- | doc/en/rg-metronome.png | bin | 0 -> 12310 bytes | |||
| -rw-r--r-- | doc/en/rg-midifilter.png | bin | 0 -> 15349 bytes | |||
| -rw-r--r-- | doc/en/rg-midimixer.png | bin | 0 -> 38207 bytes | |||
| -rw-r--r-- | doc/en/rg-move.png | bin | 0 -> 235 bytes | |||
| -rw-r--r-- | doc/en/rg-notation-toolbars.png | bin | 0 -> 5417 bytes | |||
| -rw-r--r-- | doc/en/rg-notationquantizer.png | bin | 0 -> 27527 bytes | |||
| -rw-r--r-- | doc/en/rg-notationtools.png | bin | 0 -> 2360 bytes | |||
| -rw-r--r-- | doc/en/rg-notationview-multipage.png | bin | 0 -> 109121 bytes | |||
| -rw-r--r-- | doc/en/rg-notationview.png | bin | 0 -> 58931 bytes | |||
| -rw-r--r-- | doc/en/rg-pastedialog.png | bin | 0 -> 10594 bytes | |||
| -rw-r--r-- | doc/en/rg-pencil.png | bin | 0 -> 361 bytes | |||
| -rw-r--r-- | doc/en/rg-percussionmatrix.png | bin | 0 -> 158608 bytes | |||
| -rw-r--r-- | doc/en/rg-plugin-dialog.png | bin | 0 -> 14476 bytes | |||
| -rw-r--r-- | doc/en/rg-pluginbuttons.png | bin | 0 -> 5380 bytes | |||
| -rw-r--r-- | doc/en/rg-plugineditorbutton.png | bin | 0 -> 7684 bytes | |||
| -rwxr-xr-x | doc/en/rg-quickmarker.png | bin | 0 -> 643 bytes | |||
| -rw-r--r-- | doc/en/rg-rawnoteruler.png | bin | 0 -> 15998 bytes | |||
| -rw-r--r-- | doc/en/rg-resize.png | bin | 0 -> 198 bytes | |||
| -rw-r--r-- | doc/en/rg-segmentparameterbox.png | bin | 0 -> 7419 bytes | |||
| -rw-r--r-- | doc/en/rg-segno.png | bin | 0 -> 543 bytes | |||
| -rw-r--r-- | doc/en/rg-select.png | bin | 0 -> 258 bytes | |||
| -rw-r--r-- | doc/en/rg-split.png | bin | 0 -> 213 bytes | |||
| -rw-r--r-- | doc/en/rg-synthpluginbuttons.png | bin | 0 -> 5331 bytes | |||
| -rw-r--r-- | doc/en/rg-tempodialog.png | bin | 0 -> 35751 bytes | |||
| -rw-r--r-- | doc/en/rg-temporuler.png | bin | 0 -> 1736 bytes | |||
| -rw-r--r-- | doc/en/rg-text-cursor.png | bin | 0 -> 515 bytes | |||
| -rw-r--r-- | doc/en/rg-textdialog.png | bin | 0 -> 13508 bytes | |||
| -rw-r--r-- | doc/en/rg-timesigdialog.png | bin | 0 -> 16190 bytes | |||
| -rw-r--r-- | doc/en/rg-trackbutton-instrumentmenu.png | bin | 0 -> 19046 bytes | |||
| -rw-r--r-- | doc/en/rg-trackbutton-instruments.png | bin | 0 -> 13486 bytes | |||
| -rw-r--r-- | doc/en/rg-trackbutton-labels.png | bin | 0 -> 10851 bytes | |||
| -rw-r--r-- | doc/en/rg-trackbuttons.png | bin | 0 -> 3986 bytes | |||
| -rw-r--r-- | doc/en/rg-trackeditor.png | bin | 0 -> 26457 bytes | |||
| -rw-r--r-- | doc/en/rg-trackparameterbox.png | bin | 0 -> 44313 bytes | |||
| -rw-r--r-- | doc/en/rg-transport.png | bin | 0 -> 16050 bytes | |||
| -rw-r--r-- | doc/en/rg-triggersegment.png | bin | 0 -> 8787 bytes | |||
| -rw-r--r-- | doc/en/rg-tupletdialog.png | bin | 0 -> 11568 bytes | |||
| -rw-r--r-- | doc/en/rg-useornament.png | bin | 0 -> 12898 bytes | |||
| -rw-r--r-- | doc/en/tips | 316 | ||||
| -rw-r--r-- | doc/en/transpose-by-interval.png | bin | 0 -> 14436 bytes | |||
| -rw-r--r-- | doc/es/CMakeLists.txt | 12 | ||||
| -rw-r--r-- | doc/es/index.docbook | 6416 | ||||
| -rw-r--r-- | doc/ja/CMakeLists.txt | 12 | ||||
| -rw-r--r-- | doc/ja/index.docbook | 5376 | ||||
| -rw-r--r-- | doc/sv/CMakeLists.txt | 12 | ||||
| -rw-r--r-- | doc/sv/index.docbook | 6485 | ||||
| -rw-r--r-- | doc/sv/rg-audiofilemanager.png | bin | 0 -> 21744 bytes | |||
| -rw-r--r-- | doc/sv/rg-audiomixer.png | bin | 0 -> 34307 bytes | |||
| -rw-r--r-- | doc/sv/rg-bankeditor.png | bin | 0 -> 23851 bytes | |||
| -rw-r--r-- | doc/sv/rg-clefdialog.png | bin | 0 -> 6634 bytes | |||
| -rw-r--r-- | doc/sv/rg-colours.png | bin | 0 -> 24157 bytes | |||
| -rw-r--r-- | doc/sv/rg-devicemanager.png | bin | 0 -> 57989 bytes | |||
| -rw-r--r-- | doc/sv/rg-eventlisteditor.png | bin | 0 -> 20685 bytes | |||
| -rw-r--r-- | doc/sv/rg-gridquantizer.png | bin | 0 -> 15465 bytes | |||
| -rw-r--r-- | doc/sv/rg-ipb-audio.png | bin | 0 -> 2931 bytes | |||
| -rw-r--r-- | doc/sv/rg-ipb-midi.png | bin | 0 -> 22193 bytes | |||
| -rw-r--r-- | doc/sv/rg-ipb-synth.png | bin | 0 -> 2780 bytes | |||
| -rw-r--r-- | doc/sv/rg-keysigdialog.png | bin | 0 -> 13593 bytes | |||
| -rw-r--r-- | doc/sv/rg-mainwindow.png | bin | 0 -> 44924 bytes | |||
| -rw-r--r-- | doc/sv/rg-matrixview.png | bin | 0 -> 71224 bytes | |||
| -rw-r--r-- | doc/sv/rg-metronome.png | bin | 0 -> 6977 bytes | |||
| -rw-r--r-- | doc/sv/rg-midifilter.png | bin | 0 -> 11976 bytes | |||
| -rw-r--r-- | doc/sv/rg-midimixer.png | bin | 0 -> 24240 bytes | |||
| -rw-r--r-- | doc/sv/rg-notationquantizer.png | bin | 0 -> 23469 bytes | |||
| -rw-r--r-- | doc/sv/rg-notationview-multipage.png | bin | 0 -> 41203 bytes | |||
| -rw-r--r-- | doc/sv/rg-notationview.png | bin | 0 -> 35396 bytes | |||
| -rw-r--r-- | doc/sv/rg-pastedialog.png | bin | 0 -> 4809 bytes | |||
| -rw-r--r-- | doc/sv/rg-plugin-dialog.png | bin | 0 -> 7220 bytes | |||
| -rw-r--r-- | doc/sv/rg-pluginbuttons.png | bin | 0 -> 2353 bytes | |||
| -rw-r--r-- | doc/sv/rg-plugineditorbutton.png | bin | 0 -> 13500 bytes | |||
| -rw-r--r-- | doc/sv/rg-segmentparameterbox.png | bin | 0 -> 4138 bytes | |||
| -rw-r--r-- | doc/sv/rg-synthpluginbuttons.png | bin | 0 -> 2109 bytes | |||
| -rw-r--r-- | doc/sv/rg-tempodialog.png | bin | 0 -> 17555 bytes | |||
| -rw-r--r-- | doc/sv/rg-timesigdialog.png | bin | 0 -> 10171 bytes | |||
| -rw-r--r-- | doc/sv/rg-trackbutton-instruments.png | bin | 0 -> 2477 bytes | |||
| -rw-r--r-- | doc/sv/rg-trackbutton-labels.png | bin | 0 -> 2410 bytes | |||
| -rw-r--r-- | doc/sv/rg-trackeditor.png | bin | 0 -> 45816 bytes | |||
| -rw-r--r-- | doc/sv/rg-transport.png | bin | 0 -> 15432 bytes | |||
| -rw-r--r-- | doc/sv/rg-tupletdialog.png | bin | 0 -> 9132 bytes | |||
| -rw-r--r-- | doc/sv/rosegarden.po | 7454 |
109 files changed, 32992 insertions, 0 deletions
diff --git a/doc/CMakeLists.txt b/doc/CMakeLists.txt new file mode 100644 index 0000000..a8b8de4 --- /dev/null +++ b/doc/CMakeLists.txt @@ -0,0 +1,12 @@ +################################################# +# +# (C) 2010-2011 Serghei Amelian +# serghei (DOT) amelian (AT) gmail.com +# +# Improvements and feedback are welcome +# +# This file is released under GPL >= 2 +# +################################################# + +tde_auto_add_subdirectories() diff --git a/doc/de/.gitignore b/doc/de/.gitignore new file mode 100644 index 0000000..e69de29 --- /dev/null +++ b/doc/de/.gitignore diff --git a/doc/en/CMakeLists.txt b/doc/en/CMakeLists.txt new file mode 100644 index 0000000..eb6d853 --- /dev/null +++ b/doc/en/CMakeLists.txt @@ -0,0 +1,12 @@ +################################################# +# +# (C) 2011 Timothy Pearson +# kb9vqf (AT) pearsoncomputing.net +# +# Improvements and feedback are welcome +# +# This file is released under GPL >= 2 +# +################################################# + +tde_create_handbook( DESTINATION rosegarden ) diff --git a/doc/en/headers-and-unicode-lyrics.png b/doc/en/headers-and-unicode-lyrics.png Binary files differnew file mode 100644 index 0000000..3b16938 --- /dev/null +++ b/doc/en/headers-and-unicode-lyrics.png diff --git a/doc/en/index.docbook b/doc/en/index.docbook new file mode 100644 index 0000000..064dd2b --- /dev/null +++ b/doc/en/index.docbook @@ -0,0 +1,6885 @@ +<?xml version="1.0" ?> +<!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.1.2-Based Variant V1.0//EN" "dtd/kdex.dtd" [ + <!ENTITY rosegarden "<application>Rosegarden</application>"> + <!ENTITY MIDI "<acronym>MIDI</acronym>"> + <!ENTITY % English "INCLUDE" > <!-- change language only here --> + <!ENTITY % addindex "IGNORE"> +]> + +<!-- The language must be changed in the <book> tag for translations. --> + + +<!-- + + Notes on style and terminology for Rosegarden handbook + ====================================================== + + * Try to use British spelling and idiom as much as you possibly + can, so the American bits don't stick out like a sore + thumb. Realise, not realize, colour, not color, though of + course an American is going to miss using colorful (oops) + British sayings like "a bit naff," and won't have any idea + what the bloody hell (that was good, but a bit too vulgar, of + course) words like "heuristic" mean. + + * Aim to be clear, brief and direct, but be informal. + + * Write instructions in the second person. + + Good: "You can select segments by clicking on them with + the arrow tool." + + Bad: "Segments can be selected by clicking on them with + the arrow tool." + + Very bad: "The arrow tool allows the user to select segments + by clicking on them." + + If you dislike the first of these because you want to make the + phrase "the arrow tool" more obvious by placing it at the + start of the sentence, then perhaps you should be using a + variablelist instead and making "the arrow tool" a list item. + + * It's perfectly permissible to detour to explain why + something is the way it is, particularly if it might not be + obvious. + + * It's also entirely permissible to omit advanced stuff. This + document is be about understanding how and why, not about + knowing every last clever detail. Initially we were going to + include a function reference section for the clever details, + but it proved too hard to keep up to date, and not all that + useful. Providing a quick bit of guidance is most of the job. + + * Bear in mind we can link extensively from any part of + the handbook to any other. Unfortunately DocBook won't allow + you to write a link to a target that doesn't exist yet, so if + you want to link to something that's not yet been written, + either make a note of the planned link in an XML comment, or + go and create a stub for the bit that hasn't been written yet, + or else just write in a way that allows for a link to be + easily added later (we could do an editing phase specially for + links). + + * Be strict about using the correct terminology for + Rosegarden data structures (segment, event, track, instrument, + composition), but don't capitalise the words. Capitalisation + is useful in technical documents to make it clear that you're + referring to a precise concept, but you shouldn't have to do + it to make your meaning clear in user documentation. If + something seems ambiguous without, try rewording it instead. + + + About Screenshots + ================= + + We recommend saving your current user preferences as a new theme + using the KDE theme manager, so you can restore your usual + desktop after your work on this manual is done. Then we + recommend that you spare yourself some effort, and use the + "Rosegarden Handbook" KDE theme I just created, and put here: + + http://rosegarden.sourceforge.net/Rosegarden\ Handbook.kth + + If you can't use the theme for some reason, you must dial in + these changes by hand. Screenshots used with this documentation + should use the following style, colour and font settings: + + (NOTE: These specs are from the KDE 2.x era, surely, and make no + particular mention of icon themes. I have no idea what icons + were used in the original version of this document, since it was + not specified. I have used the new default "Crystal SVG" icons + in creating the theme above. This will probably result in a + mis-match, but I find I really don't care.) + + (NOTE in reply to the above: the scheme was originally from + KDE 2.x, yes. I suggest we don't worry about icon mismatches too + much, as most of the screenshots don't have icons in semantically + meaningful roles anyway. I use Crystal SVG too now and I don't + really intend to change that for the documentation.) + + * KDE Style: "Light Style, 3rd Revision" + + * Colour scheme: "Blue Slate", with high-contrast + setting and with the standard widget background set to white. + (I have this saved as a new scheme.) + + * Fonts: Verdana 11px for general use and menus; Verdana + 11px bold for window titles; antialiasing on, but sub-pixel + antialiasing off. (For pictures of the segment and instrument + parameter boxes I usually turn the size up to 13px, which + perhaps says something about our use of font size in these + boxes.) WARNING: This is not a reliable hint any more, as + the KDE font size is not in pixels but points that depend + on the detected monitor resolution. Go for something that + looks a bit like the existing screenshots; it will probably + be smaller than 11pt. + + NOTE: switching off sub-pixel antialiasing is quite important, + as otherwise your text will look weird and fuzzy to any + readers with CRT monitors or LCDs with a different colour + ordering. The exact choice of font is less important: I + think you can get away with Vera or whatever. + + * Window Decorations: "Quartz" + + None of these would be my first choice for nice-looking + screenshots now, but we're not here to sell Rosegarden in this + document, we're here to provide clear and consistent help text. + So the priority is to make new screenshots look like the existing + ones, not to make them look fancy. Also, I think there is an + advantage to having screenshots in a help document look a bit + distinct from the user's own window decorations surrounding the + help text. + + Screenshots of the whole program or of whole matrix or notation + windows may be taken using different themes if desired, but + screenshots of individual dialogs or window components must use + the above scheme. + +--> + +<!-- + Notes on Usability Defects + ========================== + + This comment is a place to note anything I find difficult to + document, or anything where the functions for two necessarily + linked concepts are not actually linked in the GUI (etc). + + * The audio file directory (in document properties) can't be + inspected or changed from the audio file manager. This is + arguably linked to a need for a project directory. There + are various other usability problems with the audio file + manager as well, e.g. there's no way to tell it to pull all + imported audio files into a single audio directory. + + * Track buttons showing sometimes-instrument, sometimes-label. + + * Mostly FIXED - Can't usefully double-click / right-click on + most rulers. This would be useful for a slower but clearer + way to set loops; adding and editing markers; etc. Setting + loops is particularly opaque especially in notation and + matrix views. + + * Hideous inconsistency (documented in an RFE already) between + having to use RG for MIDI routing and being unable to use RG + for audio routing. + + Troubleshooting + =============== + + Shall we have a troubleshooting section? + + * I'm not seeing any MIDI outputs + * I'm not hearing any sound from my MIDI outputs + * I'm not seeing any audio outputs + * I'm not hearing any sound from my audio outputs + * I don't see any synth plugins + +--> + +<!-- + Still to do (yeah right, in 30 to 75 years) + =========== + + * Control rulers + + * Controller editing + + * Event list + + * Event editor dialogs + + * Document properties + + * Add images for the tools (move, split &c) when describing them + + * Add images for transport buttons in transport section + + * Update notation menu references + + * Add new notation stuff <- "new" when this to-do item was added? when was that I wonder? + + * Config dialog + + * Make sure the guimenuitem etc tags are being used for all menu refs + + * Give keyboard shortcuts for menu functions? + + * Go through again changing Rosegarden -> &rosegarden; and double-hyphen -> + – or — and review any uses of "the ... function" to see + if these words are redundant + + * Troubleshooter + + * Check !!! items + + * Fill gaps in revision history + + * Consistent capitalisation: Instrument Parameter Box or instrument + parameter box? Audio Mixer or audio mixer? Device or device? + + * Finally, review the structure again and adjust the <chapter>/<sect*> + for balance + +--> + + +<book id="rosegarden" lang="&language;"> + + <!-- This header contains all of the meta-information for the document such + as Authors, publish date, the abstract, and Keywords --> + + <bookinfo> + <title>The Rosegarden Handbook</title> + <authorgroup> + <author> + <firstname>Chris</firstname> + <surname>Cannam</surname> + </author> + <author> + <firstname>Richard</firstname> + <surname>Bown</surname> + </author> + <author> + <firstname>Guillaume</firstname> + <surname>Laurent</surname> + <firstname>D. Michael</firstname> + <surname>McIntyre</surname> + <firstname>Pedro</firstname> + <surname>Lopez-Cabanillas</surname> + <firstname>Heikki</firstname> + <surname>Junes</surname> + </author> + <!-- TRANS:ROLES_OF_TRANSLATORS --> + </authorgroup> + + <copyright> + <year>2002-2008</year> + <holder>Chris Cannam, Richard Bown, Guillaume Laurent, D. Michael + McIntyre, Pedro Lopez-Cabanillas, Heikki Junes</holder> + </copyright> + + <date>2008-05-05</date> + <releaseinfo>1.7.0</releaseinfo> + + <abstract> + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-mainwindow.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>&rosegarden;</phrase> + </textobject> + </mediaobject> + </screenshot> + + Rosegarden is an audio and &MIDI; sequencer and musical notation + editor. This Handbook describes how to use it. + + </para> + </abstract> + + <keywordset> + <keyword>Rosegarden</keyword> + <keyword>sequencer</keyword> + <keyword>MIDI</keyword> + <keyword>audio</keyword> + <keyword>music</keyword> + <keyword>notation</keyword> + <keyword>score</keyword> + <keyword>KDE</keyword> + </keywordset> + + </bookinfo> + + <!-- The contents of the documentation begins here. Label each + chapter so with the id attribute. This is necessary for two reasons: + it allows you to easily reference the chapter from other chapters of + your document, and if there is no ID, the name of the generated HTML + files will vary from time to time making it hard to manage for + maintainers and for the CVS system. Any chapter labelled (OPTIONAL) + may be left out at the author's discretion. Other chapters should + not be left out in order to maintain a consistent documentation + style across all KDE apps. --> + + <chapter id="introduction"> + <title>Introduction</title> + + <sect1> + <title>About Rosegarden</title> + <para> + <application>Rosegarden</application> is a &MIDI; and audio + sequencer and musical notation editor. Rosegarden allows you to + record, arrange, and compose music, in the shape of traditional + score or &MIDI; data, or of audio files either imported or + recorded from a microphone, guitar or whatever audio source you + care to specify. You can use Rosegarden to write, edit, and + organise music to create a composition, which you can then + synthesise, add effects to, and mix down for burning to CD or + distribution on the web. Rosegarden also contains well-rounded + notation editing support for high quality printed output. + </para> + + <para> + <application>Rosegarden</application> is designed to look and + act in a manner familiar to experienced users coming to Linux + from other platforms, whilst also being accessible and friendly + to users new to music software generally. + </para> + + <sect2 id="intro-handbook"> + <title>About this Handbook</title> + <para> + This handbook summarises the capabilities of &rosegarden; and + provides a reference for some of the concepts involved. It's + designed to make sense either read in order or used as a reference + to the concepts and functions available in Rosegarden. If you + would like to read a tutorial as well, <ulink + url="http://rosegarden.sourceforge.net/tutorial/en/chapter-0.html">you + can find one here</ulink>.</para> + + <para>If there's something else that you + don't understand or require further help with, please visit + <ulink url="http://www.rosegardenmusic.com/support/">the + Rosegarden website</ulink> for Frequently Asked Questions and + mailing list instructions. + </para> + </sect2> + + <sect2 id="intro-menufunctions"> + <title>About Menus and Shortcuts</title> <para>This handbook + usually refers to the functions you can use in Rosegarden by + describing where they live on the menus. For example, the + function to add a single new track to the main track editor is + <menuchoice> + <guimenu lang="en">Tracks</guimenu> + <guimenuitem>Add Track</guimenuitem> + </menuchoice>.</para> + + <para>In many cases, this is not the only way to reach a + particular function. In this case the same function is also + available through the keyboard shortcut Ctrl+T, and it also + appears as an icon on one of the main window's toolbars. Both + the keyboard shortcut and the icon can quickly be learned, + because they are shown on the menu in Rosegarden alongside the + name of the function. You should bear in mind that although we + always give the full menu location in this documentation for + reference purposes, it's not necessarily the best or most usual + way to use a function, and you should keep an eye on the + keyboard shortcuts or toolbar icons as well. + </para> + </sect2> + + <sect2 id="intro-optional"> + <title>Optional Features</title> <para>This Handbook assumes + that your Rosegarden installation supports all the features of + which it is capable. Some of Rosegarden's features, including + some very major ones, are actually optional when building a + Rosegarden installation, depending on which other libraries and + supporting code is available. For example, the whole audio + subsystem is only compiled in if JACK libraries are available; + synth plugin support depends on a number of other modules; + etc.</para> <para>These dependencies are documented in the + Rosegarden README and configuration documentation. If you find + that this Handbook refers to features not visible in the version + of Rosegarden you're using, consult your configuration + documentation or distributor. + </para> + </sect2> + </sect1> + </chapter> + + +<!-- + ********************************** + + PART I: + Discussion and tutorial material + + ********************************** + --> + + + <chapter id="file-operations"> + <title>Rosegarden Files and Documents</title> + <para> + &rosegarden; stores each composition in its own document, using + its own internal format. When you save a document it is stored + on disc as a file with the .rg extension.<footnote><para> + Many users have complained about our opaque binary file + format. It is, in fact, nothing more than gzipped XML. + </para></footnote> &rosegarden; can also + handle a number of other standard file formats. + </para> + + <sect1 id="file-creating"> + <title>New compositions</title> + <para> + When &rosegarden; starts up, it does so with a new document, + containing an "empty" composition ready to start editing. + To put something in that composition, you must either record + something, or create some blank lengths of music (referred + to as "segments") that you can then fill in using the + various editing facilities. + </para> + <para>See <link linkend="recording">Recording</link> for details of how to record music, and see the <link + linkend="segment-view">Track Editor</link> section for a + description of how to create, edit, and manage segments of + music. + </para> + </sect1> + + <sect1 id="file-midi"> + <title>Using MIDI files</title> + <para> + To import and export MIDI files, use the + <menuchoice> + <guimenu lang="en">File</guimenu> + <guimenuitem>Import</guimenuitem> + <guimenuitem>Import MIDI File</guimenuitem> + </menuchoice> + and + <menuchoice> + <guimenu lang="en">File</guimenu> + <guimenuitem>Export</guimenuitem> + <guimenuitem>Export MIDI File</guimenuitem> + </menuchoice> + functions. + </para> + <para> + Although &rosegarden; can load and save file formats such as + MIDI, it does not store MIDI data internally. You should + generally prefer to save files in &rosegarden;'s own format, + as &rosegarden; stores quite a lot of information that will + be lost when exporting to MIDI. This also applies if you merely + import a file, and then immediately export it back out. &rosegarden; + translates the raw MIDI to its internal format, and then translates that format + back into MIDI. Some details of the file structure can and do get + lost or rearranged in this translation, but the resulting performances + should be functionally identical. + </para> + <para> + When a MIDI file is loaded, &rosegarden; splits out the + music into one track per MIDI track or channel in the file, + <link linkend="studio-midi-import">sets up the appropriate + instrument mappings</link>, and <link + linkend="nv-quantization">attempts to calculate plausible + notation</link> for the MIDI performance data. + </para> + </sect1> + + <sect1 id="file-rgproject"> + <title>Rosegarden Project files</title> <para>A Rosegarden + composition file (.rg) contains all of the the note information + for your composition, as well as other data such as MIDI + controller settings, plugin details, and the names of any audio + files referred to in your composition. The audio files + themselves are not stored in the Rosegarden composition file; + instead you are expected to keep track of their location on disk + yourself (see <link linkend="segment-view-audio-segments">Audio + segments</link>). When you need to transfer a project from one + computer to another, or to a friend or colleague, this can be + inconvenient. This is where Rosegarden Project files are + useful. A Project file contains your composition, all of the + audio files it uses, any further data files required for plugins + used in the composition, and any additional files you may want + to include, all in one big bundle.</para> + <para>Use <menuchoice> + <guimenu>File</guimenu> + <guimenuitem>Export</guimenuitem> + <guimenuitem>Export Rosegarden Project file...</guimenuitem></menuchoice> to export the current composition and its associated data into a Rosegarden Project file, and <menuchoice> + <guimenu>File</guimenu> + <guimenuitem>Import</guimenuitem> + <guimenuitem>Import Rosegarden Project file...</guimenuitem></menuchoice> to expand a Rosegarden Project file back into a composition and load it.</para> + + <para>Note that Rosegarden Project format is an interchange + format, not an archival format. Although Rosegarden composition + files are very carefully checked for compatibility from one + Rosegarden version to the next, no long-term guarantees are made for the + Project file format.</para> + </sect1> + + <sect1 id="file-other"> + <title>Other file formats</title> + <para>Rosegarden can export to and import from a number of other file formats. Some of these are described here; see also <link linkend="file-printing">Printing</link> for information about LilyPond file export.</para> + <variablelist> + <varlistentry> + <term>Csound</term> + <listitem> + <para>You can export score files for the Csound synthesis system using + <menuchoice> + <guimenu>File</guimenu> + <guimenuitem>Export</guimenuitem> + <guimenuitem>Export Csound score file...</guimenuitem> + </menuchoice>. Together with a suitable orchestra file (not supplied), this can be used to play the composition through <ulink url="http://www.csounds.com/">Csound</ulink>. Note that not all data in the Rosegarden composition necessarily can or will be saved in the Csound format.</para> + </listitem> + </varlistentry> + <varlistentry> + <term>Mup</term> + <listitem> + <para>You can use <menuchoice> + <guimenu>File</guimenu> + <guimenuitem>Export</guimenuitem> + <guimenuitem>Export Mup file...</guimenuitem> + </menuchoice> + to save the contents of the current composition into a new Mup file. This can then be processed by the <ulink url="http://www.arkkra.com/">Mup</ulink> music publication system, although it is likely that the file may need some tweaking to get really good quality output. Note that not all data in the Rosegarden composition necessarily can or will be saved in the Mup format.</para> + </listitem> + </varlistentry> + <varlistentry> + <term>MusicXML</term> + <listitem> + <para>The <menuchoice> + <guimenu>File</guimenu> + <guimenuitem>Export</guimenuitem> + <guimenuitem>Export MusicXML file...</guimenuitem> + </menuchoice> + function saves the contents of the current composition into a new MusicXML file. This can then be used with any music software that supports the MusicXML format. Note that MusicXML support is experimental and has not been well tested. Not all data in the Rosegarden composition necessarily can or will be saved in the MusicXML format.</para> + </listitem> + </varlistentry> + <varlistentry> + <term>Hydrogen</term> + <listitem> + <para>Rosegarden can import h2song files created by the Hydrogen drum machine. These are imported into a skeletal MIDI-style structure with one track per pattern. The audio samples they use are not imported. Use <menuchoice> + <guimenu>File</guimenu> + <guimenuitem>Import</guimenuitem> + <guimenuitem>Import Hydrogen file...</guimenuitem> + </menuchoice> to import a Hydrogen file.</para> + </listitem> + </varlistentry> + <varlistentry> + <term>Rosegarden 2.1</term> + <listitem> + <para>Use the + <menuchoice> + <guimenu>File</guimenu> + <guimenuitem>Import</guimenuitem> + <guimenuitem>Import Rosegarden 2.1 file...</guimenuitem> + </menuchoice> function to create a new composition from the contents of an existing X11 Rosegarden v2.1 (.rose) file. + </para> + </listitem> + + </varlistentry> + </variablelist> + </sect1> + + <sect1 id="file-merge"> + <title>Merging files</title> <para>As well as loading or + importing files, you can also merge them into the current + document, loading or importing the data from the file, as necessary, + and adding it to the existing composition. + </para> + + <para>To merge a file, just use the relevant option on the + <menuchoice> + <guimenu lang="en">File</guimenu> + <guimenuitem>Merge</guimenuitem> + </menuchoice> + submenu, instead of using the Open or + Import option. + </para> + </sect1> + + <sect1 id="file-printing"> + <title>Printing</title> + <para> + You can print out a composition in the form of a musical + score, using the + <menuchoice> + <guimenu lang="en">File</guimenu> + <guimenuitem>Print</guimenuitem> + </menuchoice> + function or the + <menuchoice> + <guimenu lang="en">File</guimenu> + <guimenuitem>Print with LilyPond</guimenuitem> + </menuchoice> + function. + </para> + + <para> + Producing a score from performance data is a hard task, and + in most cases it's unreasonable to expect a default printout + based on MIDI data to be very readable. You should use the + <link linkend="notation-view">notation editor</link> to tidy + up the score before printing. (See also <link + linkend="nv-quantization">Notation from performance + data</link>.) + </para> + + <para>&rosegarden; is capable of producing very readable scores. Even + so, it is designed to be a screen editor and not primarily a + typesetter. If you want to produce true print-quality scores you + should consider using <ulink + url="http://www.lilypond.org">LilyPond</ulink> in conjunction + with &rosegarden;. LilyPond is music typesetting software that + reads a specialised text file format and produces high-quality + typeset output. &rosegarden; is capable of writing LilyPond files + using the + <menuchoice> + <guimenu lang="en">File</guimenu> + <guimenuitem>Export</guimenuitem> + <guimenuitem>Export LilyPond</guimenuitem> + </menuchoice> + function, and it + features special <link linkend="nv-lilypond-directives">exportable + directives</link> and <link linkend="track-parameters">track + parameters</link> that provide access to LilyPond features for + which there is currently no parallel within &rosegarden;'s own + native interface. + </para> + + <para>LilyPond may be conveniently used with the + <menuchoice> + <guimenu lang="en">File</guimenu> + <guimenuitem>Preview with LilyPond</guimenuitem> + </menuchoice> + function, which exports the file into a temporary file and processes + it directly with LilyPond for preview with a PDF viewer. + If you are happy with the preview, you may print the score using the + printing capability of the PDF viewer, or use the + <menuchoice> + <guimenu lang="en">File</guimenu> + <guimenuitem>Print with LilyPond</guimenuitem> + </menuchoice> + function. + </para> + + <para> + When Export, Preview, or Printing is done with LilyPond, + there is available also a collection of + <link linkend="lilypond-options">LilyPond options</link>. + </para> + </sect1> + + <sect1 id="lilypond-options"> + <title>LilyPond options</title> + <para>If one of the LilyPond export functions is invoked, there will + appear a dialog in which options specific to LilyPond export may be + altered. + </para> + + <variablelist> + <varlistentry> + <term>LilyPond version</term> + <listitem><para> + LilyPond version installed into the system should be automatically + detected in the dialog, but it is possible to export to any other + LilyPond version since 2.6. Historically, LilyPond's syntax has + changed somewhat over time, but since LilyPond version 2.6 changes + have have been less radical and more maintainable.</para> + </listitem> + </varlistentry> + <varlistentry> + <term>Paper size and Landscape</term> + <listitem><para> + Paper size can be A3, A4, A5, A6, Legal, US Letter, and Tabloid. + All paper sizes may also be used in Landscape mode.</para> + </listitem> + </varlistentry> + <varlistentry> + <term>Font size</term> + <listitem><para> + Font size affects the size of the notes. If you want to fit more + staffs into the paper, you should decrease the font size.</para> + </listitem> + </varlistentry> + <varlistentry> + <term>Export content</term> + <listitem><para> + Export content concerns tracks that have segments in them, which + are the tracks that are not empty. + It is possible to export All tracks, Non-muted tracks, the current + Selected track, or Selected segments. If LilyPond export is + launched from the Notation view, Selected segments include + the same selection which was used in opening the Notation view.</para> + </listitem> + </varlistentry> + <varlistentry> + <term>Merge tracks that have the same name</term> + <listitem><para> + It is possible to Merge tracks that have the same name. + This options allows for example to make a piano score with + several independent voices. You may give first three tracks + name "Right" and three next tracks "Left" and then merge + them in LilyPond export. (This provides an easier way to manage + overlapping segments with the price that the top and bottom + parts will have different names on the page. If you wish both + of them to be named, eg. "Piano," then you will have to keep all + of the segments on the same pair of staffs. Consult <ulink + url="http://rosegarden.sourceforge.net/tutorial/supplemental/piano/">Piano + by Example</ulink> for a hands-on demonstration of this.) <!-- + this comment makes absolutely no sense to me(dmm): Sometimes you + may encounter notes that overlap in printed form, you may avoid + them by selecting one of the collapsing notes and fine adjust + its position in Notation view function --> + <menuchoice> + <guimenu lang="en">Adjust</guimenu> + <guimenuitem>Fine Positioning</guimenuitem> + <guimenuitem>Push Right/Left</guimenuitem> + </menuchoice>.</para> + </listitem> + </varlistentry> + <varlistentry> + <term>Export tempo marks</term> + <listitem><para> + Tempo marks are not exported by default. If tempo changes + rarely, you may want to export all tempo marks, but if + tempo changes too often, you may export only the first mark.</para> + </listitem> + </varlistentry> + <varlistentry> + <term>Export lyrics</term> + <listitem><para> + <link linkend="nv-text-lyrics">Lyrics</link> is exported if this + option is checked. Text is entered in Unicode, which + makes it possible to enter lyrics in all languages. Multiple + lines of lyrics per staff is also possible, see the section + on <link linkend="nv-text-lyrics">Editing lyrics</link>.</para> + </listitem> + </varlistentry> + <varlistentry> + <term>Export beamings</term> + <listitem><para> + <link linkend="nv-beamed-groups">Beams</link> defined in + &rosegarden; can be exported, or the default + beam grouping of LilyPond can be used. Future versions + of &rosegarden; may support nested note grouping.</para> + </listitem> + </varlistentry> +<!-- deprecated + <varlistentry> + <term>Add staff group bracket</term> + <listitem><para> + Staff group bracket may be added to cover all staffs. + Future versions of &rosegarden; may support nested staff + groupings.</para> + </listitem> + </varlistentry> --> + <varlistentry> + <term>Lyrics alignment</term> + <listitem><para> + Lyrics is aligned Left by default. Sometimes Center or + Right alignment provides results and more pleasant output.</para> + </listitem> + </varlistentry> + <varlistentry> + <term>Ragged bottom</term> + <listitem><para> + The staffs normally cover the whole page from top to bottom. + When there are only a few staffs, this option places the + extra vertical space at the bottom of the page instead.</para> + </listitem> + </varlistentry> <varlistentry> + <term>Enable "point-and-click" debugging</term> + <listitem><para> + If you export the LilyPond source with the + <menuchoice> + <guimenu lang="en">File</guimenu> + <guimenuitem>Export</guimenuitem> + <guimenuitem>Export LilyPond</guimenuitem> + </menuchoice> + function, you may open the LilyPond source by clicking + notes in the PDF output. Consult <ulink url=" http://lilypond.org/doc/v2.10/Documentation/user/lilypond/Point-and-click#Point-and-click">LilyPond documentation</ulink> for more + information. +</para> + </listitem> + </varlistentry> <varlistentry> + <term>Export \midi block</term> + <listitem><para> + LilyPond is also capable of producing MIDI output. Check this + option if you wish the LilyPond source to use this option. + Note however that MIDI output which you obtain via &rosegarden; + sequencer, via + <menuchoice> + <guimenu lang="en">File</guimenu> + <guimenuitem>Export</guimenuitem> + <guimenuitem>Export MIDI file</guimenuitem> + </menuchoice>, + and via LilyPond's MIDI output may differ considerably.</para> + </listitem> + </varlistentry> <varlistentry> + <term>Headers</term> + <listitem><para> + Headers can be edited both in LilyPond export dialog and through the + <menuchoice> + <guimenu lang="en">Composition</guimenu> + <guimenuitem>Edit Document Properties</guimenuitem> + </menuchoice> function.</para><para>Some of the headers will appear + only in LilyPond output. + The position of the Printable headers match roughly with + the positions of the headers in the printed output. + Below is shown an example with all headers and lyrics + entered with Unicode text.</para> + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="headers-and-unicode-lyrics.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>LilyPond's output showing all headers and Unicode lyrics.</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + </listitem> + </varlistentry> + </variablelist> + </sect1> + + </chapter> + + <chapter id="segment-view"> + <title>The Track Editor</title> + <sect1 id="segment-view-overview"> + <title>Overview</title> + <para> + &rosegarden;'s main layout is similar to many + other popular sequencers. It is based on a track + structure — the main window shows a track editor with + a list of tracks and their associated instruments down the + left hand side. You can manipulate and move blocks of + music data (referred to as “segments”) on the + track editor as well as opening the segments themselves in + specialised editors (<link + linkend="notation-view">notation</link>, <link + linkend="matrix-view">matrix</link>, <link + linkend="percussion-matrix-view">percussion matrix</link>, and <link + linkend="event-view">event list</link>). + </para> + + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-trackeditor.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>&rosegarden;'s Track Editor showing two segments of music data</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + + <para> + Tracks govern what sort of segment you can create in a particular + place. If you create a segment on an audio track, it will be an audio + segment, no matter where that segment subsequently moves. If you + create a segment on a &MIDI; track, it will always be a &MIDI; + segment. You can set <link linkend="track-parameters"> + track parameters</link> to pre-select various segment properties at the track + level, and to exercise fine control over &MIDI; recording. + </para> + <para> + Tracks can be assigned to a range of &MIDI;, plugin synth, or + audio instruments. In the picture above we see three segments + in the track editor on tracks assigned to General MIDI + instruments. + </para> + + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-trackbutton-labels.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>&rosegarden;'s Track buttons showing track labels</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + + <para> + The button area to the left of the segment canvas shows you + the track number, mute and record status, and the label of the + track. You can mute or unmute a track by clicking on the blue + LED-style button, and select a particular track as a record + target by clicking on the red one. To change the track label, + double-click on it. + </para> + + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-trackbutton-instruments.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>&rosegarden;'s Track buttons showing instrument assignments</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + + <para> + Track labels are only shown if the + <menuchoice> + <guimenu lang="en">Settings</guimenu> + <guimenuitem>Show Track Labels</guimenuitem> + </menuchoice> + menu option is enabled. + Otherwise, as in this picture, the instrument assignments for + the tracks are shown instead.</para> + + </sect1> + <sect1 id="segment-view-instruments"> + <title>Tracks and instruments</title> + <para> + Each track must have an instrument assigned to it, in order to + be heard. By default the first 16 tracks are assigned to the + 16 instruments of the first available MIDI device, and the + next 16 tracks are assigned to audio.</para> + + <para>To change the instrument assignment for a track, + right-click on the track label: a pop-up menu will appear from + which you can select among all the available instruments. + </para> + + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-trackbutton-instrumentmenu.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>&rosegarden;'s Instrument menu</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + + <para> + An instrument can be understood as a single channel on a + &MIDI; device, or as a mono or stereo audio output or an audio + synth plugin. Tracks containing note data should be assigned + to &MIDI; or synth plugin instruments, and those containing + audio to audio instruments. You can assign more than one + track to the same instrument, in which case the multiple + tracks will produce sounds in the same way (&MIDI; tracks playing + panned to the left with a flute, or audio tracks playing with the same + volume levels, through the same stack of <link linkend="studio-plugins"> + plugins</link>.) + </para> + <para> + You can change various properties of the instrument + associated with a track using the <link + linkend="segment-view-instrumentparameterbox">Instrument + Parameter Box</link>. This is where, for example, you would + set a MIDI instrument to use a particular patch and so + produce a particular sound (piano, strings etc). + </para> + <para> + See the + <link linkend="studio-introduction">Studio</link> section + for more about instruments. + </para> + + </sect1> + <sect1 id="segment-view-creating"> + <title>Creating segments</title> + + <para> + To create an empty segment, in order to begin composing + something new, you need to use the pencil tool (which is normally the + default active tool when you first start &rosegarden;). Click on + the pencil on the toolbar, and then click at the point where + you want the segment to start (at the correct height for the + track you want the segment to be on, and at a distance + across the editor window corresponding to the correct time) + and drag rightwards until the segment is the right number of + bars long. + </para> + + <para>You can also create segments using the <link + linkend="segment-view-selector">Select tool</link>, by clicking + and dragging either with the middle mouse button, or with the + left button and Ctrl held down.</para> + + + <para>If you want to draw a segment longer than the visible + portion of the canvas, the canvas will scroll automatically once you + reach its edge. If you keep dragging past the end of the entire + composition, you can keep dragging, and will push the end marker right along + with you. (This is a welcome contrast to earlier versions of + &rosegarden;.) + </para> + + <para> + Usually each new segment starts on a barline and extends bar + by bar, but this snap-to-grid effect can be prevented by + holding down Shift while clicking and dragging. + </para> + + <para>New segments are created in a yellow colour, with a treble clef by + default. You may wish to jump ahead and have a look at <link + linkend="track-parameters">track parameters</link> to explore + other possibilities. + </para> + + <para>If you wish to draw a segment that begins in the middle of an + existing segment, hold Ctrl and Alt when clicking. The track will + automatically expand to accommodate this new segment. This is especially + useful for some situations involving music notation. + </para> + + <para> + Once you have created a segment, you can then begin editing + using the <link linkend="matrix-view">matrix</link>, <link linkend="percussion-matrix-view">percussion matrix</link> or <link + linkend="notation-view">notation</link> editors. To use one + of these editors, either double-click on the segment, or + else click with the right mouse button and choose the editor + you want from the context menu. + </para> + + <para> + If you are intending to <link + linkend="recording">record</link> from a MIDI device or audio + input, you don't need to create a new segment to record into + first -- each separate recording always goes into a new + segment, created automatically during recording. + </para> + </sect1> + + <sect1 id="segment-view-audio-segments"> + <title>Audio segments</title> + <para> + An audio segment contains recorded or sampled audio data, + instead of editable note-event data. Rosegarden allows you to + record, play, arrange and split audio segments, but does not + contain audio waveform editing facilities. + </para> + <para>To create an audio segment, you can <link + linkend="recording">record</link> from an audio source onto a + track assigned to an audio instrument, or you can work with + existing WAV files. To do this, you need to use the audio + manager dialog (reached via <menuchoice><guimenu + lang="en">File</guimenu><guimenuitem>Manage Audio Files</guimenuitem></menuchoice>). + </para> + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-audiofilemanager.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>The audio file manager</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + + <para>You can drag-and-drop audio files from the KDE file + browser or your KDE desktop into the audio file manager, or you + can open them using its File menu. Then you can either + drag-and-drop them onto Rosegarden's track canvas, or use the + audio file manager's <menuchoice><guimenu + lang="en">Action</guimenu><guimenuitem>Insert into Selected + Audio Track</guimenuitem></menuchoice> menu function, provided the current + selected track in the main window is assigned to an audio + instrument. Newly-recorded audio segments also appear in the + audio file manager dialog.</para> + + <para>Details of the audio files associated with a particular + composition are saved with that composition, but the audio files + themselves are not. You should ensure your document has a + sensible audio file search path (via <menuchoice><guimenu + lang="en">Composition</guimenu><guimenuitem>Edit Document + Properties...</guimenuitem><guimenuitem>Audio</guimenuitem></menuchoice>) + so as to keep your audio files accessible together. You can also export + your project to a &rosegarden; project package file (.rgp) via + <menuchoice><guimenu lang="en">File</guimenu> + <guimenuitem>Export</guimenuitem><guimenuitem>Export Rosegarden Project File + </guimenuitem></menuchoice> to collect any scattered audio files + together in one place.</para> + + <para>The audio manager dialog also shows the sample-rate and + other information for each audio file, and marks with an + asterisk any audio file whose sample rate does not match that of + the current JACK audio session that Rosegarden is using. + Rosegarden will resample these files at playback time using a + very low quality zero order hold resampler. You are advised to + resample them separately using a separate dedicated audio editor + instead. + </para> + + </sect1> + + <sect1 id="segment-view-manipulating"> + <title>Manipulating segments</title> + <para> + The main window contains a selection of "tools" for editing + segments. These are available from the main toolbar: first + select the tool you want from the toolbar, and then click + and drag on the segments on the main canvas. + </para> + + <sect2 id="segment-view-selector"> + <title>The Select tool</title> + <para> + The select tool <inlinemediaobject> + <imageobject> + <imagedata fileref="rg-select.png"/> + </imageobject> + </inlinemediaobject> + is actually a + multipurpose tool: it can be used to select, move, copy, + resize and create segments.</para> + + <para>The most obvious use is + selection: select a single segment by clicking on it with + the select tool, or select several by clicking with Shift + held down, or by clicking in an empty area of the window and + dragging out an area. + </para> + + <para>To move segments with the select tool, simply click and + drag on the segment. To create copies, click and drag with + Ctrl held down. To resize a segment, click and drag on the + right-hand edge of the segment. To create new segments, click + and drag on an empty area either with the middle mouse button + or with the left mouse button and Ctrl held down.</para> + + <para> + The select tool doesn't replace the other tools completely, + though — sometimes you need to be more precise about + which operation you intend, particularly when working on small + segments. + </para> + + </sect2> + + <sect2 id="segment-view-move-resize"> + <title>Move and Resize tools</title> + <para>To move a segment to a different start time or track, + use the move tool <inlinemediaobject> + <imageobject> + <imagedata fileref="rg-move.png"/> + </imageobject> + </inlinemediaobject> + and click and drag on the segment you want + to move. If you hold down the Ctrl key while dragging, the + segment will be copied instead of moved.</para> + + <para>To resize a segment, use the resize tool <inlinemediaobject> + <imageobject> + <imagedata fileref="rg-resize.png"/> + </imageobject> + </inlinemediaobject> + and click and drag on the right-hand end of the segment. + Resizing a segment has the effect of extending or + shortening it, by subtracting some of its contents or adding + silence at the start or end. If you hold down the Ctrl + key, the segment will be <link + linkend="segment-view-rescale">rescaled</link> (stretched + or squashed) instead of extended or shortened.</para> + + <para>For both move and resize you can hold Shift for fine + positioning, to avoid snapping to a particular grid position. + </para> + + </sect2> + + <sect2 id="segment-view-rescale"> + <title>Stretching and squashing segments</title> + <para>Resizing a segment normally makes it shorter or longer + by subtracting content or adding some extra space. However, + by holding the Ctrl key while resizing, you can instead + stretch or squash the contents of the segment. You can also do this by selecting the segment and then using <menuchoice><guimenu lang="en">Segments</guimenu> + <guimenuitem>Stretch or Squash...</guimenuitem></menuchoice>.</para> + <para> + For segments that contain MIDI events, this re-spaces the + events so that they are spread across the new segment's + duration, playing back faster or slower than before but in + the same relative proportions. + </para> + <para> + For audio segments, this time-stretches the audio, altering + its played speed without altering its pitch (as would happen + if the audio was simply played back faster or slower). + Time-stretching usually adds some audible artifacts as well, + so the quality of your results may vary. + </para> + <para> + &rosegarden; does not alter the original audio file when + time-stretching an audio segment, and if you rescale the same + segment repeatedly it will always work from the original + file instead of accumulating timestretching artifacts with + each rescale. You can rescale both mono and stereo audio. + </para> + <para> + (For reference, &rosegarden; uses a frequency-domain + time-stretcher based on a phase vocoder with phase-locking + at percussive transients. This usually produces good + results with stable harmonic sounds such as pads and basses + as well as purely percussive sounds such as drum loops, but + is less effective for composite material or music with soft + or breathy note onsets.) + </para> + </sect2> + + <sect2 id="segment-view-split-join"> + <title>Split tool</title> + <para> + You can use the split tool + <inlinemediaobject> + <imageobject> + <imagedata fileref="rg-split.png"/> + </imageobject> + </inlinemediaobject> + to split a single segment + into two separate segments. To split your segment, select the + split tool and click on the segment you wish to split. + </para> + <para> + By default segments are split on the closest barline to the + cursor, but this can be prevented by holding down Shift + while splitting the segment. + </para> + + </sect2> + + <sect2 id="segment-view-split-by-pitch"> + <title>Other Split functions</title> + <para>The Segments menu contains a number of other Split functions.</para> + <variablelist> + <varlistentry> + <term>Split on Silence</term> + <listitem><para><menuchoice> + <guimenu>Segments</guimenu> + <guimenuitem>Split</guimenuitem> + <guimenuitem>Split on Silence</guimenuitem> + </menuchoice> + splits the selected segments on silences. + This function works slightly differently depending + on whether the selected segments contain audio or + MIDI data. For audio segments, it offers you a + dialog in which you can choose a threshold below + which the segment is considered "silent"; it then + splits the segment whenever its amplitude falls + below this threshold. For MIDI segments, it simply + splits the segment everywhere that a full bar of + silence occurs. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>Split by Pitch</term> + <listitem><para> + <menuchoice> + <guimenu>Segments</guimenu> + <guimenuitem>Split</guimenuitem> + <guimenuitem>Split by Pitch...</guimenuitem> + </menuchoice> + splits the currently selected segments into higher and + lower parts. + + This function invokes a dialog allowing you to + choose a pitch as a "split point", and then splits + the selected segments in half with all the notes on + or above that split point in the "higher" segment + and all the notes below it in the "lower". + + </para> + <para> + If the music in the segment consists of two separate + parts (e.g. left and right hand piano parts) that + are not always completely on either side of a single + split point, you may with to select the "ranging + split-point" option. If this is selected, + Rosegarden will attempt to track the two parts as + they move up and down, usually doing a slightly + better job of separating out notes that were + intended to lie in the two separate parts. + + </para> + <para> + The resulting segments are both created on the same + track, with one overlapping the other. + + </para> + </listitem></varlistentry> + + <varlistentry> +<term>Split by Recording Source</term><listitem><para><menuchoice> + <guimenu>Segments</guimenu> + <guimenuitem>Split</guimenuitem> + <guimenuitem>Split by Recording Source...</guimenuitem> + </menuchoice> splits the currently selected segments according to the MIDI channel and device their events were recorded from.</para><para>If you have recorded events from more than one MIDI channel or device into the a single segment, you can use this function to split them into separate segments afterwards. Select the channel or device whose events you want to split out, and the segment will be split into two segments, one containing events from the selected channel or device and the other containing the remaining events. The two segments are both created on the same track, with one overlapping the other.</para><para>See also <link linkend="recording">Recording</link> and <link linkend="track-recording-filters">Track recording filters</link> for more details on how to select the source MIDI channel or device for a recording.</para></listitem></varlistentry> + + + <varlistentry> + <term>Split at Time</term><listitem><para>The <menuchoice> + <guimenu>Segments</guimenu> + <guimenuitem>Split</guimenuitem> + <guimenuitem>Split at Time...</guimenuitem> + </menuchoice> function simply splits the currently selected segments into two parts at the time you specify.</para></listitem></varlistentry> + + </variablelist> + + </sect2> + </sect1> + + <sect1 id="segment-view-tempo-timesig"> + <title>Tempo and Time Signature</title> + + <sect2 id="tempo"> + <title>Tempo in Rosegarden</title> + <para> + &rosegarden; considers a composition to be accompanied by a + single stream of "tempo changes" and "time signature + changes", which you can edit to adjust the tempo and the + number and structure of beats in each bar.</para> + + <para>A tempo change + can be to a constant fixed tempo, or it can be "ramped" + — changing smoothly to a different target tempo at a + given future time. Each tempo change takes effect until the + following one is reached, so any two consecutive tempo changes + together describe a region that will be played at a constant + or smoothly ramping tempo. + </para> + + <para> + Tempo and time signature are related, because &rosegarden; + displays tempo in beats per minute, and the duration of a + beat depends on the time signature. &rosegarden; only + permits a single time signature to be in effect in any given + bar (that is, you can't have different time signatures in + different tracks). Each new time signature causes a new bar + to start, so you can place two time signatures closer + together than the natural bar duration in order to obtain a + partial bar. + </para> + </sect2> + + <sect2 id="tempo-ruler"> + <title>Tempo rulers</title> + <para> + The &rosegarden; <link linkend="segment-view">track editor</link>, <link + linkend="matrix-view">matrix editor</link> and <link + linkend="notation-view">notation editor</link> each contain + a tempo ruler, which can be optionally displayed at the top + of the editing area.</para> + + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-temporuler.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>&rosegarden;'s tempo ruler (and the bar and beat ruler beneath it)</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + + <para>The tempo ruler shows changes to tempo and time + signature throughout the composition, and can be used for + editing tempo.</para> + + <para>To increase or decrease the tempo within the range of a + single tempo change, click and drag the horizontal line (or + sloped line, for ramped tempos) representing that tempo + upwards or downwards.</para> + + <para>To insert a new tempo change, right-click on the ruler + for a menu and select <guimenuitem>Insert Tempo + Change</guimenuitem>. This will insert a new tempo change + with the same tempo as the prior one, which you can then drag + to increase or decrease.</para> + + <para>You can also click and drag the starting point of a + tempo change left or right to move that tempo change to a + different time, and you can click and drag the ending point of + a tempo change up or down to make the tempo ramp gradually + towards an ending tempo value.</para> + + <para>Double-click on the tempo ruler to open the <link linkend="tempo-timesig">tempo and + time signature editor</link>.</para> + +</sect2> + +<sect2 id="tempo-timesig"> + <title>Tempo and time signature editor</title> + + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-tempotimesig.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>&rosegarden;'s tempo and time signature editor</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + + <para>The tempo and time signature editor window lists all of the tempo and time signature changes in the composition. You can edit an individual tempo or time signature change by double-clicking on it.</para> + + </sect2> + + <sect2 id="tempo-edit"> + <title>Changing Tempo</title> + <para> + You can edit an existing tempo change, or add a new one, by using the <link linkend="tempo-ruler">tempo ruler</link>, by double-clicking on the tempo display in the <link linkend="transport">Transport window</link>, by using the <menuchoice> + <guimenu>Composition</guimenu> + <guimenuitem>Add Tempo Change...</guimenuitem> + </menuchoice> menu function, or by double-clicking on an existing tempo in the <link linkend="tempo-timesig">tempo and time signature editor</link>. Each of these will bring you to some variation of the tempo editing dialog:</para> + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-tempodialog.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>&rosegarden;'s tempo dialog</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + <para>To set a new tempo, either dial it into the numeric tempo spinbox at the top, or else click repeatedly on the Tap button at approximately the speed you want and let &rosegarden; work out the tempo for you. + </para> + <para>By default, a new tempo is "fixed"; that is, the tempo remains constant from the tempo change until the next tempo change is reached. Alternatively, you can tell &rosegarden; to make the tempo ramp smoothly to a particular value, or to the following tempo value, by the point at which the next tempo change is reached. See also <link linkend="tempo">Tempo</link> for more details on tempo handling.</para> + </sect2> + + <sect2 id="time-signature"> + <title>Time signature</title> + <para> + To change the time signature, use <menuchoice> + <guimenu>Composition</guimenu> + <guimenuitem>Add Time Signature Change...</guimenuitem> + </menuchoice> or double-click on the existing time signature in the <link linkend="transport">Transport window</link> or <link linkend="tempo-timesig">tempo and time signature editor</link>.</para><para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-timesigdialog.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>&rosegarden;'s time signature dialog</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + </sect2> +<sect2 id="tempo-from-segment"> + <title>Setting tempo from an existing segment</title> + <para>&rosegarden; provides two ways to set tempo from a segment that you have recorded or imported:</para> + <variablelist> + <varlistentry> + <term>Audio Segment Duration</term> + <listitem><para>Use the <menuchoice> + <guimenu>Composition</guimenu> + <guimenuitem>Set Tempo to Audio Segment Duration</guimenuitem></menuchoice> function when you have imported or recorded an audio segment that you know is exactly one bar long, and you want to ensure that the tempo for surrounding note events is set appropriately.</para><para>This function uses the duration of the selected segment (which must be an audio segment of a single bar) to work out a single matching tempo setting. It does not analyse the content of the audio segment in any way; it simply looks at how long it is.</para> + </listitem> + </varlistentry> + <varlistentry> + <term>Beat Segment</term> + <listitem><para><menuchoice> + <guimenu>Composition</guimenu> + <guimenuitem>Set Tempos from Beat Segment</guimenuitem></menuchoice> analyses a segment of MIDI events that are assumed to be at beat positions for the current time signature, and sets a series of tempo changes according to the time elapsed between consecutive beats.</para> + <para>You can use this to set an overall tempo map for a composition by "tapping" tempo in a recorded segment. For example, you can record from a MIDI keyboard and tap a series of single notes at approximate beat positions, speeding up and slowing down gradually; then select the recorded segment and use this function to set a tempo map that speeds up and slows down to match your tapping.</para> + </listitem> + </varlistentry> + </variablelist> + </sect2> + + </sect1> + + <sect1 id="markers-ranges-loops"> + <title>Markers, ranges, and loops</title> + <sect2 id="markers"> + <title>Markers</title> + + <para>Markers are moments in time that have labels. You can + create any number of markers in your &rosegarden; composition, + to define particular points that you wish to remember the + locations of. Marker positions and labels will be saved in + your &rosegarden; file.</para> + + <para>Markers are shown in the main ruler at the top of each + of &rosegarden;'s editor windows.</para> + + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-markerloop.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>A marker and a loop range</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + <para>To add + a new marker, double-click on the marker area (top half) of + the ruler to open the marker editor. Make sure &rosegarden;'s + playback pointer (see <link linkend="transport">The + Transport</link>) is in the location you want to add the + marker at, and then click the Add button to add a new marker + at the playback position. You can then double-click on the + marker's entry in the marker editor window to edit its name or + adjust its location.</para> + + <para>Click on the text of a marker in the marker ruler to + move the playback pointer directly to that marker.</para> + + <para>You can set a <link linkend="ranges-loops">loop range</link> + between two marker positions, by clicking in the area between + the markers in the marker ruler with the Shift key + pressed.</para> + </sect2> + + <sect2 id="quick_marker"> + <title>Quick Marker</title> + + <para>The quick marker is a special moment in time that can be defined + on the fly with a single key (by default Ctrl-1) from the main window + (track editor). Once defined it appears as a red line in the loop ruler + (it does not appear among other markers, since it does not have a label). + At any time when in the track editor you can jump to the quick marker + position with a single key (by default simply 1). + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-quickmarker.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>Quick Marker at the start of the third bar</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + + <para>A typical use of the quick marker is when you want to record the same bars + on different instruments: after setting the quick marker at the first bar of + the working interval, it is easy to jump to the quick marker each time you need + to record a new part.</para> + + <para>Note that the quick marker position is not saved in your &rosegarden; file.</para> + </sect2> + + <sect2 id="ranges-loops"> + <title>Ranges and loops</title> + <para> + &rosegarden; allows you to highlight a period of time in the + main ruler, which will be used as a "range" for editing + operations and which will be looped during playback. + </para> + + <para>To set the current range, click and drag with the Shift + key pressed on the subdivided area of the main ruler at the + top of the editing window. The range that you drag will be + highlighted in white as you drag it, and will snap to the + nearest beat boundary at both ends. Any subsequent playback + will then be constrained to looping this range. + </para> + + <para>You can also set a range between two <link + linkend="markers">markers</link> by shift-clicking between the + marker positions in the marker ruler, or set a range using the + <link linkend="transport-overview">Transport</link> window. + The Transport contains small buttons to set the start and end + of the current range to the current playback pointer position. + Either of these methods allows you to set more precise end + points for your range than you can with click-drag.</para> + + <para>To clear a range and restore normal playback, click on + the subdivided area of the main ruler with the Shift key + pressed, or toggle the loop button on the Transport.</para> + + <para>Note that playback looping when a range is defined is + not the same thing as the <link + linkend="segment-view-segmentparameterbox">repeating + segment</link> function available in the segment parameters + (which seamlessly repeats individual segments rather than + causing the transport to jump).</para> + + <sect3 id="range-operations"> + <title>Range editing</title> + + <para>You can carry out edits + on the current range in order to cut and paste sections + of music that include the relevant parts of all + segments, tempos and time signatures within the range. + </para> + + <para>Set a range and then use the <menuchoice> <guimenu + lang="en">Edit</guimenu> <guimenuitem>Cut + Range</guimenuitem> </menuchoice> or + <menuchoice><guimenuitem>Copy + Range</guimenuitem></menuchoice> menu functions to cut or + copy the range to the clipboard.</para> + + <para>You can paste a range using the standard <menuchoice> + <guimenu lang="en">Edit</guimenu> + <guimenuitem>Paste</guimenuitem></menuchoice> menu function + to overlay its contents onto the rest of the composition at + the current playback pointer position, or you can use + <menuchoice> <guimenu lang="en">Edit</guimenu> + <guimenuitem>Paste Range</guimenuitem></menuchoice> to + insert the range from the clipboard into the composition at + the current playback pointer position.</para> + + </sect3> + + <sect3 id="range-insert"> + <title>Inserting a range</title> + + <para>You can also insert an empty range at the current + playback position using the <menuchoice> <guimenu + lang="en">Edit</guimenu> <guimenuitem>Insert + Range</guimenuitem> </menuchoice> menu function. You can + specify how much space you want to insert, and then all of + the segment content, tempos and time signatures following + the playback position will be pushed along in time by that + duration to leave an empty space. + </para> + </sect3> + + </sect2> + </sect1> + + <sect1 id="triggered-segments"> + <title>Triggered segments</title> + + <para>A triggered segment is a segment that does not appear on + the main canvas and is not positioned at a particular time or + on any particular instrument, but is instead triggered during + playback by one or more notes in other segments. These + triggering notes serve as a shorthand for the full triggered + segment, in the same way as written ornaments such as trills + in notation serve as shorthand for the notes that make up the + trill. One use of triggered segments is in fact for + <link linkend="nv-ornaments">playing ornaments</link>.</para> + + <para>Rosegarden can optionally stretch or squash each triggered + segment to match the duration of the note that triggers it, and + can raise or lower the pitch and velocity of the segment likewise + to match. A triggered segment is played on the same instrument as + its triggering event.</para> + + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-triggersegment.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>&rosegarden;'s Trigger Segment dialog, as reached from the matrix editor</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + + <para>Triggered segments are managed through a window available + via the <menuchoice> <guimenu + lang="en">Segments</guimenu><guimenuitem>Manage Triggered + Segments</guimenuitem></menuchoice> option in the main segment + canvas. To make a new triggered segment, copy a segment or part + of a segment to Rosegarden's clipboard, then use the <menuchoice> + <guimenu lang="en">Edit</guimenu> <guimenuitem>Paste as New + Triggered Segment</guimenuitem></menuchoice> menu option in this + manager window. You can then set a particular note to play this + triggered segment instead of the original note, using the + <menuchoice> <guimenu lang="en">Adjust</guimenu> + <guimenuitem>Trigger Segment...</guimenuitem></menuchoice> + function in the matrix or <menuchoice> <guimenu + lang="en">Note</guimenu><guimenuitem + lang="en">Ornaments</guimenuitem> <guimenuitem>Trigger + Ornament...</guimenuitem></menuchoice> function in the notation + editor.</para> + + <para>When triggering a segment, you will be offered a choice for + how it is played in terms of timing, because the triggered segment + (or ornament) may have a different underlying duration from your + triggering note. The options for playback timing are:</para> + + <variablelist> + + <varlistentry> + <term>As stored</term> + <listitem> + <para>Play the triggered segment with a start time + coinciding with that of the note, and at the original speed. + Keep playing the triggered segment until it ends, even if it + is longer than the triggering note. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>Truncate if longer than note</term> + <listitem> + <para>Play the triggered segment with a start time + coinciding with that of the note, and at the original speed. + If the triggered segment is longer than the triggering note, + truncate it so that it ends at the end time of the note. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>End at same time as note</term> + <listitem> + <para>Play the triggered segment with its end time + coinciding with the end of the note, and at the original + speed. This means the start of the triggered segment may be + chopped off if it is longer than the triggering note. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>Stretch or squash segment to note duration</term> + <listitem> + <para>Speed up or slow down the triggered segment so that it + fits exactly into the duration of the triggering note. This + is the default. + </para> + </listitem> + </varlistentry> + + </variablelist> + + <para>A triggered segment may contain silence at the start or end, + and this will be "played" (and stretched or squashed if + appropriate) as well as the notes and other events in the segment.</para> + + <para>It is not currently possible to make a triggered segment + start playing before the start time of its triggering note. You + also can't trigger a segment from within another triggered + segment, and you can't trigger audio segments.</para> + + <para>To edit the contents of a triggered segment, either + double-click on it in the Manage Triggered Segments window, or + double-click on any note that triggers it. Apart from editing the + notes in the segment, you can also change the duration of the + segment itself from the Edit menu of the resulting event list + view. Remember that editing a triggered segment will affect all + the notes that trigger it, not just the one that you + double-clicked to get to the editing window.</para> + + </sect1> + </chapter> + + <chapter id="transport"> + <title>The Transport</title> + <para> + When you play a composition, + &rosegarden; sweeps a playback pointer across + the tracks from left to right playing the contents of the + segments as it crosses them. The pointer's position on the + screen is tracked and controlled by a window called the + Transport. + </para> + + <sect1 id="transport-overview"><title>Overview</title> + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-transport.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>&rosegarden;'s Transport window</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + + <para> + If the Transport isn't visible, you can activate it with <menuchoice> <guimenu lang="en">Settings</guimenu> + <guimenuitem>Show Transport</guimenuitem> </menuchoice>. + </para> + + <para>The Transport shows the time reached by the playback + pointer, in seconds by default.</para> + + <para>You can switch it to show + musical time (bar and beat counts), musical time with a flashing + visual metronome, or audio sample frame times, using the topmost + of the small buttons <inlinemediaobject> + <imageobject> + <imagedata fileref="rg-button-bar-time.png"/> + </imageobject> + </inlinemediaobject> on the left of the transport window.</para> + + <para>The + button immediately below that <inlinemediaobject> + <imageobject> + <imagedata fileref="rg-button-from-end.png"/> + </imageobject> + </inlinemediaobject> toggles the display so as to show + time remaining to the end of the composition instead of from the + start.</para> + + <para> + The main controls on the transport start the sequencer playing + and pause it, fast forward the pointer position, rewind it, stop + it or jump to beginning or end of composition. + </para> + + <para> + The transport display also shows the tempo and time signature in + effect at the current playback position. Double-click on either + of these to insert a new tempo or time signature change. See + <link linkend="segment-view-tempo-timesig">Tempo and Time + Signature</link> for more ways to adjust these elsewhere in Rosegarden. + </para> + + <para> + You can also double-click anywhere on the main time display on + the transport window, to enter a precise time that you want the + playback position to be set to. + </para> + + <para>Additional controls and a &MIDI; event display are hidden on + the bottom flap on the transport, which can be toggled on or off + using the arrow button next to it at the left. Also on this extra + portion there are buttons for recording, setting the loop start + and end (see <link linkend="ranges-loops">Ranges and loops</link>), + soloing individual tracks, turning on or off the metronome (see + <link linkend="studio-metronome">Metronomes</link>), and silencing + your MIDI devices (the panic button). </para> + + </sect1> + <sect1 id="recording"> + <title>Recording</title> + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-trackbuttons.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>Track buttons in various states of recording readiness</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + <para> + To record a new segment into a track, first make sure the + right tracks are armed for recording by selecting the red + (for audio tracks) or yellow (for MIDI tracks) LED-style + buttons on the track labels, and then use the <link + linkend="transport-overview">Transport's</link> record + control. This has the effect of both starting the transport, + thus playing the existing composition, and recording into the + appropriate track, or tracks. + </para> + <para> + You can record any number of &MIDI; and audio tracks at once so long + as your computer is powerful enough, and you have enough disk space. + Be careful not to accidentally leave tracks selected when you have + finished using them and are trying to record somewhere else. + </para> + <para> + Alternatively you can use punch-in record to separate the acts + of starting the transport and entering record mode. Punch-in + record is toggled with the <keycap>Space</keycap> bar. You can press + <keycap>Space</keycap> + while playing a composition to switch instantly between + playback and recording without stopping the transport, or you + can use <keycap>Space</keycap> to arm for recording when the transport is + stopped, so that a subsequent Play will in fact record as + well. (The latter is handy when synchronising to an <link + linkend="transport-external">external transport</link>.) + </para> + <para> + If you record to MIDI tracks, you will record from the + MIDI devices that are selected for recording in the + <link linkend="studio-device-editor">MIDI device + manager</link>, as filtered through the <link + linkend="track-recording-filters">track level recording filter</link> + and the global <link linkend="studio-midi-filters">MIDI filters</link>. + </para> + <para> + If you record to audio tracks, your recording to each track + will be from the input currently selected for that track's + instrument in the <link + linkend="segment-view-instrumentparameterbox">instrument + parameter box</link>. This will either be an external audio + input or an audio submaster or master (for performing + mixdowns). If it's an external input, it will by default + record from your soundcard's first available physical record + in. You may wish to use a JACK connection tool to + connect some other JACK audio application to the input + instead. See also <link + linkend="studio-audio-routing">Audio Routing</link>. + </para> + </sect1> + <sect1 id="transport-external"> + <title>Synchronising to external transports</title> + <sect2 id="transport-jack"> + <title>JACK Transport</title> + <para> + Rosegarden supports the JACK transport mechanism for + synchronising its transport with other JACK applications on + the same computer. To activate it, go to + <menuchoice> + <guimenu lang="en">Settings</guimenu> + <guimenuitem>Configure Rosegarden...</guimenuitem> + </menuchoice> + and check the <guimenuitem>Use JACK transport</guimenuitem> box.</para> + + <para>When the JACK transport is in use, all of the applications + that are subscribed to it share a common transport control, and + you can start, stop, and move the transport from any one of + them.</para> + + <para>Many Linux audio applications that use the JACK audio + server also support JACK transport: consult their + documentation for details of whether and how.</para> + </sect2> + <sect2 id="transport-mtc"> + <title>MIDI Time Code</title> + <para> + Rosegarden supports MIDI Time Code (MTC) synchronisation in + master and slave modes. This is particularly useful for + synchronising the Rosegarden transport with a hardware + MTC-capable device, or with software running on other + computers connected via MIDI. + </para> + <para>To make Rosegarden the MTC Master, so that it will + control any MTC slave device or application connected to it, + go to + <menuchoice> + <guimenu lang="en">Settings</guimenu> + <guimenuitem>Configure Rosegarden...</guimenuitem> + </menuchoice> + and in the MIDI page's MIDI Sync tab, select "MTC + Master" from the MIDI Time Code menu. To make Rosegarden an + MTC Slave so that Rosegarden's transport will automatically + be synchronised with incoming MTC events, select "MTC + Slave". + </para> + </sect2> + </sect1> + + <sect1 id="infrared-remote-controls"> + <title>Infrared Remote Controls</title> + <para> + Rosegarden supports infrared remote controls for + almost all transport functions. In order to use it, + you need either the internal LIRC client, which is + an optional feature at Rosegarden's compile time, + or the KDE IRKick application (KDE LIRC daemon) + that you can find in your Linux distribution's + repositories. In both cases, you need to install + and configure the LIRC server daemon. The exact + details depend on your remote control and receiver, + and you should refer to the <ulink url="http://www.lirc.org/html"> + LIRC web site</ulink> for more information. + </para> + + <para> + You can find more details online about the internal + LIRC client configuration file and IRKick basics, at + <ulink url="http://www.rosegardenmusic.com/resources/documents/infrared-remotes.shtml"> + Rosegarden's web site</ulink>. + </para> + </sect1> + </chapter> + + <chapter id="studio"> + <title>The Studio</title> + + <sect1 id="studio-introduction"> + <title>Devices, instruments and connections</title> + + <para>Rosegarden uses the term Studio to refer to everything it + knows about the sound systems attached to the computer. This + may include &MIDI; and audio hardware and other sound software, + and includes information about connections, configuration, + &MIDI; patches and so on. The Studio is built-in to every + composition you create with Rosegarden.</para> + + <para>Three pieces of terminology are essential here: + + <variablelist> + + <varlistentry> + <term>Device</term> + <listitem> + <para>A <quote>device</quote>, as far as Rosegarden is + concerned, is simply something capable of producing + sounds. This may be a MIDI or audio device. MIDI + devices do not necessarily correspond directly to + physical MIDI ports: they are just things with names + that you can refer to, expected to work in particular + ways. Configuration information such as MIDI patch maps + can be attached to devices. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>Instrument</term> + <listitem> + <para>Each device has a number of + <quote>instruments</quote>, each of which is assumed + to make a particular sound. These are the things that + you can assign tracks to in order to choose which + sound they play. By default, a device contains 16 + instruments, created for you at startup: if the device + is a MIDI device, then these will each be initialised + to one of the 16 MIDI channels. The instrument is + where you set all the properties of a particular + voice, such as program settings, reverb, volume etc. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>Connection</term> + <listitem> + <para>While a MIDI device is simply a name and a + collection of configuration information, the + <quote>connection</quote> specifies which MIDI port it + is physically attached to. This can be configured in + the <link linkend="studio-device-editor">MIDI device + manager</link>. (Audio and synth plugin devices do not + have connections in the same way.) + </para> + </listitem> + </varlistentry> + </variablelist> + </para> + + <para>For example, imagine a setup consisting of a PC with two + physical MIDI ports, one of which has an external synth + attached to it. Here you would normally configure Rosegarden + so as to have one MIDI device, corresponding to the synth. + You could then configure this device with the correct name and + patch map, and then specify a connection for it that + corresponded to the relevant MIDI port on your soundcard. + Each of the 16 default instruments on the device could then be + configured with a suitable program, and you would then assign + tracks to those.</para> + + <para> + In practice, Rosegarden will by default create a device for + each of the available connections on startup. So in the + example above, two MIDI devices will be created by default + even though you only need one. You would generally then + rename and apply patch maps to the first, and delete or + simply not use the second. Remember that there is no way + for Rosegarden to know what synths you actually have plugged + in to the MIDI ports on your computer: for this reason, the + devices created at startup are just intended to be a default + set, and it's up to you to ensure that the devices you + configure match those you are really using. + </para> + + <para>Once configured, the studio setup is stored with every + Rosegarden-format file you save.</para> + + </sect1> + + <sect1 id="studio-device-editor"> + <title>Managing MIDI devices</title> + + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-devicemanager.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>The MIDI device manager</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + + <para> + The MIDI device manager dialog shows you the MIDI devices + that you currently have available to you, and where they are + connected. To reach this dialog, use <menuchoice> + <guimenu lang="en">Studio</guimenu> + <guimenuitem>Manage MIDI Devices</guimenuitem> + </menuchoice>. + </para> + + <para> + As described in the <link + linkend="studio-introduction">Devices, Instruments and + Connections</link> section, by default Rosegarden tries to + provide a plausible set of devices for you at startup, and + to make sensible connections for those devices. But the + default configuration might not always be suitable, and so + this dialog allows you to rename devices and modify their + connections and play/record direction. + </para> + + <para> + Each of the Play devices listed here provides a target for + MIDI tracks to talk to: if you add a new Play device, you + will then have 16 new instruments on this device which you + can assign tracks to. If you then assign a connection for + that device, the tracks assigned to it will play to the + appropriate channel (depending on the instrument) of any + MIDI synth attached to that connection. + </para> + + <para> The Record devices listed here represent possible + sources for recording MIDI. You can make one or more of them + current (so that Rosegarden will listen to them when + recording) using the checkboxes on each line, as shown in this + dialog. </para> + + </sect1> + + <sect1 id="studio-bank-editor"> + <title>Managing banks and programs for MIDI devices</title> + + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-bankeditor.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>The MIDI bank and program editor</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + + <para> + Remember that each MIDI device contains a number of + instruments, and that you can assign tracks to those + instruments. In MIDI terms, each instrument corresponds to + a single channel on your MIDI synth. You can choose which + of the available voices (sounds) on your synth each + instrument uses, but in order to do this, you need to let + Rosegarden know the names for all of the available voices. + </para> + + <para> + This dialog allows you to attach banks of programs (names for + voices) to your MIDI devices, thus permitting each + instrument on a device to be set to use one of those voices + in the <link + linkend="segment-view-instrumentparameterbox">Instrument + Parameter Box</link>. + </para> + + <para> + The usual way to set up the program names for a device is + simply to import them from one of the supplied device + (".rgd") files. To do this, select a device in the list on + the left of the dialog, then click the Import button below + the list and choose the .rgd file corresponding to your + synth. + </para> + + <para> + If there is no current .rgd file available for your synth, + then you can use this dialog to create a new bank. To do this + you will have to find the program map in your synth's MIDI + Implementation Chart and enter all the names by hand: you can + then Export them to a .rgd file to share with other Rosegarden + users. Contact the rosegarden-user mailing list if you have + made a new .rgd file and would like to share it. (This is how + all of the existing .rgd files have come to be included with + Rosegarden: other users have contributed them.) + </para> + + <sect2 id="studio-keymappings"> + <title>Percussion Key Mappings</title> + + <para> + Many MIDI synthesizers have at least one percussion program, + in which each "pitch" plays a different type of sound. + Rosegarden contains a dedicated percussion matrix editor to + view and edit notes against a scale consisting of the + correct names for the pitches, instead of against the + conventional piano keyboard pitch scale. + </para> + + <para> + The key mappings available for a particular MIDI device are + also defined in the Rosegarden device (".rgd") file. Each + MIDI program that is defined as a percussion program can + have a key mapping associated with it; if there is one, then + it will be used by default in any track that is assigned to + this program. Like program and bank definitions, key + mappings can be imported from and exported to .rgd files. + </para> + </sect2> + + <sect2 id="studio-soundfonts"> + <title>SoundFonts</title> + + <para> + If you happen to be using a soft-synth or soundcard synth + that uses SoundFont (.sf2) files, you can simply load the + correct program names directly from your .sf2 file into this + dialog. Just ask to Import as normal, and then choose the + .sf2 file that you are using instead of a .rgd file. + </para> + + <para>Note that the Studio only manages information about + existing MIDI devices for Rosegarden, it does not actually + handle tasks such as loading a SoundFont to your soundcard in + the first place. If you want to make sure a SoundFont is + loaded to your soundcard when Rosegarden starts up, you should + use the special "Load SoundFont to SoundBlaster card at + startup" option in the sequencer configuration in + <menuchoice> + <guimenu lang="en">Settings</guimenu> + <guimenuitem>Configure Rosegarden...</guimenuitem> + </menuchoice>. + </para> + </sect2> + + <sect2 id="studio-variations"> + <title>Variations</title> + + <para> + Some MIDI devices (for example, those from Roland) + organise their program names using a scheme known as + "variations". For these devices, you generally want to + select a program by first selecting the basic program name + — such as a piano — and then selecting one + of a set of variations on that program — such as an + electric piano. This is in contrast to General MIDI-based + synths, which organise their programs into banks and + expect you to choose a bank first and then a program from + that bank. + </para> + + <para> + Rosegarden can support devices that use variations, but + you still have to enter the program names in a bank + format. Internally, devices that use variations still use + MIDI bank select controllers to choose between the + variations; you need to find out from your synth's + documentation whether your device uses the LSB or MSB bank + select to choose variations, and which bank number + corresponds to which variation. You can then enter the + banks as normal, and use the "Show Variation list based on + MSB/LSB" option on the bank dialog to tell Rosegarden to + show variations instead of banks when displaying that + device in an instrument parameter box. + </para> + </sect2> + + <sect2 id="studio-midi-import"> + <title>Program mapping on &MIDI; import</title> + <para> + + When you import a &MIDI; file into a composition, &rosegarden; + uses the existing studio setup to determine how to map the + &MIDI; programs onto &rosegarden; instruments. The aim is to + ensure that every &MIDI; program gets mapped to an instrument + that really exists in your studio (and thus is actually + attached to your computer), so that all the &MIDI; tracks + can be heard. + + </para><para> + + The &MIDI; program-change and bank-select events found in the + imported file are used when importing, but only as an aid to + help find the appropriate instrument for each &MIDI; track + from the set of instruments in your studio. So, for + example, if your studio is currently set up to contain only + <acronym>GM</acronym> instruments, and you import a &MIDI; file with <acronym>GS</acronym> program + changes onto it, &rosegarden; will remap the <acronym>GS</acronym> banks back + onto <acronym>GM</acronym> because they're all it knows that you have at the + time you import the file. It doesn't remember the original + <acronym>GS</acronym> program numbers. + + </para><para> + + This means that you should always ensure that your studio is + correctly configured for the devices you actually have, + before you import the &MIDI; file. Otherwise the program data + in the &MIDI; file may be lost. + + </para> + </sect2> + </sect1> + + <sect1 id="studio-audio-routing"> + <title>Audio Routing</title> + <para> + Any Rosegarden track assigned to an audio or synth plugin + instrument becomes part of Rosegarden's audio routing + architecture. There are 16 audio instruments and 16 synth + plugin instruments, and each of these has a set of adjustable + parameters including fader level, pan, effects and so on. + These are generally configurable in the <link + linkend="segment-view-instrumentparameterbox">Instrument + Parameter Box</link> or <link + linkend="studio-audio-mixer">audio mixer</link>. Each audio + instrument also has an input connection, and both audio and + synth plugin instruments have an output connection. + </para> + + <para>An instrument's input connection defines where Rosegarden + will read audio data from when recording to this instrument. + The most usual setting would be to one of Rosegarden's external + audio inputs, the number of which is configurable in the <link + linkend="studio-audio-mixer">audio mixer</link>. These + correspond to JACK audio ports exposed by Rosegarden, to which + you can connect outputs from any other JACK audio application or + soundcard capture ports using an external JACK router + application such as <ulink + url="http://qjackctl.sf.net/">QJackCtl</ulink>. You can also + set an instrument's audio input to the output of one of + Rosegarden's built-in audio submasters or master output for + mixdowns. + </para> + <para>An instrument's output connection defines where the audio + goes when played. Instruments default to sending their audio to + Rosegarden's master output, which is another (stereo pair of) + external JACK port(s) that can then be connected up using the + same external JACK router. However, Rosegarden also supports up + to eight internal submaster busses, to which you can send + instrument outputs instead so as to group instruments into + related categories. You can control the number and routing of + these in the <link linkend="studio-audio-mixer">audio + mixer</link>. + </para> + <para> + Rosegarden currently supports effects using a set of pre-fader + insert effects slots for each audio instrument. You cannot + yet assign effects to the submaster busses, and Rosegarden + does not yet support send effects, although you can obtain + similar results using an external JACK effects and mixing + architecture. + </para> + <para>Some further details of audio routing configuration, + mixing, and effects are discussed in the <link + linkend="studio-audio-mixer">audio mixer</link>, <link + linkend="segment-view-instrumentparameterbox">instrument + parameter box</link> and <link + linkend="studio-plugins">audio plugins</link> sections.</para> + </sect1> + + <sect1 id="studio-midi-routing"> + <title>MIDI Routing</title> + <para>&rosegarden; is able to instantly send incoming MIDI events to + some output device and MIDI channel. This feature is known as MIDI Thru.</para> + <para>MIDI Thru is enabled by default in &rosegarden;. You may want + to globally disable it using the menu option <menuchoice> + <guimenu lang="en">Studio</guimenu> + <guimenuitem>MIDI Thru Routing</guimenuitem></menuchoice>, if you prefer + to use an external MIDI routing system. There is also a global filter by + MIDI event type, which you may use to ignore some event types and let other + types to be routed. It is explained in the section <link linkend="studio-midi-filters"> + MIDI filters</link>.</para> + <para>MIDI Thru routing works quite differently when &rosegarden; is playing + or stopped than when it is recording.</para> + <itemizedlist> + <listitem><para>When &rosegarden; is playing or in stopped state, the MIDI + thru function routes events to the selected track instrument. The selected + track has its track name highlighted.</para></listitem> + <listitem><para>When &rosegarden; is recording, the MIDI events are routed + to the armed track instruments, based on the <link linkend="track-recording-filters"> + recording filters</link>. It doesn't + matter which track is selected. Only one instrument is selected for each event, + corresponding to the first track with a matching record filter.</para> + </listitem> + </itemizedlist> + </sect1> + + <sect1 id="studio-audio-mixer"> + <title>The Audio Mixer</title> + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-audiomixer.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>&rosegarden;'s Audio Mixer</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + + <para> + Rosegarden's audio mixer window, reached through + <menuchoice> + <guimenu lang="en">Studio</guimenu> <guimenuitem>Audio + Mixer</guimenuitem></menuchoice>, resembles a hardware audio + mixer and provides a way to see and change the state of a + number of audio instruments at once. It contains many of + the same controls as found in the audio and synth plugin + <link + linkend="segment-view-instrumentparameterbox">instrument + parameter boxes</link>, most importantly a playback level + meter and fader control for each audio and synth plugin + instrument, as well as routing controls, pan, mono/stereo + and effects plugin slots. + </para> + <para> + The audio mixer window is also where you see and control the + master audio output level (at the far right of the picture + above), as well as the record level (to the left of the master + fader) and submaster output levels. + </para> + <para> + The audio mixer's <menuchoice> <guimenu + lang="en">Settings</guimenu></menuchoice> menu is particularly + relevant. Apart from controlling what will be shown in the + mixer window, this menu also contains the <link + linkend="studio-audio-routing">audio routing</link> settings + for the number of stereo audio record inputs available and the + number of submasters. These are studio settings whose values + are saved with your Rosegarden format file.</para> + + <para>Note that if you are not actually using any submasters + (i.e. if there are no instruments configured to route their + output to a submaster) you may see a small performance + improvement if you set the number of submasters explicitly to + None, rather than keeping unused ones in the configuration. + </para> + </sect1> + + <sect1 id="studio-midi-mixer"> + <title>The MIDI Mixer</title> + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-midimixer.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>&rosegarden;'s MIDI Mixer</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + <para> + Rosegarden's MIDI mixer window, reached through + <menuchoice> + <guimenu lang="en">Studio</guimenu> <guimenuitem>MIDI + Mixer</guimenuitem></menuchoice>, provides a way to see and + edit the <link + linkend="segment-view-instrumentparameterbox-midi">instrument + parameter values</link> for a number of MIDI instruments at once.</para> + + <para>The window is organised using a tabbed pane. Along the + bottom, you will see one tab for each playback MIDI device in + your studio configuration. When you select a device tab, the + rest of the window will update to show the controls for the 16 + instruments of that device. + </para> + + <para> + The controls shown for each instrument are those set up in the + <!-- !!! link linkend="studio-device-controllers" --> control + parameter manager, as well as volume (corresponding to the + MIDI volume control change, not to MIDI velocity or audio dB + levels) and an approximate output level indicator. + </para> + </sect1> + + <sect1 id="studio-plugins"> + <title>Audio Plugins</title> + <para>An audio plugin is a piece of software, separate from + Rosegarden, that Rosegarden can load and use in order to perform + a particular audio processing task. These can be broadly + divided into effects plugins and synth plugins. Effects plugins + take an audio input and manipulate it to produce a different + audio output; synth plugins take MIDI-like events as input and + turn them into audio output. Rosegarden uses the Linux standard + LADSPA plugin API for effects and the DSSI plugin API for + synths, permitting the use of large numbers of open-source + plugins made available by many developers. + </para> + <para>The use of plugins has a cost in CPU time, as audio + processing in real time usually takes a significant amount of + work even on a modern CPU. It also has a potential cost in + reliability: when Rosegarden is running a plugin, if the plugin + hangs or crashes, so does Rosegarden. Many plugins are very + reliable, but it's inevitable that some will not be so well + tested. + </para> + <sect2 id="studio-plugins-effects"> + <title>Effects plugins</title> <para>An effects plugin is + something that you can use to modify an audio signal in a + controllable way. Examples include reverb, delay effects, + dynamic compression and so on. + </para> + <para>Every audio or synth-plugin instrument in Rosegarden has + five associated effects slots. By default these are empty, + but you can load plugins into them in order to chain up to + five effects onto the audio signal before it goes through + fader level and pan processing.</para> + + <para>To load a plugin to a slot, click its button on the + <link linkend="segment-view-instrumentparameterbox-audio">instrument + parameter box</link>: + </para> + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-pluginbuttons.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>Plugin Slot Buttons</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + <para>(These buttons are also optionally available in the <link + linkend="studio-audio-mixer">audio mixer</link> window.) + </para> + <para>Clicking a plugin button will + pop up the plugin dialog. This shows you + the available categories of effects in the first menu; select + one, and you can then choose your plugin in the second menu. + </para> + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-plugin-dialog.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>A &rosegarden; Plugin Dialog</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + + <para>Below the plugin selection menus, the dialog gives you a + varying number of rotary controllers showing all the + modifiable parameters for the plugin you have selected. To + change a value, just click a rotary and drag up and down or + left and right. (Up or right to raise the value, down or left + to lower it.) You can also roll the mouse wheel to change the + value, or click with the middle mouse button to reset it to + its initial default.</para> + + <para>It is also possible to copy one plugin with its current + configuration into another slot, so as to use the same plugin + settings with more than one instrument, or to base one plugin + configuration on another. Just click the Copy button when you + have the plugin set up the way you want it, and then open + another plugin slot's plugin dialog and click Paste.</para> + + <para>Finally, you can use the Bypass toggle to remove a + plugin temporarily from processing while retaining its + configuration. + </para> + </sect2> + <sect2 id="studio-plugins-synths"> + <title>Synth plugins</title> + <para> + Synth plugins can be used in place of hardware or standalone + soft-synth MIDI devices, to generate sounds from your note + event segments.</para> + + <para>Using a synth plugin gives you somewhat better control + and repeatability than using an external MIDI device, because + Rosegarden will be able to load the correct plugins for you + and use the correct settings the next time you load your same + file. Plugins may also offer better timing resolution than + external MIDI devices, and synth plugin instruments have the + advantage of being routable like audio instruments, which also + means you can add effects plugins on top of them. + </para> + + <para>To make use of a synth plugin, first <link + linkend="segment-view-instruments">assign a track</link> to a + synth plugin instrument, and then load a synth plugin by + clicking on the topmost button in the <link + linkend="segment-view-instrumentparameterbox-synth">instrument + parameter box</link>:</para> + + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-synthpluginbuttons.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>Synth Plugin Buttons</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + + <para>This will bring up the same plugin dialog as shown above + for effects plugins, but with a list of synth plugins instead + of effects. Once again, you will be shown the particular set + of rotary parameters for the synth you have selected. Synth + plugins may also have "programs", selectable from a menu -- + this menu will only appear if you have chosen a synth that supports + them. When you have selected and configured a synth plugin + for an instrument, any MIDI data on tracks assigned to that + instrument should play through that synth, as should + incoming MIDI data during recording or monitoring. + </para> + </sect2> + + <sect2 id="studio-plugins-guis"> + <title>Plugin native editor windows</title> + + <para>Most plugins can be controlled completely using the + rotary controllers in Rosegarden's plugin dialog. However, a + few plugins (generally synths) also have their own editor + windows which can be switched on or off from Rosegarden and + which may provide more complete or more organised + controls.</para> + + <para>When you select a plugin that has its own editor window, + the button at the lower left of the plugin dialog labelled + "Editor" will become active:</para> + + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-plugineditorbutton.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>A Plugin Editor Button</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + + <para>(For synth plugins, there is a similar button in the + instrument parameter box.) Clicking this button should show + the plugin's own editor window. Any changes you make in this + editor window should also be reflected in Rosegarden's own + plugin dialog, if visible, and of course should be saved in + your Rosegarden file as normal.</para> + </sect2> + </sect1> + + <sect1 id="studio-metronome"> + <title>Metronomes</title> + <para> + Rosegarden has two built-in metronomes, one for use during + recording and one that can be switched on during normal + playback. They work by sending notes to a MIDI instrument, + and both metronomes use the same instrument, pitch and + velocity information. + </para> + + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-metronome.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>&rosegarden;'s metronome configuration dialog</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + <para> + To configure the metronomes, use + <menuchoice> + <guimenu lang="en">Studio</guimenu> + <guimenuitem>Manage Metronome</guimenuitem> + </menuchoice> + to bring up the metronome dialog. + Here you can select a MIDI instrument for the metronome and + choose the metronome's resolution (whether it should tick + once per beat, once per subdivision of a beat, or only once + per bar), pitch, and velocities. Properties such as the + actual voice the MIDI synth uses for the metronome tick + depend on the instrument selected, just as the voice used + for a MIDI track depends on the instrument that track is + assigned to. You can configure the instrument by assigning + a track to it on the main window and selecting the correct + program from the instrument parameter box. + </para> + + <para> + The record and play metronomes can be switched on or off + from the Transport window, using the metronome button. This + button controls the record metronome when recording is armed + or in progress, and the play metronome at other times. By + default, the record metronome is switched on and the play + metronome switched off. + </para> + + <para> + Rosegarden also has a "visual metronome": the transport window + can be told to flash brightly to mark each beat. See <link + linkend="transport">the Transport section</link> for more + details.</para> + </sect1> + + <sect1 id="studio-midi-filters"> + <title>MIDI filters</title> + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-midifilter.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>The MIDI filter dialog</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + + <para> + Using this dialog you can decide which MIDI events Rosegarden + will ignore or accept, either when forwarding events using + MIDI THRU or when simply recording them. Use the check boxes + on this dialog to tell Rosegarden which types of MIDI events + you don't want to forward or record. + </para> + + </sect1> + + + <sect1 id="studio-external-controllers"> + <title>External MIDI control surfaces</title> + <para> + Rosegarden's audio and MIDI mixer windows and main canvas can + also be controlled to some degree by an external MIDI device. + To set this up, you will need to use an ALSA MIDI connection + manager such as qjackctl to connect your MIDI controller + device to Rosegarden's "external controller" input and output + MIDI ports. + </para> + <para> + Rosegarden accepts MIDI control change messages to adjust the + mixer track corresponding to the incoming MIDI channel on each + controller event, and also sends out MIDI messages when + something is changed in a mixer track in order to support + controllers with powered faders or knobs. + </para> + <para>Rosegarden accepts MIDI controller number 81 to change the + currently active window. Send controller 81 with data value 0-9 + to select the main window, 10-19 to select the audio mixer + window or 20-29 to select the MIDI mixer window.</para> + <para>Rosegarden accepts MIDI controller number 82 to change the + currently selected track in the main window. The stepping of + this controller depends on the number of tracks in the window -- + the ratio of controller data value to track number will be + calculated so as to use the full MIDI controller data range, + provided there are no more than 128 tracks in the window.</para> + </sect1> + + </chapter> + + <chapter id="segment-instrument-parameters"> + <title>Special Parameters</title> + + <sect1 id="track-parameters"> + <title>The Track Parameter Box</title> + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-trackparameterbox.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>&rosegarden;'s track parameter box</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + <para> + The track parameter box can be found at the left side of the + &rosegarden; main window. It displays the parameters for the + currently selected track. (If you can't see it, try using <menuchoice> + <guimenu lang="en">Settings</guimenu> + <guimenuitem>Show Special Parameters</guimenuitem> + </menuchoice>.) + </para> + <para> + It allows you to assign instruments to tracks, control what + incoming &MIDI; data from which sources will be recorded to + particular tracks, control staff attributes (currently only for LilyPond + export,) make selections that govern how &MIDI; segments + will be created for each track that is assigned to a non-audio + instrument, and apply these selections to existing segments (as when + converting a trumpet part from an imported &MIDI; file to be + represented as notation playable by a real human on a real instrument, + for example.) + </para> + <para>This box is divided into three sections:</para> + <sect2 id="track-playback-parameters"> + <title>Playback parameters</title> + <para> + These provide an alternative mechanism to the <link + linkend="segment-view-instruments">menu-based + system</link> of instrument assignment. + </para> + </sect2> + <sect2 id="track-recording-filters"> + <title>Track recording filters</title> + <para> + These provide you a way to control what events are recorded to this track. If you leave the default values ("all") for both parameters, every received event will be stored in the track. This setting is safe and convenient if you are recording only one MIDI track. Otherwise, you should adjust one or both parameters to select only the desired events for the track. + </para> + <variablelist> + <varlistentry> + <term>Device</term> + <listitem> + <para>You can record from only one of the available devices marked for recording in the <link linkend="studio-device-editor">device manager</link>, or from all of them simultaneously.</para> + </listitem> + </varlistentry> + <varlistentry> + <term>Channel</term> + <listitem> + <para>You can record from all channels, or limit recording to only one of the 16 available MIDI channels. In this case, only MIDI channel messages matching the channel number will be recorded, and system messages not having a channel (as system exclusive events) will be discarded.</para> + </listitem> + </varlistentry> + </variablelist> + <para> + Both parameters are cummulative: you can filter only a device, only a channel, or both a device and a channel simultaneously. It is not mandatory to ensure mutually exclusive selections for all the armed tracks, but if you don't do so you will find duplicated events at several recorded tracks. + </para> + <para> + The recording filters are also used to <link linkend="studio-midi-routing">route MIDI events </link> to the assigned track instrument when you are recording. + </para> + </sect2> + <sect2 id="track-staff-params"> + <title>Staff export options</title> + <para> + These provide you with a means of exporting notation to render + at either normal, small, or tiny size (eg. for printing certain + parts at cue size,) and allow you to export a variety of nested + brackets. + </para> + <para> + You are responsible for creating a series of bracket start and + end markers that will yield a functional result, and if you make + a mistake with these, it is likely that your file will not + export or preview correctly in LilyPond. + </para> + <para>For a detailed, hands-on demonstration of brackets in action, + please see + <ulink url="http://rosegarden.sourceforge.net/tutorial/supplemental/fidelio/fidelio.html">this + online tutorial.</ulink> + </para> + </sect2> + <sect2 id="track-create-with"> + <title>Create segments with</title> + <para> + These provide you with a means of controlling many of + the <link + linkend="segment-view-segmentparameterbox">segment + parameters</link> for segments that don't yet + exist. They are aimed especially at notation users, + and they facilitate operations that require you to use + more than one segment on a track (as when using + <!-- link -->repeats, or <link + linkend="nv-lilypond-directives">alternative + endings</link>), by allowing you to create a series of new + segments that all have the same properties by default. + </para> + <para> + <variablelist> + + <varlistentry> + <term>Preset</term> + <listitem> + <para> + The <guimenuitem>Load</guimenuitem> button + launches a dialog that allows you to pick + a pre-defined collection of parameters + that provide guidelines for how you should + write parts for real-world instruments, and + optionally convert any existing segments on this + track to take on these new parameters. + <!-- needs a tutorial somewhere, and a link to + that tutorial DMM --> + </para> + <para> + <inlinemediaobject> + <imageobject> + <imagedata fileref="rg-loadpreset.png" format="PNG"/> + </imageobject> + </inlinemediaobject> + </para> + <para> + You first pick a Category, then an Instrument, + and finally choose whether you wish to write a + part for an amateur or a professional player. + <footnote><para>This database was compiled by + Magnus Johansson, who deserves all the special + mention we can muster for his outstanding effort + on this.</para></footnote> The Scope controls + allow you to choose whether these parameters + will only affect segments that don't yet exist + (which you will subsequently record, or draw + with the pencil) or should convert any existing + segments to take these parameters as well. (For + a demonstration of the latter case in action, + please see + <ulink url="http://rosegarden.sourceforge.net/tutorial/supplemental/fidelio/fidelio.html"> + this online tutorial.)</ulink> + Clicking the <guimenuitem>OK</guimenuitem> + button injects the appropriate parameters into + the remaining widgets in this part of the track + parameters box, where you can tweak them if you + desire.<footnote><para>No facility is provided + at this time for assembling your own database of + presets, or customizing the existing ones in a + permanent way.</para></footnote> </para> + <para> + Once you have loaded a preset, the name of + your chosen preset will be used as the label + for any segments you subsequently draw or + record on this track, even if you change some + or all of the associated parameters away from + the values you just loaded. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>Clef</term> + <listitem> + <para>This lets you choose the clef for any + segments you subsequently draw or record on + this track. Clefs are events, not properties. + Your segments will be created with an initial + clef event of the appropriate type (which you + may subsequently alter or delete, should you + have some occasion to do so.) + </para> + <para> + The clefs available include a variety of named + clefs representing standard clefs with various + octave offsets. + </para> + <!-- !!! I would enumerate this list, but I have + no idea how to do it in docbook. I'm just winging + it by the seat of my pants here. Why do you think + I avoided touching this hateful mess until now? I + wrote Rosegarden Companion using OO.o, and didn't + touch tag one. Wah. --> + </listitem> + </varlistentry> + + <varlistentry> + <term>Transpose</term> + <listitem> + <para> + This causes segments on this track to be + created so that their note events sound at a + given transposition. Useful, especially, for + writing parts for transposing instruments. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>Colour</term> + <listitem> + <para> + This causes segments on this track to be + created using a given colour. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>Range</term> + <listitem> + <para> + The <guimenuitem>Low:</guimenuitem> and + <guimenuitem>High:</guimenuitem> buttons, + launch a dialog that allows you to pick a + pitch using a staff. The lowest and highest pitches + you select will then appear right on these + buttons. + </para> + <para> + These represent the lowest and highest + playable notes, respectively, on the instrument for which you + are writing notation. In some cases, these + limits will be hard and fast, like the low B + on a Transverse Flute (B foot). In others, + they may only serve as guidelines to help you + make good choices for instruments with which + you are not intimately familiar. + </para> + <para> + If you enter, record, or import data that has + pitches exceeding the values specified, the + note heads will appear in red by default. You + can turn this behavior off with + <menuchoice><guimenu>Settings</guimenu><guimenuitem>Configure + Rosegarden</guimenuitem><guimenuitem>Notation</guimenuitem><guimenuitem>Show + notes outside playable range in + red</guimenuitem></menuchoice> + </para> + </listitem> + </varlistentry> + + </variablelist> + </para> + </sect2> + + </sect1> + + <sect1 id="segment-view-segmentparameterbox"> + <title>The Segment Parameter Box</title> + + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-segmentparameterbox.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>&rosegarden;'s segment parameter box</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + + <para> + The segment parameter box can be found at the left side of the Rosegarden main window. (If you can't see it, try using <menuchoice> + <guimenu lang="en">Settings</guimenu> + <guimenuitem>Show Special Parameters</guimenuitem> + </menuchoice>.) + It allows you to modify some aspects of the + selected segments.</para><para>If a single segment is currently selected, its + parameters will be shown in the segment parameter box and can be + edited there. If several segments are selected, the parameter box + will only show the current values where they are the same for all + of the selected segments -- but you can still edit them, and your + changes will apply to the whole selection. + + <variablelist> + <varlistentry> + <term>Label</term> + <listitem> + <para>Shows the label of the selected segment (or segments, if + they all have the same label). Click the "Edit" button to edit + the label.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term>Repeat</term> + <listitem> + <para>Switches repeat on or off for the selected segments. A + repeating segment will repeat until the start of the following + segment on the same track, or until the end of the composition + if there is no following segment.</para> + + <para>The repeated parts of a repeating segment are shown on + the main canvas in a fainter colour than the original segment. + You can turn them into real editable copies of the original + segment either by using + <menuchoice> + <guimenu lang="en">Segments</guimenu> + <guimenuitem>Turn Repeats into Copies</guimenuitem> + </menuchoice>, or simply by double-clicking on the + individual repeating blocks.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term>Quantize</term> + <listitem> + <para> + Shows the quantization setting for the selected + segments. You can change this to quickly quantize + the start times of all their notes. For more + advanced quantization, use <menuchoice> + <guimenu lang="en">Segments</guimenu> + <guimenuitem>Quantize...</guimenuitem> + </menuchoice>. See <link + linkend="quantization">Quantization</link> for more + details. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>Transpose</term> + <listitem> + <para>Shows the transposition (in semitones) currently applied + to the selected segments. This transposition is applied when + the segment is played, and is not shown in the notes displayed + in the matrix, notation or event list editors. You can use + this to quickly change the pitch of part or all of a + composition, and it is commonly used with segments containing + notation written for transposing instruments, such as the + clarinet.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term>Delay</term> + <listitem> + <para>Shows the delay currently in effect on the selected + segments. You can set a delay here in order to cause an entire + segment to play later than written. This delay is applied when + the segment is played, and is not shown in the notes displayed + in the matrix, notation or event list editors. + </para> + <para> + You can set a delay either in musical time (by + choosing a note duration from the delay dropdown), + in which time the exact delay will depend on the + tempo, or in real time (by choosing a time in + milliseconds from the dropdown). + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>Colour</term> + <listitem> + <para>Shows the colour being used for the display of the + selected segments. You can choose another colour from the + dropdown, or choose the "Add New Colour" option if you want a + colour not in the dropdown. + </para> + <para> + You can also manage and rename colours using +<menuchoice> + <guimenu lang="en">Composition</guimenu> + <guimenuitem>Edit Document Properties...</guimenuitem> + </menuchoice> + (then choose the Colour page on the document properties + dialog). The modified colour palette will be saved + with the composition in the Rosegarden file. + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-colours.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>&rosegarden;'s colour manager</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + </listitem> + </varlistentry> + + </variablelist> + </para> + </sect1> + + <sect1 id="segment-view-instrumentparameterbox"> + <title>The Instrument Parameter Box</title> + <para> + The instrument parameter box can be found at the left side of + the Rosegarden main window, near the <link + linkend="segment-view-segmentparameterbox">Segment Parameter + Box</link>. (If you can't see it, try using + <menuchoice> <guimenu lang="en">Settings</guimenu> + <guimenuitem>Show Special + Parameters</guimenuitem> </menuchoice>.)</para> + + <para>It shows you + which instrument is assigned to the current selected track, + and contains all of the editable controls for that instrument. + Remember that because any number of tracks can be assigned to + the same instrument, the settings in this box may affect more + than one track at a time.</para> + + <para>The layout and contents of the instrument + parameter box depend on the type of instrument: MIDI, audio, + or synth plugin. + </para> + + <sect2 id="segment-view-instrumentparameterbox-midi"> + <title>MIDI Instrument Parameters</title> + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-ipb-midi.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>&rosegarden;'s instrument parameter box for a MIDI instrument</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + <para>When you select a track assigned to a MIDI instrument, + the instrument parameter box shows MIDI parameters. + </para> + <para>At the top, this box + shows the name of the instrument and the connection that its + device is using. + </para> + <para>Below that, you can see and edit the MIDI + channel number and the <link linkend="studio-bank-editor">bank + and program</link> settings that should be sent to the + instrument at the start of playback (including a "percussion" + toggle that controls whether only percussion programs should + be offered in these settings).</para> + + <para>Finally this box shows you the <!-- !!! link + linkend="studio-device-controllers" --> controllers available + for this device (those for a General MIDI device are shown + above). Any settings you make here will be sent to this + instrument's channel at the start of playback.</para> + </sect2> + + <sect2 id="segment-view-instrumentparameterbox-audio"> + <title>Audio Instrument Parameters</title> + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-ipb-audio.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>&rosegarden;'s instrument parameter box for an audio instrument</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + <para> + When you select an audio track, the instrument parameter + box shows audio parameters. + </para> + <para> + The box has two main faders, one with a blue surround for + playback level and the other with a red surround for the + record level when recording to this instrument. Between + them is a playback level meter. + </para> + <para>The two menus at the top of the box are used to select + the input and output <link linkend="studio-audio-routing">audio routing</link> for this + instrument. Below them you can select whether the instrument + is mono or stereo, and the pan setting for position in the + stereo field. (Audio instruments are always ultimately + stereo, because the pan setting is always applied. But if you + set the instrument to mono, it will reduce any audio data and + effect outputs to mono before applying pan.) + </para> + <para>The column of five buttons at lower left are the effects + slots. Click on them to select and activate plugin effects + for this audio instrument, and to control them using the <link linkend="studio-plugins">plugin editor dialog</link>. These are insert effects, + applied in order from top to bottom before the fader and pan. + </para> + </sect2> + + <sect2 id="segment-view-instrumentparameterbox-synth"> + <title>Synth Plugin Instrument Parameters</title> + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-ipb-synth.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>&rosegarden;'s instrument parameter box for a synth plugin instrument</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + <para>When you select a track assigned to a synth plugin + instrument, the instrument parameter box shows synth + parameters. You will notice that although a synth plugin + track uses segments with MIDI data in them, in terms of + control and routing it behaves more like an audio track. + </para> + <para>The most important control here is the button at top + left (saying Xsynth in the above picture) which shows the name + of the synth plugin in use for this instrument. Click this to + select a particular synth and control it in the standard + Rosegarden <link linkend="studio-plugins">plugin editor dialog</link>. Once + you've selected a plugin, you may also be able to click the + Editor button below it in order to open a dedicated GUI editor + for the particular plugin (if the plugin has one). + </para> + <para>The remaining controls here are the same as for audio + instruments: the playback fader, playback level, output + routing, mono/stereo and pan settings and effects slots are + all exactly the same.</para> + </sect2> + + </sect1> + </chapter> + + <chapter id="quantization"> + <title>Quantization</title> + <para> + "Quantization" is the process of repositioning notes and other + events so that they start or finish on exact beat divisions. It + is traditionally used to make an approximate performance into a + precise but rather mechanical-sounding one -- either because + precision is the desired effect, or for reasons such as making + the notes clearer in notation. + </para> + + <para> + For general quantization, use + <menuchoice> + <guimenu lang="en">Segments</guimenu> + <guimenuitem>Quantize</guimenuitem> + </menuchoice> + in the main window or + <menuchoice> + <guimenu lang="en">Adjust</guimenu> + <guimenuitem>Quantize</guimenuitem> + </menuchoice> + in matrix or notation editors. This shows you a dialog in which + you can select the precise quantization parameters you need, and + then it applies these to all of the selected segments or notes. + (You can also quickly reach this dialog by pressing the "=" + key.) + </para> + + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-gridquantizer.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>&rosegarden;'s quantize dialog</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + + <para> + The quantize dialog offers a selection of quantizers, each with + its own set of parameters. The quantizers available are: + </para> + <variablelist> + + <varlistentry> + <term>Grid quantizer</term> + <listitem> + <para>The grid quantizer moves the start times of notes so + that they start at the nearest point on some grid (defined + by various parameters of the quantizer). Thus notes that + initially vary slightly in start time will be aligned by the + quantizer, making for a more precise and mechanical + performance. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>Legato quantizer</term> + <listitem> + <para>The legato quantizer carries out a simple grid + quantization, and also adjusts the note durations so as to + remove any gaps between notes by extending each note so as + to (at least) continue until the start of the following one. + You can also obtain this legato effect without the + accompanying grid quantization using the + <menuchoice> + <guimenu lang="en">Adjust</guimenu> + <guimenuitem>Quantize</guimenuitem> + <guimenuitem>Legato</guimenuitem> + </menuchoice> function in the Matrix editor. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>Heuristic notation quantizer</term> + <listitem> + <para>The notation quantizer attempts to adjust note start + times and durations so as to produce readable notation. See + <link linkend="nv-quantization">Notation from performance + data</link> for a description of this quantizer and its + uses.</para> + </listitem> + </varlistentry> + + </variablelist> + + <para>The grid quantizer has the following adjustable parameters:</para> + <variablelist> + + <varlistentry> + <term>Base grid unit</term> + <listitem> + <para>This is the size of the grid used for quantization. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>Swing</term> + <listitem> + <para>This is a percentage figure which adjusts the degree + by which alternate beats are quantized "late".</para> + <para>If set to + None (the default), quantization will be to an even grid + spaced according to the base grid unit.</para> + <para>If set to 100%, + every second grid line will be placed two-thirds of the distance + between the previous and next ones, instead of only half. + This will result in notes being quantized to the first and + third triplets of a swing beat. + </para> + <para>Other settings will produce proportionately varying degrees of + swinginess. You can also set this parameter to negative + figures (for alternate beats to start early) or to figures + greater than 100%.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term>Iterative amount</term> + <listitem> + <para>The default behaviour of the grid quantizer is to move + each note exactly onto its nearest grid line. But if you + set the iterative amount to something less than 100% (the + "Full quantize" default), each note will only be moved that + percentage of the distance toward its nearest grid line, + resulting in a nearly-but-not-quite quantized effect.</para> + <para>This quantizer may be applied repeatedly so as to try + out gradually increasing degrees of quantization, hence the + name "iterative". Use + <menuchoice> + <guimenu lang="en">Adjust</guimenu> + <guimenuitem>Quantize</guimenuitem> + <guimenuitem>Repeat Last Quantize</guimenuitem> + </menuchoice> in the Matrix editor to do so. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>Quantize durations as well as start times</term> + <listitem> + <para>If this option is enabled, the quantizer will quantize + the notes' end times to the same grid as their start times. + </para> + </listitem> + </varlistentry> + </variablelist> + + <para>The quantize dialog also has an optional Advanced section + containing further options for + <link linkend="nv-quantization">notation quantization</link>. + </para> + + <para> + Another simple way to apply a grid quantizer is to do it in the + main window, using the <guimenuitem>Quantize</guimenuitem> menu + on the <link linkend="segment-view-segmentparameterbox">Segment + Parameter Box</link>. If you select some segments and change + the value shown in the menu, the segments will immediately be + grid-quantized to the resolution shown in the menu. + </para> + + <para> + Finally, there is also a <link + linkend="matrix-grid-quantize">quantize control</link> in the matrix + view.</para> + + </chapter> + + <chapter id="matrix-view"> + <title>The Matrix editor</title> + <para> + The &rosegarden; matrix editor enables you to view and edit + music in a simple, logical format: each note represented as a + block in a grid, at a height corresponding to the pitch. + </para> + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-matrixview.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>&rosegarden;'s matrix editor</phrase> + </textobject> + </mediaobject> + </screenshot> + Each matrix editor window shows a single segment. To edit a + segment, just right-click on it in the main canvas and select + the matrix editor from the menu. Alternatively, you can + configure Rosegarden to make the matrix editor the default + editor available when you double-click on a segment. + </para> + + <sect1 id="matrix-grid-quantize"> + <title>The Grid and Quantize controls</title> + <para> + The matrix view contains Grid and Quantize menus in its main + toolbar. + </para> + <para>The Grid menu controls the size of the visible grid in the + background of the matrix view, as well as the time resolution + used when entering and moving notes. After you set it to a + particular time value, the normal note insertion and drag + operations will then snap automatically to grid points spaced at + that time width. You can override the snap-to-grid effect + temporarily by holding down Shift during editing, or you can + disable it by setting the Grid menu to None. + </para> + <para>The Quantize menu works rather differently. Rather than + controlling the behaviour of other editing tools, it actually + performs an action. When you change the value in this menu, the + selected notes -- or the whole segment if nothing is selected + -- will immediately be quantized using a grid quantizer of the + chosen resolution. + </para> + <para>The Quantize menu also shows you continuously what + resolution the current segment or selection is quantized to. + For example, if you select a set of notes that start on + consecutive quarter-note beats, the Quantize menu will update + itself to show 1/4, as this is the coarsest resolution + consistent with the existing quantization of the current + selection. + </para> + </sect1> + + <sect1 id="matrix-insertion"> + <title>Inserting notes</title> + <para> + The simplest way to enter a note in the matrix view is to + use the mouse. To do this, select the pencil tool on the + toolbar, and then click and drag on the matrix editor. The + note will be entered at the time and pitch corresponding to + the point you click at, and will have a duration + corresponding to the distance you drag before releasing the + mouse button.</para> + + <para>You can also draw notes using the Select tool (the + arrow), by clicking and dragging either with the middle mouse + button, or with the left mouse button and Ctrl pressed.</para> + + <para>By default, the time and duration are snapped to a + particular grid unit, according to the Grid setting on the + View menu or the toolbar. You can prevent this effect by + holding down Shift while clicking and dragging. + </para> + + <sect2 id="matrix-insertion-keyboard"> + <title>Typing notes with the PC keyboard</title> + + <sect3> + <title>Duration</title> + + <para>The durations of notes entered from the keyboard are + controlled by the Grid setting on the View menu or + toolbar. You can set this using the number keys:</para> + + <itemizedlist> + <listitem><para><keycap>5</keycap> – Whole bar</para></listitem> + <listitem><para><keycap>1</keycap> – Beat</para></listitem> + <listitem><para><keycap>2</keycap> – Half note (minim)</para></listitem> + <listitem><para><keycap>4</keycap> – Quarter note (crotchet)</para></listitem> + <listitem><para><keycap>8</keycap> – Eighth note (quaver)</para></listitem> + <listitem><para><keycap>6</keycap> – Sixteenth note (semiquaver)</para></listitem> + <listitem><para><keycap>3</keycap> – Thirty-second note (demisemiquaver)</para></listitem> + <listitem><para><keycap>0</keycap> – Sixty-fourth note (hemidemisemiquaver)</para></listitem> + </itemizedlist> + + </sect3> + + <sect3> + <title>Pitch</title> + + <para>Once the correct duration is selected in the Grid + menu, you can insert a note at the current position of the + <link linkend="nv-rulers">insert cursor</link> by pressing + one of the pitch keys:</para> + + <itemizedlist> + <listitem><para><keycap>A</keycap> – Do (the tonic of the current key in the current clef)<!-- !!! FIXME: no clef in matrix view --></para></listitem> + <listitem><para><keycap>S</keycap> – Re</para></listitem> + <listitem><para><keycap>D</keycap> – Mi</para></listitem> + <listitem><para><keycap>F</keycap> – Fa</para></listitem> + <listitem><para><keycap>J</keycap> – So</para></listitem> + <listitem><para><keycap>K</keycap> – La</para></listitem> + <listitem><para><keycap>L</keycap> – Ti</para></listitem> + </itemizedlist> + + <para>Holding <keycap>Shift</keycap> while pressing a key + will sharpen the note (except for Mi and Ti, which don't + have sharpened versions) and holding <keycap>Shift</keycap> + and <keycap>Ctrl</keycap> together will flatten it (except + for Fa and Do).</para> + + <para>To enter notes an octave higher, use the corresponding + keys on the next row up: <keycap>Q</keycap>, + <keycap>W</keycap>, <keycap>E</keycap>, <keycap>R</keycap>, + <keycap>U</keycap>, <keycap>I</keycap>, and + <keycap>O</keycap>. Likewise to enter notes an octave + lower, use <keycap>Z</keycap>, <keycap>X</keycap>, + <keycap>C</keycap>, <keycap>V</keycap>, <keycap>B</keycap>, + <keycap>N</keycap> and <keycap>M</keycap>.</para> + + </sect3> + + <sect3> + <title>Other remarks</title> + + <para>All of the insertion commands are also available on a + submenu of the Tools menu. It's unlikely you'd ever want to + navigate the menus just to insert a single note, but the + menus show the keyboard shortcuts and so provide a useful + reference in case you forget which key is which.</para> + + <para>The keyboard shortcuts are currently designed for use + with a QWERTY-layout keyboard. There is not yet any way to + remap the keys for another layout, short of reassigning each + key individually using <menuchoice> + <guimenu lang="en">Settings</guimenu> + <guimenuitem>Configure Shortcuts...</guimenuitem> + </menuchoice>.</para> + + </sect3> + + </sect2> + + <sect2 id="matrix-insertion-midi"> + <title>Entering notes using a MIDI keyboard</title> + + <para> + You can enter notes into the matrix editor one at a time + using a MIDI keyboard or other MIDI control device. The + matrix editor uses the pitches you play on the keyboard, + but the durations you have selected in the Grid setting of + the editor itself. This is known as "step recording". + </para> + + <para> + To start entering notes from a MIDI keyboard, first make + sure the keyboard is configured as a MIDI + record device. Then make sure you have the right Grid + setting in the View menu or toolbar, as this controls the + note duration. Then press the <!-- !!! image of button + --> step recording button on the matrix editor's toolbar, + or select Step Recording from the Tools menu. From that + point on all notes pressed on the MIDI keyboard will be + inserted at the current insertion time in that window, + until step recording is switched off again or activated in + a different window or the window is closed. + </para> + + <para> + You can change the Grid setting while step recording is in + progress, in order to insert notes of different durations. + </para> + </sect2> + </sect1> + + <sect1 id="matrix-selection"> + <title>Selecting notes</title> <para>To select notes in the + matrix editor, switch to the Select (arrow) tool and then + outline a rectangular area containing the notes you want to + select. The selected events will then be highlighted in blue. + If you instead click on a single event, just that event will + be selected. + + </para><para>If you hold <keycap>Shift</keycap> while dragging + out a rectangle or clicking on a note, the new selection will + be added to any existing selection instead of replacing it. + </para> + + <para> + To clear a selection, click in an empty space on the matrix + editor, or hit the Escape key.</para> + + <para>You can also select all of the notes of a given pitch, + by shift-clicking on a key in the piano keyboard down the left + side of the matrix editor. You can also shift-click and drag + to select a range of pitches. This selection is added to any + existing selection you have, so if you want a clean new + selection, clear the old one first. + </para> + + <sect2 id="matrix-selectionfilter"> + <title>Filtering the selection</title> + <para>The <menuchoice> + <guimenu>Edit</guimenu> + <guimenuitem>Filter Selection</guimenuitem> + </menuchoice> function offers you the ability to filter a range of events in + any of several categories out of your selection. You can use this to refine the selection, if you want some action to apply to only certain events in it. + </para> + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-eventfilter.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>The event filter dialog</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + <para> + All ranges may be either inclusive or exclusive. + </para> + <para> + An inclusive range will remove events on either side of it + from the selection. You can use this, for example, to + filter everything below middle C and above the A above + middle C out of your selection. + </para> + <para> + An exclusive range will remove the events within the range + itself, leaving everything on either side of it selected. + Using the same search points as in the previous example, + you would use an exclusive range to remove everything + between middle C and the A above middle C from your + selection, while leaving everything above and below that + range selected. + </para> + <para> + Once your selection has been filtered, you can manipulate + it by any conventional means. + </para> + </sect2> + </sect1> + + <sect1 id="matrix-editing"> + <title>Moving and copying notes</title> + <para> + You can move notes in both time and pitch on the matrix + editor by either clicking and dragging them with the Move + tool, or selecting them and then dragging them with the + Select tool. + </para> + <para> + To copy notes, select them and then use the standard copy + and paste functions. After the paste the pasted notes will + be selected instead, and you can then drag them wherever you + need them. You may also copy notes by selecting them with + the Select tool, then keeping Ctrl pressed click-and-drag + the selected notes in a new position. + </para> + </sect1> + + </chapter> + + <chapter id="percussion-matrix-view"> + <title>The Percussion Matrix editor</title> + + <para>The Percussion Matrix editor is identical to the <link + linkend="matrix-view">Matrix editor</link>, except that it shows + pitch names on the vertical scale instead of a piano keyboard, and + it does not show the duration for each note. This is intended for + use with percussion programs on MIDI instruments, in which each + note pitch plays a different percussion sound.</para> + + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-percussionmatrix.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>&rosegarden;'s percussion matrix editor</phrase> + </textobject> + </mediaobject> + </screenshot> + The pitch names are only shown if the segment being edited is + playing through a percussion instrument that has an associated + key mapping to define the names; otherwise the standard matrix + view piano keyboard will appear instead. See <link + linkend="studio-keymappings">Percussion Key Mappings</link> for + more information about key mappings.</para> + </chapter> + + <chapter id="notation-view"> + <title>The Notation editor</title> + + <!-- Introduction, purpose --> + + <sect1 id="nv-introduction"> + <title>Introduction</title> + + <para> + + The &rosegarden; notation editor enables you to view and edit + one or more staffs in traditional score notation. + + </para><para> + + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-notationview.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>&rosegarden;'s notation editor</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + <para> + &rosegarden; aims to present scores with the best possible + layout compatible with its primary focus as a sequencer + application. This means that although the editor supports + chords, overlapping and nested beamed groups, triplets and + arbitrary tuplets, grace notes, dynamics, accents, text and so + on, it does not provide as much fine control over layout + (especially in contrapuntal music) as a dedicated score + editing program might. &rosegarden; does not aim to produce + typeset-quality score, although it can export LilyPond files, + which may form a good basis for typesetting. + + </para> + </sect1> + + <!-- Single and multiple staffs, and "current staff" --> + + <sect1 id="nv-staffs"> + <title>Single and multiple staffs</title> + + <para> + There are three ways to open a notation editor from the + &rosegarden; main window. (They all require that you + have some existing segments in the main window first, + so if you're starting a new composition, you should + create your segments before you start thinking about + how to edit them.) + + <variablelist> + + <varlistentry> + <term>Double-clicking on segments</term> + <listitem> + + <para>The most obvious way is just to double-click on + a segment in the main canvas. This opens the segment + in whatever you have configured <!-- !!!Link --> as + the default editor (notation, matrix, or event list), + and by default this is the notation editor. So + double-clicking a single segment will open it as a + single staff in a Notation editor window.</para> + + <para>You can also open a multi-staff editor this way: + holding down the Shift key, select (with a single + mouse click) each of the segments on the main view + that you want to open, but double-click on the last + one. All of the selected segments will then be opened + together in a single notation window.</para> + + </listitem> + </varlistentry> + + <varlistentry> + <term>The Open in Default Editor menu function (the Return key)</term> + <listitem> + + <para>The Return key is a shortcut for the Open in + Default Editor menu function, which does much the same + thing as double-clicking: opens all of the currently + selected segments together in a notation editor, or in + whichever other editor you have configured as your + default. </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>The Open in Notation Editor menu functions</term> + <listitem> + + <para>Alternatively, you can use the main window's + Open in + Notation Editor menu function, either on + the Segments menu or on the right-button popup menu on + a segment in the canvas. Select the segments you want + to edit (by shift-clicking as above, or by using the + Select All Segments function) and + then select Open in + Notation Editor.</para> + </listitem> + + </varlistentry> + </variablelist> + + </para> + + <para> + If you have more than one staff (i.e. segment) visible in the notation + editor, only one of them can be "current" at once. The + current staff can be distinguished because it has the insert + cursor on it (see <link linkend="nv-rulers">Rulers and + Cursors</link>), and this is the staff on which any editing + operations that use the insert cursor will take place. The + topmost staff is the current one by default, but you can + switch to a different staff by ctrl-clicking on it, or by using the + <menuchoice><guimenu>Tools</guimenu><guimenuitem>Local + Cursor</guimenuitem><guimenuitem>Cursor Up Staff</guimenuitem></menuchoice> and + <menuchoice><guimenuitem>Cursor Down Staff</guimenuitem></menuchoice> menu functions. + </para> + + </sect1> + + <!-- Linear and page layouts --> + + <sect1 id="nv-layout"> + <title>Linear and page layouts</title> + + <para> + The usual way the notation editor displays staffs is known + as Linear layout: one staff on top of another, with each + staff as a single, horizontally scrollable long line. Some + of the functions of the editor (such as the <link + linkend="nv-rulers">Rulers</link>) are only available in + Linear layout. + </para> + + <para> + However, you can also display staffs in two different + page-based layouts: Continuous Page and Multiple Page.</para> + + <para>In Continuous Page layout, the music is arranged in one + infinitely-tall page of the same width as the window. Each + staff breaks at the end of a line, starting a new line below + the remaining staffs.</para> + + <para>In Multiple Page layout, the music is divided up into + real pages much as it will be when printed. The size of each + page is calculated so that approximately the same amount of + music will fit on each line as it will when actually printed + (according to the point size specified for the printing + resolution in the configuration dialog). The printed version + is unlikely to be exactly the same, as it depends on the + precise paper size and margins in use when printing, but it + should be fairly close if you happen to be using A4 + paper.</para> + + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-notationview-multipage.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>&rosegarden;'s notation editor in Multiple Page layout</phrase> + </textobject> + </mediaobject> + </screenshot> + </para><para> + Most, but not all, of the display and editing functions + work in the page layout modes as well as in linear layout. + </para> + + <para> + To switch between these layout modes, use the Linear Layout, Continuous Page Layout and Multiple Page Layout menu functions. + </para> + </sect1> + + <!-- Rulers and Cursors --> + + <sect1 id="nv-rulers"> + <title>Rulers and cursors</title> + + <para> + The &rosegarden; Notation editor window includes two graduated rulers, + each associated with its own cursor. The rulers are the horizontal strips + divided up with tickmarks at top and bottom of the main + notation canvas, and the cursors are the coloured vertical + lines shown initially at the start of the top staff in the + editor. In addition to these main two, there are the <guimenuitem>chord + name</guimenuitem> ruler, the <guimenuitem>tempo</guimenuitem> ruler, + and the <guimenuitem>raw note</guimenuitem> ruler. + </para> + <para> + Note that the rulers are only shown in <link + linkend="nv-layout">Linear layout</link> mode, and several of them + are not displayed by default. + </para> + + + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-cursors.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>The notation editor's two cursors</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + + <para> + The purple cursor is the insert cursor. It shows the point + at which operations such as insert and paste will take + place. You can reposition the insert cursor by clicking or + dragging on the top ruler, or by clicking with the Select + tool on an empty part of the staff (avoiding any events), or + by clicking anywhere with <keycap>Ctrl</keycap> held down. + </para> + + <para>You can also use the left and right arrow keys to move + the insert cursor one event at a time. If you hold <keycap>Ctrl</keycap> while + pressing the arrow keys, the cursor will move a whole bar at a + time; if you hold Shift, the cursor will <link + linkend="nv-tools-selections">select the events</link> as it + passes over them. + </para> + + <para> + The blue cursor is the playback pointer. Just like the + similar cursors in the main window and the matrix views, + this shows the location of the current playback or record + position, and it sweeps across the notation while the transport is + rolling. It can be repositioned using the bottom ruler. + </para> + <sect2 id="nv-raw-note-ruler"> + <title>The raw note ruler</title> + <para>The raw note ruler is particularly + useful when editing <link linkend="nv-quantization">quantized + notation</link> where the display duration on the page + differs from the duration of the actual performance. + Enabled via + <menuchoice> + <guimenu>Settings</guimenu> + <guimenuitem>Rulers</guimenuitem> + <guimenuitem>Show Raw Note Ruler</guimenuitem> + </menuchoice>, it draws a small bar above + each note, similar to the way notes appear in the matrix. In this + example screenshot, you can see how interpreted, quantized notes + appear on this ruler. The tenuto notes have full performance + durations, while the staccato notes are considerably shorter, and + the accented notes have a higher velocity (more red colour) than + their neighbors. + </para> + <para> + Raw note ruler marks only notes in the selected segment in the track. + The colour of the selected segment is used in the background of + the raw note ruler between the start and end time of the segment. + </para> + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata + fileref="rg-rawnoteruler.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>The raw note ruler, + showing notation whose performance duration value differs + from what appears on the staff</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + </sect2> + <sect2 id="nv-chord-name-ruler"> + <title>The chord name ruler</title> + <para>The chord name ruler analyzes the tonality of the piece, and + attempts to display which chords are sounding. This is for + informational purposes only, and you can neither print nor edit the + contents of this ruler. + <!-- !!! throw in a link to how to do proper chords with text, and + should probably get into fretboards too, but I'm not going to mention + fretboards in this manual at this time (for 1.3) because it's too + rough, and I just don't care to get into that yet --> + </para> + </sect2> + <sect2 id="nv-tempo-ruler"> + <title>The tempo ruler</title> <para>The tempo ruler displays + the global tempo, and provides a vehicle for entering, + editing, and manipulating it. It works the same way as the + tempo rulers in the main window and the matrix editor. See + <link linkend="tempo-ruler">Tempo Rulers</link> for more + information.</para> + </sect2> + + </sect1> + + <!-- Display conventions (annotated picture with some selected notes, + some quantized notes, a bar of incorrect length etc) --> + + <!-- Tools and Selections --> + + <sect1 id="nv-tools-selections"> + <title>Tools and selections</title> + <para> + Most of the menu and toolbar editing functions in the + &rosegarden; Notation editor fall into one of three + categories: <quote>tools</quote>, <quote>functions that + operate on selections</quote>, and <quote>drag + operations</quote>. + </para> + + <variablelist> + <varlistentry> + <term>Tools</term> + <listitem> + <para> + The basic tools are the selection tool, the erase + tool, and those for inserting notes, rests, text and so + on, which are usually accessed from the toolbar buttons. + </para> + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata + fileref="rg-notationtools.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>The insert, erase, text, and guitar chord tools</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + + <para> + Choosing a tool changes the default behaviour of the + mouse buttons on the main notation canvas, at least + until another tool is chosen instead. For example, + choosing the selection tool allows you to make + selections and so to use the selection-based functions + (below); choosing an insertion tool (such as one of the + notes) switches the <acronym>GUI</acronym>'s behaviour so as to insert + notes by clicking on the canvas; choosing the erase tool + allows you to remove events by clicking on them. + </para> + <para> + You can also change the current tool using the Tools menu. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>Functions that operate on selections</term> + <listitem> + <para> + The majority of the remaining menu functions require a + selection to be made on the canvas before they can be + used. Some of them (such as <guimenuitem>Cut</guimenuitem> + or the <guimenuitem>Note Style</guimenuitem> + functions) will operate on any selected events; others + (<guimenuitem>Stem Directions</guimenuitem> function) + will refuse to work unless the selection contains + some notes. + </para> + <para> + To select some events on the canvas, switch to the + Select (arrow) tool and then outline a rectangular area + containing the events you want to select. The selected + events will then be highlighted in blue. If you click + on a single event, just that event will be selected <footnote> + <para> You can also double-click on a single event to open an + editing dialog for that event, but that's got nothing to + do with selections.</para> </footnote>). + </para><para>If you hold + <keycap>Shift</keycap> while dragging + out a rectangle, its contents will be added to any + existing selection instead of replacing it. + </para> + <para> + To select a whole bar, double-click with the Select tool + on some empty space within that bar; to select the whole + staff, click three times. The Edit menu carries + functions for selecting extended areas based on the + location of the insert cursor, and you can also select + events around the insert cursor by holding Shift and + pressing the left or right arrow keys. + </para> + <para> + It is not possible to select events from more than + one staff at once. + </para> + <para>After selecting some events, you can filter your selection further using the <menuchoice> + <guimenu>Edit</guimenu> + <guimenuitem>Filter Selection</guimenuitem> + </menuchoice> function. For more details, refer to <link linkend="matrix-selectionfilter">the corresponding function in the matrix editor</link>. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>Drag operations</term> + <listitem> + <para> + You can also do a certain amount of editing just by + dragging things around. Switch to the Select (arrow) + tool, and then you can change the pitch of notes by + just click-and-dragging their heads up or down, and + change the times of notes and other events by dragging + them left or right. (You can't drag rests or time + signatures, but you can drag everything else. If you + have more than one event selected, the whole selection + will be dragged at once.) + </para> + <para> + Dragging is usually a less accurate way of editing + things than using the menu or toolbar functions, but + it can be easier. + </para> + </listitem> + </varlistentry> + </variablelist> + + <sect2> + <title>Transposing</title> + + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="transpose-by-interval.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>Transposing by interval</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + <para> + In Notation view menu there are two functions which can be + used to transpose notes by an arbitrary interval, namely + <menuchoice> + <guimenu lang="en">Adjust</guimenu> + <guimenuitem>Transpose</guimenuitem> + <guimenuitem>Transpose by Semitones</guimenuitem> + </menuchoice> + function which asks just the number of semitones to be + transposed, and + <menuchoice> + <guimenu lang="en">Adjust</guimenu> + <guimenuitem>Transpose</guimenuitem> + <guimenuitem>Transpose by Interval</guimenuitem> + </menuchoice> + function which shows a neat dialog that can be used to + transpose notes. In the latter, the dialog shows an example + notes before and after transposing and expresses the + interval in written form. The interval may be changed either + by dragging the notes shown by the dialog or by changing + separately the base note, its octavation and accidentals. + </para> + <para> + In Segment view, Notation view, and Track view there is also + <menuchoice> + <guimenu lang="en">Segment(s)</guimenu> + <guimenuitem>Transpose by Interval</guimenuitem> + </menuchoice> + function which makes a transpose to entire segment. In this + dialog you may also choose whether only the notes are + transposed or the keys of the segment are transposed also. + </para> + </sect2> + </sect1> + + <!-- Insertion: notes, auto-ties, accidentals --> + + <sect1 id="nv-insertion"> + <title>Inserting notes and rests</title> + + <para>To insert a note, select one of the note tools by clicking + on a particular duration of note on the toolbar, and then click + on the staff at the point where you want to add the note.</para> + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata + fileref="rg-notation-toolbars.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>The duration, rests, and accidentals toolbars</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + + <para>You can also select one of the accidentals on the toolbar + to insert sharpened or flattened notes. If no accidental is + selected, the note inserted will follow the key signature. + Alternatively, you can select the "Follow previous accidental" + icon (shown as a note with an arrow pointing back from where the + accidental would appear) to make the note follow whatever + accidental was last used at the same height on the staff.</para> + + <para>If you add a note at the same time as an existing note of + different duration, the editor will generally assume that you + want to create chords and will split the existing or new note + accordingly so as to create one or more chords with ties. If + you really do want to chord two different durations, you can + select the tied noteheads and use the Collapse Equal-Pitch Notes + function to merge them together. Alternatively, the default + behaviour can be changed in the &rosegarden; configuration dialog + so as not to do the split at all.</para> + + <para>If you add a note exactly over an existing note of + different duration (i.e. at the same pitch), the duration of the + existing note will be changed to that of the new one.</para> + + <para>If you add a rest at the same time as an existing note, + the note will be silenced for the duration of the rest, + shortening or possibly removing it altogether.</para> + + <sect2 id="nv-insertion-keyboard"> + <title>Typing notes and rests with the PC keyboard</title> + + <sect3> + <title>Duration</title> + + <para>First, ensure a notation tool is selected to indicate + the duration of note (or rest) you wish to insert. You can + select the various note types using the number keys:</para> + + <itemizedlist> + <listitem><para><keycap>5</keycap> – Breve</para></listitem> + <listitem><para><keycap>1</keycap> – Whole note (semibreve)</para></listitem> + <listitem><para><keycap>2</keycap> – Half note (minim)</para></listitem> + <listitem><para><keycap>4</keycap> – Quarter note (crotchet)</para></listitem> + <listitem><para><keycap>8</keycap> – Eighth note (quaver)</para></listitem> + <listitem><para><keycap>6</keycap> – Sixteenth note (semiquaver)</para></listitem> + <listitem><para><keycap>3</keycap> – Thirty-second note (demisemiquaver)</para></listitem> + <listitem><para><keycap>0</keycap> – Sixty-fourth note (hemidemisemiquaver)</para></listitem> + </itemizedlist> + + <para>You can switch to a triplet version of the note + duration by pressing the <keycap>G</keycap> key. Pressing it + again will switch back to the normal duration. The status + bar at the bottom of the window will notify you of when a + triplet duration is active.</para> + </sect3> + + <sect3> + <title>Pitch</title> + + <para>Once a notation tool is selected, you can insert a + note at the current position of the <link + linkend="nv-rulers">insert cursor</link> by pressing one of + the pitch keys:</para> + + <itemizedlist> + <listitem><para><keycap>A</keycap> – Do (the tonic of the current key in the current clef)</para></listitem> + <listitem><para><keycap>S</keycap> – Re</para></listitem> + <listitem><para><keycap>D</keycap> – Mi</para></listitem> + <listitem><para><keycap>F</keycap> – Fa</para></listitem> + <listitem><para><keycap>J</keycap> – So</para></listitem> + <listitem><para><keycap>K</keycap> – La</para></listitem> + <listitem><para><keycap>L</keycap> – Ti</para></listitem> + </itemizedlist> + + <para>Press the "." key to togggle between dotted and + undotted durations.</para> + + <para>Holding <keycap>Shift</keycap> while pressing a key + will sharpen the note (except for Mi and Ti, which don't + have sharpened versions) and holding <keycap>Shift</keycap> + and <keycap>Ctrl</keycap> together will flatten it (except + for Fa and Do).</para> + + <para>To enter notes an octave higher, use the corresponding + keys on the next row up: <keycap>Q</keycap>, + <keycap>W</keycap>, <keycap>E</keycap>, <keycap>R</keycap>, + <keycap>U</keycap>, <keycap>I</keycap>, and + <keycap>O</keycap>. Likewise to enter notes an octave + lower, use <keycap>Z</keycap>, <keycap>X</keycap>, + <keycap>C</keycap>, <keycap>V</keycap>, <keycap>B</keycap>, + <keycap>N</keycap> and <keycap>M</keycap>.</para> + + </sect3> + + <sect3> + <title>Rests</title> + + <para>To insert a rest instead of a note, press + <keycap>P</keycap>. Alternatively, you can use the + <keycap>T</keycap> and <keycap>Y</keycap> keys to switch the + current tool to a rest tool and back to a note tool again.</para> + + </sect3> + + <sect3> + <title>Chords</title> + + <para>The default behaviour of the notation editor is to + move the insert cursor forward after inserting a note, so as + to be ready to insert another note after it in a melody; + this can be changed using the <keycap>H</keycap> key, which + switches to chord mode so that subsequent insertions occur + at the same time as the last one. Pressing + <keycap>H</keycap> again switches back to the melody + insertion behaviour.</para> + + </sect3> + + <sect3> + <title>Changing note durations</title> + + <para>You can use the keyboard to change the durations of + notes that you've already entered. Make sure the notes you + want to change are selected, and then press + <keycap>Ctrl</keycap> plus the number key for the note you + want. You can also add or remove dots, by pressing + <keycap>Ctrl</keycap> plus "." — use this repeatedly to + select between one dot, two dots and no dots.</para> + + <para>If you also hold <keycap>Alt</keycap> as well as + <keycap>Ctrl</keycap>, you will change the durations of the + notes as displayed in the notation editor without changing + their performed durations. This can be very useful for + tidying up a score: see also <link + linkend="nv-quantization">notation from performance + data</link>. + </para> + </sect3> + + <sect3> + <title>Other remarks</title> + + <para>All of the insertion commands are also available on a + submenu of the Tools menu. It's unlikely you'd ever want to + navigate the menus just to insert a single note, but the + menus show the keyboard shortcuts and so provide a useful + reference in case you forget which key is which.</para> + + <para>The keyboard shortcuts are currently designed for use + with a QWERTY-layout keyboard. There is not yet any way to + remap the keys for another layout, short of reassigning each + key individually using the "Configure Shortcuts..." option + on the Settings menu.</para> + + <para>Holding the <keycap>Ctrl</keycap> key while pressing a + number will select the corresponding dotted-note + tool.</para> + + </sect3> + + </sect2> + + <sect2 id="nv-insertion-midi"> + <title>Entering notes using a MIDI keyboard</title> + + <para> + You can enter notes into the notation editor one at a time + using a MIDI keyboard or other MIDI control device — a + process known as step recording. The notation editor uses + the pitches you play on the keyboard, but the durations you + have selected in the editor itself. + </para> + + <para> + To start entering notes from a MIDI keyboard, first make + sure the keyboard is configured as your default MIDI + record device. Then make sure a notation tool is selected + to set a duration. Then press the <!-- !!! image of + button --> step recording button on the notation editor's + toolbar, or select Step Recording from the Tools menu. + From that point on all notes pressed on the MIDI keyboard + will be inserted at the current insertion time in that + notation window, until step recording is switched off + again or activated in a different window or the window is + closed. + </para> + + <para> + You can select another notation tool while step recording + is in progress, in order to insert notes of different + durations; and you can also switch into Chord mode <!-- + !!! link --> to insert chords. + </para> + </sect2> + + </sect1> + + <!-- Keys, Clefs and Time Signatures --> + + <sect1 id="nv-signatures"> + <title>Clef and key</title> + +<!-- !!! rework --> + <para>The first thing to know about the way &rosegarden; handles + these is that time-related changes (tempos and time + signatures) are treated entirely differently from clefs and + keys. In order to simplify managing playback and recording as + well as notation, &rosegarden; requires that when the tempo or + time signature changes, it does so in all staffs at once. You + can't have one staff in 2/4 and another in 6/8 simultaneously, + or one staff playing at 120 to the beat and another at 90. + This applies only to time: there is no such restriction on the + use of clef and key changes. See also <link linkend="tempo">Tempo in Rosegarden</link>.</para> + + <para>To change the clef, key, tempo or time signature within a + notation editor window, position the <link + linkend="nv-rulers">insert cursor</link> at the point where you + want the change to happen, and use one of the Edit menu's Add + Clef Change..., Add Key Change..., Add Tempo Change... and Add + Time Signature Change... functions. You will then see a dialog + box in which you can choose the particular clef, key, tempo or + time signature setting you want to apply, as follows.</para> + + <sect2 id="nv-signatures-clef"> + <title>Clef</title> + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-clefdialog.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>&rosegarden;'s clef dialog</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + + <para>The dialog allows you to choose a clef, but also + to choose how you want the clef to be applied, in + cases where there are already some notes following + the point where the clef is to be inserted. You + must choose one of the following: + + <variablelist> + + <varlistentry> + <term>Maintain current pitches</term> + <listitem> + <para> + Any notes following the clef will keep + their current performance pitches. + </para> + <para> + For example, inserting a + tenor clef in the middle of a previously + treble-clef section will cause the notes following + the clef to be moved an octave + higher up the staff, because they will still have + their treble-clef pitches. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>Transpose into appropriate octave</term> + <listitem> + <para> + Any notes following the clef will + retain their pitch within the octave, but + may be moved into a different octave to + match the new clef, and therefore will play + at a new pitch. + </para> + <para> + For example, inserting a tenor clef in the + middle of a previously treble-clef section + will cause the notes following the clef to + move by one staff line only to adjust to the new + clef, but to play an octave lower than before. + </para> + </listitem> + </varlistentry> + + </variablelist> + + </para> + </sect2> + + <sect2 id="nv-signatures-key"> + <title>Key</title> + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-keysigdialog.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>&rosegarden;'s key signature dialog</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + <para>The dialog allows you to choose a key signature, but also + to choose how you want the key signature to be applied. You + must choose among the following: + </para> + + <variablelist> + + <varlistentry> + <term>Key signature</term> + <listitem> + <para> + Used to dial up the actual key signature. The dialog will + attempt to analyze the tonality of the piece, and guess at + the key signature if no key is already in effect at that + point in the notation. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>Key transposition</term> + <listitem> + <para>You must choose whether to transpose the key according + to segment transposition, or to use the key exactly as + specified. + </para> + <para> + For example, if you are inserting a key of Bb major into a + transposed Bb trumpet part that's sounding at a + transposition of -2, you use this option to tell + &rosegarden; whether the key of Bb you have entered should + be written as a Bb (concert Ab), or should be transposed + against the segment to result in the trumpet key of C major + (concert Bb). + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>Scope</term> + <listitem> + <para> + You must choose whether to apply this key signature to + the current segment only, or to all segments, on all + tracks, at this time. + </para> + <para> + If you elect to apply the change to all segments at + this time, the previous key transposition choice will + govern whether all segments receive the specified key, + or a key appropriately transposed segment by segment. + (This is a convenient way to deal with notation for + transposing instruments, because it frees you to think + of all keys in concert pitch, and allow &rosegarden; + to work out what key is used for what transposition.) + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>Existing notes following key change</term> + <listitem> + <para> + You must choose whether any existing notes following + this key change will maintain their current pitches, + maintain their current accidentals in the key, or + whether Rosegarden should make an attempt to transpose + the part into the new key. + </para> + </listitem> + </varlistentry> + + </variablelist> + </sect2> + + </sect1> + + <!-- Text --> + + <sect1 id="nv-text"> + <title>Text, Lyrics, and LilyPond directives</title> + + <para>A staff can contain various sorts of text, in text + events. There are two basic classes of user-editable text event: single + text items used for point annotations etc., and lyrics, plus a third + type used especially for tweaking LilyPond export. User-editable + types can be created (and so associated with a particular + time in the staff) using the Text tool, which is available on + the + <inlinemediaobject> + <imageobject> + <imagedata fileref="rg-text-cursor.png" format="PNG"/> + </imageobject> + </inlinemediaobject> + button in the toolbar. Lyrics can + also be created this way, but are more easily created using + the <link linkend="nv-text-lyrics">lyric editor</link>.</para> + + <para>To add a piece of text, select the Text tool and click + at the point where you want to add it. If you want the text + associated with a particular note or rest, it may be helpful to click + the T cursor directly on that note, so as to ensure proper placement + in time. A dialog box will appear, into which you can type the text + and choose its intended purpose. (Rosegarden prefers to store what + the text is for, rather than how it should look; this is so that in + future we may be able to configure how the various sorts of text are + presented for each individual user.) + + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-textdialog.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>&rosegarden;'s text dialog</phrase> + </textobject> + </mediaobject> + </screenshot> + + The available + purposes (or styles) are:</para> + + <variablelist> + + <!-- NOTE: I have removed the "by default" in the following + descriptions. There is no "by default" to this. It does + what it does, and there is no changing it without editing + source code. (dmm) --> + + <varlistentry><term>Dynamic</term><listitem><para> Used for + minor local indications such as the dynamic marks "p", "mf" + etc. Shown below the staff in small italic + type. </para></listitem></varlistentry> + + <varlistentry><term>Direction</term><listitem><para> Used + when indicating significant changes in style or mood. Shown + above the staff in large roman type. + </para></listitem></varlistentry> + + <varlistentry><term>Local Direction</term><listitem><para> + Used to indicate less significant changes in style or mood. + Shown below the staff in a smaller bold-italic roman + type. </para></listitem></varlistentry> + + <varlistentry><term>Tempo</term><listitem><para> Used to + indicate significant changes in tempo. Shown above the + staff in large bold roman type. + </para></listitem></varlistentry> + + <varlistentry><term>Local Tempo</term><listitem><para> Used + to indicate more minor or local changes in tempo. Shown + above the staff in a small bold roman type. + </para></listitem></varlistentry> + + <varlistentry><term>Chord</term><listitem><para> Used + to indicate chord changes for guitarists, etc. Shown + above the staff in a small bold roman type. + </para></listitem></varlistentry> + + <varlistentry><term>Lyric</term><listitem><para> Although + lyrics are usually created in the <link + linkend="nv-text-lyrics">lyric editor</link>, they can also + be entered word by word if necessary using this style. This + style is shown below the text in a small roman typet. + (Warning: if you enter lyrics this way and later + edit the staff's lyrics using the lyric editor, any lyrics + entered this way may be modified or moved if their + positioning is not compatible with that expected by the + lyric editor.) </para></listitem></varlistentry> + + <varlistentry><term>Annotation</term><listitem><para> Used + for helpful text that is not strictly considered part of the + score. Shown below the staff, boxed-out in a yellow + sticky-label-style box. These may not be visible + initially, and can be turned on via + <guimenu>Settings</guimenu> + <guimenuitem>Show Annotations</guimenuitem> + </para></listitem></varlistentry> + + <varlistentry><term>LilyPond Directive</term><listitem><para> Used + as the mechanism for exporting special tags that are + only understood by the LilyPond exporter. These + provide a means to extend &rosegarden;'s capabilities + beyond what it can do within its own native interface. + Shown above the staff, in a green box. These may not be visible + initially, and can be turned on via + <guimenu>Settings</guimenu> + <guimenuitem>Show LilyPond Directives</guimenuitem> + </para></listitem></varlistentry> + </variablelist> + + <para>For many of the styles, a new combo box will appear that allows + you to select from a variety of commonly-used texts appropriate for + that style, such as "Allegro" and "ritardando." Selecting one of + these texts saves typing, but in no way impedes your ability to type + your own text by hand, should you so desire. + </para> + + <para>You can also edit text after creating it, by clicking on + the existing text with the text tool.</para> + + <sect2 id="nv-text-lyrics"> + <title>Editing lyrics</title> + + <para>The Lyric editor, available from the + <menuchoice> + <guimenu lang="en">View</guimenu> + <guimenuitem>Open Lyric Editor</guimenuitem> + </menuchoice> + function, allows you to edit all of + the lyric events for a single staff at once, using a fairly + rudimentary textual editing system. To use it, just + activate the menu option, edit the lyric text in the + resulting dialog, and then hit OK.</para> + + <para>The lyrics you enter should follow a particular + format. Bar lines are vital to avoid the editor getting + confused, and are represented with a slash ("/"). Within + each bar the individual syllables are separated by spaces + (at least one space: the editor doesn't care about any extra + whitespace). Each syllable in turn will be attached to the + next subsequent note or chord within that bar (although at + the moment the editor can get quite confused by chords that + are not exact, i.e. that require smoothing or + quantizing).</para> + + <para>If you want a note to have no syllable attached to it, + you need to provide a dot (".") as the syllable for that + note. (This is why the default lyric text for a segment is + usually full of dots.) Remember to separate the dots with + spaces, so that they are clearly separate syllables.</para> + + <para>If you want more than one syllable on the same note, + with a space between them, use a tilde ("~") instead of the + space. It will be shown as a space on the score.</para> + + <para>If you want to split a syllable across two notes, with + a hyphen, you need to enter a space following the hyphen so + the editor knows to treat it as two syllables. (Hyphens get + no special treatment within syllables.)</para> + + <para>Syllables consisting only of numbers surrounded by + square brackets (like "[29]") will be ignored; this is the + format used for the automatically-generated bar numbers + shown in the editor.</para> + + <para>You should also be aware that the textual format of + lyrics is only used for editing: the lyrics are actually + stored as distinct text events (one per syllable). This + means that the text format may potentially change in the + future to accommodate more advanced editing capabilities, + although the event format should not change and so your + saved files should continue to be compatible.</para> + + <para>&rosegarden; supports also multiple lines of lyrics. + You may always attach one more verse into a single staff + by clicking Add Verse in the lyrics editor. All the verses + are entered with the same syntax. If you leave the last verse + without syllables, or make it empty, it is removed from + the list of verses next time you open the lyrics editor. + </para> + + </sect2> + <sect2 id="nv-lilypond-directives"> + <!-- text has a link here because the reading chain is: + intro -> lilypond directives, which puts you at a point well away + from any explanation of the whole text dialog and whatnot --> + <title>Using special LilyPond directives</title> + <para>LilyPond directives are a special kind of <link + linkend="nv-text">text</link> that you can + use to export .ly files that take advantage of + functionality not yet available directly through &rosegarden;'s + own native interface. + </para> + <para>Some of these are a bit fiddly with respect to how their + placement in time affects their function. It is not always + immediately apparent at a glance just where they are, or what notes + or barlines they will affect, so I have made placement suggestions + to help ease the process of getting them in the right spot. + </para> + <para> + These directives are: + </para> + + <variablelist> + <varlistentry> + <term>Segno</term><listitem><para>used to export a + <inlinemediaobject> + <imageobject> + <imagedata fileref="rg-segno.png" format="PNG"/> + </imageobject> + </inlinemediaobject> + </para></listitem> + </varlistentry> + + <varlistentry> + <term>Coda</term><listitem><para>used to export a + <inlinemediaobject> + <imageobject> + <imagedata fileref="rg-coda.png" format="PNG"/> + </imageobject> + </inlinemediaobject> + </para></listitem> + </varlistentry> + + <varlistentry> + <term>Alt1</term><listitem><para>Placed anywhere in a + measure, designates that the measure(s) + that follow this one should be exported as the + first alternate ending (see file + lilypond-alternative-endings.rg for example) + </para></listitem> + </varlistentry> + + <varlistentry> + <term>Alt2</term><listitem><para>Placed anywhere in a + measure, designates that the measure(s) + that follow this one should be exported as the + second alternate ending (see file + lilypond-alterantive-endings.rg for example) + </para></listitem> + </varlistentry> + + <varlistentry> + <term>|| -></term><listitem><para>Placed anywhere in a + measure, designates that the next calculated barline will be + rendered as a double barline (see file + lilypond-directives.rg for example) + </para></listitem> + </varlistentry> + + <varlistentry> + <term>|. -></term><listitem><para>Placed anywhere in a + measure, designates that the next calculated barline will be + rendered as a terminating barline (see file + lilypond-directives.rg for example) + </para></listitem> + </varlistentry> + + <varlistentry> + <term>: -></term><listitem><para>Placed anywhere in a + measure, designates that the next calculated barline will be + rendered as a dashed barline (see file + lilypond-directives.rg for example) + </para></listitem> + </varlistentry> + + <varlistentry> + <term>Gliss.</term><listitem><para>Placed by clicking + directly on a notehead, draws a glissando between + the target note and the note immediately following (see file + lilypond-directives.rg for example) + </para></listitem> + </varlistentry> + + <varlistentry> + <term>Arp.</term><listitem><para>Placed by clicking + directly on a chord, draws a wavy line arpeggio + symbol immediately to the left of the affected chord (see file + lilypond-directives.rg for example) + </para></listitem> + </varlistentry> + + <varlistentry> + <term>Tiny ->.</term><listitem><para>Placed anywhere, + designates that notation immediately following this + directive should be rendered at the "tiny" size (see file + lilypond-directives.rg for example) + </para></listitem> + </varlistentry> + + <varlistentry> + <term>Small ->.</term><listitem><para>Placed anywhere, + designates that notation immediately following this + directive should be rendered at the "small" size (see file + lilypond-directives.rg for example) + </para></listitem> + </varlistentry> + + <varlistentry> + <term>Norm. ->.</term><listitem><para>Placed anywhere, + designates that notation immediately following this + directive should be rendered at the normal size; + usually used to cancel a Tiny -> or Small ->. (see file + lilypond-directives.rg for example) + </para></listitem> + </varlistentry> + </variablelist> + </sect2> + </sect1> + + <!-- Indications --> + + <sect1 id="nv-guitarchords"> + <title>Guitar Chords</title> + + <para> + Like text, it is possible to add guitar chord diagrams to a + notation track (or to edit previously added ones). This is + done by toggling the + <guimenuitem>Guitar Chord</guimenuitem> + button, and then clicking on the same area as for adding text. + This will open the Guitar Chord dialog. With it you can select + which guitar chord diagram you want to add from a chord + dictionary which comprises most of the common chord fingerings + by specifying a chord's root and its extension. For + convenience, the fingerings are sorted in three different + categories : + <guimenuitem>beginner</guimenuitem> + , + <guimenuitem>common</guimenuitem> + and + <guimenuitem>all</guimenuitem> + . These categories are actually based on the chord extension + (A7 is a beginner chord, while A13 isn't), not on the + fingering itself, so you can still see "advanced" chord + fingerings listed, even in beginner mode. + </para> + + + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-guitarchorddialog.png" + format="PNG" /> + </imageobject> + <textobject> + <phrase>&rosegarden;'s chord selector dialog + </phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + + <para> + It is also possible to add your own fingerings if needed. To + do this, click on the 'New' button. This will pop up a chord + editor, where you can "draw" which fingering you want to add, + and specify its root, chord extension, and starting fret + number. + <screenshot> + <mediaobject> + <imageobject> + <imagedata + fileref="rg-guitarchordeditordialog.png" format="PNG" /> + </imageobject> + <textobject> + <phrase>&rosegarden;'s chord editor dialog + </phrase> + </textobject> + </mediaobject> + </screenshot> + + Note that while you can choose the extension from a list of + predefined values, you can also type whatever value you want. + However, in that case, the new fingering will only be + available in the 'all' list. Also, you can only delete and + edit your own chords. Those from the predefined dictionary + cannot be changed. If you spot a mistake in one of them, + please report it to the development team. + </para> + + </sect1> + + <!-- Indications --> + + <sect1 id="nv-indication"> + <title>Slurs and hairpins</title> + + <para>Slur and hairpin (crescendo/decrescendo) dynamic markings are stored as events, + just like notes or rests. To create one, select the area you + want it to cover (a series of notes or whatever), and then use + the <guimenuitem>Add Slur</guimenuitem>, + <guimenuitem>Add Crescendo</guimenuitem> or + <guimenuitem>Add Decrescendo</guimenuitem> options from + the <guimenu>Phrase</guimenu> menu.</para> + + <para>Placement of hairpins can be somewhat tricky, and this is + especially so with haripins that run in line with dynamic markings. + It is commonly the case that a hairpin that doesn't quite look right + in &rosegarden;'s own notation editor will nevertheless come out just + fine once exported to LilyPond. &rosegarden;'s slurs generally come + out best when all the stems are running in the same direction, and + occasionally need to be <link + linkend="nv-microposition">repositioned</link> by hand to achieve + better placement. Slurs also tend to fare slightly better once + exported to LilyPond. + </para> + + <para>You remove a slur or hairpin in the same way as any + other event: either select it with the selection tool and then + hit <keycap>Delete</keycap>, or click on it with the erase tool active.</para> + + </sect1> + + <!-- Stem direction, slashes etc --> + + <sect1 id="nv-note-qualities"> + <title>Note stems and slashes</title> + + <para>You can set the stem direction of any selected notes + (provided they are a sort that have stems) using the three + Stem Direction options on the Notes menu. The options allow + you to either fix the stems up or down, or revert to the stem + direction that &rosegarden; would otherwise have chosen. See + also <link linkend="nv-beamed-groups">Beams</link>.</para> + + <para>The <guimenu>Note</guimenu> menu also contains options for adding slashes + across note stems, for example to indicate short repeated + notes or drum rolls. These are currently purely notational; + &rosegarden; will not take them into account when playing the + staff or generating &MIDI;.</para> + </sect1> + + <!-- Beamed groups, including overlapping and nesting them --> + + <sect1 id="nv-beamed-groups"> + <title>Beams</title> + + <para>Adding beams to notes is considered a grouping operation + in the &rosegarden; Notation editor, available on the <guimenu>Phrase</guimenu> + menu. Select the notes you want to beam, and use the + <guimenuitem>Beam Group</guimenuitem> menu option. To remove a beam, select the notes and use + the <guimenuitem>Unbeam</guimenuitem> menu option.</para> + + <para>It is possible to have more than one beamed group + happening at the same time — you just select and beam the + separate groups one at a time — but Rosegarden is usually not + yet clever enough to work out which notes should have stems up + and which should have stems down for simultaneous beamed + groups, so you will probably have to set the stem directions + of the notes in the groups explicitly as well as beaming them.</para> + + <para>&rosegarden; can attempt to guess a sensible beaming for a + piece of music, provided it's not too complicated. To invoke + this, select the notes you want to calculate the beaming for + (for example by triple-clicking to select a whole staff) and + then use the <guimenuitem>Auto-Beam</guimenuitem> option on the + <guimenu>Phrase</guimenu> menu. Auto-beaming + is also done automatically when loading a &MIDI; file, for + example, and the editor also does some automatic beaming as + you enter notes (this can be disabled by changing the + "Auto-Beam when appropriate" setting on the configuration + dialog or the insertion tool's right-button menu).</para> + + </sect1> + + <!-- Tuplets --> + + <sect1 id="nv-tuplets"> + <title>Triplets and other tuplets</title> + + <para>A triplet group consists of three notes or chords played + in the time of two. (More precisely, it consists of notes + with a total duration of three arbitrary units played in the + time of two of those units.)</para> + + <para>We use the word <quote>tuplet</quote> to describe the general + situation in which notes with a total duration of any given + number of units are played in the time of a different number + of those units: nine notes in the time of eight, or six in the + time of four, or a crotchet and a quaver in the time of a + single crotchet, or even two notes in the time of three. (At + present &rosegarden; does not support the last example — tuplet + groups must always be played with a shorter duration than + written.)</para> + + <para>The triplet and tuplet menu functions work by taking an + existing series of notes or rests and squashing them so they + play quicker, filling in the left-over space at the end of the + series with a final rest and drawing the whole as a tuplet + group. You can therefore create a new series of triplets by + entering the first two notes of the series (in their normal + form), making them into triplets, and then filling in the rest + left over by the triplet operation with the final note of the + triplet. Or you can apply the triplet operation before you + enter any notes, thus turning the original rest itself into + triplet form, and then insert the notes of the triplet on top + of it. Some examples may help:</para> + + <!-- Need examples and screenshots --> + + <!-- Then discuss general tuplet dialog... --> + + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-tupletdialog.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>&rosegarden;'s general tuplet dialog</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + + <para>To specify a general tuplet group, we need to know what + the base note is (for example, if we play three crotchets in + the time of two then the base is a crotchet) and the ratio of + the number of base notes written to the number played.</para> + + <!-- Then discuss "tuplet mode": with a subtitle? --> + + </sect1> + + <!-- Grace notes --> + + <!-- Paste --> + + <sect1 id="nv-paste-types"> + <title>Paste types</title> + + <para> + The meaning of <quote>cut and paste</quote> is less obvious for a music + editing program than it is for something like a word + processor in which the letters and words go in a simple + linear order. Accordingly, &rosegarden;'s Notation editor + offers several different types of Paste operation, as well + as separate Cut and Cut and + Close functions. + </para> + + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-pastedialog.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>&rosegarden;'s paste-type dialog</phrase> + </textobject> + </mediaobject> + </screenshot> + + The types of Paste operation are:</para> + + <variablelist> + + <varlistentry> + <term>Restricted</term> + <listitem> + <para>Requires an existing gap (containing nothing but + rests) of enough duration to completely contain the + clipboard's contents. The contents are pasted into + the gap. If there is no gap long enough, the paste + is not carried out. + </para> + <para> + This is the default paste type. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>Simple</term> + <listitem> + <para>Erases enough events to make a gap long enough to + paste into, and then pastes into that. The pasted + events therefore completely replace any existing ones + in the time covered by the paste. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>Open and Paste</term> + <listitem> + <para>The opposite of Cut and + Close. <!-- !!! define that --> Makes room for the paste by moving all of the + subsequent events further towards the end of the + composition. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>Note Overlay</term> + <listitem> + <para>Carries out a paste in the way that it would + happen if you entered each of the notes in the clipboard + yourself using the notation editor: if there are other + notes overlapping with them, the new or existing notes + will be split into ties appropriately. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>Matrix Overlay</term> + <listitem> + <para>Carries out a paste in the way that it would + happen if you entered each of the notes in the clipboard + yourself using the matrix editor: the notes presently + in the way of the paste will be ignored, allowing the new + notes to overlap arbitrarily with them. + </para> + </listitem> + </varlistentry> + + </variablelist> + + <para>All of these take effect at the current position of the + insert cursor on the current staff. To choose between the various + paste types, use the Paste... + menu option (with dots) on the Edit menu. + </para> + + </sect1> + + <sect1 id="nv-adjustments"> + <title>Adjusting Notation</title> + + + <sect2 id="nv-adjustments-note-rest-durations"> + <title>Adjusting note and rest durations</title> + + <sect3 id="nv-normalize-rests"> + <title>Normalizing rests</title> + + <para>Sometimes as a result of editing or quantization + operations, a piece of notation can end up with incorrect + rest durations for the current time signature. You can use + the <menuchoice><guimenu>Adjust</guimenu><guimenuitem>Rests</guimenuitem><guimenuitem>Normalize Rests</guimenuitem></menuchoice> function to + fix these. This examines each sequence of + consecutive rests found in the selection, and adjusts, + splits and merges rests as necessary to ensure that the + rests have theoretically correct durations and fall on the + correct boundaries. + </para> + + <para>For example, a 4/4 bar containing a crotchet + (quarter-note), then a minim (half-note) rest and a + crotchet rest will be rearranged to place the crotchet + rest first, as the minim rest should not cross the + central beat boundary of the bar. + </para> + </sect3> + + <sect3 id="nv-make-viable"> + <title>Splitting very long notes</title> <para>The + <menuchoice> <guimenu>Adjust</guimenu> + <guimenuitem>Notes</guimenuitem> <guimenuitem>Tie Notes at + Barlines</guimenuitem> </menuchoice> is intended to deal + with notes that have excessively long durations, and + therefore overflow barlines or are too long to be + displayed as a single note. It takes any such notes and + splits them into shorter, tied notes. + </para> + </sect3> + + <sect3 id="nv-de-counterpoint"> + <title>Splitting overlapping notes</title> + <para>The +<menuchoice> <guimenu>Adjust</guimenu> + <guimenuitem>Notes</guimenuitem> <guimenuitem>Split-and-Tie Overlapping Chords</guimenuitem> </menuchoice> function can be used to turn "counterpoint" notes into a series of split-and-tied notes and chords.</para> + + <para>It can be applied to a selection that contains + overlapping notes. It will split overlapping notes at the + point where they overlap, and tie together the resulting + split notes, ensuring that the music takes the form of a + series of chords and/or single notes starting and ending in + neat blocks, with some notes possibly tied. + </para> + </sect3> + + <sect3 id="nv-rescale"> + <title>Rescaling note durations</title> + <para>The + <menuchoice> <guimenu>Adjust</guimenu> + <guimenuitem>Rescale</guimenuitem> <guimenuitem>Halve + Durations</guimenuitem> </menuchoice> and + <menuchoice> <guimenu>Adjust</guimenu> + <guimenuitem>Rescale</guimenuitem> <guimenuitem>Double + Durations</guimenuitem> </menuchoice> functions can be + used to perform the most simple rescaling functions. + </para> + + <para>For more elaborate rescalings, use the + <menuchoice> <guimenu>Adjust</guimenu> + <guimenuitem>Rescale</guimenuitem> <guimenuitem>Stretch + or Squash...</guimenuitem> </menuchoice> function with + which you scale the total lenth of the selection. + </para> + </sect3> + +<!-- need a proper section for this and diatonic transpose + <varlistentry id="nv-transpose"> + <title>Transpose</title> + <para><action>Alters the pitch of the selected + notes.</action> This submenu contains basic + transposition functions which move the selected notes + up or down a semitone or a whole octave in pitch, as + well as a general transpose function that allows you + to choose how far up or down you want to transpose the + selection. + </para> + + <para>These functions simply change the stored pitches + of the notes in the selection, so that they both play + and appear at the new pitches. They do not deal with + performance transposition (displaying one pitch and + playing another), for which see the main window's + segment parameter box; nor do they help you with + transposing from one key into another, for which see + <link linkend="nv-signatures-key">Key + Signatures</link>. + </para> + </varlistentry> +--> + </sect2> + + <sect2> + <title id="nv-microposition">Repositioning notation elements</title> + <para> + You may occasionally wish to to nudge the positioning of some + element of notation that Rosegarden's layout algorithm has not + placed in an optimal location. Use Ctrl-click and drag to move slurs, hairpins, + text events, and several other sorts of events. You may not reposition notes in + this fashion. + </para> + </sect2> + + + + </sect1> + + <sect1 id="nv-interpret"> + <title>Interpreting Performance Cues in Notation</title> + <!-- !!! --> + <para> + You can use the Interpret function<menuchoice> + <guimenu>Adjust</guimenu><guimenuitem>Interpret...</guimenuitem> + </menuchoice> + to modify the velocities and timings of notes according to any + written or indicated dynamics found. The selection of + interpretations available is as follows: + + <variablelist> + <varlistentry> + <term>Apply text dynamics (p, mf, ff etc) + </term> + <listitem><para> Sets a velocity to each note + based on the last piece of text of "Dynamic" + type seen on the same staff (only texts of the + form pp, p, mp, mf, f, ff, fff, etc., are matched; these are + the texts that are available by default when entering text events + of this style). + </para></listitem> + </varlistentry> + + <varlistentry> + <term>Apply hairpin dynamics + </term> + <listitem><para> Makes the notes gradually + increase or decrease in velocity during a + crescendo or decrescendo hairpin. + </para></listitem> + </varlistentry> + + <varlistentry> + <term> + Stress beats + </term> + <listitem><para> Makes notes that land on bar or + beat boundaries slightly louder (greater + velocity) than the surrounding notes. + </para></listitem> + </varlistentry> + + <varlistentry> + <term> + Articulate slurs, staccato, tenuto etc + </term> + <listitem><para> Shortens unslurred notes, + shortens staccato notes more, and gives notes + inside slurs and tenuto notes their full length. + </para></listitem> + </varlistentry> + </variablelist> + + </para> + + </sect1> + + <!-- Quantization, smoothing, and display of quantized notes --> + + <sect1 id="nv-quantization"> + <title>Notation from performance data</title> + + <para> + &rosegarden; is a multi-purpose program: it is a notation + editor, but it is primarily a sequencer and editor for + performed music. And in performance, of course, the times + and durations of notes are rarely as precise as they are on + a printed score. + </para> + + <para> + This means that it's often desirable for &rosegarden; to do + a lot of tidying of the basic note times and durations when + attempting to make meaningful notes to show in the notation + editor. This is a kind of quantization, but a kind that + requires a surprising amount of guesswork to do well. + &rosegarden; includes a quantizer designed to do a slightly + better job of this than the plain grid quantizer. + </para> + + <para>Applying + quantization strictly for notation is rather unimaginatively + referred to as <quote>notation quantization</quote>: it only + applies to the notes you see and edit in notation, and + doesn't affect the notes that play, or that you edit in + other views such as the matrix. This quantization is + automatically applied to music imported or recorded from + MIDI, although not all of its possible capabilities are + enabled by default. + </para> + + <para> + There are two ways to see which notes have been quantized + for notation. By default, each notation view contains a <link + linkend="nv-raw-note-ruler">raw + note ruler</link> (in the group of rulers above the score) showing + a rectangular block for each note. This block is positioned + so as to represent the time and duration of the note as + performed, but with the top and bottom edges of the + rectangle extended or shortened to represent the time after + notation quantization. If this is too much information for + you, you can alternatively choose (in the configuration + dialog) to show in a green colour all note heads in the + score that have had their timings altered by notation + quantization. + </para> + + <para> + + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-notationquantizer.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>&rosegarden;'s notation quantize dialog</phrase> + </textobject> + </mediaobject> + </screenshot> + </para><para> + If the quantization &rosegarden; has used is not suitable, + either for the entire score or for a selection of notes, you + can choose to use a different level of quantization or none + at all. To apply a different quantization to some notes, + select the notes and use the Quantize... + menu function (tick the box labelled <quote>Quantize for + notation only</quote>). The quantization level or type used + by default can be changed in the configuration dialog. + </para> + + <sect2 id="nv-quantization-parameters"> + <title>Configurable parameters for the heuristic notation quantizer</title> + + <sect3 id="nv-quantization-parameters-during"> + <title>Parameters for quantization itself</title> + + <variablelist> + + <varlistentry> + <term>Complexity</term> + <listitem> + <para>The "complexity" of a notation quantizer is its + most fundamental parameter. A "complex" quantizer + will be more prepared to accept that complex-looking + music is in fact intended to be complex, whereas a + "simple" quantizer is more likely to assume that + complex-looking music results from an imprecise + performance of simple music. + </para> + <para>The default setting is intended to produce + reasonable results for a fairly wide range of music. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>Base grid unit</term> + <listitem> + <para>The base grid unit (set to a note duration + value) specifies the absolute minimum unit of note + that will be permitted to remain in the score after + quantization. For example, if set to a semiquaver, + all notes will be placed on boundaries of a multiple + of a semiquaver, with durations also a multiple of a + semiquaver. + </para> + <para>The setting of the base grid unit is not quite + as significant for a notation quantizer as it is for a + plain grid quantizer, because all it does is impose an + absolute limit on the level of precision permitted by + the complexity parameter. Mostly, when you find a + case in which increasing the grid unit produces better + results, you've actually found a case in which the + quantizer simply didn't do as good a job as it should + have been able to with the smaller unit. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>Tuplet level</term> + <listitem> + <para>The notation quantizer is capable of identifying + tuplets (triplets and other time-squashed groups), + within reasonable limits. This parameter controls how + ambitious it will attempt to be when looking for + tuplets, by setting a limit on how many notes per + tuplet group it will attempt to identify. If it is + set to <quote>None</quote>, the quantizer will not + attempt to identify tuplets at all. + </para> + </listitem> + </varlistentry> + + </variablelist> + + </sect3> + + <sect3 id="nv-quantization-parameters-after"> + <title>Parameters that control tidying up after quantization</title> + + <variablelist> + + <varlistentry> + <term>Re-beam</term> + <listitem> + <para> + Causes the notes to be re-beamed into groups + appropriately after quantization. This is usually + desirable. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>Add articulations (staccato, tenuto, + slurs)</term> + <listitem> + <para> + Causes the quantizer to attempt to identify, based + on the durations of individual and consecutive + notes, which notes should be notated with staccato + marks (for notes that fall significantly short of + the following note, but not apparently short + enough to merit a rest), tenuto (for notes that + almost or just overlap the following note) and + slurs (for series of notes that meet or overlap). + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>Tie notes at barlines etc</term> + <listitem> + <para>Causes any notes that are still found after + quantization to overlap barlines or to have + durations not exactly expressible with single note + heads to be split into multiple notes appropriately, + and tied. This has the same effect as applying the + <!-- !!! link --> "Tie Notes at Barlines" function + in the notation view. + </para> + <para> + This parameter is not set by default because it + changes the number of note events, which is + undesirable when using &rosegarden; partly or + principally as a MIDI sequencer. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>Split-and-tie overlapping chords</term> + <listitem> + <para> + Causes overlapping notes to be split and tied, so + as to make strict chords with individual noteheads + tied as necessary. This has the same effect as + applying the <!-- !!! link --> "Split-and-Tie + Overlapping Chords" function in the notation view. + </para> + <para> + This parameter is not set by default partly because + it changes the number of note events, which is + undesirable when using &rosegarden; partly or + principally as a MIDI sequencer. + </para> + </listitem> + </varlistentry> + </variablelist> + </sect3> + </sect2> + </sect1> + + <sect1 id="nv-ornaments"> + + <title>Playing ornaments</title> + + <para>Rosegarden supports playback of ornaments using its <link + linkend="triggered-segments">triggered segments</link> + mechanism. You can create triggered segments containing any of + the various types of trill or ornament you might want, and + associate them with the notes that want to play them.</para> + + <para>To create a new type of ornament, first write out the + notes "in longhand" that you want the ornament to play, and then + select the notes and use <menuchoice> + <guimenu>Note</guimenu><guimenuitem>Ornaments</guimenuitem><guimenuitem>Make + Ornament...</guimenuitem></menuchoice>. This cuts the notes to + the clipboard, pastes them into a new triggered segment, and + replaces them with a single note of the same duration that + triggers this segment.</para> + + <para>To make a note play an existing ornament, select it and + use <menuchoice> + <guimenu>Note</guimenu><guimenuitem>Ornaments</guimenuitem><guimenuitem>Trigger + Ornament...</guimenuitem></menuchoice>.</para> + + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-useornament.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>&rosegarden;'s Trigger Ornament dialog</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + + <para>To edit the notes played in a triggered ornament, you can + double-click on the note that triggers it. This will + change all uses of that ornament, not just the one that you + double-clicked on.</para> + + <para>Note that while Rosegarden can shift triggered segments up + and down in pitch to match their triggering notes, it is not + clever enough to perform transposition into a different + key or scale position.</para> + + <para>See <link linkend="triggered-segments">triggered + segments</link> for more details about ornaments and other uses + of triggered segments.</para> + </sect1> + + <sect1 id="nv-note-styles"> + <title>Note styles</title> + + <para> + &rosegarden; also allows you to change various aspects of the + way the various types of notes are drawn, such as the choice + of note heads, the number of tails, whether notes are filled + or unfilled and so on. + </para> + + <para> + A set of standard styles (Classical, Cross, Triangle and + Mensural) is provided, and you can change the style used for + individual notes by selecting them and then using the Note + Style menu options. Each note remembers which + style has been chosen for it, and this information is saved + as part of the composition. You can also change the default + style for new notes using the + <guimenuitem>Configure Rosegarden...</guimenuitem> option in the + <guimenu>Settings</guimenu> menu. + </para> + + <para> + It is also possible to create your own note styles by + describing them in <acronym>XML</acronym> files. (Even the + standard styles are defined this way: the only reason the + editor knows that a Classical semiquaver has a tilted oval + filled head, a stem, two flags, etc., is that the description + in Classical.xml says so.) See <link + linkend="developers-note-styles">Customising Rosegarden</link> + for more information. + </para> + </sect1> + + <sect1 id="nv-note-fonts"> + <title>Note fonts</title> + <para> + &rosegarden; is supplied with a single scalable notation + font, the Feta font developed by the LilyPond project. Feta + is an extremely high quality font that should be suitable + for nearly all classical work. + </para> + + <para>&rosegarden; also includes support as standard for a + number of other notation fonts. You will need to provide the + fonts themselves in TrueType (.ttf) or PostScript Type-1 + (.pfb, .pfa) format, and you will need the relevant + permissions to install them to the same place as &rosegarden; + was installed. To install a supported notation font, locate + the share directory for the &rosegarden; installation (usually + a subdirectory of the KDE desktop installation tree, such as + /opt/kde/share/apps/rosegarden). You will find that this + directory has a subdirectory called "fonts": copy the font + files into there, and restart &rosegarden;. If your font is + supported, it should now appear on the font menu in the + notation editor.</para> + + <para>Complete or partial support is currently provided for + the following fonts: Fughetta, by Blake Hodgetts; Petrucci, + the "original" Finale font; Maestro, the "new" Finale font; + Opus, the Sibelius font; Inkpen, the Sibelius jazz font; + Sonata from Adobe; Steinberg, from the Cubase sequencer; and + Xinfonia. (Most of the above font names are registered + trademarks of the respective companies.) THE ROSEGARDEN TEAM + MAKES NO REPRESENTATION AS TO THE LEGAL STATUS OF ANY USE OF + THESE FONTS WITH ROSEGARDEN. It is your responsibility to + ensure you are in compliance with the licence (if any) under + which a font was provided to you, before attempting to use it. + If you are not sure whether you have the right to use a font, + don't: apart from anything else, the standard Feta font is + better than most of these anyway.</para> + + <para>It is also possible to provide new mapping files so as + to use new fonts. For some fonts that have similar mappings + or metrics to fonts in the above list, this may be as simple + as editing the name of the font in the mapping file. See + <link linkend="developers-note-fonts">Customising Rosegarden</link> + for more information. + + </para> + </sect1> + </chapter> + + <chapter id="event-view"> + <title>The Event List editor</title> + <sect1 id="ev-introduction"> + <title>Introduction</title> + + <para> + + The &rosegarden; Event List editor shows the events in a + single segment in a raw form, and enables you to edit the + precise properties of those events individually. + + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-eventlisteditor.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>&rosegarden;'s event list editor</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + </sect1> + </chapter> + + + + + <!-- + ********************************** + + PART III: + Technical material + + ********************************** + --> + + <chapter id="developers"> + <title>Customising Rosegarden</title> + + <sect1 id="developers-note-fonts"> + <title>Configuring custom notation fonts</title> + + <para>If you have a notation font installed on your system in a + scalable format (TrueType or Type-1) but it is not currently + supported by Rosegarden, you can create your own mapping XML + file to describe the font's character map and metrics in a way + Rosegarden can use. These files are installed in the + fonts/mappings subdirectory of the Rosegarden installation + directory, and a number of samples are included with the + distribution.</para> + + <para>You can also use these mapping files to define new + pixmap-based fonts, in which every shape in a particular size is + loaded from a separate pixmap file. The two standard notation + fonts supplied with Rosegarden are pixmap fonts defined in + exactly this way. + </para> + + <para>It is even possible to define a notation font as using one + or more scalable system fonts, augmented with pixmaps for + particular sizes or for characters not found in the scalable + fonts. This is because most of the mapping file format is the + same for scalable and pixmap fonts, and where there are + different elements for the different sorts of fonts, it is + usually possible to include both of them. Rosegarden will + usually use pixmaps where available and scalable fonts + otherwise. + </para> + + <para>You may also wish to edit the mapping files supplied with + Rosegarden if you find their measurements for alignment or + sizing are not to your liking. (If you believe that any of the + supplied files are actually wrong, please let us know.) + </para> + + <sect2 id="developers-note-fonts-codes-glyphs"> + <title>Codes and Glyphs</title> + + <para></para> + </sect2> + + <sect2 id="developers-note-fonts-mapping-format"> + <title>Notation font mapping XML format</title> + + <para>Here is a summary of the XML elements that may be used + in the font mapping file.</para> + + <sect3 id="developers-note-fonts-mapping-format-font-encoding"> + <title>rosegarden-font-encoding</title> + + <para>This element must exist in every mapping file, and + should contain all the other elements. The only attribute + is "name", which contains the font's name as shown in the + font selection dropdown. Although the file format will + permit any name to be used here, Rosegarden will only pick + up the font corectly if the XML file has the same name as + the contents of this attribute (except that the XML file + should be named in lower-case and should end in ".xml"). + </para> + </sect3> + + <sect3 id="developers-note-fonts-mapping-format-font-information"> + <title>font-information</title> + + <para>This should normally be the first child element of + "rosegarden-font-encoding". It may have any of the + following attributes, all of which are optional: + + <variablelist> + <varlistentry> + <term>origin</term> + <listitem> + <para>A textual description of the likely origin of + the mapped font (not the origin of the mapping + file).</para> + </listitem> + </varlistentry> + + <varlistentry> + <term>copyright</term> + <listitem> + <para>A textual description of the likely copyright + status of the mapped font (not the copyright status + of the mapping file). Note that because the mapping + file contains information such as origin and + copyright of the font itself, it is usually + advisable to make separate mapping files for + separate fonts where practical, even if the fonts + share other mapping data.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term>mapped-by</term> + <listitem> + <para>The name of the creator of the mapping file + (i.e. you, presumably).</para> + </listitem> + </varlistentry> + + <varlistentry> + <term>type</term> + <listitem> + <para>The type of the font. This attribute should + contain one of the values "pixmap" or "scalable". + Fonts that are loaded into the windowing system and + are available to Rosegarden as standard system fonts + have type "scalable"; fonts that need to be loaded + from pixmap files corresponding to individual sizes + of pixmap (such as the feta and rg21 fonts included + with Rosegarden) have type "pixmap".</para> + + <para>This information is only intended for the user + reference; it isn't actually used by Rosegarden. It is + legitimate in practice for a font to be a mixture of the + two, but in general we will assume in this documentation + that a font is either scalable or pixmap.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term>smooth</term> + <listitem> + <para>A boolean attribute indicating whether the + font is antialiased (smooth) or not. Should have + the value "true" or "false". If the font is smooth, + other display elements such as beams and slurs that + are not generated from the font will also be + antialiased.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term>autocrop</term> + <listitem> + <para>Only relevant for scalable (system) fonts. + Rosegarden usually expects the metrics for a font to + contain the vertically smallest bounding boxes for + elements such as note heads and accents, rather than + including empty space above or below these elements + for alignment purposes. Most fonts do not do what + Rosegarden expects. Therefore for these fonts you + should set the autocrop attribute to "true"; then + Rosegarden will crop any unnecessary space from the + top and bottom of these elements when rendering + them.</para> + </listitem> + </varlistentry> + + </variablelist> + + </para> + </sect3> + + <sect3 id="developers-note-fonts-mapping-format-font-requirements"> + <title>font-requirements</title> + <para> + This element is only relevant for scalable fonts. It is + used to specify that this font should only be offered if + certain system fonts are available, as well as to + associate IDs with those system fonts to refer to in the + <link + linkend="developers-note-fonts-mapping-format-font-symbol-map">font-symbol-map</link> + element. This scheme is used to decide which notation + fonts should be offered to the user, and also allows you + to compose a Rosegarden notation font from more than one + system font if desired. + </para> + <para>The "font-requirements" element should contain a list + of "font-requirement" child elements. Each of these has two + attributes: "font-id", containing a numerical ID of your + choice for reference elsewhere in the file, and either a + "name" or a "names" attribute. If "name" is provided, it + will be used as the name of a single system font to be + associated with the font id; if "names" is provided, it will + be treated as a comma-separated list of system fonts and the + first one found will be associated with the font id. + </para> + </sect3> + + <sect3 id="developers-note-fonts-mapping-format-font-sizes"> + <title>font-sizes</title> + + <para>The "font-sizes" element specifies which notation font + sizes are available, and how the nominal font size relates + to the dimensions of non-font elements such as stems, staff + lines and beams. The "size" of a notation font is assumed + to be the distance in pixels between staff lines, or more + precisely, the height of a conventional note head that + completely fills the space between lines: the size therefore + does not include the thickness of either of the neighbouring + staff lines. + </para> + + <para> + <!-- !!! TODO throughout this section: how to mark up XML element/attribute names? equiv of <code> in HTML would do --> + There are two possible child elements of "font-sizes": + "font-scale" and "font-size". Their use depends on the + type of font being described.</para> + + <para> + For pixmap (non-scalable) fonts, the "font-sizes" element + should contain a list of "font-size" elements, one for + each size of pixmaps available. The pixmaps themselves + must be installed in the + fonts/<font-name>/<font-size> subdirectory of + the Rosegarden installation directory, where + <font-name> is the name of the font (as specified in + the "rosegarden-font-encoding" element at the start of the + mapping file), or a lower-case version of the name, and + <font-size> is the pixel size of the font. A font + size will only be made available to the user if it has an + entry in the "font-sizes" list and the pixmap directory is + found. + </para> + + <para> + For scalable fonts, the "font-sizes" element should + contain one "font-scale" element that defines the + relationships between font and non-font elements in a + general way, and also defines the relationship between + Rosegarden's nominal font size and the size of the + corresponding system font. If this "font-scale" element + is found, then Rosegarden will assume the font is + available in any size. You can however still include one + or more "font-size" elements to define precise proportions + for any particular size for which the general proportions + do not quite work correctly, for example because of + rounding error. + </para> + + <para> + The attributes of "font-scale" and "font-size" are very + similar. The main difference is that all attributes of + "font-scale" are floating-point values relative to the + font size, where 1.0 is the base font size (i.e. the + distance between staff lines), whereas attributes of + "font-size" are integer pixel values. The attributes + available are as follows. (Those marked "optional" have + vaguely sensible defaults, so it's a good idea to try not + setting them first.) + </para> + + <variablelist> + + <varlistentry> + <term>note-height</term> + <listitem> + <para>This attribute is only available for the + "font-size" element, and it is mandatory in that + element. It defines the base size of font to which the + other attributes in this element apply, and a size that + will be offered to the user and used when looking up + pixmaps for this font.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term>font-height</term> + <listitem> + <para>May be used in either "font-size" or "font-scale". + This is only relevant for scalable fonts, but is + mandatory for them if used in the "font-scale" element. + This defines the size of the system font used to draw a + given size of notation font.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term>beam-thickness</term> + <listitem> + <para>Optional. Defines the thickness of a beam.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term>staff-line-thickness</term> + <listitem> + <para>Optional. Defines the thickness of a staff line.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term>stem-thickness</term> + <listitem> + <para>Optional. Defines the thickness of a note stem.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term>flag-spacing</term> + <listitem> + <para>Optional. Defines the gap between note flags in + cases where multiple flags are drawn by drawing a single + flag several times.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term>border-x</term> + <listitem> + <para>Optional. Specifies that the note head pixmaps + have a fixed area to left and right that should not be + considered part of the note head. This attribute gives + the thickness of that area.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term>border-y</term> + <listitem> + <para>Optional. Specifies that the note head pixmaps + have a fixed area to top and bottom that should not be + considered part of the note head. This attribute gives + the thickness of that area.</para> + </listitem> + </varlistentry> + + </variablelist> + </sect3> + + <sect3 id="developers-note-fonts-mapping-format-font-symbol-map"> + <title>font-symbol-map</title> + <para> + This element lists the symbols available in this notation + font, and which pixmap files or system font code points + they should be drawn from.</para> + + <para>It should contain a list of "symbol" elements. These + have several possible attributes, the choice of which will + normally depend on whether the font is based on pixmaps or + system fonts: + </para> + + <variablelist> + <varlistentry> + <term>name</term> + <listitem> + <para>Mandatory. This attribute should contain the + name of the notation symbol. If the symbol exists in + the <ulink + url="http://www.unicode.org/charts/PDF/U1D100.pdf">Unicode + 3.2 standard</ulink>, the name should be that used to + identify the symbol in the standard.</para> + + <para>Most of the symbols Rosegarden expects to find + are in the standard; one exception is that many fonts + have a special version of the flag symbol that is + intended to be used when composing multiple flags from + individual single flags. Rosegarden refers to this as + "MUSICAL SYMBOL COMBINING FLAG-0", a name not used in + the Unicode standard (which has flags 1-5 only).</para> + + <para>For a definitive set of the symbol names + Rosegarden knows about, see the file + "gui/notecharname.cpp" in the Rosegarden source + distribution. Note however that it is possible to use + additional symbol names by introducing them in a <link + linkend="developers-note-styles">notation + style</link>. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>src</term> + <listitem> + <para>The name of the pixmap file from which this + symbol should be loaded, without a directory or + extension. This is the usual way of describing a + symbol in a pixmap font. The file itself should be + installed to + fonts/<font-name>/<font-size>/<src>.xpm + under the Rosegarden installation directory. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>inversion-src</term> + <listitem> + <para>The name of a pixmap file from which an inverted + version of this symbol may be loaded, without a + directory or extension. If this attribute is absent + and an inverted version of the symbol is required, it + will be generated simply by loading the normal version + and reflecting it in a central x-axis. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>code</term> + <listitem> + <para>The code point at which this symbol may be found + in the relevant system font, as a decimal integer. + This is a way of describing a symbol in a scalable + font. This attribute will only be referred to if no + pixmap file is supplied, or if the pixmap file fails + to load. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>inversion-code</term> + <listitem> + <para>The code point at which an inverted version of + this symbol may be found in the relevant system font. + If this attribute is absent and an inverted version of + the symbol is required, it will be generated simply by + loading the normal version and reflecting it in a + central x-axis. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>glyph</term> + <listitem> + <para>The raw glyph index at which this symbol may be found + in the relevant system font, as a decimal integer. + This is a way of describing a symbol in a scalable + font. This attribute will only be referred to if no + pixmap file is supplied, or if the pixmap file fails + to load. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>inversion-glyph</term> + <listitem> + <para>The raw glyph index at which an inverted version of + this symbol may be found in the relevant system font. + If this attribute is absent and an inverted version of + the symbol is required, it will be generated simply by + loading the normal version and reflecting it in a + central x-axis. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>font-id</term> + <listitem> + <para>The id of the system font from which this symbol + should be loaded, as defined in the <link + linkend="developers-note-fonts-mapping-format-font-requirements">font-requirements</link> + element. The default is 0. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>codebase</term> + <listitem> + <para>This (decimal integer) attribute may be of use + if many of the symbols in a scalable font cover a + short range of code points starting at a relatively + high code page. If supplied, the codebase value will + be added to each of the subsequent code and + inversion-code values when looking up a symbol. + </para> + </listitem> + </varlistentry> + + </variablelist> + + <para> + Although none of these attributes is mandatory except for + the name, a symbol obviously needs to supply at least one + of "src", "inversion-src", "code", "inversion-code", + "glyph", or "inversion-glyph" to stand any chance of being + rendered at all. It is of course perfectly legitimate to + supply several or all of these attributes. + </para> + + </sect3> + + <sect3 id="developers-note-fonts-mapping-format-font-hotspots"> + <title>font-hotspots</title> + <para> + </para> + </sect3> + + </sect2> + + </sect1> + + <sect1 id="developers-note-styles"> + <title>Creating new notation styles</title> + + <para> + Rosegarden's notation editor has the ability to display and + edit notes in various standard styles: classical, diamond + heads and so on. These styles are all defined in XML style + definition files installed along with the application, and + it's possible to create a new one by writing a simple XML + file. Rosegarden simply looks at the set of installed files + to determine which styles to offer the user. You can refer to + the default set of files in the styles subdirectory of the + Rosegarden installation directory for examples. + </para> + + <para> + The file format is not yet especially comprehensive; at the + moment it has been designed to be powerful enough to describe + the standard styles that come with Rosegarden, but not much + more. If you should try to create new styles this way, we'd + be very interested in your feedback on the Rosegarden + mailing-lists. + </para> + + <sect2 id="developers-note-styles-format"> + <title>Notation style XML format</title> + + <para> + Here is a summary of the XML elements that may be used in + a style definition file. + </para> + + <sect3 id="developers-note-styles-note-style"> + <title>rosegarden-note-style</title> + + <para>This element must exist in every style file, and + should contain all the other elements. It has one optional + attribute, "base-style", which may be used to name a style + from which this style takes the default values for any + parameters not specified elsewhere in the present file. + It's often good practice to define a style in terms of the + minimal difference from a given base style: see the supplied + Cross.xml for a particularly simple example. + </para> + + <para>Note that the "rosegarden-note-style" element does not + give the name of the style being defined, which is instead + currently drawn from the name of the file. At some point in + the future we may add internationalizable style name + attributes to this element.</para> + </sect3> + + <sect3 id="developers-note-styles-global-note"> + <title>global, note</title> + + <para>Within the "rosegarden-note-style" element, there may + be one "global" element and any number of "note" elements. + We describe these together, as they have almost identical + sets of attributes. The "global" element simply provides + default values for those parameters not specified for a + particular note type in any following "note" element. + </para> + + <para>The attributes for these elements are as follows. All + of these are optional except as described:</para> + + <variablelist> + + <varlistentry> + <term>type</term> + <listitem> + <para>Only relevant to the "note" element, and + mandatory for that element. This attribute specifies + which sort of note is being styled. Legal values are + textual American or British note names (from "64th", + "sixth-fourth note", "hemidemisemiquaver" etc to + "double whole note"). + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>shape</term> + <listitem> + <para>Defines a note head shape for this style. Any + string is a legal value, but the only values + implemented so far are "angled oval", "level oval", + "breve", "cross", "triangle up", "triangle down", + "diamond" and "rectangle". The value "number" is also + recognised but not yet implemented. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>charname</term> + <listitem> + <para>Defines a note font character name to be used as + the note head for this style. An element may supply a + "shape" or "charname" attribute, but not both. The + name should be one of those defined in the current + notation font's <link + linkend="developers-note-fonts-mapping-format-font-symbol-map">symbol + map</link> (in a "name" attribute). + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>filled</term> + <listitem> + <para>Specifies whether this note should have a filled + head (where applicable, i.e. where the shape attribute + supplies a shape that is available both filled and + unfilled). Must be "true" or "false". + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>stem</term> + <listitem> + <para>Specifies whether this note should have a stem. + Must be "true" or "false". + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>flags</term> + <listitem> + <para>Defines how many flags or beams this note should + have. The valid range is 0 to 4. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>slashes</term> + <listitem> + <para>Defines how many slashes this note should have + across its stem. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>hfixpoint</term> + <listitem> + <para>Specifies in which x position the stem fixes to + the note head. Acceptable values are "normal" (the + right side when the stem points up, the left when it + points down), "central", and "reversed" (left side + when the stem points up, right when it points down). + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>vfixpoint</term> + <listitem> + <para>Specifies in which y position the stem fixes to + the note head. Acceptable values are "near" (the stem + fixes to the top when pointing up, the bottom when + pointing down), "middle", or "far". + </para> + </listitem> + </varlistentry> + + </variablelist> + </sect3> + </sect2> + </sect1> + + + <!-- (OPTIONAL) A Programming/Scripting reference chapter should be + used for apps that use plugins or that provide their own scripting hooks + and/or development libraries. --> + + <!-- cc: I think we should document the DCOP API here, but I don't + think we should include extensive developer docs, although we should + point to where they can be found in the source tree or online. --> + <!-- + <para> + Programming <application>Rosegarden</application> plugins is + a joy to behold. Just read through the next + 66 pages of <acronym>API</acronym>'s to learn how! + </para> + --> + <!-- Use refentries to describe APIs. Refentries are fairly + complicated and you should consult the docbook reference for + further details. The example below was taken from that reference + and shortened a bit for readability. --> + <!-- + <refentry id="re-1007-unmanagechildren-1"> + <refmeta> + <refentrytitle>XtUnmanageChildren</refentrytitle> + <refmiscinfo>Xt – Geometry Management</refmiscinfo> + </refmeta> + <refnamediv> + <refname>XtUnmanageChildren + </refname> + <refpurpose>remove a list of children from a parent widget's managed list. + </refpurpose> + </refnamediv> + <refsynopsisdiv> + <refsynopsisdivinfo> + <date>4 March 1996</date> + </refsynopsisdivinfo> + <synopsis> + void XtUnmanageChildren(<replaceable>children</replaceable>, <replaceable>num_children</replaceable>) + WidgetList <replaceable>children</replaceable>; + Cardinal <replaceable>num_children</replaceable>; + </synopsis> + + <refsect2 id="r2-1007-unmanagechildren-1"> + <title>Inputs</title> + <variablelist> + <varlistentry> + <term><replaceable>children</replaceable> + </term> + <listitem> + <para> + Specifies an array of child widgets. Each child must be of + class RectObj or any subclass thereof. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term><replaceable>num_children</replaceable> + </term> + <listitem> + <para>Specifies the number of elements in <replaceable>children</replaceable>. + </para> + </listitem> + </varlistentry> + </variablelist> + </refsect2></refsynopsisdiv> + + <refsect1 id="r1-1007-unmanagechildren-1"> + <title>Description + </title> + <para> + <function>XtUnmanageChildren()</function> unmaps the specified widgets + and removes them from their parent's geometry management. + The widgets will disappear from the screen, and (depending + on its parent) may no longer have screen space allocated for + them. + </para> + <para>Each of the widgets in the <replaceable>children</replaceable> array must have + the same parent. + </para> + <para>See the “Algorithm” section below for full details of the + widget unmanagement procedure. + </para> + </refsect1> + + <refsect1 id="r1-1007-unmanagechildren-2"> + <title>Usage</title> + <para> + Unmanaging widgets is the usual method for temporarily + making them invisible. They can be re-managed with + <function>XtManageChildren()</function>. + </para> + <para> + You can unmap a widget, but leave it under geometry + management by calling <function>XtUnmapWidget()</function>. You can + destroy a widget's window without destroying the widget by + calling <function>XtUnrealizeWidget()</function>. You can destroy a + widget completely with <function>XtDestroyWidget()</function>. + </para> + <para> + If you are only going to unmanage a single widget, it is + more convenient to call <function>XtUnmanageChild()</function>. It is + often more convenient to call <function>XtUnmanageChild()</function> + several times than it is to declare and initialize an array + of widgets to pass to <function>XtUnmanageChildren()</function>. Calling + <function>XtUnmanageChildren()</function> is more efficient, however, + because it only calls the parent's <function>change_managed()</function> + method once. + </para> + </refsect1> + + <refsect1 id="r1-1007-unmanagechildren-3"> + <title>Algorithm + </title> + <para><function>XtUnmanageChildren()</function> performs the following: + </para> + <variablelist> + <varlistentry> + <term>- + </term> + <listitem> + <para>Ignores the child if it already is unmanaged or is being + destroyed. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>- + </term> + <listitem> + <para>Otherwise, if the child is realized, it makes it nonvisible + by unmapping it. + </para> + </listitem> + </varlistentry> + </variablelist> + <para> + </para> + </refsect1> + + <refsect1 id="r1-1007-unmanagechildren-4"> + <title>Structures</title> + <para> + The <type>WidgetList</type> type is simply an array of widgets: + </para> + <screen id="sc-1007-unmanagechildren-1"> + typedef Widget *WidgetList; + </screen> + </refsect1> + </refentry> + --> + </chapter> + + + <chapter id="credits"> + + <title>Credits and License</title> + + <para> + <application>Rosegarden</application> + </para> + <para> + <itemizedlist> + <listitem> + <para> + + Rosegarden is Copyright 2000-2008 Guillaume Laurent, + Chris Cannam and Richard Bown. The moral rights of + Guillaume Laurent, Chris Cannam and Richard Bown to be + identified as the authors of this work have been asserted. + + </para> + </listitem> + + <listitem> + <para> + + Parts of Rosegarden are derived from X11 Rosegarden 2.1, + which is Copyright 1994 – 2001 Chris Cannam, Andrew Green, + Richard Bown and Guillaume Laurent. + + </para> + </listitem> + + <listitem> + <para> + + For musical notation display Rosegarden uses pixmaps + derived from the Feta font, part of the <ulink + url="http://lilypond.org/">LilyPond</ulink> software, + which is Copyright 1997 – 2001 Jan Nieuwenhuizen and + Han-Wen Nienhuys. + + </para> + </listitem> + + <listitem> + <para> + + Other major contributors include Randall Farmer, Ron + Kuris, Hans Kieserman, Michael McIntyre, and Pedro + Lopez-Cabanillas. + + </para> + </listitem> + + <listitem> + <para> + + The Rosegarden splash-screen image is Copyright 2006 Carolyn H. McIntyre, + used by permission. + + </para> + </listitem> + + </itemizedlist> + </para> + + <para> + Documentation copyright 2002-2006 Chris Cannam, Richard Bown, Guillaume Laurent + </para> + <!-- + <para> + Translations done by: + <itemizedlist> + <listitem> + <para>Babel D. Fish <email>babelfish@kde.org</email> (Sanskrit)</para> + </listitem> + </itemizedlist> + </para> + --> + <!-- For URL links to common stuff like the one below, + always use paths like "common/gpl-licence". + In this path, "common" will be a symbolic link built at "make install" time. + This link will normally point to $KDEDIR/share/doc/HTML/en/common, + where "en" should be replaced with the current language. --> + + <para> + This program is licensed under the terms of the + <ulink url="common/gpl-license.html">GNU General Public License</ulink>. + </para> + </chapter> + + <!-- Note that the revhistory tags apply to the documentation + version and not to the app version. That is why we use an + ItemizedList instead for this list of revisions to the app. --> + + <chapter id="rosegarden-revhistory"> + <title>Rosegarden Revision History</title> + <para> + <itemizedlist> + <listitem><para> + 1.7.0 – May 2008: notation track headers, nested brackets in + LilyPond export, grace notes finally functional, quick playback + position marker, ties can be flipped, variable-height tracks allow + access to all previously overlapping segments, take track + transpose into account while recording, convert existing segments + when loading an instrument preset, etc., bug fixes galore + </para></listitem> + <listitem><para> + 1.6.0 – November 2007: fretboards, diatonic transpose, multiple lines of lyrics, marker ruler improvements, overlapping notes visibility, LilyPond export enhancements and new dialog, better infrared remote control support, better configuration dialog, fixes + </para></listitem> + <listitem><para> + 1.5.1 – March 2007: bug fixes + </para></listitem> + <listitem><para> + 1.5 – February 2007: audio timestretching and input format conversion, matrix usability improvements, tempo tapping, context help, some features, code reorganisation and new build system (again) + </para></listitem> + <listitem><para> + 1.4 – September 2006: LilyPond export vastly improved, + exportable LilyPond directives, cut/copy/paste by ranges that + include tempo and time data, tempo entry and manipulation vastly + improved, multi-track MIDI recording, MIDI recording filters, + track paramter box, create segments using preset parameters from + a database of over 300 real-world instruments, texts like + "Allegro" offered as a parallel alternative to typing, LilyPond + preview, assorted smaller features, many bug fixes + </para></listitem> + <listitem><para> + 1.2.4 – July 2006: bug fixes + </para></listitem> + <listitem><para> + 1.2.3 – February 2006: new segment canvas, percussion matrix, multi-track audio recording, project packager, external MIDI controllers, MTC sync, proper ALSA MIDI ports, new icons, new build system + </para></listitem> + <listitem><para> + 1.0 – February 2005: many fixes, DSSI effects, latency compensation + </para></listitem> + <listitem><para> + 0.9.9 – July 2004: plugin synths, triggered segments, notation improvements + </para></listitem> + <listitem><para> + 0.9.8 – May 2004: better audio subsystem + </para></listitem> + <listitem><para> + 0.9.7 – February 2004: + </para></listitem> + <listitem><para> + 0.9.6 – December 2003: bug fixes + </para></listitem> + <listitem><para> + 0.9.5 – November 2003: a great lot of stuff + </para></listitem> + <listitem><para> + 0.9.1 – May 2003: step recording, Mup export, many many bug fixes + </para></listitem> + <listitem><para> + 0.9 – April 2003: many notation improvements, improved bank editor, audio enhancements and refinements, translations + </para></listitem> + <listitem><para> + 0.8.5 – December 2002: bank editor, MIDI filters, panic button + </para></listitem> + <listitem><para> + 0.8 – October 2002: printing, LADSPA plugins, improved Matrix View + </para></listitem> + <listitem><para> + 0.2.0 – August 2002: WAV file support, sweep selections, contrapuntal staves + </para></listitem> + <listitem><para> + 0.1.6 – June 2002: configuration dialog, LilyPond support, quantize dialog + </para></listitem> + <listitem><para> + 0.1.5 – May 2002: KDE 3, ALSA support, JACK audio support + </para></listitem> + <listitem><para> + 0.1.4 – March 2002: more undo, segment editing, audio playback + </para></listitem> + <listitem><para> + 0.1.3 – January 2002: piano-roll/matrix view, &MIDI; recording + </para></listitem> + <listitem><para> + 0.1.2 – November 2001: notation undo, transport dialog, position pointer + </para></listitem> + <listitem><para> + 0.1.1 – October 2001: scalable notation + </para></listitem> + <listitem><para> + 0.1 – June 2001: first public release of Rosegarden-4 + </para></listitem> + </itemizedlist> + </para> + </chapter> + + &documentation.index; +</book> diff --git a/doc/en/rg-audiofilemanager.png b/doc/en/rg-audiofilemanager.png Binary files differnew file mode 100644 index 0000000..f6a0e47 --- /dev/null +++ b/doc/en/rg-audiofilemanager.png diff --git a/doc/en/rg-audiomixer.png b/doc/en/rg-audiomixer.png Binary files differnew file mode 100644 index 0000000..ebb2968 --- /dev/null +++ b/doc/en/rg-audiomixer.png diff --git a/doc/en/rg-bankeditor.png b/doc/en/rg-bankeditor.png Binary files differnew file mode 100644 index 0000000..8e4d2d0 --- /dev/null +++ b/doc/en/rg-bankeditor.png diff --git a/doc/en/rg-button-bar-time.png b/doc/en/rg-button-bar-time.png Binary files differnew file mode 100644 index 0000000..214dbe6 --- /dev/null +++ b/doc/en/rg-button-bar-time.png diff --git a/doc/en/rg-button-from-end.png b/doc/en/rg-button-from-end.png Binary files differnew file mode 100644 index 0000000..1f69092 --- /dev/null +++ b/doc/en/rg-button-from-end.png diff --git a/doc/en/rg-clefdialog.png b/doc/en/rg-clefdialog.png Binary files differnew file mode 100644 index 0000000..ae408ce --- /dev/null +++ b/doc/en/rg-clefdialog.png diff --git a/doc/en/rg-coda.png b/doc/en/rg-coda.png Binary files differnew file mode 100644 index 0000000..e34f2b0 --- /dev/null +++ b/doc/en/rg-coda.png diff --git a/doc/en/rg-colours.png b/doc/en/rg-colours.png Binary files differnew file mode 100644 index 0000000..4054931 --- /dev/null +++ b/doc/en/rg-colours.png diff --git a/doc/en/rg-cursors.png b/doc/en/rg-cursors.png Binary files differnew file mode 100644 index 0000000..dbe11ea --- /dev/null +++ b/doc/en/rg-cursors.png diff --git a/doc/en/rg-devicemanager.png b/doc/en/rg-devicemanager.png Binary files differnew file mode 100644 index 0000000..035ad68 --- /dev/null +++ b/doc/en/rg-devicemanager.png diff --git a/doc/en/rg-eraser.png b/doc/en/rg-eraser.png Binary files differnew file mode 100644 index 0000000..3377546 --- /dev/null +++ b/doc/en/rg-eraser.png diff --git a/doc/en/rg-eventfilter.png b/doc/en/rg-eventfilter.png Binary files differnew file mode 100644 index 0000000..91738d0 --- /dev/null +++ b/doc/en/rg-eventfilter.png diff --git a/doc/en/rg-eventlisteditor.png b/doc/en/rg-eventlisteditor.png Binary files differnew file mode 100644 index 0000000..8f53694 --- /dev/null +++ b/doc/en/rg-eventlisteditor.png diff --git a/doc/en/rg-gridquantizer.png b/doc/en/rg-gridquantizer.png Binary files differnew file mode 100644 index 0000000..7671eb7 --- /dev/null +++ b/doc/en/rg-gridquantizer.png diff --git a/doc/en/rg-guitarchorddialog.png b/doc/en/rg-guitarchorddialog.png Binary files differnew file mode 100644 index 0000000..8ec07f9 --- /dev/null +++ b/doc/en/rg-guitarchorddialog.png diff --git a/doc/en/rg-guitarchordeditordialog.png b/doc/en/rg-guitarchordeditordialog.png Binary files differnew file mode 100644 index 0000000..8bcb04a --- /dev/null +++ b/doc/en/rg-guitarchordeditordialog.png diff --git a/doc/en/rg-ipb-audio.png b/doc/en/rg-ipb-audio.png Binary files differnew file mode 100644 index 0000000..34b0f6d --- /dev/null +++ b/doc/en/rg-ipb-audio.png diff --git a/doc/en/rg-ipb-midi.png b/doc/en/rg-ipb-midi.png Binary files differnew file mode 100644 index 0000000..8230321 --- /dev/null +++ b/doc/en/rg-ipb-midi.png diff --git a/doc/en/rg-ipb-synth.png b/doc/en/rg-ipb-synth.png Binary files differnew file mode 100644 index 0000000..b3df553 --- /dev/null +++ b/doc/en/rg-ipb-synth.png diff --git a/doc/en/rg-keysigdialog.png b/doc/en/rg-keysigdialog.png Binary files differnew file mode 100644 index 0000000..463c956 --- /dev/null +++ b/doc/en/rg-keysigdialog.png diff --git a/doc/en/rg-loadpreset.png b/doc/en/rg-loadpreset.png Binary files differnew file mode 100644 index 0000000..f1bdf65 --- /dev/null +++ b/doc/en/rg-loadpreset.png diff --git a/doc/en/rg-mainwindow.png b/doc/en/rg-mainwindow.png Binary files differnew file mode 100644 index 0000000..70769fc --- /dev/null +++ b/doc/en/rg-mainwindow.png diff --git a/doc/en/rg-markerloop.png b/doc/en/rg-markerloop.png Binary files differnew file mode 100644 index 0000000..8d76cd2 --- /dev/null +++ b/doc/en/rg-markerloop.png diff --git a/doc/en/rg-matrixview.png b/doc/en/rg-matrixview.png Binary files differnew file mode 100644 index 0000000..1e88e4b --- /dev/null +++ b/doc/en/rg-matrixview.png diff --git a/doc/en/rg-metronome.png b/doc/en/rg-metronome.png Binary files differnew file mode 100644 index 0000000..6ed2065 --- /dev/null +++ b/doc/en/rg-metronome.png diff --git a/doc/en/rg-midifilter.png b/doc/en/rg-midifilter.png Binary files differnew file mode 100644 index 0000000..f58891f --- /dev/null +++ b/doc/en/rg-midifilter.png diff --git a/doc/en/rg-midimixer.png b/doc/en/rg-midimixer.png Binary files differnew file mode 100644 index 0000000..ca3e27f --- /dev/null +++ b/doc/en/rg-midimixer.png diff --git a/doc/en/rg-move.png b/doc/en/rg-move.png Binary files differnew file mode 100644 index 0000000..b99d3e4 --- /dev/null +++ b/doc/en/rg-move.png diff --git a/doc/en/rg-notation-toolbars.png b/doc/en/rg-notation-toolbars.png Binary files differnew file mode 100644 index 0000000..e4c8807 --- /dev/null +++ b/doc/en/rg-notation-toolbars.png diff --git a/doc/en/rg-notationquantizer.png b/doc/en/rg-notationquantizer.png Binary files differnew file mode 100644 index 0000000..92e3016 --- /dev/null +++ b/doc/en/rg-notationquantizer.png diff --git a/doc/en/rg-notationtools.png b/doc/en/rg-notationtools.png Binary files differnew file mode 100644 index 0000000..5cb9add --- /dev/null +++ b/doc/en/rg-notationtools.png diff --git a/doc/en/rg-notationview-multipage.png b/doc/en/rg-notationview-multipage.png Binary files differnew file mode 100644 index 0000000..0ee2ed2 --- /dev/null +++ b/doc/en/rg-notationview-multipage.png diff --git a/doc/en/rg-notationview.png b/doc/en/rg-notationview.png Binary files differnew file mode 100644 index 0000000..7728430 --- /dev/null +++ b/doc/en/rg-notationview.png diff --git a/doc/en/rg-pastedialog.png b/doc/en/rg-pastedialog.png Binary files differnew file mode 100644 index 0000000..0961b4f --- /dev/null +++ b/doc/en/rg-pastedialog.png diff --git a/doc/en/rg-pencil.png b/doc/en/rg-pencil.png Binary files differnew file mode 100644 index 0000000..8e2f895 --- /dev/null +++ b/doc/en/rg-pencil.png diff --git a/doc/en/rg-percussionmatrix.png b/doc/en/rg-percussionmatrix.png Binary files differnew file mode 100644 index 0000000..6ceba5e --- /dev/null +++ b/doc/en/rg-percussionmatrix.png diff --git a/doc/en/rg-plugin-dialog.png b/doc/en/rg-plugin-dialog.png Binary files differnew file mode 100644 index 0000000..15e30eb --- /dev/null +++ b/doc/en/rg-plugin-dialog.png diff --git a/doc/en/rg-pluginbuttons.png b/doc/en/rg-pluginbuttons.png Binary files differnew file mode 100644 index 0000000..837e7d3 --- /dev/null +++ b/doc/en/rg-pluginbuttons.png diff --git a/doc/en/rg-plugineditorbutton.png b/doc/en/rg-plugineditorbutton.png Binary files differnew file mode 100644 index 0000000..9fa0568 --- /dev/null +++ b/doc/en/rg-plugineditorbutton.png diff --git a/doc/en/rg-quickmarker.png b/doc/en/rg-quickmarker.png Binary files differnew file mode 100755 index 0000000..fe818b4 --- /dev/null +++ b/doc/en/rg-quickmarker.png diff --git a/doc/en/rg-rawnoteruler.png b/doc/en/rg-rawnoteruler.png Binary files differnew file mode 100644 index 0000000..36999e1 --- /dev/null +++ b/doc/en/rg-rawnoteruler.png diff --git a/doc/en/rg-resize.png b/doc/en/rg-resize.png Binary files differnew file mode 100644 index 0000000..f4fa099 --- /dev/null +++ b/doc/en/rg-resize.png diff --git a/doc/en/rg-segmentparameterbox.png b/doc/en/rg-segmentparameterbox.png Binary files differnew file mode 100644 index 0000000..c888d14 --- /dev/null +++ b/doc/en/rg-segmentparameterbox.png diff --git a/doc/en/rg-segno.png b/doc/en/rg-segno.png Binary files differnew file mode 100644 index 0000000..d6946a4 --- /dev/null +++ b/doc/en/rg-segno.png diff --git a/doc/en/rg-select.png b/doc/en/rg-select.png Binary files differnew file mode 100644 index 0000000..0bee367 --- /dev/null +++ b/doc/en/rg-select.png diff --git a/doc/en/rg-split.png b/doc/en/rg-split.png Binary files differnew file mode 100644 index 0000000..f3aa72e --- /dev/null +++ b/doc/en/rg-split.png diff --git a/doc/en/rg-synthpluginbuttons.png b/doc/en/rg-synthpluginbuttons.png Binary files differnew file mode 100644 index 0000000..9b92029 --- /dev/null +++ b/doc/en/rg-synthpluginbuttons.png diff --git a/doc/en/rg-tempodialog.png b/doc/en/rg-tempodialog.png Binary files differnew file mode 100644 index 0000000..33ffc7f --- /dev/null +++ b/doc/en/rg-tempodialog.png diff --git a/doc/en/rg-temporuler.png b/doc/en/rg-temporuler.png Binary files differnew file mode 100644 index 0000000..950e2bf --- /dev/null +++ b/doc/en/rg-temporuler.png diff --git a/doc/en/rg-text-cursor.png b/doc/en/rg-text-cursor.png Binary files differnew file mode 100644 index 0000000..c52e6a0 --- /dev/null +++ b/doc/en/rg-text-cursor.png diff --git a/doc/en/rg-textdialog.png b/doc/en/rg-textdialog.png Binary files differnew file mode 100644 index 0000000..3fd4521 --- /dev/null +++ b/doc/en/rg-textdialog.png diff --git a/doc/en/rg-timesigdialog.png b/doc/en/rg-timesigdialog.png Binary files differnew file mode 100644 index 0000000..2e017e8 --- /dev/null +++ b/doc/en/rg-timesigdialog.png diff --git a/doc/en/rg-trackbutton-instrumentmenu.png b/doc/en/rg-trackbutton-instrumentmenu.png Binary files differnew file mode 100644 index 0000000..54ea72a --- /dev/null +++ b/doc/en/rg-trackbutton-instrumentmenu.png diff --git a/doc/en/rg-trackbutton-instruments.png b/doc/en/rg-trackbutton-instruments.png Binary files differnew file mode 100644 index 0000000..bd8a242 --- /dev/null +++ b/doc/en/rg-trackbutton-instruments.png diff --git a/doc/en/rg-trackbutton-labels.png b/doc/en/rg-trackbutton-labels.png Binary files differnew file mode 100644 index 0000000..f3e005a --- /dev/null +++ b/doc/en/rg-trackbutton-labels.png diff --git a/doc/en/rg-trackbuttons.png b/doc/en/rg-trackbuttons.png Binary files differnew file mode 100644 index 0000000..2605de2 --- /dev/null +++ b/doc/en/rg-trackbuttons.png diff --git a/doc/en/rg-trackeditor.png b/doc/en/rg-trackeditor.png Binary files differnew file mode 100644 index 0000000..62d8cc3 --- /dev/null +++ b/doc/en/rg-trackeditor.png diff --git a/doc/en/rg-trackparameterbox.png b/doc/en/rg-trackparameterbox.png Binary files differnew file mode 100644 index 0000000..fdcb9ef --- /dev/null +++ b/doc/en/rg-trackparameterbox.png diff --git a/doc/en/rg-transport.png b/doc/en/rg-transport.png Binary files differnew file mode 100644 index 0000000..006fa0e --- /dev/null +++ b/doc/en/rg-transport.png diff --git a/doc/en/rg-triggersegment.png b/doc/en/rg-triggersegment.png Binary files differnew file mode 100644 index 0000000..2c827f8 --- /dev/null +++ b/doc/en/rg-triggersegment.png diff --git a/doc/en/rg-tupletdialog.png b/doc/en/rg-tupletdialog.png Binary files differnew file mode 100644 index 0000000..6275b28 --- /dev/null +++ b/doc/en/rg-tupletdialog.png diff --git a/doc/en/rg-useornament.png b/doc/en/rg-useornament.png Binary files differnew file mode 100644 index 0000000..897370b --- /dev/null +++ b/doc/en/rg-useornament.png diff --git a/doc/en/tips b/doc/en/tips new file mode 100644 index 0000000..99074a8 --- /dev/null +++ b/doc/en/tips @@ -0,0 +1,316 @@ +<tip category="Rosegarden|General"> +<html> +<p>To configure a track to play using a particular instrument:</p> + * click on the track label and hold a moment<br> + * select an output device<br> + * select one of that device's available instruments (#1 - #16)<br> + * adjust that instrument's output channel, program, bank, and +controllers via the instrument parameters box +</html> +</tip> +<tip category="Rosegarden|General"> +<html> +<p>...that Rosegarden has an autosave feature?<br><br> +You can select your autosave interval from <b>Settings->Configure +Rosegarden</b>.<br><br> +When something goes awry, such as a power outage or a Rosegarden crash +(unfortunately, it happens...) simply load the file you were working on, and you'll be given the +option to load the autosaved version, or the unmodified original.</p> +</html> +</tip> +<tip category="Rosegarden|General"> +<html> +<p> +...that you can save the current document as your default studio by using +<b>Composition -> Studio -> Save Current Document as Default Studio</b>?</p> +</html> +</tip> +<tip category="Rosegarden|General"> +<html> +<p>...that your default studio is a complete Rosegarden composition that gets +loaded every time you create a new document or import a MIDI file?</p> +</html> +</tip> +<tip category="Rosegarden|General"> +<html> +<p>...that your default studio can contain instrument assignments, document properties, LilyPond headers, +and many other things?<br><br>The default studio is a complete Rosegarden composition, so it can contain anything that you may wish to have available in each +new document you create.</p> +</html> +</tip> +<tip category="Rosegarden|General"> +<html> +<p>...that Rosegarden will detect and create a default connection for ALSA soft +synth applications that are started after Rosegarden is already running?</p> +</html> +</tip> +<tip category="Rosegarden|General"> +<html> +<p>...that you can make your default studio override that in every Rosegarden composition you load?<br><br>If your studio setup does not change very often, and you would prefer for +the settings in your default studio to take precedence over whatever +studio is saved with any files you happen to load, you can make your studio the default for everything using <b>Settings -> Configure Rosegarden -> +MIDI -> Always use default studio when loading files</b>.</p> +</html> +</tip> +<tip category="Rosegarden|General"> +<html> +<p>If you have accidentally recorded a segment so short that it does not +appear on the canvas, which you can only hear during subsequent recording +sessions, you can gain access to it by using <b>Composition -> Change +Composition Start and End</b> and then setting the composition to start at a negative number.</p> +</html> +</tip> +<tip category="Rosegarden|General"> +<html> +<p>...that if you place a note at the wrong pitch using the notation or matrix editor, you can move it one semitone at a time with the up and down arrow keys on your keyboard?</p> +</html> +</tip> +<tip category="Rosegarden|General"> +<html> +<p>...that you can toggle stem directions in the notation editor by selecting +one or more notes and using Ctrl-PageUp and Ctrl-PageDown?</p> +</html> +</tip> +<tip category="Rosegarden|General"> +<html> +<p>...that you can change the accidental used for a note in the notation editor (without changing the pitch of the note) by selecting +it and using the up and down arrow keys with both Ctrl and Shift pressed?</p> +</html> +</tip> +<tip category="Rosegarden|General"> +<html> +<p>...that you can hold down the Shift key while repositioning segments on the +segment canvas in order to avoid the "snap-to" effect and exert finer control?</p> +</html> +</tip> +<tip category="Rosegarden|General"> +<html> +<p>...that you can use the arrow tool to draw, move, and resize segments and events as well as to select them?<br><br>Drag a segment or event block to move it, drag the right edge of a block to resize it, and drag with the middle mouse button pressed to draw a new segment or event.<br><br>(Of course, the dedicated draw, move and resize tools are still quicker for repeated operations.)</p> +</html> +</tip> +<tip category="Rosegarden|General"> +<html> +<p>...that you can hold down the Shift key while repositioning segments on the +segment canvas in order to avoid the "snap-to" effect and exert finer control?</p> +</html> +</tip> +<tip category="Rosegarden|General"> +<html> +<p>...that you can hold down the Shift key while repositioning or resizing events in the +matrix view in order to avoid the "snap-to" effect and exert finer control?</p> +</html> +</tip> +<tip category="Rosegarden|General"> +<html> +<p>...that you can edit multiple segments on multiple tracks simultaneously in +the notation editor? Simply select the segments, then use <b>Edit -> Open in Notation Editor</b>.</p> +</html> +</tip> +<tip category="Rosegarden|General"> +<html> +<p>...that Rosegarden can export files for use by LilyPond, the high-quality score typesetting system?<br><br> +From the <b>File</b> menu, navigate to <b>Export -> Export LilyPond File</b></p> +</html> +</tip> +<tip category="Rosegarden|General"> +<html> +<p>...that Rosegarden can print via LilyPond, the high-quality score typesetting system?<br><br> +From the <b>File</b> menu, navigate to <b>Preview with LilyPond</b>. The file +will be exported, rendered, and a preview will appear in KPDF, or one of +several other PDF viewers, where it can then be printed as well.</p> +</html> +</tip> +<tip category="Rosegarden|General"> +<html> +<p>...that if you use the quantizer from within the notation view, you can tell it to quantize only the timing used for notation -- making it possible to have good looking notation <b>and</b> a human MIDI performance?</p> +</html> +</tip> +<tip category="Rosegarden|General"> +<html> +<p>...that you can change segment labels using the controls on the Segment Parameters box +in the main window?</p> +</html> +</tip> +<tip category="Rosegarden|General"> +<html> +<p>...that the number of tracks in new documents is based on the contents of +your autoload.rg file? +<br><br> +Whether you prefer to start with three tracks or 43, create a document that +contains the desired number of tracks, plus any other studio or document properties settings +you wish to configure, and use <b>Composition -> Studio -> Save Current Document as Default +Studio</b> to make this your new default.</p> +</html> +</tip> +<tip category="Rosegarden|General"> +<html> +<p>...that you can change the name of a track by double clicking on the label? (The +label must be visible for this to work.)</p> +</html> +</tip> +<tip category="Rosegarden|General"> +<html> +<p>...that you can configure what happens when you double-click on a segment?<br><br>Go to <b>Settings -> Configure Rosegarden</b> and choose your preferred editing window under the <b>Behaviour</b> tab.</p> +</html> +</tip> +<tip category="Rosegarden|General"> +<html> +<p>...that Rosegarden is being developed as a community effort with +contributions from around the world?<br><br> +The four most active developers live in London (England), Cannes, Barcelona, +and... Christiansburg? (Christiansburg is a town of about 50,000 in +southwestern Virginia, USA.)<br><br> +We have had contributors from elsewhere in the US, UK, Spain, Mexico, Argentina, Germany, +Sweden, Russia, Japan, Finland, and Italy, just to name a few...</p> +</html> +</tip> +<tip category="Rosegarden|General"> +<html> +<p>...that Rosegarden is available in Spanish, French, German, Russian, Welsh, Swedish, Italian and Estonian +translations? (Just to name a few.)<br><br> +If you're interested in translating Rosegarden to another language, drop us a +line at <b>rosegarden-devel@lists.sourceforge.net</b>.</p> +</html> +</tip> +<tip category="Rosegarden|General"> +<html> +<p>...that you can change the total number of bars in the composition via +<b>Composition -> Change Composition Start and End</b>?</p> +</html> +</tip> +<tip category="Rosegarden|General"> +<html> +<p>...that you can see the difference between performance and display duration +of duration-quantized notes in the notation editor?<br><br> +Use <b>Settings -> Show Raw Note Ruler</b> to turn on this handy +feature.<br><br> +<i>Note that this feature does not work in page layout view.</i></p> +</html> +</tip> +<tip category="Rosegarden|General"> +<html> +<p>...that you can add tempo and time-signature changes by double-clicking on the values displayed in the transport window or tempo rulers?</p> +</html> +</tip> +<tip category="Rosegarden|General"> +<html> +<p>...that the transport window can display musical time, sample frame count, and a visual metronome as well as real time?<br><br>Just click on the small button at the extreme top left of the window.</p> +</html> +</tip> +<tip category="Rosegarden|General"> +<html> +<p>...that you can select all notes of a particular pitch in the matrix view, by shift-clicking on that pitch on the piano keyboard at the left?<br><br>If you shift-click-drag, you can select whole ranges too.</p> +</html> +</tip> +<tip category="Rosegarden|General"> +<html> +<p>...that you can set a loop in the main window by clicking-and-dragging on the time ruler with Shift pressed?<br><br>(If the ruler isn't visible, use <b>Settings -> Show Rulers</b>.)</p> +</html> +</tip> +<tip category="Rosegarden|General"> +<html> +<p>...that if you're editing a section in the matrix or notation view, you can +set that section to loop while you edit it?<br><br>Select it and use <b>Tools -> +Local Cursor -> Set Loop to Selection</b>, then hit Play.</p><br><br> +<i>This feature does not work quite as well for compositions that include sampled +audio.</i> +</html> +</tip> +<tip category="Rosegarden|General"> +<html> +<p>...if you have more than one note or controller event at the same time, you +can use the [ and ] keys to flip the stack of events around on the controller +and velocity rulers in order to bring the item you wish to adjust into +focus.</p> +</html> +</tip> +<tip category="Rosegarden|General"> +<html> +<p>...that the notation view shows you notes using their display duration, while the +matrix allows you to edit their performance duration?<br><br> +<i>Be careful with tied notes in the matrix. It is not apparent that they are +tied, and if you split up a pair of tied notes, subsequent notation views will +be confused and unhappy. This is an old bug that has been on our TODO list +for years. Sorry about that, folks. Patches welcome.</i> +</p> +</html> +</tip> +<tip category="Rosegarden|General"> +<html> +<p>If you're working with a human performance and you need to insert some new +notes, these new notes will sound for their entire written duration. To blend +these new notes into a human performance, select them, then use <b>Adjust -> Interpret...</b> +from the notation view to interpret any marks and massage their performance +durations to something less mechanical.</p> +</html> +</tip> +<tip category="Rosegarden|General"> +<html> +<p>...that Rosegarden can export certain things to LilyPond that it cannot yet +display within its own native interface?<br><br>These new directives can be inserted +via the <b>T</b> text insert tool in the notation view.<br><br> +Load the example files +<b>lilypond-alternative-endings.rg</b> and <b>lilypond-directives.rg</b> for a +demonstration of how to use the new exportable directives.<br><br> +Use <b>File -> Preview with +LilyPond</b> to see what they look like on the exported page.<br><br> +<i>Be sure to turn on +<b>Settings -> Show LilyPond Directives</b> and <b>Show Annotations</b> within +the notation view.</i></p> +</html> +</tip> +<tip category="Rosegarden|General"> +<html> +<p>...that Rosegarden has track parameters allowing you to <b>Create segments with:</b> certain +properties by default?<br><br>You can pre-select the clef, transposition, colour, and specify +the highest and lowest playable notes (notes outside this range display in +red by default). Then draw a segment with the pencil, or record one, and any +new segments created on this track will take these properties as segment +parameters.<br><br> +<i>These parameters do not apply to audio tracks.</i></p> +</html> +</tip> +<tip category="Rosegarden|General"> +<html> +<p>...that Rosegarden has a database of preset parameters describing more than 300 +musical instruments from the real world, grouped into several convenient +categories?<br><br>Each preset contains a clef, transposition, and playable range +suggestions for both amateur and professional players.<br><br>Click the +<b>Load</b> button in the new track parameters box to get started! <i>(If you +do not see a <b>Load</b> button, be sure your parameter panel is set for +tabbed mode, rather than stacked mode.)</i> <br><br> <i>(Special thanks to Magnus +Johansson for assembling this extraordinary database.)</i></p> +</html> +</tip> +<tip category="Rosegarden|General"> +<html> +<p>...that when exporting to Lilypond, you can merge tracks that have the same name onto a single staff?<br><br>For example, if there are three voices in a single part, write each +voice as an independent segment/staff, each on a separate track. Give all +three tracks the same name, and select <b>[x] Merge tracks that have the same +name</b> from the options dialog that appears when you export to, or preview +with LilyPond.<br><br> +<i>The tracks must have a non-default name for this to work.</i></p> +</html> +</tip> +<tip category="Rosegarden|General"> +<html> +<p>...that you can use the mouse wheel to scroll up and down, scroll left and right, and zoom in and out?<br><br>Just roll the wheel to scroll up or down. Hold Alt as well to scroll left or right, or hold Ctrl to zoom in and out.</p> +</html> +</tip> +<tip category="Rosegarden|General"> +<html> +<p>...that you can time-stretch an audio segment -- stretching or squashing a +sample to a different duration without changing its pitch -- just by +dragging its right edge with the Ctrl key pressed?</p> +</html> +</tip> +<tip category="Rosegarden|General"> +<html> +<p>...that you can add audio to your Rosegarden composition just by dragging an audio file from your file manager and dropping it on the Rosegarden segment canvas? (Make sure you drop it on an audio track!)<br><br>You can also drop audio files from Rosegarden's audio file manager window onto the segment canvas, and from other programs onto the audio file manager.</p> +</html> +</tip> +<tip category="Rosegarden|General"> +<html> +<p>...that you can set the tempo to match the duration of an audio segment if you know it's an exact number of bars or beats long?<br><br>Just select the audio segment and use <b>Composition -> Tempo and Time Signature -> Set Tempo to Audio Segment Duration</b>.</p> +</html> +</tip> diff --git a/doc/en/transpose-by-interval.png b/doc/en/transpose-by-interval.png Binary files differnew file mode 100644 index 0000000..727eb2f --- /dev/null +++ b/doc/en/transpose-by-interval.png diff --git a/doc/es/CMakeLists.txt b/doc/es/CMakeLists.txt new file mode 100644 index 0000000..eb6d853 --- /dev/null +++ b/doc/es/CMakeLists.txt @@ -0,0 +1,12 @@ +################################################# +# +# (C) 2011 Timothy Pearson +# kb9vqf (AT) pearsoncomputing.net +# +# Improvements and feedback are welcome +# +# This file is released under GPL >= 2 +# +################################################# + +tde_create_handbook( DESTINATION rosegarden ) diff --git a/doc/es/index.docbook b/doc/es/index.docbook new file mode 100644 index 0000000..3b15e0d --- /dev/null +++ b/doc/es/index.docbook @@ -0,0 +1,6416 @@ +<?xml version="1.0" ?> +<!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.1.2-Based Variant V1.0//EN" "dtd/kdex.dtd" [ + <!ENTITY rosegarden "<application +>Rosegarden</application +>"> + <!ENTITY MIDI "<acronym +>MIDI</acronym +>"> + <!ENTITY % Spanish "INCLUDE" +> <!-- change language only here --> + <!ENTITY % addindex "IGNORE"> +]> + +<!-- The language must be changed in the <book +> tag for translations. --> + + +<!-- + + Notes on style and terminology for Rosegarden handbook + ====================================================== + + * Aim to be clear, brief and direct, but be informal. + + * Write instructions in the second person. + + Good: "You can select segments by clicking on + them with the arrow tool." + + Bad: "Segments can be selected by clicking on + them with the arrow tool." + + Very bad: "The arrow tool allows the user to select + segments by clicking on them." + + If you dislike the first of these because you want to + make the phrase "the arrow tool" more obvious by placing + it at the start of the sentence, then perhaps you + should be using a variablelist instead and making + "the arrow tool" a list item. + + * It's perfectly permissible to detour to explain why + something is the way it is, particularly if it might + not be obvious. + + * It's also entirely permissible to omit advanced stuff + from the "Using Rosegarden" section and document it + only in the reference section. "Using Rosegarden" + should be about understanding how and why, not about + knowing every last clever detail. + + * Bear in mind we can link extensively from any part of + the handbook to any other. Unfortunately DocBook won't + allow you to write a link to a target that doesn't + exist yet, so if you want to link to something that's + not yet been written, either make a note of the planned + link in an XML comment, or go and create a stub for the + bit that hasn't been written yet, or else just write in + a way that allows for a link to be easily added later + (we could do an editing phase specially for links). + + * Be strict about using the correct terminology for + Rosegarden data structures (segment, event, track, + instrument, composition), but don't capitalise the + words. Capitalisation is useful in technical documents + to make it clear that you're referring to a precise + concept, but you shouldn't have to do it to make your + meaning clear in user documentation. If something + seems ambiguous without, try rewording it instead. + + + About Screenshots + ================= + + Screenshots used with this documentation should use the + following style, colour and font settings: + + * KDE Style: "Light Style, 3rd Revision" + + * Colour scheme: "Blue Slate", with high-contrast + setting and with the standard widget background set + to white. (I have this saved as a new scheme.) + + * Fonts: Verdana 11px for general use and menus; Verdana + 11px bold for window titles; antialiasing on, but + sub-pixel antialiasing off. (For pictures of the + segment and instrument parameter boxes I usually turn + the size up to 13px, which perhaps says something about + our use of font size in these boxes.) + + * Window Decorations: "Quartz" + + None of these would be my first choice for nice-looking + screenshots now, but we're not here to sell Rosegarden in this + document, we're here to provide clear and consistent help text. + So the priority is to make new screenshots look like the existing + ones, not to make them look fancy. Also, I think there is an + advantage to having screenshots in a help document look a bit + distinct from the user's own window decorations surrounding the + help text. + + Screenshots of the whole program or of whole matrix or + notation windows may be taken using different themes if + desired, but screenshots of individual dialogs or window + components must use the above scheme. + +--> + +<!-- + Notes on Usability Defects + ========================== + + This comment is a place to note anything I find difficult to + document, or anything where the functions for two necessarily + linked concepts are not actually linked in the GUI (etc). + + * The audio file directory (in document properties) can't be + inspected or changed from the audio file manager. This is + arguably linked to a need for a project directory. There + are various other usability problems with the audio file + manager as well, e.g. there's no way to tell it to pull all + imported audio files into a single audio directory. + + * Track buttons showing sometimes-instrument, sometimes-label. + + * Can't usefully double-click / right-click on most rulers. + This would be useful for a slower but clearer way to set + loops; adding and editing markers; etc. Setting loops is + particularly opaque especially in notation and matrix views. + + * Hideous inconsistency (documented in an RFE already) between + having to use RG for MIDI routing and being unable to use RG + for audio routing. + + * Uh, Pedro implemented this multiport recording but we can't + actually split the results can we? + + Troubleshooting + =============== + + Shall we have a troubleshooting section? + + * I'm not seeing any MIDI outputs + * I'm not hearing any sound from my MIDI outputs + * I'm not seeing any audio outputs + * I'm not hearing any sound from my audio outputs + * I don't see any synth plugins + +--> + +<!-- + Still to do + =========== + + * Control rulers + + * Controller editing + + * Event list + + * Event editor dialogs + + * Tempo / timesig editor + + * Triggered segments + + * Split by Pitch + + * Document properties + + * Add images for the tools (move, split &c) when describing them + + * Add images for transport buttons in transport section + + * Update notation menu references + + * Add new notation stuff + + * Config dialog + + * Make sure the guimenuitem etc tags are being used for all menu refs + + * Give keyboard shortcuts for menu functions? + + * Go through again changing Rosegarden -> &rosegarden; and double-hyphen -> + – or — and review any uses of "the ... function" to see + if these words are redundant + + * Troubleshooter + + * Check !!! items + + * Fill gaps in revision history + + * Consistent capitalisation: Instrument Parameter Box or instrument + parameter box? Audio Mixer or audio mixer? Device or device? + + * Finally, review the structure again and adjust the <chapter +>/<sect*> + for balance + +--> + + +<book id="rosegarden" lang="&language;"> + + <!-- This header contains all of the meta-information for the document such + as Authors, publish date, the abstract, and Keywords --> + + <bookinfo> + <title +>El Manual de Rosegarden</title> + <authorgroup> + <author +><firstname +>Chris</firstname +> <surname +>Cannam</surname +> </author> + <author +><firstname +>Richard</firstname +> <surname +>Bown</surname +> </author> + <author +><firstname +>Guillaume</firstname +> <surname +>Laurent</surname +> </author> + <othercredit role="translator" +><firstname +>Marcos</firstname +> <surname +>Guglielmetti</surname +> <affiliation +><address +> <email +>marcospcmusica@yahoo.com.ar</email> + </address +></affiliation> + <contrib +>traducci n</contrib +> <!-- ??? not sure what this tag is actually for --> + </othercredit> + </authorgroup> + + <copyright> + <year +>2002-2004</year> + <holder +>Chris Cannam, Richard Bown, Guillaume Laurent</holder> + </copyright> + + <date +>2004-08-04</date> + <releaseinfo +>0.9.9</releaseinfo> + + <abstract> + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-mainwindow.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>&rosegarden;</phrase> + </textobject> + </mediaobject> +</screenshot +> Rosegarden es un secuenciador de audio y &MIDI; y un editor de notación musical. Este manual describe como usarlo. </para> + </abstract> + + <keywordset> + <keyword +>Rosegarden</keyword> + <keyword +>secuenciador</keyword> + <keyword +>MIDI</keyword> + <keyword +>audio</keyword> + <keyword +>música</keyword> + <keyword +>notación</keyword> + <keyword +>partitura</keyword> + <keyword +>KDE</keyword> + </keywordset> + + </bookinfo> + + <!-- The contents of the documentation begins here. Label each + chapter so with the id attribute. This is necessary for two reasons: + it allows you to easily reference the chapter from other chapters of + your document, and if there is no ID, the name of the generated HTML + files will vary from time to time making it hard to manage for + maintainers and for the CVS system. Any chapter labelled (OPTIONAL) + may be left out at the author's discretion. Other chapters should + not be left out in order to maintain a consistent documentation + style across all KDE apps. --> + + <chapter id="introduction"> + <title +>introducción</title> + + <sect1> + <title +>Sobre Rosegarden</title> + <para +><application +>Rosegarden</application +>es un secuenciador de audio y &MIDI; y un editor de notación musical. Rosegarden le permite grabar, armar y componer música en la forma tradicional de partituras o como datos &MIDI;, o archivos de audio tanto importados como grabados de un micrófono, guitarra o cualquier fuente de audio que usted desee. Puede usar Rosegarden para escribir, editar y organizar música para crear una composición, a la cual puede sintetizarla, agregarle efectos, y mezclar para quemar un CD o distribuir en la web. Rosegarden también provee soporte para edición de notación profesional para impresiones de alta calidad. </para> + + <para +><application +>Rosegarden</application +>está diseñado para parecer y actuar de manera similar para usuarios experimentados que llegan a Linux de otras plataformas, siendo generalmente accesible y amistoso para nuevos usuarios de software para música. </para> + + <sect2 id="intro-handbook"> + <title +>Sobre este Manual</title> + <para +>Este manual resume la capacidades de &rosegarden; y provee una referencia para alguno de los conceptos involucrados. Está diseñado para tener sentido tanto leyéndolo en orden o siendo usado como referencia de los conceptos y funciones disponibles en Rosegarden. Si quiere leer un tutorial también, <ulink url="http://www.rosegardenmusic.com/resources/tutorial/using_en.shtml" +>you puede encontrar uno aquí</ulink +>.</para> + + <para +>Si llegara a existir algo que no entienda o requiera de ayuda, por favor visite <ulink url="http://www.rosegardenmusic.com/support/" +>el website de Rosegarden</ulink +> para la lista de Preguntas Frecuentes (FAQ) e instrucciones sobre la lista de correo. </para> + </sect2> + + <sect2 id="intro-menufunctions"> + <title +>Sobre los Menúes y Atajos</title +> <para +>Este manual usualmente se refiere a las funciones que puede usar en Rosegarden describiendo donde se encuentran en los menúes. Por ejemplo, la función para agregar una pista nueva al editor principal de pistas es <menuchoice +> <guimenu lang="en" +>Tracks</guimenu +> <guimenuitem +>Add Track</guimenuitem +> </menuchoice +>.</para> + + <para +>En muchos casos, ésta no es la única forma forma de llegar a una función particular. Ebn el caso en particular, ésta misma función se encuentra disponible a través del atajo de teclado Ctrl+T, y también aparece como un ícono en una de las barras de herramientas de la ventana princiapl. Tanto el atajo de teclado como el ícono pueden ser fácilmente aprendidos, puesto que son mostrados en el menú de Rosegarden junto con el nombre de la función. Debe tener presente que , por motivos de referencia en ésta documentación, aunque siempre damos la localización dentro del menú de forma completa, no es necesariamente la mejor o mas usual forma para usar una función, por lo que debe prestar atención a los atajos de teclados e íconos de las barras de herramientas. </para> + </sect2> + + <sect2 id="intro-optional"> + <title +>Características especiales</title +> <para +>Éste manual asume que su instalación de Rosegarden soporta todas las características de las que es capaz. Algunas de ellas, incluyendo ciertas muy importantes, son actualmente opcionales al momento de realizar la instalación de Rosegarden, dependiendo en qué otras librerías y códigos de soporte se encuentran disponibles. Por ejemplo, el subsistema completo de audio es compilado sólo si las librerías de JACK se encuentran disponibles; plugins de soporte para sintetizadores dependen de un número de otros módulos; etc.</para +> <para +>Éstas dependencias están documentadas en el README de Rosegarden y en la documentacíon de configuración. Si encuentra que éste manual se refiere a características no visibles en la versión de Rosegarden que está utilizando, consulte la documentación de configuración o a su distribuidor. </para> + </sect2> + </sect1> + </chapter> + + +<!-- + ********************************** + + PART I: + Discussion and tutorial material + + ********************************** + --> + + + <chapter id="file-operations"> + <title +>Archivos y Documentos de Rosegarden</title> + <para +>&rosegarden; guarda cada configuración en su propio documento, usando su propio formato interno. Cuando guarda un documento, el mismo es guardado en el disco como un archivo con la extensión .rg . &rosegarden; también puede manejar otros formatos estándar. </para> + + <sect1 id="file-creating"> + <title +>Nuevas composiciones</title> + <para +>&rosegarden; inicia con un documento nuevo, conteniendo una composición "vacía" lista para empezar a ser editada. Para colocar algo en su composición, es posible tanto grabar algo o crear algunos segmentos en blanco de música (referidos como "segmentos") que puede llenar usando varias de las facilidades de edición. </para> + <para +>Mire <link linkend="recording" +>Grabación</link +> para obtener detalles de cómo grabar música, y mire la sección <link linkend="segment-view" +>Editor de Pistas</link +> para una descripción de como crear, editar y manejar segmentos de música. </para> + </sect1> + + <sect1 id="file-midi"> + <title +>Usando archivos MIDI</title> + <para +>Para importar y exportar archivos MIDI, utilice el menú <menuchoice +> <guimenu lang="es" +>Archivo</guimenu +> <guimenuitem +>Importar</guimenuitem +> <guimenuitem +>Importar archivo MIDI</guimenuitem +> </menuchoice +> y <menuchoice +> <guimenu lang="es" +>Archivo</guimenu +> <guimenuitem +>Exportar</guimenuitem +> <guimenuitem +>Exportar archivo MIDI</guimenuitem +> </menuchoice +>. </para> + <para +>Aunque &rosegarden; puede cargar y guardar archivos en formatos como el MIDI, no guarda datos MIDI internamente. Generalmente debería preferir guardar los archivos en el formato propio de &rosegarden;, ya que &rosegarden; guarda un montón mas de información que sería perdida si se exportara a MIDI. </para> + <para +>Cuando un archivo MIDI es cargado, &rosegarden; particiona la música en una pista por pista MIDI o canal en el archivo, <link linkend="studio-midi-import" +>setea los mapeos de instrumentos apropiados</link +>, e <link linkend="nv-quantization" +>inetnta calcular notación plausible</link +> para los datos MIDI de performance. </para> + </sect1> + + <sect1 id="file-merge"> + <title +>Mezclando archivos</title +> <para +>De la misma manera en que es posible cargar o importar archivos, también es posible mezclarlos en el documento actual, agregando los segmentos del archivo a los que se se encuentran ya ahí. </para> + + <para +>Para mezclar un archivo, utilice la opción del submenú <menuchoice +> <guimenu lang="es" +>Archivo</guimenu +> <guimenuitem +>Merge</guimenuitem +> </menuchoice +> en vez de usar la opción Abrir o Importar. </para> + </sect1> + + <sect1 id="file-printing"> + <title +>Imprimiendo</title> + <para +>Es posible imprimir una composición en el formato de partitura, usando la función <menuchoice +> <guimenu lang="es" +>Archivo</guimenu +> <guimenuitem +>Imprimir</guimenuitem +> </menuchoice +>. </para> + + <para +>Producir una partitura de los datos de la performance es una tarea difícil. Es recomendable usar el <link linkend="notation-view" +>editor de notación</link +> para emprolijar la partitura antes de imprimir. (Ver también <link linkend="nv-quantization" +>Notación desde datos de performance</link +>.) </para> + + <para +>&rosegarden; es capaz de producir partituras muy legibles. De todas formas, está diseñado para ser un editor de pantalla y no primariamente un editor de partes. Si quiere producir partituras con verdadera calidad de impresión, se debe considerar el uso de <ulink url="http://www.lilypond.org" +>Lilypond</ulink +> junto con &rosegarden;. Lilypond es un software para crear partituras que lee un archivo de texto especializado y produce impresiones de alta calidad. &rosegarden; es capaz de escribir archivos de Lilypond usando la función <menuchoice +> <guimenu lang="es" +>Archivo</guimenu +> <guimenuitem +>Exportar</guimenuitem +> <guimenuitem +>Exportar a Lilypond</guimenuitem +> </menuchoice +>. </para +> </sect1> + + </chapter> + + <chapter id="segment-view"> + <title +>El editor de Pistas</title> + <sect1 id="segment-view-overview"> + <title +>Características</title> + <para +>La presentación principal de &rosegarden; es similar a la de muchos otros secuenciadores populares. Está basado en una estructura de pistas — la ventana principalmuestra un editor de pistas con una lista de las mismas y sus instrumentos asociados en la izquierda. Es posible manipular y mover bloques de datos (referidos como “segmentos”) en el editor de pistas como así también abrir los segmentos en un editores especializados (<link linkend="notation-view" +>notación</link +>, <link linkend="matrix-view" +>matríz</link +>, and <link linkend="event-view" +>lista de eventos</link +>). </para> + + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-trackeditor.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>El editor de pistas de &rosegarden; mostrando dos segmentos de datos de música.</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + + <para +>Las pistas pueden ser asignadas a un rango de instrumentos &MIDI;, sintetizadores por plugins o instrumentos de audio. En la figura de arriba se puede ver tres segmentos en el editor de pistas asignados a instrumentos General MIDI. </para> + + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-trackbutton-labels.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>Los botones de pista de &rosegarden; mostrando susetiquetas correspondientes.</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + + <para +>El área de botones a la izqueirda del canvas de segmentos muestra el número de pista, los estátus de silenciamiento y grabación y la etiqueta de la pista. Puede silenciar o desilenciar una pista cliqueando en el botón con forma de LED azul, y seleccionar una pista en particular para grabacíon cliqueando en el rojo. Para cambiar la etiqueta de la pista, haga doble click en ella. </para> + + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-trackbutton-instruments.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>Los botones de pista de &rosegarden; mostrando la asignación de instrumentos.</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + + <para +>Las etiquetas de pistas son sólo mostradas si la opción del menú <menuchoice +> <guimenu lang="es" +>Configuraciones</guimenu +> <guimenuitem +>Mostrar las Etiquetas de Pistas</guimenuitem +> </menuchoice +> está activado. De otra forma, como se ve en la figura, se muestra la asignación de instrumentos para cada pista.</para> + + </sect1> + <sect1 id="segment-view-instruments"> + <title +>Pistas e Instrumentos</title> + <para +>Cada pista debe tener un instrumento asignado a ella, para que pueda ser escuchada. Por defecto, las primeras 16 pistas son asignadas a los 16 instrumentos del primer dispositivo MIDI disponible, y las siguientes 16 asignadas a audio.</para> + + <para +>Para cambiar la asignación de instrumentos para cada pista, cliquee con el botón derecho en la etiqueta de la pista Un menú emergente aparecerá, en el cuál es posible seleccionar entre todos los instrumentos disponibles. </para> + + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-trackbutton-instrumentmenu.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>Mneú de instrumentos de &rosegarden;</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + + <para +>Un instrumento puede ser interpretado como un solo canál en un dispositivo &MIDI;, o como una entrada de audio mono ó estéreo o un plugin de sintetizador. Las pistas que contienen datos de notas deben ser asignados a un instrumento &MIDI; o a uno de un plugin de sintetizador, y aquellas que contengan audio, a un instrumento de audio. Es posible asignar más de una pista para el mismo instrumento, en cuyo caso las múltiples pistas van a usar los mismos sonidos. </para> + <para +>Es posible cambiar varias de las propiedades de los instrumentos asociados con una pista usando la <link linkend="segment-view-instrumentparameterbox" +>caja de Parámetros de Instrumentos</link +>. Desde aquí se puede, por ejemplo, setear un instrumento MIDI para utilizar un patch en particular y de ésa manera producir un sonido en particular (piano, cuerdas, etc.). </para> + <para +>Vea la sección <link linkend="studio-introduction" +>Estudio</link +> para mas información acerca de instrumentos. </para> + + </sect1> + + <sect1 id="segment-view-creating"> + <title +>Creando segmentos</title> + <para +>Para crear un segmento vacío, de forma de empezar a componer algo nuevo, es necesario utilizar la herramienta lapiz. Cliquee en el lápiz de la barra de herramientas y luego cliquee en el punto donde quiere que empiece su segmento (a la altura correcta para la pista en la que desea que el segmento se encuentre, y a una distancia através de la ventana del editor correspondiente al tiempo que desea) y arrastre hacia la derecha hasta que el segmento tenga el número correcto de barras de longitud. </para> + + <para +>Usualmente cada nuevo segmento empieza en una línea de barra y se extiende barra por barra, pero este efecto de ajustar-a-la-grilla puede ser prevenido presionando la tecla Shift mientras se cliquea y arrastra. </para> + + <para +>Una vez creado el segmento, puede empezar a editarlo utilizando los ediores de<link linkend="matrix-view" +>matríz</link +> o de <link linkend="notation-view" +>notación</link +>. Para usar uno de éstos editores, haga doble click en el segmento, o cliquee con el botón derecho y elija el editor que quiere del menú de contexto. </para> + + <para +>Si pretende <link linkend="recording" +>grabar</link +> de un dispositivo MIDI o una entrada de audio, no necesita crear un nuevo segmento para grabar en él. Cada granación por separado siempre va en un segmento nuevo, creado automáticamente durante la grabación. </para> + </sect1> + + <sect1 id="segment-view-audio-segments"> + <title +>Segmentos de audio</title> + <para +>Un segmento de audio contiene o datos de una grabación o de audio sampleado, en vez de datos de eventos-de-nota editables. Rosegarden permite grabar, reproducir, acomodar y dividir segmentos de audio, pero no contiene facilidades de edición de señal de audio. </para> + <para +>Para crear un segmento de audio, puede <link linkend="recording" +>grabar</link +> desde una fuente de audio en una pista asignada a un instrumento de audio, o puede trabajar con archivos WAV existentes. Para lograr esto, se utiliza el diálogo de administración de audio (que se puede encontrar en <menuchoice +><guimenu lang="es" +>Segmentos</guimenu +><guimenuitem +>Manejar Segmentos de Audio</guimenuitem +></menuchoice +>). </para> + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-audiofilemanager.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>El administrador de archivos de audio</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + + <para +>Es posible arrastrar y soltar archivos de audio desde el explorador de archivos de KDE o desde su escritorio KDE dentro del administrador de archivos de audio, o puede abrirlos usando el menú Archivo. Entonces es posible arrastar y soltarlos en el canvas de pistas de Rosegarden, o usar la función del administrador de archivos de audio<menuchoice +><guimenu lang="es" +>Acción</guimenu +><guimenuitem +>Insertar en la Pista de Audio seleccionada</guimenuitem +></menuchoice +>, siempre que la pista seleccionada en la ventana principal esté asignada a un instrumento de audio. Segmentos de audio recién grabados también aparecen en el diálogo del administrador de archivos de audio.</para> + + <para +>Detalles de los archivos de audio utilizados con una composición en particular son guardados junto con ésa composición, pero no lo son los archivos de audio propiamente dichos. Debe asegurarse que su documento tenga el path de búsqueda de archivos de audio correcto (vía <menuchoice +><guimenu lang="es" +>Composición</guimenu +><guimenuitem +>Editar Propiedades del Documento...</guimenuitem +><guimenuitem +>Audio</guimenuitem +></menuchoice +>) de manera de mantener sus archivos de audio accesibles al mismo tiempo.</para> + + <para +>El administrador de audio también muestra la tasa de sampleo y otros detalles para cada archivo de audio, y marca con un asterisco cualquier archivo de audio cuya tasa de sampleo no coincide con la sesión de JACK utilizada en el momento por Rosegarden. Rosegarden resampleará éstos archivos al momento de reproducción usando un resampleador lineal rápido (pero de muy baja calidad). Se recomienda resamplear los archivos utilizando un editor de audio dedicado de manera separada. </para> + + </sect1> + + <sect1 id="segment-view-manipulating"> + <title +>Manipulando segmentos</title> + <para +>La ventana principal contiene una selección de "herramientas" para editar segmentos. éstas se esncuentran disponibles desde la barra de herramientas principal: primero seleccione la herramienta que desea de la barra, y luego cliquee y arrastre sobre los segmentos del canvas principal. </para> + + <sect2 id="segment-view-selector"> + <title +>La herramienta de selección</title> + <para +>La "herramienta de selección" (la herramienta flecha) es realmente una multipropósito, puede ser usada para seleccionar, mover, copiar y redimensionar segmentos.</para> + + <para +>El uso mas obvio es selección: seleccione un solo segmento cliqueando sobre él con la herramienta de selección, o seleccione varios de ellos manteniendo presionada la tecla Shift, o cliqueando en un área vacía de la ventana y arrastrando un área que cubra dichos segmentos. </para> + + <para +>Para mover segmentos con la herramienta de selección, simplemente cliquee y arrastre sobre el segmento. Para crear copias, cliquee y arrastre mientras presiona la tecla Ctrl. Para redimensionar un segmento, cliquee y arrastre en el borde derecho del segmento; y para crear nuevos segmentos, cliquee y arrastre en un área vacía con el botón del medio del ratón. </para> + + <para +>La herramienta de selección no reemplaza a las demás herramientas completamente;— a veces se necesita ser mas preciso sobre la operación que se pretende, particularmente cuando se trata de segmentos pequeños. </para> + + </sect2> + + <sect2 id="segment-view-move-resize"> + <title +>Herramientas para Mover y Redimensionar</title> + <para +>Para mover un segmento a un punto distinto de comienzo o pista, use la herramienta Mover y cliquee y arrastre el segmento que desea mover. Si mantiene presionada la tecla Ctrl mientras arrastra, el segmento será copiado en vez de movido.</para> + + <para +>Para redimensionar un segmento, utilice la herramienta Redimensionar; y cliquee y arrastre en el lado derecho del segmento.</para> + + <para +>Para mover y redimensionar de manera mas precisa (posicionamiento fino) se debe mantener presionada la tecla Shift, de ésta manera se evita que el segmento se ajuste a una posición particular de la grilla. </para> + + </sect2> + + <sect2 id="segment-view-split-join"> + <title +>Herramienta de División</title> + <para +>La herramienta de división <inlinemediaobject +> <imageobject +> <imagedata fileref="rg-split.png"/> </imageobject +> </inlinemediaobject +> permite dividir un segmento en dos separados. Para dividir un segmento, seleccione la herramienta de división y cliquee en el segmento que desea dividir. </para> + <para +>Por defecto, los segmentos son divididos en la línea de barras mas cercana al cursor, pero ésto puede ser evitado presionando la tecla Shift mientras se separa el segmento. </para> + </sect2> + </sect1> + + <sect1 id="segment-view-tempo-timesig"> + <title +>Tiempo de medida y compás</title> + <sect2 id="tempo"> + <title +>Tempo</title> + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-tempodialog.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>Diálogo de tempo de &rosegarden;</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + </sect2> + + <sect2 id="time-signature"> + <title +>Tiempo de medida y compás</title> + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-timesigdialog.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>El diálogo de tiempo de medida y compás de &rosegarden;</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + </sect2> + </sect1> + </chapter> + + <chapter id="transport"> + <title +>El Transporte</title> + <para +>Cuando se reproduce una composición, &rosegarden; muestra un puntero de reproducción através de las pistas de izquierda a derecha, reproduciendo el contenido de los segmentos que atraviesa. La posición del puntero en pantalla es seguida y controlada por una ventana llamada el Transporte. </para> + + <sect1 id="transport-overview" +><title +>Características</title> + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-transport.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>Ventana de Transporte de &rosegarden;</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + + <para +>Si el Transporte no se encuentra visible, puede activarlo con <menuchoice +> <guimenu lang="es" +>Configuración</guimenu +> <guimenuitem +>Mostrar Transporte</guimenuitem +> </menuchoice +>. </para> + + <para +>El Transporte muestra el tiempo a el cuál ha llegado el puntero de reproducción, mostrado en segundos por defecto. Puede cambiarlo para mostrar tiempo musical (conteo de barras y beats), tiempo musical con un metrónomo visual relampageante, o frames de muestreo de audio, usando el botón que se encuentra mas arriba entre los botones pequeños en la ventana de transporte izquierda. El botón inmediatamente inferior cambia el display de manera de mostrar el tiempo faltante para el final de la composición en vez de mostrar el tiempo transcurrido desde el comienzo.</para> + + <para +>Los controles principales del transporte comienzan la ejecución del secuenciador y lo pausan, adelantan el puntero de posición, lo rebobinan, lo paran o permiten saltar hasta el principio o el final de la composición. </para> + + <para +>Controles adicionales y un display de eventos &MIDI; se encuentran escondidos en el fondo extensible del transporte, el cuál puede ser mostrado o escondido mediante el botón con forma de flecha en el borde inferior izquierdo del transporte. En ésta porción extra del transporte se puede encontrar también botones para grabación, setear loops, solos de pistas determinadas, encender o apagar el metrónomo, y silenciar dispositivos MIDI (botón de pánico). </para> + + </sect1> + <sect1 id="recording"> + <title +>Grabando</title> + <para +>Para grabar un nuevo segmento en una pista, primero asegúrese que la pista correcta haya sido seleccionada para grabar seleccionando el botón estilo LED rojo en la etiqueta de la pista, y luego use el control de grabación del Tranporte. Esto hace que se inicien tanto el transporte (por lo que se reproduce la composición existente) como la grabación en la pista apropiada. Por el momento solo una pista por vez puede estar activa para grabar. </para> + <para +>Alternativamente se puede utilizar la grabación de pinchado para separar los actos de comenzar el transporte y entrar en modo de grabación. Las grabaciones por pinchado pueden ser activadas y desactivadas con la barra espaciadora. Puede presionarla mientras se reproduce una composición para cambiar instantáneamente entre reproducción y grabación sin tener que parar el transporte, o puede utilizarla para armar para grabación cuando el transporte se encuentra detenido, de manera que la reproducción subsecuente sea de hecho una grabación. (Esto último es práctico cuando se utiliza un <link linkend="transport-external" +>transporte externo</link +>.) </para> + <para +>Si la pista a grabar está asignada a un instrumento MIDI, la grabación va a llevarse a cabo para todos los intrumentos en <link linkend="studio-device-editor" +>Administrador de dispositivos MIDI</link +>. </para> + <para +>Si la pista a grabar está asignada a un instrumento de audio, la grabación será desde la entrada seleccionada en ese momento en la <link linkend="segment-view-instrumentparameterbox" +>caja de parámetros de instrumentos</link +>. Éste puede ser una entrada de audio externa o un master o submaster de audio (para realizar mezclas). Si se tratara de una entrada externa, será por defecto grabada de la primer entrada física de sonido disponible de la placa de audio. Quizás prefiera usar una herramienta de conección para JACK para conectar alguna otra aplicación JACK a la entrada de audio. </para> + </sect1> + + <sect1 id="transport-external"> + <title +>Transportes externos</title> + <para +>Rosegarden soporta el mecanismo de tranporte JACK para sincronizar su transporte con otras aplicaciones JACK. Para activarlo, vaya a <menuchoice +> <guimenu lang="es" +>Configuraciones</guimenu +> <guimenuitem +>Configurar Rosegarden...</guimenuitem +> </menuchoice +> y en la página del Secuenciador, tab Sincronización, seleccione "Sincronizar" del menú de modo de transporte JACK.</para> + + <para +>Cuando el transporte JACK se encuentra en uso, todas las aplicaciones subscriptas a él comparten un control de transporte común, y es posible empezar, parar y mover el transporte para cualquiera de ellas.</para> + + <para +>Muchas aplicaciones de audio para Linux soportan el transporte JACK: consulte la documentación de las aplicaciones para mas detalles.</para> + </sect1> + </chapter> + + <chapter id="studio"> + <title +>El Estudio</title> + + <sect1 id="studio-introduction"> + <title +>Dispositivos, instrumentos y conecciones</title> + + <para +>Rosegarden utiliza el término Estudio para referirse a todo lo que conoce sobre los sistemas de sonido de su computadora. Esto puede incluir hardware &MIDI; y de audio, y otros softwares de audio, e incluye información sobre conecciones, configuraciones, parches &MIDI; y demás. El Estudio está dentro de cada composición que cree con Rosegarden.</para> + + <para +>Tres piezas de terminología son esenciales aquí: <variablelist> + + <varlistentry> + <term +>Dispositivo</term> + <listitem> + <para +>Un <quote +>dispositivo</quote +>, a consideración de Rosegarden, es sencillamente algo que es capaz de producir sonidos. Ésto puede ser un dispositivo de audio o MIDI. Los dispositivos MIDI no corresponden necesariamente a un puerto MIDI físico: son sólo cosas con nombres a los que es posible referirse, y de los que se espera que funcionen de cierta manera. Información de configuración como mapas de parches MIDI pueden ser adozadas a los dispositivos. </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>Instrumento</term> + <listitem> + <para +>Cada dispositivo tiene un número de <quote +>instrumentos</quote +>, para los que se asume que cada uno de los cuales tienen un sonido particular. éstas son las cosas a las que se les puede asignar pistas con el fin de elegir que sonido ejecutar. Por defecto, un dispositivo contiene 16 instrumentos, creados parra usted al inicio. Si el dispositivo fuera MIDI, entonces éstos seran inicializados a uno de los 16 canales MIDI. El instrumento es donde se configuran todas las propiedades de una voz en particular, como seteos de programa, reverberación, volumen, etc. </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>Conexión</term> + <listitem> + <para +>Mientras que un dispositivo MIDI es simplemente un nombre y una colección de información de configuración, la <quote +>conexión</quote +> especifica qué puerto MIDI está físicamente vinculado. Esto puede ser configurado en <link linkend="studio-device-editor" +>Composición - Estudio - Gestionar Dispositivos MIDI</link +>. (El Audio y los dispositivos de plugins sintéticos no tienen el mismo tipo de conexiones.) </para> + </listitem> + </varlistentry> + </variablelist> + </para> + + <para +>Por ejemplo, imagina una configuración consistente en una PC con dos puertos MIDI físicos, uno de los cuales tiene un sintetizador externo conectado a éste. Aquí normalmente configurarías Rosegarden para que tuviera un dispositivo MIDI, correspondiente al sintetizador. Podrías luego configurar este dispositivo con el nombre y datos de Banco, Programa y Controladores correspondiente, y luego especificar una conexión para éste que corresponda al puerto pertinente en tu placa de sonido. Cada uno de los 16 instrumentos predeterminados en el dispositivo pueden luego ser configurados con un programa satisfactorio, y luego les asignarías pistas.</para> + + <para +>En la práctica, Rosegarden creará de forma predeterminada un dispositivo por cada una de las conexiones disponibles durante el inicio. Entonces, en el ejemplo anterior, serán creados dos dispositivos MIDI de manera predeterminada incluso si necesitaras sólo uno. Generalmente renombrarías y aplicarías Datos de Banco, Programa y Controladores al primer dispositivo, y borrarías o simplemente no usarías el segundo. Recuerda que no hay un modo actualmente en que Rosegarden pueda saber qué sintetizadores conectaste a los puertos MIDI de tu computadora: por ésta razón, los dispositivos creados durante el inicio intentan ser solamente un set predeterminado, y depende de tí asegurarte de que los dispositivos configurados tengan que ver con los que realmente estás usando. </para> + + <para +>Una vez configurada, la configuración del Estudio es guardada con cada archivo de formato Rosegarden que grabes posteriormente.</para> + + </sect1> + + <sect1 id="studio-device-editor"> + <title +>Gestionando dispositivos MIDI</title> + + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-devicemanager.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>Gestionar Dispositivos MIDI</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + + <para +>El diálogo Gestionar Dispositivos MIDI te muestra los dispositivos MIDI disponibles para tí en este momento y dónde están conectados. Para llegar a éste diálogo, usa <menuchoice +> <guimenu lang="es" +>Composición</guimenu +> <guimenuitem +>Estudio</guimenuitem +> <guimenuitem +>Gestionar Dispositivos MIDI</guimenuitem +> </menuchoice +>. </para> + + <para +>Como se describe en la sección <link linkend="studio-introduction" +>Dispositivos, Instrumentos y Conexiones</link +>, Rosegarden, de forma predeterminada, trata de proveer un plausible set de dispositivos para tí en el inicio, y de hacer conexiones razonables para esos dispositivos. Pero la configuración predeterminada puede no ser siempre satisfactoria y, por eso mismo, éste diálogo te permite renombrar los dispositivos y modificar sus conexiones y dirección de reproducción y grabación. </para> + + <para +>Cada uno de los dispositivos de Reproducción listados aquí provee un destino o target para que las pistas MIDI le puedan hablar: si agregas un nuevo dispositivo de Reproducción, tendrás 16 nuevos instrumentos en este dispositivo al cual le puedes asignar pistas. Si luego asignas una conexión para ese dispositivo, las pistas asignadas a él reproducirán el canal apropiado (dependiendo del instrumento) de cualquier sintetizador MIDI conectado a esa conexión. </para> + + <para +>Los dispositivos de grabación listados aquí representan posibles fuentes para grabar MIDI. Puedes converir en actual uno o más de ellos (entonces Rosegarden los escuchará cuando graba) usando las casillas de chequeo en cada línea, como se muestra en éste diálogo </para> + + </sect1> + + <sect1 id="studio-bank-editor"> + <title +>Administrando bancos y programas para dispositivos MIDI</title> + + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-bankeditor.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>El Editor de bancos y programas MIDI</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + + <para +>Recuerda que cada dispositivo MIDI contienen un número de instrumentos, y que puedes asignar pistas para elegir instrumentos. En términos MIDI, cada instrumento corresponde a un sólo canal en tu sintetizador MIDI. Puedes elegir cuál de las voces disponibles (sonidos) en tu sintetizador usa cada instrumento, pero para hacer ésto, debes dejar que Rosegarden sepa los nombres para todas las voces disponibles. </para> + + <para +>Éste diálogo te permite adjuntar bancos de programas (nombres de voces) a tus dispositivos MIDI, de ese modo permite a cada instrumento en un dispositivo dado ser configurado para usar una de esas voces en la ventana <link linkend="segment-view-instrumentparameterbox" +>Parámetros de Instrumento</link +>. </para> + + <para +>El modo usual para configurar nombres de programas para un dispositivo consiste simplemente en importarlo desde alguno de los archivos de dispositivo dados (".rgd"). Para hacer ésto, selecciona un dispositivo en la lista en la izquierda del diálogo, luego haz click en el botón Importar debajo de la lista, y elige el archivo .rgd correspondiente a tu sintetizador. </para> + + <para +>Si no hay un archivo .rgd actualmente para tu sintetizador, puedes usar éste diálogo para crear un nuevo banco. Para hacer ésto deberás encontrar el mapa de programa en tu Esquema de Implementación MIDI de tu Sintetizador e ingresar todos los nombres a mano: puedes luego exportarlo a un archivo .rgd para compartir con otros usuarios de Rosegarden. </para> + + <sect2 id="studio-soundfonts"> + <title +>SoundFonts(fuentes de sonido)</title> + + <para +>Si sucede que estás usando un sintetizador por software o un sintetizador de placa de sonido que usa archivos SoundFont (.sf2), puedes simplemente cargar los nombres de programa correctos directamente desde tu archivo .sf2 dentro de éste diálogo. Sólo elige Importar normalmente, y luego elige el archivo .sf2 que estás usando, en lugar de un archivo .rgd. </para> + + <para +>Nota que el Estudio sólo maneja información acerca de los dispositivos MIDI existentes paraq Rosegarden, actualmente no maneja tareas como por ejemplo cargar un SoundFont en tu placa de sonido en un primer momento. Si quieres asegurarte que un SoundFont fue cargado en tu placa de sonido cuando Rosegarden inicia, deberías usar la opción especial "Cargar Fuente de Sonidos en la tarjeta SoundBlaster al inicio" </para> + </sect2> + + <sect2 id="studio-variations"> + <title +>Variaciones</title> + + <para +>Algunos dispositivos MIDI (por ejemplo, esos de Roland) organizan sus nombres de programa usando un esquema conocido como "variaciones". Para esos dispositivos, generalmente querrás seleccionar un programa primeramente seleccionado el nombre de programa básico —, como por ejemplo un piano — y luego selecciona uno del set de variaciones en ese programa — como por ejemplo, piano eléctrico. Ésto contrasta con los sintetizadores basados en General MIDI, que organizan sus programas dentro de bancos y esperan que tú elijas un banco en primer lugar, y luego un programa para ese banco. </para> + + <para +>Rosegarden puede soportar dispositivos que usan variaciones, pero todavía tiene que ingresar los nombres de programas en un formato de banco. Internamente, los dispositivos que usan variaciones aún usan selección de controladores por banco MIDI para elegir entre las variaciones; debes encontrar en la documentación de tu sintetizador si tu dispositivo usa selección de banco LSB o MSB para elegir variaciones, y qué número de banco corresponde a qué variación. Puedes luego ingresar los bancos normalmente, y usar "Mostrar lista de Variaciones basada en MSB/LSB" </para> + </sect2> + + <sect2 id="studio-midi-import"> + <title +>Mapeo de programas en &MIDI; importar</title> + <para +>Cuando importas un archivo &MIDI; dentro de una composición, &rosegarden; usa la configuración estudio existente para determinar cómo mapear los programas &MIDI; dentro de los instrumentos de &rosegarden;. Lo que se pretende es asegurarse de que cada programa &MIDI; quede mapeado a un instrumento que realmente exista en tu estudio (y que esté conectado tu PC), así todas las pistas &MIDI; pueden ser escuchadas. </para +><para +>Los cambios de programas &MIDI; y los eventos de selección de bancos encontrados en el archivo importado son usados mientras se importa, pero como un ayuda para ayudar a encontrar el instrumento apropiado para cada pista &MIDI; desde el set de instrumentos en tu estudio. Así, por ejemplo, si tu estudio está actualmente configurado para contener solamente instrumentos <acronym +>GM</acronym +>, y tú importas un archivo &MIDI; con cambios de programa <acronym +>GS</acronym +> dentro de éste, &rosegarden; remapeará los bancos <acronym +>GS</acronym +> de vuelta dentro de <acronym +>GM</acronym +> porque son todos los que conoce que tú tienes al momento de importar el archivo. Rosegarden no recuerda los números de programas <acronym +>GS</acronym +> originales. </para +><para +>Ésto significa que tú deberías siempre asegurarte que tu estudio esté correctamente configurado para los dispositivos que posees actualmente, antes de importar el archivo &MIDI;. De otra manera, los datos de programas en el archivo &MIDI; se perderán. </para> + </sect2> + </sect1> + + <sect1 id="studio-audio-routing"> + <title +>Direccionamiento de Audio</title> + <para +>Cualquier pista de Rosegarden asignada a un instrumento de audio o synth plugin se convierte en parte de la arquitectura de direccionamiento de audio de Rosegarden. Hay 16 instrumentos de audio y 16 instrumentos synth plugin, y cada uno de ellos tiene un set de parámetros ajustables incluyendo nivel del fader (volumen), paneo, efectos, etc. Éstos son configurables generalmente en el diálogo de <link linkend="segment-view-instrumentparameterbox" +>Parámetros de Segmento</link +> o en <link linkend="studio-audio-mixer" +>Mezclador de audio</link +>. Cada instrumento de audio también tiene una conexión de entrada, y ambos instrumentos audio y synth plugin tienen una conexión de salida. </para> + + <para +>Una conexión de entrada de un instrumento define de dónde Rosegarden leerá datos de audio mientras graba en este instrumento. La configuración más usual sería desde una de las conexiones de entrada externas de Rosegarden, cuyo número es configurable en el <link linkend="studio-audio-mixer" +>Mezclador de Audio</link +>. Ésto corresponde a los puertos de audio JACK expuestos por Rosegarden, en los cuales puedes conectar salidas desde cualquier otra aplicación de audio JACK o puertos de captura de placa de sonido usando una aplicación de direccionamiento externo como <ulink url="http://qjackctl.sf.net/" +>QJackCtl</ulink +>. Puedes también configurar una entrada de un instrumento de audio hacia la salida de una de las salidas de submasters o master incorporadas en rosegarden para realizar mezclas. </para> + <para +>Una conexión de salida de instrumento define dónde va el audio cuando se reproduce. De forma predeterminada los instrumentos envían su audio hacia la salida de master de Rosegarden, que es otro par de puertos externos de JACK que pueden ser conectados usando el mismdo direccionador externo de JACK (qjackctl). De todos modos, Rosegarden también soporta hasta ocho buses de submaster internos, hacia los cuales puedes enviar salidas de instrumentos para agruparlos en categorías específicas. Puedes controlar el número de direccionamiento de éstos en el <link linkend="studio-audio-mixer" +>Mezclador de Audio</link +>. </para> + <para +>Actualmente Rosegarden soporta efectos usando un set de slots insert pre-fader para cada instrumento de audio. No puedes aún asignar efectos a los busses de submaster, y Rosegrden no soporta aún enviar efectos, aunque puedes obtener resultados similares usando la arquitectura de efectos externos y mezcla de JACK. </para> + <para +>Algunos detalles más acerca de la configuración del direccionamiento de audio, mezcla y efectos son discutidos en las secciones <link linkend="studio-audio-mixer" +>Mezclador de Audio</link +>, <link linkend="segment-view-instrumentparameterbox" +>Parámetros de Instrumento</link +> y <link linkend="studio-plugins" +>Plugins de Audio</link +>.</para> + </sect1> + + <sect1 id="studio-audio-mixer"> + <title +>El Mezclador de Audio</title> + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-audiomixer.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>El Mezclador de Audio de &rosegarden;</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + + <para +>La ventana de Mezclador de Audio de Rosegarden, a la cual se llega mediante <menuchoice +> <guimenu lang="en" +>Composición</guimenu +> <guimenuitem +>Estudio</guimenuitem +> <guimenuitem +>MEzclador de Audio</guimenuitem +></menuchoice +>, se parece a un mezclador de audio físico (por hardware) y provee un modo de ver y cambiar el estado de un número de instrumentos de audio de una vez. Contiene muchos de los mismos controles tal como se encuentran en audio y synth plugin <link linkend="segment-view-instrumentparameterbox" +>Parámetros de Instrumento</link +>, siendo los más importantes un display de volumen de reproducción y una perilla de volumen (fader) para cada instrumento de audio y synth plugin, como también controles de direccionamiento, paneo, mono/stereo y slots de plugins de efectos. </para> + <para +>La ventana de mezclador de audio es también el lugar en el cual ves y controlas el nivel de volumen de audio de salida del master (bien sobre la derecha en la imagen de arriba), tanto como el nivel de grabación (a la izquierda del fader del master) y los niveles de salida del submaster. </para> + <para +>El menu de <menuchoice +> <guimenu lang="es" +>Preferencias</guimenu +></menuchoice +> del mezclador de audio es particularmente relevante. Además de controlar lo que será mostrado en la ventana del mezclador, éste menú también contiene la configuración del <link linkend="studio-audio-routing" +>Direccionamiento de Audio</link +> para el número de entradas de grabación stereo disponibles y el número de sobmasters. Estas son configuraciones de Estudio que son grabadas con tu archivo de formato Rosegarden.</para> + + <para +>Nota que si actualmente no estás usando ningún submaster (por ejemplo si no hay instrumentos configurados para direccionar sus salidas hacia un submaster) puedes ver una pequeña mejora en la performance si configuras el número de submaster explícitamente a Ninguno, en lugar de mantener submasters en desuso en la configuración. </para> + </sect1> + + <sect1 id="studio-midi-mixer"> + <title +>El Mezclador MIDI</title> + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-midimixer.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>El Mezclador MIDI de &rosegarden;</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + <para +>AL ventana de Mezclador MIDI de Rosegarden, que se alcanza desde <menuchoice +> <guimenu lang="es" +>Composición</guimenu +> <guimenuitem +>Estudio</guimenuitem +> <guimenuitem +>Mezclador MIDI</guimenuitem +></menuchoice +>, provee una forma de ver y editar los <link linkend="segment-view-instrumentparameterbox-midi" +>Valores de parámetros de instrumento</link +> para un número de instumentos MIDI de una sola vez.</para> + + <para +>La ventana está organizada usando un panel de solapas. A lo largo de la parte iferior verás una solapa para cada dispositivo de reproducción MIDI en tu configuración de estudio. Cuando seleccionas una solapa de dispositivo, el resto de la ventana se actualizará para mostrar los controles para los 16 instrumentos de ese dispositivo. </para> + + <para +>Los controles mostrados para cada instrumento son esos que han sido configurados en el administrador de control de parámetros, así como el volumen (correspondiente al controlador de cambio de volumen MIDI, no a la velocidad o MIDI velocity o niveles en dB de audio) y un indicador de nivel aproximado de salida. </para> + </sect1> + + <sect1 id="studio-plugins"> + <title +>Plugins de Audio</title> + <para +>Un plugin (o extensión) de audio es una pieza de software, separada de Rosegarden, que Rosegarden puede cargar y usar con el objetivo de cumplir una tarea particular de procesamiento de audio. Éstas pueden ser ampliamente divididas en plugins de efectos y synth plugins (extensiones de sintetizador). Los plugins de efectos toman una entrada de audio y la manipulan para producir una salida de audio diferente; los synth plugins toman eventos del tipo MIDI como entrada y los convierten salida de audio. Rosegarden usa el API standard para Linux LADSPA para efectos y el API plugin DSSI para los sintetizadores, permitiendo el uso de una gran candidad de plugins de código abierto, que están disponibles gracias al trabajo de muchos desarrolladores. </para> + <para +>El uso de plugins tiene un costo en términos de tiempo de CPU, porque el procesamiento de audio en tiempo real usualmente toma una significante cantidad de trabajo incluso en un moderno CPU. </para> + <sect2 id="studio-plugins-effects"> + <title +>Extensiones de Efectos (plugins de efectos)</title +> <para +>Un plugin de efectos es algo que podés usar para modificar una señal de audio de un modo controlable. Los ejemplos incluyen reverb, delay, comprensión dinámica y así. </para> + <para +>Cada instrumento de audio o synth-plugin en Rosegarden tiene cinco slots de efectos asociados. De forma predeterminada están vacíos, pero puedes cargar plugins dentro de ellos para encadenar hasta cinco efectos dentro de la señal de audio antes de que ésta vaya al procesamiento de nivel de fader (volumen) y paneo.</para> + + <para +>Para cargar un plugin en un slot (o casilla), cliquea su botón en <link linkend="segment-view-instrumentparameterbox-audio" +>Parámetros de Instrumento</link +>: </para> + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-pluginbuttons.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>Botones de Slots de Plugins</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + <para +>(Estos botones están disponibles de forma opcional en la ventana del <link linkend="studio-audio-mixer" +>mezclador de audio</link +>.) </para> + <para +>Haciendo clic en un botón de un plugin desplegarás el diálogo del mismo. Esto te muestra las categorías de efectos disponibles en el primer menú; selecciona uno, y luego puedes seleccionar tu plugin en el segundo menú. </para> + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-plugin-dialog.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>Un diálogo de Plugin de &rosegarden;</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + + <para +>Debajo de los menús, el diálogo te da un número variante de controladores rotatorios mostrando todos los parámetros modificables para el plugin que has seleccionado. Para cambiar el valor, sólo cliquea en una perilla y arrastra el mouse hacia arriba, abajo, izquierda o derecha. (Arriba o a la derecha para elevar el valor, abajo o a la izquierda para bajarlo). Tabién puedes girar la rueda del mouse para cambiar ese valor, o hacer clic con el botón del medio del mouse para resetearla a si valor inicial.</para> + + <para +>También es posible copiar un plugin con su configuración actual dentro de otro slot, para usar las mismas configuraciones de plugins con más de un instrumento, o basar una configuración de plugin en otra. Sólo cliquea en el botón Copy cuando tengas el plugins configurado del modo en tú lo quieres tener, y luego abre otro diálogo de slot de plugin y cliquea en Pegar.</para> + + <para +>Finalmente, puedes checkear la casilla Desviación para que el plugin deje de procesar temporariamente, y a la vez retiene su configuración. </para> + </sect2> + <sect2 id="studio-plugins-synths"> + <title +>Extensiones de Síntesis o Synth Plugins</title> + <para +>Las extensiones de síntesis o Synth Plugins pueden utilizarse en lugar de dispositivos MIDI basados en hardware o software para generar sonidos desde tus segmentos de eventos de notas.</para> + + <para +>Usar una extensión de síntesis (synth plugin) le da un mejor control que usar un dispositivo MIDI externo, debido a que Rosegarden cargara las extensiones correspondientes y usara las configuraciones correctas la próxima vez que utilice el mismo archivo. Las extensiones también pueden ofrecer una mejor resolución temporal que un dispositivo MIDI externo; y los instrumentos sintetizados tienen la ventaja de ser ruteables como instrumentos de audio, lo que significa que usted puede agregar efectos por arriba de ellos </para> + + <para +>Para utilizar una extensión de síntesis (synth plugin), primero <link linkend="segment-view-instruments" +>asigne una pista</link +> a un instrumento y luego cargue una extensión de síntesis (synth plugin) cliqueando en el botón de mas arriba en el <link linkend="segment-view-instrumentparameterbox-synth" +>cuadro de dialogo parámetros de instrumento</link +>:</para> + + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-synthpluginbuttons.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>Botones de Extensiones de Síntesis</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + + <para +>Esto abrirá la misma caja de dialogo que la mostrada anteriormente para los efectos, pero con una lista de sintetizadores. Una vez mas vera el conjunto particular de parámetros rotativos para el sintetizador seleccionado. Los sintetizadores también pueden tener "programs", seleccionables desde un menú --este menú solo aparecerá si ha elegido un sintetizador que los soporta. Cuando seleccione y configure una extensión para un instrumento, cualquier dato MIDI o pistas asignadas a ese instrumento deberían reproducirse a través de ese sintetizador y debería recibir datos MIDI durante el monitoreo o grabación. </para> + </sect2> + + <sect2 id="studio-plugins-guis"> + <title +>Ventanas del editor nativo de extensiones</title> + + <para +>La mayoría de las extensiones pueden ser controladas completamente usando los controles rotativos en el cuadro de dialogo de extensión de Rosegarden. Sin embargo, algunas de ellas (generalmente sintetizadores) también tienen su propia ventana de edición que puede ser activada o no desde Rosegarden y que puede proveer controles mas completos u organizados.</para> + + <para +>Cuando se selecciona una extensión que tiene su propia ventana de edición, el botón en la esquina inferior izquierda del cuadro de dialogo llamada "Editor" se activara:</para> + + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-plugineditorbutton.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>Un botón de edición de la extensión</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + + <para +>(para los sintetizadores, existe un botón similar en el cuadro de dialogo parámetros de instrumento.) Al cliquear este botón aparece la ventana de edición del sintetizador. Cualquier cambio que haga en esta ventana de edición también debería verse reflejado en el cuadro de dialogo de la extensión de Rosegarden, si esta visible, y por supuesto debería guardarse normalmente en su archivo de Rosegarden.</para> + </sect2> + </sect1> + + <sect1 id="studio-metronome"> + <title +>Metrónomos</title> + <para +>Rosegarden tiene dos metrónomos incorporados, uno para usar durante la grabación y otro que puede encenderse durante la reproducción normal. Trabajan enviando notas a un instrumento MIDI y ambos metrónomos usan la misma información de instrumento, tono y velocidad. </para> + + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-metronome.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>Configuración del metrónomo de &rosegarden;'</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + <para +>Para configurar los metrónomos, use <menuchoice +> <guimenu lang="en" +>Composition</guimenu +> <guimenu lang="en" +>Studio</guimenu +> <guimenuitem +>Manage Metronome</guimenuitem +> </menuchoice +> para abrir el cuadro de dialogo metrónomo. Aquí puede elegir un instrumento MIDI para el metrónomo y elegir la resolución del mismo (si es un tick por beat, uno por subdivisión de beat o solo uno por barra), el tono y la velocidad. Propiedades como la voz actual utilizada por el sintetizador MIDI para el tick del metrónomo dependen del instrumento elegido, así como la voz utilizada por una pista MIDI depende del instrumento asignado a esa pista. Puede configurar el instrumento asignándole una pista en la ventana principal y eligiendo el programa correcto en los parámetros del instrumento. </para> + + <para +>Los metrónomos de grabación y reproducción pueden ser activados desde la ventana Transporte, usando el botón metrónomo. Este botón controla el metrónomo de grabación cuando hay una grabación armada o en progreso y el metrónomo de reproducción en los demás casos. Por omisión el metrónomo de grabación esta activado, no así el de reproducción. </para> + + <para +>Rosegarden también tiene un "visual metronome": la ventana Transporte puede parpadear para marcar cada beat. Vea <link linkend="transport" +>la sección Transporte</link +> para mas detalles.</para> + </sect1> + + <sect1 id="studio-midi-filters"> + <title +>Filtros MIDI</title> + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-midifilter.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>El cuadro de dialogo Filtro MIDI</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + + <para +>Usando este cuadro de dialogo puede decidir que eventos MIDI ignorara o aceptara Rosegarden, ya sea al reenviar eventos a través de MIDI THRU o simplemente al grabarlos. Utilice las casillas de verificación para decirle a Rosegarden que tipo de eventos MIDI no quiere reenviar o grabar. </para> + + </sect1> + + </chapter> + + + <chapter id="segment-instrument-parameters"> + <title +>Parámetros de Segmento e Instrumento</title> + + <sect1 id="segment-view-segmentparameterbox"> + <title +>El Cuadro de Dialogo Parámetro de Segmento</title> + + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-segmentparameterbox.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>el cuadro de dialogo parámetro de segmento de &rosegarden;</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + + <para +>El cuadro de dialogo Parámetro de Segmento se ubica a la izquierda de la ventana principal de Rosegarden. (Si no puede verla, intente usar <menuchoice +> <guimenu lang="en" +>Settings</guimenu +> <guimenuitem +>Show Segment and Instrument Parameters</guimenuitem +> </menuchoice +>.) Esto permite modificar algunos aspectos de los segmentos elegidos.</para +><para +>Si se selecciona un único segmento, sus parámetros serán mostrados en el cuadro de dialogo y pueden ser editados allí mismo. Si se eligen múltiples segmentos, el cuadro de dialogo solo mostrara los valores actuales que son iguales para todos los segmentos - pero todavía puede editarlos y sus cambios se aplicaran a toda la selección. <variablelist> + <varlistentry> + <term +>Etiqueta</term> + <listitem> + <para +>Muestra la etiqueta del segmento elegido (o segmentos, si todos tienen la misma etiqueta). Cliquee el botón "..." para editarla.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>Repetir</term> + <listitem> + <para +>Activa o desactiva la repetición de los segmentos elegidos. Un segmento se repetirá hasta el comienzo del segmento siguiente de la misma pista, o hasta el final de la composición si no es seguido por ningún otro segmento.</para> + + <para +>Las partes repetidas de un segmento repetido se muestran en el cuadro principal en un color mas tenue que el segmento original. Puede transformarlo en copias reales editables del segmento original ya sea usando <menuchoice +> <guimenu lang="en" +>Segments</guimenu +> <guimenuitem +>Turn Repeats into Copies</guimenuitem +> </menuchoice +>, o simplemente haciendo doble click en los bloques individuales repetidos.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>Cuantificar</term> + <listitem> + <para +>Muestra la configuración de cuantificación para los segmentos elegidos. Puede cambiar esto para cuantificar rápidamente los comienzos de todas las notas. Para una cuantificación mas avanzada, utilice <menuchoice +> <guimenu lang="en" +>Segments</guimenu +> <guimenuitem +>Quantize...</guimenuitem +> </menuchoice +>. Vea <link linkend="quantization" +>Cuantificación</link +> para mas detalles. </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>Transponer</term> + <listitem> + <para +>Muestra la transposición (en semitonos) actualmente aplicada a los segmentos elegidos. Esta transposición es aplicada cuando el segmento es reproducido y no se muestra en las notas de los editores de matriz, notación o eventos. Puede utilizar esto para cambiar rápidamente el tono de una parte o toda la composición.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>Retardo</term> + <listitem> + <para +>Muestra el retardo actualmente en efecto en los segmentos seleccionados. Puede fijar un retardo aquí para provocar que un segmento completo se reproduzca mas tarde que lo previsto. Este retardo es aplicado en la reproducción del segmento y no se muestra en las notas de los editores de matriz, notación o eventos. </para> + <para +>Puede fijar un retardo ya sea en tiempo musical (eligiendo la duración de una nota en el menú desplegable), en cuyo caso el retardo exacto dependerá del tempo; o en tiempo real (eligiendo una duración en milisegundos en el menú desplegable). </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>Color</term> + <listitem> + <para +>Muestra el color utilizado para mostrar los segmentos seleccionados. Puede elegir otro color en el menú desplegable, o elegir la opción "Add New Colour" si desea un color que no esta en el menú. </para> + <para +>También puede administrar y renombrar colores usando <menuchoice +> <guimenu lang="en" +>Composition</guimenu +> <guimenuitem +>Edit Document Properties...</guimenuitem +> </menuchoice +> (luego elija la página Color en el cuadro de dialogo propiedades de documento). La paleta de colores modificada se guardara con la composición en el archivo de Rosegarden. <screenshot +> <mediaobject> + <imageobject> + <imagedata fileref="rg-colours.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>Administrador de color de &rosegarden;'</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + </listitem> + </varlistentry> + + </variablelist> + </para> + </sect1> + + <sect1 id="segment-view-instrumentparameterbox"> + <title +>El Cuadro de Dialogo Parámetro de Instrumento</title> + <para +>El cuadro de dialogo Parámetro de Instrumento se encuentra en la esquina inferior izquierda de la ventana principal de Rosegarden, debajo de <link linkend="segment-view-segmentparameterbox" +>Cuadro de dialogo Parámetro de Segmento</link +>. (Si no puede verla, pruebe usando <menuchoice +> <guimenu lang="en" +>Settings</guimenu +> <guimenuitem +>Show Segment and Instrument Parameters</guimenuitem +> </menuchoice +>.)</para> + + <para +>Le muestra que instrumento esta asignado a la pista actual y contiene todos los controles editables para ese instrumento. Recuerde que debido a que se puede asignar cualquier cantidad de pistas al mismo instrumento, la configuración de este cuadro de dialogo puede afectar a mas de una pista a la vez.</para> + + <para +>La disposición y los contenidos del cuadro de dialogo parámetro de instrumento depende del tipo de instrumento: MIDI, audio o sintetizador. </para> + + <sect2 id="segment-view-instrumentparameterbox-midi"> + <title +>Parámetros de Instrumento MIDI</title> + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-ipb-midi.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>cuadro de dialogo parámetro de instrumento de &rosegarden; para un instrumento MIDI</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + <para +>Cuando selecciona una pista asignada a un instrumento MIDI, el cuadro de dialogo parámetro de instrumento muestra los parámetros MIDI </para> + <para +>En la parte superior, este cuadro de dialogo muestra el nombre del instrumento y la conexión que esta utilizando el dispositivo. </para> + <para +>Debajo, puede ver y editar el numero de canal MIDI y la configuración <link linkend="studio-bank-editor" +>bank and program</link +> que deben ser enviadas al instrumento al comienzo de la reproducción (incluyendo un "percussion" toggle que controla cuando se deben ofrecer solo programas de percusión en estas configuraciones).</para> + + <para +>Finalmente este cuadro de dialogo le muestra los controladores disponibles para este dispositivo (aquellos para un dispositivo General MIDI son mostrados arriba). Cualquier ajuste que haga aquí sera enviado al canal del instrumento al comienzo de la reproducción.</para> + </sect2> + + <sect2 id="segment-view-instrumentparameterbox-audio"> + <title +>Parámetros de Instrumento de Audio</title> + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-ipb-audio.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>cuadro de dialogo parámetro de instrumento de &rosegarden;' para un instrumento de audio</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + <para +>Cuando selecciona una pista de audio, el cuadro de dialogo parámetro de instrumento muestra los parámetros de audio. </para> + <para +>El cuadro de dialogo tiene dos atenuadores, uno con contorno azul para el nivel de reproducción y otro con contorno rojo para el nivel de grabación de este instrumento. Entre ellos hay un medidor de nivel de reproducción. </para> + <para +>Los dos menús en la parte superior se usan para seleccionar el ruteo de entrada y salida de audio para este instrumento. Debajo de ellos puede seleccionar si el instrumento es mono o estéreo y el ajuste panorámico de la posición en el campo estéreo. (Los instrumentos de audio son siempre estéreo, debido a que el ajuste panorámico siempre se aplica. Pero si cambia el instrumento a mono, reducirá cualquier salida de datos o efectos a mono antes de aplicar la panorámica.) </para> + <para +>La columna de cinco botones abajo a la izquierda son las ranuras de efectos. Haga click en ellas para seleccionar y activar efectos para este instrumento y para controlarlos usando el editor de extensiones. Estos son efectos de inserción, aplicados en orden de abajo hacia arriba después del atenuador y la panorámica. </para> + </sect2> + + <sect2 id="segment-view-instrumentparameterbox-synth"> + <title +>Parámetros de Sintetizador</title> + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-ipb-synth.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>el cuadro de dialogo parámetro de instrumento de &rosegarden; para un sintetizador</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + <para +>Cuando selecciona una pista asignada a un sintetizador, el cuadro de dialogo parámetro de instrumento muestra sus parámetros. Notara que si bien una pista de sintetizador usa segmentos con datos MIDI, en términos de control y ruteo se comporta como una pista de audio. </para> + <para +>El control mas importante aquí es el botón arriba a la izquierda (el que dice Xsynth en la figura de arriba) que muestra el nombre del sintetizador en uso por este instrumento. Haga click allí para elegir un sintetizador en particular y controlarlo en el editor de extensiones estándar de Rosegarden. Una vez que eligió la extensión, debería poder cliquear el botón Editor para abrir un editor para esa extensión (si tiene uno). </para> + <para +>Los controles restantes son iguales a los de los instrumentos de audio: el atenuador, el nivel de reproducción, el ruteo de salida, los ajustes mono/estereo y panorámicos así como las ranuras de efectos son exactamente iguales.</para> + </sect2> + + </sect1> + </chapter> + + <chapter id="quantization"> + <title +>Cuantificación</title> + <para +>"Quantization" es el proceso de reposicionar notas y otros eventos de manera que comiencen o terminen en divisiones rítmicas exactas. Se utiliza tradicionalmente para transformar una ejecución aproximada en una precisa pero de sonido mecánico - ya sea porque se busca precisión o para hacer las notas mas claras en la notación. </para> + + <para +>Para cuantificación general, utilice <menuchoice +> <guimenu lang="en" +>Segments</guimenu +> <guimenuitem +>Quantize</guimenuitem +> </menuchoice +> en la ventana principal o <menuchoice +> <guimenu lang="en" +>Adjust</guimenu +> <guimenuitem +>Quantize</guimenuitem +> </menuchoice +> en los editores de matriz o notación. Esto le muestra un cuadro de dialogo en donde puede elegir los parámetros precisos de cuantificación que necesita, que luego se aplican a todos los segmentos o notas. (También puede abrir rápidamente este cuadro de dialogo presionando la tecla "=".) </para> + + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-gridquantizer.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>Cuadro de diálogo de cuantificación de &rosegarden;</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + + <para +>El cuadro de dialogo de cuantificación ofrece una selección de cuantificadores, cada uno con su propio conjunto de parámetros. Los cuantificadores disponibles son: </para> + <variablelist> + + <varlistentry> + <term +>Cuantizador de Grilla</term> + <listitem> + <para +>El cuantizador de grilla mueve los tiempos de inicio de las notas haciendo que èstos inicien en el punto más cercano de la grilla (definido por varios parámetros del cuantizador). Aquellas notas que inicialmente varían en el inicio, serán alineadas por el cuantizador, logrando un resultado más preciso y mecánico </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>Cuantizador de ligados</term> + <listitem> + <para +>EL cuantizador de ligados funciona como una simple cuantización por grilla, pero además ajusta la duración de las notas y remueve los silencios o cortes entre ellas extendiendo cada nota hasta el comienzo de la siguiente. También puede obtener este efecto de ligado sin usar la cuantización de grilla usando la función <menuchoice +> <guimenu lang="en" +>Adjust</guimenu +> <guimenuitem +>Quantize</guimenuitem +> <guimenuitem +>Legato</guimenuitem +> </menuchoice +> en el editor de matriz </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>Cuantizador de notación heurística</term> + <listitem> + <para +>El cuantizador de notación heurística intenta ajustar los tiempos de inicio y duración de las notas para producir una notación leíble. Ver <link linkend="nv-quantization" +> Notación desde datos de ejecución </link +> para una descripción de este cuantizador y sus usos.</para> + </listitem> + </varlistentry> + + </variablelist> + + <para +>El cuanizador de grilla tiene los siguientes parámetros:</para> + <variablelist> + + <varlistentry> + <term +>Unidad base de grilla</term> + <listitem> + <para +>Esta es la medida de la grilla usada para la cuantización. </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>Ritmo</term> + <listitem> + <para +>Este es un porcentaje de la figura la cual ajusta el grado de cuantización de los tiempos "late".</para> + <para +>Si se setea en Ninguno (por defecto), la cuantización será siempre espaciada en la grilla de acuerdo a la unidad base de grilla</para> + <para +>Si se setea al 100%, cada segunda línea en la grilla será ubicada a dos tercios de la distancia entre la previa y las siguientes, en vez de sólo la mitad. Esto dará por resultado que las notas serán cuantizadas a la primera y tercera figura de un tresillo </para> + <para +>Otros seteos producirán variaciones proporcionales de grado de ritmo. También es posible setear este parámetro a figuras negativas (para que algunos tiempos comiencen antes) o para figuras mayores que 100%.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>Suma iterativa</term> + <listitem> + <para +>El comportamiento por defecto de el cuantizador de grilla es mover cada nota exactamente sobre la línea de la grilla más cercana. Pero si se configura la suma iterativa a algo menos que el 100% (el "Cuantización completa" por defecto), cad nota será corrida el porcentage propicio de la distancia a su línea más cercana, resultando un cercano-pero-no-del todo efecto de cuantización</para> + <para +>Este cuantizador debe ser aplicado repetidamente para ir probando gradualmente incrementos en el grado de cuantización, de allí en nombre "iterativo". Usando <menuchoice +> <guimenu lang="en" +>Adjust</guimenu +> <guimenuitem +>Quantize</guimenuitem +> <guimenuitem +>Repeat Last Quantize</guimenuitem +> </menuchoice +> en el editor de Matriz se logra el mismo resultado </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>Duración de cuantización además de tiempos de inicio</term> + <listitem> + <para +>Si esta opción está habilitada, el cuantizador cuantizará las notas' tiempo de finalización a la misma grilla que los tiempos de inicio </para> + </listitem> + </varlistentry> + </variablelist> + + <para +>El diálogo de cuantización tiene además una sección Avanzada conteniendo opciones adicionales para <link linkend="nv-quantization" +>cuantización de notas</link +>. </para> + + <para +>Otra simple manera de aplicar una cuantización de grilla es hacerlo en la ventana principal, usando el <guimenuitem +>Quantize</guimenuitem +> menú en la <link linkend="segment-view-segmentparameterbox" +>Caja de Parámetros de Secciones</link +>. Si se seleccionan algunas secciones y se cambia el valor mostrado en el menú, la selección entera será automáticamente cualtizada a la resolución mostrada en el menú </para> + + <para +>Finalmente, Hay también un <link linkend="matrix-grid-quantize" +>control de cuantización</link +> en la vista de matriz.</para> + + </chapter> + + <chapter id="matrix-view"> + <title +>El editor de matriz</title> + <para +>El editor de matriz de &rosegarden; permite ver y editar música de una forma simple y lógica: cada nota es representada por un bloque en una grilla, a una altura correspondiente con el tono. </para> + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-matrixview.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>El editor de matriz de &rosegarden;</phrase> + </textobject> + </mediaobject> +</screenshot +> cada ventana del editor de matriz muestra un sólo segmento o sección. Para editar alguna de ellas, simplemente se hace un clic derecho en el cuadro principal y se selecciona el editor de matriz desde el menú. De otra manera, se puede configurar Rosegarden para que el editor de matriz se abra por defecto al hacer doble clic sobre alguna sección. </para> + + <sect1 id="matrix-grid-quantize"> + <title +>Los controles de Grilla y Cuantización</title> + <para +>La vista de matriz contiene los menúes de Grilla y Cuantización en su barra de herramientas principal. </para> + <para +>El menú de Grilla controla el tamaño de la grilla visible en segundo plano de la vista de matriz, así como también la resolución del tiempo usada cuando se ingresan y se mueven notas. Luego que se setea a un tiempo particular, la inserción común de notas y las operaciones de copiado y pegado se acomodarán automáticamente a esos espacios de tiempo. Se puede obviar este efecto temporariamente manteniendo apretada la tecla Shift durante la edición, o se puede desabilitar poniendo el menú de Grilla en Ninguno. </para> + <para +>El menú de Cuantización trabaja de manera diferente. En lugar de controlar el comportamiento de otras herramientas de edición, interpreta una acción. Cuando se cambia el valor en este menú, las notas seleccionadas -- o el segmento entero si niguna es seleccionada -- inmediatamente será cuantizada usando el cuantizador de grilla de la resolución elegida. </para> + <para +>El menú de Cuantización también muestra continuamente a qué resolución está cuantizado el segmento actual. Por ejemplo, si se seleeciona un grupo de notas que empiezan en negras consecutivas, el menú de Cuantización se actualizará y mostrará 1/4, por ser la resolución más común resultante de la actual selección. </para> + </sect1> + + <sect1 id="matrix-insertion"> + <title +>Insertando notas</title> + <para +>La manera más simple de insertar una nota en la vista de matriz es usando el mouse. Para hacerlo, primero se selecciona la herramienta lápiz en la barra de herramientas, y luego se cliquea y arrastra en el editor de matriz. La nota será ingresada al tiempo y la altura correspondiente a lo que se ha cliqueado, y la duración de la nota dependerá de la distancia que se arrastre antes de soltar el botón del mouse.</para> + + <para +>Por defecto, el tiempo y la duración están relacionadas con una unidad particular de la unidad de grilla, de acuerdo a la configuración de Grilla en menú Ver o la barra de herramientas. Se puede prevenir este efecto manteniendo apretada la tecla Shift mientras se cliquea y arrastra </para> + + <sect2 id="matrix-insertion-keyboard"> + <title +>Tipeando notas con el teclado de la PC</title> + + <sect3> + <title +>Duración</title> + + <para +>La duración de las notas ingresadas con el teclado están controladas por el seteo de Grilla en el menú Ver o la barra de herramientas. Se puede editar usando las teclas numéricas:</para> + + <itemizedlist> + <listitem +><para +><keycap +>5</keycap +> – Compás entero</para +></listitem> + <listitem +><para +><keycap +>1</keycap +> – Un tiempo</para +></listitem> + <listitem +><para +><keycap +>2</keycap +> – 1/2 (Blanca)</para +></listitem> + <listitem +><para +><keycap +>4</keycap +> – 1/4 (Negra)</para +></listitem> + <listitem +><para +><keycap +>8</keycap +> – 1/8 (Corchea)</para +></listitem> + <listitem +><para +><keycap +>6</keycap +> – 1/16 (Semicorchea)</para +></listitem> + <listitem +><para +><keycap +>3</keycap +> – 1/32 (Fusa)</para +></listitem> + <listitem +><para +><keycap +>0</keycap +> – 1/64 (Semifusa)</para +></listitem> + </itemizedlist> + + </sect3> + + <sect3> + <title +>Tono / Altura</title> + + <para +>Una vez que se ha seleccionado la duración en el menú Grilla, se procede a insertar la nota en la posición actual <link linkend="nv-rulers" +>del cursor</link +> presionando una de las teclas de tono </para> + + <itemizedlist> + <listitem +><para +><keycap +>A</keycap +> – Do (la tónica de la escala en la actual tonalidad) </para +></listitem> + <listitem +><para +><keycap +>S</keycap +> – Re</para +></listitem> + <listitem +><para +><keycap +>D</keycap +> – Mi</para +></listitem> + <listitem +><para +><keycap +>F</keycap +> – Fa</para +></listitem> + <listitem +><para +><keycap +>J</keycap +> – Sol</para +></listitem> + <listitem +><para +><keycap +>K</keycap +> – La</para +></listitem> + <listitem +><para +><keycap +>L</keycap +> – Si</para +></listitem> + </itemizedlist> + + <para +>manteniendo apretada la tecla <keycap +>Shift</keycap +> mientras se pulsa una tecla agregaremos un sostenido (#) a esa nota (salvo Mi y si que no lo tienen) y manteniendo apretada <keycap +>Shift</keycap +> y <keycap +>Ctrl</keycap +> juntas la alteraremos con un bemol (b) (excepto para Fa y Do).</para> + + <para +>Para ingresar notas una octava más alta, se deben usar las teclas de la fila superior: <keycap +>Q</keycap +>, <keycap +>W</keycap +>, <keycap +>E</keycap +>, <keycap +>R</keycap +>, <keycap +>U</keycap +>, <keycap +>I</keycap +>, y <keycap +>O</keycap +>. Asimismo, para notas una octava más baja, usar <keycap +>Z</keycap +>, <keycap +>X</keycap +>, <keycap +>C</keycap +>, <keycap +>V</keycap +>, <keycap +>B</keycap +>, <keycap +>N</keycap +> y <keycap +>M</keycap +>.</para> + + </sect3> + + <sect3> + <title +>Otras observaciones</title> + + <para +>Todos los comandos de inserción están también disponibles en un submenú del menú Herramientas. Es improbable que para ingresar una nota se deba navegar por todo un menú, pero el menú muestra los atajos de teclado y provee una útil referencia en caso de que las combinaciones de teclas sean olvidadas.</para> + + <para +>Los atajos de teclado están designados para ser usados con una disposición QWERTY. No hay aún una forma de mapear las teclas para otros diseños de teclado, lo que se puede hacer es reasignar tecla por tecla usando <menuchoice +> <guimenu lang="en" +>Settings</guimenu +> <guimenuitem +>Configurar atajos......</guimenuitem +> </menuchoice +>.</para> + + </sect3> + + </sect2> + + <sect2 id="matrix-insertion-midi"> + <title +>Ingresando notas a través de un teclado MIDI</title> + + <para +>Se pueden ingresar notas una por vez en el editor de matriz usando un teclado MIDI o cualquier dispositivo de control MIDI. El editor matricial usa las notas que se ejecutan en el teclado, pero la duración de las mismas se seleccionan en el editor de Grilla. Esto es conocido como "grabación por pasos". </para> + + <para +>Para ingresar las notas a través de un teclado MIDI, primero hay que confirmar que el teclado está configurado como el dispositivo MIDI predeterminado. Verificar que esté configurado correctamente el seteo de la Grilla en el menú Ver o la barra de herramientas, como los controles de duración de las notas. Entonces se presiona el botón de grabación por pasos en la barra de herramientas del editor de matriz, o se selecciona Grabación por pasos desde el menú Herramientas. A partir de allí, todas las notas presionadas en el teclado MIDI serán insertadas en la posición actual en la ventana, hasta que la grabación por pasos se termine, o se cambie de ventana, o se cierre la misma. </para> + + <para +>Es posible cambiar la configuración de la Grilla mientras se está grabando, para poder ingresar notas de diferente duración. </para> + </sect2> + </sect1> + + <sect1 id="matrix-selection"> + <title +>Seleccionando notas</title +> <para +>Para seleccionar notas en el editor de matriz, cambiar a la herramienta de Selección (flecha) y dibujar un área rectangular abarcando las notas requeridas. Los elementos seleccionados se resaltarán en azul. Si se cliquea en un solo evento, sólo ese evento será seleccionado. </para +><para +>Si se mantiene apretada la tecla <keycap +>Shift</keycap +> mientras se arrastra o se cliquea, la nueva selección será adicionada a una existente en lugar de reemplazarla. </para> + + <para +>Para deseleccionar un área, cliquear en un espacio vacío del editor matricial, o pulsar la tecla Escape.</para> + + <para +>También es posible seleccionar todas las notas de una determinada altura, presionando Shift + clic y arrastrando para seleccionar una rango de notas. Esta selección es agregada a una preexistente, por lo que si se necesita una selección limpia, hay que deseleccionar la previa antes. </para> + </sect1> + + <sect1 id="matrix-editing"> + <title +>Moviendo y copiando notas</title> + <para +>Se puede mover notas en altura y posición en el editor de matriz, cliqueando y arrastrando con la herramienta Mover, o seleccionando primero con la herramienta de selección y luego arrastrando. </para> + <para +>Para copiar notas, seleccionarlas primero y luego usar las funciones habituales de copiar y pegar. Luego de pegadas, las notas pueden ser ubicadas allí donde se las necesitare. </para> + </sect1> + + </chapter> + + <chapter id="notation-view"> + <title +>El Editor de Partituras</title> + + <!-- Introduction, purpose --> + + <sect1 id="nv-introduction"> + <title +>introducción</title> + + <para +>El editor de partituras de Rosegarden permite ver y editar en la forma tradicional de partituras </para +><para> + + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-notationview.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>Editor de partituras Rosegarden</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + <para +>Rosegarden pretende presentar partituras con la mejor distribución posible compatible con la función de secuenciador. Esto significa que soporta acordes, superposiciones y grupos anidados, tresillos y arbtrarios, notas de adorno, dinámicas, acentos y demás, no provee mucho control fino sobre la disposición (especialmente en música con contrapuntos) como un programa específico de edición de partituras. Rosegarden no pretende ser un editor de partituras de calidad, pero permite exportar en formato lilypond, lo cual es una buena base para la publicación. </para> + </sect1> + + <!-- Single and multiple staffs, and "current staff" --> + + <sect1 id="nv-staffs"> + <title +>Partituras simples y múltiples</title> + + <para +>Hay tres maneras de abrir el editor de partituras desde la ventana principal de Rosegarden. (Todas ellas requieren que haya segmentos ya insertados en la ventana principal, por lo que si se está comenzando una nueva composición, deberían crearse segmentos antes de pensar en esitarlos. <variablelist> + + <varlistentry> + <term +>Doble clic en los segmentos</term> + <listitem> + + <para +>La manera más obvia es hacer doble clic en un segmento en el tablero principal. Esta acción abre el segmento en el editor que se haya configurado por defecto (partituras, matriz o lista de eventos), y por omisión está configurado el editor de partituras. Así es que si se hace doble clic en un determinado segmento abrirá éste como un pentagrama solitario en el editor de partituras.</para> + + <para +>Es posible además abrir el editor con varias líneas de pentagrama, manteniendo la tecla Shift, seleccionar los segmentos que se desean editar (con un solo clic del mouse) pero doble clic en el último. Todos los segmentos serán abiertos juntos en una ventana del editor</para> + + </listitem> + </varlistentry> + + <varlistentry> + <term +>La función de Abrir en el Editor por Defecto (La tecla Enter)</term> + <listitem> + + <para +>la tecla Enter es un atajo para la función Abrir en el Editor por Defecto, que hace lo mismo que un cliqueo doble: abre los segmentos actualmente seleccionados en el editor de partituras, o en el que se haya preseleccionado como editor por omisión. </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>Las funciones del menú Abrir en el Editor de Partituras</term> + <listitem> + + <para +>Alternativamente, se puede usar la función de Abrir en el Editor de Partituras en los menúes de los Segmentos o con el menú contextual (botón derecho del mouse) sobre un segmento en el tablero principal. Se seleccionan primero los segmentos a editar (cliqueando + Shift como se ha dicho anteriormente, o usando la función Seleccionar Todo) y lo seleccionado se abre en el Editor de Partituras.</para> + </listitem> + + </varlistentry> + </variablelist> + + </para> + + <para +>Si se tiene más de una línea de pentagrama (por ejemplo en un segmento) visible en el editor de partiturasm sólo una de ellas podrá ser la editable a la vez. La que lo sea será distinguible por tener el cursor de ingreso en ella (ver <link linkend="nv-rulers" +>Reglas y Cursores</link +>) y ésta será el pentagrama en el cual tomarán lugar los eventos de edición. Por omisión, la línea superior es la actualmente editable, pero es seleccionable presionando Ctrl + cliqueando en la línea deseada o usando las funciones Mover el Cursor al Pentagrama Superior y Mover el Cursor al Pentagrama Inferior del menú de funciones. </para> + + </sect1> + + <!-- Linear and page layouts --> + + <sect1 id="nv-layout"> + <title +>Distribuciones lineales y de página</title> + + <para +>La manera usual de presentación del editor de partituras es conocida como distribución Lineal: una línea de pentagrama sobre la otra, en las cuales, cada pentagrama es una línea horizontal. Algunas funciones del editor (como la <link linkend="nv-rulers" +>Reglas</link +>)solamente están disponibles en la distribución Lineal. </para> + + <para +>De todos modos, se puede mostrar las partituras en dos diferentes distribuciones: Página Continua y Páginas Múltiples.</para> + + <para +>En la vista de Página Continua, la música es ubicada en una infinita página del ancho de la ventana. Cada pentagrama se corta al final de una línea, empezando una nueva línea debajo de los restantes pentagramas.</para> + + <para +>En la distribución de Página Múltiple, la música es dividida en páginas reales, tantas como serán impresas. El tamaño de cada página es calculado aproximadamente al valor de la música que completará cada línea cuando sea impresa (de acuerdo al tamaño de puntos especificado en la resolución de la impresora en el cuadro de configuración). La versión impresa será no todo lo igual que se quisiera, pero bastante aproximada si se usa papel tamaño A4.</para> + + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-notationview-multipage.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>El editor de partituras Rosegarden en la vista de Página Múltiple</phrase> + </textobject> + </mediaobject> + </screenshot> + </para +><para +>La mayoría, pero no todas las funciones, funcionan igual de bien en las vistas de página tanto como en la lineal. </para> + + <para +>Para cambiar entre estas vistas, se debe usar las funciones del menú, Vista Lineal, Vista de Página Continua y Vista de Múltiples Páginas </para> + </sect1> + + <!-- Rulers and Cursors --> + + <sect1 id="nv-rulers"> + <title +>Reglas y cursores</title> + + <para +>El editor de partituras de Rosegarden incluye dos reglas y dos cursores. Las reglas están graduadas y ubicadas en las tiras horizontales, arriba y debajo del tablero principal, y los cursores son las líneas verticales de color que se muestran inicialmente al principio del pentagrama superior en el editor. </para> + + <para +>El cursor púrpura es el cursor de inserción. Muestra el punto en el cual tomarán lugar las operaciones tales como copiar y pegar. Se puede ubicar el cursor de inserción cliqueando o arrastrando sobre la regla superior, o cliqueando con la herramienta de selección en una parte vacía del pentagrama (evitando los eventos), o cliqueando en cualquier lugar mientas se mantiene apretada la tecla <keycap +>Ctrl</keycap +>. </para> + + <para +>También es posible usar las flechas derecha e izquierda para mover el cursor de ingreso un evento a la vez. Si se mantiene apretada la tecla <keycap +>Ctrl</keycap +> mientras se presionan las teclas de flechas, el cursor se moverá un compás a la vez; si se presiona Shift el cursor <link linkend="nv-tools-selections" +>seleccionará los eventos</link +> mientras pasa sobre ellos. </para> + + <para +>El cursor azul es el puntero de reproducción. Tal cual los homónimos en la ventana principal y en las vistas de matriz, muestra la posición actual de la reproducción o grabación en curso. Puede ser reposicionado usando la regla inferior. </para> + + <para +>Nótese que las reglas son mostradas únicamente en el modo <link linkend="nv-layout" +>Distribución Lineal</link +>. </para> + + </sect1> + + <!-- Display conventions (annotated picture with some selected notes, + some quantized notes, a bar of incorrect length etc) --> + + <!-- Tools and Selections --> + + <sect1 id="nv-tools-selections"> + <title +>Herramientas y selecciones</title> + <para +>La mayoría de las funciones y herramientas de edición del menú del Editor de Partituras de Rosegarden se ubican en tres categorías: <quote +>herramientas</quote +>, <quote +>funciones que afectan selecciones</quote +>, y <quote +>operaciones de arrastre.</quote +>. </para> + + <variablelist> + <varlistentry> + <term +>Herramientas</term> + <listitem> + <para +>Las herramientas básicas son la de selección, la de borrado y aquellas para insertar notas y silencios, a las cuales se acceden desde los botones de la barra de herramientas. Eligiendo una herramienta cambian los comportamientos por defecto de los botones del mouse en la ventana principal, hasta que otra herramienta es escogida. Por ejemplo, eligiendo la herrramienta de seleccionar, es posible hacer selecciones de eventos y usar las funciones basadas en ellas (abajo); eligiendo una herramienta de inserción (como la de las notas) cambia el comportamiento de la <acronym +>interfase gráfica </acronym +> insertando notas cliqueando en el tablero, eligiendo la herramienta de borrado, permite remover eventos cliqueando sobre ellos. </para> + <para +>También se puede cambiar la herramienta usando el menú de Herramientas. </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>Funciones que operan en selecciones</term> + <listitem> + <para +>La mayor parte de las funciones que restan en el menú, requieren que previamente se realice una selección antes de aplicarlas. Alguna de ellas, (como las funciones <guimenuitem +>Cortar</guimenuitem +> o la <guimenuitem +>Estilo de Nota</guimenuitem +> ) operarán en todos los eventos seleccionados; y otras (como las funciones <guimenuitem +>Notas de gracia</guimenuitem +> o <guimenuitem +>Direcciones de Plica </guimenuitem +> ) no funcionarán hasta que la selección incluya algunas notas. </para> + <para +>Para seleccionar eventos en la ventana principal, cambiar a la herramienta de Selección (flecha) y entonces dibujar un área rectangular conteniendo los eventos que se quieran seleccionar. Los eventos seleccionados se resaltarán en color azul. Si se hace clic en un sólo evento, sólo éste será seleccionado. <footnote +> <para +>De todas maneras, es posible hacer un doble clic en un evento en particular para abrir una ventana de diálogo para ese evento, pero nada que hacer con lo seleccionado.</para +> </footnote +> </para +><para +>Si se mantiene presionada la tecla <keycap +>Shift</keycap +> mientras se arrastra el rectángulo, se agregará lo seleecionado a una selección previa, en lugar de reemplazar a aquella. </para> + <para +>Para seleccionar un compás entero, hacer doble clic con la herramienta de Seleccionar en un espacio libre en ese compás, para seleccionar una línea de pentagrama entera, hacer tres clics. El menú Edición contiene funciones para seleccionar areas extensas según la ubicación del cursor de inserción, apretando la tecla Shift y presionado las flechas derecha o izquierda. </para> + <para +>No es posible seleccionar eventos en más de un pentagrama a la vez. </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>Operaciones de arrastre</term> + <listitem> + <para +>Es posible realizar una cierta clase de edición, simplemente arrastrando elementos. Cambiar a la herramienta (flecha) de selección, y desde allí se puede cambiar la altura de las notas simplemente cliqueando sobre la cabeza de la nota y la ubicación de ellas arrastrando a izquierda y derecha. (No se pueden arrastrar silencios o tiempos, pero sí todo lo demás. Si se han seleccionado varios eventos, todos se mueven a la vez.) </para> + <para +>El arrastre es usualmente una manera no tan exacta de editar eventos, tal como el uso del menú o las funciones del menú de Herramientas, pero es la más simple. </para> + </listitem> + </varlistentry> + </variablelist> + </sect1> + + <!-- Insertion: notes, auto-ties, accidentals --> + + <sect1 id="nv-insertion"> + <title +>Insertando notas y silencios</title> + + <para +>Para insertar una nota, seleccionar una de las herramientas de nota cliqueando en una duración particular en la barra de herramientas, y luego cliquear en el pentagrama en el punto en el que se quiera insertar.</para> + + <para +>También se pueden seleccionar las alteraciones en el menú de herramientas, para insertar bemoles o sostenidos. Si no se seleccionan alteraciones, la nota seguirá la armadura de clave. Alternativamente, se puede seleccionar el ícono "Continuar la alteración previa" (se ve como una nota con una flecha señalando hacia atrás donde la alteración aparecerá) para hacer que la nota siga la última alteración que se haya producido en la partitura.</para> + + <para +>Si se agrega una nota al mismo tiempo que una nota existente de diferente duración, el editor generalmente asume que se intenta crear una acorde y entonces se corre la nota para armar la representación del mismo con puntillo. Si realmente se quiere hacer una corde con dos duraciones diferentes, se debe seleccionar las notas con puntillos y usar la función de Juntar las Notas de Igual Altura para juntarlas. De otra manera se puede editar el comportamiento por defecto de esta función desde el diálogo de configuración de Rosegarden.</para> + + <para +>Si se agrega una nota exactamente sobre una nota existente de diferente duración (por ejemplo con la misma altura), la duración de la nota existente será cambiada a la nueva. </para> + + <para +>Si se agrega un silencio al mismo tiempo que una nota existente, la nota será silenciada por la duración del silencio, acortando o suprimiendo al mismo.</para> + + <sect2 id="nv-insertion-keyboard"> + <title +>Tipeando notas y silencios con el teclado de la PC</title> + + <sect3> + <title +>Duración</title> + + <para +>Primero, confirmar que la herramienta de notación está seleccionada para indicar la duración de las notas o silencios que se deseen insertar. Es posible insertar varios tipos de notas usando las teclas numéricas:</para> + + <itemizedlist> + <listitem +><para +><keycap +>5</keycap +> – Breve</para +></listitem> + <listitem +><para +><keycap +>1</keycap +> – Nota entera (semibreve)</para +></listitem> + <listitem +><para +><keycap +>2</keycap +> – 1/2 (Blanca)</para +></listitem> + <listitem +><para +><keycap +>4</keycap +> – 1/4 (Negra)</para +></listitem> + <listitem +><para +><keycap +>8</keycap +> – 1/8 (Corchea)</para +></listitem> + <listitem +><para +><keycap +>6</keycap +> – 1/16 (Semicorchea)</para +></listitem> + <listitem +><para +><keycap +>3</keycap +> – 1/32 (Fusa)</para +></listitem> + <listitem +><para +><keycap +>0</keycap +> – 1/64 (Semifusa)</para +></listitem> + </itemizedlist> + + <para +>Se puede cambiar a nota atresillada presionando la tecla <keycap +>G</keycap +>. Presionando la misma tecla una vez más se vuelve a la duración normal. La barra de status en la parte inferior de la ventana notificará cuando la duración atresillada está activa.</para> + </sect3> + + <sect3> + <title +>Tono / Altura</title> + + <para +>Una vez que la herramienta de notación está seleccionada, se puede insertar una nota en la posición actual del <link linkend="nv-rulers" +>cursor de inserción</link +> presionando una de las teclas de las teclas de altura:</para> + + <itemizedlist> + <listitem +><para +><keycap +>A</keycap +> – Do (la tónica de la escala en la actual tonalidad)</para +></listitem> + <listitem +><para +><keycap +>S</keycap +> – Re</para +></listitem> + <listitem +><para +><keycap +>D</keycap +> – Mi</para +></listitem> + <listitem +><para +><keycap +>F</keycap +> – Fa</para +></listitem> + <listitem +><para +><keycap +>J</keycap +> – Sol</para +></listitem> + <listitem +><para +><keycap +>K</keycap +> – La</para +></listitem> + <listitem +><para +><keycap +>L</keycap +> – Si</para +></listitem> + </itemizedlist> + + <para +>Presione la tecla "." para cambiar entre duraciones con puntillos o sin ellos.</para> + + <para +>manteniendo apretada la tecla <keycap +>Shift</keycap +> mientras se pulsa una tecla agregaremos un sostenido (#) a esa nota (salvo Mi y si que no lo tienen) y manteniendo apretada <keycap +>Shift</keycap +> y <keycap +>Ctrl</keycap +> juntas la alteraremos con un bemol (b) (excepto para Fa y Do).</para> + + <para +>Para ingresar notas una octava más alta, se deben usar las teclas de la fila superior: <keycap +>Q</keycap +>, <keycap +>W</keycap +>, <keycap +>E</keycap +>, <keycap +>R</keycap +>, <keycap +>U</keycap +>, <keycap +>I</keycap +>, y <keycap +>O</keycap +>. Asimismo, para notas una octava más baja, usar <keycap +>Z</keycap +>, <keycap +>X</keycap +>, <keycap +>C</keycap +>, <keycap +>V</keycap +>, <keycap +>B</keycap +>, <keycap +>N</keycap +> y <keycap +>M</keycap +>.</para> + + </sect3> + + <sect3> + <title +>Silencios</title> + + <para +>Para insertar un silencio en vez de una nota, presionar <keycap +>P</keycap +>. Alternativamente, se puede usar la tecla <keycap +>T</keycap +> y la <keycap +>Y</keycap +> para cambiar la herrramienta actual a la de silencio y volver a la de nota nuevamente.</para> + + </sect3> + + <sect3> + <title +>Acordes</title> + + <para +>El comportamiento por defecto del editor de partituras es mover el cursor de inserción hacia adelante luego de insertar una nota, para quedar listo para el ingreso de la próxima nota en la melodía; esto puede ser cambiado presionando la tecla <keycap +>H</keycap +>, que cambia a modo de acorde, para poner las siguientes notas en el mismo tempo que la anterior para armar el acorde. Cambiando luego con <keycap +>H</keycap +> volvemos al comportamiento melodía.</para> + + </sect3> + + <sect3> + <title +>Cambiando la duración de las notas</title> + + <para +>Es posible usar el teclado para cambiar la duración de las notas que se han ingresado. Verificar que las notas se han seleccionado y luego presionar <keycap +>Ctrl</keycap +> más la tecla numérica de la nota que se desee. También se puede agregar o quitar puntillos presionando <keycap +>Ctrl</keycap +> más "." guión; usando repetidamente se puede selecconar entre puntillo, doble puntillo y sin él.</para> + + <para +>Si se mantiene presionada la tecla <keycap +>Alt</keycap +> junto con la <keycap +>Ctrl</keycap +> se cambiará las duraciones de las notas en el menú de edición sin cambiar sus duraciones de interpretación. Esto puede ser muy útil para hacer más prolija una partitura: ver también <link linkend="nv-quantization" +>partitura desde una interpretación</link +>. </para> + </sect3> + + <sect3> + <title +>Otras observaciones</title> + + <para +>Todos los comandos de inserción están también disponibles en un submenú del menú Herramientas. Es improbable que para ingresar una nota se deba navegar por todo un menú, pero el menú muestra los atajos de teclado y provee una útil referencia en caso de que las combinaciones de teclas sean olvidadas.</para> + + <para +>Los atajos de teclado están diseñados para ser usados desde un teclado QWERTY. No hay forma aún de remapear todo el teclado y para otras distribuciones se debe asiganr cada tecal desde el menú "Configurar atajos..." en el menú de Opciones.</para> + + <para +>Manteniendo la tecla <keycap +>Ctrl</keycap +> mientras se presiona un número se seleccionará la correspndiente herramienta de puntillos.</para> + + </sect3> + + </sect2> + + <sect2 id="nv-insertion-midi"> + <title +>Ingresando notas a través de un teclado MIDI</title> + + <para +>Es posible ingresar notas desde un teclado MIDI, en un proceso conocido como grabación por pasos. Las notas tendrán la altura de las notas pulsadas en el teclado pero la duración que figura en el editor </para> + + <para +>Para ingresar las notas a través de un teclado MIDI, primero hay que confirmar que el teclado está configurado como el dispositivo MIDI predeterminado. Verificar asimismo que la herramienta de notación muestra la duración deseada. Entonces se presiona el botón de grabación por pasos en la barra de herramientas del editor de partituras, o se selecciona Grabación por pasos desde el menú Herramientas. A partir de allí, todas las notas presionadas en el teclado MIDI serán insertadas en la posición actual en la ventana, hasta que la grabación por pasos se termine, o se cambie de ventana, o se cierre la misma. </para> + + <para +>Se puede seleccionar una herramienta de partituras diferente mientras la grabación por pasos está en proceso; y además se puede cambiar al modo Acorde para ingresar los mismos. </para> + </sect2> + + </sect1> + + <!-- Keys, Clefs and Time Signatures --> + + <sect1 id="nv-signatures"> + <title +>Armadura de clave y tonalidad</title> + +<!-- !!! rework --> + <para +>La primera cuestión que hay que saber acerca de la manera en que Rosegarden maneja estas cuestiones, es que los cambios relativos al tiempo (tempo y duración de las notas) son tratados de manera completamente distinta de las alturas y tonalidades. En la senda de simplificar el manejo de la grabación y reproducción tanto como la escritura de la partitura, Rosegarden requiere que cuando el tiempo o el compás cambian, lo hagan en todos las líneas de pentagramas a la vez. No es posible tener una línea en 3/4 y otra en 4/4 a la vez, o un pentagrama con nerga de 120 y otro con 90. Esta restricción se aplica sólo a los tiempos: no a el uso de tonalidades o armaduras de clave.</para> + + <para +>Para cambiar la tonalidad, clave, tiempo o compás en la ventana del editor de partituras, colocar el <link linkend="nv-rulers" +>cursor de inserción</link +> en el lugar en que se quiera aplicar el cambio, y suar luego las funciones Agregar cambio de Tonalidad..., Agregar Cambio de Clave..., Agregar Cambio de Tempo..., Agregar Cambio de Compás... del Menú Edición. Entonces se verá una caja de diálogo en la que se podrán seleccionar los parámetros requeridos.</para> + + <sect2 id="nv-signatures-clef"> + <title +>Armadura de clave</title> + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-clefdialog.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>Diálogo de armadura de clave Rosegarden</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + + <para +>El diálogo perimite elegir una tonalidad, pero también escoger como esa tonalidad será aplicada, en caso en que haya algunas notas luego de la armadura de clave. Se deberá elegir una de las siguientes: <variablelist> + + <varlistentry> + <term +>Manteniendo las alturas iguales</term> + <listitem> + <para +>Todas las notas posteriores a la armadura mantienen su altura de ejecución </para> + <para +>Por ejemplo insertando una armadura de clave de tenor en el medio de una sección en agudos, causará que las notas siguientes a la armadura serán movidas una octava hacia arriba, porque ellas aún tendrán sus alturas de agudos. </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>Transponer una octava</term> + <listitem> + <para +>Las notas que siguen a la armadura de clave, retendrán su afinación dentro de la octava, pero deben ser movidas a una octava diferente para confeccionar una nueva clave, y allí serán ejecutadas en la nueva afinación. </para> + <para +>Por ejemplo insertando una clave de tenor en el medio de una sección de clave aguda causará que las notas se ajusten a la nueva tonalidad moviéndose una línea pero se ejecutarán una octava más baja que antes., </para> + </listitem> + </varlistentry> + + </variablelist> + + </para> + </sect2> + + <sect2 id="nv-signatures-key"> + <title +>Tonalidad</title> + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-keysigdialog.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>Diálogo de tonalidad Rosegarden</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + </sect2> + + </sect1> + + <!-- Text --> + + <sect1 id="nv-text"> + <title +>Texto y letras</title> + + <para +>Un pentagrama puede contener varias clases eventos de textos. Hay dos clases básicas de un evento de texto: ítems simples usados como anotaciones de notas etc., y las letras. El esquema será creado (y asociado a un determinado tempo en el pentagrama) usando la Herramienta de Texto, la cual está disponible en el botón con la <guilabel +>T</guilabel +> en la barra de herramientas. Las letras pueden ser creadas también de esta manera, pero es más fácil usando el <link linkend="nv-text-lyrics" +>editor de letras</link +>.</para> + + <para +>Para agregar un texto, seleccionar la herramienta de Texto y cliquear en el sitio en que se quiera insertar el mismo. Una caja de diálogo aparecerá, Allí se tipea el texto u se elige el propósito al que se destinará. (Rosegarden prefiere guardar el destino del texto, en vez de su aspecto; así en el futuro estará disponible para editar las diferentes clases de texto según la elección de cada usuario.) Los destinos (o estilos) disponibles son:</para> + + <variablelist> + + <varlistentry +><term +>Dinámico</term +><listitem +><para +>Usada para indicaciones menores como marcas "p", "mf" etc. Se muestran pequeñas y en bastardilla por defecto. </para +></listitem +></varlistentry> + + <varlistentry +><term +>Dirección</term +><listitem +><para +>Se usan para indicar cambios significativos en el estilo. Se muestran en el pentagrama en tipo romano grande por default. </para +></listitem +></varlistentry> + + <varlistentry +><term +>Dirección local</term +><listitem +><para +>usado para representar cambios menores en el estilo. Por omisión, en el pentagrama se verán con una tipografía roman bastardilla y negrita más pequeña. </para +></listitem +></varlistentry> + + <varlistentry +><term +>Tempo</term +><listitem +><para +>Se usa para identificar cambios en el tiempo. Se mostrará en el pentagrama en una fuente roman en negrita por defecto. </para +></listitem +></varlistentry> + + <varlistentry +><term +>Tempo Local</term +><listitem +><para +>Usada para indicar cambios menores en el tiempo. Se verán en el pentagrama en una tipografía pequeña roman en negrita. </para +></listitem +></varlistentry> + + <varlistentry +><term +>Letras</term +><listitem +><para +>No obstante las letras son usualmente creadas en el <link linkend="nv-text-lyrics" +>editor de letras</link +>, pueden ser ingresadas palabra por palabra si fuese necesario usando este estilo. Este estilo es mostrado abajo en una tipografía romana pequeña. (Advertencia: Si las letras son ingresadas de esta manera y luego se edita en el editor de letras del editor de partituras, las letras ingresadas deben ser modificadas o movidas si su posición no es compatible con lo esperado por el editor. </para +></listitem +></varlistentry> + + <varlistentry +><term +>Anotación</term +><listitem +><para +>Usado para texto de ayuda que no es considerado estrictamente parte de la partitura. Se mostrará bajo el pentagrama, recuadrado en un estilo tipo papel de notas amarillo. </para +></listitem +></varlistentry> + + </variablelist> + + <para +>Se puede además editar el texto luego de escribirlo, cliqueando en el texto con la herramienta Texto.</para> + + <sect2 id="nv-text-lyrics"> + <title +>Editando letras</title> + + <para +>El Editor de Letras, disponible desde el la opción <guimenuitem +>Abrir Editor de Letras</guimenuitem +> de el menú <guimenu +>Ver</guimenu +>, permite la edición de todos los eventos de letras de canciones de una sola vez para un pentagrama completo, usando un sistema básico de edición textual. Para usarlo, simplemente se deba activar la opción en el menú, editar el texto en el diálogo resultante y apretar "OK"</para> + + <para +>Las letras que se ingresen, estarán en un formato particular. Las líneas de compás que son vitales para evitar que el editor se confunda, están representadas por una barra ("/"). Entre cada barra las sílabas están separadas por espacios (en realidad un espacio: el editor no tiene en cuenta los espacios adicionales). Cada sílaba será adjuntada a el siguiente acorde o nota en ese compás. (no obstante lo cual el editor puede llega a perderse cuando los acordes no se correspnden exactamente, por ejemplo en aquellos que requieren cuantización</para> + + <para +>Si se requiere tener una nota que no tenga una sílaba adjuntada a ella, se coloac n punto (".") para esa nota. (He allí el porqué de que la letra por default para un segmento está llena de puntos.) Recuerdesé separa los puntos con espacios, para separar claramente las sílabas.</para> + + <para +>Si se necesita más de una sílaba para la misma nota, con un espacio entre ellas, se debe usar un tilde ("~") en lugar de un espacio. Será mostrado como un espacio en el pentagrama.</para> + + <para +>Si se necesita repartir na sílaba entre dos notas, con un guión, se debe ingresar un espacio siguiendo a el guión para que el editor sepa que se trata de dos sílabas. (El guión no toma tratamiento especial entre dos sílabas.)</para> + + <para +>Las sílabas que consisten solamente en números seguidos por corchtes (como "[29]") serán ignoradas; este es el formato usado para generar automáticamente números de compás mostrados en el editor.</para> + + <para +>Se debe prestar atención al formato de texto usado para editar las letras: éstas son guardadas como diferentes eventos de texto (uno por sílaba). Esto significa que el formato de texto puede variar en el futuro para incorporar capacidades de edición avanzadas, de todas maneras los formatos de eventos no deberían cambiar para mantener la compatibilidad entre archivos.</para> + + </sect2> + + </sect1> + + <!-- Indications --> + + <sect1 id="nv-indication"> + <title +>Borrones y ganchos</title> + + <para +>Son marcas dinámicas guardadas como eventos, como las notas o los silencios. Para crear uno, seleccionar el área a cubrir (una serie de notas o lo que sea), y entonces se debe usar las opciones <guimenuitem +>Agregar borrón</guimenuitem +>, <guimenuitem +>Agregar Crescendo</guimenuitem +> o <guimenuitem +>Agregar Decrescendo</guimenuitem +> del menú <guimenu +>Grupo</guimenu +>.</para> + + <para +>Se remueven exactamente igual que otro evento: primero se seleccionan con la herramienta de selección y luego se aprieta la tecla <keycap +>Suprimir</keycap +> o con la herramienta de borrado.</para> + + </sect1> + + <!-- Stem direction, slashes etc --> + + <sect1 id="nv-note-qualities"> + <title +>Fade Out y Cortes de notas</title> + + <para +>Es posible setear la dirección de la plica de las notas seleccionadas (se proveen varias) usando las tres posibilidades del submenú Dirección de Plica en el manú Notas. Estas opciones le permitirán seleccionar plica hacia arriba o abajo o revertir las existentes que Rosegarden ha escogido. Ver también<link linkend="nv-beamed-groups" +>Pulsos</link +>.</para> + + <para +>El menu <guimenu +>Grupo</guimenu +> también contiene optciones para agregar barras a través de las asas de las notas, por ejemplo, para indicar notas corta y repetidas o rolls de percusión. Éstas son actualmente puramente notación; &rosegarden; no las tomará en cuenta cuando reproduzca la partitura o genere &MIDI;.</para> + </sect1> + + <!-- Beamed groups, including overlapping and nesting them --> + + <sect1 id="nv-beamed-groups"> + <title +>Unir Plicas</title> + + <para +>Unir plicas en las notas está considerada una operación de agrupamiento en el Editor de Partitura de &rosegarden;, disponible en el menu <guimenu +>Grupo</guimenu +>. Selecciona las notas que quieres unir, y usa la opción Agrupar Plicas dentro del menú <guimenu +>Grupo</guimenu +>. Para remover la plica, selecciona las notas y usa la opción <guimenuitem +>Desagrupar Plicas</guimenuitem +>.</para> + + <para +>Es posible tener más de un grupo con plicas al mismo tiempo — simplemente selecciona y une los grupos separados de a uno — pero Rosegarden usualmente no es lo suficientemente inteligente como para saber qué notas deben tener las plicas hacia arriba y cuáles deben estar hacia abajo para un grupo de plicas unidas simultáneamente, entonces probablememte deberás corregir las direcciones de las plicas de las notas en los grupos explícitamente, como así también deberás unirlas.</para> + + <para +>&rosegarden; puede intentar adivinar una forma coherente de unir las piezas de música, no es tan complicado. Para invocar ésto, selecciona las notas para las cuales que quieres calcular la unión, (por ejemplo, por triple-clicleo para seleccionar todo el pentagrama) y luego usa la opción <guimenuitem +>Auto-Unir</guimenuitem +> en el <guimenu +>Groupos menu</guimenu +>. Esto es realizado incluso cuando se carga un archivo &MIDI;, por ejemplo, y el editor también hace algunas uniones automáticas mientras ingresas notas (ésto puede ser deshabilitado cambiando la configuración del diálogo "Auto-Unir cuando sea apropiado" o en la barra de herrramientas de inserción, con el menú que aparece presionando el botón derecho.</para> + + </sect1> + + <!-- Tuplets --> + + <sect1 id="nv-tuplets"> + <title +>Tresillos y otros tríos</title> + + <para +>Un grupo de tresillos consiste en tres notas o acordes repoducidos en el tiempo de dos. (Más precisamente, consiste en notas con una duración total de tres unidades arbitrarias reproducidas en el tiempo de dos de esas unidades.)</para> + + <para +>Usamos la frase <quote +>grupo irregular</quote +> para describir la situación general en la cual las notas con una duración total de cualquier número de unidades son reproducidas en el tiempo de un diferente número de esas unidades: nueve notas en el tiempo de ocho, o seis en el tiempo de cuatro, o incluso dos notas en el tiempo de tres. (En el presente &rosegarden; no soporta el último ejemplo —, los grupo irregular deben siempre ser reproducidos con una duración más corta que la escrita.)</para> + + <para +>Las funciones de los menus de tresillos y grupos irregulares funcionan tomando una serie de notas existentes o silencios, </para> + + <!-- Need examples and screenshots --> + + <!-- Then discuss general tuplet dialog... --> + + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-tupletdialog.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>Diálogo de tresillos de Rosegarden</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + + <para +>Para especificar un grupo irregular general, necesitamos saber cuál es la nota base (por ejemplo, si tocamos tres corcheas en el tiempo de dos, entonces la base es una corchea) y el radio del número de notas base escritas en el número interpretado.</para> + + <!-- Then discuss "tuplet mode": with a subtitle? --> + + </sect1> + + <!-- Grace notes --> + + <!-- Paste --> + + <sect1 id="nv-paste-types"> + <title +>Tipos de pegado</title> + + <para +>El significado de <quote +>cortar y pegar</quote +> es menos obvio para un programa de edición de música de lo que lo es para algo como un procesador de textos en el cual las letras y las palabras van en un orden simple y lineal. De acuerdo con ésto, el Editor de Partituras de &rosegarden; ofrece diferentes y variados tipos de operaciones de Pegado, así como funciones separadas de Cortar, y Cortar y Cerrar. </para> + + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-pastedialog.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>Diálogo de tipos de pegado Rosegarden</phrase> + </textobject> + </mediaobject> +</screenshot +> Los tipos de operación de pegado son:</para> + + <variablelist> + + <varlistentry> + <term +>Restringido</term> + <listitem> + <para +>Requiere un vacío existente (conteniendo nada salvo los silencios) de una duración suficiente como para contener completamente los contenidos del portapapeles. Los contenidos son pegados dentro del vacío. Si no hay un espacio vacío lo suficientemente largo, la operación de pegado no se lleva a cabo. </para> + <para +>Este es el tipo de pegado por defecto </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>Simple</term> + <listitem> + <para +>Borra suficientes eventos como para hacer un vacío lo suficientemente largo como para pegar algo dentro, y luego pega dentro de éste. Los eventos pegados remplazan cualquier nota existente en el tiempo cubierto por el pegado. </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>Abrir y Pegar</term> + <listitem> + <para +>Lo opuesto a Cortar y Cerrar. Hace lugar para el pegado moviendo todos los eventos subsecuentes un poco más lejos hacia el final de la composición. </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>Solapar la nota</term> + <listitem> + <para +>Lleva a cabo un pegado en la manera en que pasaría si ingresaras cada una de las notas en el portapapeles tú mismo usando el Editor de Partituras: si hay otras notas superponiéndose encima de ellas, las nuevas o existentes notas serán divididas con ligaduras de prolongación de una manera apropiada. </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>Solapar la matriz</term> + <listitem> + <para +>Lleva a cabo un pegado en la manera en que pasaría si ingresaras cada una de las notas en el portapapeles tú mismo usando el Editor de Matriz: las notas presentes en el camino del pegado serán ignoradas, permitiendo a las nuevas notas superponerse arbitrariamente con ellas. </para> + </listitem> + </varlistentry> + + </variablelist> + + <para +>Todo ésto tiene efecto en la posición actual del cursor de inserción en el pentagrama actual. Para elegir entre los varios tipos de pegado, usa la opción de menú Pegar... (con puntos suspensivos) en el menú Editar. </para> + + </sect1> + + <sect1 id="nv-adjustments"> + <title +>Ajustando la partitura</title> + + + <sect2 id="nv-adjustments-note-rest-durations"> + <title +>Ajustando las duraciones de silencios y notas</title> + + <sect3 id="nv-normalize-rests"> + <title +>Normalizando silencios</title> + + <para +>A veces como resultado de operaciones de editado o cuantización, una parte de la partitura puede terminar con duraciones de silencios incorrectas para la medida de compás actual. Puedes usar la funcion <guimenuitem +>Normalizar Silencios</guimenuitem +> para arreglar ésto. Ésta función examina cada secuencia consecutiva e silencios que se encuentran en la selección, y ajusta, divide y mezcla los silencios tanto como sea necesario como para asegurar que esos silencios tienen teóricamente duraciones correctas y caen en las barras correctas. </para> + + <para +>Por ejemplo, una barra 4/4 que contiene una negra, luego un silencio de blanca y un silencio de negra será reacomodado de manera de poner el silencio de negra antes que el de blanca, dado que éste último no debe cruzar el límite central de pulso de la barra. </para> + </sect3> +<!-- + <varlistentry id="commands-nv-menu-transforms-make-viable"> + <term +><menuchoice> + <guimenu +>Transforms</guimenu> + <guimenuitem +>Make Notes Viable</guimenuitem> + </menuchoice +></term> + <listitem> + <para +><action +>Splits notes at displayable + durations.</action +> This function is intended to deal + with notes that have excessively long durations that + overflow barlines or that are too long to be displayed + as a single note. It takes any such notes and splits + them into shorter, tied notes. + </para> + </listitem> + </varlistentry> + + <varlistentry id="commands-nv-menu-transforms-de-counterpoint"> + <term +><menuchoice> + <guimenu +>Transforms</guimenu> + <guimenuitem +>De-Counterpoint</guimenuitem> + </menuchoice +></term> + <listitem> + <para +><action +>Turns counterpoint into a series of split-and-tied notes and chords.</action> + + &rosegarden; has no explicit support for counterpoint + (multiple lines of notes edited separately on the + same staff), but it will do its best to approximate + it when it finds notes in a segment that are + apparently contrapuntal, i.e. that overlap but that + are not precise enough to be treated as chords. For + example, when a short note starts shortly after a + longer note, Rosegarden will show the longer note + and a short <quote +>spacing</quote +> rest together, followed by the + shorter note. Unfortunately this often isn't what + you want. + </para> + + <para +>The De-Counterpoint function can be applied to a + selection that contains overlapping notes. It will + split overlapping notes at the point where they + overlap, and tie together the resulting split notes, + ensuring that the music takes the form of a series of + chords and/or single notes starting and ending in neat + blocks, with some notes possibly tied. + </para> + </listitem> + </varlistentry> + + <varlistentry id="nv-transpose"> + <title +>Transpose</title> + <para +><action +>Alters the pitch of the selected + notes.</action +> This submenu contains basic + transposition functions which move the selected notes + up or down a semitone or a whole octave in pitch, as + well as a general transpose function that allows you + to choose how far up or down you want to transpose the + selection. + </para> + + <para +>These functions simply change the stored pitches + of the notes in the selection, so that they both play + and appear at the new pitches. They do not deal with + performance transposition (displaying one pitch and + playing another), for which see the main window's + segment parameter box; nor do they help you with + transposing from one key into another, for which see + <link linkend="nv-signatures-key" +>Key + Signatures</link +>. + </para> + </varlistentry> +--> + </sect2> + </sect1> + + <sect1 id="nv-interpret"> + <title +>Interpretando colas de performance en la notación</title> + <!-- !!! --> + <para +>La función Interpretación puede ser usada para modificar las velocidades y tiempos de las notas de acuerdo a cualquier marca dinámica escrita o indicada que se encuentre. La selección de interpretaciones disponibles son: <variablelist> + <varlistentry> + <term +>Aplicar las marcas dinámicas de texto (p, mf, ff, etc) </term> + <listitem +><para +>Setea la velocidad de cada nota basado en la última marca de texto de tipo "Dinámico"vista en el mismo staff (sólo se consideran textos de la forma pp, p, mp, f, ff, fff, etc). </para +></listitem> + </varlistentry> + + <varlistentry> + <term +>Dinámicas de crescendo/decrescendo </term> + <listitem +><para +>Hace que las notas aumenten o disminuyan su velocidad gradualmente durante una marca de este tipo. </para +></listitem> + </varlistentry> + + <varlistentry> + <term +>Acentuación de pulsos </term> + <listitem +><para +>Hace que las notas que descansan en la barra o en pulsos suenen un poco mas fuerte que las restantes (acentuación). </para +></listitem> + </varlistentry> + + <varlistentry> + <term +>Articular ligaduras de expresión, staccatos, tenutos, etc. </term> + <listitem +><para +>Acorta notas no ligadas, acorta mas las notas staccato, y le da a las notas dentro de ligaduras de expresión y tenutos su longitud completa </para +></listitem> + </varlistentry> + </variablelist> + + </para> + + </sect1> + + <!-- Quantization, smoothing, and display of quantized notes --> + + <sect1 id="nv-quantization"> + <title +>Notación desde datos de ejecución (performance)</title> + + <para +>&rosegarden; es un programa multi propósito: es un editor de notación, pero es primariamente un secuenciador y editor para música ejecutada. Y en una ejecución, por supuesto, los tiempos y duraciones de las notas son raramente tan precisas como en una partitura impresa. </para> + + <para +>Esto significa que es deseable que &rosegarden; haga un gran trabajo de ordenamiento de los tiempos y duraciones de las notas cuando se intenta lograr notas significativas para mostrar en el editor de notación. Ésto es una forma de cuantización, pero una forma que requiere una sorprendente cantidad de trabajo de suposición para funcionar bien. &rosegarden; incluye un cuantizador diseñado para hacer un trabajo un poco mejor que éste que el cuantizador de grilla común. </para> + + <para +>Aplicar cuantización estrictamente para la notación es normalmente referido como <quote +>cuantización de notación</quote +>: sólo se aplica a las notas que uno ve y edita en notación, y no afecta a otras notas que se ven o editan desde otras vistas que no sea la matrix. Ésta cuantización es automáticamente aplicada a la música importada o grabada desde MIDI, aunque no todas las capacidades posibles son activadas por defecto. </para> + + <para +>Existen dos maneras de ver que notas han sido cuantizadas para la notación. Por defecto, cada vista de notación contiene una Regla de Notas (en el grupo de reglas por sobre la parte) que muestra un block rectangular para cada nota. éste block está posicionado para representar el teimpo y la duración de a nota según haya sido ejecutada, pero con los bordes superior e inferior del rectángulo extendidos o reducidos para representar el tiempo después de la cuantización de notas. Si esto resulta demasiada información, puede, alternativamente, elegir (en el diálogo de configuración) mostrar en un color verde todas las cabezas de las notas de la parte cuyos tiempos han sido alterados por la cuantización de notación. </para> + + <para> + + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-notationquantizer.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>El diálogo de cuantización de &rosegarden;</phrase> + </textobject> + </mediaobject> + </screenshot> + </para +><para +>Si la cuantizacíon que &rosegarden; ha realizado no es conveniente, tanto para la parte completa como para una selección de notas, puede usar un nivel de cuantización distinto o ninguno en absoluto. Para aplicar una cuantización diferente a algunas notas, seleccione las notas y utilice la función del menú Cuantizar... (marque la caja llamada <quote +> Cuantizar para notación solamente</quote +>). El nivel o tipo de cuantización usado por defecto puede ser cambiado en el diálogo de configuración. </para> + + <sect2 id="nv-quantization-parameters"> + <title +>Parámetros configurables para el cuantizador de notación heurístico</title> + + <sect3 id="nv-quantization-parameters-during"> + <title +>Parámetros para la cuantización misma</title> + + <variablelist> + + <varlistentry> + <term +>Complejidad</term> + <listitem> + <para +>la "complejidad" de un cuantizador de notación es el parámetro mas fundamental. Un cuantizador "complejo"va a estar mas preparado para aceptar que música-que-se-ve-compleja es de hecho música que se pretende compleja, mientras que es mas normal que un cuantizador "simple" asuma que música-que-se-ve-compleja resulta de una performance imprecisa de música simple. </para> + <para +>El seteo por defecto tiene por cometido producir resultados razonables para un verdadero amplio rango de música. </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>Unidad base de grilla</term> + <listitem> + <para +>La unidad base de grilla (seteado al valor de duración de una nota) especifica la unidad absoluta mínima de una nota a la que se permite en la parte luego de una cuantización. Por ejemplo, si se setea el valor a una semicorchea, todas las notas serán colocadas en las vecindades de un múltiplo de una semicorchea, con duraciones también múltiplo de la misma. </para> + <para +>El seteo de la unidad de base de grilla no es tan significante para un cuantizador de notación como lo es para un cuantizador de grilla plana, ya que todo lo que hace es imponer un límite absoluto en el nivel de presición permitido por el parámetro de complejidad. Mayormente, cuando se encuentra un caso en el cuál incrementando la unidad de grilla producen mejores resultados, ha encontrado realmente un caso en el que el cuantizador simplemente no hizo un tan buen trabajo como el que podría haber hecho con una unidad menor. </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>Nivel de trecillo</term> + <listitem> + <para +>El cuantizador de notación es capaz de identidficar trecillos (tripletos y otros tipos de particiones de tiempo), con límites razonables. Éste parámetro controla que tan ambiciosamente va a intentar ser al momento de buscar trecillos, seteando un límite en cuántas notas por grupo de trecillos va a intentar identificar. Si se encuentra seteado a <quote +>Ninguno</quote +>, el cuantizador no intentará identificar trecillos. </para> + </listitem> + </varlistentry> + + </variablelist> + + </sect3> + + <sect3 id="nv-quantization-parameters-after"> + <title +>Parámetros que controlan el emparejamiento luego de la cuantización</title> + + <variablelist> + + <varlistentry> + <term +>Re-ligadura</term> + <listitem> + <para +>Hace que la notación sea re-ligada en grupos apropiados luego de la cuantización. Ésto es usualmente deseable. </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>Agregar articulaciones (staccatos, tenutos, ligaduras de expresión)</term> + <listitem> + <para +>Hace que el cuantizador intente identificar, basado en la duración de notas individuales y consecutivas, que notas deben ser escritas con marcas de staccato (para notas que son significantemente mas cortas que la nota siguiente, pero aparentemente no lo suficientemente cortas para merecer un silencio), tenuto (para notas que casi o justamente se sobreponen a la siguiente nota) y ligaduras de expresión (para series de notas que se sobreponen). </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>Ligación de notas en las barras, etc.</term> + <listitem> + <para +>Hace que las notas que luego de la cuantización todavía se encuentran presentes através de una barra o que no son exactamente expresables con la cabeza de una nota simple, sean divididas en múltiples notas apropiadamente, y ligadas. Ésto tiene el mismo efecto que aplicar la función "Ligar notas en las barras" en la vista de notación. </para> + <para +>Éste parámetro no se encuentra activado por defecto debido a que cambia el número de eventos de notas, lo que es indeseable cuando se utiliza &rosegarden; principalmente o en parte como secuanciador MIDI. </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>Dividir y ligar acordes que se sobreponen</term> + <listitem> + <para +>Hace que los acordes que se sobreponen sean divididos y ligados, de manera de formar los acordes estrictos con notas individuales ligadas de la forma que sea necesaria. Ésto tiene el mismo efecto que aplicar la función "Dividir y ligar acordes superpuestos" en la vista de notación. </para> + <para +>Éste parámetro no se encuentra activado por defecto debido a que cambia el número de eventos de notas, lo que es indeseable cuando se utiliza &rosegarden; principalmente o en parte como secuanciador MIDI. </para> + </listitem> + </varlistentry> + </variablelist> + </sect3> + </sect2> + </sect1> + + + <sect1 id="nv-note-styles"> + <title +>Estilos de notas</title> + + <para +>&rosegarden; también permite cambiar varios aspectos de la manera en la que varios tipos de notas son dibujadas, como la cabeza de las notas, el número de colas, si las notas son o no rellenadas, etc. </para> + + <para +>Se provee un set de estilos estándar (Clásico, Cruzado, Triángulo y Medible), y es posible cambiar el estilo usado para notas individuales seleccionandolas y utilizando las opciones del menú Estilo de notas. Cada nota recuerda que estilo ha sido elegido para ella, y esta información es guardada como parte de la composición. También es posible cambiar el estilo por defecto para notas nuevas usando la opción <guimenuitem +>Configurar Rosegarden...</guimenuitem +> el el menú <guimenu +>Configuraciones</guimenu +>. </para> + + <para +>También es posible crear sus propios estilos de nota describiéndolos en archivos <acronym +>XML</acronym +>. Incluso los estilos estándar son definidos de ésta forma, la única razón por la cuál el editor sabe que una semicirchea de estilo Clásico tiene una cabez ovalada, rellena y aplastada, una plica, dos banderas, etc., es porque la descripción en Classical.xml dice eso. Vea <link linkend="developers-note-styles" +>Personalizando Rosegarden</link +> para mas información. </para> + </sect1> + + <sect1 id="nv-note-fonts"> + <title +>Fuentes de notas</title> + <para +>&rosegarden; se provee con una sola fuente escalable de notación, la fuente Feta desarrollada por el proyecto Lilypond. Feta es una fuente de extremadamente alta calidad que debería ser apropiada para casi todo el trabajo clásico. </para> + + <para +>&rosegarden; también incluye soporte como estándar para un número de otras fuentes de notación. Necesitará proveer éstas fuentes en formato TrueType (.ttf) o PostScript tipo 1 (.pfb, .pfa), y necesitará los permisos relevantes para instalarlos en el mismo lugar en el que &rosegarden; fué instalado. Para instalar una fuente soportadalocalice el directorio compartido para la instalación de &rosegarden; (usualmente un subdirectorio del árbol de instalación de KDE, como por ejemplo /opt/kde/share/apps/rosegarden). Encontrará que éste directorio contiene un subdirectorio llamado "fonts":copie los archivos de fuentes ahí, y reinicie &rosegarden;. Si su fuente es soportada, debería aparecer ahora en el menú de fuentes en el editor de notación.</para> + + <para +>Soporte parcial o completo es actualmente proveído para las siguientes fuentes: Fughetta, por Blake Hodgetts; Petrucci, la fuente "original" de Finale; Maestro, la "nueva" fuente de Finale; Opus, la fuente de Sibelius; Inkpen, la fuente de jazz Sibelius; Sonata de Adobe; Steinberg, del secuenciador Cubase; y Xinfonia. EL EQUIPO DE ROSEGARDEN NO HACE REPRESENTACIÓN DEL ESTÁTUS LEGAL DE ALGÚN USO DE ÉSTAS FUENTES CON ROSEGARDEN. Es su responsabilidad de asegurarse que está cumpliendo con la licencia (si existe alguna) bajo la cuál la fuente le fué provista, antes de usarla. Si no está seguro de si tiene o no el derecho de usar una fuente, no se aparte a otra cosa, la fuente Feta es mejor que la mayoría de éstas de todos modos.</para> + + <para +>Es también posible proveer nuevos archivos de mapeos de manera de usar nuevas fuentes. Para algunas fuentes que poseen mapeos o métricas similares a la lista de mas arriba, ésto puede ser tan simple como editar el nombre de la fuente en el archivo de mapeo. Vea <link linkend="developers-note-fonts" +>Personalizando Rosegarden</link +> para mas información. </para> + </sect1> + + + </chapter> + + <chapter id="event-view"> + <title +>El editor de Lista de Eventos</title> + <sect1 id="ev-introduction"> + <title +>introducción</title> + + <para +>El editor de Lista de Eventos de &rosegarden; muestra los eventos en un segmento simple en una forma cruda, y le permite editar las propiedades precisas de esos eventos individualmente. <screenshot +> <mediaobject> + <imageobject> + <imagedata fileref="rg-eventlisteditor.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>El editor de eventos de &rosegarden;</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + </sect1> + </chapter> + + + + + <!-- + ********************************** + + PART II: + Command reference + + ********************************** + --> +<!-- NO + + <chapter id="commands"> + <title +>Command Reference</title> + + + <para +></para> + + <sect1 id="commands-main"> + <title +>Main window</title> + <para +></para> + + + <sect2> + <title +>File menu</title> + <para> + <variablelist> + + <varlistentry id="commands-main-file-new"> + <term +><menuchoice> + <shortcut> + <keycombo +><keycap +>Ctrl</keycap +><keycap +>n</keycap +></keycombo> + </shortcut> + <guimenu +>File</guimenu> + <guimenuitem +>New</guimenuitem> + </menuchoice +></term> + <listitem +><para +><action +>Creates a new composition.</action +></para +></listitem> + </varlistentry> + + <varlistentry id="commands-main-file-open"> + <term +><menuchoice> + <shortcut> + <keycombo +><keycap +>Ctrl</keycap +><keycap +>o</keycap +></keycombo> + </shortcut> + <guimenu +>File</guimenu> + <guimenuitem +>Open</guimenuitem> + </menuchoice +></term> + <listitem +><para +><action +>Opens an existing composition from a Rosegarden-4 (.rg) file.</action +></para +></listitem> + </varlistentry> + + <varlistentry id="commands-main-file-import"> + <term +><menuchoice> + <guimenu +>File</guimenu> + <guimenuitem +>Import</guimenuitem> + </menuchoice +></term> + <listitem +><para +>This submenu contains functions for importing compositions from other file formats.</para> + + <variablelist> + + <varlistentry id="commands-main-file-import-midi"> + <term +><menuchoice> + <guimenu +>Import</guimenu> + <guimenuitem +>Import &MIDI; file...</guimenuitem> + </menuchoice +></term> + <listitem +><para +><action +>Creates a new composition from the contents of an existing &MIDI; (.mid) file.</action +></para +></listitem> + </varlistentry> + + <varlistentry id="commands-main-file-import-rg21"> + <term +><menuchoice> + <guimenu +>Import</guimenu> + <guimenuitem +>Import Rosegarden 2.1 file...</guimenuitem> + </menuchoice +></term> + <listitem +><para +><action +>Creates a new composition from the contents of an existing Rosegarden 2.1 (.rose) file.</action +></para +></listitem> + </varlistentry> + + </variablelist> + </listitem> + </varlistentry> + + <varlistentry id="commands-main-file-merge"> + <term +><menuchoice> + <guimenu +>File</guimenu> + <guimenuitem +>Merge</guimenuitem> + </menuchoice +></term> + <listitem +><para +>This submenu contains functions for merging other files into the current composition.</para> + + <variablelist> + + <varlistentry id="commands-main-file-merge-file"> + <term +><menuchoice> + <guimenu +>Merge</guimenu> + <guimenuitem +>Merge File...</guimenuitem> + </menuchoice +></term> + <listitem +><para +><action +>Merges the contents of an existing Rosegarden (.rg) file into the current composition. You will be offered a choice of whether to merge the file in new tracks at the start of the composition, or after the end of the current composition.</action +></para +></listitem> + </varlistentry> + + <varlistentry id="commands-main-file-merge-midi"> + <term +><menuchoice> + <guimenu +>Merge</guimenu> + <guimenuitem +>Merge &MIDI; file...</guimenuitem> + </menuchoice +></term> + <listitem +><para +><action +>Merges the contents of an existing &MIDI; (.mid) file into the current composition. You will be offered a choice of whether to merge the file in new tracks at the start of the composition, or after the end of the current composition.</action +></para +></listitem> + </varlistentry> + + <varlistentry id="commands-main-file-merge-rg21"> + <term +><menuchoice> + <guimenu +>Merge</guimenu> + <guimenuitem +>Merge Rosegarden 2.1 file...</guimenuitem> + </menuchoice +></term> + <listitem +><para +><action +>Merges the contents of an existing Rosegarden 2.1 (.rose) file into the current composition. You will be offered a choice of whether to merge the file in new tracks at the start of the composition, or after the end of the current composition.</action +></para +></listitem> + </varlistentry> + + </variablelist> + </listitem> + </varlistentry> + + <varlistentry id="commands-main-file-export"> + <term +><menuchoice> + <guimenu +>File</guimenu> + <guimenuitem +>Export</guimenuitem> + </menuchoice +></term> + <listitem +><para +>This submenu contains functions for exporting the contents of compositions to other file formats.</para> + + <variablelist> + + <varlistentry id="commands-main-file-export-midi"> + <term +><menuchoice> + <guimenu +>Export</guimenu> + <guimenuitem +>Export &MIDI; file...</guimenuitem> + </menuchoice +></term> + <listitem +><para +><action +>Saves the contents of the current composition into a new &MIDI; file.</action +> Note that not all data in the Rosegarden composition necessarily can or will be saved in the &MIDI; format.</para +></listitem> + </varlistentry> + + <varlistentry id="commands-main-file-export-csound"> + <term +><menuchoice> + <guimenu +>Export</guimenu> + <guimenuitem +>Export Csound score file...</guimenuitem> + </menuchoice +></term> + <listitem +><para +><action +>Saves the contents of the current composition into a new Csound score file.</action +> Together with a suitable orchestra file (not supplied), this can be used to play the composition through <ulink url="http://www.csounds.com/" +>Csound</ulink +>. Note that not all data in the Rosegarden composition necessarily can or will be saved in the Csound format.</para +></listitem> + </varlistentry> + + <varlistentry id="commands-main-file-export-lilypond"> + <term +><menuchoice> + <guimenu +>Export</guimenu> + <guimenuitem +>Export Lilypond file...</guimenuitem> + </menuchoice +></term> + <listitem +><para +><action +>Saves the contents of the current composition into a new Lilypond file.</action +> This can then be processed by the <ulink url="http://www.lilypond.org/" +>Lilypond</ulink +> system to produce typeset-quality music, although it is likely that the file may need some tweaking to get really good quality output. Note that not all data in the Rosegarden composition necessarily can or will be saved in the Lilypond format.</para +></listitem> + </varlistentry> + + <varlistentry id="commands-main-file-export-mup"> + <term +><menuchoice> + <guimenu +>Export</guimenu> + <guimenuitem +>Export Mup file...</guimenuitem> + </menuchoice +></term> + <listitem +><para +><action +>Saves the contents of the current composition into a new Mup file.</action +> This can then be processed by the <ulink url="http://www.arkkra.com/" +>Mup</ulink +> music publication system, although it is likely that the file may need some tweaking to get really good quality output. Note that not all data in the Rosegarden composition necessarily can or will be saved in the Mup format.</para +></listitem> + </varlistentry> + + <varlistentry id="commands-main-file-export-musicxml"> + <term +><menuchoice> + <guimenu +>Export</guimenu> + <guimenuitem +>Export MusicXML file...</guimenuitem> + </menuchoice +></term> + <listitem +><para +><action +>Saves the contents of the current composition into a new MusicXML file.</action +> This can then be used with any music software that supports the MusicXML format. Note that MusicXML support is experimental and has not been well tested. Not all data in the Rosegarden composition necessarily can or will be saved in the MusicXML format.</para +></listitem> + </varlistentry> + + </variablelist> + </listitem> + </varlistentry> + + <varlistentry id="commands-main-file-save"> + <term +><menuchoice> + <shortcut> + <keycombo +><keycap +>Ctrl</keycap +><keycap +>s</keycap +></keycombo> + </shortcut> + <guimenu +>File</guimenu> + <guimenuitem +>Save</guimenuitem> + </menuchoice +></term> + <listitem +><para +><action +>Saves the composition.</action +></para +></listitem> + </varlistentry> + + <varlistentry id="commands-main-file-save-as"> + <term +><menuchoice> + <guimenu +>File</guimenu> + <guimenuitem +>Save As...</guimenuitem> + </menuchoice +></term> + <listitem +><para +><action +>Saves the composition with a new filename.</action +></para +></listitem> + </varlistentry> + + <varlistentry id="commands-main-file-close"> + <term +><menuchoice> + <shortcut> + <keycombo +><keycap +>Ctrl</keycap +><keycap +>w</keycap +></keycombo> + </shortcut> + <guimenu +>File</guimenu> + <guimenuitem +>Close</guimenuitem> + </menuchoice +></term> + <listitem +><para +><action +>Closes the current composition.</action +></para +></listitem> + </varlistentry> + + <varlistentry id="commands-main-file-print"> + <term +><menuchoice> + <shortcut> + <keycombo +><keycap +>Ctrl</keycap +><keycap +>p</keycap +></keycombo> + </shortcut> + <guimenu +>File</guimenu> + <guimenuitem +>Print</guimenuitem> + </menuchoice +></term> + <listitem +><para +><action +>Prints the current composition.</action +> At the time of writing, the print function is incomplete. We recommend using the <link linkend="commands-main-file-export-lilypond" +>Export Lilypond file</link +> function and printing with Lilypond instead.</para +></listitem> + </varlistentry> + + <varlistentry id="commands-main-file-quit"> + <term +><menuchoice> + <shortcut> + <keycombo +><keycap +>Ctrl</keycap +><keycap +>q</keycap +></keycombo> + </shortcut> + <guimenu +>File</guimenu> + <guimenuitem +>Quit</guimenuitem> + </menuchoice +></term> + <listitem +><para +><action +>Quits &rosegarden;</action +></para +></listitem> + </varlistentry> + + </variablelist> + </para> + + </sect2> + + + <sect2> + <title +>Edit menu</title> + <para> + <variablelist> + + <varlistentry id="commands-main-edit-undo"> + <term> + <menuchoice> + <shortcut> + <keycombo> + <keycap +>Ctrl</keycap> + <keycap +>z</keycap> + </keycombo> + </shortcut> + <guimenu +>Edit</guimenu> + <guimenuitem +>Undo</guimenuitem> + </menuchoice> + </term> + <listitem> + <para> + <action> + Reverses the last command performed. + </action> + </para> + </listitem> + </varlistentry +> + + <varlistentry id="commands-main-edit-redo"> + <term> + <menuchoice> + <shortcut> + <keycombo> + <keycap +>Ctrl</keycap> + <keycap +>Shift</keycap> + <keycap +>z</keycap> + </keycombo> + </shortcut> + <guimenu +>Edit</guimenu> + <guimenuitem +>Redo</guimenuitem> + </menuchoice> + </term> + <listitem> + <para> + <action> + Repeats the last command performed, following an undo. + </action> + </para> + </listitem> + </varlistentry +> + + <varlistentry id="commands-main-edit-cut"> + <term> + <menuchoice> + <shortcut> + <keycombo> + <keycap +>Ctrl</keycap> + <keycap +>x</keycap> + </keycombo> + </shortcut> + <guimenu +>Edit</guimenu> + <guimenuitem +>Cut</guimenuitem> + </menuchoice> + </term> + <listitem> + <para> + <action> + Removes the currently selected segment from the + composition view and adds it to the clipboard. Note that + when you have selected a track, all segments in that track + are selected. + </action> + </para> + </listitem> + </varlistentry +> + + <varlistentry id="commands-main-edit-copy"> + <term> + <menuchoice> + <shortcut> + <keycombo> + <keycap +>Ctrl</keycap> + <keycap +>c</keycap> + </keycombo> + </shortcut> + <guimenu +>Edit</guimenu> + <guimenuitem +>Copy</guimenuitem> + </menuchoice> + </term> + <listitem> + <para> + <action> + Removes the selected segments from the composition and + places them in the clipboard to replace any contents the + clipboard previously had. + </action +> + Note that when you have selected a track, all segments in that track + are selected. + </para> + </listitem> + </varlistentry +> + + + <varlistentry id="commands-main-edit-paste"> + <term> + <menuchoice> + <shortcut> + <keycombo> + <keycap +>Ctrl</keycap> + <keycap +>v</keycap> + </keycombo> + </shortcut> + <guimenu +>Edit</guimenu> + <guimenuitem +>Paste</guimenuitem> + </menuchoice> + </term> + <listitem> + <para> + <action> + Inserts the contents of the clipboard into the composition. + Verbage hear stating where the contents are inserted + (current track, offset within that track etc). + </action> + </para> + </listitem> + </varlistentry +> + + <varlistentry id="commands-main-edit-delete"> + <term> + <menuchoice> + <shortcut> + <keycombo> + <keycap +>Delete</keycap> + </keycombo> + </shortcut> + <guimenu +>Edit</guimenu> + <guimenuitem +>Delete</guimenuitem> + </menuchoice> + </term> + <listitem> + <para> + <action> + Removes the selected segments from the composition and throws them away. + </action> + </para> + </listitem> + </varlistentry +> + + + <varlistentry id="commands-main-edit-select-all-segments"> + <term> + <menuchoice> + <guimenu +>Edit</guimenu> + <guimenuitem +>Select All Segments</guimenuitem> + </menuchoice> + </term> + <listitem> + <para> + <action> + Selects all segments within the composition. + </action> + </para> + </listitem> + </varlistentry +> + + <varlistentry id="commands-main-edit-add-tempo-change"> + <term> + <menuchoice> + <guimenu +>Edit</guimenu> + <guimenuitem +>Add Tempo Change...</guimenuitem> + </menuchoice> + </term> + <listitem> + <para> + <action> + Invokes a tempo change dialog. + </action> + This offers a + selection of ways to change the tempo of the + composition, including changing the tempo from the + insert cursor position onwards, from the last + tempo change onwards, or for the entire + composition. See + +for more information. + + </para> + </listitem> + </varlistentry +> + + <varlistentry id="commands-main-edit-add-time-signature"> + <term> + <menuchoice> + <guimenu +>Edit</guimenu> + <guimenuitem +>Add Time Signature Change...</guimenuitem> + </menuchoice> + </term> + <listitem> + <para> + <action> + Invokes a time-signature change dialog. + </action> + + This offers a + selection of ways to change the tempo of the + composition, including changing the time signature + from the insert cursor position onwards or from the + start of the current bar. See + + for more information. + + </para> + </listitem> + </varlistentry +> + + + <varlistentry id="commands-main-edit-change-composition-duration"> + <term> + <menuchoice> + <guimenu +>Edit</guimenu> + <guimenuitem +>Change Composition Duration...</guimenuitem> + </menuchoice> + </term> + <listitem> + <para> + <action> + Invokes a composition duration change dialog. + </action> + + This allows you to change the overall duration of + the composition. This duration sets a hard limit + (as a number of bars) on the scrollable width of the + main window and the length of time you can play or + record before the composition is deemed to have + ended. The default is 100 bars. + + </para> + </listitem> + </varlistentry +> + + + <varlistentry id="commands-main-edit-document-properties"> + <term> + <menuchoice> + <guimenu +>Edit</guimenu> + <guimenuitem +>Edit Document Properties...</guimenuitem> + </menuchoice> + </term> + <listitem> + <para> + <action> + Invokes a document properties dialog. + </action> + + The document properties dialog allows you to review and/or modify the current document properties. Note - explain what are properties. Note to developers - It seems kinda weird to have icons on the left for selecting, and tabs in each one. Why not just tabs or just the things on the left? + + </para> + </listitem> + </varlistentry +> + + + </variablelist> + </para> + </sect2> + + <sect2> + <title +>Segments menu</title> + <para> + <variablelist> + + <varlistentry id="commands-main-segments-open-default-editor"> + <term> + <menuchoice> + <shortcut> + <keycombo> + <keycap +>Return</keycap> + </keycombo> + </shortcut> + <guimenu +>Segments</guimenu> + <guimenuitem +>Open in Default Editor</guimenuitem> + </menuchoice> + </term> + <listitem> + <para> + <action +> Opens all of the currently + selected segments together in a notation editor, or in + whichever other editor you have configured as your + default. + </action> + </para> + </listitem> + </varlistentry +> + + <varlistentry id="commands-main-segments-open-matrix-editor"> + <term> + <menuchoice> + <guimenu +>Segments</guimenu> + <guimenuitem +>Open in Matrix Editor</guimenuitem> + </menuchoice> + </term> + <listitem> + <para> + <action +> Opens all of the currently + selected segments in a matrix editor. + </action> + See <link linkend="matrix-view" +>matrix editor</link +>. + </para> + </listitem> + </varlistentry +> + + <varlistentry id="commands-main-segments-open-notation-editor"> + <term> + <menuchoice> + <guimenu +>Segments</guimenu> + <guimenuitem +>Open in Notation Editor</guimenuitem> + </menuchoice> + </term> + <listitem> + <para> + <action +> Opens all of the currently + selected segments together in a notation editor. + </action> + See <link linkend="notation-view" +>notation editor</link +>. + </para> + </listitem> + </varlistentry +> + + <varlistentry id="commands-main-segments-open-event-editor"> + <term> + <menuchoice> + <guimenu +>Segments</guimenu> + <guimenuitem +>Open in Event List Editor</guimenuitem> + </menuchoice> + </term> + <listitem> + <para> + <action +> Opens all of the currently + selected segments together in a event-list editor. + </action> + See <link linkend="event-view" +>event-list editor</link +>. + </para> + </listitem> + </varlistentry +> + + + <varlistentry id="commands-main-segments-quantize"> + <term> + <menuchoice> + <guimenu +>Segments</guimenu> + <guimenuitem +>Quantize...</guimenuitem> + </menuchoice> + </term> + <listitem> + <para> + <action +>Invokes a quantization dialog for quantizing the current selection. + </action> + See <link linkend="nv-quantization" +>quantization</link +>. + </para> + </listitem> + </varlistentry +> + + <varlistentry id="commands-main-segments-rescale"> + <term> + <menuchoice> + <guimenu +>Segments</guimenu> + <guimenuitem +>Rescale...</guimenuitem> + </menuchoice> + </term> + <listitem> + <para> + <action +>Allows you to stretch or squash segments in time. + </action> + + This option invokes a rescale dialog, which allows + you to specify a ratio of timings that is then + applied to the selected segments. This has the + result of stretching (slowing down) or squashing + (speeding up) the selected segments, changing their + durations accordingly. + + </para> + <para> + This only applies to segments containing MIDI + events, not to audio segments. Rosegarden does not + currently provide native support for audio + time-stretching. + </para> + </listitem> + </varlistentry +> + + <varlistentry id="commands-main-segments-auto-split"> + <term> + <menuchoice> + <guimenu +>Segments</guimenu> + <guimenuitem +>Auto-Split</guimenuitem> + </menuchoice> + </term> + <listitem> + <para> + <action> + Splits the selected segments on silences. + </action> + + This function works slightly differently depending + on whether the selected segments contain audio or + MIDI data. For audio segments, it offers you a + dialog in which you can choose a threshold below + which the segment is considered "silent"; it then + splits the segment whenever its amplitude falls + below this threshold. For MIDI segments, it simply + splits the segment everywhere that a full bar of + silence occurs. + </para> + </listitem> + </varlistentry +> + + <varlistentry id="commands-main-segments-split-by-pitch"> + <term> + <menuchoice> + <guimenu +>Segments</guimenu> + <guimenuitem +>Split by Pitch...</guimenuitem> + </menuchoice> + </term> + <listitem> + <para> + <action +>Splits the currently selected segments into higher and + lower parts. + </action> + + This function invokes a dialog allowing you to + choose a pitch as a "split point", and then splits + the selected segments in half with all the notes on + or above that split point in the "higher" segment + and all the notes below it in the "lower". + + </para> + <para> + If the music in the segment consists of two separate + parts (e.g. left and right hand piano parts) that + are not always completely on either side of a single + split point, you may with to select the "ranging + split-point" option. If this is selected, + Rosegarden will attempt to track the two parts as + they move up and down, usually doing a slightly + better job of separating out notes that were + intended to lie in the two separate parts. + + </para> + <para> + The resulting segments are both created on the same + track, with one overlapping the other. + + </para> + </listitem> + </varlistentry +> + + + + + </variablelist> + </para> + </sect2> + </sect1> + + <sect1 id="commands-nv"> + <title +>Notation editor</title> + <para +></para> + + + <sect2 id="commands-nv-menu-file"> + <title +>File menu</title> + <para> + <variablelist> + + <varlistentry id="commands-nv-menu-file-close"> + <term +><menuchoice> + <shortcut> + <keycombo +><keycap +>Ctrl</keycap +><keycap +>w</keycap +></keycombo> + </shortcut> + <guimenu +>File</guimenu> + <guimenuitem +>Close</guimenuitem> + </menuchoice +></term> + <listitem +><para +><action +>Closes the window</action +></para +></listitem> + </varlistentry> + + </variablelist> + </para> + + </sect2> + + <sect2 id="commands-nv-menu-edit"> + <title +>Edit menu</title> + <para> + <variablelist> + + <varlistentry id="commands-nv-menu-edit-undo"> + <term +><menuchoice> + <shortcut> + <keycombo +><keycap +>Ctrl</keycap +><keycap +>z</keycap +></keycombo> + </shortcut> + <guimenu +>Edit</guimenu> + <guimenuitem +>Undo</guimenuitem> + </menuchoice +></term> + <listitem> + <para> + <action> + + Reverses the last edit. + + </action +> Edits are shared across + all views, so if the last edit was not made in + this view, undoing it might not appear to change + this view either. + </para> + </listitem> + </varlistentry> + + <varlistentry id="commands-nv-menu-edit-redo"> + <term +><menuchoice> + <shortcut> + <keycombo +><keycap +>Ctrl</keycap +><keycap +>Shift</keycap +><keycap +>z</keycap +></keycombo> + </shortcut> + <guimenu +>Edit</guimenu> + <guimenuitem +>Redo</guimenuitem> + </menuchoice +></term> + <listitem> + <para> + <action> + + Repeats the last edit, following an undo. + + </action> + </para> + </listitem> + </varlistentry> + + <varlistentry id="commands-nv-menu-edit-cut"> + <term +><menuchoice> + <shortcut> + <keycombo +><keycap +>Ctrl</keycap +><keycap +>x</keycap +></keycombo> + </shortcut> + <guimenu +>Edit</guimenu> + <guimenuitem +>Cut</guimenuitem> + </menuchoice +></term> + <listitem> + <para> + <action> + + Removes the selected events from the composition + and places them in the clipboard to replace any + contents the clipboard previously had. + + </action> + </para> + </listitem> + </varlistentry> + + <varlistentry id="commands-nv-menu-edit-copy"> + <term +><menuchoice> + <shortcut> + <keycombo +><keycap +>Ctrl</keycap +><keycap +>c</keycap +></keycombo> + </shortcut> + <guimenu +>Edit</guimenu> + <guimenuitem +>Copy</guimenuitem> + </menuchoice +></term> + <listitem> + <para> + <action> + + Copies the selected events to the clipboard + to replace any contents the clipboard previously had. + + </action> + </para> + </listitem> + </varlistentry> + + <varlistentry id="commands-nv-menu-edit-paste"> + <term +><menuchoice> + <shortcut> + <keycombo +><keycap +>Ctrl</keycap +><keycap +>v</keycap +></keycombo> + </shortcut> + <guimenu +>Edit</guimenu> + <guimenuitem +>Paste</guimenuitem> + </menuchoice +></term> + <listitem> + <para> + <action> + + Copies the contents of the clipboard to the + location of the insert cursor in the current + composition. + + </action> + + The clipboard must not contain + multiple segments, and there must be enough + space (occupied only by rests) starting at + the insert cursor position to accommodate the + clipboard's contents. + + </para> + </listitem> + </varlistentry> + + <varlistentry id="commands-nv-menu-edit-cut-and-close"> + <term +><menuchoice> + <shortcut> + <keycombo +><keycap +>Ctrl</keycap +><keycap +>Shift</keycap +><keycap +>x</keycap +></keycombo> + </shortcut> + <guimenu +>Edit</guimenu> + <guimenuitem +>Cut and Close</guimenuitem> + </menuchoice +></term> + <listitem> + <para> + <action> + + Removes the selected events from the composition + and places them in the clipboard to replace any + contents the clipboard previously had, and closes + the gap left behind by moving all subsequent + events towards the beginning of the composition. + + </action> + </para> + </listitem> + </varlistentry> + + <varlistentry id="commands-nv-menu-edit-paste-dot-dot-dot"> + <term +><menuchoice> + <shortcut> + <keycombo +><keycap +>Ctrl</keycap +><keycap +>Shift</keycap +><keycap +>v</keycap +></keycombo> + </shortcut> + <guimenu +>Edit</guimenu> + <guimenuitem +>Paste...</guimenuitem> + </menuchoice +></term> + <listitem> + <para> + <action> + + Provides a choice of paste mechanisms with the + ability to set one as the default for use in the + Paste menu function. + + </action> + + See the section on <link linkend="nv-paste-types" +>Paste types</link +> for more information. + + </para> + </listitem> + </varlistentry> + + + <varlistentry id="commands-nv-menu-edit-delete"> + <term +><menuchoice> + <shortcut> + <keycombo +><keycap +>Del</keycap +></keycombo> + </shortcut> + <guimenu +>Edit</guimenu> + <guimenuitem +>Delete</guimenuitem> + </menuchoice +></term> + <listitem> + <para> + <action> + Removes the selected events from the composition + and throws them away. + </action> + </para> + </listitem> + </varlistentry> + + + <varlistentry id="commands-nv-menu-edit-select-from-start"> + <term +><menuchoice> + <guimenu +>Edit</guimenu> + <guimenuitem +>Select from Start</guimenuitem> + </menuchoice +></term> + <listitem> + <para> + <action> + Extends the current selection by selecting + all events from the start of the staff up to the + current selection (or up to the insert cursor, + if no events are currently selected). + </action> + </para> + </listitem> + </varlistentry> + + + <varlistentry id="commands-nv-menu-edit-select-to-end"> + <term +><menuchoice> + <guimenu +>Edit</guimenu> + <guimenuitem +>Select to End</guimenuitem> + </menuchoice +></term> + <listitem> + <para> + <action> + Extends the current selection by selecting + all events from the end of the current selection + (or from the insert cursor, if no events are + currently selected) up to the end of the staff. + </action> + </para> + </listitem> + </varlistentry> + + + <varlistentry id="commands-nv-menu-edit-select-whole-staff"> + <term +><menuchoice> + <guimenu +>Edit</guimenu> + <guimenuitem +>Select Whole Staff</guimenuitem> + </menuchoice +></term> + <listitem> + <para> + <action> + Selects all the events on the current staff. + </action> + </para> + </listitem> + </varlistentry> + + + <varlistentry id="commands-nv-menu-edit-clear-selection"> + <term +><menuchoice> + <shortcut> + <keycombo +><keycap +>Esc</keycap +></keycombo> + </shortcut> + <guimenu +>Edit</guimenu> + <guimenuitem +>Clear Selection</guimenuitem> + </menuchoice +></term> + <listitem> + <para> + <action> + Unselects all events. + </action> + </para> + </listitem> + </varlistentry> + + + <varlistentry id="commands-nv-menu-edit-filter-selection"> + <term +><menuchoice> + <guimenu +>Edit</guimenu> + <guimenuitem +>Filter Selection</guimenuitem> + </menuchoice +></term> + <listitem> + <para> + <action> + Invokes an event filter dialog. + </action> + This offers you the ability to filter a range of events in + any of several categories out of your selection. + </para> + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-eventfilter.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>The event filter dialog</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + <para> + All ranges may be either inclusive or exclusive. + </para> + <para> + An inclusive range will remove events on either side of it + from the selection. You can use this, for example, to + filter everything below middle C and above the A above + middle C out of your selection. + </para> + <para> + An exclusive range will remove the events within the range + itself, leaving everything on either side of it selected. + Using the same search points as in the previous example, + you would use an exclusive range to remove everything + between middle C and the A above middle C from your + selection, while leaving everything above and below that + range selected. + </para> + <para> + Once your selection has been filtered, you can manipulate + it by any conventional means. + </para> + </listitem> + </varlistentry> + + + <varlistentry id="commands-nv-menu-edit-add-tempo"> + <term +><menuchoice> + <guimenu +>Edit</guimenu> + <guimenuitem +>Add Tempo Change...</guimenuitem> + </menuchoice +></term> + <listitem> + <para> + <action> + Invokes a tempo change dialog. + </action> + This offers a + selection of ways to change the tempo of the + composition, including changing the tempo from the + insert cursor position onwards, from the last + tempo change onwards, or for the entire + composition. See + +for more information. + </para> + </listitem> + </varlistentry> + + + <varlistentry id="commands-nv-menu-edit-add-time-signature"> + <term +><menuchoice> + <guimenu +>Edit</guimenu> + <guimenuitem +>Add Time Signature Change...</guimenuitem> + </menuchoice +></term> + <listitem> + <para> + <action> + + Invokes a time-signature change dialog. + + </action> + + This offers a + selection of ways to change the tempo ofthe + composition, including changing the time signature + from the insert cursor position onwards or from the + start of the current bar. See +Changing the Time Signature + + for more information. + + </para> + </listitem> + </varlistentry> + + + <varlistentry id="commands-nv-menu-edit-add-clef"> + <term +><menuchoice> + <guimenu +>Edit</guimenu> + <guimenuitem +>Add Clef Change...</guimenuitem> + </menuchoice +></term> + <listitem> + <para> + <action> + + Invokes a clef selection dialog, and inserts the + chosen clef at the current insert cursor position. + + </action> + + The dialog allows you to choose a clef, but also + to choose how you want the clef to be applied, in + cases where there are already some notes following + the point where the clef is to be inserted. You + must choose one of the following: + + <variablelist> + + <varlistentry> + <term +>Maintain current pitches</term> + <listitem> + <para> + Any notes following the clef will keep + their current performance pitches. + </para> + <para> + For example, inserting a + tenor clef in the middle of a previously + treble-clef section will cause the notes following + the clef to be moved an octave + higher up the staff, because they will still have + their treble-clef pitches. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>Transpose into appropriate octave</term> + <listitem> + <para> + Any notes following the clef will + retain their pitch within the octave, but + may be moved into a different octave to + match the new clef, and therefore will play + at a new pitch. + </para> + <para> + For example, inserting a tenor clef in the + middle of a previously treble-clef section + will cause the notes following the clef to + move by one staff line only to adjust to the new + clef, but to play an octave lower than before. + </para> + </listitem> + </varlistentry> + + </variablelist> + + </para> + </listitem> + </varlistentry> + + + <varlistentry id="commands-nv-menu-edit-add-key-signature"> + <term +><menuchoice> + <guimenu +>Edit</guimenu> + <guimenuitem +>Add Key Change...</guimenuitem> + </menuchoice +></term> + <listitem> + <para> + <action> + + </action> + </para> + </listitem> + </varlistentry> + + + </variablelist> + </para> + + </sect2> + + <sect2 id="commands-nv-menu-group"> + <title +>Group menu</title> + <para> + <variablelist> + + + <varlistentry id="commands-nv-menu-group-beam"> + <term +><menuchoice> + <guimenu +>Group</guimenu> + <guimenuitem +>Beam Group</guimenuitem> + </menuchoice +></term> + <listitem> + <para> + <action> + Makes the selected notes into a beamed group. + </action> + </para> + </listitem> + </varlistentry> + + + <varlistentry id="commands-nv-menu-group-auto-beam"> + <term +><menuchoice> + <guimenu +>Group</guimenu> + <guimenuitem +>Auto-Beam</guimenuitem> + </menuchoice +></term> + <listitem> + <para> + <action> + Scans the area covered by the selection and attempts + to group short notes into plausible beamed groups. + </action> + </para> + </listitem> + </varlistentry> + + + <varlistentry id="commands-nv-menu-group-break-group"> + <term +><menuchoice> + <guimenu +>Group</guimenu> + <guimenuitem +>Unbeam</guimenuitem> + </menuchoice +></term> + <listitem> + <para> + <action> + Removes the selected notes from any beamed groups + they may be part of, leaving them as separate + individuals. + </action> + If part of a beamed group is selected, the unselected + part of the group will remain beamed. + </para> + </listitem> + </varlistentry> + + <varlistentry id="commands-nv-menu-group-tuplet"> + <term +><menuchoice> + <guimenu +>Group</guimenu> + <guimenuitem +>Tuplet</guimenuitem> + </menuchoice +></term> + <listitem> + <para> + <action> + Makes a triplet or other tuplet group. + </action> + This function allows you to adjust the timing of a + short section of music in the ratio of two + durations, for example to indicate that three notes + should be played in the time of two (the classic + triplet), or nine in the time of six, or whatever. + You can set this ratio in a dialog box when you + invoke the function. + </para> + <para> + If you have selected some events before invoking the + function, it will assume that you want to make a + tuplet group out of the selected region (or as close + to its duration as possible) and will adjust the + default values available in the dialog accordingly. + </para> + </listitem> + </varlistentry> + + + <varlistentry id="commands-nv-menu-group-simple-tuplet"> + <term +><menuchoice> + <guimenu +>Group</guimenu> + <guimenuitem +>Simple Tuplet</guimenuitem> + </menuchoice +></term> + <listitem> + <para> + <action> + + Makes a tuplet group (normally of triplets) with + the most apparently obvious ratio of durations. + + </action> + Usually this function will attempt to make a triplet + group starting at the current insert cursor, or if + some events are selected, will attempt to make them + into triplets. It is possible that it might end up + making non-triplet groups if there is no obvious + valid triplet arrangement. + </para> + </listitem> + </varlistentry> + + + <varlistentry id="commands-nv-menu-group-grace"> + <term +><menuchoice> + <guimenu +>Group</guimenu> + <guimenuitem +>Make Grace Notes</guimenuitem> + </menuchoice +></term> + <listitem> + <para> + <action> + Converts the selected notes into grace notes. + </action> + </para> + </listitem> + </varlistentry> + + + + <varlistentry id="commands-nv-menu-group-ungrace"> + <term +><menuchoice> + <guimenu +>Group</guimenu> + <guimenuitem +>Ungrace</guimenuitem> + </menuchoice +></term> + <listitem> + <para> + <action> + Converts any grace notes in the selection to + normal notes. + </action> + </para> + </listitem> + </varlistentry> + + + + <varlistentry id="commands-nv-menu-group-slur"> + <term +><menuchoice> + <guimenu +>Group</guimenu> + <guimenuitem +>Slur</guimenuitem> + </menuchoice +></term> + <listitem> + <para> + <action> + Adds a slur across the selected notes. + </action> + To remove the slur, click on it + with the erase tool just as you would for a note. + </para> + </listitem> + </varlistentry> + + + + <varlistentry id="commands-nv-menu-group-crescendo"> + <term +><menuchoice> + <guimenu +>Group</guimenu> + <guimenuitem +>Crescendo</guimenuitem> + </menuchoice +></term> + <listitem> + <para> + <action> + Adds a crescendo (opening hairpin) indication + across the selected notes. + </action> + To remove the crescendo indication, click on it + with the erase tool just as you would for a note. + </para> + </listitem> + </varlistentry> + + + + <varlistentry id="commands-nv-menu-group-decrescendo"> + <term +><menuchoice> + <guimenu +>Group</guimenu> + <guimenuitem +>Decrescendo</guimenuitem> + </menuchoice +></term> + <listitem> + <para> + <action> + Adds a decrescendo (closing hairpin) indication + across the selected notes. + </action> + To remove the decrescendo indication, click on it + with the erase tool just as you would for a note. + </para> + </listitem> + </varlistentry> + + + </variablelist> + </para> + + </sect2> + + <sect2 id="commands-nv-menu-notes"> + <title +>Notes menu</title> + <para> + <variablelist> + + <varlistentry id="commands-nv-menu-notes-"> + <term +><menuchoice> + <guimenu +>Notes</guimenu> + <guimenuitem +></guimenuitem> + </menuchoice +></term> + <listitem> + <para> + <action> + + </action> + </para> + </listitem> + </varlistentry> + + + <varlistentry id="commands-nv-menu-notes-style-actionmenu"> + <term +><menuchoice> + <guimenu +>Notes</guimenu> + <guimenuitem +>Note Style</guimenuitem> + </menuchoice +></term> + <listitem> + <para> + <action> + Change the note style of the selected notes. + </action> + This submenu contains an entry for each of the <link + linkend="nv-note-styles" +>note + styles</link +> that are currently available. Choosing one + will change the note style of the selected notes to + that style. + </para> + </listitem> + </varlistentry> + + + <varlistentry id="commands-nv-menu-notes-stems"> + <term +><menuchoice> + <guimenu +>Notes</guimenu> + <guimenuitem +>Stem Direction</guimenuitem> + </menuchoice +></term> + <listitem> + <para> + <action> + Change the stem + direction of the selected notes. + </action> + This submenu allows you to specify that all the + <link linkend="nv-note-qualities" +>stems</link +> of + the selected notes should point up or down, plus an + entry to reset the stem directions to those that + Rosegarden originally chose for the notes. + </para> + </listitem> + </varlistentry> + + + <varlistentry id="commands-nv-menu-notes-slashes"> + <term +><menuchoice> + <guimenu +>Notes</guimenu> + <guimenuitem +>Slashes</guimenuitem> + </menuchoice +></term> + <listitem> + <para> + <action> + Add diagonal + slashes across the selected notes' stems. + </action> + This submenu allows you to choose a number of + diagonal strokes or <link linkend="nv-note-qualities" +>slashes</link +> to be drawn across the + stems of each of the selected notes. These may be + used, for example, to indicate repetition or rolls + to a human reader. They do not (yet) affect + performance using Rosegarden. + </para> + </listitem> + </varlistentry> + + </variablelist> + </para> + + </sect2> + + <sect2 id="commands-nv-menu-marks"> + <title +>Marks menu</title> + <para> + <variablelist> + <varlistentry> + <term +><menuchoice> + <guimenu +>blah</guimenu> + <guimenuitem +>blah</guimenuitem> + </menuchoice +></term> + <listitem> + <para +>to be continued</para> + </listitem> + </varlistentry> + </variablelist> + </para> + + </sect2> + + <sect2 id="commands-nv-menu-transforms"> + <title +>Transforms menu</title> + <para> + <variablelist> + + <varlistentry id="commands-nv-menu-transforms-normalize-rests"> + <term +><menuchoice> + <guimenu +>Transforms</guimenu> + <guimenuitem +>Normalize Rests</guimenuitem> + </menuchoice +></term> + <listitem> + <para> + <action +>Makes the rests in the selection + theoretically correct.</action> + + This function examines each sequence of consecutive + rests found in the selection, and adjusts, splits + and merges rests as necessary to ensure that the + rests have theoretically correct durations and fall + on the correct boundaries. + </para> + + <para +>For example, a 4/4 bar containing a crotchet + (quarter-note), then a minim (half-note) rest and a + crotchet rest will be rearranged to place the crotchet + rest first, as the minim rest should not cross the + central beat boundary of the bar. + </para> + + <para +>This function is also useful in occasional + situations where Rosegarden has made a bad job of + maintaining the rests correctly within a bar, for + example when editing imported &MIDI; data. Normalizing + the rests will usually make the arrangement of notes + in such a situation a bit clearer. (Rosegarden always + normalizes the rests as a matter of course when + importing or recording &MIDI;, but things can sometimes + get muddled up again.)</para> + + </listitem> + </varlistentry> + + <varlistentry id="commands-nv-menu-transforms-collapse-rests"> + <term +><menuchoice> + <guimenu +>Transforms</guimenu> + <guimenuitem +>Collapse Rests</guimenuitem> + </menuchoice +></term> + <listitem> + <para> + <action +>Makes multiple short rests into fewer longer + ones.</action> + + This function merges consecutive rests into longer + rests, wherever possible. That is, wherever two + consecutive rests in the selection are found to have + a total duration expressible as a single longer + rest, they will be merged. + </para> + </listitem> + </varlistentry> + + <varlistentry id="commands-nv-menu-transforms-collapse-notes"> + <term +><menuchoice> + <guimenu +>Transforms</guimenu> + <guimenuitem +>Collapse Equal-Pitch Notes</guimenuitem> + </menuchoice +></term> + <listitem> + <para> + <action +>Makes multiple short notes into fewer longer + ones.</action> + + This function merges consecutive notes into longer + notes, wherever possible. That is, wherever two + consecutive notes of equal pitch in the selection + are found to have a total duration expressible as a + single longer note, they will be merged. + </para> + </listitem> + </varlistentry> + + <varlistentry id="commands-nv-menu-transforms-tie-notes"> + <term +><menuchoice> + <guimenu +>Transforms</guimenu> + <guimenuitem +>Tie Equal-Pitch Notes</guimenuitem> + </menuchoice +></term> + <listitem> + <para +><action +>Ties consecutive notes whenever possible.</action> + + This function ties together any consecutive notes of + equal pitch found in the selection. Tied notes are + shown with a curved line joining the note heads, and + are played as a single long note. + </para> + </listitem> + </varlistentry> + + <varlistentry id="commands-nv-menu-transforms-untie-notes"> + <term +><menuchoice> + <guimenu +>Transforms</guimenu> + <guimenuitem +>Untie Notes</guimenuitem> + </menuchoice +></term> + <listitem> + <para +><action +>Breaks ties between notes.</action> + + Any tied notes found in the selection are untied, + and will subsequently be played as separate + notes.</para> + </listitem> + </varlistentry> + + <varlistentry id="commands-nv-menu-transforms-make-viable"> + <term +><menuchoice> + <guimenu +>Transforms</guimenu> + <guimenuitem +>Make Notes Viable</guimenuitem> + </menuchoice +></term> + <listitem> + <para +><action +>Splits notes at displayable + durations.</action +> This function is intended to deal + with notes that have excessively long durations that + overflow barlines or that are too long to be displayed + as a single note. It takes any such notes and splits + them into shorter, tied notes. + </para> + </listitem> + </varlistentry> + + <varlistentry id="commands-nv-menu-transforms-de-counterpoint"> + <term +><menuchoice> + <guimenu +>Transforms</guimenu> + <guimenuitem +>De-Counterpoint</guimenuitem> + </menuchoice +></term> + <listitem> + <para +><action +>Turns counterpoint into a series of split-and-tied notes and chords.</action> + + &rosegarden; has no explicit support for counterpoint + (multiple lines of notes edited separately on the + same staff), but it will do its best to approximate + it when it finds notes in a segment that are + apparently contrapuntal, i.e. that overlap but that + are not precise enough to be treated as chords. For + example, when a short note starts shortly after a + longer note, Rosegarden will show the longer note + and a short <quote +>spacing</quote +> rest together, followed by the + shorter note. Unfortunately this often isn't what + you want. + </para> + + <para +>The De-Counterpoint function can be applied to a + selection that contains overlapping notes. It will + split overlapping notes at the point where they + overlap, and tie together the resulting split notes, + ensuring that the music takes the form of a series of + chords and/or single notes starting and ending in neat + blocks, with some notes possibly tied. + </para> + </listitem> + </varlistentry> + + <varlistentry id="commands-nv-menu-transforms-quantize"> + <term +><menuchoice> + <guimenu +>Transforms</guimenu> + <guimenuitem +>Quantize...</guimenuitem> + </menuchoice +></term> + <listitem> + <para +><action +>Quantizes the selection.</action +></para> + </listitem> + </varlistentry> + + <varlistentry id="commands-nv-menu-transforms-fix-smoothing"> + <term +><menuchoice> + <guimenu +>Transforms</guimenu> + <guimenuitem +>Fix Smoothed Values</guimenuitem> + </menuchoice +></term> + <listitem> + <para +><action +>Makes the note durations in the current + view permanent.</action> + + When notating recorded or performance &MIDI;, + Rosegarden usually has to round off the durations of + some notes so that they can be displayed as normal + note types. This is known as <link + linkend="nv-quantization" +>smoothing</link +>, and it + normally does not affect the notes actually played, + it's just a convenience for display. The Fix + Smoothed Values function takes the current smoothed + note durations and sets them such that they are used + for performance (and editing in the matrix view, + etc) as well as for notation. + </para> + </listitem> + </varlistentry> + + <varlistentry id="commands-nv-menu-transforms-interpret"> + <term +><menuchoice> + <guimenu +>Transforms</guimenu> + <guimenuitem +>Interpret...</guimenuitem> + </menuchoice +></term> + <listitem> + <para +><action +>Modifies the velocities and timings of + notes according to any written or indicated dynamics + found.</action +> The selection of interpretations + available is as follows: + + <variablelist> + <varlistentry> + <term +>Apply text dynamics (p, mf, ff etc) + </term> + <listitem +><para +> Sets a velocity to each note + based on the last piece of text of "Dynamic" + type seen on the same staff (only texts of the + form pp, p, mp, mf, f, ff, fff etc are matched). + </para +></listitem> + </varlistentry> + + <varlistentry> + <term +>Apply hairpin dynamics + </term> + <listitem +><para +> Makes the notes gradually + increase or decrease in velocity during a + crescendo or decrescendo hairpin. + </para +></listitem> + </varlistentry> + + <varlistentry> + <term> + Stress beats + </term> + <listitem +><para +> Makes notes that land on bar or + beat boundaries slightly louder (greater + velocity) than the surrounding notes. + </para +></listitem> + </varlistentry> + + <varlistentry> + <term> + Articulate slurs, staccato, tenuto etc + </term> + <listitem +><para +> Shortens unslurred notes, + shortens staccato notes more, and gives notes + inside slurs and tenuto notes their full length. + </para +></listitem> + </varlistentry> + </variablelist> + + </para> + + </listitem> + </varlistentry> + + <varlistentry id="commands-nv-menu-transforms-transpose"> + <term +><menuchoice> + <guimenu +>Transforms</guimenu> + <guimenuitem +>Transpose</guimenuitem> + </menuchoice +></term> + <listitem> + <para +><action +>Alters the pitch of the selected + notes.</action +> This submenu contains basic + transposition functions which move the selected notes + up or down a semitone or a whole octave in pitch, as + well as a general transpose function that allows you + to choose how far up or down you want to transpose the + selection. + </para> + + <para +>These functions simply change the stored pitches + of the notes in the selection, so that they both play + and appear at the new pitches. They do not deal with + performance transposition (displaying one pitch and + playing another), for which see the main window's + segment parameter box; nor do they help you with + transposing from one key into another, for which see + the <link + linkend="commands-nv-menu-edit-add-key-signature" +>key + change</link +> function. + </para> + </listitem> + </varlistentry> + + </variablelist> + </para> + + </sect2> + + + </sect1> + </chapter> + +--> + + + <!-- + ********************************** + + PART III: + Technical material + + ********************************** + --> + + <chapter id="developers"> + <title +>Personalizando Rosegarden</title> + + <sect1 id="developers-note-fonts"> + <title +>Configurando fuentes de notación personales</title> + + <para +>Si dispone de una fuente de notación en su sistema en un formato escalable (TrueType o Type-1) pero no es actualmente soportado por Rosegarden, puede crear su propio archivo de mapeo XML para describir el mapa de caracteres y métrica de la fuente de una forma que Rosegarden pueda usar. Éstos archivosson instalados en el subdirectorio fonts/mapping del directorio de instalación de Rosegarden, y un número de ejemplos son incluídos con la distribución.</para> + + <para +>También puede usar estos archivos de mapeo para definir nuevas fuentes basadas en mapas de pixeles (pixmaps), donde cada forma en un tamaño particular es cargada de un mapa de pixeles diferente. Las dos fuentes estándar de notación proveídas con Rosegarden-4 son fuentes de mapa de pixeles definidas en exactamente ésta forma. </para> + + <para +>Es incluso posible definir una fuente de notación usando una o mas fuentes escalables del sistema, aumentadas con mapas de pixeles para tamaños particulares o para caracteres que no se encuentran en fuentes escalables. Ésto es porquela mayoría del formato del archivo de mapeo es el mismo para fuentes escalables y de mapa de pixeles, y cuando hay diferentes elementos para los diferentes tipos de fuentes, es usualmente posible incluir ambos de ellos. Rosegarden va a usar usualmente mapas de pixeles donde se los disponga y fuentes escalables en caso contrario. </para> + + <para +>Quizás quiera editar los archivos de mapeo provistos con Rosegarden si encuentra que sus dimensiones para alineación o tamaño no son de su preferencia (si cree que cualquiera de los archivos provistos están equivocados, por favor háganoslo saber). </para> + + <sect2 id="developers-note-fonts-codes-glyphs"> + <title +>Codas y Glipses</title> + + <para +></para> + </sect2> + + <sect2 id="developers-note-fonts-mapping-format"> + <title +>Formato de mapeo XML de las fuentes de notación</title> + + <para +>Aquí hay un sumario de los elementos XML que pueden ser usados en el archivo de mapeo de fuentes.</para> + + <sect3 id="developers-note-fonts-mapping-format-font-encoding"> + <title +>rosegarden-font-encoding</title> + + <para +>Éste elemento debe existir en cada archivo de mapeo, y debe contener a el resto de los elementos. El único atributo es "name" (nombre), que contiene el nombre de la fuente que es mostrado el el menú desplegable de selección de fuentes. Aunque éste formato de archivo va a permitir que cualquier nombre se utilice aquí, Rosegarden solo usará la fuente correctamente si el archivo XML tiene el mismo nombre que los contenidos de éste atributo (excepto que el archivo XML sea nombrado en minúsculas y termine en ".xml"). </para> + </sect3> + + <sect3 id="developers-note-fonts-mapping-format-font-information"> + <title +>font-information</title> + + <para +>Éste debe normalmente ser el primer elemento hijo de "rosegarden-font-encoding". Puede tener alguno de los siguientes atributos, todos ellos opcionales: <variablelist> + <varlistentry> + <term +>origin</term> + <listitem> + <para +>Una descripción textual del origen de la fuente mapeada (no del origen del archivo de mapeo).</para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>copyright</term> + <listitem> + <para +>Una descripción textual del estátus del derecho de copia (copyright) de la fuente mapeada (no el estátus de copyright del archivo de mapeo). Note que debido a que el archivo de mapeo contenga información como el origen y copyright de la fuente misma, es usualmente recomendable hacer archivos de mapeo separados para fuentes separadas mientras sea práctico, incluso si las fuentes compartem otros datos de mapeo.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>mapped-by</term> + <listitem> + <para +>El nombre del creador del archivo de mapeo (i.e. usted, presumiblemente).</para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>type</term> + <listitem> + <para +>El tipo de la fuente. éste atributo debe contener uno de los valores "pixmap" o "scalable". Las fuentes que son cargadas en el sistema de ventanas están disponibles para Rosegarden como fuentes estándar del sistema del tipo "scalable", las fuentes que necesitan ser cargadas de archivos de mapa de pixeles correspondientes a tamaños individuales de mapa de pixeles (como las fuentes feta y rg21 incluídas en Rosegarden) son del tipo "pixmap".</para> + + <para +>Ésta información pretende ser solo para referencia del usuario, realmente no es usada por Rosegarden. En la práctica, para una fuente es legítimo ser una mezcla de los dos, pero en general asumiremos en ésta documentación que una fuente es o escalable o de mapa de pixeles.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>smooth</term> + <listitem> + <para +>Un atributo booleano que indica si la fuente utiliza antialiasing (suave o smooth) o no. Debe tener el valor "true" (verdadero) o "false" (falso). Si la fuente es suave (smooth), otros elementos como ligaduras que no son generados desde la fuente serán también suaves (antialiased).</para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>autocrop</term> + <listitem> + <para +>Sólo importante para fuentes escalables (del sistema). Rosegarden normalmente espera que las medidas de una fuente contengan las mas pequeñas cajas contenedoras para elementos como cabezas de notas y acentos, mas que incluir espacio libre por sobre o debajo de éstos elementos para propósitos de alineación. La mayoría de las fuentes no hacen lo que Rosegarden espera. Por lo tanto, éstas fuentes deben setar el atrubuto autocrop a "true"; luego Rosegarden va a recortar cualquier espacio innecesario de la parte superior o inferior de éstos elementos cuando los renderiza.</para> + </listitem> + </varlistentry> + + </variablelist> + + </para> + </sect3> + + <sect3 id="developers-note-fonts-mapping-format-font-requirements"> + <title +>font-requirements</title> + <para +>Éste elemento es solo importante para fuentes escalables. es usado para especificar que ésta fuente debe solo ser ofrecida si ciertos tipos de fuentes se encuentran disponibles, como también para asociar IDs con aquellas fuentes del sistema a las que referirse en el elemento <link linkend="developers-note-fonts-mapping-format-font-symbol-map" +>font-symbol-map</link +>. Éste esquema es usado para decidir que fuentes de notación deben ser ofrecidas al usuario, y también permite crear una fuente de notación para Rosegarden desde mas de una fuente de sistema si así lo desea. </para> + <para +>El elemento "font-requirements" debe contener una lista de elementos "font-requirement" hijos. Cada uno de ellos tiene dos atributos: "font-id", contiene un ID numéricode su preferencia para referirse en otro lugar del archivo, y también un atributo "nme" o "names". Si se utiliza "name", se interpretará como el nombre de una sola fuente del sistema asociada al id de la fuente; si se utiliza "names", será tratado como una lista separada por comasde fuentes del sistema, y la primera que se encuentre será asociada al id de fuente. </para> + </sect3> + + <sect3 id="developers-note-fonts-mapping-format-font-sizes"> + <title +>font-sizes</title> + + <para +>El elemento "font-sizes" especifica que tamaños de fuente de notación se encuentran disponibles, y como los tamaños de fuente nominales se relacionan con las dimensiones de elementos no-fuente como plicas, pentagramas y ligaduras. El atributo "size" (tamaño) de una fuente de notación se asume de ser la distancia en pixeles entre lineas del pentagrama, o mas precisamente, la altura de una cabeza de nota convencional que rellena completamente el espacio entre líneas: por lo tanto, el tamaño no incluye el grosor o la proximidad de las líneas del pentagrama. </para> + + <para +>Existen dos posibles elementos hijos de "font-sizes": "font-scale" y "font-size". Su uso depende del tipo de fuente que se está describiendo.</para> + + <para +>Para fuentes de mapa de pixeles (no escalables), el elemento "font-sizes" debe contener una lista de elementos "font-size", uno para cada tamaño de mapa de bits disponible. Los mapas de bits por sí mismos deben ser instalados en el subdirectorio fonts/<font-name>/<font-size> del directorio de instalación de Rosegarden, donde <font-name>es el nombre de la fuente (como fué especificado en el elemento "rosegarden-font-encoding" al comienzo del archivo de mapeo), o una versión en minúsculas del nombre, y <font-size> es el tamaño en pixeles de la fuente. Un tamaño específico será disponible al usuario solo si tiene una entrada en la lista "font-sizes" y el directorio de mapa de pixeles es encontrado. </para> + + <para +>Para fuentes escalables, el elemento "font-sizes" debería contener un elemento "font-scale" que define la relación entre elementos de fuente y no-fuente en una forma general, y también define la relación entre el tamaño nominal de fuente de Rosegarden y el tamaño de la fuente de sistema correspondiente. Si el elemento "font-scale" no se encontrara, entonces Rosegarden asumirá que la fuente se encuentra disponible en cualquier tamaño. De todas maneras se puede incluir uno o mas elementos "font-size" para definir proporciones precisaspara cualquier tipo particular de tamaño para los cuales las proporciones generales no funcionan correctamente, por ejemplo debido a un error de redondeo. </para> + + <para +>Los atributos de "font-scale" y "font-size" son muy similares. La diferencia principal es que todos los atributos de "font-scale" son valores de punto flotante relativos al tamaño de la fuente, donde 1.0 es el tamaño de la fuente base (i.e. la distancia entre líneas del pentagrama), mientras que los atributos de "font-size" son valores enteros de pixeles. Los atributos disponibles son los siguientes. Aquellos marcados como "optional" tienen resultados vagamente sensibles, por lo que es una buena idea tratar de no setearlos primero. </para> + + <variablelist> + + <varlistentry> + <term +>note-height</term> + <listitem> + <para +>Éste atributo se encuentra disponible solo para el elemento "font-size", y es obligatorio en ése elemento. Define el tamaño base de la fuente en el cuál los otros atributos se aplican, y un tamaño que será ofrecido al usuario y usado al momento de buscar mapas de pixeles para ésta fuente.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>font-height</term> + <listitem> + <para +>Puede ser usado tanto en "font-size" como en "font-scale". Es sólo relevante para fuentes escalables, pero es obligatorio para ellos si es usado en el elemento "font-scale". Define el tamaño de la fuente de sistema usada para dibujar un tamaño dado de fuente de notación.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>beam-thickness</term> + <listitem> + <para +>Opcional. Define el grosor de una ligadura.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>staff-line-thickness</term> + <listitem> + <para +>Opcional. Define el grosor de una línea de pentagrama.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>stem-thickness</term> + <listitem> + <para +>Opcional. Define la anchura de un note stem.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>flag-spacing</term> + <listitem> + <para +>Opcional. Define el espacio entre note flags en los casos en donde se dibujan múltiples flags repitiendo uno muchas veces.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>border-x</term> + <listitem> + <para +>Opcional. Especifica que los mapas de pixels de los note heads tienen un área fija a derecha e izquierda que no debe ser considerada parte del mismo. Este atributo fija la anchura de ese área.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>border-y</term> + <listitem> + <para +>Opcional. Especifica que los mapas de pixels de los note heads tienen un área fija arriba y abajo que no debe ser considerada parte del mismo. Este atributo fija la anchura de ese área.</para> + </listitem> + </varlistentry> + + </variablelist> + </sect3> + + <sect3 id="developers-note-fonts-mapping-format-font-symbol-map"> + <title +>mapa tipo de letra-simbolo</title> + <para +>Este elemento lista los símbolos disponibles en este tipo de letra, y desde que archivos de mapa de pixeles o tipos de letra del sistema debe dibujarse.</para> + + <para +>Debería contener una lista de elementos "símbolo". Estos tienen numerosos atributos posibles, la elección de los cuales dependerá de si la fuente esta basada en mapas de pixeles o tipos de letra del sistema. </para> + + <variablelist> + <varlistentry> + <term +>name</term> + <listitem> + <para +>Obligatorio. Este atributo debería contener el nombre del símbolo. Si el símbolo existe en el <ulink url="http://www.unicode.org/charts/PDF/U1D100.pdf" +>estándar Unicode 3.2</ulink +>, el nombre debería usarse para identificar el símbolo en el estándar.</para> + + <para +>La mayoría de los símbolos que Rosegarden espera encontrar están en el estándar; una excepción es que muchas fuentes tienen una versión especial del símbolo flag, que se utiliza en los casos en donde se componen múltiples flags a partir de uno solo. Rosegarden se refiere a esto como "MUSICAL SYMBOL COMBINING FLAG-0", un nombre no utilizado en el estándar Unicode (que tiene los flags 1-5 solamente).</para> + + <para +>Para una lista definitiva de los nombres de símbolo reconocidos por Rosegarden, vea el archivo "gui/notecharname.cpp" en su código fuente. Notar, sin embargo, que es posible usar nombres de símbolo adicionales introduciéndolos en <link linkend="developers-note-styles" +>estilo notación</link +>. </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>src</term> + <listitem> + <para +>El nombre del archivo de mapa de pixels desde donde se carga el símbolo, sin directorio o extensión. Esta es la forma usual de describir un símbolo en un tipo de letra pixmap. El archivo en si debe ser instalado en fonts/<font-name>/<font-size>/<src>.xpm dentro del directorio de instalación de Rosegarden. </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>inversion-src</term> + <listitem> + <para +>El nombre del archivo de mapa de pixels desde donde se carga la versión invertida del símbolo, sin directorio o extensión. Si este atributo esta ausente y se requiere una versión invertida del símbolo, sera generado cargando la versión normal y reflejándola en el eje x central. </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>code</term> + <listitem> + <para +>El punto del código en el cual se encuentra el símbolo en el tipo de letra del sistema, como un entero decimal. Esta es una manera de describir un símbolo en una fuente escalable. Este atributo solo sera referenciado si no se proporciona un archivo de mapa de pixels o si el mismo falla en el momento de la carga. </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>inversion-code</term> + <listitem> + <para +>El punto del código en donde se encuentra la versión invertida del símbolo en el tipo de letra del sistema. Si este atributo esta ausente y se requiere una versión invertida del símbolo, sera generado cargando la versión normal y reflejándola en el eje x central. </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>glyph</term> + <listitem> + <para +>El índice raw glyph en donde se encuentra el símbolo en el tipo de letra del sistema, como un entero decimal. Esta es una forma de describir un símbolo en un tipo de letra escalable. Este atributo sólo será referenciado si no se proporciona un archivo de mapa de pixels o si falla la carga del mismo. </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>inversion-glyph</term> + <listitem> + <para +>El índice raw glyph en el que se encuentra la versión invertida del símbolo, en el tipo de letra correspondiente. Si se omite este atributo y se necesita una versión invertida del símbolo, el mismo se generará cargando la versión normal y reflejándola en su eje x central. </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>font-id</term> + <listitem> + <para +>El identificador del tipo de letra del sistema desde el cual se cargara el símbolo, según lo definido en el elemento <link linkend="developers-note-fonts-mapping-format-font-requirements" +>requisitos de tipo de letra</link +>. El valor por defecto es 0. </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>codebase</term> + <listitem> + <para +>Este atributo (entero decimal) debe ser útil si muchos de los símbolos en un tipo de letra escalable cubren un rango corto de puntos de código, comenzando en un código de página relativamente alto. Si es incluido, el valor codebase sera agregado a cada uno de los valores de los códigos (y códigos inversos) al buscar un símbolo. </para> + </listitem> + </varlistentry> + + </variablelist> + + <para +>Si bien ninguno de estos atributos es obligatorio excepto el nombre, un símbolo obviamente necesita tener por lo menos algún "src", "inversion-src", "code", "inversion-code", "glyph", or "inversion-glyph" para tener alguna chance de ser interpretado. Por supuesto, es perfectamente legítimo suministrar muchos de estos atributos. </para> + + </sect3> + + <sect3 id="developers-note-fonts-mapping-format-font-hotspots"> + <title +>font-hotspots</title> + <para +> </para> + </sect3> + + </sect2> + + </sect1> + + <sect1 id="developers-note-styles"> + <title +>Creando nuevos estilos de notación</title> + + <para +>El editor de notación de Rosegarden tiene la habilidad de mostrar y editar notas en varios estilos estándar: clásico, diamond heads, etc. Todos estos estilos están definidos mediante archivos XML instalados con la aplicación y es posible crear nuevos escribiendo un simple archivo XML. Rosegarden solo mira el conjunto de archivos instalado para determinar que estilos puede ofrecerle al usuario. Puede ver el conjunto de archivos por defecto en el subdirectorio estilos del directorio de instalación de Rosegarden para ver ejemplos. </para> + + <para +>El formato de archivo no es especialmente comprehensivo aun, por el momento ha sido diseñado para ser lo suficientemente poderoso para describir los estilos estándar incluidos en Rosegarden, pero no mucho mas.Si usted intenta crear nuevos estilos de esta forma, estaremos muy interesados en recibir sus comentarios en la lista de correo de Rosegarden. </para> + + <sect2 id="developers-note-styles-format"> + <title +>Estilo de notación en formato XML</title> + + <para +>Este es un sumario de los elementos XML que pueden usarse en un archivo de definición de estilos. </para> + + <sect3 id="developers-note-styles-note-style"> + <title +>rosegarden-note-style</title> + + <para +>Este elemento debe existir en cada archivo de estilos y debe contener a todos los demás elementos. Tiene un atributo opcional, "base-style", el cual puede usarse para nombrar un estilo del cual el estilo actual toma valores por defecto para cualquier parámetro no especificado en el archivo. Habitualmente es una buena practica definir un estilo en términos de la diferencia mínima con un estilo base dado: vea el archivo Cross.xml proporcionado para un ejemplo particular simple. </para> + + <para +>Notar que el elemento "rosegarden-note-style" no da el nombre del estilo definido, el cual es extraído del nombre del archivo. El el futuro podríamos agregar atributos para nombres de estilo internacionales a este elemento.</para> + </sect3> + + <sect3 id="developers-note-styles-global-note"> + <title +>global, note</title> + + <para +>Con el elemento "rosegarden-note-style", puede haber un elemento "global" y cualquier cantidad de elementos "note". Los describimos juntos porque sus atributos son casi idénticos. El elemento "global" simplemente provee valores por defecto para aquellos parámetros no especificados para un tipo de nota en particular en cualquiera de los elementos "note" que lo siguen. </para> + + <para +>Los atributos para estos elementos son los siguientes. Todos son opcionales, a menos que se indique lo contrario:</para> + + <variablelist> + + <varlistentry> + <term +>type</term> + <listitem> + <para +>Sólo es relevante al elemento "nota", y es obligatorio para ese elemento. Este atributo especifica que clase de nota esta siendo estilizada. Los valores legales son los nombres americanos o ingleses de las notas (desde "64th", "sixth-fourth note", "hemidemisemiquaver" etc, a "double whole note"). </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>shape</term> + <listitem> + <para +>Define la forma de un note head para este estilo. Cualquier cadena de caracteres es un valor legal, pero los únicos valores implementados son "angled oval", "level oval", "breve", "cross", "triangle up", "triangle down", "diamond" y "rectangle". El valor "number" también es reconocido pero no esta implementado aun. </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>charname</term> + <listitem> + <para +>Define un nombre de carácter para ser usado como note head para este estilo. Un elemento puede proporcionar un atributo "shape" o "charname", pero no ambos. El nombre debería ser uno de los definidos en el tipo de letra de la notación actual... ??? </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>filled</term> + <listitem> + <para +>Especifica cuando esta nota debería tener filled head (cuando es aplicable, por ejemplo cuando el atributo shape proporciona una forma disponible como filled o unfilled). Debe ser "true" o "false". </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>stem</term> + <listitem> + <para +>Especifica cuando esta nota debería tener un stem. Debe ser "true" o "false". </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>flags</term> + <listitem> + <para +>Define cuantos flags o beams debe tener esta nota. El rango válido es entre 0 y 4. </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>slashes</term> + <listitem> + <para +>Define cuantos slashes debe tener esta nota a través de su stem. </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>hfixpoint</term> + <listitem> + <para +>Especifica en que posición x se fija el stem al note head. Los valores aceptables son "normal" (el lado derecho cuando el stem apunta hacia arriba, el izquierdo cuando apunta hacia abajo), "central" y "reversed" (lado izquierdo cuando el stem apunta hacia arriba, derecho cuando apunta hacia abajo). </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>vfixpoint</term> + <listitem> + <para +>Especifica en que posición y se fija al stem al note head. Los valores aceptables son "near" (el stem se fija al tope cuando apunta hacia arriba, a la parte inferior cuando apunta hacia abajo), "middle", o "far". </para> + </listitem> + </varlistentry> + + </variablelist> + </sect3> + </sect2> + </sect1> + + + <!-- (OPTIONAL) A Programming/Scripting reference chapter should be + used for apps that use plugins or that provide their own scripting hooks + and/or development libraries. --> + + <!-- cc: I think we should document the DCOP API here, but I don't + think we should include extensive developer docs, although we should + point to where they can be found in the source tree or online. --> + <!-- + <para> + Programming <application +>Rosegarden</application +> plugins is + a joy to behold. Just read through the next + 66 pages of <acronym +>API</acronym +>'s to learn how! + </para> + --> + <!-- Use refentries to describe APIs. Refentries are fairly + complicated and you should consult the docbook reference for + further details. The example below was taken from that reference + and shortened a bit for readability. --> + <!-- + <refentry id="re-1007-unmanagechildren-1"> + <refmeta> + <refentrytitle +>XtUnmanageChildren</refentrytitle> + <refmiscinfo +>Xt – Geometry Management</refmiscinfo> + </refmeta> + <refnamediv> + <refname +>XtUnmanageChildren + </refname> + <refpurpose +>remove a list of children from a parent widget's managed list. + </refpurpose> + </refnamediv> + <refsynopsisdiv> + <refsynopsisdivinfo> + <date +>4 March 1996</date> + </refsynopsisdivinfo> + <synopsis +> + void XtUnmanageChildren(<replaceable>children</replaceable>, <replaceable>num_children</replaceable>) + WidgetList <replaceable>children</replaceable>; + Cardinal <replaceable>num_children</replaceable>; + </synopsis> + + <refsect2 id="r2-1007-unmanagechildren-1"> + <title +>Inputs</title> + <variablelist> + <varlistentry> + <term +><replaceable +>children</replaceable> + </term> + <listitem> + <para> + Specifies an array of child widgets. Each child must be of + class RectObj or any subclass thereof. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term +><replaceable +>num_children</replaceable> + </term> + <listitem> + <para +>Specifies the number of elements in <replaceable +>children</replaceable +>. + </para> + </listitem> + </varlistentry> + </variablelist> + </refsect2 +></refsynopsisdiv> + + <refsect1 id="r1-1007-unmanagechildren-1"> + <title +>Description + </title> + <para> + <function +>XtUnmanageChildren()</function +> unmaps the specified widgets + and removes them from their parent's geometry management. + The widgets will disappear from the screen, and (depending + on its parent) may no longer have screen space allocated for + them. + </para> + <para +>Each of the widgets in the <replaceable +>children</replaceable +> array must have + the same parent. + </para> + <para +>See the “Algorithm” section below for full details of the + widget unmanagement procedure. + </para> + </refsect1> + + <refsect1 id="r1-1007-unmanagechildren-2"> + <title +>Usage</title> + <para> + Unmanaging widgets is the usual method for temporarily + making them invisible. They can be re-managed with + <function +>XtManageChildren()</function +>. + </para> + <para> + You can unmap a widget, but leave it under geometry + management by calling <function +>XtUnmapWidget()</function +>. You can + destroy a widget's window without destroying the widget by + calling <function +>XtUnrealizeWidget()</function +>. You can destroy a + widget completely with <function +>XtDestroyWidget()</function +>. + </para> + <para> + If you are only going to unmanage a single widget, it is + more convenient to call <function +>XtUnmanageChild()</function +>. It is + often more convenient to call <function +>XtUnmanageChild()</function> + several times than it is to declare and initialize an array + of widgets to pass to <function +>XtUnmanageChildren()</function +>. Calling + <function +>XtUnmanageChildren()</function +> is more efficient, however, + because it only calls the parent's <function +>change_managed()</function> + method once. + </para> + </refsect1> + + <refsect1 id="r1-1007-unmanagechildren-3"> + <title +>Algorithm + </title> + <para +><function +>XtUnmanageChildren()</function +> performs the following: + </para> + <variablelist> + <varlistentry> + <term +>- + </term> + <listitem> + <para +>Ignores the child if it already is unmanaged or is being + destroyed. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term +>- + </term> + <listitem> + <para +>Otherwise, if the child is realized, it makes it nonvisible + by unmapping it. + </para> + </listitem> + </varlistentry> + </variablelist> + + </refsect1> + + <refsect1 id="r1-1007-unmanagechildren-4"> + <title +>Structures</title> + <para> + The <type +>WidgetList</type +> type is simply an array of widgets: + </para> + <screen id="sc-1007-unmanagechildren-1" +> + typedef Widget *WidgetList; + </screen> + </refsect1> + </refentry> + --> + </chapter> + + + <chapter id="credits"> + + <title +>Créditos y Licencia</title> + + <para> + <application +>Rosegarden</application> + </para> + <para> + <itemizedlist> + <listitem> + <para +>Rosegarden-4 es Copyright 2000-2004 Guillaume Laurent, Chris Cannam y Richard Bown. Los derechos morales de Guillaume Laurent, Chris Cannam y Richard Bown serán identificados ??? </para> + </listitem> + + <listitem> + <para +>Partes de Rosegarden-4 son derivadas de Rosegarden 2.1, que es Copyright 1994 – 2001 Chris Cannam, Andrew Green, Richard Bown y Guillaume Laurent. </para> + </listitem> + + <listitem> + <para +>Para reproducir notación musical, Rosegarden utiliza mapas de pixels derivados del tipo de letra Feta, parte del software <ulink url="http://lilypond.org/" +>Lilypond</ulink +>, que es Copyright 1997 – 2001 Jan Nieuwenhuizen y Han-Wen Nienhuys. </para> + </listitem> + + <listitem> + <para +>Otros colaboradores importantes son Randall Farmer, Ron Kuris, Hans Kieserman y Michael McIntyre. </para> + </listitem> + + <listitem> + <para +>La imagen de bienvenida de Rosegarden es de una postal del 1900 de Thornden Park en la Universidad de Syracuse, Syracuse, NY, usada con permiso del personal de la universidad. </para> + </listitem> + + </itemizedlist> + </para> + + <para +>Documentación: copyright 2002-2004 Chris Cannam, Richard Bown, Guillaume Laurent </para> + <!-- + <para> + Translations done by: + <itemizedlist> + <listitem> + <para +>Babel D. Fish <email +>babelfish@kde.org</email +> (Sanskrit)</para> + </listitem> + </itemizedlist> + </para> + --> + <!-- For URL links to common stuff like the one below, + always use paths like "common/gpl-licence". + In this path, "common" will be a symbolic link built at "make install" time. + This link will normally point to $KDEDIR/share/doc/HTML/en/common, + where "en" should be replaced with the current language. --> + + <para +>Este programa esta licenciado bajo los términos de la <ulink url="common/gpl-license.html" +>GNU General Public License</ulink +>. </para> + </chapter> + + <!-- Note that the revhistory tags apply to the documentation + version and not to the app version. That is why we use an + ItemizedList instead for this list of revisions to the app. --> + + <chapter id="rosegarden-revhistory"> + <title +>Historial de revisiones de Rosegarden-4</title> + <para> + <itemizedlist> + <listitem +><para +>0.9.9 – Julio 2004: mejoras en extensiones de síntesis, segmentos ??? y notación </para +></listitem> + <listitem +><para +>0.9.8 – Mayo 2004: mejor subsistema de audio </para +></listitem> + <listitem +><para +>0.9.7 – Febrero 2004: </para +></listitem> + <listitem +><para +>0.9.6 – Diciembre 2003: correcciones </para +></listitem> + <listitem +><para +>0.9.5 – Noviembre 2003: muchas mejoras </para +></listitem> + <listitem +><para +>0.9.1 – Mayo 2003: grabación por pasos, exportación Mup, numerosas correcciones </para +></listitem> + <listitem +><para +>0.9 – Abril 2003: numerosas mejoras en la notación, editor de bancos mejorado, mejoras de audio, traducciones </para +></listitem> + <listitem +><para +>0.8.5 – Diciembre 2002: editor de bancos, filtros MIDI, boton panic </para +></listitem> + <listitem +><para +>0.8 – Octubre 2002: impresión, extensiones LADSPA, vista de matriz mejorada </para +></listitem> + <listitem +><para +>0.2.0 – Agosto 2002: soporte para archivos WAV, selecciones de barrido, ??? </para +></listitem> + <listitem +><para +>0.1.6 – Junio 2002: cuadro de dialogo de configuración, soporte Lilypond, cuadro de dialogo Cuantificar </para +></listitem> + <listitem +><para +>0.1.5 – Mayo 2002: KDE 3, soporte ALSA, soporte para JACK </para +></listitem> + <listitem +><para +>0.1.4 – Marzo 2002: Deshacer mejorado, edición de segmentos, reproducción de audio </para +></listitem> + <listitem +><para +>0.1.3 – Enero 2002: vista piano-roll/matriz, grabación &MIDI; </para +></listitem> + <listitem +><para +>0.1.2 – Noviembre 2001: Deshacer notación, cuadro de dialogo transporte, puntero de posición </para +></listitem> + <listitem +><para +>0.1.1 – Octubre 2001: notación escalable </para +></listitem> + <listitem +><para +>0.1 – Junio 2001: primera versión de Rosegarden-4 </para +></listitem> + </itemizedlist> + </para> + </chapter> + + &documentation.index; +</book> diff --git a/doc/ja/CMakeLists.txt b/doc/ja/CMakeLists.txt new file mode 100644 index 0000000..eb6d853 --- /dev/null +++ b/doc/ja/CMakeLists.txt @@ -0,0 +1,12 @@ +################################################# +# +# (C) 2011 Timothy Pearson +# kb9vqf (AT) pearsoncomputing.net +# +# Improvements and feedback are welcome +# +# This file is released under GPL >= 2 +# +################################################# + +tde_create_handbook( DESTINATION rosegarden ) diff --git a/doc/ja/index.docbook b/doc/ja/index.docbook new file mode 100644 index 0000000..a1c09bf --- /dev/null +++ b/doc/ja/index.docbook @@ -0,0 +1,5376 @@ +<?xml version="1.0" ?> +<!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.1.2-Based Variant V1.0//EN" "dtd/kdex.dtd" [ + <!ENTITY rosegarden "<application>Rosegarden</application>"> + <!ENTITY MIDI "<acronym>MIDI</acronym>"> + <!ENTITY % English "INCLUDE" > <!-- change language only here --> + <!ENTITY % addindex "IGNORE"> +]> + +<!-- The language must be changed in the <book> tag for translations. --> + + +<!-- + + Notes on style and terminology for Rosegarden handbook + ====================================================== + + * Aim to be clear, brief and direct, but be informal. + + * Write instructions in the second person. + + Good: "You can select segments by clicking on + them with the arrow tool." + + Bad: "Segments can be selected by clicking on + them with the arrow tool." + + Very bad: "The arrow tool allows the user to select + segments by clicking on them." + + If you dislike the first of these because you want to + make the phrase "the arrow tool" more obvious by placing + it at the start of the sentence, then perhaps you + should be using a variablelist instead and making + "the arrow tool" a list item. + + * It's perfectly permissible to detour to explain why + something is the way it is, particularly if it might + not be obvious. + + * It's also entirely permissible to omit advanced stuff + from the "Using Rosegarden" section and document it + only in the reference section. "Using Rosegarden" + should be about understanding how and why, not about + knowing every last clever detail. + + * Bear in mind we can link extensively from any part of + the handbook to any other. Unfortunately DocBook won't + allow you to write a link to a target that doesn't + exist yet, so if you want to link to something that's + not yet been written, either make a note of the planned + link in an XML comment, or go and create a stub for the + bit that hasn't been written yet, or else just write in + a way that allows for a link to be easily added later + (we could do an editing phase specially for links). + + * Be strict about using the correct terminology for + Rosegarden data structures (segment, event, track, + instrument, composition), but don't capitalise the + words. Capitalisation is useful in technical documents + to make it clear that you're referring to a precise + concept, but you shouldn't have to do it to make your + meaning clear in user documentation. If something + seems ambiguous without, try rewording it instead. + +--> + + +<book id="rosegarden" lang="ja"> + + <!-- This header contains all of the meta-information for the document such + as Authors, publish date, the abstract, and Keywords --> + + <bookinfo> + <title>Rosegarden ハンドブック</title> + <authorgroup> + <author> + <firstname>Richard</firstname> + <surname>Bown</surname> + </author> + <author> + <firstname>Chris</firstname> + <surname>Cannam</surname> + </author> + <author> + <firstname>Guillaume</firstname> + <surname>Laurent</surname> + </author> + <!-- TRANS:ROLES_OF_TRANSLATORS --> + </authorgroup> + + <copyright> + <year>2002-2003</year> + <holder>Richard Bown, Chris Cannam, Guillaume Laurent</holder> + </copyright> + + <date>2003-11-26</date> + <releaseinfo>0.9.5</releaseinfo> + + <abstract> + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-mainwindow.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>&rosegarden;</phrase> + </textobject> + </mediaobject> + </screenshot> + + Rosegardenは音と &MIDI; シーケンサと楽譜エディタである。この + ハンドブックはどのようにこれを使うかを説明する。 + + </para> + </abstract> + + <keywordset> + <keyword>Rosegarden</keyword> + <keyword>sequencer</keyword> + <keyword>MIDI</keyword> + <keyword>audio</keyword> + <keyword>music</keyword> + <keyword>notation</keyword> + <keyword>score</keyword> + <keyword>KDE</keyword> + </keywordset> + + </bookinfo> + + <!-- The contents of the documentation begins here. Label each + chapter so with the id attribute. This is necessary for two reasons: + it allows you to easily reference the chapter from other chapters of + your document, and if there is no ID, the name of the generated HTML + files will vary from time to time making it hard to manage for + maintainers and for the CVS system. Any chapter labelled (OPTIONAL) + may be left out at the author's discretion. Other chapters should + not be left out in order to maintain a consistent documentation + style across all KDE apps. --> + + <chapter id="introduction"> + <title>概要</title> + + <para> + <application>Rosegarden</application> は&MIDI; と音シーケンサ + と楽譜エディタである。音楽の録音、編曲と作曲ができる。音楽は + 従来の楽譜か&MIDI; データ、あるいは指定した任意の音源かギターか + マイクからの入力で録音されたものか、一続きの音ファイルから + インポートされたもので表現される。 + sequencer and musical notation editor. It allows the user to + record, arrange and compose music. Music is represented either + by traditional score or &MIDI; data, or by sets of audio files + either imported or recorded from a microphone, guitar or + whatever audio source you care to specify. Music data can be + edited to create a composition, effects can be applied and the + resulting mix can be burnt to CD or turned into MP3/ogg format + suitable for distribution on the web. Professional notation + editing support also provides high quality printed output of the + composition. + </para> + + <para> + <application>Rosegarden</application> is designed to look and + act in a manner familiar to experienced users coming to Linux + from other platforms whilst also being accessible and friendly + to users new to music software generally. + </para> + + <para> + このハンドブックは参考資料と基本概念の簡単な概要と、&rosegarden; の + 使用法を含んでいる。これは + <ulink url="http://rosegarden.sourceforge.net/tutorial/"> ここに + 置いてあるチュートリアル</ulink> ではない。 もしも何か理解できないか、 + さらに助言が必要であれば、 + <ulink url="http://www.all-day-breakfast.com/rosegarden/"> + Rosegarden webサイト</ulink> にFAQ とメーリングリストがあるので + 見てほしい。 + </para> + + <!-- Note that the revhistory tags apply to the documentation + version and not to the app version. That is why we use an + ItemizedList here. --> + + <sect1 id="rosegarden-revhistory"> + <title>変更記録</title> + <para> + <itemizedlist> + <listitem><para> + 0.9.5 – November 2003: a great many stuff + </para></listitem> + <listitem><para> + 0.9.1 – May 2003: step recording, Mup export, many many bug fixes + </para></listitem> + <listitem><para> + 0.9 – April 2003: many notation improvements, improved bank editor, audio enhancements and refinements, translations + </para></listitem> + <listitem><para> + 0.8.5 – December 2002: bank editor, MIDI filters, panic button + </para></listitem> + <listitem><para> + 0.8 – October 2002: printing, LADSPA plugins, improved Matrix View + </para></listitem> + <listitem><para> + 0.2.0 – August 2002: WAV file support, sweep selections, contrapuntal staves + </para></listitem> + <listitem><para> + 0.1.6 – June 2002: configuration dialog, Lilypond support, quantize dialog + </para></listitem> + <listitem><para> + 0.1.5 – May 2002: KDE 3, ALSA support, JACK audio support + </para></listitem> + <listitem><para> + 0.1.4 – March 2002: more undo, segment editing, audio playback + </para></listitem> + <listitem><para> + 0.1.3 – January 2002: piano-roll/matrix view, &MIDI; recording + </para></listitem> + <listitem><para> + 0.1.2 – November 2001: notation undo, transport dialog, position pointer + </para></listitem> + <listitem><para> + 0.1.1 – October 2001: scalable notation + </para></listitem> + <listitem><para> + 0.1 – June 2001: first public release of Rosegarden4 + </para></listitem> + </itemizedlist> + </para> + </sect1> + </chapter> + + +<!-- + ********************************** + + PART I: + Discussion and tutorial material + + ********************************** + --> + + + <chapter id="using-rosegarden"> + <title>Rosegardenの使用法</title> + + <!-- This chapter should tell the user how to use your app. You + should use as many sections (Chapter, Sect1, Sect3, etc...) as is + necessary to fully document your application. --> + + <!-- Note that all graphics should be in .png format. Use no + gifs because of patent issues. --> + + + <sect1 id="file-operations"> + <title>ファイルとドキュメントの基礎</title> + <para> + &rosegarden; は各々の楽曲情報を固有のドキュメントに、固有の内部 + 形式で格納する。ドキュメントをセーブするとき、ディスク上に、 + .rg 拡張子を付けたファイルとして格納される。&rosegarden; は、 + いくつかの、その他のファイル形式も扱うことができる。 + </para> + + <sect2 id="file-creating"> + <title>新しい楽曲情報</title> + <para> + &rosegarden; の起動時には、編集を行なうための、"空白の"楽曲情報 + を含む新しいドキュメントが開かれる。その楽曲情報になんらかのもの + を配置するために、何らかを録音するか、色々な編集機能を使って埋める + ことができる、長さ0(空白)の音楽("セグメント"として参照される)を + 作成しなければならない。 + </para> + <para>音楽の録音についての詳細の記述がある + <!-- link linkend="recording" -->録音<!-- /link + --> と、どのように音楽のセグメントを作成、編集、編集するか + が記載されている<link + linkend="segment-view">トラックエディタ</link> セクションを + 参照のこと。 + </para> + </sect2> + + <sect2 id="file-midi"> + <title>MIDIファイルの使用法</title> + <para> + MIDIファイルをインポート/エクスポートするためには、 + ファイルメニューのインポートとエクスポートサブメニュー + 中にある + "MIDIファイルのインポート"と"MIDIファイルのエクスポート" + を使用する。 + </para> + <para> + &rosegarden; がMIDIファイルのようなファイル形式をロード/セーブ + できるにもかかわらず、内部的にはMIDIデータを格納しない。 + 一般的には、&rosegarden; が、MIDIにエクスポートするときに + 失われる大量の情報を格納する &rosegarden; 固有の形式でセーブ + することを選択しなければならない。 + </para> + <para> + MIDIファイルがロードされると、&rosegarden;は音楽データを + MIDI1トラックごとに1つのトラックに分割するか、ファイルに送り + 込み、 + <link linkend="studio-midi-import">は適切な楽器のマッピングを + 行ない</link>、 <link + linkend="nv-quantization">MIDIパフォーマンスデータのために + もっともな楽譜</link>を計算することを試みる。 + </para> + </sect2> + + <sect2 id="file-merge"> + <title>ファイルのマージ</title> + <para> + ファイルをロード/インポートするだけではなく、現在のドキュメント + 中にそれらをマージすることも、すでにそこにあるファイル中にある + セグメントを追加することもできる。 + </para> + + <para> + ファイルをマージするために、オープン又はインポートオプションを + 使う代わりに、ファイルメニュー中のマージサブメニュー上の適切な + オプションを使う。 + </para> + </sect2> + + <sect2 id="file-printing"> + <title>印刷</title> + <para> + ファイルメニュー中の"印刷"機能を使うことで、 + 楽譜として楽曲情報を印刷することができる。 + </para> + + <para> + 楽譜を演奏データから作成することは大変な作業なので、 + ほとんどの場合、MIDIデータに基づく既定値の印刷結果がとても読み + やすいことを期待するのは無謀である。印刷する前に、楽譜を + <link linkend="notation-view">楽譜エディタ</link> + を使って整形すべきである。 + (<link linkend="nv-quantization">演奏データからの作譜</link> + も参照のこと。) + </para> + + <para> + 注意深く扱うことによって、 &rosegarden;はとても読みやすい楽譜を + 作成する能力がある。たとえそうでも、スクリーンエディタとして + デザインされたのであって、写植機ではない。本当に印刷品質の + 楽譜を作成したいのであれば、&rosegarden; と結合できる + <ulink url="http://www.lilypond.org">Lilypond</ulink> + を考慮すべきである。 Lilypond は楽譜の写植を行なうソフトウェアで、 + 特別なテキストファイル形式を読み込み、高品質の活字化された + 楽譜を生成する。 + &rosegarden; はファイルメニュー中のエクスポートサブメニュー上の + "Lilypondにエクスポート"を使うことでLilypondファイルを書き出す + ことができる。 + </para> + </sect2> + + </sect1> + + <sect1 id="segment-view"> + <title>トラックエディタ</title> + <sect2 id="segment-view-overview"> + <title>概要</title> + <para> + &rosegarden; のメインレイアウトは、その他の一般的なシーケンサ + とよく似たコンセプトである。これは、— のトラック + コンセプトを基礎としていて、メインウィンドウはトラックの + 一覧を表示しているトラックエディタを表示し、そのトラックは、 + 左側の下の楽器に関連付けられている。 + (<link + linkend="notation-view">notation</link>、 <link + linkend="matrix-view">matrix</link>、と <link + linkend="event-view">event list</link>)という特化した + エディタ中でセグメントそれ自身をオープンするのと同じように、 + トラックエディタ上で(“セグメント”として参照 + される)音楽データのブロックを移動したり操作することができる。 + </para> + + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-trackeditor.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>&rosegarden;'s Track Editor showing two segments of music data</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + + <para> + トラックは、&MIDI;のレンジや、オーディオ楽器(audio instruments) + に割り当てることができる。上記の絵の中では、トラックエディタ上で + 2つのセグメント(黄色がかった緑のブロックの部分)が表示されていて、 + それは"IIWU Synth"という楽器に割り当てられている。 + </para> + </sect2> + <sect2 id="segment-view-instruments"> + <title>トラックと楽器</title> + <para> + 各々のトラックは、音を鳴らすために、それに割り当てられている + 楽器を持たなければならない。1つの楽器をトラックに割り当てるために、 + トラックラベル上で左マウスボタンをクリックしホールドする。 + するとポップアップメニューが表示され、その中に有効な楽器の + 一覧が表示される。 + </para> + <para> + 楽器というものは、&MIDI;デバイス上の1つのチャネル、あるいは + 1つのオーディオ出力として理解することができる。トラックには + &MIDI; 楽器に割り当てられなければならない音符データを含み、 + それらは、音から音へのinstrumentを含んでいる。1つ以上のトラックに + 同じ楽器を割り当てることができ、その場合、複数のトラックは + 同じ音を使う。 + </para> + <para> + <link + linkend="segment-view-instrumentparameterbox">楽器パラメータ + ボックス</link> を使うことで、トラックに割り当てられた色々な + プロパティを変更することができる。ここは、たとえば、特定の + パッチを使って特定の音(ピアノ、ストリング、その他)を出すために + MIDI楽器を設定するところである。 + </para> + <para> + 楽器についての詳細がある + <link linkend="studio-introduction">Studio</link> セクションを + 参照のこと。 </para> + </sect2> + + <sect2 id="segment-view-creating"> + <title>セグメントの作成</title> + <para> + 何らかの作曲を開始するために、1つの空白のセグメントを作成するために、 + 鉛筆ツールを使う必要がある。ツールバーの鉛筆をクリックし、 + セグメントを開始したい場所でまたクリックし、 + (at the correct height for the + track you want the segment to be on, and at a distance + across the editor window corresponding to the correct time) + セグメントが正しい長さのバーになるまで右にドラッグする。 + </para> + + <para> + 既定値では、新しいセグメントはバーライン上で開始し、バー単位で + 拡張するが、これは、クリックとドラッグ中シフトキーを押すことに + よってグリッドに張り付く効果を抑止できる。 + </para> + + <para> + 一度セグメントを作成すると、 + <link linkend="matrix-view">マトリクス</link> 又は <link + linkend="notation-view">notation</link>エディタを使って編集を + 開始できる。それらのエディタを使うためには、セグメントをダブル + クリックするか、右マウスボタンをクリックし、コンテキストメニュー で使いたいエディタを選択する。 + </para> + + <para> + MIDIデバイスかオーディオ入力からの録音を考えているならば、 + 最初に新しいセグメントを作成する必要はない -- それぞれの分離 + された録音は、録音中に自動的に作成される常に新しいセグメント + 中に入る。 + </para> + </sect2> + + <sect2 id="segment-view-manipulating"> + <title>セグメントの操作</title> + <para> + メインウィンドウはセグメントを編集するための"ツール"の集まり + が用意されている。それらはメインツールバーで有効になっている。 + 最初にツールバーから使いたいツールを選択し、メインキャンバス上の + セグメント上にクリックとドラッグを行なう。 + </para> + + <sect3 id="segment-view-selector"> + <title>選択ツール</title> + <para> + "選択ツール"(矢印ツール)は実際には他目的のツールである: + それは選択、移動、コピー、リサイズとセグメントの作成に + 使える。</para> + + <para> + 最も明白な使用方法は"選択"である:これは、選択ツールで、 + セグメントを、 + セグメント上でクリックすることで1つを選択するか、 + シフトキーを押したままでクリックしていくつかを選択するか、 + ウィンドウの空白の領域中でクリックして領域外にドラッグする。 + </para> + + <para> + 選択ツールでセグメントを移動するためには、単にクリックし、 + セグメントをドラッグする。コピーを作成するためには、クリックし、 + セグメントの右端をドラッグする。新しいセグメントを作成するため + には、中マウスボタンで空白の領域をクリックしてドラッグする。 + </para> + + <para> + 選択ツールは、時々、—が + 特に小さなセグメント上で、意図している動作により明確にする必要がある + にもかかわらず、 + その他のツールを完全に置き換えるものではない。 + </para> + + </sect3> + + <sect3 id="segment-view-move-resize"> + <title>移動とリサイズツール</title> + <para> + セグメントを別の開始時間又はトラックに移動するためには、 + 移動ツールを使い、移動したい場所に、セグメント上でクリックし + ドラッグする。もしも、Ctrlキーを押したまま移動するならば、 + セグメントは移動でなはくてコピーされる。 + </para> + + <para> + セグメントのリサイズをしたいならば、リサイズツールを使い、 + セグメントの右端をクリックし、ドラッグする。</para> + + <para> + 移動とリサイズの両方のために、特定のグリッド位置に張り付くのを + 防ぐため、シフトキーを押すことができる。 + </para> + + </sect3> + + <sect3 id="segment-view-split-join"> + <title>分割ツール</title> + <para> + + <inlinemediaobject> + <imageobject> + <imagedata fileref="rg-split.png"/> + </imageobject> + </inlinemediaobject> + を、1つのセグメントを2つの分離されたセグメントにするために + 分割ツールを使うことができる。セグメントを分割するために、 + 分割ツールを選択し、分割したい点でクリックする。 + </para> + <para> + 既定値では、セグメントは、カーソルに関係した最も近いバーラインに + 分割されるが、これはセグメントを分割している間シフトキーを押すこと + で抑制できる。 + </para> + </sect3> + </sect2> + + <sect2 id="segment-view-segmentparameterbox"> + <title>セグメントパラメータボックス</title> + + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-segmentparameterbox.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>&rosegarden;'s segment parameter box</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + + <para> + セグメントパラメータボックスは、選択されたセグメントのいくつかの + 外見を変更することができる。もしも1つのセグメントが現在選択され + ているのならば、そのパラメータはセグメントパラメータボックス中 + で表示され、そこで編集できる。もしも複数のセグメントが選択されて + いるのならば、パラメータボックスは選択されたセグメントすべてで + 現在共通な値のみが表示されるが、それらは変更でき、それはすべての + 選択されたセグメントに反映される。 + + <variablelist> + <varlistentry> + <term>ラベル</term> + <listitem> + <para> + 選択されたセグメント(もしも同じラベルを持っているならば、 + 複数のセグメント)のラベルを表示する。"..."ボタンをクリック + してラベルの編集ができる</para> + </listitem> + </varlistentry> + + <varlistentry> + <term>繰り返し</term> + <listitem> + <para> + 選択されたセグメントの繰り返しのon/offを切り替える。繰り返しを + 指定されたセグメントは、同じトラック上の継続するセグメントの + 開始点まで繰り返すか、継続するセグメントがない場合、楽曲の + 最後まで繰り返す。 + </para> + + <para> + 繰り返しているセグメントの繰り返している部分は、オリジナルの + セグメントに比べて、メインキャンバス上で淡い色で表示される。 + セグメントメニュー上で"Turn Repeats into Copies"オプションを + 使うか、単に単一の繰り返しブロック上でダブルクリックを行なう + ことによって、オリジナルのセグメントを真に編集可能なコピーに + 変更することができる。 + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>Quantize</term> + <listitem> + <para> + 選択されたセグメントのquantizationを表示する。 + すべてのそれらの音符の開始時間を簡単にquantize + するために、これを変更することができる。 + より詳細なquantizationはセグメントメニュー上の + Quantize機能を使う。 <link + linkend="quantization">Quantization</link> + に詳細がある。 + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>Transpose</term> + <listitem> + <para> + 選択されたセグメントに現在適用されているtransposition(in semitones) + を表示する。このtranspositionはセグメントが演奏されるときに適用され、 + マトリクス、notationまたはイベントリストエディタ内で表示される音符 + では見えない。楽曲全部または一部分のピッチを簡単に変更するために、 + これを使うことができる。</para> + </listitem> + </varlistentry> + + <varlistentry> + <term>ディレイ</term> + <listitem> + <para> + 選択されたセグメント上で現在効力のあるディレイを表示する。 + 演奏するために、後で書くより、セグメント全体にさせるために、 + ここでディレイを設定することができる。このディレイはセグメントが + 演奏されるときに適用されるが、マトリクス、notationまたはイベント + リストエディタ内で表示される音符では見えない。 + </para> + <para> + You can set a delay either in musical time (by + choosing a note duration from the delay dropdown), + in which time the exact delay will depend on the + tempo, or in real time (by choosing a time in + milliseconds from the dropdown). + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>色</term> + <listitem> + <para> + 選択されたセグメントが表示されるときに使われる色を表示する。 + ドロップダウン機能を使うか、ドロップダウンで見付からない場合、 + "新しい色を追加"オプションを選択することでその他の色を選択できる。 + </para> + <para> + 編集メニュー上の"ドキュメントプロパティの編集" + (ドキュメントプロパティダイアログの色ページを選択) + を使うことによって色の管理と名前の変更もできる。 + 変更された色のパレットはRosegardenファイル中の楽曲 + データと共にセーブされる。 + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-colours.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>&rosegarden;の色マネージャ</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + </listitem> + </varlistentry> + + </variablelist> + </para> + </sect2> + + <sect2 id="segment-view-instrumentparameterbox"> + <title>楽器パラメータボックス</title> + <para> + </para> + </sect2> + </sect1> + + <sect1 id="transport"> + <title>The Transport</title> + <para> + トラックエディタは、割り当てられた楽器にたいして配置される一連の + セグメントを表示する。楽曲を演奏するとき、&rosegarden; はそれが + クロスしているセグメントの内容を演奏するときに左から右へとトラック + 上でポインタを横切る。画面上でのポインタの位置は、Transportと + 呼ばれるダイアログによってtrackされ制御される。 + </para> + + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-transport.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>&rosegarden;'s Transport dialog</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + + <para> + もしもTransportが見えないならば設定メニューに行くことで + 有効にできる。 + (<menuchoice> <guimenu lang="ja">設定</guimenu> + <guimenuitem>Transportの表示</guimenuitem> </menuchoice>). + </para> + + <para> + Transportは最初のバー(秒単位)または、24-fps<acronym>SMPTE + </acronym>中の時間又は代わりにバーとビートからの絶対時間の + ポインタの現在位置を表示する。それは、希望するならば、 + 楽曲の最後からの時間も表示できる。それらの機能はメインの + transport表示の左にある小さなボタンによって制御できる。 + </para> + + <para> + transport上のメインコントロールはシーケンサの演奏を起動、一時停止、 + ポインタの位置の早送り、巻き戻し、停止または楽曲の最初/最後への + 移動を行なう。 + </para> + + <para> + 追加のコントロールと &MIDI; イベントはtransport上の下部にある + 矢印ボタンの左に隣接しているものでon/offすることができる。 + さらに、この特別な部分は録音、ループ、ソロとメトロノームの実行 + ボタンがある。 + </para> + + </sect1> + + <sect1 id="studio"> + <title>スタジオ</title> + + <sect2 id="studio-introduction"> + <title>デバイス、楽器と接続</title> + + <para> + Rosegardenは"スタジオ"という単語をコンピュータに繋がれる + サウンドシステムについて知っているモのすべてを参照するために + 使う。これは、&MIDI; とオーディオ用のハードウェアとその他の + サウンドソフトウェアを含んでもよく、さらに、接続状態の情報と + 構成(configuration)と&MIDI; パッチやその他を含んでもよい。 + </para> + + <para> + 用語の3つの部分はここで重要である: + + <variablelist> + + <varlistentry> + <term>デバイス</term> + <listitem> + <para> + <quote>デバイス</quote>はRosegardenの範囲において + 関係するものは、単に音を生成する能力がある何かである。 + これはMIDIシンセサイザーやオーディオデバイスでもよい。 + MIDIデバイスは物理的なMIDIポートに直接対応する必要は + ない:それらは参照することができ、特定の手段で動作する + ことを期待する、名前を持つ何らかのものである。MIDIパッチ + マップのような構成情報は、デバイスに割り当てることができる。 + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>楽器</term> + <listitem> + <para> + 各々のデバイスはいくつかの<quote>楽器</quote>をもち、 + それらの各々は、特定の音を作るために仮定される。それらは + 音を演奏するために選択されたトラックに割り当てることができる + ものである。既定値ではデバイスは起動時に生成される16の + 楽器を持つ:もしも、デバイスがMIDIデバイスであれば、16の + MIDIチャネルのうちの1つに初期化される。楽器はたとえば、 + プログラムの設定、リバーブ(reverb)、ボイスなどのような + 特定のボイスのすべてのプロパティである。 + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>接続</term> + <listitem> + <para> + MIDIデバイスが単に名前で、構成情報の集合の間は<quote> + 接続</quote>はどのMIDIポートに物理的に割り当てられている + かを指定する。これは、MIDIデバイス管理ダイアログ中で構成 + することができる(オーディオデバイスは同じ方法では接続を + もたない)。 + </para> + </listitem> + </varlistentry> + </variablelist> + </para> + + <para> + 例をあげると、セットアップが、2つの物理MIDIポートを持つPC + によって成り立っていて、その1つは外部のシンセサイザー + が接続されていることを想像する。ここでは1台のシンセサイザーに + 対応するMIDIデバイスを持つために、通常Resegardenを構成する。 + 次に、このデバイスについて、名前を修正し、マップをパッチする + ように構成することができ、次にサウンドカードの関連するMIDI + ポートにそれを結合するために接続を指定する。それぞれの16個の + デバイス上の既定値の楽器は適切なプログラムとともに構成でき、 + それらをトラックに割り当てられる。</para> + + <para> + 実際の所、Rosegardenは既定値で、起動時に有効な接続をおのおのの + デバイスに対して作成するだろう。そのため、上記の例では、 + 2つのMIDIデバイスは1つのみが必要だったとしても既定値で2つの + デバイスが作成されるだろう。一般的に、最初のものに対して + 名前を変え、パッチマップを適用し、2つめのものに対しては、 + 削除するか未使用にする。コンピュータ上のMIDIポートに実際に + どのシンセサイザーが接続されているかをRosegardenが知るすべは + ないことを記憶しておくこと。この理由により、起動時に作成され + るデバイスは、既定値のセットになる予定であり、構成するデバイスが + 本当に使うものに一致しているかどうかはあなた次第である。 + </para> + + <para> + 一度構成されると、スタジオのセットアップはセーブするRosegarden + 形式のファイルに毎回保存される。 + </para> + + </sect2> + <sect2 id="studio-midi-import"> + <title>&MIDI; インポート上のスタジオのマッピング</title> + <para> + 楽曲情報に &MIDI;ファイルをインポートするとき、&rosegarden; は + &rosegarden; の楽器上に &MIDI; プログラムをどのようにマップするかを + 決めるために、存在するスタジオのセットアップを使用する。 + 目的は、スタジオ中に実際に存在するマップされた1つの楽器を、 + すべての &MIDI; プログラムが得ることを確実にすることであり、 + (そして、そういう理由で、実際にコンピュータに割り当てられる) + そのため、すべての &MIDI;トラックは聞くことができる。 + + </para><para> + + インポートされたファイル中に見付かった、&MIDI; プログラム + チェンジとバンクセレクトイベントはインポートのときに使用されるが、 + スタジオ中の1まとまりの楽器から各々の&MIDI;トラックのための + 適切な楽器を見つけるのを手助けする手段としてのみ使われる。そのため、 + 例をあげると、もしもスタジオが現在<acronym>GM</acronym>楽器(音源) + のみ含んでいるようにセットアップされていた場合で、 + <acronym>GS</acronym> プログラムチェンジをその上に含む&MIDI;ファイル + をインポートした場合、&rosegarden;は<acronym>GS</acronym>バンク + を<acronym>GM</acronym>にリマップする。なぜならば、ファイルを + インポートするときに知っているすべてだからである。オリジナルの + <acronym>GS</acronym> プログラムナンバーを憶えているわけではない。 + + </para><para> + + このことは、&MIDI; ファイルをインポートする前に、 + 実際に持っているデバイス向けに正しくスタジオを + 構成することを確実にしなければならない、ということを意味する。 + それ以外では、&MIDI;ファイル中のプログラムデータは失われるだ + ろう。 + + </para> + </sect2> + + <sect2 id="studio-device-editor"> + <title>MIDIデバイスの管理</title> + + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-devicemanager.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>The MIDI device manager</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + + <para> + MIDIデバイスマネージャダイアログは現在有効なMIDIデバイスと + どこに繋がっているかを表示する。このダイアログに到達する + ためには、スタジオメニューのMIDIデバイス管理機能を使う。 + </para> + + <para> + <link linkend="studio-introduction"> デバイス、楽器、と接続 + </link> 中で説明されているように、既定値では Rosegardenは + 起動時に、もっともらしいデバイスのセットを提供しようとする。 + しかし、既定値の構成では、通常は最適ではないかもしれないので、 + このダイアログはデバイスの名前を変更し、それらの接続を変更 + し、再生/録音方向の接続を修正する。 + </para> + + <para> + 各々のここでリストされた再生デバイスは、通信(talk to)するため + のMIDIトラックのためのターゲットを提供する。もしも、新しい + 再生デバイスを追加するならば、トラックに割り当てることができる + このデバイス上の16の新しい楽器を持つことができるだろう。 + もしも、そのデバイスに対する接続を割り当てるならば、 + トラックはその接続に割り当てられた任意のMIDIシンセサイザー + の適切なチャネル(楽器によって依存する)で再生するために + 割り当てられる。 + </para> + + <para> + ここでリストされた録音デバイスは、MIDIを録音することが + 可能なソースを意味する。それらの1つはこのダイアログ中でその + 時点で有効状態になっている。 + </para> + + </sect2> + + <sect2 id="studio-bank-editor"> + <title>MIDIデバイスのバンクとプログラムの管理</title> + + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-bankeditor.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>The MIDI bank and program editor</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + + <para> + おのおののMIDIデバイスは複数の楽器を含み、それらの楽器を + トラックに割り当てることができることを憶えておくこと。 + MIDI用語中では、おのおのの楽器はMIDIシンセサイザー上の + 1つのチャネルに対応する。使用する各々の楽器のシンセサイザー + 上の有効なボイス(サウンド)のどれかを選択することができるが、 + この理由により、すべての有効なボイスの名前をRosegardenが + 知っているようにする必要がある。 + </para> + + <para> + このダイアログはプログラムのバンク(ボイスの名前)をMIDIデバイス + に接続することを可能にし、それゆえ、 + <link + linkend="segment-view-instrumentparameterbox"> + 楽器パラメータボックス</link> + 中のそれらのボイスの1つを使うために、デバイス上の各々の楽器は + セットされる。 + </para> + + <para> + デバイスのプログラム名をセットアップするための通常の方法は、 + 単に提供されるデバイスファイル(".rgd")の1つからそれらを + インポートすることである。これを行なうために、ダイアログの + 左のリスト中のデバイスを選択し、リストの下のインポートボタン + をクリックし、シンセサイザーに対応する.rgdファイルを選択する。 + </para> + + <para> + もしも、シンセサイザー用に何らの.rgdファイルが有効になっていない + のであれば、新しいバンクを作るためにこのダイアログを使うことが + できる。これを行なうために、シンセサイザーのMIDI実装チャート中の + プログラムマップを見つけ、すべての名前を手入力で入力する必要が + ある。次にそれを他のRosegardenユーザのために.rgdファイルに + エクスポートする。もしもそれを共有したいのであれば、 + rosegarden-userメーリングリストにコンタクトしてほしい(これは + どのようにして、Rosegardenと共に存在するすべての.rgdファイルが + 含まれているかの理由である)。 + </para> + + <para> + もしも、ソフトウェアシンセサイザーかSountFont(.sf2)ファイルを + 使うサウンドカードを使っているならば、このダイアログ中に + .sf2ファイルから正しいプログラム名を単純に直接ロードすることが + できる。通常と同じようにインポートをも止められたら、.rgdファイル + の代わりに.sf2ファイルを選択する。 + </para> + + <sect3 id="studio-variations"> + <title>Variations</title> + + <para> + いくつかのMIDIデバイス(たとえばローランドからのもの)は、 + "variations"として知られているスキームを使うプログラム名 + を体系化している。それらのデバイスのために、一般的に + 基本的なプログラム名—を最初に選択することによって + プログラムを選択したい。そして、電子ピアノのようなプログラム + —上の1セットのvariationsを選択する。これは、一般的な + MIDIベースのシンセサイザーと対象的であり、それはバンク中に + それらのプログラムを組織化し、バンクを最初に選択することを + 期待し、次にそのバンクからプログラムを選択する。 + </para> + + <para> + Rosegarden はvariationを使うデバイスをサポートできるが、 + バンクフォーマット中にプログラム名を入力しなければならない。 + 内部的に、variationを使うデバイスはvariationsとの間で + 選択するために、MIDIバンク選択コントローラを使う。 + variationを選択するために、デバイスがLSBかMSBのどちらかの + バンクセレクトを使うかを、シンセサイザーのドキュメントから + 見つけ出す必要があり、どのバンク番号がどのvariationに + 対応しているかを見つけ出す必要がある。次に、通常として、 + バンクを入力し、バンクダイアログ上の、 + "MSB/LSB上のVariationリストの表示"オプションを使い、 + Rosegardenに楽器パラメータボックス内でそのデバイスが表示される + ときにバンクの代わりにvariationが表示するように伝える。 + </para> + </sect3> + + </sect2> + + <sect2 id="studio-metronome"> + <title>メトロノーム</title> + <para> + Rosegarden は内蔵の2ツのメトロノームを持っていて、その1つは + 録音中に使い、もう一つは通常の再生中にスイッチすることができる。 + それらはMIDI楽器にノートを送ることによって動作し、両方の + メトロノームは同じ楽器、ピッチとベロシティ情報を使う。 + </para> + + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-metronome.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>&rosegarden;'s metronome configuration dialog</phrase> + </textobject> + </mediaobject> + </screenshot> + + メトロノームを構成するためには、スタジオメニュー上の + "メトロノームの管理"オプションを使いメトロノームダイアログを + 起動する。そののち、メトロノームのためのMIDI楽器とメトロノーム + の解像度(1つのビートあたりのティック、ビートの再分割、 + あるいはビートあたり1つ)を選択できる。MIDIシンセサイザーの + 実際のボイスのようなプロパティは選択された楽器に依存する + メトロノームのティックのために使われ、トラックに割り当てられた + 楽器に依存するMIDIトラックのために使われるボイスのようである。 + メインウィンドウ上でそれにをラックを割り当てることで楽器を + 構成することができ、楽器パラメータボックスから正しいプログラム + を選択することができる。 + </para> + + <para> + メトロノームの録音と再生はTransportウィンドウでメトロノーム + ボタンによってonまたはoffすることができる。このボタンは + 録音が供給されているか、実行中の時にメトロノームの録音を制御し、 + 録音メトロノームはonにされ、再生メトロノームはoffにされる。 + </para> + </sect2> + + <sect2 id="studio-midi-filters"> + <title>MIDIフィルタ</title> + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-midifilter.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>The MIDI filter dialog</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + + <para> + このダイアログを使うことで、どのMIDIイベントをRosegardenが + MIDI THRUを使ってイベントを送るか、それを単に録音するかで + 受け付けたり無視したりすることを決められる。このダイアログ上の + チェックボックスを使うことで、RosegardenにどのタイプのMIDI + イベントを送るか録音するかを希望しないことを伝える。 + </para> + + </sect2> + + </sect1> + + <sect1 id="quantization"> + <title>Quantization</title> + <para> + "Quantization" は音符の再ポジショニングのプロセスとその他の + イベントであり、 so that they start or finish on exact beat divisions. + It is traditionally used to make an approximate performance + into a precise but rather mechanical-sounding one, either + because precision is the desired effect or for a result such + as making the notes clearer in notation. + </para> + + <para> + The quickest way to quantize something is to do it in the main + window, using the Quantize menu on the <link + linkend="segment-view-segmentparameterbox">Segment Parameter + Box</link>. If you select some segments and change the value + shown in the menu, the segments will immediately be quantized + so that all their notes start at multiples of the note + duration in the menu. + </para> + + <para> + + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-gridquantizer.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>&rosegarden;'s quantize dialog</phrase> + </textobject> + </mediaobject> + </screenshot> + For more control, use the Quantize function on the Segments + menu of the main window, or on the Transforms menu of the + matrix or notation editors. This shows you a dialog in which + you can select the precise quantization parameters you need, + and then it applies these to all of the selected segments or + notes. + </para> + + <para> + <!-- !!! to be continued --> + </para> + + </sect1> + + <sect1 id="matrix-view"> + <title>マトリクスエディタ</title> + <para> + &rosegarden;のマトリクスエディタは、クリヤで論理的な形式で + 音楽を表示し、編集することを可能にする。それぞれの音符は + グリッド中のブロックとして表わされ、高さはピッチに関連する。 + </para> + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-matrixview.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>&rosegarden;'s matrix editor</phrase> + </textobject> + </mediaobject> + </screenshot> + それぞれのマトリクスエディタウィンドウは1つのセグメントを表示する。 + セグメントを編集するために、メインキャンバス上で右クリックし、 + メニューからマトリクスエディタを選択する。代わりに、セグメントを + ダブルクリックするときにマトリクスエディタが既定値のエディタに + なるようにRosegardenを設定することも可能である。 + </para> + + <sect2 id="matrix-insertion"> + <title>音符の挿入</title> + <para> + マトリクスビューにノートを挿入する一番簡単な方法は、マウスを + 使うことである。これを行なうために、ツールバー上で鉛筆ツール + を選択し、マトリクスエディタ上にクリックしドラッグする。 + 音符と、そこでクリックした点に関連するピッチが入力され、 + マウスボタンをリリースする前に関連した距離に関連するduration + を持つだろう。 + </para> + + <para> + 既定値では、時間とdurationはツールバー又は表示メニュー上のグリッド + 設定に添った形で、特定のグリッドユニットに貼り付けられる。 + クリックとドラッグ中にシフトキーを押したままにすることでこの効果を + 抑止できる。 + </para> + + <sect3 id="matrix-insertion-keyboard"> + <title>PCキーボードからのノートのタイプ</title> + + <sect4> + <title>Duration</title> + + <para> + キーボードからのノートのdurations入力は、ツールバー又は + 表示メニュー上のグリッド設定によって制御される。これを + 以下の数字キーを使って設定することができる:</para> + + <itemizedlist> + <listitem><para><keycap>5</keycap> – Whole bar</para></listitem> + <listitem><para><keycap>1</keycap> – Beat</para></listitem> + <listitem><para><keycap>2</keycap> – Half note (minim)</para></listitem> + <listitem><para><keycap>4</keycap> – Quarter note (crotchet)</para></listitem> + <listitem><para><keycap>8</keycap> – Eighth note (quaver)</para></listitem> + <listitem><para><keycap>6</keycap> – Sixteenth note (semiquaver)</para></listitem> + <listitem><para><keycap>3</keycap> – Thirty-second note (demisemiquaver)</para></listitem> + <listitem><para><keycap>0</keycap> – Sixty-fourth note (hemidemisemiquaver)</para></listitem> + </itemizedlist> + + </sect4> + + <sect4> + <title>ピッチ</title> + + <para> + 一旦正確なdurationがグリッドメニュー中で選択されると、 + 以下のピッチキーの1つを押すことによって、 + <link linkend="nv-rulers">カーソルの挿入</link>による + 現在の位置にノートを挿入できる。 + </para> + + <itemizedlist> + <listitem><para><keycap>A</keycap> – ド (the tonic of the current key in the current clef)<!-- !!! FIXME: no clef in matrix view --></para></listitem> + <listitem><para><keycap>S</keycap> – レ</para></listitem> + <listitem><para><keycap>D</keycap> – ミ</para></listitem> + <listitem><para><keycap>F</keycap> – ファ</para></listitem> + <listitem><para><keycap>J</keycap> – ソ</para></listitem> + <listitem><para><keycap>K</keycap> – ラ</para></listitem> + <listitem><para><keycap>L</keycap> – シ</para></listitem> + </itemizedlist> + + <para>キーを押す間に<keycap>Shiftキー</keycap>を押すと、 + ノートが半音上がり、(シャープが定義されていないミとシは + 除く) <keycap>Shift</keycap>と<keycap>Ctrl</keycap>キーを + 一緒に押すと、半音下がる(ファとドを除く)</para> + + <para> + 1オクターブ上を入力する場合は、 + use the corresponding + keys on the next row up: <keycap>Q</keycap>, + <keycap>W</keycap>, <keycap>E</keycap>, <keycap>R</keycap>, + <keycap>U</keycap>, <keycap>I</keycap>, と + <keycap>O</keycap>を使う。 + 同様に、1オクターブ下を入力する場合には + <keycap>Z</keycap>, <keycap>X</keycap>, + <keycap>C</keycap>, <keycap>V</keycap>, <keycap>B</keycap>, + <keycap>N</keycap> と <keycap>M</keycap>を使う。</para> + + </sect4> + + <sect4> + <title>その他の注意すべき点</title> + + <para> + すべてのコマンドの挿入はツールメニューのサブメニュー上で + 有効である。たった1つのノートを挿入するためにメニューを + 辿っていくことはありそうもないが、メニューはキーボード + ショートカットを表示しているので、どのキーがどの機能に + 割り当てられているかを忘れた場合には役に立つリファレンスを + 提供する。</para> + + <para> + キーボードショートカットはQWERTYレイアウトキーボード用に + 現在デザインされている。その他のレイアウトにキーをリマップ + する方法はまだなく、設定メニュー上の"ショートカットの構成" + オプションを使うことによって各々のキーの再定義を個別に行なう??。 + short of reassigning each + key individually using the "Configure Shortcuts..." option + on the Settings menu.</para> + + </sect4> + + </sect3> + + <sect3 id="matrix-insertion-midi"> + <title>MIDIキーボードからのノートの入力</title> + + <para> + MIDIキーボード又はその他のMIDI制御デバイスを使うことで + マトリクスエディタ中にノートを入力することができる。 + マトリクスエディタはキーボード上で演奏したピッチを使うが、 + durationsはエディタそれ自身でのグリッドの設定中で選択したもの + You can enter notes into the matrix editor one at a time + using a MIDI keyboard or other MIDI control device. The + matrix editor uses the pitches you play on the keyboard, + but the durations you have selected in the Grid setting of + the editor itself. これは"ステップ録音"として知られている。 + </para> + + <para> + MIDIキーボードからノートを入力するために、最初に既定値の + MIDIデバイスにキーボードを構成することを確実にする必要が + ある。次に、ツールバー又は表示メニュー中で、このコントロールが、 + ノートのdurationとなる正しいグリッド設定を確実にする必要がある。 + Then make sure you have the right Grid + setting in the View menu or toolbar, as this controls the + note duration. + 次に、マトリクスエディタのツールバー上のステップ録音ボタンか + ツールメニューのステップ録音を選択する。MIDIキーボード上で + 押されたすべてのノート上のその点は、ウィンドウがクローズするか、 + 別のウィンドウが有効になるか、再度ステップ録音がoffにされるまで + そのウィンドウ中に現在の挿入時間で挿入される。 + </para> + + <para> + 異なったdurationのノートを挿入するために、ステップ録音実行 + 中の間グリッド設定を変更することができる。 + </para> + </sect3> + </sect2> + + <sect2 id="matrix-selection"> + <title>ノートの選択</title> <para> + マトリクスエディタ中でノートを選択するために、選択(矢印)ツール + にスイッチし、次に、選択したいノートを含む四角の領域を囲む。 + 選択されたイベントは青でハイライトされる。もしも1つのイベント + 上で代わりにクリックすると、そのイベントのみが選択される。 + </para><para> + もしも、<keycap>シフト</keycap>キーを、ノートをクリックするか、 + 四角で囲む間押しているならば、新しい選択が、置き代わる代わりに + 存在する任意の選択に追加される。 + </para> + + <para> + 選択を解除したい場合には、マトリクスエディタの空白の場所で + クリックするか、エスケープキーを押す。</para> + + <para> + マトリクスエディタの左端のピアノキーボードの下中でキー上で + シフトしながらクリックすることによって与えられたピッチの + ノートをすべて選択することができる。ピッチの範囲を選択する + ために、シフトキーをOSIながらドラッグすることもできる。この選択 + は、今まで選択したものに追加されるので、新しく選択したい場合には + 古いものを先に消す。 + </para> + </sect2> + + <sect2 id="matrix-editing"> + <title>音符の移動とコピー</title> + <para> + 移動ツールと共にクリックしてドラッグするか、選択の後 + 選択ツールと共にドラッグするかをマトリクスエディタで + 行なうことによって時間とピッチの両方中でノートを移動 + することができる。 + </para> + <para> + ノートをコピーするためには、まず選択し、標準のコピーと + 貼り付け機能を使う。貼り付け後、張り付けられた音符は + 代わりに選択され、必要なところにどこにもドラッグすることが + できる。 + </para> + </sect2> + + <sect2 id="matrix-view-options"> + <title>マトリクス表示の設定</title> + <para> + <!-- zoom, rulers etc --> + </para> + </sect2> + </sect1> + + <sect1 id="notation-view"> + <title>Notationエディタ</title> + + <!-- Introduction, purpose --> + + <sect2 id="nv-introduction"> + <title>概要</title> + + <para> + + &rosegarden;のnotationエディタは、伝統的なスコア記法中で + 1つまたはそれ以上のstaffを表示、編集することを可能にする。 + + </para><para> + + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-notationview.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>&rosegarden;'s notation editor</phrase> + </textobject> + </mediaobject> + </screenshot> + &rosegarden; はシーケンサアプリケーションとして、その主要な + 焦点と互換性を持つ、最高のレイアウトを提供しようとする。 + This means that although the editor supports + chords, overlapping and nested beamed groups, triplets and + arbitrary tuplets, grace notes, dynamics, accents, text and + so on, it does not provide as much fine control over layout + (especially in contrapuntal music) as a dedicated score + editing program might. + + 写植によい形式である、 + <link linkend="commands-main-file-export-lilypond"> + Lilypondファイル</link> を書くことができるのにもかかわらず、 + 写植品質の楽譜を&rosegarden;は生成することを目的としない。 + + </para> + </sect2> + + <!-- Single and multiple staffs, and "current staff" --> + + <sect2 id="nv-staffs"> + <title>1つまたは複数のstaff</title> + + <para> + &rosegarden;メインウィンドウからnotationエディタを開く + 3つの方法がある(それらはすべて、メインウィンドウに + いくつかのセグメントが存在することを最初に要求し、 + そのため、もしも、新しい楽曲構成を始めるならば、 + それを編集することを考え始める前に、セグメントを + 作成する必要がある)。 + + <variablelist> + + <varlistentry> + <term>セグメント上でのダブルクリック</term> + <listitem> + + <para> + 最も明らかな手段は、メインキャンバス中でセグメントを + ダブルクリックする方法である。これは既定のエディタ + (notation、マトリクスまたはイベントリスト)として + 構成されているもので、どこででもセグメントを + オープンし、既定値でこれはnotationエディタである。 + そのため、Notationエディタウィンドウ中で1つの + staffとして、1つのセグメントをダブルクリックする + と開く。</para> + + <para> + この方法で複数のstaffをオープンすることもできる。 + シフトキーを押しながら、オープンしたい複数のセグメントの + 各々を、メイン表示上で選択(1つのマウスクリック)するが、 + 最後のものをダブルクリックする。選択されたすべての + セグメントは1つのnotationウィンドウ中に一緒に + オープンされる。 + </para> + + </listitem> + </varlistentry> + + <varlistentry> + <term>既定のエディタメニュー機能でのオープン(リターンキー)</term> + <listitem> + + <para> + リターンキーは既定のエディタメニュー機能の中のオープン + のショートカットであり、それはダブルクリックと同じ + である。notationエディタ中で現在選択されている + セグメントすべてをまとめてオープンするか、既定値として + 構成したその他のエディタでオープンする。</para> + </listitem> + </varlistentry> + + <varlistentry> + <term>Notationエディタメニュー機能内でのオープン</term> + <listitem> + + <para>代わりに、メインウィンドウのメニュー機能内の + オープンた、キャンバス内のセグメント上の右ボタンの + ポップアップメニュー上でオープンすることもできる。 + 希望のセグメントを選択(上記のようにシフトキー+クリックか、 + <link linkend="commands-main-edit-select-all-segments"> + すべてのセグメントの選択</link>機能のどちらか)し、 + 次に、Notationエディタ中でオープンを選択する。 + </para> + </listitem> + + </varlistentry> + </variablelist> + + </para> + + <para> + もしも1つ以上のstaff(すなわちセグメント)をnotationエディタ + 内で表示したいのであれば、一時にそのうちの1つのみが"カレント" + にできる。 + カレントstaffは、その上に挿入カーソルを持つことで識別すること + ができ(<link linkend="nv-rulers">ルーラとカーソル</link> + を参照)、挿入用カーソルを使う編集操作が起こった上のstaff + である。this is the staff on which any editing + operations that use the insert cursor will take place. + 最上部のstaffは既定値ではカレントであるが、その上で + コントロールキーを押しながらクリックするか、 + Staff上のカーソルを上に + とStaff上のカーソルを下にメニュー機能を使うことで、 + 違ったstaffに切り替えることができる。 + </para> + + </sect2> + + <!-- Linear and page layouts --> + + <sect2 id="nv-layout"> + <title>リニアとページレイアウト</title> + + <para> + notationエディタがstaffを表示する通常の方法は、 + リニアレイアウトとして知られているものである。1つのstaff + がその他の一番上にあり、それぞれのstaffは単独の、水平に + スクロール可能な長い行になっている。エディタ上のいくつかの + 機能は(<link linkend="nv-rulers">ルーラ</link>のようなもの) + リニアレイアウトのみで有効である。 + </para> + + <para> + しかし、2つの違ったページベースのレイアウト内でstaffを + 表示させることも可能である。継続(Continuous)ページ + と複数(Multiple)ページである。</para> + + <para> + 継続ページレイアウト内では、楽曲はウィンドウとして同じ + 幅の無限の高さのページとして編集される。各々のstaffは + 各行の終わりで区切られ、残りのstaffを以下に持つ新しい + 行で始まる。 + </para> + + <para> + 複数ページレイアウトでは楽曲は印刷されるときに真のページに + 分割される。それぞれのページのサイズは、実際に印刷される + 的にそれぞれのラインにほぼ同じ量の楽曲がフィットするように + 計算される(構成ダイアログ中で印刷の改造度のために指定された + ポイントサイズに従って)。印刷バージョンは、印刷するときに + 明確な紙の大きさとマージンに依存するので、まったく同じという + ことはありそうもないが、A4サイズを使うときにはそれはかなり + 近くなければならない。 + </para> + + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-notationview-multipage.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>複数ページレイアウトでの&rosegarden;のnotationエディタ</phrase> + </textobject> + </mediaobject> + </screenshot> + ほとんど、但し全部ではない、表示と編集機能はリニアレイアウト + と同じようにページレイアウトモードで動く。 + </para> + + <para> + 3つのレイアウトモードを切り替えるためには、リニアレイアウト、 + 継続ページレイアウトと複数ページレイアウトメニュー機能を使う。 + </para> + </sect2> + + <!-- Rulers and Cursors --> + + <sect2 id="nv-rulers"> + <title>ルーラとカーソル</title> + + <para> + &rosegarden;notation エディタウィンドウは2つのルーラと + カーソルを含んでいる。ルーラはメインnotationキャンバスの + 上から下までtickmarkとともに水平のstripで分割されていて、 + カーソルはエディタ中のトップのstaffの開始点に初期状態として + 垂直の色が付いた行としてある。 + </para> + + <para> + 紫色のカーソルは挿入カーソルである。これは、挿入かペースト + が起こるような動作のポイントを表示する。上部のルーラ上で + ドラッグかクリックをするか、(任意のイベントを避ける)空白の + staffの一部上でクリックするかドラッグするか、<keycap> + コントロール</keycap>キーを押したままどこかでクリックすること + で挿入カーソルを移動することができる。 + </para> + + <para> + 一度に1つのイベントを、挿入カーソルを移動するために、左か右の + 矢印キーを使うことができる。もしも<keycap>コントロール</keycap> + キーを、矢印キーを押すときに押していると、カーソルは一度に + すべてのバーを移動する。もしもシフトキーを押しているならば、 + カーソルはそれらをパスするように、 + <link linkend="nv-tools-selections">イベントの選択</link> + を行なう。 + </para> + + <para> + 青のカーソルは再生ポインタである。マトリクス表示とメイン + ウィンドウ内の同様のカーソルと同じく、これは、現在の再生 + または録音位置を示す。これは下の方のルーラで位置を変更できる。 + </para> + + <para> + ルーラは<link linkend="nv-layout">リニアレイアウト</link> + モードでのみ表示されることに注意。 + </para> + + </sect2> + + <!-- Display conventions (annotated picture with some selected notes, + some quantized notes, a bar of incorrect length etc) --> + + <!-- Tools and Selections --> + + <sect2 id="nv-tools-selections"> + <title>ツールと選択</title> + <para> + ほとんどの、&rosegarden; Notationエディタのメニューと + ツールバー編集機能は<quote>ツール</quote>、<quote> + 選択を行なう機能</quote>と<quote>ドラッグ操作</quote> + の3つの機能に分類される。 + </para> + + <variablelist> + <varlistentry> + <term>ツール</term> + <listitem> + <para> + 基本的なツールはツールバーボタンから通常アクセスできる、 + 選択ツール、消去ツールと、ノートの挿入、rests、テキスト + その他のためのそれらである。ツールを選択すると、代わりに + 少なくとも他のツールが選択されるまで、メインnotation + キャンバス上でマウスボタンの既定の動作が変わる。たとえば、 + 選択ツールを選択すると、選択が可能になり、(以下の) + 選択ベースの機能が使えるようになる。挿入ツールを選択すると + (たとえばノートの1つ)、<acronym>GUI</acronym>の動作が + 切り替えられ、キャンバス上でクリックすることでノートを + 挿入できる。削除ツールはそれらをクリックすることでイベントを + 削除する。 + </para> + <para> + ツール目丹生を使うことで現在のツールを変更することもできる。 + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>選択操作上の機能</term> + <listitem> + <para> + 残りの大多数のメニュー機能は使うことができる前にキャンバス + 上で選択されることを要求する。そのうちのいくつかは、 + (たとえば、<guimenuitem>Cut</guimenuitem> や + <guimenuitem>Note スタイル</guimenuitem>機能) + 選択されたイベント上で動作する。その他は + (たとえば<guimenuitem>Grace Notes</guimenuitem>や + <guimenuitem>Stem Directions</guimenuitem>機能) + 選択がいくつかのnoteを含むまで実行を凍結する。 + </para> + <para> + キャンバス上のいくつかのイベントを選択するために、 + 選択(矢印)ツールに切り替え、選択したいイベントを含む + 矩形領域を囲む。選択されたイベントは、青にハイライト + される。もしも1つのイベント上でクリックすると、 + そのイベントのみが選択される。 + <footnote><para> + そのイベントのために編集ダイアログをオープンするために + 1つのイベント上でダブルクリックをすることもできるが、 + それは選択には何の動作もしない。</para></footnote>。 + </para> + <para> + もしも、<keycap>シフト</keycap>を矩形領域からドラッグ + アウトする間押しているならば、そのコンテンツは置換の + 変わりに存在する任意の選択に追加される。 + </para> + <para> + すべてのバーを選択するために、そのバー内のどこか空白の + 場所で、選択ツールと共にダブルクリックする。staffのすべて + をセンタｃするために、3回クリックする。編集メニューは + 挿入カーソルの位置上を元にした拡張領域を選択するための + 機能を運び、シフトキーと左又は右矢印キーを押すことによって、 + 挿入カーソルの周りのイベントを選択できる。 + </para> + <para> + 一度に、1つのstaffより多くイベントを選択することはできない。 + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>ドラッグ操作</term> + <listitem> + <para> + あるものの周りでドラッグを行なうことでひとまとまりの編集を + 確実にすることができる。選択(矢印)ツールに切り替え、 + ノートのピッチを、その頭を上か下にクリックし、ドラッグする + ことによって変更でき、noteの時間とその他のイベントは、 + それらを左か右にドラッグすることによって変更できる。 + (残りの時間シグネチャにドラッグできないが、それ以外は + すべてドラッグできる。もしも1つ以上のイベントを選択 + しているならば、一度にすべての選択がドラッグされる。) + </para> + <para> + ドラッグは通常ツールバー機能やメニューを使うよりも、 + より少ない確実な手段であるが、それはより簡単である。 + </para> + </listitem> + </varlistentry> + </variablelist> + </sect2> + + <!-- Insertion: notes, auto-ties, accidentals --> + + <sect2 id="nv-insertion"> + <title>ノートの挿入とrests</title> + + <para> + noteを挿入するために、ツールバー上の特定のduration上でクリックする + ことによってノートメニューの1つを選択し、ノートを追加したい位置の + staff上でクリックする。 + </para> + + <para> + If you add a note at the same time as an existing note of + different duration, the editor will generally assume that you + want to create chords and will split the existing or new note + accordingly so as to create one or more chords with ties. If + you really do want to chord two different durations, you can + select the tied noteheads and use the Collapse Equal-Pitch Notes + function to merge them together. Alternatively, the default + behaviour can be changed in the &rosegarden; configuration dialog + so as not to do the split at all.</para> + + <para> + もしも、異なったduration(すなわち同じピッチ)の存在する音符の + 上に正確に音符を追加するならば、存在する音符のdurationは新しい + ものによって変更される。 + </para> + + <para> + もしも存在する音符と同じような時間の休符を追加するならば、 + 音符は、おそらくそれと共に削除されるか、短くされるか、 + restのdurationのために、封じられる。 + If you add a rest at the same time as an existing note, + the note will be silenced for the duration of the rest, + shortening or possibly removing it altogether.</para> + + <sect3 id="nv-insertion-keyboard"> + <title>PCキーボードによる音符と休符の入力</title> + + <sect4> + <title>Duration</title> + + <para> + 最初に、挿入したいときに音符(又は休符)のdurationを + 表示するためにnotationツールを選択することを確実にすること。 + 以下の数字キーを使うことによって色々なノートタイプを選択できる: + </para> + + <itemizedlist> + <listitem><para><keycap>5</keycap> – Breve</para></listitem> + <listitem><para><keycap>1</keycap> – Whole note (semibreve)</para></listitem> + <listitem><para><keycap>2</keycap> – Half note (minim)</para></listitem> + <listitem><para><keycap>4</keycap> – Quarter note (crotchet)</para></listitem> + <listitem><para><keycap>8</keycap> – Eighth note (quaver)</para></listitem> + <listitem><para><keycap>6</keycap> – Sixteenth note (semiquaver)</para></listitem> + <listitem><para><keycap>3</keycap> – Thirty-second note (demisemiquaver)</para></listitem> + <listitem><para><keycap>0</keycap> – Sixty-fourth note (hemidemisemiquaver)</para></listitem> + </itemizedlist> + + <para>数字キーを押す間に<keycap>Ctrl</keycap>キーを押すと、 + 関連するdotted-noteツールを選択する。</para> + + <para> + <keycap>G</keycap>キーを押すことで、tripletバージョンの + note durationに切り替えることができる。もう一回押すと、 + 通常のdurationに切り替わる。ウィンドウの下部のステータス + バーはtriplet durationが有効の時にそれを通知する。</para> + </sect4> + + <sect4> + <title>ピッチ</title> + + <para> + notationツールが選択されると、以下のピッチキーのどれかを + 押すことによって<link linkend="nv-rulers">カーソルの挿入 + </link> で現在の位置に音符を挿入することができる。</para> + + <itemizedlist> + <listitem><para><keycap>A</keycap> – ド (the tonic of the current key in the current clef)</para></listitem> + <listitem><para><keycap>S</keycap> – レ</para></listitem> + <listitem><para><keycap>D</keycap> – ミ</para></listitem> + <listitem><para><keycap>F</keycap> – ファ</para></listitem> + <listitem><para><keycap>J</keycap> – ソ</para></listitem> + <listitem><para><keycap>K</keycap> – ラ</para></listitem> + <listitem><para><keycap>L</keycap> – シ</para></listitem> + </itemizedlist> + + <para>キーを押している間<keycap>Shift</keycap>キーを押すと、 + 半音noteが高くなり(＃が定義されていないミとシを除く) + <keycap>Shift</keycap>と<keycap>Ctrl</keycap>キーを一緒に押すと、 + 半音低くなる(ファとドを除く) + </para> + + <para>一オクターブ高い音符を入力するためには、以下にあるキーを + 使う。<keycap>Q</keycap>, + <keycap>W</keycap>, <keycap>E</keycap>, <keycap>R</keycap>, + <keycap>U</keycap>, <keycap>I</keycap>と + <keycap>O</keycap>。同様に、オクターブ下の音符を入力する + ためには、 <keycap>Z</keycap>, <keycap>X</keycap>, + <keycap>C</keycap>, <keycap>V</keycap>, <keycap>B</keycap>, + <keycap>N</keycap> と<keycap>M</keycap>を使う。</para> + + </sect4> + + <sect4> + <title>休符</title> + + <para>音符の代わりに休符を挿入するためには、 + <keycap>P</keycap>を使う。その代わりに、現在のツールを + 切り替えてrestツールに、また、noteツールに再度戻すために、 + <keycap>T</keycap> と <keycap>Y</keycap>を使うことができる。 + </para> + + </sect4> + + <sect4> + <title>Chords</title> + + <para> + 既定値のnotationエディタの動作は、音符の挿入後に挿入 + カーソルを次に進め、メロディ中でその後に別の音符を + 挿入できるようになる。これは、<keycap>H</keycap>キーを、 + chordモードに切り替えるために使うことによって、変更する + ことができ、最後のものの同じ時間に続く挿入が起きるchord + モードへ切り替えることができる。再度<keycap>H</keycap> + キーを押すと、メロディ挿入動作に戻る。</para> + + </sect4> + + <sect4> + <title>その他の注意点</title> + + <para> + 挿入コマンドのすべては、ツールメニューのサブメニューで有効で + ある。1つのno-toを挿入するためにメニューを操作することは、 + ありそうもないことであるが、メニューはショートカットを表示し、 + それゆえ、どのキーがどの機能か忘れた場合に有効なリファレンス + を提供する。</para> + + <para> + キーボードショートカットはQWERTYレイアウトキーボード用に + 現在デザインされている。その他のレイアウトにキーをリマップ + する方法はまだなく、設定メニュー上の"ショートカットの構成" + オプションを使うことによって各々のキーの再定義を個別に行なう??。 + The keyboard shortcuts are currently designed for use + with a QWERTY-layout keyboard. There is not yet any way to + remap the keys for another layout, short of reassigning each + key individually using the "Configure Shortcuts..." option + on the Settings menu.</para> + + </sect4> + + </sect3> + + <sect3 id="nv-insertion-midi"> + <title>MIDIキーボードを使った音符の挿入</title> + + <para> + MIDIキーボード又はその他のMIDI制御デバイスを使うことで + マトリクスエディタ中に音符を入力することができる。 + notationエディタはキーボード上で演奏したピッチを使うが、 + durationsはエディタそれ自身でのグリッドの設定中で選択したもの + をつかう。これは"ステップ録音"として知られている。 + </para> + + <para> + MIDIキーボードからノートを入力するために、最初に既定値の + MIDIデバイスにキーボードを構成することを確実にする必要が + ある。次に、notationツールがdurationをセットするために選択 + されることを確実にする。次に、notationエディタのツールバー + 上のステップ録音ボタンかツールメニューのステップ録音を + 選択する。MIDIキーボード上で押されたすべてのノート上のその点 + は、ウィンドウがクローズするか、 + 別のウィンドウが有効になるか、再度ステップ録音がoffにされるまで + そのウィンドウ中に現在の挿入時間で挿入される。 + </para> + + <para> + 異なったdurationのノートを挿入するために、ステップ録音実行 + 中の間別のnotationツールに変更することができ、また、chord + を挿入するために、Chordモードに切り替えることができる。 + </para> + </sect3> + + </sect2> + + <!-- Keys, Clefs and Time Signatures --> + + <sect2 id="nv-signatures"> + <title>Clefs, keys, テンポと時間シグネチャ</title> + + <para> + 時間に関係した変更(テンポと時間シグネチャ)を操作するために + &rosegarden;が行なう方法について知る最初のことは、clefsと + keysに完全に違うことが扱われる。 + The first thing to know about the way &rosegarden; handles + these is that time-related changes (tempos and time + signatures) are treated entirely differently from clefs and + keys. + notationと同じように再生と録音を簡単に管理するために、&rosegarden; + はテンポと時間シグネチャが変更されることを要求し、それは一度に + すべてのstaffを行なう。 + In order to simplify managing playback and recording as + well as notation, &rosegarden; requires that when the tempo or + time signature changes, it does so in all staffs at once. You + can't have one staff in 3/4 and another in 4/4 simultaneously, + or one staff playing at 120 to the beat and another at 90. + This applies only to time: there is no such restriction on the + use of clef and key changes.</para> + + <para>clef, key, テンポまたは時間シグネチャをnotationエディタ + 内で変更したい場合、変更を行ないたい場所に<link + linkend="nv-rulers">挿入カーソル</link>を位置づけ、編集 + メニュー + <link linkend="commands-nv-menu-edit-add-clef">Add Clef + Change...</link>, <link linkend="commands-nv-menu-edit-add-key-signature">Add Key + Change...</link>, <link linkend="commands-nv-menu-edit-add-tempo">Add + Tempo Change...</link> と <link + linkend="commands-nv-menu-edit-add-time-signature">Add Time Signature + Change...</link> 機能を使う。すると以下のように、変更したい固有の + clef,key,テンポまたは時間シグネチャを変更できる所にダイアログ + ボックスが表示される。</para> + + <sect3 id="nv-signatures-clef"> + <title>Clef</title> + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-clefdialog.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>&rosegarden;'s clef dialog</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + </sect3> + + <sect3 id="nv-signatures-key"> + <title>Key</title> + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-keysigdialog.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>&rosegarden;'s key signature dialog</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + </sect3> + + <sect3 id="nv-signatures-tempo"> + <title>テンポ</title> + <!-- Should be in general section, not notation --> + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-tempodialog.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>&rosegarden;'s tempo dialog</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + </sect3> + + <sect3 id="nv-signatures-time-signature"> + <title>時間シグネチャ</title> + <!-- Should be in general section, not notation --> + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-timesigdialog.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>&rosegarden;'s time signature dialog</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + </sect3> + </sect2> + + <!-- Text --> + + <sect2 id="nv-text"> + <title>テキストと歌詞</title> + + <para> + テキストイベント中で、staffはたくさんの種類のテキストを含む + ことが可能である。テキストイベントには2つの基本的なクラスがある。 + 最初のものは、(staff中の特定の時間に関連付けられる)ツールバー + 中の大きな<guilabel>T</guilabel>としてマークされたボタン上で + 有効な、テキストツールを使うことで、作成できる。 + 歌詞は、これと同じ方法で作成できるが、 + <link linkend="nv-text-lyrics">歌詞エディタ</link> + を使うことによってより簡単に作成できる。 + </para> + + <para> + 小さなテキストを追加するために、追加したい点でテキストツールを + 選択してクリックする。ダイアログボックスが表示され、その中に + テキストを入力することができ、その意図された目的を選択する。 + (Rosegarden prefers to store what the text + is for, rather than how it should look; this is so that in + future we may be able to configure how the various sorts of + text are presented for each individual user.) + 有効なpurposes(又はスタイル)は以下の通りである。 + </para> + + <variablelist> + + <varlistentry><term>Dynamic</term><listitem><para> Used for + minor local indications such as the dynamic marks "p", "mf" + etc. Shown below the staff in small italic + type by default. </para></listitem></varlistentry> + + <varlistentry><term>Direction</term><listitem><para> Used + when indicating significant changes in style or mood. Shown + above the staff in large roman type by default. + </para></listitem></varlistentry> + + <varlistentry><term>Local Direction</term><listitem><para> + Used to indicate less significant changes in style or mood. + Shown below the staff in a smaller bold-italic roman type by + default. </para></listitem></varlistentry> + + <varlistentry><term>Tempo</term><listitem><para> Used to + indicate significant changes in tempo. Shown above the + staff in large bold roman type by default. + </para></listitem></varlistentry> + + <varlistentry><term>Local Tempo</term><listitem><para> Used + to indicate more minor or local changes in tempo. Shown + above the staff in a small bold roman type by default. + </para></listitem></varlistentry> + + <varlistentry><term>歌詞</term><listitem><para> + <link linkend="nv-text-lyrics">歌詞エディタ</link> + を使うことで通常歌詞は作成できるが、このスタイルを使うことで + 1語1語入力することもできる。このスタイルは既定値では + 小さなroman type でテキストの下に表示される。 + (注意:もしもこの方法で歌詞を入力し、staffの歌詞を + あとで編集する場合、この方法で入力した任意の歌詞は、 + その位置が、もしも、歌詞エディタによって期待される所と適合して + いなければ、変更又は移動される。) + </para></listitem></varlistentry> + + <varlistentry><term>Annotation</term><listitem><para> Used + for helpful text that is not strictly considered part of the + score. Shown below the staff, boxed-out in a yellow + sticky-label-style box by default. + </para></listitem></varlistentry> + + </variablelist> + + <para> + テキストツールで存在するテキスト上でクリックすることで、 + 作成した後にテキストを編集することもできる。</para> + + <sect3 id="nv-text-lyrics"> + <title>歌誌の編集</title> + + <para><guimenu>表示</guimenu>メニュー中の、 + <guimenuitem>歌詞エディタのオープン</guimenuitem>オプション + から、歌詞エディタは有効であり、これは、一度に1つのstaffの + ためにすべての歌詞イベントを編集することができるようになり、 + これは基本の本文編集システムを使う。これを使うために、メニュー + オプションを有効にし、残りのダイアログ中で歌詞を編集し、 + OKをクリックする。</para> + + <para>The lyrics you enter should follow a particular + format. Bar lines are vital to avoid the editor getting + confused, and are represented with a slash ("/"). Within + each bar the individual syllables are separated by spaces + (at least one space: the editor doesn't care about any extra + whitespace). Each syllable in turn will be attached to the + next subsequent note or chord within that bar (although at + the moment the editor can get quite confused by chords that + are not exact, i.e. that require smoothing or + quantizing).</para> + + <para>If you want a note to have no syllable attached to it, + you need to provide a dot (".") as the syllable for that + note. (This is why the default lyric text for a segment is + usually full of dots.) Remember to separate the dots with + spaces, so that they are clearly separate syllables.</para> + + <para>If you want more than one syllable on the same note, + with a space between them, use a tilde ("~") instead of the + space. It will be shown as a space on the score.</para> + + <para>If you want to split a syllable across two notes, with + a hyphen, you need to enter a space following the hyphen so + the editor knows to treat it as two syllables. (Hyphens get + no special treatment within syllables.)</para> + + <para>Syllables consisting only of numbers surrounded by + square brackets (like "[29]") will be ignored; this is the + format used for the automatically-generated bar numbers + shown in the editor.</para> + + <para>You should also be aware that the textual format of + lyrics is only used for editing: the lyrics are actually + stored as distinct text events (one per syllable). This + means that the text format may potentially change in the + future to accommodate more advanced editing capabilities, + although the event format should not change and so your + saved files should continue to be compatible.</para> + + </sect3> + + </sect2> + + <!-- Indications --> + + <sect2 id="nv-indication"> + <title>スラーとhairpins</title> + + <para>スラーとhairpin dynamic markingsはイベントとして、 + noteやrestsと同じように保存される。これらを生成するために、 + カバーしたいもの(一続きのnoteやその他)の領域を選択し、次に、 + <guimenu>グループ</guimenu>メニューからの + <guimenuitem>スラーの追加</guimenuitem>, + <guimenuitem>クレッシェンドの追加</guimenuitem> または + <guimenuitem>デクレッシェンドの追加</guimenuitem> options from + the <guimenu>Group</guimenu> を選択する。</para> + + <para>その他のイベントと同じように、スラー又はhairpin を取り除く + ことができる。選択ツールを使って選択し、<keycap>Delete</keycap> + キーを押すか、削除ツールを有効にしてそれをクリックする。</para> + + </sect2> + + <!-- Stem direction, slashes etc --> + + <sect2 id="nv-note-qualities"> + <title>Note stems and slashes</title> + + <para>You can set the stem direction of any selected notes + (provided they are a sort that have stems) using the three + Stem Direction options on the Notes menu. The options allow + you to either fix the stems up or down, or revert to the stem + direction that &rosegarden; would otherwise have chosen. See + also <link linkend="nv-beamed-groups">Beams</link>.</para> + + <para>The <guimenu>Notes</guimenu> menu also contains options for adding slashes + across note stems, for example to indicate short repeated + notes or drum rolls. These are currently purely notational; + &rosegarden; will not take them into account when playing the + staff or generating &MIDI;.</para> + </sect2> + + <!-- Beamed groups, including overlapping and nesting them --> + + <sect2 id="nv-beamed-groups"> + <title>Beams</title> + + <para>Adding beams to notes is considered a grouping operation + in the &rosegarden; Notation editor, available on the <guimenu>Group</guimenu> + menu. Select the notes you want to beam, and use the Beam + <guimenu>Group</guimenu> menu option. To remove a beam, select the notes and use + the <guimenuitem>Unbeam</guimenuitem> menu option.</para> + + <para>It is possible to have more than one beamed group + happening at the same time — you just select and beam the + separate groups one at a time — but Rosegarden is usually not + yet clever enough to work out which notes should have stems up + and which should have stems down for simultaneous beamed + groups, so you will probably have to set the stem directions + of the notes in the groups explicitly as well as beaming them.</para> + + <para>&rosegarden; can attempt to guess a sensible beaming for a + piece of music, provided it's not too complicated. To invoke + this, select the notes you want to calculate the beaming for + (for example by triple-clicking to select a whole staff) and + then use the <guimenuitem>Auto-Beam</guimenuitem> option on the + <guimenu>Group menu</guimenu>. Auto-beaming + is also done automatically when loading a &MIDI; file, for + example, and the editor also does some automatic beaming as + you enter notes (this can be disabled by changing the + "Auto-Beam when appropriate" setting on the configuration + dialog or the insertion tool's right-button menu).</para> + + </sect2> + + <!-- Tuplets --> + + <sect2 id="nv-tuplets"> + <title>三連符とその他の連符</title> + + <para>A triplet group consists of three notes or chords played + in the time of two. (More precisely, it consists of notes + with a total duration of three arbitrary units played in the + time of two of those units.)</para> + + <para>We use the word <quote>tuplet</quote> to describe the general + situation in which notes with a total duration of any given + number of units are played in the time of a different number + of those units: nine notes in the time of eight, or six in the + time of four, or a crotchet and a quaver in the time of a + single crotchet, or even two notes in the time of three. (At + present &rosegarden; does not support the last example — tuplet + groups must always be played with a shorter duration than + written.)</para> + + <para>The triplet and tuplet menu functions work by taking an + existing series of notes or rests and squashing them so they + play quicker, filling in the left-over space at the end of the + series with a final rest and drawing the whole as a tuplet + group. You can therefore create a new series of triplets by + entering the first two notes of the series (in their normal + form), making them into triplets, and then filling in the rest + left over by the triplet operation with the final note of the + triplet. Or you can apply the triplet operation before you + enter any notes, thus turning the original rest itself into + triplet form, and then insert the notes of the triplet on top + of it. Some examples may help:</para> + + <!-- Need examples and screenshots --> + + <!-- Then discuss general tuplet dialog... --> + + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-tupletdialog.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>&rosegarden;'s general tuplet dialog</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + + <para>To specify a general tuplet group, we need to know what + the base note is (for example, if we play three crotchets in + the time of two then the base is a crotchet) and the ratio of + the number of base notes written to the number played.</para> + + <!-- Then discuss "tuplet mode": with a subtitle? --> + + </sect2> + + <!-- Grace notes --> + + <!-- Paste --> + + <sect2 id="nv-paste-types"> + <title>Paste types</title> + + <para> + The meaning of <quote>cut and paste</quote> is less obvious for a music + editing program than it is for something like a word + processor in which the letters and words go in a simple + linear order. Accordingly, &rosegarden;'s Notation editor + offers several different types of Paste operation, as well + as separate <link + linkend="commands-nv-menu-edit-cut">Cut</link> and <link + linkend="commands-nv-menu-edit-cut-and-close">Cut and + Close</link> functions. + </para> + + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-pastedialog.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>&rosegarden;'s paste-type dialog</phrase> + </textobject> + </mediaobject> + </screenshot> + + The types of Paste operation are:</para> + + <variablelist> + + <varlistentry> + <term>Restricted</term> + <listitem> + <para>Requires an existing gap (containing nothing but + rests) of enough duration to completely contain the + clipboard's contents. The contents are pasted into + the gap. If there is no gap long enough, the paste + is not carried out. + </para> + <para> + This is the default paste type. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>Simple</term> + <listitem> + <para>Erases enough events to make a gap long enough to + paste into, and then pastes into that. The pasted + events therefore completely replace any existing ones + in the time covered by the paste. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>Open and Paste</term> + <listitem> + <para>The opposite of <link + linkend="commands-nv-menu-edit-cut-and-close">Cut and + Close</link>. Makes room for the paste by moving all of the + subsequent events further towards the end of the + composition. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>Note Overlay</term> + <listitem> + <para>Carries out a paste in the way that it would + happen if you entered each of the notes in the clipboard + yourself using the notation editor: if there are other + notes overlapping with them, the new or existing notes + will be split into ties appropriately. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>Matrix Overlay</term> + <listitem> + <para>Carries out a paste in the way that it would + happen if you entered each of the notes in the clipboard + yourself using the matrix editor: the notes presently + in the way of the paste will be ignored, allowing the new + notes to overlap arbitrarily with them. + </para> + </listitem> + </varlistentry> + + </variablelist> + + <para>All of these take effect at the current position of the + insert cursor on the current staff. To choose between the various + paste types, use the <link + linkend="commands-nv-menu-edit-paste-dot-dot-dot">Paste...</link> + menu option (with dots) on the <link + linkend="commands-nv-menu-edit">Edit</link> menu. + </para> + + </sect2> + + <sect2 id="nv-note-styles"> + <title>音符のスタイル</title> + + <para> + &rosegarden;は、たとえば、音符の頭の選択、tailの数を、音符が + 埋まっているか埋まっていないかにかかわらず、描画された音符の + 色々なタイプの色々な描画方法を変更することができる。 + </para> + + <para> + 標準のスタイル(クラシック、クロス、三角とMensual)が提供され、 + 音符スタイルメニューオプションを、選択した個別の音符のために + スタイルを変更することができる。それぞれの音符はそれに対して + ドのスタイルが選択されたかを憶えていて、この情報は楽曲情報 + の中に格納される。<guimenu>設定</guimenu>メニュー中の + <guimenuitem>Rosegardenの構成...</guimenuitem>オプションを + 使うことによって新しい音符の既定値のスタイルを + 変更することができる。 + </para> + + <para> + <acronym>XML</acronym>ファイル中に音符のスタイルを記述する + ことによって固有の音符スタイルを作成することができる。 + (Even the standard styles are + defined this way: the only reason the editor knows that a + Classical semiquaver has a tilted oval filled head, a stem, + two flags, etc., is that the description in Classical.xml + says so.) See the <link + linkend="developers-note-styles">Developers Guide</link> for + more information. + </para> + </sect2> + + <sect2 id="nv-note-fonts"> + <title>音符フォント</title> + <para> + &rosegarden; は、Lilypondプロジェクトによって開発された、 + Fetaフォントという1つのスケーラブルなnotationフォントを提供 + している。Fetaはほとんどすべての古典的な仕事のために適合して + いるとても高品質のフォントである。 + </para> + + <para>&rosegarden; は、数多くの、その他のnotationフォントを + 標準のサポートを含む。それらは、TrueType(.ttf)またはPostScript + Type-1(.pfb,.pfa)形式のフォントで提供されることを必要とし、 + &rosegarden;がインストールされた場所にそれらをインストール + するために、関連したパーミッションを必要とする。サポートされて + いるnotationフォントをインストールするために、&rosegarden; + のインストールのためにshareディレクトリに位置づける(通常 + /opt/kde/share/apps/rosegardenのようなKDEデスクトップの + インストールツリーである)。これは、"fonts"と呼ばれる + サブディレクトリで見付かる。そこにフォントファイルをコピーし、 + &rosegarden;を再起動する。もしも、そのフォントがサポートされて + いるならば、それは、notationエディタのフォントメニューに + 現われる</para> + + <para>完全又は部分的なサポートは以下のフォントで提供されて + いる:Blake HodgettsによるFughetta; "オリジナル" Finale + フォントのPetrucci;"新しい"Finale"フォントのMaestro; + SibeliusフォントのOpus;Sibelius ジャズフォントのInkpen; + AdobeからのSonata;CubaseシーケンサからのSteinberg;と + Xinfonia(上記のフォントのほとんどは、各社の登録商標で + ある)。THE ROSEGARDEN TEAM + MAKES NO REPRESENTATION AS TO THE LEGAL STATUS OF ANY USE OF + THESE FONTS WITH ROSEGARDEN。 + It is your responsibility to + ensure you are in compliance with the licence (if any) under + which a font was provided to you, before attempting to use it. + If you are not sure whether you have the right to use a font, + don't: apart from anything else, the standard Feta font better + than most of these anyway.</para> + + <para>It is also possible to provide new mapping files so as + to use new fonts. For some fonts that have similar mappings + or metrics to fonts in the above list, this may be as simple + as editing the name of the font in the mapping file. See the + <link linkend="developers-note-fonts">Developers Guide</link> + for more information. + + </para> + </sect2> + + + <!-- Quantization, smoothing, and display of quantized notes --> + + <sect2 id="nv-quantization"> + <title>Notation from performance data</title> + + <para> + &rosegarden; は多用途のプログラムである。これはnotation + エディタであるが、第一次的にはシーケンサと音楽を演奏する + ためのプログラムである。さらに、演奏中、もちろん、時間と + noteのduration は印刷された楽譜上ほど明確ではない。 + </para> + + <para> + これは、notationエディタ中で意味のあるnoteを表示させるために + 大量の基本的なnoteの時間とdurationを試みることを&rosegarden; + が行なうためにそれはたびたび望ましいことを意味する。これは + quantizationの一種であるが、大量の、驚くべき、あてずっぽうで + うまく行なうことを要求する種類のものである。&rosegarden;は、 + 平面のグリッドquantizerよりもわずかによい仕事を行なうために + デザインされたquantizerを含む。</para> + + <para>Applying + quantization strictly for notation is rather unimaginatively + referred to as <quote>notation quantization</quote>: it only + applies to the notes you see and edit in notation, and + doesn't affect the notes that play, or that you edit in + other views such as the matrix. This quantization is + automatically applied to music imported or recorded from + MIDI, although not all of its possible capabilities are + enabled by default. + </para> + + <para> + There are two ways to see which notes have been quantized + for notation. By default, each notation view contains a Raw + Note Ruler (in the group of rulers above the score) showing + a rectangular block for each note. This block is positioned + so as to represent the time and duration of the note as + performed, but with the top and bottom edges of the + rectangle extended or shortened to represent the time after + notation quantization. If this is too much information for + you, you can alternatively choose (in the configuration + dialog) to show in a green colour all note heads in the + score that have had their timings altered by notation + quantization. + </para> + + <para> + + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-notationquantizer.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>&rosegarden;'s notation quantize dialog</phrase> + </textobject> + </mediaobject> + </screenshot> + If the quantization &rosegarden; has used is not suitable, + either for the entire score or for a selection of notes, you + can choose to use a different level of quantization or none + at all. To apply a different quantization to some notes, + select the notes and use the <link + linkend="commands-nv-menu-transforms-quantize">Quantize</link> + menu function (tick the box labelled <quote>Quantize for + notation only</quote>). The quantization level or type used + by default can be changed in the configuration dialog. + </para> + + <sect3 id="nv-quantization-parameters"> + <title>Configurable parameters for the heuristic notation quantizer</title> + + <sect4 id="nv-quantization-parameters-during"> + <title>Parameters for quantization itself</title> + + <variablelist> + + <varlistentry> + <term>Complexity</term> + <listitem> + <para>The "complexity" of a notation quantizer is its + most fundamental parameter. A "complex" quantizer + will be more prepared to accept that complex-looking + music is in fact intended to be complex, whereas a + "simple" quantizer is more likely to assume that + complex-looking music results from an imprecise + performance of simple music. + </para> + <para>The default setting is intended to produce + reasonable results for a fairly wide range of music. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>Base grid unit</term> + <listitem> + <para>The base grid unit (set to a note duration + value) specifies the absolute minimum unit of note + that will be permitted to remain in the score after + quantization. For example, if set to a semiquaver, + all notes will be placed on boundaries of a multiple + of a semiquaver, with durations also a multiple of a + semiquaver. + </para> + <para>The setting of the base grid unit is not quite + as significant for a notation quantizer as it is for a + plain grid quantizer, because all it does is impose an + absolute limit on the level of precision permitted by + the complexity parameter. Mostly, when you find a + case in which increasing the grid unit produces better + results, you've actually found a case in which the + quantizer simply didn't do as good a job as it should + have been able to with the smaller unit. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>Tuplet level</term> + <listitem> + <para>The notation quantizer is capable of identifying + tuplets (triplets and other time-squashed groups), + within reasonable limits. This parameter controls how + ambitious it will attempt to be when looking for + tuplets, by setting a limit on how many notes per + tuplet group it will attempt to identify. If it is + set to <quote>None</quote>, the quantizer will not + attempt to identify tuplets at all. + </para> + </listitem> + </varlistentry> + + </variablelist> + + </sect4> + + <sect4 id="nv-quantization-parameters-after"> + <title>Parameters that control tidying up after quantization</title> + + <variablelist> + + <varlistentry> + <term>Tie notes at barlines etc</term> + <listitem> + <para>Causes any notes that are still found after + quantization to overlap barlines or to have + durations not exactly expressible with single note + heads to be split into multiple notes appropriately, + and tied. This has the same effect as applying the + <!-- !!! link --> "Tie Notes at Barlines" function + in the notation view. + </para> + <para> + This parameter is not set by default because it + changes the number of note events, which is + undesirable when using &rosegarden; partly or + principally as a MIDI sequencer. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>Split-and-tie overlapping chords</term> + <listitem> + <para> + Causes overlapping notes to be split and tied, so + as to make strict chords with individual noteheads + tied as necessary. This has the same effect as + applying the <!-- !!! link --> "Split-and-Tie + Overlapping Chords" function in the notation view. + </para> + <para> + This parameter is not set by default partly because + it changes the number of note events, which is + undesirable when using &rosegarden; partly or + principally as a MIDI sequencer. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>Re-beam</term> + <listitem> + <para> + Causes the notes to be re-beamed into groups + appropriately after quantization. This is usually + desirable. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>Add articulations (staccato, tenuto, + slurs)</term> + <listitem> + <para> + Causes the quantizer to attempt to identify, based + on the durations of individual and consecutive + notes, which notes should be notated with staccato + marks (for notes that fall significantly short of + the following note, but not apparently short + enough to merit a rest), tenuto (for notes that + almost or just overlap the following note) and + slurs (for series of notes that meet or overlap). + </para> + </listitem> + </varlistentry> + </variablelist> + </sect4> + </sect3> + </sect2> + + </sect1> + + <sect1 id="event-view"> + <title>The Event List editor</title> + <sect2 id="ev-introduction"> + <title>概要</title> + + <para> + + The &rosegarden; Event List editor shows the events in a + single segment in a raw form, and enables you to edit the + precise properties of those events individually. + + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-eventlisteditor.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>&rosegarden;'s event list editor</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + </sect2> + </sect1> + + </chapter> + + + + +<!-- + ********************************** + + PART II: + Command reference + + ********************************** + --> + + + <chapter id="commands"> + <title>Command Reference</title> + + <!-- (OPTIONAL, BUT RECOMMENDED) This chapter should list all of + the application windows and their menubar and toolbar commands for + easy reference. Also include any keys that have a special + function but have no equivalent in the menus or toolbars. This may + not be necessary for small apps or apps with no tool or menu + bars. --> + + <para></para> + + <sect1 id="commands-main"> + <title>Main window</title> + <para></para> + + + <sect2> + <title>File menu</title> + <para> + <variablelist> + + <varlistentry id="commands-main-file-new"> + <term><menuchoice> + <shortcut> + <keycombo><keycap>Ctrl</keycap><keycap>n</keycap></keycombo> + </shortcut> + <guimenu>File</guimenu> + <guimenuitem>New</guimenuitem> + </menuchoice></term> + <listitem><para><action>Creates a new composition.</action></para></listitem> + </varlistentry> + + <varlistentry id="commands-main-file-open"> + <term><menuchoice> + <shortcut> + <keycombo><keycap>Ctrl</keycap><keycap>o</keycap></keycombo> + </shortcut> + <guimenu>File</guimenu> + <guimenuitem>Open</guimenuitem> + </menuchoice></term> + <listitem><para><action>Opens an existing composition from a Rosegarden-4 (.rg) file.</action></para></listitem> + </varlistentry> + + <varlistentry id="commands-main-file-import"> + <term><menuchoice> + <guimenu>File</guimenu> + <guimenuitem>Import</guimenuitem> + </menuchoice></term> + <listitem><para>This submenu contains functions for importing compositions from other file formats.</para> + + <variablelist> + + <varlistentry id="commands-main-file-import-midi"> + <term><menuchoice> + <guimenu>Import</guimenu> + <guimenuitem>Import &MIDI; file...</guimenuitem> + </menuchoice></term> + <listitem><para><action>Creates a new composition from the contents of an existing &MIDI; (.mid) file.</action></para></listitem> + </varlistentry> + + <varlistentry id="commands-main-file-import-rg21"> + <term><menuchoice> + <guimenu>Import</guimenu> + <guimenuitem>Import Rosegarden 2.1 file...</guimenuitem> + </menuchoice></term> + <listitem><para><action>Creates a new composition from the contents of an existing Rosegarden 2.1 (.rose) file.</action></para></listitem> + </varlistentry> + + </variablelist> + </listitem> + </varlistentry> + + <varlistentry id="commands-main-file-merge"> + <term><menuchoice> + <guimenu>File</guimenu> + <guimenuitem>Merge</guimenuitem> + </menuchoice></term> + <listitem><para>This submenu contains functions for merging other files into the current composition.</para> + + <variablelist> + + <varlistentry id="commands-main-file-merge-file"> + <term><menuchoice> + <guimenu>Merge</guimenu> + <guimenuitem>Merge File...</guimenuitem> + </menuchoice></term> + <listitem><para><action>Merges the contents of an existing Rosegarden (.rg) file into the current composition. You will be offered a choice of whether to merge the file in new tracks at the start of the composition, or after the end of the current composition.</action></para></listitem> + </varlistentry> + + <varlistentry id="commands-main-file-merge-midi"> + <term><menuchoice> + <guimenu>Merge</guimenu> + <guimenuitem>Merge &MIDI; file...</guimenuitem> + </menuchoice></term> + <listitem><para><action>Merges the contents of an existing &MIDI; (.mid) file into the current composition. You will be offered a choice of whether to merge the file in new tracks at the start of the composition, or after the end of the current composition.</action></para></listitem> + </varlistentry> + + <varlistentry id="commands-main-file-merge-rg21"> + <term><menuchoice> + <guimenu>Merge</guimenu> + <guimenuitem>Merge Rosegarden 2.1 file...</guimenuitem> + </menuchoice></term> + <listitem><para><action>Merges the contents of an existing Rosegarden 2.1 (.rose) file into the current composition. You will be offered a choice of whether to merge the file in new tracks at the start of the composition, or after the end of the current composition.</action></para></listitem> + </varlistentry> + + </variablelist> + </listitem> + </varlistentry> + + <varlistentry id="commands-main-file-export"> + <term><menuchoice> + <guimenu>File</guimenu> + <guimenuitem>Export</guimenuitem> + </menuchoice></term> + <listitem><para>This submenu contains functions for exporting the contents of compositions to other file formats.</para> + + <variablelist> + + <varlistentry id="commands-main-file-export-midi"> + <term><menuchoice> + <guimenu>Export</guimenu> + <guimenuitem>Export &MIDI; file...</guimenuitem> + </menuchoice></term> + <listitem><para><action>Saves the contents of the current composition into a new &MIDI; file.</action> Note that not all data in the Rosegarden composition necessarily can or will be saved in the &MIDI; format.</para></listitem> + </varlistentry> + + <varlistentry id="commands-main-file-export-csound"> + <term><menuchoice> + <guimenu>Export</guimenu> + <guimenuitem>Export Csound score file...</guimenuitem> + </menuchoice></term> + <listitem><para><action>Saves the contents of the current composition into a new Csound score file.</action> Together with a suitable orchestra file (not supplied), this can be used to play the composition through <ulink url="http://www.csounds.com/">Csound</ulink>. Note that not all data in the Rosegarden composition necessarily can or will be saved in the Csound format.</para></listitem> + </varlistentry> + + <varlistentry id="commands-main-file-export-lilypond"> + <term><menuchoice> + <guimenu>Export</guimenu> + <guimenuitem>Export Lilypond file...</guimenuitem> + </menuchoice></term> + <listitem><para><action>Saves the contents of the current composition into a new Lilypond file.</action> This can then be processed by the <ulink url="http://www.lilypond.org/">Lilypond</ulink> system to produce typeset-quality music, although it is likely that the file may need some tweaking to get really good quality output. Note that not all data in the Rosegarden composition necessarily can or will be saved in the Lilypond format.</para></listitem> + </varlistentry> + + <varlistentry id="commands-main-file-export-mup"> + <term><menuchoice> + <guimenu>Export</guimenu> + <guimenuitem>Export Mup file...</guimenuitem> + </menuchoice></term> + <listitem><para><action>Saves the contents of the current composition into a new Mup file.</action> This can then be processed by the <ulink url="http://www.arkkra.com/">Mup</ulink> music publication system, although it is likely that the file may need some tweaking to get really good quality output. Note that not all data in the Rosegarden composition necessarily can or will be saved in the Mup format.</para></listitem> + </varlistentry> + + <varlistentry id="commands-main-file-export-musicxml"> + <term><menuchoice> + <guimenu>Export</guimenu> + <guimenuitem>Export MusicXML file...</guimenuitem> + </menuchoice></term> + <listitem><para><action>Saves the contents of the current composition into a new MusicXML file.</action> This can then be used with any music software that supports the MusicXML format. Note that MusicXML support is experimental and has not been well tested. Not all data in the Rosegarden composition necessarily can or will be saved in the MusicXML format.</para></listitem> + </varlistentry> + + </variablelist> + </listitem> + </varlistentry> + + <varlistentry id="commands-main-file-save"> + <term><menuchoice> + <shortcut> + <keycombo><keycap>Ctrl</keycap><keycap>s</keycap></keycombo> + </shortcut> + <guimenu>File</guimenu> + <guimenuitem>Save</guimenuitem> + </menuchoice></term> + <listitem><para><action>Saves the composition.</action></para></listitem> + </varlistentry> + + <varlistentry id="commands-main-file-save-as"> + <term><menuchoice> + <guimenu>File</guimenu> + <guimenuitem>Save As...</guimenuitem> + </menuchoice></term> + <listitem><para><action>Saves the composition with a new filename.</action></para></listitem> + </varlistentry> + + <varlistentry id="commands-main-file-close"> + <term><menuchoice> + <shortcut> + <keycombo><keycap>Ctrl</keycap><keycap>w</keycap></keycombo> + </shortcut> + <guimenu>File</guimenu> + <guimenuitem>Close</guimenuitem> + </menuchoice></term> + <listitem><para><action>Closes the current composition.</action></para></listitem> + </varlistentry> + + <varlistentry id="commands-main-file-print"> + <term><menuchoice> + <shortcut> + <keycombo><keycap>Ctrl</keycap><keycap>p</keycap></keycombo> + </shortcut> + <guimenu>File</guimenu> + <guimenuitem>Print</guimenuitem> + </menuchoice></term> + <listitem><para><action>Prints the current composition.</action> At the time of writing, the print function is incomplete. We recommend using the <link linkend="commands-main-file-export-lilypond">Export Lilypond file</link> function and printing with Lilypond instead.</para></listitem> + </varlistentry> + + <varlistentry id="commands-main-file-quit"> + <term><menuchoice> + <shortcut> + <keycombo><keycap>Ctrl</keycap><keycap>q</keycap></keycombo> + </shortcut> + <guimenu>File</guimenu> + <guimenuitem>Quit</guimenuitem> + </menuchoice></term> + <listitem><para><action>Quits &rosegarden;</action></para></listitem> + </varlistentry> + + </variablelist> + </para> + + </sect2> + + + <!-- Levi Burton additions 2003.03.05 --> + <sect2> + <title>Edit menu</title> + <para> + <variablelist> + + <varlistentry id="commands-main-edit-undo"> + <term> + <menuchoice> + <shortcut> + <keycombo> + <keycap>Ctrl</keycap> + <keycap>z</keycap> + </keycombo> + </shortcut> + <guimenu>Edit</guimenu> + <guimenuitem>Undo</guimenuitem> + </menuchoice> + </term> + <listitem> + <para> + <action> + Reverses the last command performed. + </action> + </para> + </listitem> + </varlistentry> + + <varlistentry id="commands-main-edit-redo"> + <term> + <menuchoice> + <shortcut> + <keycombo> + <keycap>Ctrl</keycap> + <keycap>Shift</keycap> + <keycap>z</keycap> + </keycombo> + </shortcut> + <guimenu>Edit</guimenu> + <guimenuitem>Redo</guimenuitem> + </menuchoice> + </term> + <listitem> + <para> + <action> + Repeats the last command performed, following an undo. + </action> + </para> + </listitem> + </varlistentry> + + <varlistentry id="commands-main-edit-cut"> + <term> + <menuchoice> + <shortcut> + <keycombo> + <keycap>Ctrl</keycap> + <keycap>x</keycap> + </keycombo> + </shortcut> + <guimenu>Edit</guimenu> + <guimenuitem>Cut</guimenuitem> + </menuchoice> + </term> + <listitem> + <para> + <action> + Removes the currently selected segment from the + composition view and adds it to the clipboard. Note that + when you have selected a track, all segments in that track + are selected. + </action> + </para> + </listitem> + </varlistentry> + + <varlistentry id="commands-main-edit-copy"> + <term> + <menuchoice> + <shortcut> + <keycombo> + <keycap>Ctrl</keycap> + <keycap>c</keycap> + </keycombo> + </shortcut> + <guimenu>Edit</guimenu> + <guimenuitem>Copy</guimenuitem> + </menuchoice> + </term> + <listitem> + <para> + <action> + Removes the selected segments from the composition and + places them in the clipboard to replace any contents the + clipboard previously had. + </action> + Note that when you have selected a track, all segments in that track + are selected. + </para> + </listitem> + </varlistentry> + + + <varlistentry id="commands-main-edit-paste"> + <term> + <menuchoice> + <shortcut> + <keycombo> + <keycap>Ctrl</keycap> + <keycap>v</keycap> + </keycombo> + </shortcut> + <guimenu>Edit</guimenu> + <guimenuitem>Paste</guimenuitem> + </menuchoice> + </term> + <listitem> + <para> + <action> + Inserts the contents of the clipboard into the composition. + Verbage hear stating where the contents are inserted + (current track, offset within that track etc). + </action> + </para> + </listitem> + </varlistentry> + + <varlistentry id="commands-main-edit-delete"> + <term> + <menuchoice> + <shortcut> + <keycombo> + <keycap>Delete</keycap> + </keycombo> + </shortcut> + <guimenu>Edit</guimenu> + <guimenuitem>Delete</guimenuitem> + </menuchoice> + </term> + <listitem> + <para> + <action> + Removes the selected segments from the composition and throws them away. + </action> + </para> + </listitem> + </varlistentry> + + + <varlistentry id="commands-main-edit-select-all-segments"> + <term> + <menuchoice> + <guimenu>Edit</guimenu> + <guimenuitem>Select All Segments</guimenuitem> + </menuchoice> + </term> + <listitem> + <para> + <action> + Selects all segments within the composition. + </action> + </para> + </listitem> + </varlistentry> + + <varlistentry id="commands-main-edit-add-tempo-change"> + <term> + <menuchoice> + <guimenu>Edit</guimenu> + <guimenuitem>Add Tempo Change...</guimenuitem> + </menuchoice> + </term> + <listitem> + <para> + <action> + Invokes a tempo change dialog. + </action> + This offers a + selection of ways to change the tempo of the + composition, including changing the tempo from the + insert cursor position onwards, from the last + tempo change onwards, or for the entire + composition. See <!-- !!!link linkend="segment-tempo-changes" -->Changing the Tempo<!-- /link --> for more information. + + </para> + </listitem> + </varlistentry> + + <varlistentry id="commands-main-edit-add-time-signature"> + <term> + <menuchoice> + <guimenu>Edit</guimenu> + <guimenuitem>Add Time Signature Change...</guimenuitem> + </menuchoice> + </term> + <listitem> + <para> + <action> + Invokes a time-signature change dialog. + </action> + + This offers a + selection of ways to change the tempo of the + composition, including changing the time signature + from the insert cursor position onwards or from the + start of the current bar. See + <!-- !!!link linkend="segment-tempo-changes" -->Changing the Time Signature<!-- /link --> + for more information. + + </para> + </listitem> + </varlistentry> + + + <varlistentry id="commands-main-edit-change-composition-duration"> + <term> + <menuchoice> + <guimenu>Edit</guimenu> + <guimenuitem>Change Composition Duration...</guimenuitem> + </menuchoice> + </term> + <listitem> + <para> + <action> + Invokes a composition duration change dialog. + </action> + + This allows you to change the overall duration of + the composition. This duration sets a hard limit + (as a number of bars) on the scrollable width of the + main window and the length of time you can play or + record before the composition is deemed to have + ended. The default is 100 bars. + + </para> + </listitem> + </varlistentry> + + + <varlistentry id="commands-main-edit-document-properties"> + <term> + <menuchoice> + <guimenu>Edit</guimenu> + <guimenuitem>Edit Document Properties...</guimenuitem> + </menuchoice> + </term> + <listitem> + <para> + <action> + Invokes a document properties dialog. + </action> + + The document properties dialog allows you to review and/or modify the current document properties. Note - explain what are properties. Note to developers - It seems kinda weird to have icons on the left for selecting, and tabs in each one. Why not just tabs or just the things on the left? + + </para> + </listitem> + </varlistentry> + + + </variablelist> + </para> + </sect2> + <!-- Levi Burton additions 2003.03.05 --> + + <sect2> + <title>Segments menu</title> + <para> + <variablelist> + + <varlistentry id="commands-main-segments-open-default-editor"> + <term> + <menuchoice> + <shortcut> + <keycombo> + <keycap>Return</keycap> + </keycombo> + </shortcut> + <guimenu>Segments</guimenu> + <guimenuitem>Open in Default Editor</guimenuitem> + </menuchoice> + </term> + <listitem> + <para> + <action> Opens all of the currently + selected segments together in a notation editor, or in + whichever other editor you have configured as your + default. + </action> + </para> + </listitem> + </varlistentry> + + <varlistentry id="commands-main-segments-open-matrix-editor"> + <term> + <menuchoice> + <guimenu>Segments</guimenu> + <guimenuitem>Open in Matrix Editor</guimenuitem> + </menuchoice> + </term> + <listitem> + <para> + <action> Opens all of the currently + selected segments in a matrix editor. + </action> + See <link linkend="matrix-view">matrix editor</link>. + </para> + </listitem> + </varlistentry> + + <varlistentry id="commands-main-segments-open-notation-editor"> + <term> + <menuchoice> + <guimenu>Segments</guimenu> + <guimenuitem>Open in Notation Editor</guimenuitem> + </menuchoice> + </term> + <listitem> + <para> + <action> Opens all of the currently + selected segments together in a notation editor. + </action> + See <link linkend="notation-view">notation editor</link>. + </para> + </listitem> + </varlistentry> + + <varlistentry id="commands-main-segments-open-event-editor"> + <term> + <menuchoice> + <guimenu>Segments</guimenu> + <guimenuitem>Open in Event List Editor</guimenuitem> + </menuchoice> + </term> + <listitem> + <para> + <action> Opens all of the currently + selected segments together in a event-list editor. + </action> + See <link linkend="event-view">event-list editor</link>. + </para> + </listitem> + </varlistentry> + + + <varlistentry id="commands-main-segments-quantize"> + <term> + <menuchoice> + <guimenu>Segments</guimenu> + <guimenuitem>Quantize...</guimenuitem> + </menuchoice> + </term> + <listitem> + <para> + <action>Invokes a quantization dialog for quantizing the current selection. + </action> + See <link linkend="nv-quantization">quantization</link>. + </para> + </listitem> + </varlistentry> + + <varlistentry id="commands-main-segments-rescale"> + <term> + <menuchoice> + <guimenu>Segments</guimenu> + <guimenuitem>Rescale...</guimenuitem> + </menuchoice> + </term> + <listitem> + <para> + <action>Allows you to stretch or squash segments in time. + </action> + + This option invokes a rescale dialog, which allows + you to specify a ratio of timings that is then + applied to the selected segments. This has the + result of stretching (slowing down) or squashing + (speeding up) the selected segments, changing their + durations accordingly. + + </para> + <para> + This only applies to segments containing MIDI + events, not to audio segments. Rosegarden does not + currently provide native support for audio + time-stretching. + </para> + </listitem> + </varlistentry> + + <varlistentry id="commands-main-segments-auto-split"> + <term> + <menuchoice> + <guimenu>Segments</guimenu> + <guimenuitem>Auto-Split</guimenuitem> + </menuchoice> + </term> + <listitem> + <para> + <action> + Splits the selected segments on silences. + </action> + + This function works slightly differently depending + on whether the selected segments contain audio or + MIDI data. For audio segments, it offers you a + dialog in which you can choose a threshold below + which the segment is considered "silent"; it then + splits the segment whenever its amplitude falls + below this threshold. For MIDI segments, it simply + splits the segment everywhere that a full bar of + silence occurs. + </para> + </listitem> + </varlistentry> + + <varlistentry id="commands-main-segments-split-by-pitch"> + <term> + <menuchoice> + <guimenu>Segments</guimenu> + <guimenuitem>Split by Pitch...</guimenuitem> + </menuchoice> + </term> + <listitem> + <para> + <action>Splits the currently selected segments into higher and + lower parts. + </action> + + This function invokes a dialog allowing you to + choose a pitch as a "split point", and then splits + the selected segments in half with all the notes on + or above that split point in the "higher" segment + and all the notes below it in the "lower". + + </para> + <para> + If the music in the segment consists of two separate + parts (e.g. left and right hand piano parts) that + are not always completely on either side of a single + split point, you may with to select the "ranging + split-point" option. If this is selected, + Rosegarden will attempt to track the two parts as + they move up and down, usually doing a slightly + better job of separating out notes that were + intended to lie in the two separate parts. + + </para> + <para> + The resulting segments are both created on the same + track, with one overlapping the other. + + </para> + </listitem> + </varlistentry> + + + + + </variablelist> + </para> + </sect2> + + + + + </sect1> + + <sect1 id="commands-nv"> + <title>Notation editor</title> + <para></para> + + <!-- Tools --> + <!-- Note insertion tools --> + <!-- Rest insertion tools --> + <!-- Clef insertion tools --> + <!-- Text tool --> + <!-- Eraser --> + + <sect2 id="commands-nv-menu-file"> + <title>File menu</title> + <para> + <variablelist> + + <varlistentry id="commands-nv-menu-file-close"> + <term><menuchoice> + <shortcut> + <keycombo><keycap>Ctrl</keycap><keycap>w</keycap></keycombo> + </shortcut> + <guimenu>File</guimenu> + <guimenuitem>Close</guimenuitem> + </menuchoice></term> + <listitem><para><action>Closes the window</action></para></listitem> + </varlistentry> + + </variablelist> + </para> + + </sect2> + + <sect2 id="commands-nv-menu-edit"> + <title>Edit menu</title> + <para> + <variablelist> + + <varlistentry id="commands-nv-menu-edit-undo"> + <term><menuchoice> + <shortcut> + <keycombo><keycap>Ctrl</keycap><keycap>z</keycap></keycombo> + </shortcut> + <guimenu>Edit</guimenu> + <guimenuitem>Undo</guimenuitem> + </menuchoice></term> + <listitem> + <para> + <action> + + Reverses the last edit. + + </action> Edits are shared across + all views, so if the last edit was not made in + this view, undoing it might not appear to change + this view either. + </para> + </listitem> + </varlistentry> + + <varlistentry id="commands-nv-menu-edit-redo"> + <term><menuchoice> + <shortcut> + <keycombo><keycap>Ctrl</keycap><keycap>Shift</keycap><keycap>z</keycap></keycombo> + </shortcut> + <guimenu>Edit</guimenu> + <guimenuitem>Redo</guimenuitem> + </menuchoice></term> + <listitem> + <para> + <action> + + Repeats the last edit, following an undo. + + </action> + </para> + </listitem> + </varlistentry> + + <varlistentry id="commands-nv-menu-edit-cut"> + <term><menuchoice> + <shortcut> + <keycombo><keycap>Ctrl</keycap><keycap>x</keycap></keycombo> + </shortcut> + <guimenu>Edit</guimenu> + <guimenuitem>Cut</guimenuitem> + </menuchoice></term> + <listitem> + <para> + <action> + + Removes the selected events from the composition + and places them in the clipboard to replace any + contents the clipboard previously had. + + </action> + </para> + </listitem> + </varlistentry> + + <varlistentry id="commands-nv-menu-edit-copy"> + <term><menuchoice> + <shortcut> + <keycombo><keycap>Ctrl</keycap><keycap>c</keycap></keycombo> + </shortcut> + <guimenu>Edit</guimenu> + <guimenuitem>Copy</guimenuitem> + </menuchoice></term> + <listitem> + <para> + <action> + + Copies the selected events to the clipboard + to replace any contents the clipboard previously had. + + </action> + </para> + </listitem> + </varlistentry> + + <varlistentry id="commands-nv-menu-edit-paste"> + <term><menuchoice> + <shortcut> + <keycombo><keycap>Ctrl</keycap><keycap>v</keycap></keycombo> + </shortcut> + <guimenu>Edit</guimenu> + <guimenuitem>Paste</guimenuitem> + </menuchoice></term> + <listitem> + <para> + <action> + + Copies the contents of the clipboard to the + location of the insert cursor in the current + composition. + + </action> + + The clipboard must not contain + multiple segments, and there must be enough + space (occupied only by rests) starting at + the insert cursor position to accommodate the + clipboard's contents. + + </para> + </listitem> + </varlistentry> + + <varlistentry id="commands-nv-menu-edit-cut-and-close"> + <term><menuchoice> + <shortcut> + <keycombo><keycap>Ctrl</keycap><keycap>Shift</keycap><keycap>x</keycap></keycombo> + </shortcut> + <guimenu>Edit</guimenu> + <guimenuitem>Cut and Close</guimenuitem> + </menuchoice></term> + <listitem> + <para> + <action> + + Removes the selected events from the composition + and places them in the clipboard to replace any + contents the clipboard previously had, and closes + the gap left behind by moving all subsequent + events towards the beginning of the composition. + + </action> + </para> + </listitem> + </varlistentry> + + <varlistentry id="commands-nv-menu-edit-paste-dot-dot-dot"> + <term><menuchoice> + <shortcut> + <keycombo><keycap>Ctrl</keycap><keycap>Shift</keycap><keycap>v</keycap></keycombo> + </shortcut> + <guimenu>Edit</guimenu> + <guimenuitem>Paste...</guimenuitem> + </menuchoice></term> + <listitem> + <para> + <action> + + Provides a choice of paste mechanisms with the + ability to set one as the default for use in the + Paste menu function. + + </action> + + See the section on <link linkend="nv-paste-types">Paste types</link> for more information. + + </para> + </listitem> + </varlistentry> + + + <varlistentry id="commands-nv-menu-edit-delete"> + <term><menuchoice> + <shortcut> + <keycombo><keycap>Del</keycap></keycombo> + </shortcut> + <guimenu>Edit</guimenu> + <guimenuitem>Delete</guimenuitem> + </menuchoice></term> + <listitem> + <para> + <action> + Removes the selected events from the composition + and throws them away. + </action> + </para> + </listitem> + </varlistentry> + + + <varlistentry id="commands-nv-menu-edit-select-from-start"> + <term><menuchoice> + <guimenu>Edit</guimenu> + <guimenuitem>Select from Start</guimenuitem> + </menuchoice></term> + <listitem> + <para> + <action> + Extends the current selection by selecting + all events from the start of the staff up to the + current selection (or up to the insert cursor, + if no events are currently selected). + </action> + </para> + </listitem> + </varlistentry> + + + <varlistentry id="commands-nv-menu-edit-select-to-end"> + <term><menuchoice> + <guimenu>Edit</guimenu> + <guimenuitem>Select to End</guimenuitem> + </menuchoice></term> + <listitem> + <para> + <action> + Extends the current selection by selecting + all events from the end of the current selection + (or from the insert cursor, if no events are + currently selected) up to the end of the staff. + </action> + </para> + </listitem> + </varlistentry> + + + <varlistentry id="commands-nv-menu-edit-select-whole-staff"> + <term><menuchoice> + <guimenu>Edit</guimenu> + <guimenuitem>Select Whole Staff</guimenuitem> + </menuchoice></term> + <listitem> + <para> + <action> + Selects all the events on the current staff. + </action> + </para> + </listitem> + </varlistentry> + + + <varlistentry id="commands-nv-menu-edit-clear-selection"> + <term><menuchoice> + <shortcut> + <keycombo><keycap>Esc</keycap></keycombo> + </shortcut> + <guimenu>Edit</guimenu> + <guimenuitem>Clear Selection</guimenuitem> + </menuchoice></term> + <listitem> + <para> + <action> + Unselects all events. + </action> + </para> + </listitem> + </varlistentry> + + + <varlistentry id="commands-nv-menu-edit-filter-selection"> + <term><menuchoice> + <guimenu>Edit</guimenu> + <guimenuitem>Filter Selection</guimenuitem> + </menuchoice></term> + <listitem> + <para> + <action> + Invokes an event filter dialog. + </action> + This offers you the ability to filter a range of events in + any of several categories out of your selection. + </para> + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-eventfilter.png" format="PNG"/> + </imageobject> + <textobject> + <phrase>The event filter dialog</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + <para> + All ranges may be either inclusive or exclusive. + </para> + <para> + An inclusive range will remove events on either side of it + from the selection. You can use this, for example, to + filter everything below middle C and above the A above + middle C out of your selection. + </para> + <para> + An exclusive range will remove the events within the range + itself, leaving everything on either side of it selected. + Using the same search points as in the previous example, + you would use an exclusive range to remove everything + between middle C and the A above middle C from your + selection, while leaving everything above and below that + range selected. + </para> + <para> + Once your selection has been filtered, you can manipulate + it by any conventional means. + </para> + </listitem> + </varlistentry> + + + <varlistentry id="commands-nv-menu-edit-add-tempo"> + <term><menuchoice> + <guimenu>Edit</guimenu> + <guimenuitem>Add Tempo Change...</guimenuitem> + </menuchoice></term> + <listitem> + <para> + <action> + Invokes a tempo change dialog. + </action> + This offers a + selection of ways to change the tempo of the + composition, including changing the tempo from the + insert cursor position onwards, from the last + tempo change onwards, or for the entire + composition. See <!-- !!!link linkend="segment-tempo-changes" -->Changing the Tempo<!-- /link --> for more information. + </para> + </listitem> + </varlistentry> + + + <varlistentry id="commands-nv-menu-edit-add-time-signature"> + <term><menuchoice> + <guimenu>Edit</guimenu> + <guimenuitem>Add Time Signature Change...</guimenuitem> + </menuchoice></term> + <listitem> + <para> + <action> + + Invokes a time-signature change dialog. + + </action> + + This offers a + selection of ways to change the tempo ofthe + composition, including changing the time signature + from the insert cursor position onwards or from the + start of the current bar. See + <!-- !!!link linkend="segment-tempo-changes" -->Changing the Time Signature<!-- /link --> + for more information. + + </para> + </listitem> + </varlistentry> + + + <varlistentry id="commands-nv-menu-edit-add-clef"> + <term><menuchoice> + <guimenu>Edit</guimenu> + <guimenuitem>Add Clef Change...</guimenuitem> + </menuchoice></term> + <listitem> + <para> + <action> + + Invokes a clef selection dialog, and inserts the + chosen clef at the current insert cursor position. + + </action> + + The dialog allows you to choose a clef, but also + to choose how you want the clef to be applied, in + cases where there are already some notes following + the point where the clef is to be inserted. You + must choose one of the following: + + <variablelist> + + <varlistentry> + <term>Maintain current pitches</term> + <listitem> + <para> + Any notes following the clef will keep + their current performance pitches. + </para> + <para> + For example, inserting a + tenor clef in the middle of a previously + treble-clef section will cause the notes following + the clef to be moved an octave + higher up the staff, because they will still have + their treble-clef pitches. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>Transpose into appropriate octave</term> + <listitem> + <para> + Any notes following the clef will + retain their pitch within the octave, but + may be moved into a different octave to + match the new clef, and therefore will play + at a new pitch. + </para> + <para> + For example, inserting a tenor clef in the + middle of a previously treble-clef section + will cause the notes following the clef to + move by one staff line only to adjust to the new + clef, but to play an octave lower than before. + </para> + </listitem> + </varlistentry> + + </variablelist> + + </para> + </listitem> + </varlistentry> + + + <varlistentry id="commands-nv-menu-edit-add-key-signature"> + <term><menuchoice> + <guimenu>Edit</guimenu> + <guimenuitem>Add Key Change...</guimenuitem> + </menuchoice></term> + <listitem> + <para> + <action> + + </action> + </para> + </listitem> + </varlistentry> + + + </variablelist> + </para> + + </sect2> + + <sect2 id="commands-nv-menu-group"> + <title>Group menu</title> + <para> + <variablelist> + + + <varlistentry id="commands-nv-menu-group-beam"> + <term><menuchoice> + <guimenu>Group</guimenu> + <guimenuitem>Beam Group</guimenuitem> + </menuchoice></term> + <listitem> + <para> + <action> + Makes the selected notes into a beamed group. + </action> + </para> + </listitem> + </varlistentry> + + + <varlistentry id="commands-nv-menu-group-auto-beam"> + <term><menuchoice> + <guimenu>Group</guimenu> + <guimenuitem>Auto-Beam</guimenuitem> + </menuchoice></term> + <listitem> + <para> + <action> + Scans the area covered by the selection and attempts + to group short notes into plausible beamed groups. + </action> + </para> + </listitem> + </varlistentry> + + + <varlistentry id="commands-nv-menu-group-break-group"> + <term><menuchoice> + <guimenu>Group</guimenu> + <guimenuitem>Unbeam</guimenuitem> + </menuchoice></term> + <listitem> + <para> + <action> + Removes the selected notes from any beamed groups + they may be part of, leaving them as separate + individuals. + </action> + If part of a beamed group is selected, the unselected + part of the group will remain beamed. + </para> + </listitem> + </varlistentry> + + <varlistentry id="commands-nv-menu-group-tuplet"> + <term><menuchoice> + <guimenu>Group</guimenu> + <guimenuitem>Tuplet</guimenuitem> + </menuchoice></term> + <listitem> + <para> + <action> + Makes a triplet or other tuplet group. + </action> + This function allows you to adjust the timing of a + short section of music in the ratio of two + durations, for example to indicate that three notes + should be played in the time of two (the classic + triplet), or nine in the time of six, or whatever. + You can set this ratio in a dialog box when you + invoke the function. + </para> + <para> + If you have selected some events before invoking the + function, it will assume that you want to make a + tuplet group out of the selected region (or as close + to its duration as possible) and will adjust the + default values available in the dialog accordingly. + </para> + </listitem> + </varlistentry> + + + <varlistentry id="commands-nv-menu-group-simple-tuplet"> + <term><menuchoice> + <guimenu>Group</guimenu> + <guimenuitem>Simple Tuplet</guimenuitem> + </menuchoice></term> + <listitem> + <para> + <action> + + Makes a tuplet group (normally of triplets) with + the most apparently obvious ratio of durations. + + </action> + Usually this function will attempt to make a triplet + group starting at the current insert cursor, or if + some events are selected, will attempt to make them + into triplets. It is possible that it might end up + making non-triplet groups if there is no obvious + valid triplet arrangement. + </para> + </listitem> + </varlistentry> + + + <varlistentry id="commands-nv-menu-group-grace"> + <term><menuchoice> + <guimenu>Group</guimenu> + <guimenuitem>Make Grace Notes</guimenuitem> + </menuchoice></term> + <listitem> + <para> + <action> + Converts the selected notes into grace notes. + </action> + </para> + </listitem> + </varlistentry> + + + + <varlistentry id="commands-nv-menu-group-ungrace"> + <term><menuchoice> + <guimenu>Group</guimenu> + <guimenuitem>Ungrace</guimenuitem> + </menuchoice></term> + <listitem> + <para> + <action> + Converts any grace notes in the selection to + normal notes. + </action> + </para> + </listitem> + </varlistentry> + + + + <varlistentry id="commands-nv-menu-group-slur"> + <term><menuchoice> + <guimenu>Group</guimenu> + <guimenuitem>Slur</guimenuitem> + </menuchoice></term> + <listitem> + <para> + <action> + Adds a slur across the selected notes. + </action> + To remove the slur, click on it + with the erase tool just as you would for a note. + </para> + </listitem> + </varlistentry> + + + + <varlistentry id="commands-nv-menu-group-crescendo"> + <term><menuchoice> + <guimenu>Group</guimenu> + <guimenuitem>Crescendo</guimenuitem> + </menuchoice></term> + <listitem> + <para> + <action> + Adds a crescendo (opening hairpin) indication + across the selected notes. + </action> + To remove the crescendo indication, click on it + with the erase tool just as you would for a note. + </para> + </listitem> + </varlistentry> + + + + <varlistentry id="commands-nv-menu-group-decrescendo"> + <term><menuchoice> + <guimenu>Group</guimenu> + <guimenuitem>Decrescendo</guimenuitem> + </menuchoice></term> + <listitem> + <para> + <action> + Adds a decrescendo (closing hairpin) indication + across the selected notes. + </action> + To remove the decrescendo indication, click on it + with the erase tool just as you would for a note. + </para> + </listitem> + </varlistentry> + +<!-- + + <varlistentry id="commands-nv-menu-group-remove-indications"> + <term><menuchoice> + <guimenu>Group</guimenu> + <guimenuitem>Remove Indications</guimenuitem> + </menuchoice></term> + <listitem> + <para> + <action> + + </action> + </para> + </listitem> + </varlistentry> + +--> + + </variablelist> + </para> + + </sect2> + + <sect2 id="commands-nv-menu-notes"> + <title>Notes menu</title> + <para> + <variablelist> + + <varlistentry id="commands-nv-menu-notes-"> + <term><menuchoice> + <guimenu>Notes</guimenu> + <guimenuitem></guimenuitem> + </menuchoice></term> + <listitem> + <para> + <action> + + </action> + </para> + </listitem> + </varlistentry> + + + <varlistentry id="commands-nv-menu-notes-style-actionmenu"> + <term><menuchoice> + <guimenu>Notes</guimenu> + <guimenuitem>Note Style</guimenuitem> + </menuchoice></term> + <listitem> + <para> + <action> + Change the note style of the selected notes. + </action> + This submenu contains an entry for each of the <link + linkend="nv-note-styles">note + styles</link> that are currently available. Choosing one + will change the note style of the selected notes to + that style. + </para> + </listitem> + </varlistentry> + + + <varlistentry id="commands-nv-menu-notes-stems"> + <term><menuchoice> + <guimenu>Notes</guimenu> + <guimenuitem>Stem Direction</guimenuitem> + </menuchoice></term> + <listitem> + <para> + <action> + Change the stem + direction of the selected notes. + </action> + This submenu allows you to specify that all the + <link linkend="nv-note-qualities">stems</link> of + the selected notes should point up or down, plus an + entry to reset the stem directions to those that + Rosegarden originally chose for the notes. + </para> + </listitem> + </varlistentry> + + + <varlistentry id="commands-nv-menu-notes-slashes"> + <term><menuchoice> + <guimenu>Notes</guimenu> + <guimenuitem>Slashes</guimenuitem> + </menuchoice></term> + <listitem> + <para> + <action> + Add diagonal + slashes across the selected notes' stems. + </action> + This submenu allows you to choose a number of + diagonal strokes or <link linkend="nv-note-qualities">slashes</link> to be drawn across the + stems of each of the selected notes. These may be + used, for example, to indicate repetition or rolls + to a human reader. They do not (yet) affect + performance using Rosegarden. + </para> + </listitem> + </varlistentry> + + </variablelist> + </para> + + </sect2> + + <sect2 id="commands-nv-menu-marks"> + <title>Marks menu</title> + <para> + <variablelist> + <varlistentry> + <term><menuchoice> + <guimenu>blah</guimenu> + <guimenuitem>blah</guimenuitem> + </menuchoice></term> + <listitem> + <para>to be continued</para> + </listitem> + </varlistentry> + </variablelist> + </para> + + </sect2> + + <sect2 id="commands-nv-menu-transforms"> + <title>Transforms menu</title> + <para> + <variablelist> + + <varlistentry id="commands-nv-menu-transforms-normalize-rests"> + <term><menuchoice> + <guimenu>Transforms</guimenu> + <guimenuitem>Normalize Rests</guimenuitem> + </menuchoice></term> + <listitem> + <para> + <action>Makes the rests in the selection + theoretically correct.</action> + + This function examines each sequence of consecutive + rests found in the selection, and adjusts, splits + and merges rests as necessary to ensure that the + rests have theoretically correct durations and fall + on the correct boundaries. + </para> + + <para>For example, a 4/4 bar containing a crotchet + (quarter-note), then a minim (half-note) rest and a + crotchet rest will be rearranged to place the crotchet + rest first, as the minim rest should not cross the + central beat boundary of the bar. + </para> + + <para>This function is also useful in occasional + situations where Rosegarden has made a bad job of + maintaining the rests correctly within a bar, for + example when editing imported &MIDI; data. Normalizing + the rests will usually make the arrangement of notes + in such a situation a bit clearer. (Rosegarden always + normalizes the rests as a matter of course when + importing or recording &MIDI;, but things can sometimes + get muddled up again.)</para> + + </listitem> + </varlistentry> + + <varlistentry id="commands-nv-menu-transforms-collapse-rests"> + <term><menuchoice> + <guimenu>Transforms</guimenu> + <guimenuitem>Collapse Rests</guimenuitem> + </menuchoice></term> + <listitem> + <para> + <action>Makes multiple short rests into fewer longer + ones.</action> + + This function merges consecutive rests into longer + rests, wherever possible. That is, wherever two + consecutive rests in the selection are found to have + a total duration expressible as a single longer + rest, they will be merged. + </para> + </listitem> + </varlistentry> + + <varlistentry id="commands-nv-menu-transforms-collapse-notes"> + <term><menuchoice> + <guimenu>Transforms</guimenu> + <guimenuitem>Collapse Equal-Pitch Notes</guimenuitem> + </menuchoice></term> + <listitem> + <para> + <action>Makes multiple short notes into fewer longer + ones.</action> + + This function merges consecutive notes into longer + notes, wherever possible. That is, wherever two + consecutive notes of equal pitch in the selection + are found to have a total duration expressible as a + single longer note, they will be merged. + </para> + </listitem> + </varlistentry> + + <varlistentry id="commands-nv-menu-transforms-tie-notes"> + <term><menuchoice> + <guimenu>Transforms</guimenu> + <guimenuitem>Tie Equal-Pitch Notes</guimenuitem> + </menuchoice></term> + <listitem> + <para><action>Ties consecutive notes whenever possible.</action> + + This function ties together any consecutive notes of + equal pitch found in the selection. Tied notes are + shown with a curved line joining the note heads, and + are played as a single long note. + </para> + </listitem> + </varlistentry> + + <varlistentry id="commands-nv-menu-transforms-untie-notes"> + <term><menuchoice> + <guimenu>Transforms</guimenu> + <guimenuitem>Untie Notes</guimenuitem> + </menuchoice></term> + <listitem> + <para><action>Breaks ties between notes.</action> + + Any tied notes found in the selection are untied, + and will subsequently be played as separate + notes.</para> + </listitem> + </varlistentry> + + <varlistentry id="commands-nv-menu-transforms-make-viable"> + <term><menuchoice> + <guimenu>Transforms</guimenu> + <guimenuitem>Make Notes Viable</guimenuitem> + </menuchoice></term> + <listitem> + <para><action>Splits notes at displayable + durations.</action> This function is intended to deal + with notes that have excessively long durations that + overflow barlines or that are too long to be displayed + as a single note. It takes any such notes and splits + them into shorter, tied notes. + </para> + </listitem> + </varlistentry> + + <varlistentry id="commands-nv-menu-transforms-de-counterpoint"> + <term><menuchoice> + <guimenu>Transforms</guimenu> + <guimenuitem>De-Counterpoint</guimenuitem> + </menuchoice></term> + <listitem> + <para><action>Turns counterpoint into a series of split-and-tied notes and chords.</action> + + &rosegarden; has no explicit support for counterpoint + (multiple lines of notes edited separately on the + same staff), but it will do its best to approximate + it when it finds notes in a segment that are + apparently contrapuntal, i.e. that overlap but that + are not precise enough to be treated as chords. For + example, when a short note starts shortly after a + longer note, Rosegarden will show the longer note + and a short <quote>spacing</quote> rest together, followed by the + shorter note. Unfortunately this often isn't what + you want. + </para> + + <para>The De-Counterpoint function can be applied to a + selection that contains overlapping notes. It will + split overlapping notes at the point where they + overlap, and tie together the resulting split notes, + ensuring that the music takes the form of a series of + chords and/or single notes starting and ending in neat + blocks, with some notes possibly tied. + </para> + </listitem> + </varlistentry> + + <varlistentry id="commands-nv-menu-transforms-quantize"> + <term><menuchoice> + <guimenu>Transforms</guimenu> + <guimenuitem>Quantize...</guimenuitem> + </menuchoice></term> + <listitem> + <para><action>Quantizes the selection.</action></para> + </listitem> + </varlistentry> + + <varlistentry id="commands-nv-menu-transforms-fix-smoothing"> + <term><menuchoice> + <guimenu>Transforms</guimenu> + <guimenuitem>Fix Smoothed Values</guimenuitem> + </menuchoice></term> + <listitem> + <para><action>Makes the note durations in the current + view permanent.</action> + + When notating recorded or performance &MIDI;, + Rosegarden usually has to round off the durations of + some notes so that they can be displayed as normal + note types. This is known as <link + linkend="nv-quantization">smoothing</link>, and it + normally does not affect the notes actually played, + it's just a convenience for display. The Fix + Smoothed Values function takes the current smoothed + note durations and sets them such that they are used + for performance (and editing in the matrix view, + etc) as well as for notation. + </para> + </listitem> + </varlistentry> + + <varlistentry id="commands-nv-menu-transforms-interpret"> + <term><menuchoice> + <guimenu>Transforms</guimenu> + <guimenuitem>Interpret...</guimenuitem> + </menuchoice></term> + <listitem> + <para><action>Modifies the velocities and timings of + notes according to any written or indicated dynamics + found.</action> The selection of interpretations + available is as follows: + + <variablelist> + <varlistentry> + <term>Apply text dynamics (p, mf, ff etc) + </term> + <listitem><para> Sets a velocity to each note + based on the last piece of text of "Dynamic" + type seen on the same staff (only texts of the + form pp, p, mp, mf, f, ff, fff etc are matched). + </para></listitem> + </varlistentry> + + <varlistentry> + <term>Apply hairpin dynamics + </term> + <listitem><para> Makes the notes gradually + increase or decrease in velocity during a + crescendo or decrescendo hairpin. + </para></listitem> + </varlistentry> + + <varlistentry> + <term> + Stress beats + </term> + <listitem><para> Makes notes that land on bar or + beat boundaries slightly louder (greater + velocity) than the surrounding notes. + </para></listitem> + </varlistentry> + + <varlistentry> + <term> + Articulate slurs, staccato, tenuto etc + </term> + <listitem><para> Shortens unslurred notes, + shortens staccato notes more, and gives notes + inside slurs and tenuto notes their full length. + </para></listitem> + </varlistentry> + </variablelist> + + </para> + + </listitem> + </varlistentry> + + <varlistentry id="commands-nv-menu-transforms-transpose"> + <term><menuchoice> + <guimenu>Transforms</guimenu> + <guimenuitem>Transpose</guimenuitem> + </menuchoice></term> + <listitem> + <para><action>Alters the pitch of the selected + notes.</action> This submenu contains basic + transposition functions which move the selected notes + up or down a semitone or a whole octave in pitch, as + well as a general transpose function that allows you + to choose how far up or down you want to transpose the + selection. + </para> + + <para>These functions simply change the stored pitches + of the notes in the selection, so that they both play + and appear at the new pitches. They do not deal with + performance transposition (displaying one pitch and + playing another), for which see the main window's + segment parameter box; nor do they help you with + transposing from one key into another, for which see + the <link + linkend="commands-nv-menu-edit-add-key-signature">key + change</link> function. + </para> + </listitem> + </varlistentry> + + </variablelist> + </para> + + </sect2> + + + </sect1> + </chapter> + + + + +<!-- + ********************************** + + PART III: + Technical material + + ********************************** + --> + + <chapter id="developers"> + <title>Developer's Guide to Rosegarden</title> + + <sect1 id="developers-note-fonts"> + <title>Configuring custom notation fonts</title> + + <para>If you have a notation font installed on your system in a + scalable format (TrueType or Type-1) but it is not currently + supported by Rosegarden, you can create your own mapping XML + file to describe the font's character map and metrics in a way + Rosegarden can use. These files are installed in the + fonts/mappings subdirectory of the Rosegarden installation + directory, and a number of samples are included with the + distribution.</para> + + <para>You can also use these mapping files to define new + pixmap-based fonts, in which every shape in a particular size is + loaded from a separate pixmap file. The two standard notation + fonts supplied with Rosegarden-4 are pixmap fonts defined in + exactly this way. + </para> + + <para>It is even possible to define a notation font as using one + or more scalable system fonts, augmented with pixmaps for + particular sizes or for characters not found in the scalable + fonts. This is because most of the mapping file format is the + same for scalable and pixmap fonts, and where there are + different elements for the different sorts of fonts, it is + usually possible to include both of them. Rosegarden will + usually use pixmaps where available and scalable fonts + otherwise. + </para> + + <para>You may also wish to edit the mapping files supplied with + Rosegarden if you find their measurements for alignment or + sizing are not to your liking. (If you believe that any of the + supplied files are actually wrong, please let us know.) + </para> + + <sect2 id="developers-note-fonts-codes-glyphs"> + <title>Codes and Glyphs</title> + + <para></para> + </sect2> + + <sect2 id="developers-note-fonts-mapping-format"> + <title>Notation font mapping XML format</title> + + <para>Here is a summary of the XML elements that may be used + in the font mapping file.</para> + + <sect3 id="developers-note-fonts-mapping-format-font-encoding"> + <title>rosegarden-font-encoding</title> + + <para>This element must exist in every mapping file, and + should contain all the other elements. The only attribute + is "name", which contains the font's name as shown in the + font selection dropdown. Although the file format will + permit any name to be used here, Rosegarden will only pick + up the font corectly if the XML file has the same name as + the contents of this attribute (except that the XML file + should be named in lower-case and should end in ".xml"). + </para> + </sect3> + + <sect3 id="developers-note-fonts-mapping-format-font-information"> + <title>font-information</title> + + <para>This should normally be the first child element of + "rosegarden-font-encoding". It may have any of the + following attributes, all of which are optional: + + <variablelist> + <varlistentry> + <term>origin</term> + <listitem> + <para>A textual description of the likely origin of + the mapped font (not the origin of the mapping + file).</para> + </listitem> + </varlistentry> + + <varlistentry> + <term>copyright</term> + <listitem> + <para>A textual description of the likely copyright + status of the mapped font (not the copyright status + of the mapping file). Note that because the mapping + file contains information such as origin and + copyright of the font itself, it is usually + advisable to make separate mapping files for + separate fonts where practical, even if the fonts + share other mapping data.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term>mapped-by</term> + <listitem> + <para>The name of the creator of the mapping file + (i.e. you, presumably).</para> + </listitem> + </varlistentry> + + <varlistentry> + <term>type</term> + <listitem> + <para>The type of the font. This attribute should + contain one of the values "pixmap" or "scalable". + Fonts that are loaded into the windowing system and + are available to Rosegarden as standard system fonts + have type "scalable"; fonts that need to be loaded + from pixmap files corresponding to individual sizes + of pixmap (such as the feta and rg21 fonts included + with Rosegarden) have type "pixmap".</para> + + <para>This information is only intended for the user + reference; it isn't actually used by Rosegarden. It is + legitimate in practice for a font to be a mixture of the + two, but in general we will assume in this documentation + that a font is either scalable or pixmap.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term>smooth</term> + <listitem> + <para>A boolean attribute indicating whether the + font is antialiased (smooth) or not. Should have + the value "true" or "false". If the font is smooth, + other display elements such as beams and slurs that + are not generated from the font will also be + antialiased.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term>autocrop</term> + <listitem> + <para>Only relevant for scalable (system) fonts. + Rosegarden usually expects the metrics for a font to + contain the vertically smallest bounding boxes for + elements such as note heads and accents, rather than + including empty space above or below these elements + for alignment purposes. Most fonts do not do what + Rosegarden expects. Therefore for these fonts you + should set the autocrop attribute to "true"; then + Rosegarden will crop any unnecessary space from the + top and bottom of these elements when rendering + them.</para> + </listitem> + </varlistentry> + + </variablelist> + + </para> + </sect3> + + <sect3 id="developers-note-fonts-mapping-format-font-requirements"> + <title>font-requirements</title> + <para> + This element is only relevant for scalable fonts. It is + used to specify that this font should only be offered if + certain system fonts are available, as well as to + associate IDs with those system fonts to refer to in the + <link + linkend="developers-note-fonts-mapping-format-font-symbol-map">font-symbol-map</link> + element. This scheme is used to decide which notation + fonts should be offered to the user, and also allows you + to compose a Rosegarden notation font from more than one + system font if desired. + </para> + <para>The "font-requirements" element should contain a list + of "font-requirement" child elements. Each of these has two + attributes: "font-id", containing a numerical ID of your + choice for reference elsewhere in the file, and either a + "name" or a "names" attribute. If "name" is provided, it + will be used as the name of a single system font to be + associated with the font id; if "names" is provided, it will + be treated as a comma-separated list of system fonts and the + first one found will be associated with the font id. + </para> + </sect3> + + <sect3 id="developers-note-fonts-mapping-format-font-sizes"> + <title>font-sizes</title> + + <para>The "font-sizes" element specifies which notation font + sizes are available, and how the nominal font size relates + to the dimensions of non-font elements such as stems, staff + lines and beams. The "size" of a notation font is assumed + to be the distance in pixels between staff lines, or more + precisely, the height of a conventional note head that + completely fills the space between lines: the size therefore + does not include the thickness of either of the neighbouring + staff lines. + </para> + + <para> + <!-- !!! TODO throughout this section: how to mark up XML element/attribute names? equiv of <code> in HTML would do --> + There are two possible child elements of "font-sizes": + "font-scale" and "font-size". Their use depends on the + type of font being described.</para> + + <para> + For pixmap (non-scalable) fonts, the "font-sizes" element + should contain a list of "font-size" elements, one for + each size of pixmaps available. The pixmaps themselves + must be installed in the + fonts/<font-name>/<font-size> subdirectory of + the Rosegarden installation directory, where + <font-name> is the name of the font (as specified in + the "rosegarden-font-encoding" element at the start of the + mapping file), or a lower-case version of the name, and + <font-size> is the pixel size of the font. A font + size will only be made available to the user if it has an + entry in the "font-sizes" list and the pixmap directory is + found. + </para> + + <para> + For scalable fonts, the "font-sizes" element should + contain one "font-scale" element that defines the + relationships between font and non-font elements in a + general way, and also defines the relationship between + Rosegarden's nominal font size and the size of the + corresponding system font. If this "font-scale" element + is found, then Rosegarden will assume the font is + available in any size. You can however still include one + or more "font-size" elements to define precise proportions + for any particular size for which the general proportions + do not quite work correctly, for example because of + rounding error. + </para> + + <para> + The attributes of "font-scale" and "font-size" are very + similar. The main difference is that all attributes of + "font-scale" are floating-point values relative to the + font size, where 1.0 is the base font size (i.e. the + distance between staff lines), whereas attributes of + "font-size" are integer pixel values. The attributes + available are as follows. (Those marked "optional" have + vaguely sensible defaults, so it's a good idea to try not + setting them first.) + </para> + + <variablelist> + + <varlistentry> + <term>note-height</term> + <listitem> + <para>This attribute is only available for the + "font-size" element, and it is mandatory in that + element. It defines the base size of font to which the + other attributes in this element apply, and a size that + will be offered to the user and used when looking up + pixmaps for this font.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term>font-height</term> + <listitem> + <para>May be used in either "font-size" or "font-scale". + This is only relevant for scalable fonts, but is + mandatory for them if used in the "font-scale" element. + This defines the size of the system font used to draw a + given size of notation font.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term>beam-thickness</term> + <listitem> + <para>Optional. Defines the thickness of a beam.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term>staff-line-thickness</term> + <listitem> + <para>Optional. Defines the thickness of a staff line.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term>stem-thickness</term> + <listitem> + <para>Optional. Defines the thickness of a note stem.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term>flag-spacing</term> + <listitem> + <para>Optional. Defines the gap between note flags in + cases where multiple flags are drawn by drawing a single + flag several times.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term>border-x</term> + <listitem> + <para>Optional. Specifies that the note head pixmaps + have a fixed area to left and right that should not be + considered part of the note head. This attribute gives + the thickness of that area.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term>border-y</term> + <listitem> + <para>Optional. Specifies that the note head pixmaps + have a fixed area to top and bottom that should not be + considered part of the note head. This attribute gives + the thickness of that area.</para> + </listitem> + </varlistentry> + + </variablelist> + </sect3> + + <sect3 id="developers-note-fonts-mapping-format-font-symbol-map"> + <title>font-symbol-map</title> + <para> + This element lists the symbols available in this notation + font, and which pixmap files or system font code points + they should be drawn from.</para> + + <para>It should contain a list of "symbol" elements. These + have several possible attributes, the choice of which will + normally depend on whether the font is based on pixmaps or + system fonts: + </para> + + <variablelist> + <varlistentry> + <term>name</term> + <listitem> + <para>Mandatory. This attribute should contain the + name of the notation symbol. If the symbol exists in + the <ulink + url="http://www.unicode.org/charts/PDF/U1D100.pdf">Unicode + 3.2 standard</ulink>, the name should be that used to + identify the symbol in the standard.</para> + + <para>Most of the symbols Rosegarden expects to find + are in the standard; one exception is that many fonts + have a special version of the flag symbol that is + intended to be used when composing multiple flags from + individual single flags. Rosegarden refers to this as + "MUSICAL SYMBOL COMBINING FLAG-0", a name not used in + the Unicode standard (which has flags 1-5 only).</para> + + <para>For a definitive set of the symbol names + Rosegarden knows about, see the file + "gui/notecharname.cpp" in the Rosegarden source + distribution. Note however that it is possible to use + additional symbol names by introducing them in a <link + linkend="developers-note-styles">notation + style</link>. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>src</term> + <listitem> + <para>The name of the pixmap file from which this + symbol should be loaded, without a directory or + extension. This is the usual way of describing a + symbol in a pixmap font. The file itself should be + installed to + fonts/<font-name>/<font-size>/<src>.xpm + under the Rosegarden installation directory. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>inversion-src</term> + <listitem> + <para>The name of a pixmap file from which an inverted + version of this symbol may be loaded, without a + directory or extension. If this attribute is absent + and an inverted version of the symbol is required, it + will be generated simply by loading the normal version + and reflecting it in a central x-axis. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>code</term> + <listitem> + <para>The code point at which this symbol may be found + in the relevant system font, as a decimal integer. + This is a way of describing a symbol in a scalable + font. This attribute will only be referred to if no + pixmap file is supplied, or if the pixmap file fails + to load. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>inversion-code</term> + <listitem> + <para>The code point at which an inverted version of + this symbol may be found in the relevant system font. + If this attribute is absent and an inverted version of + the symbol is required, it will be generated simply by + loading the normal version and reflecting it in a + central x-axis. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>glyph</term> + <listitem> + <para>The raw glyph index at which this symbol may be found + in the relevant system font, as a decimal integer. + This is a way of describing a symbol in a scalable + font. This attribute will only be referred to if no + pixmap file is supplied, or if the pixmap file fails + to load. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>inversion-glyph</term> + <listitem> + <para>The raw glyph index at which an inverted version of + this symbol may be found in the relevant system font. + If this attribute is absent and an inverted version of + the symbol is required, it will be generated simply by + loading the normal version and reflecting it in a + central x-axis. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>font-id</term> + <listitem> + <para>The id of the system font from which this symbol + should be loaded, as defined in the <link + linkend="developers-note-fonts-mapping-format-font-requirements">font-requirements</link> + element. The default is 0. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>codebase</term> + <listitem> + <para>This (decimal integer) attribute may be of use + if many of the symbols in a scalable font cover a + short range of code points starting at a relatively + high code page. If supplied, the codebase value will + be added to each of the subsequent code and + inversion-code values when looking up a symbol. + </para> + </listitem> + </varlistentry> + + </variablelist> + + <para> + Although none of these attributes is mandatory except for + the name, a symbol obviously needs to supply at least one + of "src", "inversion-src", "code", "inversion-code", + "glyph", or "inversion-glyph" to stand any chance of being + rendered at all. It is of course perfectly legitimate to + supply several or all of these attributes. + </para> + + </sect3> + + <sect3 id="developers-note-fonts-mapping-format-font-hotspots"> + <title>font-hotspots</title> + <para> + </para> + </sect3> + + </sect2> + + </sect1> + + <sect1 id="developers-note-styles"> + <title>Creating new notation styles</title> + + <para> + Rosegarden's notation editor has the ability to display and + edit notes in various standard styles: classical, diamond + heads and so on. These styles are all defined in XML style + definition files installed along with the application, and + it's possible to create a new one by writing a simple XML + file. Rosegarden simply looks at the set of installed files + to determine which styles to offer the user. You can refer to + the default set of files in the styles subdirectory of the + Rosegarden installation directory for examples. + </para> + + <para> + The file format is not yet especially comprehensive; at the + moment it has been designed to be powerful enough to describe + the standard styles that come with Rosegarden, but not much + more. If you should try to create new styles this way, we'd + be very interested in your feedback on the Rosegarden + mailing-lists. + </para> + + <sect2 id="developers-note-styles-format"> + <title>Notation style XML format</title> + + <para> + Here is a summary of the XML elements that may be used in + a style definition file. + </para> + + <sect3 id="developers-note-styles-note-style"> + <title>rosegarden-note-style</title> + + <para>This element must exist in every style file, and + should contain all the other elements. It has one optional + attribute, "base-style", which may be used to name a style + from which this style takes the default values for any + parameters not specified elsewhere in the present file. + It's often good practice to define a style in terms of the + minimal difference from a given base style: see the supplied + Cross.xml for a particularly simple example. + </para> + + <para>Note that the "rosegarden-note-style" element does not + give the name of the style being defined, which is instead + currently drawn from the name of the file. At some point in + the future we may add internationalizable style name + attributes to this element.</para> + </sect3> + + <sect3 id="developers-note-styles-global-note"> + <title>global, note</title> + + <para>Within the "rosegarden-note-style" element, there may + be one "global" element and any number of "note" elements. + We describe these together, as they have almost identical + sets of attributes. The "global" element simply provides + default values for those parameters not specified for a + particular note type in any following "note" element. + </para> + + <para>The attributes for these elements are as follows. All + of these are optional except as described:</para> + + <variablelist> + + <varlistentry> + <term>type</term> + <listitem> + <para>Only relevant to the "note" element, and + mandatory for that element. This attribute specifies + which sort of note is being styled. Legal values are + textual American or British note names (from "64th", + "sixth-fourth note", "hemidemisemiquaver" etc to + "double whole note"). + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>shape</term> + <listitem> + <para>Defines a note head shape for this style. Any + string is a legal value, but the only values + implemented so far are "angled oval", "level oval", + "breve", "cross", "triangle up", "triangle down", + "diamond" and "rectangle". The value "number" is also + recognised but not yet implemented. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>charname</term> + <listitem> + <para>Defines a note font character name to be used as + the note head for this style. An element may supply a + "shape" or "charname" attribute, but not both. The + name should be one of those defined in the current + notation font's <link + linkend="developers-note-fonts-mapping-format-font-symbol-map">symbol + map</link> (in a "name" attribute). + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>filled</term> + <listitem> + <para>Specifies whether this note should have a filled + head (where applicable, i.e. where the shape attribute + supplies a shape that is available both filled and + unfilled). Must be "true" or "false". + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>stem</term> + <listitem> + <para>Specifies whether this note should have a stem. + Must be "true" or "false". + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>flags</term> + <listitem> + <para>Defines how many flags or beams this note should + have. The valid range is 0 to 4. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>slashes</term> + <listitem> + <para>Defines how many slashes this note should have + across its stem. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>hfixpoint</term> + <listitem> + <para>Specifies in which x position the stem fixes to + the note head. Acceptable values are "normal" (the + right side when the stem points up, the left when it + points down), "central", and "reversed" (left side + when the stem points up, right when it points down). + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>vfixpoint</term> + <listitem> + <para>Specifies in which y position the stem fixes to + the note head. Acceptable values are "near" (the stem + fixes to the top when pointing up, the bottom when + pointing down), "middle", or "far". + </para> + </listitem> + </varlistentry> + + </variablelist> + </sect3> + </sect2> + </sect1> + + + <!-- (OPTIONAL) A Programming/Scripting reference chapter should be + used for apps that use plugins or that provide their own scripting hooks + and/or development libraries. --> + + <!-- cc: I think we should document the DCOP API here, but I don't + think we should include extensive developer docs, although we should + point to where they can be found in the source tree or online. --> +<!-- + <para> + Programming <application>Rosegarden</application> plugins is + a joy to behold. Just read through the next + 66 pages of <acronym>API</acronym>'s to learn how! + </para> +--> + <!-- Use refentries to describe APIs. Refentries are fairly + complicated and you should consult the docbook reference for + further details. The example below was taken from that reference + and shortened a bit for readability. --> +<!-- + <refentry id="re-1007-unmanagechildren-1"> + <refmeta> + <refentrytitle>XtUnmanageChildren</refentrytitle> + <refmiscinfo>Xt – Geometry Management</refmiscinfo> + </refmeta> + <refnamediv> + <refname>XtUnmanageChildren + </refname> + <refpurpose>remove a list of children from a parent widget's managed list. + </refpurpose> + </refnamediv> + <refsynopsisdiv> + <refsynopsisdivinfo> + <date>4 March 1996</date> + </refsynopsisdivinfo> + <synopsis> + void XtUnmanageChildren(<replaceable>children</replaceable>, <replaceable>num_children</replaceable>) + WidgetList <replaceable>children</replaceable>; + Cardinal <replaceable>num_children</replaceable>; + </synopsis> + + <refsect2 id="r2-1007-unmanagechildren-1"> + <title>Inputs</title> + <variablelist> + <varlistentry> + <term><replaceable>children</replaceable> + </term> + <listitem> + <para> + Specifies an array of child widgets. Each child must be of + class RectObj or any subclass thereof. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term><replaceable>num_children</replaceable> + </term> + <listitem> + <para>Specifies the number of elements in <replaceable>children</replaceable>. + </para> + </listitem> + </varlistentry> + </variablelist> + </refsect2></refsynopsisdiv> + + <refsect1 id="r1-1007-unmanagechildren-1"> + <title>Description + </title> + <para> + <function>XtUnmanageChildren()</function> unmaps the specified widgets + and removes them from their parent's geometry management. + The widgets will disappear from the screen, and (depending + on its parent) may no longer have screen space allocated for + them. + </para> + <para>Each of the widgets in the <replaceable>children</replaceable> array must have + the same parent. + </para> + <para>See the “Algorithm” section below for full details of the + widget unmanagement procedure. + </para> + </refsect1> + + <refsect1 id="r1-1007-unmanagechildren-2"> + <title>Usage</title> + <para> + Unmanaging widgets is the usual method for temporarily + making them invisible. They can be re-managed with + <function>XtManageChildren()</function>. + </para> + <para> + You can unmap a widget, but leave it under geometry + management by calling <function>XtUnmapWidget()</function>. You can + destroy a widget's window without destroying the widget by + calling <function>XtUnrealizeWidget()</function>. You can destroy a + widget completely with <function>XtDestroyWidget()</function>. + </para> + <para> + If you are only going to unmanage a single widget, it is + more convenient to call <function>XtUnmanageChild()</function>. It is + often more convenient to call <function>XtUnmanageChild()</function> + several times than it is to declare and initialize an array + of widgets to pass to <function>XtUnmanageChildren()</function>. Calling + <function>XtUnmanageChildren()</function> is more efficient, however, + because it only calls the parent's <function>change_managed()</function> + method once. + </para> + </refsect1> + + <refsect1 id="r1-1007-unmanagechildren-3"> + <title>Algorithm + </title> + <para><function>XtUnmanageChildren()</function> performs the following: + </para> + <variablelist> + <varlistentry> + <term>- + </term> + <listitem> + <para>Ignores the child if it already is unmanaged or is being + destroyed. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>- + </term> + <listitem> + <para>Otherwise, if the child is realized, it makes it nonvisible + by unmapping it. + </para> + </listitem> + </varlistentry> + </variablelist> + <para> + </para> + </refsect1> + + <refsect1 id="r1-1007-unmanagechildren-4"> + <title>Structures</title> + <para> + The <type>WidgetList</type> type is simply an array of widgets: + </para> + <screen id="sc-1007-unmanagechildren-1"> + typedef Widget *WidgetList; + </screen> + </refsect1> + </refentry> +--> + </chapter> + + + <chapter id="credits"> + + <title>Credits and License</title> + + <para> + <application>Rosegarden</application> + </para> + <para> + <itemizedlist> + <listitem> + <para> + + Rosegarden-4 is Copyright 2000-2003 Guillaume Laurent, + Chris Cannam and Richard Bown. The moral rights of + Guillaume Laurent, Chris Cannam and Richard Bown to be + identified as the authors of this work have been asserted. + + </para> + </listitem> + + <listitem> + <para> + + Parts of Rosegarden-4 are derived from Rosegarden 2.1, + which is Copyright 1994 – 2001 Chris Cannam, Andrew Green, + Richard Bown and Guillaume Laurent. + + </para> + </listitem> + + <listitem> + <para> + + For musical notation display Rosegarden-4 uses pixmaps + derived from the Feta font, part of the <ulink + url="http://lilypond.org/">Lilypond</ulink> software, + which is Copyright 1997 – 2001 Jan Nieuwenhuizen and + Han-Wen Nienhuys. + + </para> + </listitem> + + <listitem> + <para> + + Other major contributors include Randall Farmer, Ron + Kuris, Hans Kieserman, and Michael McIntyre. + + </para> + </listitem> + + <listitem> + <para> + + The Rosegarden splash-screen image is from a 1900 postcard + of Thornden Park at Syracuse University, Syracuse, NY, + used with thanks to the staff of Syracuse University. + + </para> + </listitem> + + </itemizedlist> + </para> + + <para> + Documentation copyright 2002-2003 Chris Cannam, Richard Bown, Guillaume Laurent + </para> +<!-- + <para> + Translations done by: + <itemizedlist> + <listitem> + <para>Babel D. Fish <email>babelfish@kde.org</email> (Sanskrit)</para> + </listitem> + </itemizedlist> + </para> +--> + <!-- For URL links to common stuff like the one below, + always use paths like "common/gpl-licence". + In this path, "common" will be a symbolic link built at "make install" time. + This link will normally point to $KDEDIR/share/doc/HTML/en/common, + where "en" should be replaced with the current language. --> + + <para> + This program is licensed under the terms of the + <ulink url="common/gpl-license.html">GNU GPL</ulink>. + </para> + </chapter> + + + &documentation.index; +</book> diff --git a/doc/sv/CMakeLists.txt b/doc/sv/CMakeLists.txt new file mode 100644 index 0000000..eb6d853 --- /dev/null +++ b/doc/sv/CMakeLists.txt @@ -0,0 +1,12 @@ +################################################# +# +# (C) 2011 Timothy Pearson +# kb9vqf (AT) pearsoncomputing.net +# +# Improvements and feedback are welcome +# +# This file is released under GPL >= 2 +# +################################################# + +tde_create_handbook( DESTINATION rosegarden ) diff --git a/doc/sv/index.docbook b/doc/sv/index.docbook new file mode 100644 index 0000000..066dcb0 --- /dev/null +++ b/doc/sv/index.docbook @@ -0,0 +1,6485 @@ +<?xml version="1.0" ?> +<!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.1.2-Based Variant V1.0//EN" "dtd/kdex.dtd" [ + <!ENTITY rosegarden "<application +>Rosegarden</application +>"> + <!ENTITY MIDI "<acronym +>MIDI</acronym +>"> + <!ENTITY % Swedish "INCLUDE" +> <!-- change language only here --> + <!ENTITY % addindex "IGNORE"> +]> + +<!-- The language must be changed in the <book +> tag for translations. --> + + +<!-- + + Notes on style and terminology for Rosegarden handbook + ====================================================== + + * Aim to be clear, brief and direct, but be informal. + + * Write instructions in the second person. + + Good: "You can select segments by clicking on + them with the arrow tool." + + Bad: "Segments can be selected by clicking on + them with the arrow tool." + + Very bad: "The arrow tool allows the user to select + segments by clicking on them." + + If you dislike the first of these because you want to + make the phrase "the arrow tool" more obvious by placing + it at the start of the sentence, then perhaps you + should be using a variablelist instead and making + "the arrow tool" a list item. + + * It's perfectly permissible to detour to explain why + something is the way it is, particularly if it might + not be obvious. + + * It's also entirely permissible to omit advanced stuff + from the "Using Rosegarden" section and document it + only in the reference section. "Using Rosegarden" + should be about understanding how and why, not about + knowing every last clever detail. + + * Bear in mind we can link extensively from any part of + the handbook to any other. Unfortunately DocBook won't + allow you to write a link to a target that doesn't + exist yet, so if you want to link to something that's + not yet been written, either make a note of the planned + link in an XML comment, or go and create a stub for the + bit that hasn't been written yet, or else just write in + a way that allows for a link to be easily added later + (we could do an editing phase specially for links). + + * Be strict about using the correct terminology for + Rosegarden data structures (segment, event, track, + instrument, composition), but don't capitalise the + words. Capitalisation is useful in technical documents + to make it clear that you're referring to a precise + concept, but you shouldn't have to do it to make your + meaning clear in user documentation. If something + seems ambiguous without, try rewording it instead. + + + About Screenshots + ================= + + Screenshots used with this documentation should use the + following style, colour and font settings: + + * KDE Style: "Light Style, 3rd Revision" + + * Colour scheme: "Blue Slate", with high-contrast + setting and with the standard widget background set + to white. (I have this saved as a new scheme.) + + * Fonts: Verdana 11px for general use and menus; Verdana + 11px bold for window titles; antialiasing on, but + sub-pixel antialiasing off. (For pictures of the + segment and instrument parameter boxes I usually turn + the size up to 13px, which perhaps says something about + our use of font size in these boxes.) + + * Window Decorations: "Quartz" + + None of these would be my first choice for nice-looking + screenshots now, but we're not here to sell Rosegarden in this + document, we're here to provide clear and consistent help text. + So the priority is to make new screenshots look like the existing + ones, not to make them look fancy. Also, I think there is an + advantage to having screenshots in a help document look a bit + distinct from the user's own window decorations surrounding the + help text. + + Screenshots of the whole program or of whole matrix or + notation windows may be taken using different themes if + desired, but screenshots of individual dialogs or window + components must use the above scheme. + +--> + +<!-- + Notes on Usability Defects + ========================== + + This comment is a place to note anything I find difficult to + document, or anything where the functions for two necessarily + linked concepts are not actually linked in the GUI (etc). + + * The audio file directory (in document properties) can't be + inspected or changed from the audio file manager. This is + arguably linked to a need for a project directory. There + are various other usability problems with the audio file + manager as well, e.g. there's no way to tell it to pull all + imported audio files into a single audio directory. + + * Track buttons showing sometimes-instrument, sometimes-label. + + * Can't usefully double-click / right-click on most rulers. + This would be useful for a slower but clearer way to set + loops; adding and editing markers; etc. Setting loops is + particularly opaque especially in notation and matrix views. + + * Hideous inconsistency (documented in an RFE already) between + having to use RG for MIDI routing and being unable to use RG + for audio routing. + + * Uh, Pedro implemented this multiport recording but we can't + actually split the results can we? + + Troubleshooting + =============== + + Shall we have a troubleshooting section? + + * I'm not seeing any MIDI outputs + * I'm not hearing any sound from my MIDI outputs + * I'm not seeing any audio outputs + * I'm not hearing any sound from my audio outputs + * I don't see any synth plugins + +--> + +<!-- + Still to do + =========== + + * Control rulers + + * Controller editing + + * Event list + + * Event editor dialogs + + * Tempo / timesig editor + + * Triggered segments + + * Split by Pitch + + * Document properties + + * Add images for the tools (move, split &c) when describing them + + * Add images for transport buttons in transport section + + * Update notation menu references + + * Add new notation stuff + + * Config dialog + + * Make sure the guimenuitem etc tags are being used for all menu refs + + * Give keyboard shortcuts for menu functions? + + * Go through again changing Rosegarden -> &rosegarden; and double-hyphen -> + – or — and review any uses of "the ... function" to see + if these words are redundant + + * Troubleshooter + + * Check !!! items + + * Fill gaps in revision history + + * Consistent capitalisation: Instrument Parameter Box or instrument + parameter box? Audio Mixer or audio mixer? Device or device? + + * Finally, review the structure again and adjust the <chapter +>/<sect*> + for balance + +--> + + +<book id="rosegarden" lang="&language;"> + + <!-- This header contains all of the meta-information for the document such + as Authors, publish date, the abstract, and Keywords --> + + <bookinfo> + <title +>Handbok Rosegarden</title> + <authorgroup> + <author +><firstname +>Chris</firstname +> <surname +>Cannam</surname +> </author> + <author +><firstname +>Richard</firstname +> <surname +>Bown</surname +> </author> + <author +><firstname +>Guillaume</firstname +> <surname +>Laurent</surname +> </author> + <othercredit role="translator" +> <firstname +>Stefan</firstname +> <surname +>Asserhäll</surname +> <affiliation +><address +><email +>stefan.asserhall@comhem.se</email +></address +></affiliation +> <contrib +>Översättare</contrib +></othercredit +> + </authorgroup> + + <copyright> + <year +>2002-2004</year> + <holder +>Chris Cannam, Richard Bown, Guillaume Laurent</holder> + </copyright> + + <date +>2005-08-04</date> + <releaseinfo +>1.2.0</releaseinfo> + + <abstract> + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-mainwindow.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>&rosegarden;</phrase> + </textobject> + </mediaobject> +</screenshot +> Rosegarden är ett program för ljud- och &MIDI;-inspelning och en editor för musikalisk notskrift. Den här handboken beskriver hur det används. </para> + </abstract> + + <keywordset> + <keyword +>Rosegarden</keyword> + <keyword +>musikbehandlare</keyword> + <keyword +>MIDI</keyword> + <keyword +>ljud</keyword> + <keyword +>musik</keyword> + <keyword +>beteckning</keyword> + <keyword +>partitur</keyword> + <keyword +>KDE</keyword> + </keywordset> + + </bookinfo> + + <!-- The contents of the documentation begins here. Label each + chapter so with the id attribute. This is necessary for two reasons: + it allows you to easily reference the chapter from other chapters of + your document, and if there is no ID, the name of the generated HTML + files will vary from time to time making it hard to manage for + maintainers and for the CVS system. Any chapter labelled (OPTIONAL) + may be left out at the author's discretion. Other chapters should + not be left out in order to maintain a consistent documentation + style across all KDE apps. --> + + <chapter id="introduction"> + <title +>Inledning</title> + + <sect1> + <title +>Om Rosegarden</title> + <para +><application +>Rosegarden</application +> är ett program för ljud- och &MIDI;-inspelning och en editor för musikalisk notskrift. Rosegarden låter dig spela in, arrangera och komponera musik, i form av ett traditionellt partitur eller &MIDI;-data, eller ljudfiler som antingen importeras eller spelas in via en mikrofon, gitarr eller vilken ljudkälla du önskar. Du kan använda Rosegarden för att skriva, redigera och organisera musik för att skapa en komposition, som du därefter kan syntetisera, lägga till effekter i och mixa för att bränna till en cd eller distribuera på webben. Rosegarden innehåller också professionellt stöd för notredigering för utskrift med hög kvalitet. </para> + + <para +><application +>Rosegarden</application +> är konstruerat för att se ut som och fungera på ett sätt som är bekant för erfarna användare som kommer till Linux från andra plattformar, medan det också är tillgängligt och användarvänligt för de som är nykomlingar till musikprogramvara i allmänhet. </para> + + <sect2 id="intro-handbook"> + <title +>Om den här handboken</title> + <para +>Den här handboken ger en översikt av &rosegarden;s möjligheter, och tillhandahåller en referens för en del av de begrepp som ingår. Den är skapad för att antingen vara meningsfull när den läses i en följd, eller när den används som en referens till begrepp och tillgängliga funktioner i Rosegarden. Om du dessutom vill läsa en handledning, <ulink url="http://www.rosegardenmusic.com/resources/tutorial/using_en.shtml" +>hittar du en här</ulink +>.</para> + + <para +>Om det finns något annat du inte förstår eller något du behöver ytterligare hjälp med, besök gärna <ulink url="http://www.rosegardenmusic.com/support/" +>Rosegardens webbplats</ulink +> för vanliga frågor och instruktioner om användning av e-postlistan. </para> + </sect2> + + <sect2 id="intro-menufunctions"> + <title +>Om menyer och snabbtangenter</title +> <para +>Handboken hänvisar oftast till funktionerna du kan använda i Rosegarden genom att beskriva var de befinner sig i menyerna. Funktionen för att lägga till ett enstaka nytt spår i huvudspåreditorn är exempelvis <menuchoice +><guimenu lang="sv" +>Spår</guimenu +> <guimenuitem +>Lägg till spår</guimenuitem +></menuchoice +>.</para> + + <para +>I många fall är det inte det enda sättet att nå en viss funktion. I det här fallet är samma funktion också tillgänglig via snabbtangenten Ctrl+T, och den visas också som en ikon i en av huvudfönstrets verktygsrader. Både snabbtangenten och ikonen kan snabbt läras in, eftersom de visas i Rosegardens meny tillsammans med funktionens namn. Du bör komma ihåg att även om vi alltid anger det fullständiga menyalternativet i dokumentationen av referensskäl, är det inte nödvändigtvis det bästa eller det vanligaste sättet att använda en funktion, och du bör dessutom hålla ett öga på snabbtangenter och ikoner i verktygsraderna. </para> + </sect2> + + <sect2 id="intro-optional"> + <title +>Valfria funktioner</title +> <para +>Handboken antar att installationen av Rosegarden stöder alla funktionerna som det har möjlighet till. Vissa av Rosegardens funktioner, inklusive några av de större, är i själva verket valfria när en installation av Rosegarden byggs. Hela ljuddelsystemet kompileras till exempel bara om JACK-biblioteken är tillgängliga, stöd för syntinsticksmoduler beror på ett antal andra moduler, etc.</para +> <para +>Dessa beroenden är dokumenterade i filen README och Rosegardens konfigureringsdokumentation. Om du märker att handboken hänvisar till funktioner som inte finns i den version av Rosegarden som du använder, rådfråga konfigureringsdokumentationen eller distributören. </para> + </sect2> + </sect1> + </chapter> + + +<!-- + ********************************** + + PART I: + Discussion and tutorial material + + ********************************** + --> + + + <chapter id="file-operations"> + <title +>Rosegarden-filer och -dokument</title> + <para +>&rosegarden; lagrar varje komposition i ett eget dokument, med sitt eget interna format. När du sparar ett dokument lagras det på disk som en fil med filändelsen .rg. &rosegarden; kan också hantera ett antal andra standardfilformat. </para> + + <sect1 id="file-creating"> + <title +>Nya kompositioner</title> + <para +>När &rosegarden; startar, görs det med ett nytt dokument som innehåller en "tom" komposition som är klar att börja redigera. För att lägga till något i kompositionen måste du antingen spela in något eller skapa några tomma musikavsnitt (som kallas "segment"), som du sedan kan fylla i med de olika redigeringsfunktionerna. </para> + <para +>Se <link linkend="recording" +>Inspelning</link +> för detaljinformation om hur musik spelas in, och se avsnittet om <link linkend="segment-view" +>spåreditorn</link +> för en beskrivning av hur musiksegment skapas, redigeras och hanteras. </para> + </sect1> + + <sect1 id="file-midi"> + <title +>Använda MIDI-filer</title> + <para +>För att importera och exportera MIDI-filer, använd alternativen <menuchoice +><guimenu lang="sv" +>Arkiv</guimenu +> <guimenuitem +>Importera</guimenuitem +> <guimenuitem +>Importera MIDI-fil</guimenuitem +></menuchoice +> och <menuchoice +><guimenu lang="sv" +>Arkiv</guimenu +> <guimenuitem +>Exportera</guimenuitem +> <guimenuitem +>Exportera MIDI-fil</guimenuitem +></menuchoice +>. </para> + <para +>Även om &rosegarden; kan ladda och spara filformat som MIDI, lagras inte MIDI-data internt. Du bör i allmänhet föredra att spara filer med &rosegarden;s eget format, eftersom &rosegarden; lagrar en hel del information som går förlorad vid export till MIDI. </para> + <para +>När en MIDI-fil laddas, delar &rosegarden; upp musiken i ett spår per MIDI-spår eller kanal i filen, <link linkend="studio-midi-import" +>ställer in lämpliga instrumentavbildningar</link +> och <link linkend="nv-quantization" +>försöker beräkna en trolig notering</link +> för utförd MIDI-data. </para> + </sect1> + + <sect1 id="file-merge"> + <title +>Sammanfoga filer</title +> <para +>Förutom att ladda eller importera filer, kan du också sammanfoga dem med det nuvarande dokumentet, och lägga till segmenten som hittas i filen till de som redan finns. </para> + + <para +>För att sammanfoga en fil, använd bara passande alternativ i undermenyn <menuchoice +><guimenu lang="sv" +>Arkiv</guimenu +> <guimenuitem +>Sammanfoga</guimenuitem +></menuchoice +>, istället för att använda alternativen Öppna eller Importera. </para> + </sect1> + + <sect1 id="file-printing"> + <title +>Utskrift</title> + <para +>Du kan skriva ut en komposition i form av ett partitur, genom att använda funktionen <menuchoice +><guimenu lang="sv" +>Arkiv</guimenu +> <guimenuitem +>Skriv ut</guimenuitem +></menuchoice +>. </para> + + <para +>Att skapa ett partitur från utförd data är en svår uppgift, och i de flesta fall är det inte rimligt att förvänta sig att en standardutskrift baserad på MIDI-data är särskilt läsbar. Du bör använda <link linkend="notation-view" +>notbehandlaren</link +> för att städa upp partituret innan du skriver ut det. (Se också <link linkend="nv-quantization" +>Notskrift från utförandedata</link +>.) </para> + + <para +>&rosegarden; klarar av att skapa helt läsbara partitur. Även om det är så, är programmet avsett att vara en skärmeditor, och inte i huvudsak avsett för typsättning. Om du vill skapa partitur med riktig utskriftskvalitet, bör du fundera på att använda <ulink url="http://www.lilypond.org" +>Lilypond</ulink +> tillsammans med &rosegarden;. Lilypond är programvara för typsättning av musik som läser ett specialiserat textfilformat, och skapar typsatt utmatning av hög kvalitet. &rosegarden; klarar av att skriva Lilypond-filer med funktionen <menuchoice +> <guimenu lang="sv" +>Arkiv</guimenu +> <guimenuitem +>Exportera</guimenuitem +> <guimenuitem +>Exportera Lilypond-fil</guimenuitem +></menuchoice +>. </para +> </sect1> + + </chapter> + + <chapter id="segment-view"> + <title +>Spåreditorn</title> + <sect1 id="segment-view-overview"> + <title +>Översikt</title> + <para +>&rosegarden;s utseende liknar många andra populära musikbehandlare. Det är baserat på en spårstruktur: Huvudfönstret visar en spåreditor med en spårlista och tillhörande instrument längs med vänster sida. Du kan behandla och flytta block med musikdata (som kallas “segment”) i spåreditorn, samt öppna själva segmenten i specialiserade editorer (<link linkend="notation-view" +>not</link +>, <link linkend="matrix-view" +>matris</link +>, <link linkend="percussion-matrix-view" +>slagverksmatris</link +> och <link linkend="event-view" +>händelselista</link +>). </para> + + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-trackeditor.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>&rosegarden;s spåreditor som visar två segment med musikdata</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + + <para +>Spår kan tilldelas en uppsättning &MIDI;-instrument, syntinsticksmoduler eller ljudinstrument. I bilden ovan syns tre segment i spåreditorn för spår som är tilldelade till generella MIDI-instrument. </para> + + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-trackbutton-labels.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>&rosegarden;s spårknappar som visar spårnamn</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + + <para +>Området med knappar till vänster om segmentduken visar spårnummer, tystnads- och inspelningsstatus, och spårets namn. Du kan göra ett spår tyst eller inte genom att klicka på den blåa knappen i form av en lysdiod, och välja ett visst spår som ska användas för inspelning genom att klicka på den röda knappen. För att ändra spårnamnet, dubbelklicka på det. </para> + + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-trackbutton-instruments.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>&rosegarden;s spårknappar som visar instrumenttilldelningar</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + + <para +>Spårnamn visas bara om menyalternativet <menuchoice +><guimenu lang="sv" +>Inställningar</guimenu +> <guimenuitem +>Visa spårnamn</guimenuitem +></menuchoice +> är aktiverat. Annars visas spårens instrumenttilldelningar istället, som i bilden.</para> + + </sect1> + <sect1 id="segment-view-instruments"> + <title +>Spår och instrument</title> + <para +>Varje spår måste ha ett tilldelat instrument för att kunna höras. Normalt tilldelas de 16 första spåren till de 16 instrumenten i den första tillgängliga MIDI-enheten, och de följande 16 spåren tilldelas till ljud.</para> + + <para +>För att ändra instrumenttilldelningen för ett spår, högerklicka på spårnamnet: En meny dyker upp där du kan välja bland alla tillgängliga instrument. </para> + + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-trackbutton-instrumentmenu.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>&rosegarden;s instrumentmeny</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + + <para +>Ett instrument kan betraktas som en enstaka kanal i en &MIDI;-enhet, som en mono- eller stereoljudutgång, eller som en ljudsyntinsticksmodul. Spår som innehåller notinformation ska tilldelas till &MIDI;- eller syntinsticksinstrument, och de som innehåller ljud till ljudinstrument. Du kan tilldela mer än ett spår till samma instrument, och i så fall använder alla dessa spår samma ljud. </para> + <para +>Du kan ändra diverse egenskaper för instrumentet som tilldelats ett spår, genom att använda <link linkend="segment-view-instrumentparameterbox" +>instrumentparameterrutan</link +>. Det är till exempel här som du kan ställa in ett MIDI-instrument så att det använder en speciell ljudpatch, och på så sätt åstadkommer ett speciellt ljud (piano, stråkar, etc.). </para> + <para +>Se avsnittet <link linkend="studio-introduction" +>Studio</link +> för mer om instrument. </para> + + </sect1> + + <sect1 id="segment-view-creating"> + <title +>Skapa segment</title> + <para +>För att skapa ett tomt segment när någonting nytt ska komponeras, måste du använda pennverktyget. Klicka på pennan i verktygsraden, och klicka därefter på stället där du vill att segmentet ska börja (på rätt plats för spåret som du vill att segmentet ska finnas i, och på ett avstånd i redigeringsfönstret som motsvarar rätt tid) och dra åt höger till segmentet är rätt antal takter i längd. </para> + + <para +>Oftast börjar varje nytt segment på ett taktstreck och utökas takt för takt, men effekten att låsa till rutnätet kan förhindras genom att hålla nere Skift under klick- och dragåtgärden. </para> + + <para +>När du väl har skapat ett segment kan du börja redigera det med <link linkend="matrix-view" +>matriseditorn</link +>, <link linkend="percussion-matrix-view" +>slagverksmatriseditorn</link +> eller <link linkend="notation-view" +>notbehandlaren</link +>. För att använda en av editorerna, dubbelklicka antingen på segmentet eller klicka med höger musknapp och välj editorn du vill använda i den sammanhangsberoende menyn. </para> + + <para +>Om du avser att <link linkend="recording" +>spela in</link +> från en MIDI-enhet eller ljudingång, behöver du inte först skapa ett nytt segment att spela in till. Varje enskild inspelning hamnar alltid i ett nytt segment, som skapas automatiskt under inspelningen. </para> + </sect1> + + <sect1 id="segment-view-audio-segments"> + <title +>Ljudsegment</title> + <para +>Ett ljudsegment innehåller inspelad eller samplad ljuddata, istället för redigerbar tonhändelsedata. Rosegarden låter dig spela in, spela upp, arrangera och dela ljudsegment, men innehåller inte funktioner för redigering av ljudvågformer. </para> + <para +>För att skapa ett ljudsegment kan du <link linkend="recording" +>spela in</link +> från en ljudkälla till ett spår som hör till ett ljudinstrument, eller arbeta med befintliga WAV-filer. För att göra det måste du använda ljudhanteringsdialogrutan (som nås via <menuchoice +><guimenu lang="sv" +>Segment</guimenu +> <guimenuitem +>Hantera ljudsegment</guimenuitem +></menuchoice +>). </para> + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-audiofilemanager.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>Ljudfilhantering</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + + <para +>Du kan dra och släppa ljudfiler från KDE:s filbläddrare eller KDE-skrivbordet till ljudfilhanteringen, eller öppna dem med dess arkivmeny. Därefter kan du antingen dra och släppa dem på Rosegardens spårduk, eller använda menyfunktionen <menuchoice +><guimenu lang="sv" +>Åtgärd</guimenu +> <guimenuitem +>Infoga i markerat ljudspår</guimenuitem +></menuchoice +> i ljudfilhanteringen, under förutsättning att spåret som för närvarande är markerat i huvudfönstret är tilldelat till ett ljudinstrument. Nyinspelade ljudsegment syns också i dialogrutan för ljudfilhantering.</para> + + <para +>Information om ljudfilerna som hör ihop med en viss komposition är sparad med kompositionen, men själva ljudfilerna är inte det. Du måste försäkra dig om att ditt dokument har en vettig sökväg för ljudfiler (via <menuchoice +><guimenu lang="sv" +>Komposition</guimenu +> <guimenuitem +>Redigera dokumentegenskaper...</guimenuitem +> <guimenuitem +>Ljud</guimenuitem +></menuchoice +>, för att göra det möjligt att komma åt dina ljudfiler tillsammans.</para> + + <para +>Dialogrutan för ljudfilhantering visar också samplingsfrekvensen och annan information för varje ljudfil, och markerar eventuella ljudfiler vars samplingsfrekvens inte motsvarar nuvarande JACK-ljudsessionen som Rosegarden använder. Rosegarden samplar om filerna vid uppspelning med en snabb linjär omsampling (men därför med mycket dålig kvalitet). Du råds att sampla om dem separat med en särskild dedicerad ljudeditor istället. </para> + + </sect1> + + <sect1 id="segment-view-manipulating"> + <title +>Hantering av segment</title> + <para +>Huvudfönstret innehåller en uppsättning "verktyg" för att redigera segment. De är tillgängliga i huvudverktygsraden: Välj först verktyget du vill ha i verktygsraden, och klicka och dra därefter på segmenten i huvudduken. </para> + + <sect2 id="segment-view-selector"> + <title +>Markeringsverktyget</title> + <para +>"Markeringsverktyget" (pilverktyget) är i själva verket ett verktyg med flera användningar. Det kan användas för att markera, flytta, kopiera, ändra storlek och skapa segment.</para> + + <para +>Den mest uppenbara användningen är markering: Markera ett enstaka segment genom att klicka på det med markeringsverktyget, eller markera flera genom att klicka med Skift nertryckt, eller genom att klicka på ett tomt ställe i fönstret och dra för att åstadkomma ett område. </para> + + <para +>För att flytta segment med markeringsverktyget, klicka och dra helt enkelt segmentet. För att skapa kopior, klicka och dra med Ctrl nertryckt. För att ändra storlek på ett segment, klicka och dra segmentets högerkant, och för att skapa nya segment klicka och dra på ett tomt ställe med musens mittenknapp. </para> + + <para +>Markeringsverktyget ersätter ändå inte övriga verktyg helt och hållet: Ibland behöver du vara noggrannare med vilken åtgärd du avsåg, särskilt vid arbete med små segment. </para> + + </sect2> + + <sect2 id="segment-view-move-resize"> + <title +>Verktygen för att flytta och ändra storlek</title> + <para +>För att flytta ett segment till en annan starttid eller ett annat spår, använd förflyttningsverktyget och klicka och dra segmentet du vill flytta. Om du håller nere Ctrl-tangenten medan du drar, kopieras segmentet istället för att flyttas.</para> + + <para +>För att ändra storlek på ett segment, använd verktyget för storleksändring, och klicka och dra i högra ändan av segmentet.</para> + + <para +>Både vid förflyttning och storleksändring kan du hålla nere Skift för finpositionering, för att undvika att hoppa till en viss rutnätsposition. </para> + + </sect2> + + <sect2 id="segment-view-split-join"> + <title +>Delningsverktyget</title> + <para +>Du kan använda delningsverktyget <inlinemediaobject +> <imageobject +> <imagedata fileref="rg-split.png"/> </imageobject +> </inlinemediaobject +> för att dela ett enstaka segment i två separata segment. För att dela segmentet, välj delningsverktyget och klicka på segmentet du vill dela. </para> + <para +>Normalt delas segment vid taktstrecket närmast markören, men det kan förhindras genom att hålla nere Skift när segmentet delas. </para> + </sect2> + </sect1> + + <sect1 id="segment-view-tempo-timesig"> + <title +>Tempo och taktart</title> + <sect2 id="tempo"> + <title +>Tempo</title> + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-tempodialog.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>&rosegarden;s tempodialogruta</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + </sect2> + + <sect2 id="time-signature"> + <title +>Taktart</title> + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-timesigdialog.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>&rosegarden;s taktartsdialogruta</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + </sect2> + </sect1> + </chapter> + + <chapter id="transport"> + <title +>Överföringen</title> + <para +>När du spelar upp en komposition, sveper &rosegarden; en uppspelningsmarkör över spåren från vänster till höger och spelar upp innehållet i segmenten när den korsar dem. Markörens position på skärmen följs och styrs av ett fönster som kallas Överföring. </para> + + <sect1 id="transport-overview" +><title +>Översikt</title> + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-transport.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>&rosegarden;s överföringsfönster</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + + <para +>Om överföringen inte är synlig, kan du aktivera den med <menuchoice +> <guimenu lang="sv" +>Inställningar</guimenu +> <guimenuitem +>Visa överföring</guimenuitem +></menuchoice +>. </para> + + <para +>Överföringen visar tiden som uppnåtts av uppspelningsmarkören, normalt i sekunder. Du kan ändra den att visa metronomtid (takter och taktslag), metronomtid med en blinkande visuell metronom, eller ramtider för ljudsampling, med den översta av de små knapparna till vänster i överföringsfönstret. Knappen direkt nedanför byter mellan att visa tid som är kvar till kompositionens slut istället för tid från början.</para> + + <para +>Huvudknapparna i överföringen startar uppspelning med musikbehandlaren eller gör paus, flyttar markörpositionen framåt, flyttar den bakåt, stoppar den eller går till kompositionens början eller slut. </para> + + <para +>Ytterligare knappar och visning av &MIDI;-händelser är dolda längst ner i överföringsfönstret, och kan visas eller inte med pilknappen i det längst till vänster. Dessutom finns knappar för inspelning, för upprepning, för att spela enskilda spår solo, för att stänga av eller sätta på metronomen och för att tysta dina MIDI-enheter (panikknapp) i extradelen. </para> + + </sect1> + <sect1 id="recording"> + <title +>Inspelning</title> + <para +>För att spela in ett nytt segment i ett spår, försäkra dig först om att rätt spår är markerat för inspelning genom att klicka på den röda (för ljudspår) eller gula (för MIDI-spår) lysdiodknappen vid spårets namn, och använd därefter överföringens inspelningsknapp. Det ger effekten att både starta överföringen, och därigenom spela upp den befintliga kompositionen, och att spela in i motsvarande spår. </para> + <para +>Du kan bara markera ett enda MIDI-spår för inspelning, men du kan spela in hur många ljudspår som helst samtidigt så länge datorn är kraftfull nog. Du kan också markera ett MIDI-spår och ett eller flera ljudspår samtidigt. Var försiktig så att du inte lämnar spår markerade av misstag när du är klar med användning av dem och försöker spela in någon annanstans. </para> + <para +>Som ett alternativ kan du använda punch-in inspelning för att skilja på åtgärderna att starta överföringen och gå in i inspelningsläge. Punch-in inspelning ändras med mellanslagstangenten. Du kan trycka på mellanslag medan en komposition spelas upp för att omedelbart byta mellan uppspelning och inspelning utan att stoppa överföringen, eller använda mellanslag för att förbereda inspelning medan överföringen är stoppad, så att följande uppspelning i själva verket också spelar in. (Det senare är praktiskt vid synkronisering med en <link linkend="transport-external" +>extern överföring</link +>.) </para> + <para +>Om du spelar in ett MIDI-spår, sker inspelning från alla MIDI-enheter som är inställda för inspelning i <link linkend="studio-device-editor" +>MIDI-enhetshanteringen</link +>. </para> + <para +>Om du spelar in ljudspår, sker inspelning av varje spår från ingången som för närvarande är inställd för det spårets instrument i <link linkend="segment-view-instrumentparameterbox" +>instrumentparameterrutan</link +>. Det är antingen en extern ljudingång eller en delnivå eller huvudnivå för ljud (för att utföra ihopmixningar). Om det är en extern ingång, spelas det normalt in från ljudkortets första tillgängliga fysiska inspelningsingång. Du kanske vill använda ett anslutningsverktyg i JACK för att ansluta ett annat ljudprogram som stöder JACK till ingången istället. </para> + </sect1> + <sect1 id="transport-external"> + <title +>Synkronisering med extern överföring</title> + <sect2 id="transport-jack"> + <title +>Överföring med JACK</title> + <para +>Rosegarden stöder överföringsmekanismen i JACK för att synkronisera överföringen med andra program med JACK på samma dator. För att aktivera den, gå till <menuchoice +><guimenu lang="sv" +>Inställningar</guimenu +> <guimenuitem +>Anpassa Rosegarden...</guimenuitem +></menuchoice +> och välj "Synkronisera" i menyn för JACK överföringsläge på sidan Musikbehandlare under fliken Synkronisering.</para> + + <para +>När överföring med JACK används, delar alla program som prenumererar på den en gemensam styrning av överföringen, och du kan starta, stoppa och förflytta överföringen från vart och ett av dem.</para> + + <para +>Många ljudprogram under Linux som använder ljudservern JACK stöder också överföring med JACK. Titta i deras dokumentation för detaljinformation om de gör det och hur.</para> + </sect2> + <sect2 id="transport-mtc"> + <title +>MIDI-tidkod</title> + <para +>Rosegarden stöder synkronisering med MIDI-tidkod (MTC) i huvud- och slavläge. Det är särskilt användbart för att synkronisera Rosegardens överföring med en hårdvaruenhet som stöder MTC, eller med programvara som kör på andra datorer anslutna via MIDI. </para> + <para +>För att göra Rosegarden till MTC-huvudenhet, så att det styr alla MTC-slavar eller program som ansluts, gå till <menuchoice +><guimenu lang="sv" +>Inställningar</guimenu +> <guimenuitem +>Anpassa Rosegarden...</guimenuitem +></menuchoice +> och välj "MTC-huvudenhet" i menyn MIDI-tidkodsläge under fliken Synkronisering på sidan Musikbehandlare. För att göra Rosegarden till en slav, så att Rosegardens överföring automatiskt synkroniseras med inkommande MTC-händelser, välj "MTC-slav". </para> + </sect2> + </sect1> + </chapter> + + <chapter id="studio"> + <title +>Studion</title> + + <sect1 id="studio-introduction"> + <title +>Enheter, instrument och anslutningar</title> + + <para +>Rosegarden använder termen studio för att ange allt som den känner till om ljudsystemen anslutna till datorn. Det kan omfatta &MIDI;- och ljudhårdvara och annan ljudprogramvara, och omfattar information om anslutningar, inställning, &MIDI;-patchar och så vidare. Studion är inbyggd i alla kompositioner du skapar med Rosegarden.</para> + + <para +>Tre ord i terminologin är fundamentala här: <variablelist> + + <varlistentry> + <term +>Enhet</term> + <listitem> + <para +>En <quote +>enhet</quote +>, så vitt det angår Rosegarden, är helt enkelt något som kan skapa ljud. Det kan vara en MIDI- eller ljudenhet. MIDI-enheter motsvarar inte nödvändigtvis direkt med fysiska MIDI-portar: De är bara saker med namn som du kan ange, som förväntas fungera på ett visst sätt. Inställningsinformation som MIDI-patchavbildningar kan anslutas till enheter. </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>Instrument</term> + <listitem> + <para +>Varje enhet har ett antal <quote +>instrument</quote +>, där vart och ett antas låta på ett visst sätt. Detta är det du kan tilldela spår till för att välja vilket ljud de spelar. Normalt innehåller en enhet 16 instrument, som skapas åt dig vid start. Om enheten är en MIDI-enhet, initieras vart och ett av dem till en av de 16 MIDI-kanalerna. Instrumentet är stället där du anger alla egenskaper för en viss stämma, som programinställningar, eko, volym, etc. </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>Anslutning</term> + <listitem> + <para +>Även om en MIDI-enhet helt enkelt är ett namn och en samling inställningsinformation, anger <quote +>anslutningen</quote +> vilken MIDI-port som den är fysiskt ansluten till. Det kan ställas in i <link linkend="studio-device-editor" +>MIDI-enhetshanteringen</link +>. (Ljud- och syntinsticksmodulenheter har inte anslutningar på samma sätt). </para> + </listitem> + </varlistentry> + </variablelist> + </para> + + <para +>Tänk dig exempelvis en konfiguration som består av en dator med två fysiska MIDI-portar, där den ena har en extern synt ansluten. Då skulle du normalt ställa in Rosegarden att ha en MIDI-enhet, som motsvarar synten. Du skulle därefter kunna ställa in enheten med rätt namn och patchavbildning, och ange en anslutning för den som motsvarar ljudkortets verkliga MIDI-port. Vart och ett av de 16 standardinstrumenten på enheten skulle kunna anpassas med ett lämpligt program, och därefter skulle du tilldela spår till dem.</para> + + <para +>I praktiken försöker Rosegarden normalt skapa en enhet för var och en av de tillgängliga anslutningarna vid start. Så med exemplet ovan skulle två MIDI-enheter normalt skapas även om du bara behöver en. Du skulle därefter i allmänhet byta namn på och ange patchavbildningar för den första, och ta bort eller helt enkelt inte använda den andra. Kom ihåg att det finns inget sätt för Rosegarden att veta vilka syntar som du verkligen har anslutit till MIDI-portarna på datorn. Av denna anledning är enheterna som skapas vid start bara avsedda som en standarduppsättning, och det är upp till dig att försäkra dig om att enheterna du ställer in stämmer med de du verkligen använder. </para> + + <para +>Så fort den är inställd, lagras studioinställningen med varje fil på Rosegarden-format som du sparar.</para> + + </sect1> + + <sect1 id="studio-device-editor"> + <title +>Hantering av MIDI-enheter</title> + + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-devicemanager.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>MIDI-enhetshantering</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + + <para +>Dialogrutan för MIDI-enhetshantering visar de MIDI-enheter som för närvarande är tillgängliga, och var de är anslutna. Använd <menuchoice +><guimenu lang="sv" +>Komposition</guimenu +> <guimenuitem +>Studio</guimenuitem +> <guimenuitem +>Hantera MIDI-enheter</guimenuitem +></menuchoice +> för att nå dialogrutan. </para> + + <para +>Som beskrivs i avsnittet <link linkend="studio-introduction" +>Enheter, instrument och anslutningar</link +>, försöker Rosegarden normalt tillhandahålla en rimlig uppsättning enheter vid start, och göra rimliga anslutningar för enheterna. Standarduppsättningen kanske dock inte alltid är lämplig, och därför låter dialogrutan dig byta namn på enheter och ändra deras anslutningar och uppspelnings- eller inspelningsriktningar. </para> + + <para +>Var och en av uppspelningsenheterna här tillhandahåller en utgång för MIDI-spår att skicka till: Om du lägger till en ny uppspelningsenhet, får du 16 nya instrument i enheten som du kan tilldela spår till. Om du därefter tilldelar en anslutning till enheten, spelas spåren som har tilldelats till den på lämplig kanal (beroende på instrumentet) i vilken MIDI-synt som helst som är kopplad till anslutningen. </para> + + <para +>Inspelningsenheterna som listas här representerar möjliga källor för att spela in MIDI. Du kan göra en eller flera av dem aktuella (så att Rosegarden lyssnar på den vid inspelning) med kryssrutorna på varje rad, som visas i dialogrutan. </para> + + </sect1> + + <sect1 id="studio-bank-editor"> + <title +>Hantera banker och program för MIDI-enheter</title> + + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-bankeditor.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>Editorn för MIDI-banker och program</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + + <para +>Kom ihåg att varje MIDI-enhet innehåller ett antal instrument, och att du kan tilldela spår till instrumenten. Med MIDI-terminologi, motsvarar varje instrument en enskild kanal i MIDI-synten. Du kan välja vilken av de tillgängliga stämmorna (ljuden) i synten som varje instrument använder, men för att göra det måste du tala om namnen på alla tillgängliga stämmor för Rosegarden. </para> + + <para +>Den här dialogrutan låter dig tilldela programbanker (namn på stämmor) till MIDI-enheter, och på så sätt låta varje instrument i en enhet att ställas in att använda en av stämmorna i <link linkend="segment-view-instrumentparameterbox" +> instrumentparameterrutan</link +>. </para> + + <para +>Det vanliga sättet att ställa in programnamn för en enhet är att helt enkelt importera dem från en av enhetsfilerna (".rgd") som tillhandahålls. För att göra det, markera en enhet i listan till vänster i dialogrutan, klicka därefter på importknappen under listan och välj .rgd-filen som motsvarar din synt. </para> + + <para +>Om det inte finns en aktuell .rgd-fil tillgänglig för din synt, kan du använda dialogrutan för att skapa en ny bank. För att göra det måste du hitta programavbildningen i din synts MIDI-implementeringsdiagram och skriva in namnen för hand: Därefter kan du exportera dem till en .rgd-fil att dela med andra användare av Rosegarden. Kontakta e-postlistan rosegarden-user om du har skapat en ny .rgd-fil och vill bidra med den. (Det är hur alla befintliga .rgd-filer har kommit att inkluderas med Rosegarden: andra användare har bidragit dem.) </para> + + <sect2 id="studio-keymappings"> + <title +>Tonavbildningar för slagverk</title> + + <para +>Många MIDI-syntar har åtminstone ett slagverksprogram, där varje "tonhöjd" spelar ett annorlunda ljud. Rosegarden innehåller en särskild matriseditor för slagverk för att visa och redigera toner med en skala som består av de riktiga namnen på tonhöjderna, istället för den konventionella tonskalan på ett piano. </para> + + <para +>Tonavbildningarna som är tillgängliga för en viss MIDI-synt definieras också i Rosegardens enhetsfil (".rgd"). Varje MIDI-program som definieras som ett slagverksprogram kan ha en tillhörande tonavbildning. Om det finns en, används den normalt för alla spår som tilldelas programmet. Liksom program och bankdefinitioner kan tonavbildningar importeras från och exporteras till .rgd-filer. </para> + </sect2> + + <sect2 id="studio-soundfonts"> + <title +>Ljudteckensnitt</title> + + <para +>Om du råkar använda en programvarusynt eller ljudkortssynt som använder ljudteckensnittsfiler (.sf2), kan du helt enkelt ladda riktiga programnamn direkt från .sf2-filen i dialogrutan. Begär bara import som vanligt, och välj därefter .sf2-filen som du använder istället för en .rgd-fil. </para> + + <para +>Observera att studion bara hanterar information om befintliga MIDI-enheter i Rosegarden. Den hanterar inte uppgifter som att ladda ett ljudteckensnitt till ljudkortet från början. Om du vill försäkra dig om att ett ljudteckensnitt laddas till ljudkortet när Rosegarden startas, ska du använda det speciella alternativet "Ladda ljudsamplingar till Soundblaster-kort vid start" i inställningen av musikbehandlaren under <menuchoice +><guimenu lang="sv" +>Inställningar</guimenu +> <guimenuitem +>Anpassa Rosegarden...</guimenuitem +></menuchoice +>. </para> + </sect2> + + <sect2 id="studio-variations"> + <title +>Varianter</title> + + <para +>Vissa MIDI-enheter (till exempel de från Roland) organiserar programnamn på ett sätt som kallas "varianter". För dessa enheter vill man i allmänhet välja ett program genom att först ange ett grundprogramnamn, som ett piano, och därefter ange en av ett antal varianter av programmet, som ett elektriskt piano. Detta skiljer sig från syntar baserad på generell MIDI, som organiserar programmen i banker och förväntar sig att du först väljer en bank och därefter ett program i banken. </para> + + <para +>Rosegarden kan stödja enheter som använder varianter, men du måste ändå skriva in programnamnen med bankformat. Internt använder enheter med variationer fortfarande styrning med val av MIDI-bank för att välja bland variationerna: Du måste ta reda på om enheten använder mest signifikant eller minst signifikant värde i bankväljaren för att ange variationer, och vilket banknummer som motsvarar vilken variant. Därefter kan du skriva in bankerna som vanligt, och använda alternativet "Visa variantlista baserad på Mest signifikant värde/Minst signifikant värde" i bankdialogrutan för att tala om för Rosegarden att varianter istället för banker ska visas när enheten visas i en instrumentparameterruta. </para> + </sect2> + + <sect2 id="studio-midi-import"> + <title +>Programavbildning vid &MIDI;-import</title> + <para +>När du importerar en &MIDI;-fil till en komposition, använder &rosegarden; befintlig studioinställning för att avgöra hur &MIDI;-programmen avbildas på &rosegarden;-instrument. Målet är att försäkra att varje &MIDI;-program avbildas på ett instrument som verkligen finns i studion (och alltså verkligen är anslutet till datorn), så att alla &MIDI;-spår kan höras. </para +><para +>&MIDI; programändrings- och bankvalshändelserna som hittas i den importerade filen används vid import, men bara som en hjälp att hitta lämpligt instrument för varje &MIDI;-spår bland instrumentuppsättningen i studion. Om studion till exempel för närvarande är inställd att bara innehålla <acronym +>GM</acronym +>-instrument, och du importerar en &MIDI;-fil som innehåller <acronym +>GS</acronym +>-programändringar, avbildar &rosegarden; <acronym +>GS</acronym +>-bankerna tillbaka till <acronym +>GM</acronym +> eftersom de är allt som den vet om att du har vid tiden då filen importeras. Den kommer inte ihåg ursprungliga <acronym +>GS</acronym +>-programnummer. </para +><para +>Det här betyder att du alltid ska försäkra dig om att din studio är riktigt inställd för enheterna som du verkligen har, innan du importerar &MIDI;-filen. Annars kan programdata i &MIDI;-filen gå förlorad. </para> + </sect2> + </sect1> + + <sect1 id="studio-audio-routing"> + <title +>Ljudfördelning</title> + <para +>Alla spår i Rosegarden som tilldelas till ett ljudinstrument eller syntinsticksmodulinstrument blir en del av Rosegardens ljudfördelningsarkitektur. Det finns 16 ljudinstrument och 16 syntinsticksmodulinstrument, och vart och ett av dem har en uppsättning justerbara parametrar som omfattar toningsnivå, panorering, effekter och så vidare. De är i allmänhet inställningsbara i <link linkend="segment-view-instrumentparameterbox" +>instrumentparameterrutan</link +> eller <link linkend="studio-audio-mixer" +>ljudmixern</link +>. Varje ljudinstrument har också en ingångsanslutning, och både ljudinstrument och syntinsticksmodulinstrument har en utgångsanslutning. </para> + + <para +>Ett instruments ingångsanslutning definierar varifrån Rosegarden läser ljuddata vid inspelning till instrumentet. Den vanligaste inställningen är en av Rosegardens externa ljudingångar, vars antal kan ställas in i <link linkend="studio-audio-mixer" +>ljudmixern</link +>. De motsvarar JACK ljudportar exponerade av Rosegarden, där du kan ansluta utgångar från vilket JACK ljudprogram som helst eller från någon av ljudkortets portar med ett externt JACK fördelningsprogram som <ulink url="http://qjackctl.sf.net/" +>QJackCtl</ulink +>. Du kan också ställa in ett instruments ljudingång till en av Rosegardens inbyggda delnivåutgångar eller huvudutgångar för ihopmixningar. </para> + <para +>Ett instruments utgångsanslutning definierar var ljudet tar vägen när det spelas upp. Instrumentens normalinställning är att skicka ljud till Rosegardens huvudutgång, som är en annan extern JACK port (eller ett par portar vid stereo), som därefter kan anslutas genom att använda samma externa JACK fördelningsprogram. Rosegarden stöder dock också upp till åtta interna delutgångsbussar, dit du kan skicka utdata från instrument istället, för att gruppera instrument i samhörande kategorier. Du kan styra antalet och fördelningen av dem i <link linkend="studio-audio-mixer" +>ljudmixern</link +>. </para> + <para +>Rosegarden stöder för närvarande effekter med en uppsättning effektplatser som infogas innan toningen för varje ljudinstrument. Du kan ännu inte tilldela effekter till delnivåbussarna, och Rosegarden stöder ännu inte att skicka effekter, även om du kan uppnå liknande resultat genom att använda JACK externa effekter och mixningsarkitektur. </para> + <para +>Några ytterligare detaljer angående inställning av ljudfördelning, mixning och effekter beskrivs i avsnitten <link linkend="studio-audio-mixer" +> ljudmixern</link +>, <link linkend="segment-view-instrumentparameterbox" +>instrumentparameterrutan</link +> och <link linkend="studio-plugins" +>ljudinsticksmoduler</link +>.</para> + </sect1> + + <sect1 id="studio-audio-mixer"> + <title +>Ljudmixern</title> + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-audiomixer.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>&rosegarden;s ljudmixer</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + + <para +>Rosegardens ljudmixningsfönster, som visas med <menuchoice +><guimenu lang="sv" +>Komposition</guimenu +> <guimenuitem +>Studio</guimenuitem +> <guimenuitem +>Ljudmixer</guimenuitem +></menuchoice +>, liknar en ljudmixer i hårdvara och tillhandahåller ett sätt att se och ändra tillståndet för ett antal ljudinstrument på en gång. Den innehåller många likadana knappar som finns i ljud- och syntinsticksmodulernas <link linkend="segment-view-instrumentparameterbox" +> instrumentparameterrutor</link +>, där de viktigaste är mätaren av uppspelningsnivå och toningskontroll för varje ljudinstrument och syntinsticksmodulinstrument, samt fördelningskontroll, panorering, mono/stereo och platser för effektinsticksmoduler. </para> + <para +>Ljudmixerfönstret är också platsen där du ser och styr huvudljudnivån (längst till höger i bilden ovan), samt inspelningsnivån (till vänster om huvudtoningen) och delutnivåer. </para> + <para +>Menyn <menuchoice +><guimenu lang="sv" +>Inställningar</guimenu +></menuchoice +> i ljudmixern är särskilt relevant. Förutom att styra vad som visas i mixerfönstret, innehåller menyn också inställningen av <link linkend="studio-audio-routing" +>ljudfördelningen</link +> för antalet ljudinspelningsingångar i stereo som är tillgängliga och för antalet delnivåutgångar. De är studioinställningar som sparas med din Rosegarden formatfil.</para> + + <para +>Observera att om du i själva verket inte använder några delnivåer (dvs. om det inte finns några instrument som är inställda att skicka sin utsignal till en delnivå) kan du se en liten prestandaförbättring om du uttryckligen ställer in antalet delnivåer till inga, istället för att behålla oanvända i inställningen. </para> + </sect1> + + <sect1 id="studio-midi-mixer"> + <title +>MIDI-mixern</title> + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-midimixer.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>&rosegarden;s MIDI-mixer</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + <para +>Rosegardens MIDI-mixningsfönster, som visas med <menuchoice +><guimenu lang="sv" +>Komposition</guimenu +> <guimenuitem +>Studio</guimenuitem +> <guimenuitem +>MIDI-mixer</guimenuitem +></menuchoice +>, tillhandahåller ett sätt att se och redigera <link linkend="segment-view-instrumentparameterbox-midi" +>instrumentparametervärden</link +> för ett antal MIDI-instrument på en gång.</para> + + <para +>Fönstret är organiserat som en ruta med flikar. Längs nederkanten ser du en flik för varje MIDI-uppspelningsenhet i studioinställningen. När en enhetsflik väljes, uppdateras resten av fönstret för att visa knapparna för enhetens 16 instrument. </para> + + <para +>Knapparna som visas för varje instrument är de som ställts in i hanteringen av styrparametrar, samt volym (som motsvarar ändring av MIDI-volymstyrningen, inte en MIDI-ljudstyrka eller ljudnivå i decibel) och en ungefärlig utnivåindikator. </para> + </sect1> + + <sect1 id="studio-plugins"> + <title +>Ljudinsticksmoduler</title> + <para +>En ljudinsticksmodul är en programvarumodul, skild från Rosegarden, men som Rosegarden kan ladda och använda för att utföra en viss ljudbehandlingsuppgift. De kan grovt delas upp i effektinsticksmoduler och syntinsticksmoduler. Effektinsticksmoduler tar ljudindata och behandlar det för att skapa annorlunda ljudutdata. Rosegarden använder Linux-standarden LADSPA för effektinsticksmodulernas programmeringsgränssnitt, och DSSI för syntinsticksmodulernas programmeringsgränssnitt, vilket gör det möjligt att använda ett stort antal insticksmoduler med öppen källkod som gjorts tillgängliga av många utvecklare. </para> + <para +>Användning av insticksmoduler ger en kostnad i processortid, eftersom ljudbehandling i realtid oftast kräver en väsentlig mängd arbete till och med med en modern processor. Det ger också en potentiell kostnad i tillförlitlighet: När Rosegarden kör en insticksmodul, och insticksmodulen hänger sig eller kraschar, så gör Rosegarden också det. Många insticksmoduler är mycket tillförlitliga, men det är oundvikligt att vissa inte är så vältestade. </para> + <sect2 id="studio-plugins-effects"> + <title +>Effektinsticksmoduler</title +> <para +>En effektinsticksmodul är något som du kan använda för att ändra en ljudsignal på ett styrbart sätt. Exempel omfattar eko, fördröjningseffekter, dynamisk komprimering och så vidare. </para> + <para +>Varje ljud- eller syntinsticksmodulinstrument i Rosegarden har fem tillhörande effektplatser. Normalt är de tomma, men du kan ladda insticksprogram i dem för att bilda en kedja med upp till fem effekter för ljudsignalen innan den går igenom toningsnivå och panoreringsbehandling.</para> + + <para +>För att ladda en insticksmodul på en plats, klicka på dess knapp i <link linkend="segment-view-instrumentparameterbox-audio" +>instrumentparameterrutan</link +>: </para> + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-pluginbuttons.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>Insticksplatsknappar</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + <para +>(Dessa knappar är också alternativt tillgängliga i <link linkend="studio-audio-mixer" +>ljudmixerns fönster</link +>.) </para> + <para +>Att klicka på en insticksmodulknapp visar insticksmoduldialogrutan. Den visar tillgängliga effektkategorier i den första menyn. Markera en, så kan du därefter välja insticksmodul i den andra menyn. </para> + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-plugin-dialog.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>En insticksdialogruta i &rosegarden;</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + + <para +>Under menyerna för val av insticksmoduler, har dialogrutan ett varierande antal vridbara rattar som visar alla parametrar som kan ändras för insticksprogrammet du har valt. För att ändra ett värde, klicka bara på en ratt och dra uppåt och neråt, eller vänster och höger. (Uppåt eller åt höger för att öka värdet, neråt eller åt vänster för att minska det.) Du kan också rulla mushjulet för att ändra värdet, eller klicka med musens mittenknapp för att återställa det till det ursprungliga normalvärdet.</para> + + <para +>Det är också möjligt att kopiera en insticksmodul med sin nuvarande inställning till en annan plats, för att använda samma insticksmodulinställningar för mer än ett instrument, eller för att basera en insticksmodulinställning på en annan. Klicka bara på knappen Kopiera när du har ställt in insticksmodulen som du vill ha den, och öppna därefter dialogrutan för en annan insticksmodulplats och klicka på Klistra in.</para> + + <para +>Till sist kan du använda åtgärden Förbikoppla för att tillfälligt ta bort en insticksmodul från behandlingen, men ändå behålla dess inställning. </para> + </sect2> + <sect2 id="studio-plugins-synths"> + <title +>Syntinsticksmoduler</title> + <para +>Syntinsticksmoduler kan användas istället för MIDI-enheter i hårdvara eller fristående programvarusyntar, för att skapa ljud från segmenten med tonhändelser.</para> + + <para +>Att använda en syntinsticksmodul ger dig något bättre kontroll och upprepningsbarhet än att använda en extern MIDI-enhet, eftersom Rosegarden kan ladda rätt insticksmodul åt dig och använda riktiga inställningar nästa gång du laddar samma fil. Insticksmoduler kan också ge bättre tidsupplösning än externa MIDI-enheter, och syntinsticksmodulinstrument har fördelen att vara fördelningsbara som ljudinstrument, vilket också betyder att du kan lägga till effektinsticksmoduler ovanför dem. </para> + + <para +>För att använda en syntinsticksmodul, <link linkend="segment-view-instruments" +>tilldela först ett spår</link +> till ett syntinsticksmodulinstrument, och ladda därefter en syntinsticksmodul genom att klicka på den översta knappen i <link linkend="segment-view-instrumentparameterbox-synth" +>instrumentparameterrutan</link +>:</para> + + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-synthpluginbuttons.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>Syntinsticksmodulknappar</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + + <para +>Det här visar samma insticksmoduldialogruta som visas ovan för effektinsticksmoduler, men med en lista över syntinsticksmoduler istället för effekter. Återigen visas den särskilda uppsättning med vridbara parametrar för synten du har valt. Syntinsticksmoduler kan också ha "program" som kan väljas i en meny. Menyn visas bara om du har valt en synt som stöder det. När du har valt och ställt in en syntinsticksmodul för ett instrument, ska all MIDI-data på spår som tilldelas till det instrumentet spelas via synten, liksom inkommande MIDI-data under inspelning eller övervakning. </para> + </sect2> + + <sect2 id="studio-plugins-guis"> + <title +>Egna redigeringsfönster i en insticksmodul</title> + + <para +>De flesta insticksmoduler kan styras helt och hållet med rattarna i Rosegardens insticksmoduldialogruta. Dock har några få insticksmoduler (i allmänhet syntar) också sina egna redigeringsfönster som kan aktiveras eller inaktiveras från Rosegarden, och som kan tillhandahålla fullständigare eller bättre organiserade knappar.</para> + + <para +>När du väljer en insticksmodul som har sitt eget redigeringsfönster, aktiveras knappen nere till vänster i insticksmodulens dialogruta som heter "Editor":</para> + + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-plugineditorbutton.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>Redigeringsknappen i en insticksmodul</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + + <para +>(För syntinsticksmoduler finns en liknande knapp i instrumentparameterrutan.) Att klicka på knappen visar insticksmodulens eget redigeringsfönster. Alla ändringar som du gör i redigeringsfönstret ska också synas i Rosegardens egen insticksmoduldialogruta, och ska naturligtvis sparas i din Rosegarden-fil som vanligt.</para> + </sect2> + </sect1> + + <sect1 id="studio-metronome"> + <title +>Metronomer</title> + <para +>Rosegarden har två inbyggda metronomer, en för användning under inspelning och en som kan kopplas in under normal uppspelning. De fungerar genom att skicka toner till ett MIDI-instrument, och båda metronomerna använder samma instrument, tonhöjds- och ljudstyrkeinformation. </para> + + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-metronome.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>&rosegarden;s inställningsdialogruta för metronom</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + <para +>För att ställa in metronomerna, använd <menuchoice +><guimenu lang="sv" +>Komposition</guimenu +> <guimenu lang="sv" +>Studio</guimenu +> <guimenuitem +>Hantera metronom</guimenuitem +></menuchoice +> för att visa metronomdialogrutan. Här kan du välja ett MIDI-instrument för metronomen och välja metronomens upplösning (om den ska ticka en gång per taktslag, en gång per underavdelning av ett taktslag, eller bara en gång per takt), tonhöjd och ljudstyrkor. Egenskaper som själva stämman som MIDI-synten använder för metronomens tick beror på instrumentet som väljes, precis som stämman för ett MIDI-spår beror på instrumentet som spåret är tilldelat till. Du kan ställa in instrumentet genom att tilldela ett spår till det i huvudfönstret och välja rätt program från instrumentparameterrutan. </para> + + <para +>Metronomerna för inspelning och uppspelning kan aktiveras eller inaktiveras från överföringsfönstret genom att använda metronomknappen. Knappen styr inspelningsmetronomen när inspelning är förberedd eller pågår, och annars uppspelningsmetronomen. Normalt är inspelningsmetronomen aktiverad och uppspelningsmetronomen inaktiverad. </para> + + <para +>Rosegarden har också en "visuell metronom": Överföringsfönstret kan ställas in att blinka starkt för att markera varje taktslag. Se avsnittet om <link linkend="transport" +>överföringen</link +> för mer detaljinformation.</para> + </sect1> + + <sect1 id="studio-midi-filters"> + <title +>MIDI-filter</title> + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-midifilter.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>MIDI-filterdialogrutan</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + + <para +>Genom att använda den här dialogrutan kan du bestämma vilka MIDI-händelser som Rosegarden ignorerar eller accepterar, antingen när händelser skickas vidare med MIDI THRU, eller helt enkelt när de spelas in. Använd kryssrutorna för att tala om för Rosegarden vilka typer av MIDI-händelser som du inte vill skicka vidare eller spela in. </para> + + </sect1> + + + <sect1 id="studio-external-controllers"> + <title +>Externa MIDI-styrenheter</title> + <para +>Rosegardens ljud- och MIDI-mixningsfönster samt huvudfönstret kan också i viss mån styras av en extern MIDI-enhet. För att ställa in det, måste du använda ett ALSA MIDI-anslutningsprogram som qjackctl för att ansluta MIDI-styrenheten till Rosegardens "externa styringång" och MIDI-utgångarna. </para> + <para +>Rosegarden tar emot MIDI-styrändringsmeddelanden för att justera mixerspåret som motsvarar den inkommande MIDI-kanalen vid varje styrenhetshändelse, och skickar också ut MIDI-meddelanden när något ändras i ett mixerspår för att stödja styrenheter med motoriserade skjutreglage eller knappar. </para> + <para +>Rosegarden tar emot MIDI-styrenhet nummer 81 för att ändra fönstret som för närvarande är aktivt. Skicka styrenhet 81 med datavärdet 0-9 för att välja huvudfönstret, 10-19 för att välja ljudmixerfönstret eller 20-29 för att välja MIDI-mixerfönstret.</para> + <para +>Rosegarden tar emot MIDI-styrenhet nummer 82 för att ändra spår som för närvarande är markerat i huvudfönstret. Stegningen av styrenheten beror på antal spår i fönstret: förhållandet mellan styrenhetens datavärde till spårnummer beräknas så att det fullständiga dataintervallet i MIDI-styrenheten används, under förutsättning att det inte finns mer än 128 spår i fönstret.</para> + </sect1> + + </chapter> + + + <chapter id="segment-instrument-parameters"> + <title +>Segment- och instrumentparametrar</title> + + <sect1 id="segment-view-segmentparameterbox"> + <title +>Segmentparameterrutan</title> + + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-segmentparameterbox.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>&rosegarden;s segmentparameterruta</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + + <para +>Segmentparameterrutan hör hemma till vänster i Rosegardens huvudfönster. (Om du inte kan se den, försök använda <menuchoice +><guimenu lang="sv" +>Inställningar</guimenu +> <guimenuitem +>Visa segment- och instrumentparametrar</guimenuitem +></menuchoice +>.) Den låter dig ändra vissa aspekter av markerade segment.</para +><para +>Om ett enstaka segment för närvarande är markerat, visas dess parametrar i segmentparameterrutan och kan redigeras där. Om flera segment är markerade, visar parameterrutan bara nuvarande värden där de är samma för alla markerade segment, men du kan fortfarande redigera dem och ändringarna gäller för allt som är markerat. <variablelist> + <varlistentry> + <term +>Namn</term> + <listitem> + <para +>Visar namnet på det markerade segmentet (eller segmenten, om alla har samma namn). Klicka på knappen "..." för att redigera namnet.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>Upprepa</term> + <listitem> + <para +>Stänger av eller sätter på upprepning för markerade segment. Ett upprepande segment upprepas till efterföljande segment börjar i samma spår, eller till kompositionens slut om det inte finns något efterföljande segment.</para> + + <para +>Upprepade delar av ett upprepande segment visas med en svagare färg på huvudduken än det ursprungliga segmentet. Du kan ändra dem till riktiga redigerbara kopior av det ursprungliga segmentet genom att antingen använda <menuchoice +><guimenu lang="sv" +>Segment</guimenu +> <guimenuitem +>Omvandla upprepningar till kopior</guimenuitem +></menuchoice +>, eller genom att helt enkelt dubbelklicka på enskilda upprepade block.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>Kvantisera</term> + <listitem> + <para +>Visar kvantiseringsinställningen för markerade segment. Du kan ändra den för att snabbt kvantisera starttider för alla deras toner. För mer avancerad kvantisering, använd <menuchoice +> <guimenu lang="sv" +>Segment</guimenu +> <guimenuitem +>Kvantisera...</guimenuitem +> </menuchoice +>. Se <link linkend="quantization" +>Kvantisering</link +> för mer detaljinformation. </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>Transponera</term> + <listitem> + <para +>Visar transponeringen (i halvtonssteg) som för närvarande används för det markerade segmentet. Transponeringen utförs när segmentet spelas upp, och visas inte med noterna i matris-, not- eller händelseeditorerna. Du kan använda den för att snabbt ändra tonhöjd för en del eller hela kompositionen.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>Fördröjning</term> + <listitem> + <para +>Visar fördröjningen som för närvarande gäller för markerade segment. Du kan ställa in en fördröjning här för att göra att ett helt segment spelas upp senare än skrivet. Fördröjningen utförs när segmentet spelas upp, och visas inte med noterna i matris-, not- eller händelseeditorerna. </para> + <para +>Du kan antingen ange en fördröjning med metronomtid (genom att välja notvärde i fördröjningskombinationsrutan), då fördröjningens exakta tid beror på tempot, eller med klocktid (genom att välja tiden i millisekunder i kombinationsrutan). </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>Färg</term> + <listitem> + <para +>Visar färgen som används för att visa markerade segment. Du kan välja en annan färg i kombinationsrutan, eller välja alternativet "Lägg till ny färg" om du vill ha en färg som inte finns i kombinationsrutan. </para> + <para +>Du kan också hantera och byta namn på färger genom att använda <menuchoice +><guimenu lang="sv" +>Komposition</guimenu +> <guimenuitem +>Redigera dokumentegenskaper...</guimenuitem +></menuchoice +> (och därefter välja sidan Färg i dialogrutan med dokumentegenskaper). Den ändrade färgpaletten sparas med kompositionen i Rosegarden-filen. <screenshot +> <mediaobject> + <imageobject> + <imagedata fileref="rg-colours.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>&rosegarden;s färghantering</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + </listitem> + </varlistentry> + + </variablelist> + </para> + </sect1> + + <sect1 id="segment-view-instrumentparameterbox"> + <title +>Instrumentparameterrutan</title> + <para +>Instrumentparameterrutan finns i nedre vänstra hörnet av Rosegardens huvudfönster, nedanför <link linkend="segment-view-segmentparameterbox" +>segmentparameterrutan</link +>. (Om du inte kan se den, försök använda <menuchoice +><guimenu lang="sv" +>Inställningar</guimenu +> <guimenuitem +>Visa segment- och instrumentparametrar</guimenuitem +></menuchoice +>.)</para> + + <para +>Den visar vilka instrument som tilldelats nuvarande markerat spår, och innehåller alla redigerbara knapparna för instrumentet. Kom ihåg att eftersom hur många spår som helst kan tilldelas till samma instrument, kan inställningarna i rutan påverka mer än ett spår åt gången.</para> + + <para +>Utseendet och innehållet i instrumentparameterrutan beror på instrumenttypen: MIDI, ljud eller syntinsticksmodul. </para> + + <sect2 id="segment-view-instrumentparameterbox-midi"> + <title +>MIDI-instrumentparametrar</title> + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-ipb-midi.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>&rosegarden;s instrumentparameterruta för ett MIDI-instrument</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + <para +>När du markerar ett spår som är tilldelat till ett MIDI-instrument, visar instrumentparameterrutan MIDI-parametrar. </para> + <para +>Längst upp visar rutan instrumentets namn och anslutningen som dess enhet använder. </para> + <para +>Därunder kan du se och redigera MIDI-kanalnumret och inställningar av <link linkend="studio-bank-editor" +>bank och program</link +> som ska skickas till instrumentet vid uppspelningens start (inklusive kryssrutan "Slagverk" som styr om bara slagverksprogram ska erbjudas i inställningarna).</para> + + <para +>Till sist visar rutan tillgängliga styrenheter för enheten (de för en generell MIDI-enhet visas ovan). Alla inställningar som du gör här skickas till instrumentets kanal vid uppspelningens start.</para> + </sect2> + + <sect2 id="segment-view-instrumentparameterbox-audio"> + <title +>Ljudinstrumentparametrar</title> + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-ipb-audio.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>&rosegarden;s instrumentparameterruta för ett ljudinstrument</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + <para +>När du markerar ett ljudspår, visar instrumentparameterrutan ljudparametrar. </para> + <para +>Rutan har två huvudtoningar, en omgiven av blått för uppspelning och den andra omgiven av rött för inspelningsnivå vid inspelning till instrumentet. Mellan dem finns en mätare av uppspelningsnivå. </para> + <para +>De två menyerna längst upp i rutan används för att välja ingångs- och utgångsfördelning för instrumentet. Under dem kan du välja om instrumentet är mono eller stereo, och panoreringsinställning för plats i stereofältet. (Ljudinstrument är alltid till sist stereo, eftersom panoreringsinställningen alltid tillämpas. Men om du ställer in instrumentet till mono, reduceras all ljuddata och effektutdata till mono innan panoreringen tillämpas.) </para> + <para +>Kolumnen med fem knappar längst ner till vänster är effektplatserna. Klicka på dem för att välja och aktivera insticksmoduler för ljudinstrumentet, och för att styra dem med redigeringsdialogrutan för insticksmoduler. Detta är infogade effekter, som utförs i ordning uppifrån och ner innan toning och panorering. </para> + </sect2> + + <sect2 id="segment-view-instrumentparameterbox-synth"> + <title +>Instrumentparametrar för syntinsticksmoduler</title> + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-ipb-synth.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>&rosegarden;s instrumentparameterruta för ett syntinsticksmodulinstrument</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + <para +>När du markerar ett spår som är tilldelat till ett syntinsticksmodulinstrument, visar instrumentparameterrutan syntparametrar. Du märker att även om en syntinsticksmodul använder segment med MIDI-data, så beter den sig mer som ett ljudspår när det gäller styrning och fördelning. </para> + <para +>Den viktigaste knappen här är den längst upp till vänster (som lyder Xsynth i bilen ovan), som visar namnet på syntinsticksmodulen som används för instrumentet. Klicka på den för att välja en viss synt och styra den i Rosegardens vanliga redigeringsdialog för insticksmoduler. När du väl har valt en insticksmodul, kanske du också kan klicka på redigeringsknappen nedanför för att öppna en dedicerad grafisk editor för den särskilda insticksmodulen (om insticksmodulen har någon). </para> + <para +>Återstående knappar här är samma som för ljudinstrument: Uppspelningstoning, uppspelningsnivå, utgångsfördelning, mono/stereo, panoreringsinställningar och effektplatser är alla exakt likadana.</para> + </sect2> + + </sect1> + </chapter> + + <chapter id="quantization"> + <title +>Kvantisering</title> + <para +>"Kvantisering" är processen att flytta toner och andra händelser så att de börjar eller avslutas på exakta taktdelar. Det används traditionellt för att göra ett ungefärligt utförande till ett precist men som låter ganska mekaniskt, antingen på grund av att precision är önskad effekt, eller på grund av orsaker som att göra noter tydligare i notering. </para> + + <para +>För allmän kvantisering, använd <menuchoice +><guimenu lang="sv" +>Segment</guimenu +> <guimenuitem +>Kvantisera</guimenuitem +></menuchoice +> i huvudfönstret eller <menuchoice +><guimenu lang="sv" +>Justera</guimenu +> <guimenuitem +>Kvantisera</guimenuitem +></menuchoice +> i matriseditorn eller notbehandlarna. Det visar en dialogruta där du kan välja precis de kvantiseringsparametrarna du behöver, och tillämpar dem på alla markerade segment eller toner. (Du kan också snabbt nå dialogrutan genom att trycka på tangenten "=".) </para> + + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-gridquantizer.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>&rosegarden;s kvantiseringsdialogruta</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + + <para +>Kvantiseringsdialogrutan erbjuder ett urval kvantiseringsmetoder, var och en med sin egen uppsättning parametrar. Tillgängliga kvantiseringsmetoder är: </para> + <variablelist> + + <varlistentry> + <term +>Rutnätskvantisering</term> + <listitem> + <para +>Rutnätskvantiseringen flyttar starttider för toner så att de börjar på den närmaste punkten i ett rutnät (definierat av de olika parametrarna för kvantiseringen). På så sätt justeras toner som ursprungligen varierar något i starttid av kvantiseringen, vilket ger ett mer precist och mekaniskt utförande. </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>Legato-kvantisering</term> + <listitem> + <para +>Legato-kvantiseringen utför en enkel rutnätskvantisering, och justerar också notvärdena så att eventuella avstånd mellan tonerna tas bort genom att förlänga varje not så att den (åtminstone) fortsätter till början på nästa. Du kan också få denna legato-effekt utan tillhörande rutnätskvantisering med funktionen <menuchoice +><guimenu lang="sv" +>Justera</guimenu +> <guimenuitem +>Kvantisera</guimenuitem +> <guimenuitem +>Legato</guimenuitem +></menuchoice +> i matriseditorn. </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>Heuristisk kvantisering</term> + <listitem> + <para +>Kvantiseringen försöker justera starttider och notvärden för toner så att en läsbar notering skapas. Se <link linkend="nv-quantization" +>Notskrift från utförandedata</link +> för en beskrivning av kvantiseringen och dess användning.</para> + </listitem> + </varlistentry> + + </variablelist> + + <para +>Rutnätskvantiseringen har följande justerbara parametrar:</para> + <variablelist> + + <varlistentry> + <term +>Grundenhet för rutnät</term> + <listitem> + <para +>Det här är storleken på rutnätet som används för kvantiseringen. </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>Svaj</term> + <listitem> + <para +>Det här är ett procenttal som justerar graden som alternerande taktslag kvantiseras "sent".</para> + <para +>Om inställt till inget (förvalt värde), görs kvantiseringen till ett jämt rutnät med avstånd enligt grundenheten för rutnätet.</para> + <para +>Om inställd till 100 %, placeras varannan rutnätslinje två tredjedelar av avståndet mellan föregående och nästa, istället för halvvägs. Det gör att toner kvantiseras till första och tredje triolen med en svajig takt. </para> + <para +>Övriga inställningar ger proportionellt varierande grad av svaj. Du kan också ställa in parametern till negativa värden (för att omväxlande taktslag ska börja tidigare) eller till värden större än 100 %.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>Itereringsvärde</term> + <listitem> + <para +>Rutnätskvantiseringens normalbeteende är att exakt flytta varje not till den närmaste rutnätslinjen, men om du ställer in iterationsgränsen till något som är mindre än 100 % (normalvärdet "Fullständig kvantisering") flyttas varje not bara den procentandelen av avståndet till närmaste rutnätslinje, vilket resulterar i en kvantiseringseffekt som nästan utförs, men inte helt och hållet.</para> + <para +>Kvantiseringen kan utföras upprepade gånger, för att pröva gradvis ökande kvantiseringsgrader, därav namnet "iterativ". Använd <menuchoice +><guimenu lang="sv" +>Justera</guimenu +> <guimenuitem +>Kvantisera</guimenuitem +> <guimenuitem +>Upprepa senaste kvantisering</guimenuitem +></menuchoice +> i matriseditorn för att göra det. </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>Kvantisera både notvärden och starttider</term> + <listitem> + <para +>Om det här alternativet är aktiverat, kvantiseras tonernas sluttider till samma rutnät som deras starttider. </para> + </listitem> + </varlistentry> + </variablelist> + + <para +>Kvantiseringsdialogrutan har också en valfri avancerad sektion som innehåller ytterligare alternativ för <link linkend="nv-quantization" +>kvantisering</link +>. </para> + + <para +>Ett annat enkelt sätt att utföra en rutnätskvantisering är att göra den i huvudfönstret med menyn <guimenuitem +>Kvantisera</guimenuitem +> i <link linkend="segment-view-segmentparameterbox" +>segmentparameterrutan</link +>. Om du markerar några segment och ändrar värdet som visas i menyn, blir segmenten omedelbart rutnätskvantiserade till upplösningen som visas i menyn. </para> + + <para +>Till sist finns också en <link linkend="matrix-grid-quantize" +>styrning av kvantisering</link +> i matrisvyn.</para> + + </chapter> + + <chapter id="matrix-view"> + <title +>Matriseditorn</title> + <para +>&rosegarden;s matriseditor låter dig visa och redigera musik med ett enkelt logiskt format: Varje not representeras som ett block i ett rutnät, på en plats som motsvarar tonhöjden. </para> + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-matrixview.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>&rosegarden;s matriseditor</phrase> + </textobject> + </mediaobject> +</screenshot +> Varje fönster i matriseditorn visar ett enstaka segment. För att redigera ett segment, högerklicka bara på det på huvudduken och välj matriseditorn i menyn. Alternativt kan du ställa in Rosegarden att göra matriseditorn till standardvy som är tillgänglig genom att dubbelklicka på ett segment. </para> + + <sect1 id="matrix-grid-quantize"> + <title +>Styrning av rutnät och kvantisering</title> + <para +>Matrisvyn innehåller menyerna Rutnät och Kvantisering i huvudmenyraden. </para> + <para +>Rutnätsmenyn styr det synliga rutnätets storlek i matrisvyns bakgrund, samt tidsupplösningen som används när noter skrivs in och flyttas. Efter du har ställt in det till ett visst tidsvärde, låses de normala åtgärderna för att infoga och dra noter automatiskt till rutnätspunkter åtskilda med det tidsvärdets bredd. Du kan överskrida positioneringsfunktionen tillfälligt genom att hålla nere Skift under redigeringen, eller inaktivera den genom att ställa in rutnätsmenyn till Ingen låsning. </para> + <para +>Kvantiseringsmenyn fungerar på ett ganska annorlunda sätt. I stället för att styra beteendet hos andra redigeringsverktyg, utför den verkligen en åtgärd. När du ändrar värde i menyn, blir de markerade noterna, eller hela segmentet om ingenting är markerat, omedelbart kvantiserade av en rutnätskvantisering med vald upplösning. </para> + <para +>Kvantiseringsmenyn visar också kontinuerligt vilken upplösning som det nuvarande segmentet eller markeringen är kvantiserad med. Om du till exempel markerar en uppsättning noter som börjar på efterföljande kvartsnotstaktslag, uppdateras kvantiseringsmenyn så att 1/4 visas, eftersom det är den grövsta upplösningen som motsvarar den befintliga kvantiseringen av nuvarande markering. </para> + </sect1> + + <sect1 id="matrix-insertion"> + <title +>Infoga noter</title> + <para +>Det enklaste sättet att mata in en not i matrisvyn är att använda musen. För att göra det, välj pennverktyget i verktygsraden, klicka och dra därefter i matriseditorn. Noten matas in vid tiden och med tonhöjden som motsvarar punkten du klickar, och har ett notvärde som motsvarar avståndet du drar innan du släpper musknappen.</para> + + <para +>Normalt är tiden och notvärdet låsta till en viss rutnätsenhet enligt rutnätsinställningarna i menyn Visa eller verktygsraden. Du kan förhindra effekten genom att hålla nere Skift medan du klickar och drar. </para> + + <sect2 id="matrix-insertion-keyboard"> + <title +>Skriva in noter med datorns tangentbord</title> + + <sect3> + <title +>Notvärde</title> + + <para +>Notvärden för noter som matas in via tangentbordet styrs av rutnätsinställningarna i menyn Visa eller verktygsraden . Du kan ställa in det genom att använda de numeriska tangenterna:</para> + + <itemizedlist> + <listitem +><para +><keycap +>5</keycap +> – Hel takt</para +></listitem> + <listitem +><para +><keycap +>1</keycap +> – Takt</para +></listitem> + <listitem +><para +><keycap +>2</keycap +> – Halvnot</para +></listitem> + <listitem +><para +><keycap +>4</keycap +> – Kvartsnot</para +></listitem> + <listitem +><para +><keycap +>8</keycap +> – Åttondedelsnot</para +></listitem> + <listitem +><para +><keycap +>6</keycap +> – Sextondedelsnot</para +></listitem> + <listitem +><para +><keycap +>3</keycap +> – Trettioandredelsnot</para +></listitem> + <listitem +><para +><keycap +>0</keycap +> – Sextifjärdedelsnot</para +></listitem> + </itemizedlist> + + </sect3> + + <sect3> + <title +>Tonhöjd</title> + + <para +>Så fort rätt notvärde är vald i rutnätsmenyn kan du infoga en not på <link linkend="nv-rulers" +>infogningsmarkörens</link +> aktuella position genom att trycka på en av tonhöjdstangenterna:</para> + + <itemizedlist> + <listitem +><para +><keycap +>A</keycap +> – C (Do, tonikan i aktuell tonart för aktuell klav) </para +></listitem> + <listitem +><para +><keycap +>S</keycap +> – D (Re)</para +></listitem> + <listitem +><para +><keycap +>D</keycap +> – E (Mi)</para +></listitem> + <listitem +><para +><keycap +>F</keycap +> – F (Fa)</para +></listitem> + <listitem +><para +><keycap +>J</keycap +> – G (So)</para +></listitem> + <listitem +><para +><keycap +>K</keycap +> – A (La)</para +></listitem> + <listitem +><para +><keycap +>L</keycap +> – H (Ti)</para +></listitem> + </itemizedlist> + + <para +>Genom att hålla nere <keycap +>Skift</keycap +> när en tangent trycks, fås en upphöjd not (utom för E och H som inte har upphöjda versioner) och genom att hålla nere <keycap +>Skift</keycap +> och <keycap +>Ctrl</keycap +> tillsammans fås en nersänkt not (utom för F och C).</para> + + <para +>För att skriva in noter en oktav högre,använd motsvarande tangenter på nästa rad ovanför: <keycap +>Q</keycap +>, <keycap +>W</keycap +>, <keycap +>E</keycap +>, <keycap +>R</keycap +>, <keycap +>U</keycap +>, <keycap +>I</keycap +> och <keycap +>O</keycap +>. På motsvarande sätt, för att lägga till noter en oktav lägre, använd <keycap +>Z</keycap +>, <keycap +>X</keycap +>, <keycap +>C</keycap +>, <keycap +>V</keycap +>, <keycap +>B</keycap +>, <keycap +>N</keycap +> och <keycap +>M</keycap +>.</para> + + </sect3> + + <sect3> + <title +>Övriga anmärkningar</title> + + <para +>Alla infogningskommandon är också tillgängliga från en undermeny i menyn Verktyg. Det är inte troligt att du någonsin vill navigera i menyn bara för att infoga en enstaka not, men menyerna visar snabbtangenterna och tillhandahåller på så sätt en användbar referens om du skulle glömma vilken tangent som gör vad.</para> + + <para +>Snabbtangenterna är för närvarande gjorda för att användas med tangentbord som har QWERTY-organisation. Det finns ännu inte något sätt att ändra snabbtangenter till en annan organisation, förutom att individuellt ändra tilldelning av varje tangent med <menuchoice +><guimenu lang="sv" +>Inställningar</guimenu +> <guimenuitem +>Anpassa genvägar...</guimenuitem +></menuchoice +>.</para> + + </sect3> + + </sect2> + + <sect2 id="matrix-insertion-midi"> + <title +>Skriva in noter genom att använda ett MIDI-keyboard</title> + + <para +>Du kan lägga till noter i matriseditorn en i taget med ett MIDI-keyboard eller en annan MIDI-styrenhet. Matriseditorn använder tonhöjden du spelar på ett keyboard, men de notvärden du har valt i editorns egna rutnätsinställningar. Det är känt som "stegvis inspelning". </para> + + <para +>För att börja mata in noter från ett MIDI-keyboard, försäkra dig först om att det är inställt som förvald MIDI-inspelningsenhet. Försäkra dig därefter om att du har rätt rutnätsinställning i menyn Visa eller på verktygsraden, eftersom det styr notvärdena. Tryck därefter på knappen för stegvis inspelning i matriseditorns verktygsrad, eller välj Stegvis inspelning i menyn Verktyg. Från detta ögonblick infogas alla toner som du spelar på ditt MIDI-keyboard vid den nuvarande inmatningstiden i fönstret, ända till stegvis inspelning stängs av igen, aktiveras i ett annat fönster eller fönstret stängs. </para> + + <para +>Du kan ändra rutnätsinställningar medan stegvis inspelning pågår, för att infoga noter med olika notvärden. </para> + </sect2> + </sect1> + + <sect1 id="matrix-selection"> + <title +>Markera noter</title +> <para +>För att markera noter i matriseditorn, byt till markeringsverktyget (pilen) och rita upp ett rektangulärt område som innehåller noterna du vill markera. Markerade händelser färgläggs då i blått. Om du istället klickar på en enstaka händelse, markeras bara den händelsen. </para +><para +>Om du håller nere <keycap +>Skift</keycap +> medan du ritar upp en rektangel eller klickar på en not, läggs den nya markeringen till i en eventuell befintlig markering istället för att ersätta den. </para> + + <para +>För att rensa en markering, klicka på ett tomt område i matriseditorn eller tryck på Esc-tangenten.</para> + + <para +>Du kan också markera alla noter av en viss tonhöjd genom att skift-klicka på en tangent på pianoklaviaturen längs vänster sida i matriseditorn. Du kan också skift-klicka och dra för att markera en uppsättning tonhöjder. Markeringen läggs till i en eventuell befintlig markering, så om du vill ha en helt ny markering, avmarkera först den föregående. </para> + </sect1> + + <sect1 id="matrix-editing"> + <title +>Flytta och kopiera noter</title> + <para +>Du kan flytta noter både i tid och tonhöjd i matriseditorn genom att antingen klicka och dra dem med förflyttningsverktyget, eller markera dem och därefter dra dem med markeringsverktyget. </para> + <para +>För att kopiera noter, markera dem och använd därefter de vanliga funktionerna kopiera och klistra in. Efter de har klistrats in är de inklistrade noterna markerade istället, och du kan dra dem var du än vill ha dem. </para> + </sect1> + + </chapter> + + <chapter id="percussion-matrix-view"> + <title +>Slagverksmatriseditorn</title> + + <para +>Slagverksmatriseditorn är identisk med <link linkend="matrix-view" +>matriseditorn</link +>, förutom att den visar tonhöjdsnamn på den vertikala skalan istället för pianotangenter, och att den inte visar notvärdet för varje not. Den är avsedd för användning med slagverksprogram i MIDI-instrument, där varje tonhöjd spelar ett annorlunda slagverksljud.</para> + + <para +>Se också <link linkend="studio-keymappings" +>Tonavbildningar för slagverk</link +>.</para> + </chapter> + + <chapter id="notation-view"> + <title +>Notbehandlaren</title> + + <!-- Introduction, purpose --> + + <sect1 id="nv-introduction"> + <title +>Inledning</title> + + <para +>&rosegarden;s notbehandlare gör det möjligt att visa och redigera ett eller flera notsystem med traditionell partiturnotation. </para +><para> + + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-notationview.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>&rosegarden;s notbehandlare</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + <para +>&rosegarden; försöker presentera partitur med bästa möjliga utläggning givet dess huvudsakliga fokus som en musikbehandlare. Det betyder att även om editorn stöder ackord, överlappande och nästlade balkgrupper, trioler och godtyckliga annandelningar, prydnadsnoter, dynamik, accenter, text och så vidare, tillhandahåller den inte så mycket detaljkontroll över utläggningen (särskilt i musik med kontrapunkt) som särskilda program för redigering av partitur kan göra. &rosegarden; har inte som mål att skapa partitur av typsättningskvalitet, även om Lilypond-filer kan exporteras, vilka kan utgöra en bra grund för typsättning. </para> + </sect1> + + <!-- Single and multiple staffs, and "current staff" --> + + <sect1 id="nv-staffs"> + <title +>Enkla och flera notsystem</title> + + <para +>Det finns tre sätt att öppna en notbehandlare i &rosegarden;s huvudfönster. (Alla kräver att du först har ett befintligt segment i huvudfönstret, så om du påbörjar en ny komposition, bör du skapa dina segment innan du börjar fundera på hur de ska redigeras.) <variablelist> + + <varlistentry> + <term +>Dubbelklicka på segment</term> + <listitem> + + <para +>Det mest uppenbara sättet är att dubbelklicka på ett segment på huvudduken. Det öppnar segmentet i den editor som du har ställt in som standardvy (not, matris eller händelselista), som normalt är notbehandlaren. Alltså öppnas ett segment som ett enskilt notsystem i notbehandlarens fönster genom att dubbelklicka på det.</para> + + <para +>Du kan också öppna en editor med flera notsystem på följande sätt: Håll nere Skift-tangenten, markera (med ett enda musklick) alla segment i huvudvyn som du vill öppna, men dubbelklicka på det sista. Alla markerade segment öppnas då tillsammans i ett enda fönster i notbehandlaren.</para> + + </listitem> + </varlistentry> + + <varlistentry> + <term +>Funktionen Öppna i standardvy (returtangenten)</term> + <listitem> + + <para +>Returtangenten är en snabbtangent för menyfunktionen att öppna i standardvyn, som gör i stort sett samma sak som att dubbelklicka: Den öppnar alla segment som för närvarande är markerade i notbehandlaren, eller i någon annan editor som du har ställt in som standardvy. </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>Menyfunktionerna Öppna i notbehandlare</term> + <listitem> + + <para +>Som ett alternativ kan du använda huvudfönstrets menyalternativ Öppna i notbehandlare, antingen i menyn Segment eller i menyn som visas med höger musknapp över ett segment på duken. Markera segmenten du vill redigera (genom att skift-klicka som ovan, eller genom att använda alternativet Markera alla segment) och välj därefter Öppna i notbehandlare.</para> + </listitem> + + </varlistentry> + </variablelist> + + </para> + + <para +>Om du har mer än ett notsystem (dvs. segment) synligt i notbehandlaren kan bara ett av dem vara "aktuellt" på en gång. Det aktuella notsystemet kan urskiljas eftersom infogningsmarkören visas i det (se <link linkend="nv-rulers" +>Linjaler och markörer</link +>), och det är notsystemet där alla redigeringsåtgärder som använder infogningsmarkören äger rum. Det översta notsystemet är normalt det aktuella, men du kan byta till ett annat notsystem genom att Ctrl-klicka på det eller genom att använda menyalternativen Markör upp notsystem och Markör ner notsystem. </para> + + </sect1> + + <!-- Linear and page layouts --> + + <sect1 id="nv-layout"> + <title +>Horisontell och sidbaserad utläggning</title> + + <para +>Det vanliga sättet som notbehandlaren visar notsystem är känt som horisontell utläggning: Notsystem ovanför varandra, med varje notsystem som en enda, horisontell rullande lång rad. Vissa funktioner i editorn (som <link linkend="nv-rulers" +>linjalerna</link +>) är bara tillgängliga med horisontell utläggning. </para> + + <para +>Du kan dock också visa notsystem med två olika sidbaserade utläggningar: Vertikal utläggning eller Sidutläggning.</para> + + <para +>I vertikal utläggning visas noteringen på en oändligt hög sida med samma bredd som fönstret. Varje notsystem bryts vid radens slut, och påbörjar en ny rad under återstående notsystem.</para> + + <para +>I sidutläggning visas noteringen uppdelad på riktiga sidor i stort sett som den ser ut när den skrivs ut. Varje sidas storlek beräknas så att ungefär samma antal noter får plats på varje rad som när det verkligen skrivs ut (enligt punktstorleken som anges för utskriftsupplösningen i inställningsdialogrutan). Den utskrivna versionen är troligen inte precis likadan, eftersom det beror på den exakta pappersstorleken och marginalerna som används vid utskrift, men det bör vara ganska nära om du råkar använda A4-papper.</para> + + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-notationview-multipage.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>&rosegarden;s notbehandlare med sidutläggning</phrase> + </textobject> + </mediaobject> + </screenshot> + </para +><para +>De flesta, men inte alla, av visnings- och redigeringsfunktionerna fungerar lika bra i sidutläggningslägena som i horisontell utläggning. </para> + + <para +>För att byta mellan utläggningslägen, använd menyalternativen Horisontell utläggning, Vertikal utläggning och Sidutläggning. </para> + </sect1> + + <!-- Rulers and Cursors --> + + <sect1 id="nv-rulers"> + <title +>Linjaler och markörer</title> + + <para +>&rosegarden;s notredigeringsfönster innehåller två linjaler och två markörer. Linjalerna är de horisontella raderna uppdelade med graderingar längst upp och längst ner på huvudnoteringsduken, och markörerna är de färgade vertikala linjerna som ursprungligen visas i början av det översta notsystemet i editorn. </para> + + <para +>Den violetta markören är infogningsmarkören. Den visar platsen där åtgärder som infoga och klistra in utförs. Du kan flytta infogningsmarkören genom att klicka eller dra på den övre linjalen, eller genom att klicka med markeringsverktyget på en tom del av notsystemet (och undvika alla händelser), eller genom att klicka var som helst med <keycap +>Ctrl</keycap +> intryckt. </para> + + <para +>Du kan också använda vänster och höger piltangenter för att flytta infogningsmarkören en händelse i taget. Om du håller nere <keycap +>Ctrl</keycap +> medan piltangenterna trycks, flyttas markören en hel takt åt gången. Om du håller nere Skift, <link linkend="nv-tools-selections" +>markeras händelserna</link +> medan markören rör sig över dem. </para> + + <para +>Den blåa markören är uppspelningsmarkören. Precis som liknande markörer i huvudfönstret och matrisvyn, visar den platsen för nuvarande uppspelning eller inspelning. Den kan förflyttas genom att använda linjalen längst ner. </para> + + <para +>Observera att linjalerna bara visas i läget <link linkend="nv-layout" +>Horisontell utläggning</link +>. </para> + + </sect1> + + <!-- Display conventions (annotated picture with some selected notes, + some quantized notes, a bar of incorrect length etc) --> + + <!-- Tools and Selections --> + + <sect1 id="nv-tools-selections"> + <title +>Verktyg och markeringar</title> + <para +>De flesta redigeringsfunktioner i menyer och verktygsrader i &rosegarden;s notbehandlare ingår i en av tre kategorier: <quote +>verktyg</quote +>, <quote +>funktioner som arbetar med markeringar</quote +> och <quote +>dragåtgärder</quote +>. </para> + + <variablelist> + <varlistentry> + <term +>Verktyg</term> + <listitem> + <para +>De grundläggande verktygen är markeringsverktyget, borttagningsverktyget och de som används för att infoga noter, pauser, text och så vidare, vilka oftast väljes med knappar i verktygsraden. Att välja ett verktyg ändrar det normala beteendet hos musknapparna på huvudnoteringsduken, åtminstone till ett annat verktyg väljes istället. Genom att till exempel välja markeringsverktyget kan du göra markeringar och på så sätt använda de markeringsbaserade funktionerna (nedan). Genom att välja ett infogningsverktyg (som en av noterna) ändras det grafiska gränssnittets beteende så att noter infogas genom att klicka på duken. Genom att välja borttagningsverktyget gör att du kan ta bort händelser genom att klicka på dem. </para> + <para +>Du kan också byta aktuellt verktyg med menyn Verktyg. </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>Funktioner som arbetar med markeringar</term> + <listitem> + <para +>Flertalet återstående menyalternativen kräver att en markering görs på duken innan de kan användas. Vissa av dem (såsom alternativen <guimenuitem +>Klipp ut</guimenuitem +> eller <guimenuitem +>Notstil</guimenuitem +>) fungerar på alla händelser som markerats. Andra (såsom <guimenuitem +>Prydnadsnot</guimenuitem +> eller <guimenuitem +>Skaftriktning</guimenuitem +>) vägrar fungera om inte markeringen innehåller några noter. </para> + <para +>För att markera några händelser på duken, byt till markeringsverktyget (pilen) och rita därefter upp ett rektangulärt område som innehåller händelserna du vill markera. De markerade händelserna färgläggs då med blått. Om du klickar på en enskild händelse, markeras bara den händelsen <footnote +> <para +> Du kan också dubbelklicka på en enskild händelse för att visa en redigeringsdialogruta för händelsen, men det har ingenting att göra med markeringar.</para +> </footnote +>). </para +><para +>Om du håller nere <keycap +>Skift</keycap +> medan du ritar upp en rektangel, läggs innehållet till i en eventuell befintlig markering istället för att ersätta den. </para> + <para +>För att markera en hel takt, dubbelklicka med markeringsverktyget på ett tomt utrymme i takten. För att markera hela notsystemet, klicka tre gånger. Redigeringsmenyn innehåller alternativ för att markera utökade områden baserat på infogningsmarkörens plats, och du kan också markera händelser omkring infogningsmarkören genom att hålla nere Skift och trycka på vänster eller höger piltangent. </para> + <para +>Det är inte möjligt att markera händelser i mer än ett notsystem på en gång. </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>Dragåtgärder</term> + <listitem> + <para +>Du kan också utföra en viss mängd redigering genom att bara dra omkring saker. Byt till markeringsverktyget (pilen), och därefter kan du ändra tonhöjd på noter genom att bara klicka och dra deras huvuden uppåt eller neråt, och ändra tider för noter och andra händelser genom att dra dem åt vänster eller höger. (Du kan inte dra pauser eller taktarter, men du kan dra allting annat. Om du har markerat mer än en händelse, dras hela markeringen på en gång.) </para> + <para +>Att dra är oftast ett mindre noggrant sätt att redigera än att använda funktionerna i menyn eller verktygsraden, men det kan vara enklare. </para> + </listitem> + </varlistentry> + </variablelist> + </sect1> + + <!-- Insertion: notes, auto-ties, accidentals --> + + <sect1 id="nv-insertion"> + <title +>Infoga noter och pauser</title> + + <para +>För att infoga en not, välj ett av notverktygen genom att klicka på ett visst notvärde i verktygsraden, och därefter klicka i notsystemet på platsen där du vill lägga till noten.</para> + + <para +>Du kan också markera en av de tillfälliga förtecknen på verktygsraden för att infoga upphöjda eller nersänkta noter. Om inget tillfälligt förtecken används, följer den infogade noten de fasta förtecknen. Som ett alternativ kan du välja ikonen "Följ föregående tillfälliga förtecken" (som visas som en not med en pil som pekar tillbaka från stället där förtecknet skulle visas) för att få noten att följa det tillfälliga förtecken som senast användes på samma plats i notsystemet.</para> + + <para +>Om du lägger till en not på samma tid som en befintlig not med annat notvärde, antar editorn i allmänhet att du vill skapa ackord och delar upp den befintliga eller nya noten på motsvarande sätt för att skapa ett eller flera bundna ackord. Om du verkligen vill skapa ett ackord med två olika notvärden, kan du markera de bundna nothuvudena och använda funktionen Lägg ihop noter med samma tonhöjd för att lägga ihop dem. Som ett alternativ kan det förvalda beteendet ändras in &rosegarden;s inställningsdialogruta, så att uppdelningen inte alls görs.</para> + + <para +>Om du lägger till en not exakt ovanpå en befintlig not med annorlunda notvärde (dvs. på samma tonhöjd), ändras notvärdet på den befintliga noten till det nya notvärdet.</para> + + <para +>Om du lägger till en paus på exakt samma tid som en befintlig not, blir den befintliga noten tyst under pausvärdet, vilket förkortar den eller möjligen tar bort den helt och hållet.</para> + + <sect2 id="nv-insertion-keyboard"> + <title +>Skriva in noter och pauser med datorns tangentbord</title> + + <sect3> + <title +>Notvärde</title> + + <para +>Försäkra dig först om att ett notverktyg är valt för att ange notvärdet (eller pausvärdet) som du vill infoga. Du kan välja de olika nottyperna genom att använda nummertangenterna:</para> + + <itemizedlist> + <listitem +><para +><keycap +>5</keycap +> – Brevis</para +></listitem> + <listitem +><para +><keycap +>1</keycap +> – Helnot</para +></listitem> + <listitem +><para +><keycap +>2</keycap +> – Halvnot</para +></listitem> + <listitem +><para +><keycap +>4</keycap +> – Kvartsnot</para +></listitem> + <listitem +><para +><keycap +>8</keycap +> – Åttondedelsnot</para +></listitem> + <listitem +><para +><keycap +>6</keycap +> – Sextondedelsnot</para +></listitem> + <listitem +><para +><keycap +>3</keycap +> – Trettioandredelsnot</para +></listitem> + <listitem +><para +><keycap +>0</keycap +> – Sextifjärdedelsnot</para +></listitem> + </itemizedlist> + + <para +>Du kan byta till en triolversion av notvärdet genom att trycka på tangenten <keycap +>G</keycap +>. Genom att trycka på den igen byter du tillbaka till normalt notvärde. Statusraden längst ner i fönstret underrättar dig om att ett triolvärde är aktivt.</para> + </sect3> + + <sect3> + <title +>Tonhöjd</title> + + <para +>Så fort ett notverktyg är valt, kan du infoga en not på <link linkend="nv-rulers" +>infogningsmarkörens</link +> aktuella position genom att trycka på en av tonhöjdstangenterna:</para> + + <itemizedlist> + <listitem +><para +><keycap +>A</keycap +> – C (Do, tonikan i aktuell tonart för aktuell klav)</para +></listitem> + <listitem +><para +><keycap +>S</keycap +> – D (Re)</para +></listitem> + <listitem +><para +><keycap +>D</keycap +> – E (Mi)</para +></listitem> + <listitem +><para +><keycap +>F</keycap +> – F (Fa)</para +></listitem> + <listitem +><para +><keycap +>J</keycap +> – G (So)</para +></listitem> + <listitem +><para +><keycap +>K</keycap +> – A (La)</para +></listitem> + <listitem +><para +><keycap +>L</keycap +> – H (Ti)</para +></listitem> + </itemizedlist> + + <para +>Tryck på tangenten "." för att växla mellan notvärden med eller utan punkt.</para> + + <para +>Genom att hålla nere <keycap +>Skift</keycap +> när en tangent trycks, fås en upphöjd not (utom för E och H som inte har upphöjda versioner) och genom att hålla nere <keycap +>Skift</keycap +> och <keycap +>Ctrl</keycap +> tillsammans fås en nersänkt not (utom för F och C).</para> + + <para +>För att skriva in noter en oktav högre,använd motsvarande tangenter på nästa rad ovanför: <keycap +>Q</keycap +>, <keycap +>W</keycap +>, <keycap +>E</keycap +>, <keycap +>R</keycap +>, <keycap +>U</keycap +>, <keycap +>I</keycap +> och <keycap +>O</keycap +>. På motsvarande sätt, för att lägga till noter en oktav lägre, använd <keycap +>Z</keycap +>, <keycap +>X</keycap +>, <keycap +>C</keycap +>, <keycap +>V</keycap +>, <keycap +>B</keycap +>, <keycap +>N</keycap +> och <keycap +>M</keycap +>.</para> + + </sect3> + + <sect3> + <title +>Pauser</title> + + <para +>För att infoga en paus istället för en not, tryck på <keycap +>P</keycap +>. Som ett alternativ kan du använda tangenterna <keycap +>T</keycap +> och <keycap +>Y</keycap +> för att byta aktuellt verktyg till ett pausverktyg och tillbaka till ett notverktyg igen.</para> + + </sect3> + + <sect3> + <title +>Ackord</title> + + <para +>Normalbeteendet i notbehandlaren är att flytta infogningsmarkören framåt efter en not har infogats, så att den är klar att mata in en ny not på efterföljande plats i en melodi. Det kan ändras med tangenten <keycap +>H</keycap +>, som byter till ackordsläge så att efterföljande inmatning sker samtidigt som den senaste. Att trycka på <keycap +>H</keycap +> igen byter tillbaka till inmatningsbeteende för melodi.</para> + + </sect3> + + <sect3> + <title +>Ändra notvärden</title> + + <para +>Du kan använda tangentbordet för att ändra notvärden som du redan har skrivit in. Försäkra dig om att noterna du vill ändra är markerade, och tryck därefter på <keycap +>Ctrl</keycap +> samt nummertangenten för noten som du vill ha. Du kan också lägga till eller ta bort punkter, genom att trycka <keycap +>Ctrl</keycap +> och ".". Använd det upprepade gånger för att välja mellan en punkt, två punkter eller ingen punkt.</para> + + <para +>Om du håller nere <keycap +>Alt</keycap +> samt <keycap +>Ctrl</keycap +>, ändrar du notvärden som de visas i notbehandlaren utan att ändra utfört notvärde. Det kan vara mycket användbart för att städa upp ett partitur: Se också <link linkend="nv-quantization" +>Notskrift från utförandedata</link +>. </para> + </sect3> + + <sect3> + <title +>Övriga anmärkningar</title> + + <para +>Alla infogningskommandon är också tillgängliga från en undermeny i menyn Verktyg. Det är inte troligt att du någonsin vill navigera i menyn bara för att infoga en enstaka not, men menyerna visar snabbtangenterna och tillhandahåller på så sätt en användbar referens om du skulle glömma vilken tangent som gör vad.</para> + + <para +>Snabbtangenterna är för närvarande gjorda för att användas med tangentbord som har QWERTY-organisation. Det finns ännu inte något sätt att ändra snabbtangenter till en annan organisation, förutom att individuellt ändra tilldelning av varje tangent med alternativet "Anpassa genvägar..." i menyn Inställningar.</para> + + <para +>Genom att hålla nere <keycap +>Ctrl</keycap +> vid tryck på en nummertangent väljes motsvarande verktyg med punkt.</para> + + </sect3> + + </sect2> + + <sect2 id="nv-insertion-midi"> + <title +>Skriva in noter genom att använda ett MIDI-keyboard</title> + + <para +>Du kan lägga till noter i notbehandlaren en i taget med ett MIDI-keyboard eller en annan MIDI-styrenhet, en process som är känd som "stegvis inspelning". Notbehandlaren använder tonhöjden du spelar på ett keyboard, men de notvärden du har valt i själva editorn. </para> + + <para +>För att börja mata in noter från ett MIDI-keyboard, försäkra dig först om att det är inställt som förvald MIDI-inspelningsenhet. Försäkra dig därefter om att ett notverktyg är valt för att ange ett notvärde. Tryck därefter på knappen för stegvis inspelning i notbehandlarens verktygsrad, eller välj Stegvis inspelning i menyn Verktyg. Från detta ögonblick infogas alla toner som du spelar på ditt MIDI-keyboard vid den nuvarande inmatningstiden i noteringsfönstret, ända till stegvis inspelning stängs av igen, aktiveras i ett annat fönster eller fönstret stängs. </para> + + <para +>Du kan välja ett annat notverktyg medan stegvis inspelning pågår för att infoga noter med olika notvärden, och du kan också byta till ackordläge för att infoga ackord. </para> + </sect2> + + </sect1> + + <!-- Keys, Clefs and Time Signatures --> + + <sect1 id="nv-signatures"> + <title +>Klav och tonart</title> + +<!-- !!! rework --> + <para +>Det första man måste veta om hur &rosegarden; hanterar dessa är att tidsrelaterade ändringar (tempo och taktarter) hanteras helt annorlunda än klaver och tonarter. För att förenkla hantering av uppspelning och inspelning samt notering, kräver &rosegarden; att när tempo eller taktart ändras, görs det i alla notsystem på en gång. Du kan inte låta ett notsystem använda 3/4 medan ett annat samtidigt använder 4/4, eller ha ett notsystem som spelar med 120 taktslag och ett annat med 90. Det gäller bara tid: Det finns inga sådana begränsningar för användning av klav- och tonartsbyten.</para> + + <para +>För att ändra klav, tonart, tempobeteckning eller taktart inne i ett fönster i notbehandlaren, placera <link linkend="nv-rulers" +>infogningsmarkören</link +> på ett ställe där du vill att ändringen ska ske, och använd en av redigeringsmenyns funktioner Lägg till klavbyte..., Lägg till tonartsbyte..., Byt tempo... eller Byt taktart... . Då visas en dialogruta där du kan välja en viss inställning för klav, tonart, tempobeteckning eller taktart som du vill använda, enligt följande.</para> + + <sect2 id="nv-signatures-clef"> + <title +>Klav</title> + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-clefdialog.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>&rosegarden;s klavdialogruta</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + + <para +>Dialogrutan låter dig välja en klav, och låter dig dessutom välja hur du vill att klaven ska användas, i fall där det redan finns några noter efter punkten där klaven ska infogas. Du måste välja något av följande: <variablelist> + + <varlistentry> + <term +>Behåll nuvarande tonhöjder</term> + <listitem> + <para +>Alla noter som följer klaven behåller sina nuvarande utförda tonhöjder. </para> + <para +>Genom att till exempel infoga en c-klav i mitten av ett avsnitt med en tidigare g-klav gör att noterna som kommer efter klaven att flyttas en oktav högre i notsystemet, eftersom de fortfarande har sina tonhöjder enligt g-klaven. </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>Transponera till lämplig oktav</term> + <listitem> + <para +>Alla noter som kommer efter klaven behåller sin tonhöjd inom oktaven, men kan flyttas till en annan oktav för att passa med den nya klaven, och spelas därför med annan tonhöjd. </para> + <para +>Genom att till exempel infoga en c-klav i mitten av ett avsnitt med en tidigare g-klav gör att noterna som kommer efter klaven bara att flyttas en linje i notsystemet för att justeras enligt den nya klaven, men spelas en oktav lägre än tidigare. </para> + </listitem> + </varlistentry> + + </variablelist> + + </para> + </sect2> + + <sect2 id="nv-signatures-key"> + <title +>Tonart</title> + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-keysigdialog.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>&rosegarden;s dialogruta för fasta förtecken</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + </sect2> + + </sect1> + + <!-- Text --> + + <sect1 id="nv-text"> + <title +>Text och sångtexter</title> + + <para +>Ett notsystem kan innehålla olika sorters text, i texthändelser. Det finns två grundläggande klasser med texthändelser: Enstaka textobjekt som används för punktnoteringar etc., och sångtexter. De förstnämnda kan skapas (och på så sätt kopplas till en viss tid i notsystemet) med textverktyget, som är tillgängligt från knappen markerad med ett stort <guilabel +>T</guilabel +> i verktygsraden. Sångtext kan också skapas på detta sätt, men skapas enklare med <link linkend="nv-text-lyrics" +>sångtexteditorn</link +>.</para> + + <para +>För att lägga till ett textstycke, välj textverktyget och klicka på stället där du vill lägga till den. En dialogruta visas, där du kan skriva in texten och välja dess tänkta syfte. (Rosegarden föredrar att lagra vad texten är till för, istället för hur. Det görs så att vi i framtiden kan ställa in hur diverse textsorter presenteras för varje individuell användare). Tillgängliga syften (eller stilar) är:</para> + + <variablelist> + + <varlistentry +><term +>Dynamik</term +><listitem +><para +>Används för mindre lokala föredragsbeteckningar som dynamikbeteckningarna "p", "mf" etc. Visas normalt under notsystemet med liten kursiv stil. </para +></listitem +></varlistentry> + + <varlistentry +><term +>Anvisning</term +><listitem +><para +>Används för att ange väsentliga ändringar i stil eller stämning. Visas normalt ovanför notsystemet med stort romerskt teckensnitt. </para +></listitem +></varlistentry> + + <varlistentry +><term +>Lokal anvisning</term +><listitem +><para +>Används för att ange mindre väsentliga ändringar i stil eller stämning. Visas normalt under notsystemet med mindre romerskt teckensnitt i fetstil. </para +></listitem +></varlistentry> + + <varlistentry +><term +>Tempo</term +><listitem +><para +>Används för att ange väsentliga ändringar av tempo. Visas normalt ovanför notsystemet med stort romerskt teckensnitt i fetstil. </para +></listitem +></varlistentry> + + <varlistentry +><term +>Lokalt tempo</term +><listitem +><para +>Används för att ange mindre viktiga eller lokala ändringar av tempo. Visas normalt ovanför notsystemet med litet romerskt teckensnitt i fetstil. </para +></listitem +></varlistentry> + + <varlistentry +><term +>Sångtext</term +><listitem +><para +>Även om sångtext oftast skapas i <link linkend="nv-text-lyrics" +>sångtexteditorn</link +>, kan de också skrivas in ord för ord om det behövs genom att använda den här stilen. Normalt visas stilen under texten med litet romerskt teckensnitt. (Varning: Om du skriver in sångtext på detta sätt och senare redigerar notsystemets sångtext med sångtexteditorn, kan all sångtext som skrivs in på detta sätt ändras eller flyttas om positionen inte stämmer med den som sångtexteditorn förväntar sig.) </para +></listitem +></varlistentry> + + <varlistentry +><term +>Anteckning</term +><listitem +><para +>Används för hjälptext som inte strikt anses tillhöra partituret. Visas normalt under notsystemet, i en gul ruta som liknar en klisterlapp. </para +></listitem +></varlistentry> + + </variablelist> + + <para +>Du kan också redigera text efter den skapats genom att klicka på den befintliga texten med textverktyget.</para> + + <sect2 id="nv-text-lyrics"> + <title +>Redigera sångtexter</title> + + <para +>Sångtexteditorn, tillgänglig från alternativet <guimenuitem +>Öppna sångtexteditor</guimenuitem +> i menyn <guimenu +>Visa</guimenu +>, låter dig redigera alla sångtexthändelser för ett enskilt notsystem på en gång, med ett ganska grundläggande textbaserat redigeringssystem. För att använda den, välj bara menyalternativet, redigera sångtexten i dialogrutan som visas, och klicka därefter på Ok.</para> + + <para +>Sångtext som du skriver in måste följa ett visst format. Taktstreck är mycket viktiga för att undvika att editorn blir förvirrad, och representeras med ett snedstreck ("/"). Inom varje takt skiljs enskilda stavelser åt med mellanslag (åtminstone ett mellanslag: editorn bryr sig inte om extra blanktecken). Varje stavelse kopplas i sin tur till nästföljande not eller ackord i takten (även om editorn för närvarande kan bli riktigt förvirrad av ackord som inte är exakta, dvs. som kräver utjämning eller kvantisering).</para> + + <para +>Om du vill att en not inte ska ha någon tillhörande stavelse, måste du använda en punkt (".") som stavelse för noten. (Det är därför standardtexten för ett segment oftast är full med punkter.) Kom ihåg att skilja punkterna åt med mellanslag, så att de tydligt är skilda stavelser.</para> + + <para +>Om du vill ha mer än en stavelse för samma not, med ett mellanslag mellan dem, använd tilde ("~") istället för mellanslag. Det visas som ett mellanslag i partituret.</para> + + <para +>Om du vill dela en stavelse mellan två noter med ett bindestreck, måste du skriva in ett mellanslag efter bindestrecket så att editorn vet att det ska behandlas som två stavelser. (Bindestreck hanteras inte speciellt inne i stavelser.)</para> + + <para +>Stavelser som bara består av siffror omgivna av hakparenteser (som "[29]") ignoreras. Det är formatet för automatiskt skapade taktnummer som visas i editorn.</para> + + <para +>Du bör också vara medveten om att textformatet för sångtext bara används för redigering: sångtexten lagras i själva verket som distinkta texthändelser (en per stavelse). Det betyder att textformatet potentiellt kan ändras i framtiden för att hantera mer avancerade redigeringsmöjligheter, även om händelseformatet inte bör ändras och sparade filer bör fortsätta att fungera.</para> + + </sect2> + + </sect1> + + <!-- Indications --> + + <sect1 id="nv-indication"> + <title +>Legatobågar och klykor</title> + + <para +>Dynamikmarkeringarna legatobågar och klykor lagras som händelser, precis som noter eller pauser. För att skapa en, markera området du vill täcka (en följd av noter eller något annat), och använd därefter alternativen <guimenuitem +>Lägg till legatobåge</guimenuitem +>, <guimenuitem +>Lägg till crescendo</guimenuitem +> eller <guimenuitem +>Lägg till diminuendo</guimenuitem +> i menyn <guimenu +>Grupp</guimenu +>.</para> + + <para +>Du kan ta bort en legatobåge eller klyka på samma sätt som alla andra händelser: Markera den antingen med markeringsverktyget och tryck därefter på <keycap +>Delete</keycap +>, eller klicka på den med borttagningsverktyget aktivt.</para> + + </sect1> + + <!-- Stem direction, slashes etc --> + + <sect1 id="nv-note-qualities"> + <title +>Notskaft och tvärbalkar</title> + + <para +>Du kan ställa in skaftriktningen på alla markerade noter (under förutsättning att de är av en sort som har skaft) med de tre skaftriktningsalternativen i menyn Noter. Alternativen låter dig antingen låsa skaften uppåt eller neråt, eller återgå till skaftriktningen som &rosegarden; annars skulle ha valt. Se också <link linkend="nv-beamed-groups" +>Balkar</link +>.</para> + + <para +>Menyn <guimenu +>Noter</guimenu +> innehåller också alternativ för att lägga till tvärbalkar på notskaft, för att till exempel ange korta upprepade noter eller trumvirvlar. De är för närvarande bara notation. &rosegarden; tar inte hänsyn till dem när notsystemet spelas upp eller när &MIDI; skapas.</para> + </sect1> + + <!-- Beamed groups, including overlapping and nesting them --> + + <sect1 id="nv-beamed-groups"> + <title +>Balkar</title> + + <para +>Att lägga till balkar till noter anses som en grupperingsåtgärd i &rosegarden;s notbehandlare, tillgänglig i menyn <guimenu +>Grupp</guimenu +>. Markera noterna du vill lägga till en balk för, och använd menyalternativet Balkar i menyn <guimenu +>Grupp</guimenu +>. För att ta bort en balk, markera noterna och använd menyalternativet <guimenuitem +>Ta bort balkar</guimenuitem +>.</para> + + <para +>Det är möjligt att ha mer än en balkgrupp som inträffar samtidigt. Du markerar och lägger bara till balkar för enskilda grupper en åt gången. Oftast är Rosegarden inte ännu smart nog för att räkna ut vilka noter som bör ha skaften uppåt och vilka som bör ha skaften neråt för grupper som samtidigt ges balkar, alltså behöver du troligen explicit ange skaftriktningar för noter i grupperna samt ge dem balkar.</para> + + <para +>&rosegarden; kan försöka att gissa lämpliga balkar för ett musikstycke, under förutsättning att det inte är alltför komplicerat. För att göra det, markera noterna du vill beräkna balkar för (till exempel genom att trippelklicka för att markera ett helt notsystem) och därefter använda alternativet <guimenuitem +>Automatiska balkar</guimenuitem +> i menyn <guimenu +>Grupp</guimenu +>. Balkar skapas också automatiskt till exempel när en &MIDI;-fil laddas, och editorn skapar också vissa balkar automatiskt när du skriver in noter (det kan stängas av genom att ändra inställningen "Lägg automatiskt till balkar om lämpligt" i inställningsdialogrutan eller infogningsverktygets meny som visas med höger musknapp).</para> + + </sect1> + + <!-- Tuplets --> + + <sect1 id="nv-tuplets"> + <title +>Trioler och andra annandelningar</title> + + <para +>En triolgrupp består av tre toner eller ackord som spelas under samma tid som två. (Mer exakt består den av toner med ett totalt notvärde av tre godtyckliga enheter, som spelas under samma tid som två av enheterna.)</para> + + <para +>Vi använder ordet <quote +>annandelning</quote +> för att beskriva det allmänna fallet då toner med ett totalt notvärde av ett givet antal enheter, spelas under en tid som anges av ett annat antal av enheterna: Nio toner under tiden för åtta, eller sex under tiden för fyra, eller en fjärdedelsnot och en åttondedelsnot under tiden för en enda fjärdedelsnot, eller till och med två toner under tiden för tre. (För närvarande stöder inte &rosegarden; det sista exemplet. Annandelningar måste alltid spelas med ett kortare notvärde än det skrivna.)</para> + + <para +>Menyfunktionerna för trioler och annandelningar fungerar genom att ta en befintlig följd av noter eller pauser och trycka ihop dem så att de spelas upp snabbare, och fylla i överblivet utrymme efter följden med en slutgiltig paus och rita upp det hela som en annandelning. Därför kan du skapa en ny följd av trioler genom att mata in de första två noterna i följden (med normal form), göra dem till trioler, och därefter fylla i utrymmet som blivit kvar efter triolåtgärden med den sista noten i triolen. Eller kan du utföra triolåtgärden innan du matar in några noter, och på så sätt omvandla den ursprungliga pausen till triolform, och därefter infoga triolens noter ovanpå den. Några exempel kan vara till hjälp:</para> + + <!-- Need examples and screenshots --> + + <!-- Then discuss general tuplet dialog... --> + + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-tupletdialog.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>&rosegarden;s allmänna dialogruta för annandelningar</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + + <para +>För att ange en allmän annandelning, måste man känna till vad grundnoten är (om man till exempel spelar tre fjärdedelsnoter under tiden för två är grundnoten en fjärdedelsnot) och förhållandet mellan antalet grundnoter som skrivs till antalet som spelas.</para> + + <!-- Then discuss "tuplet mode": with a subtitle? --> + + </sect1> + + <!-- Grace notes --> + + <!-- Paste --> + + <sect1 id="nv-paste-types"> + <title +>Inklistringstyper</title> + + <para +>Betydelsen av <quote +>klipp ut och klistra in</quote +> är inte så uppenbar för musikredigeringsprogram som den är för något som en ordbehandlare, där bokstäverna och orden anges i en enkel linjär ordning. I enlighet med det erbjuder &rosegarden;s notbehandlare flera olika typer av inklistringsåtgärder, samt separata funktioner för Klipp ut eller Klipp ut och stäng. </para> + + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-pastedialog.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>&rosegarden;s inklistringstypdialogruta</phrase> + </textobject> + </mediaobject> +</screenshot +> Typerna av inklistringsåtgärder är:</para> + + <variablelist> + + <varlistentry> + <term +>Begränsat</term> + <listitem> + <para +>Kräver ett befintligt gap (som inte innehåller något annat än pauser) med tillräckligt notvärde för att helt omfatta klippbordets innehåll. Innehållet klistras in i gapet. Om det inte finns ett gap som är långt nog, utförs inte inklistringen. </para> + <para +>Det här är förvald inklistringstyp. </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>Enkel</term> + <listitem> + <para +>Raderar tillräckligt med händelser för att skapa ett gap som är långt nog att klistra in i, och klistrar därefter in i det. De inklistrade händelserna ersätter därför fullständigt alla eventuella befintliga i tiden som täcks av inklistringen. </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>Öppna och klistra in</term> + <listitem> + <para +>Motsatsen till Klipp ut och stäng. Gör rum för det som ska klistras in genom att flytta alla efterföljande händelser längre mot kompositionens slut. </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>Överlagring av noter</term> + <listitem> + <para +>Utför en inklistring på samma sätt som skulle ske om du skrev in var och en av noterna på klippbordet själv med notbehandlaren: Om det finns andra noter som överlappar med dem, delas nya och befintliga noter i lämpliga bindebågar. </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>Matrisöverlagring</term> + <listitem> + <para +>Utför en inklistring på samma sätt som skulle ske om du skrev in var och en av noterna på klippbordet själv med matriseditorn: Noterna som för närvarande är ivägen för inklistringen ignoreras, och de nya noterna får överlappa godtyckligt med dem. </para> + </listitem> + </varlistentry> + + </variablelist> + + <para +>Alla dessa får effekt på infogningsmarkörens aktuella position i aktuellt notsystem. För att välja mellan de olika typerna av inklistring, använd menyalternativet Klistra in... (med punkter) i menyn Redigera. </para> + + </sect1> + + <sect1 id="nv-adjustments"> + <title +>Justera notering</title> + + + <sect2 id="nv-adjustments-note-rest-durations"> + <title +>Justera not- och pausvärden</title> + + <sect3 id="nv-normalize-rests"> + <title +>Normalisera pauser</title> + + <para +>Ibland kan ett notavsnitt råka ut för felaktiga pausvärden för aktuell taktart, som ett resultat av redigering eller kvantiseringsåtgärder. Du kan använda funktionen <guimenuitem +>Normalisera pauser</guimenuitem +> för att fixa dem. Funktionen undersöker varje sekvens av pauser i en följd som hittas i markeringen och justerar, delar och lägger ihop pauser enligt vad som är nödvändigt för att försäkra att pauserna har rätt teoretiskt pausvärde och hamnar på rätt gränser. </para> + + <para +>Om en 4/4-takt innehåller en fjärdedelsnot, arrangeras en halvnotspaus och en fjärdedelspaus om så att fjärdedelspausen placeras först, eftersom halvnotspausen inte ska överlappa den centrala taktgränsen i takten. </para> + </sect3> +<!-- + <varlistentry id="commands-nv-menu-transforms-make-viable"> + <term +><menuchoice> + <guimenu +>Transforms</guimenu> + <guimenuitem +>Make Notes Viable</guimenuitem> + </menuchoice +></term> + <listitem> + <para +><action +>Splits notes at displayable + durations.</action +> This function is intended to deal + with notes that have excessively long durations that + overflow barlines or that are too long to be displayed + as a single note. It takes any such notes and splits + them into shorter, tied notes. + </para> + </listitem> + </varlistentry> + + <varlistentry id="commands-nv-menu-transforms-de-counterpoint"> + <term +><menuchoice> + <guimenu +>Transforms</guimenu> + <guimenuitem +>De-Counterpoint</guimenuitem> + </menuchoice +></term> + <listitem> + <para +><action +>Turns counterpoint into a series of split-and-tied notes and chords.</action> + + &rosegarden; has no explicit support for counterpoint + (multiple lines of notes edited separately on the + same staff), but it will do its best to approximate + it when it finds notes in a segment that are + apparently contrapuntal, i.e. that overlap but that + are not precise enough to be treated as chords. For + example, when a short note starts shortly after a + longer note, Rosegarden will show the longer note + and a short <quote +>spacing</quote +> rest together, followed by the + shorter note. Unfortunately this often isn't what + you want. + </para> + + <para +>The De-Counterpoint function can be applied to a + selection that contains overlapping notes. It will + split overlapping notes at the point where they + overlap, and tie together the resulting split notes, + ensuring that the music takes the form of a series of + chords and/or single notes starting and ending in neat + blocks, with some notes possibly tied. + </para> + </listitem> + </varlistentry> + + <varlistentry id="nv-transpose"> + <title +>Transpose</title> + <para +><action +>Alters the pitch of the selected + notes.</action +> This submenu contains basic + transposition functions which move the selected notes + up or down a semitone or a whole octave in pitch, as + well as a general transpose function that allows you + to choose how far up or down you want to transpose the + selection. + </para> + + <para +>These functions simply change the stored pitches + of the notes in the selection, so that they both play + and appear at the new pitches. They do not deal with + performance transposition (displaying one pitch and + playing another), for which see the main window's + segment parameter box; nor do they help you with + transposing from one key into another, for which see + <link linkend="nv-signatures-key" +>Key + Signatures</link +>. + </para> + </varlistentry> +--> + </sect2> + </sect1> + + <sect1 id="nv-interpret"> + <title +>Tolka utförandeantydningar i notskrift</title> + <!-- !!! --> + <para +>Du kan använda tolkningsfunktionen för att ändra ljudstyrkor och tider för toner enligt eventuell skriven eller angiven dynamik som hittas. Tillgängliga val av tolkningar är följande: <variablelist> + <varlistentry> + <term +>Tillämpa dynamikbeteckningar (p, mf, ff, etc.) </term> + <listitem +><para +>Anger en ljudstyrka för varje not baserat på senaste texten av typen "Dynamik" som observerats i samma notsystem (bara text på formen pp, p, mp, mf, f, ff, fff etc känns igen). </para +></listitem> + </varlistentry> + + <varlistentry> + <term +>Använd dynamikklykor </term> + <listitem +><para +>Gör att noterna gradvis ökar eller minskar ljudstyrka under en klyka som anger crescendo eller diminuendo. </para +></listitem> + </varlistentry> + + <varlistentry> + <term +>Betona taktslag </term> + <listitem +><para +>Gör noter som hamnar på takt- eller taktslagsgränser något starkare (större ljudstyrka) än omgivande noter. </para +></listitem> + </varlistentry> + + <varlistentry> + <term +>Artikulationsbeteckningar </term> + <listitem +><para +>Avkortar noter utan legatobågar, avkortar staccato-noter ännu mer, och ger noter inne i legatobågar och tenuto-noter sina fulla notvärden. </para +></listitem> + </varlistentry> + </variablelist> + + </para> + + </sect1> + + <!-- Quantization, smoothing, and display of quantized notes --> + + <sect1 id="nv-quantization"> + <title +>Notskrift från utförandedata</title> + + <para +>&rosegarden; är ett program med flera användningsområden: Det är en notbehandlare, men det är i huvudsak en musikbehandlare och editor för utförd musik, och i utföranden är tonernas tider och notvärden naturligtvis sällan så precisa som de är i ett tryckt partitur. </para> + + <para +>Det betyder att det ofta är önskvärt för &rosegarden; att göra en hel del uppstädning av grundläggande nottider och notvärden vid försök att skapa meningsfulla noter att visa i notbehandlaren. Det är en sorts kvantisering, men en sort som kräver en förvånansvärd mängd gissningar för att göras bra. Det ingår en kvantisering i &rosegarden; som är konstruerad för att göra ett något bättre jobb än den enkla rutnätskvantiseringen. </para> + + <para +>Att använda kvantisering enbart för notskrift kallas ganska fantasilöst för <quote +>kvantisering</quote +>: Den gäller bara noterna du ser och redigerar i notskrift, och påverkar inte tonerna som spelas, eller det du redigerar i andra vyer som matrisvyn. Kvantiseringen utförs automatiskt för musik som importeras eller spelas in från MIDI, även om inte alla dess möjliga funktioner normalt är aktiverade. </para> + + <para +>Det finns två sätt att se vilka noter som har kvantiserats för notskrift. Normalt innehåller varje notvy en linjal för obehandlade noter (i gruppen med linjaler ovanför partituret) som visar ett rektangulärt block för varje not. Blocket är placerat så att det representerar tiden och notvärdet för noten som utfördes, men med rektangelns övre och nedre kant utökade eller avkortade för att representera tiden efter kvantisering. Om det är för mycket information för dig, kan du som ett alternativ välja (i inställningsdialogrutan) att visa alla nothuvuden i partituret som har ändrade tider efter kvantisering med grön färg. </para> + + <para> + + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-notationquantizer.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>&rosegarden;s kvantiseringsdialogruta</phrase> + </textobject> + </mediaobject> + </screenshot> + </para +><para +>Om kvantiseringen &rosegarden; har använt inte är lämplig, antingen för hela partituret eller för ett antal markerade noter, kan du välja att använda en annan kvantiseringsnivå eller ingen alls. För att använda en annan kvantisering för vissa noter, markera noterna och använd menyfunktionen Kvantisera... (markera rutan som heter <quote +>Kvantisera bara för notskrift</quote +>). Kvantiseringsnivån som normalt används kan ändras i inställningsdialogrutan. </para> + + <sect2 id="nv-quantization-parameters"> + <title +>Inställningsbara parametrar för den heuristiska kvantiseringen</title> + + <sect3 id="nv-quantization-parameters-during"> + <title +>Parametrar för själva kvantiseringen</title> + + <variablelist> + + <varlistentry> + <term +>Komplexitet</term> + <listitem> + <para +>Kvantiseringens "komplexitet" är dess mest grundläggande parameter. En "komplex" kvantisering är mer redo att acceptera att musik som ser komplex ut i själva verket är avsedd att vara komplex, medan en "enkel" kvantisering är mer redo att anta att musik som ser komplex ut orsakas av ett mindre precist utförande av enkel musik. </para> + <para +>Standardinställningarna är avsedda att skapa rimliga resultat för ett ganska brett musikspektrum. </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>Grundenhet för rutnät</term> + <listitem> + <para +>Den grundläggande rutnätsenheten (inställd till ett notvärde) anger den absolut minsta notenheten som tillåts bli kvar i partituret efter kvantisering. Om den till exempel är inställd till en sextondedelsnot, placeras alla noter på gränser som är en multipel av sextondedelsnoter, och notvärdena är också multiplar av sextondedelsnoter. </para> + <para +>Basrutnätsenhetens Inställning är inte riktigt så viktig för kvantisering som den är för den vanliga rutnätskvantiseringen, eftersom allt den gör är att lägga en absolut gräns på precisionsnivån som tillåts av komplexitetsparametern. Oftast när du hittar ett fall där bättre resultat uppnås genom att öka rutnätsenheten, har du i själva verket hittat ett fall där kvantiseringen helt enkelt inte gjorde ett så bra jobb som den skulle ha kunnat göra med den mindre enheten. </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>Annandelningsnivå</term> + <listitem> + <para +>Kvantiseringen klarar av att identifiera annandelningar (trioler och andra tidskomprimerade grupper), inom rimliga gränser. Parametern styr hur ambitiös den försöker vara när den letar efter annandelningar, genom att ange en gräns för hur många noter per annandelning som den försöker identifiera. Om den är inställd till <quote +>Inget</quote +>, försöker inte kvantiseringen identifiera annandelningar överhuvudtaget. </para> + </listitem> + </varlistentry> + + </variablelist> + + </sect3> + + <sect3 id="nv-quantization-parameters-after"> + <title +>Parametrar som styr uppstädning efter kvantisering</title> + + <variablelist> + + <varlistentry> + <term +>Lägg till balkar igen</term> + <listitem> + <para +>Gör att noterna placeras in i balkar med grupper som är passande efter kvantiseringen. Det är ofta önskvärt. </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>Lägg till artikulationsbeteckningar</term> + <listitem> + <para +>Gör att kvantiseringen försöker identifiera vilka noter som ska markeras som staccato, baserat på notvärdet hos individuella noter och noter i följd (för noter som slutar väsentligt tidigare än den efterföljande noten, men uppenbarligen inte tidigt nog för att vara värda en paus), tenuto (för noter som nästan eller precis överlappar följande not) och legatobågar (för följder av noter som möts eller överlappar). </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>Bind noter vid taktstreck etc.</term> + <listitem> + <para +>Gör att alla noter som fortfarande finns kvar efter kvantisering och överlappar taktstreck eller som har notvärden som inte kan uttryckas exakt med enstaka nothuvuden att delas upp i flera noter på lämpligt sätt, och bindas. Det får samma effekt som att utföra funktionen "Bind noter vid taktstreck" i notvyn. </para> + <para +>Den här parametern är normalt inte aktiverad, delvis på grund av att den ändrar antalet tonhändelser, vilket är olämpligt när &rosegarden; delvis eller huvudsakligen används som en MIDI-musikbehandlare. </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>Dela och bind ackordnoter med för stora notvärden</term> + <listitem> + <para +>Gör att överlappande noter delas och binds, så att strikta ackord med individuella nothuvuden bundna efter behov skapas. Det får samma effekt som att utföra funktionen "Dela och bind ackordnoter med för stora notvärden" i notvyn. </para> + <para +>Den här parametern är normalt inte aktiverad, delvis på grund av att den ändrar antalet tonhändelser, vilket är olämpligt när &rosegarden; delvis eller huvudsakligen används som en MIDI-musikbehandlare. </para> + </listitem> + </varlistentry> + </variablelist> + </sect3> + </sect2> + </sect1> + + + <sect1 id="nv-note-styles"> + <title +>Notstilar</title> + + <para +>&rosegarden; låter dig också ändra diverse aspekter av sättet som olika nottyper ritas upp, som val av nothuvuden, antal flaggor, om noter är ifyllda eller inte och så vidare. </para> + + <para +>En uppsättning standardstilar (Klassisk, Kors, Triangel och Mensural) tillhandahålls, och du kan ändra stilen som används för enskilda noter genom att markera dem och därefter använda alternativen i menyn Notstil. Varje not kommer ihåg vilken stil som har valts för den, och informationen sparas som en del av kompositionen. Du kan också ändra förvald stil för nya noter genom att använda alternativet <guimenuitem +>Anpassa Rosegarden...</guimenuitem +> i menyn <guimenu +>Inställningar</guimenu +>. </para> + + <para +>Det är också möjligt att skapa dina egna notstilar genom att beskriva dem med <acronym +>XML</acronym +>-filer. (Till och med standardstilarna är definierade på detta sätt: Den enda orsaken att editorn vet om att en klassisk sextondedelsnot har ett ovalt lutande ifyllt huvud, ett skaft, två flaggor etc., är att beskrivningen i Classical.xml anger det.) Se <link linkend="developers-note-styles" +>Anpassa Rosegarden</link +> för mer information. </para> + </sect1> + + <sect1 id="nv-note-fonts"> + <title +>Notteckensnitt</title> + <para +>&rosegarden; levereras med ett enda skalbart notteckensnitt, Feta-teckensnittet utvecklat i Lilypond-projektet. Feta är ett teckensnitt med mycket hög kvalitet som bör vara lämpligt för nästan allt klassiskt arbete. </para> + + <para +>&rosegarden; innehåller också stöd som standard för ett antal andra notteckensnitt. Du måste själv tillhandahålla teckensnitten på formaten Truetype (.ttf) eller Postscript Typ-1 (.pfb, .pfa), och du måste ha lämpliga rättigheter för att installera dem på samma plats som &rosegarden; installerades. För att installera ett notteckensnitt som stöds, lokalisera katalogen share för &rosegarden;s installation (oftast en underkatalog till KDE-skrivbordets installationsträd, som /opt/kde/share/apps/rosegarden). Du märker att katalogen har en underkatalog som heter "fonts". Kopiera teckensnittsfilerna till den, och starta om &rosegarden;. Om teckensnittet stöds, ska det nu synas i teckensnittsmenyn i notbehandlaren.</para> + + <para +>Fullständigt eller delvis stöd tillhandahålls för närvarande för följande teckensnitt: Fughetta, av Blake Hodgetts; Petrucci, det "ursprungliga" Finale-teckensnittet; Maestro, det "nya" Finale-teckensnittet; Opus, Sibelius teckensnitt; Inkpen, Sibelius jazz-teckensnitt; Sonata från Adobe; Steinberg, från Cubase-musikbehandlaren; och Xinfonia. (De flesta av ovanstående teckensnittsnamn är registrerade varumärken av respektive företag.) ROSEGARDEN-GRUPPEN GER INGA UTFÄSTELSER ANGÅENDE JURIDISK STATUS FÖR ANVÄNDNING AV NÅGOT AV DESSA TECKENSNITT MED ROSEGARDEN. Det är ditt ansvar att försäkra dig om att du följer den licens (om det finns någon) som du erhöll teckensnittet med, innan du försöker använda det. Om du inte är säker på att du har rättighet att använda ett teckensnitt, gör då inte det. Förutom alla andra aspekter, så är det vanliga Feta-teckensnittet ändå bättre än de flesta av dem.</para> + + <para +>Det är också möjligt att tillhandahålla nya avbildningsfiler för att använda nya teckensnitt. För vissa teckensnitt som har liknande avbildningar eller mått som teckensnitt i listan ovan, kan det vara så enkelt som att redigera teckensnittets namn i avbildningsfilen. Se <link linkend="developers-note-fonts" +>Anpassa Rosegarden</link +> för mer information. </para> + </sect1> + + + </chapter> + + <chapter id="event-view"> + <title +>Händelselisteditorn</title> + <sect1 id="ev-introduction"> + <title +>Inledning</title> + + <para +>&rosegarden;s editor för händelselistan visar händelserna i ett enstaka segment i obehandlad form, och gör det möjligt att redigera de exakta egenskaperna för händelserna individuellt. <screenshot +> <mediaobject> + <imageobject> + <imagedata fileref="rg-eventlisteditor.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>&rosegarden;s händelselisteditor</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + </sect1> + </chapter> + + + + + <!-- + ********************************** + + PART II: + Command reference + + ********************************** + --> +<!-- NO + + <chapter id="commands"> + <title +>Command Reference</title> + + + <para +></para> + + <sect1 id="commands-main"> + <title +>Main window</title> + <para +></para> + + + <sect2> + <title +>File menu</title> + <para> + <variablelist> + + <varlistentry id="commands-main-file-new"> + <term +><menuchoice> + <shortcut> + <keycombo +><keycap +>Ctrl</keycap +><keycap +>n</keycap +></keycombo> + </shortcut> + <guimenu +>File</guimenu> + <guimenuitem +>New</guimenuitem> + </menuchoice +></term> + <listitem +><para +><action +>Creates a new composition.</action +></para +></listitem> + </varlistentry> + + <varlistentry id="commands-main-file-open"> + <term +><menuchoice> + <shortcut> + <keycombo +><keycap +>Ctrl</keycap +><keycap +>o</keycap +></keycombo> + </shortcut> + <guimenu +>File</guimenu> + <guimenuitem +>Open</guimenuitem> + </menuchoice +></term> + <listitem +><para +><action +>Opens an existing composition from a Rosegarden-4 (.rg) file.</action +></para +></listitem> + </varlistentry> + + <varlistentry id="commands-main-file-import"> + <term +><menuchoice> + <guimenu +>File</guimenu> + <guimenuitem +>Import</guimenuitem> + </menuchoice +></term> + <listitem +><para +>This submenu contains functions for importing compositions from other file formats.</para> + + <variablelist> + + <varlistentry id="commands-main-file-import-midi"> + <term +><menuchoice> + <guimenu +>Import</guimenu> + <guimenuitem +>Import &MIDI; file...</guimenuitem> + </menuchoice +></term> + <listitem +><para +><action +>Creates a new composition from the contents of an existing &MIDI; (.mid) file.</action +></para +></listitem> + </varlistentry> + + <varlistentry id="commands-main-file-import-rg21"> + <term +><menuchoice> + <guimenu +>Import</guimenu> + <guimenuitem +>Import Rosegarden 2.1 file...</guimenuitem> + </menuchoice +></term> + <listitem +><para +><action +>Creates a new composition from the contents of an existing Rosegarden 2.1 (.rose) file.</action +></para +></listitem> + </varlistentry> + + </variablelist> + </listitem> + </varlistentry> + + <varlistentry id="commands-main-file-merge"> + <term +><menuchoice> + <guimenu +>File</guimenu> + <guimenuitem +>Merge</guimenuitem> + </menuchoice +></term> + <listitem +><para +>This submenu contains functions for merging other files into the current composition.</para> + + <variablelist> + + <varlistentry id="commands-main-file-merge-file"> + <term +><menuchoice> + <guimenu +>Merge</guimenu> + <guimenuitem +>Merge File...</guimenuitem> + </menuchoice +></term> + <listitem +><para +><action +>Merges the contents of an existing Rosegarden (.rg) file into the current composition. You will be offered a choice of whether to merge the file in new tracks at the start of the composition, or after the end of the current composition.</action +></para +></listitem> + </varlistentry> + + <varlistentry id="commands-main-file-merge-midi"> + <term +><menuchoice> + <guimenu +>Merge</guimenu> + <guimenuitem +>Merge &MIDI; file...</guimenuitem> + </menuchoice +></term> + <listitem +><para +><action +>Merges the contents of an existing &MIDI; (.mid) file into the current composition. You will be offered a choice of whether to merge the file in new tracks at the start of the composition, or after the end of the current composition.</action +></para +></listitem> + </varlistentry> + + <varlistentry id="commands-main-file-merge-rg21"> + <term +><menuchoice> + <guimenu +>Merge</guimenu> + <guimenuitem +>Merge Rosegarden 2.1 file...</guimenuitem> + </menuchoice +></term> + <listitem +><para +><action +>Merges the contents of an existing Rosegarden 2.1 (.rose) file into the current composition. You will be offered a choice of whether to merge the file in new tracks at the start of the composition, or after the end of the current composition.</action +></para +></listitem> + </varlistentry> + + </variablelist> + </listitem> + </varlistentry> + + <varlistentry id="commands-main-file-export"> + <term +><menuchoice> + <guimenu +>File</guimenu> + <guimenuitem +>Export</guimenuitem> + </menuchoice +></term> + <listitem +><para +>This submenu contains functions for exporting the contents of compositions to other file formats.</para> + + <variablelist> + + <varlistentry id="commands-main-file-export-midi"> + <term +><menuchoice> + <guimenu +>Export</guimenu> + <guimenuitem +>Export &MIDI; file...</guimenuitem> + </menuchoice +></term> + <listitem +><para +><action +>Saves the contents of the current composition into a new &MIDI; file.</action +> Note that not all data in the Rosegarden composition necessarily can or will be saved in the &MIDI; format.</para +></listitem> + </varlistentry> + + <varlistentry id="commands-main-file-export-csound"> + <term +><menuchoice> + <guimenu +>Export</guimenu> + <guimenuitem +>Export Csound score file...</guimenuitem> + </menuchoice +></term> + <listitem +><para +><action +>Saves the contents of the current composition into a new Csound score file.</action +> Together with a suitable orchestra file (not supplied), this can be used to play the composition through <ulink url="http://www.csounds.com/" +>Csound</ulink +>. Note that not all data in the Rosegarden composition necessarily can or will be saved in the Csound format.</para +></listitem> + </varlistentry> + + <varlistentry id="commands-main-file-export-lilypond"> + <term +><menuchoice> + <guimenu +>Export</guimenu> + <guimenuitem +>Export Lilypond file...</guimenuitem> + </menuchoice +></term> + <listitem +><para +><action +>Saves the contents of the current composition into a new Lilypond file.</action +> This can then be processed by the <ulink url="http://www.lilypond.org/" +>Lilypond</ulink +> system to produce typeset-quality music, although it is likely that the file may need some tweaking to get really good quality output. Note that not all data in the Rosegarden composition necessarily can or will be saved in the Lilypond format.</para +></listitem> + </varlistentry> + + <varlistentry id="commands-main-file-export-mup"> + <term +><menuchoice> + <guimenu +>Export</guimenu> + <guimenuitem +>Export Mup file...</guimenuitem> + </menuchoice +></term> + <listitem +><para +><action +>Saves the contents of the current composition into a new Mup file.</action +> This can then be processed by the <ulink url="http://www.arkkra.com/" +>Mup</ulink +> music publication system, although it is likely that the file may need some tweaking to get really good quality output. Note that not all data in the Rosegarden composition necessarily can or will be saved in the Mup format.</para +></listitem> + </varlistentry> + + <varlistentry id="commands-main-file-export-musicxml"> + <term +><menuchoice> + <guimenu +>Export</guimenu> + <guimenuitem +>Export MusicXML file...</guimenuitem> + </menuchoice +></term> + <listitem +><para +><action +>Saves the contents of the current composition into a new MusicXML file.</action +> This can then be used with any music software that supports the MusicXML format. Note that MusicXML support is experimental and has not been well tested. Not all data in the Rosegarden composition necessarily can or will be saved in the MusicXML format.</para +></listitem> + </varlistentry> + + </variablelist> + </listitem> + </varlistentry> + + <varlistentry id="commands-main-file-save"> + <term +><menuchoice> + <shortcut> + <keycombo +><keycap +>Ctrl</keycap +><keycap +>s</keycap +></keycombo> + </shortcut> + <guimenu +>File</guimenu> + <guimenuitem +>Save</guimenuitem> + </menuchoice +></term> + <listitem +><para +><action +>Saves the composition.</action +></para +></listitem> + </varlistentry> + + <varlistentry id="commands-main-file-save-as"> + <term +><menuchoice> + <guimenu +>File</guimenu> + <guimenuitem +>Save As...</guimenuitem> + </menuchoice +></term> + <listitem +><para +><action +>Saves the composition with a new filename.</action +></para +></listitem> + </varlistentry> + + <varlistentry id="commands-main-file-close"> + <term +><menuchoice> + <shortcut> + <keycombo +><keycap +>Ctrl</keycap +><keycap +>w</keycap +></keycombo> + </shortcut> + <guimenu +>File</guimenu> + <guimenuitem +>Close</guimenuitem> + </menuchoice +></term> + <listitem +><para +><action +>Closes the current composition.</action +></para +></listitem> + </varlistentry> + + <varlistentry id="commands-main-file-print"> + <term +><menuchoice> + <shortcut> + <keycombo +><keycap +>Ctrl</keycap +><keycap +>p</keycap +></keycombo> + </shortcut> + <guimenu +>File</guimenu> + <guimenuitem +>Print</guimenuitem> + </menuchoice +></term> + <listitem +><para +><action +>Prints the current composition.</action +> At the time of writing, the print function is incomplete. We recommend using the <link linkend="commands-main-file-export-lilypond" +>Export Lilypond file</link +> function and printing with Lilypond instead.</para +></listitem> + </varlistentry> + + <varlistentry id="commands-main-file-quit"> + <term +><menuchoice> + <shortcut> + <keycombo +><keycap +>Ctrl</keycap +><keycap +>q</keycap +></keycombo> + </shortcut> + <guimenu +>File</guimenu> + <guimenuitem +>Quit</guimenuitem> + </menuchoice +></term> + <listitem +><para +><action +>Quits &rosegarden;</action +></para +></listitem> + </varlistentry> + + </variablelist> + </para> + + </sect2> + + + <sect2> + <title +>Edit menu</title> + <para> + <variablelist> + + <varlistentry id="commands-main-edit-undo"> + <term> + <menuchoice> + <shortcut> + <keycombo> + <keycap +>Ctrl</keycap> + <keycap +>z</keycap> + </keycombo> + </shortcut> + <guimenu +>Edit</guimenu> + <guimenuitem +>Undo</guimenuitem> + </menuchoice> + </term> + <listitem> + <para> + <action> + Reverses the last command performed. + </action> + </para> + </listitem> + </varlistentry +> + + <varlistentry id="commands-main-edit-redo"> + <term> + <menuchoice> + <shortcut> + <keycombo> + <keycap +>Ctrl</keycap> + <keycap +>Shift</keycap> + <keycap +>z</keycap> + </keycombo> + </shortcut> + <guimenu +>Edit</guimenu> + <guimenuitem +>Redo</guimenuitem> + </menuchoice> + </term> + <listitem> + <para> + <action> + Repeats the last command performed, following an undo. + </action> + </para> + </listitem> + </varlistentry +> + + <varlistentry id="commands-main-edit-cut"> + <term> + <menuchoice> + <shortcut> + <keycombo> + <keycap +>Ctrl</keycap> + <keycap +>x</keycap> + </keycombo> + </shortcut> + <guimenu +>Edit</guimenu> + <guimenuitem +>Cut</guimenuitem> + </menuchoice> + </term> + <listitem> + <para> + <action> + Removes the currently selected segment from the + composition view and adds it to the clipboard. Note that + when you have selected a track, all segments in that track + are selected. + </action> + </para> + </listitem> + </varlistentry +> + + <varlistentry id="commands-main-edit-copy"> + <term> + <menuchoice> + <shortcut> + <keycombo> + <keycap +>Ctrl</keycap> + <keycap +>c</keycap> + </keycombo> + </shortcut> + <guimenu +>Edit</guimenu> + <guimenuitem +>Copy</guimenuitem> + </menuchoice> + </term> + <listitem> + <para> + <action> + Removes the selected segments from the composition and + places them in the clipboard to replace any contents the + clipboard previously had. + </action +> + Note that when you have selected a track, all segments in that track + are selected. + </para> + </listitem> + </varlistentry +> + + + <varlistentry id="commands-main-edit-paste"> + <term> + <menuchoice> + <shortcut> + <keycombo> + <keycap +>Ctrl</keycap> + <keycap +>v</keycap> + </keycombo> + </shortcut> + <guimenu +>Edit</guimenu> + <guimenuitem +>Paste</guimenuitem> + </menuchoice> + </term> + <listitem> + <para> + <action> + Inserts the contents of the clipboard into the composition. + Verbage hear stating where the contents are inserted + (current track, offset within that track etc). + </action> + </para> + </listitem> + </varlistentry +> + + <varlistentry id="commands-main-edit-delete"> + <term> + <menuchoice> + <shortcut> + <keycombo> + <keycap +>Delete</keycap> + </keycombo> + </shortcut> + <guimenu +>Edit</guimenu> + <guimenuitem +>Delete</guimenuitem> + </menuchoice> + </term> + <listitem> + <para> + <action> + Removes the selected segments from the composition and throws them away. + </action> + </para> + </listitem> + </varlistentry +> + + + <varlistentry id="commands-main-edit-select-all-segments"> + <term> + <menuchoice> + <guimenu +>Edit</guimenu> + <guimenuitem +>Select All Segments</guimenuitem> + </menuchoice> + </term> + <listitem> + <para> + <action> + Selects all segments within the composition. + </action> + </para> + </listitem> + </varlistentry +> + + <varlistentry id="commands-main-edit-add-tempo-change"> + <term> + <menuchoice> + <guimenu +>Edit</guimenu> + <guimenuitem +>Add Tempo Change...</guimenuitem> + </menuchoice> + </term> + <listitem> + <para> + <action> + Invokes a tempo change dialog. + </action> + This offers a + selection of ways to change the tempo of the + composition, including changing the tempo from the + insert cursor position onwards, from the last + tempo change onwards, or for the entire + composition. See + +for more information. + + </para> + </listitem> + </varlistentry +> + + <varlistentry id="commands-main-edit-add-time-signature"> + <term> + <menuchoice> + <guimenu +>Edit</guimenu> + <guimenuitem +>Add Time Signature Change...</guimenuitem> + </menuchoice> + </term> + <listitem> + <para> + <action> + Invokes a time-signature change dialog. + </action> + + This offers a + selection of ways to change the tempo of the + composition, including changing the time signature + from the insert cursor position onwards or from the + start of the current bar. See + + for more information. + + </para> + </listitem> + </varlistentry +> + + + <varlistentry id="commands-main-edit-change-composition-duration"> + <term> + <menuchoice> + <guimenu +>Edit</guimenu> + <guimenuitem +>Change Composition Duration...</guimenuitem> + </menuchoice> + </term> + <listitem> + <para> + <action> + Invokes a composition duration change dialog. + </action> + + This allows you to change the overall duration of + the composition. This duration sets a hard limit + (as a number of bars) on the scrollable width of the + main window and the length of time you can play or + record before the composition is deemed to have + ended. The default is 100 bars. + + </para> + </listitem> + </varlistentry +> + + + <varlistentry id="commands-main-edit-document-properties"> + <term> + <menuchoice> + <guimenu +>Edit</guimenu> + <guimenuitem +>Edit Document Properties...</guimenuitem> + </menuchoice> + </term> + <listitem> + <para> + <action> + Invokes a document properties dialog. + </action> + + The document properties dialog allows you to review and/or modify the current document properties. Note - explain what are properties. Note to developers - It seems kinda weird to have icons on the left for selecting, and tabs in each one. Why not just tabs or just the things on the left? + + </para> + </listitem> + </varlistentry +> + + + </variablelist> + </para> + </sect2> + + <sect2> + <title +>Segments menu</title> + <para> + <variablelist> + + <varlistentry id="commands-main-segments-open-default-editor"> + <term> + <menuchoice> + <shortcut> + <keycombo> + <keycap +>Return</keycap> + </keycombo> + </shortcut> + <guimenu +>Segments</guimenu> + <guimenuitem +>Open in Default Editor</guimenuitem> + </menuchoice> + </term> + <listitem> + <para> + <action +> Opens all of the currently + selected segments together in a notation editor, or in + whichever other editor you have configured as your + default. + </action> + </para> + </listitem> + </varlistentry +> + + <varlistentry id="commands-main-segments-open-matrix-editor"> + <term> + <menuchoice> + <guimenu +>Segments</guimenu> + <guimenuitem +>Open in Matrix Editor</guimenuitem> + </menuchoice> + </term> + <listitem> + <para> + <action +> Opens all of the currently + selected segments in a matrix editor. + </action> + See <link linkend="matrix-view" +>matrix editor</link +>. + </para> + </listitem> + </varlistentry +> + + <varlistentry id="commands-main-segments-open-notation-editor"> + <term> + <menuchoice> + <guimenu +>Segments</guimenu> + <guimenuitem +>Open in Notation Editor</guimenuitem> + </menuchoice> + </term> + <listitem> + <para> + <action +> Opens all of the currently + selected segments together in a notation editor. + </action> + See <link linkend="notation-view" +>notation editor</link +>. + </para> + </listitem> + </varlistentry +> + + <varlistentry id="commands-main-segments-open-event-editor"> + <term> + <menuchoice> + <guimenu +>Segments</guimenu> + <guimenuitem +>Open in Event List Editor</guimenuitem> + </menuchoice> + </term> + <listitem> + <para> + <action +> Opens all of the currently + selected segments together in a event-list editor. + </action> + See <link linkend="event-view" +>event-list editor</link +>. + </para> + </listitem> + </varlistentry +> + + + <varlistentry id="commands-main-segments-quantize"> + <term> + <menuchoice> + <guimenu +>Segments</guimenu> + <guimenuitem +>Quantize...</guimenuitem> + </menuchoice> + </term> + <listitem> + <para> + <action +>Invokes a quantization dialog for quantizing the current selection. + </action> + See <link linkend="nv-quantization" +>quantization</link +>. + </para> + </listitem> + </varlistentry +> + + <varlistentry id="commands-main-segments-rescale"> + <term> + <menuchoice> + <guimenu +>Segments</guimenu> + <guimenuitem +>Rescale...</guimenuitem> + </menuchoice> + </term> + <listitem> + <para> + <action +>Allows you to stretch or squash segments in time. + </action> + + This option invokes a rescale dialog, which allows + you to specify a ratio of timings that is then + applied to the selected segments. This has the + result of stretching (slowing down) or squashing + (speeding up) the selected segments, changing their + durations accordingly. + + </para> + <para> + This only applies to segments containing MIDI + events, not to audio segments. Rosegarden does not + currently provide native support for audio + time-stretching. + </para> + </listitem> + </varlistentry +> + + <varlistentry id="commands-main-segments-auto-split"> + <term> + <menuchoice> + <guimenu +>Segments</guimenu> + <guimenuitem +>Auto-Split</guimenuitem> + </menuchoice> + </term> + <listitem> + <para> + <action> + Splits the selected segments on silences. + </action> + + This function works slightly differently depending + on whether the selected segments contain audio or + MIDI data. For audio segments, it offers you a + dialog in which you can choose a threshold below + which the segment is considered "silent"; it then + splits the segment whenever its amplitude falls + below this threshold. For MIDI segments, it simply + splits the segment everywhere that a full bar of + silence occurs. + </para> + </listitem> + </varlistentry +> + + <varlistentry id="commands-main-segments-split-by-pitch"> + <term> + <menuchoice> + <guimenu +>Segments</guimenu> + <guimenuitem +>Split by Pitch...</guimenuitem> + </menuchoice> + </term> + <listitem> + <para> + <action +>Splits the currently selected segments into higher and + lower parts. + </action> + + This function invokes a dialog allowing you to + choose a pitch as a "split point", and then splits + the selected segments in half with all the notes on + or above that split point in the "higher" segment + and all the notes below it in the "lower". + + </para> + <para> + If the music in the segment consists of two separate + parts (e.g. left and right hand piano parts) that + are not always completely on either side of a single + split point, you may with to select the "ranging + split-point" option. If this is selected, + Rosegarden will attempt to track the two parts as + they move up and down, usually doing a slightly + better job of separating out notes that were + intended to lie in the two separate parts. + + </para> + <para> + The resulting segments are both created on the same + track, with one overlapping the other. + + </para> + </listitem> + </varlistentry +> + + + + + </variablelist> + </para> + </sect2> + </sect1> + + <sect1 id="commands-nv"> + <title +>Notation editor</title> + <para +></para> + + + <sect2 id="commands-nv-menu-file"> + <title +>File menu</title> + <para> + <variablelist> + + <varlistentry id="commands-nv-menu-file-close"> + <term +><menuchoice> + <shortcut> + <keycombo +><keycap +>Ctrl</keycap +><keycap +>w</keycap +></keycombo> + </shortcut> + <guimenu +>File</guimenu> + <guimenuitem +>Close</guimenuitem> + </menuchoice +></term> + <listitem +><para +><action +>Closes the window</action +></para +></listitem> + </varlistentry> + + </variablelist> + </para> + + </sect2> + + <sect2 id="commands-nv-menu-edit"> + <title +>Edit menu</title> + <para> + <variablelist> + + <varlistentry id="commands-nv-menu-edit-undo"> + <term +><menuchoice> + <shortcut> + <keycombo +><keycap +>Ctrl</keycap +><keycap +>z</keycap +></keycombo> + </shortcut> + <guimenu +>Edit</guimenu> + <guimenuitem +>Undo</guimenuitem> + </menuchoice +></term> + <listitem> + <para> + <action> + + Reverses the last edit. + + </action +> Edits are shared across + all views, so if the last edit was not made in + this view, undoing it might not appear to change + this view either. + </para> + </listitem> + </varlistentry> + + <varlistentry id="commands-nv-menu-edit-redo"> + <term +><menuchoice> + <shortcut> + <keycombo +><keycap +>Ctrl</keycap +><keycap +>Shift</keycap +><keycap +>z</keycap +></keycombo> + </shortcut> + <guimenu +>Edit</guimenu> + <guimenuitem +>Redo</guimenuitem> + </menuchoice +></term> + <listitem> + <para> + <action> + + Repeats the last edit, following an undo. + + </action> + </para> + </listitem> + </varlistentry> + + <varlistentry id="commands-nv-menu-edit-cut"> + <term +><menuchoice> + <shortcut> + <keycombo +><keycap +>Ctrl</keycap +><keycap +>x</keycap +></keycombo> + </shortcut> + <guimenu +>Edit</guimenu> + <guimenuitem +>Cut</guimenuitem> + </menuchoice +></term> + <listitem> + <para> + <action> + + Removes the selected events from the composition + and places them in the clipboard to replace any + contents the clipboard previously had. + + </action> + </para> + </listitem> + </varlistentry> + + <varlistentry id="commands-nv-menu-edit-copy"> + <term +><menuchoice> + <shortcut> + <keycombo +><keycap +>Ctrl</keycap +><keycap +>c</keycap +></keycombo> + </shortcut> + <guimenu +>Edit</guimenu> + <guimenuitem +>Copy</guimenuitem> + </menuchoice +></term> + <listitem> + <para> + <action> + + Copies the selected events to the clipboard + to replace any contents the clipboard previously had. + + </action> + </para> + </listitem> + </varlistentry> + + <varlistentry id="commands-nv-menu-edit-paste"> + <term +><menuchoice> + <shortcut> + <keycombo +><keycap +>Ctrl</keycap +><keycap +>v</keycap +></keycombo> + </shortcut> + <guimenu +>Edit</guimenu> + <guimenuitem +>Paste</guimenuitem> + </menuchoice +></term> + <listitem> + <para> + <action> + + Copies the contents of the clipboard to the + location of the insert cursor in the current + composition. + + </action> + + The clipboard must not contain + multiple segments, and there must be enough + space (occupied only by rests) starting at + the insert cursor position to accommodate the + clipboard's contents. + + </para> + </listitem> + </varlistentry> + + <varlistentry id="commands-nv-menu-edit-cut-and-close"> + <term +><menuchoice> + <shortcut> + <keycombo +><keycap +>Ctrl</keycap +><keycap +>Shift</keycap +><keycap +>x</keycap +></keycombo> + </shortcut> + <guimenu +>Edit</guimenu> + <guimenuitem +>Cut and Close</guimenuitem> + </menuchoice +></term> + <listitem> + <para> + <action> + + Removes the selected events from the composition + and places them in the clipboard to replace any + contents the clipboard previously had, and closes + the gap left behind by moving all subsequent + events towards the beginning of the composition. + + </action> + </para> + </listitem> + </varlistentry> + + <varlistentry id="commands-nv-menu-edit-paste-dot-dot-dot"> + <term +><menuchoice> + <shortcut> + <keycombo +><keycap +>Ctrl</keycap +><keycap +>Shift</keycap +><keycap +>v</keycap +></keycombo> + </shortcut> + <guimenu +>Edit</guimenu> + <guimenuitem +>Paste...</guimenuitem> + </menuchoice +></term> + <listitem> + <para> + <action> + + Provides a choice of paste mechanisms with the + ability to set one as the default for use in the + Paste menu function. + + </action> + + See the section on <link linkend="nv-paste-types" +>Paste types</link +> for more information. + + </para> + </listitem> + </varlistentry> + + + <varlistentry id="commands-nv-menu-edit-delete"> + <term +><menuchoice> + <shortcut> + <keycombo +><keycap +>Del</keycap +></keycombo> + </shortcut> + <guimenu +>Edit</guimenu> + <guimenuitem +>Delete</guimenuitem> + </menuchoice +></term> + <listitem> + <para> + <action> + Removes the selected events from the composition + and throws them away. + </action> + </para> + </listitem> + </varlistentry> + + + <varlistentry id="commands-nv-menu-edit-select-from-start"> + <term +><menuchoice> + <guimenu +>Edit</guimenu> + <guimenuitem +>Select from Start</guimenuitem> + </menuchoice +></term> + <listitem> + <para> + <action> + Extends the current selection by selecting + all events from the start of the staff up to the + current selection (or up to the insert cursor, + if no events are currently selected). + </action> + </para> + </listitem> + </varlistentry> + + + <varlistentry id="commands-nv-menu-edit-select-to-end"> + <term +><menuchoice> + <guimenu +>Edit</guimenu> + <guimenuitem +>Select to End</guimenuitem> + </menuchoice +></term> + <listitem> + <para> + <action> + Extends the current selection by selecting + all events from the end of the current selection + (or from the insert cursor, if no events are + currently selected) up to the end of the staff. + </action> + </para> + </listitem> + </varlistentry> + + + <varlistentry id="commands-nv-menu-edit-select-whole-staff"> + <term +><menuchoice> + <guimenu +>Edit</guimenu> + <guimenuitem +>Select Whole Staff</guimenuitem> + </menuchoice +></term> + <listitem> + <para> + <action> + Selects all the events on the current staff. + </action> + </para> + </listitem> + </varlistentry> + + + <varlistentry id="commands-nv-menu-edit-clear-selection"> + <term +><menuchoice> + <shortcut> + <keycombo +><keycap +>Esc</keycap +></keycombo> + </shortcut> + <guimenu +>Edit</guimenu> + <guimenuitem +>Clear Selection</guimenuitem> + </menuchoice +></term> + <listitem> + <para> + <action> + Unselects all events. + </action> + </para> + </listitem> + </varlistentry> + + + <varlistentry id="commands-nv-menu-edit-filter-selection"> + <term +><menuchoice> + <guimenu +>Edit</guimenu> + <guimenuitem +>Filter Selection</guimenuitem> + </menuchoice +></term> + <listitem> + <para> + <action> + Invokes an event filter dialog. + </action> + This offers you the ability to filter a range of events in + any of several categories out of your selection. + </para> + <para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="rg-eventfilter.png" format="PNG"/> + </imageobject> + <textobject> + <phrase +>The event filter dialog</phrase> + </textobject> + </mediaobject> + </screenshot> + </para> + <para> + All ranges may be either inclusive or exclusive. + </para> + <para> + An inclusive range will remove events on either side of it + from the selection. You can use this, for example, to + filter everything below middle C and above the A above + middle C out of your selection. + </para> + <para> + An exclusive range will remove the events within the range + itself, leaving everything on either side of it selected. + Using the same search points as in the previous example, + you would use an exclusive range to remove everything + between middle C and the A above middle C from your + selection, while leaving everything above and below that + range selected. + </para> + <para> + Once your selection has been filtered, you can manipulate + it by any conventional means. + </para> + </listitem> + </varlistentry> + + + <varlistentry id="commands-nv-menu-edit-add-tempo"> + <term +><menuchoice> + <guimenu +>Edit</guimenu> + <guimenuitem +>Add Tempo Change...</guimenuitem> + </menuchoice +></term> + <listitem> + <para> + <action> + Invokes a tempo change dialog. + </action> + This offers a + selection of ways to change the tempo of the + composition, including changing the tempo from the + insert cursor position onwards, from the last + tempo change onwards, or for the entire + composition. See + +for more information. + </para> + </listitem> + </varlistentry> + + + <varlistentry id="commands-nv-menu-edit-add-time-signature"> + <term +><menuchoice> + <guimenu +>Edit</guimenu> + <guimenuitem +>Add Time Signature Change...</guimenuitem> + </menuchoice +></term> + <listitem> + <para> + <action> + + Invokes a time-signature change dialog. + + </action> + + This offers a + selection of ways to change the tempo ofthe + composition, including changing the time signature + from the insert cursor position onwards or from the + start of the current bar. See +Changing the Time Signature + + for more information. + + </para> + </listitem> + </varlistentry> + + + <varlistentry id="commands-nv-menu-edit-add-clef"> + <term +><menuchoice> + <guimenu +>Edit</guimenu> + <guimenuitem +>Add Clef Change...</guimenuitem> + </menuchoice +></term> + <listitem> + <para> + <action> + + Invokes a clef selection dialog, and inserts the + chosen clef at the current insert cursor position. + + </action> + + The dialog allows you to choose a clef, but also + to choose how you want the clef to be applied, in + cases where there are already some notes following + the point where the clef is to be inserted. You + must choose one of the following: + + <variablelist> + + <varlistentry> + <term +>Maintain current pitches</term> + <listitem> + <para> + Any notes following the clef will keep + their current performance pitches. + </para> + <para> + For example, inserting a + tenor clef in the middle of a previously + treble-clef section will cause the notes following + the clef to be moved an octave + higher up the staff, because they will still have + their treble-clef pitches. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>Transpose into appropriate octave</term> + <listitem> + <para> + Any notes following the clef will + retain their pitch within the octave, but + may be moved into a different octave to + match the new clef, and therefore will play + at a new pitch. + </para> + <para> + For example, inserting a tenor clef in the + middle of a previously treble-clef section + will cause the notes following the clef to + move by one staff line only to adjust to the new + clef, but to play an octave lower than before. + </para> + </listitem> + </varlistentry> + + </variablelist> + + </para> + </listitem> + </varlistentry> + + + <varlistentry id="commands-nv-menu-edit-add-key-signature"> + <term +><menuchoice> + <guimenu +>Edit</guimenu> + <guimenuitem +>Add Key Change...</guimenuitem> + </menuchoice +></term> + <listitem> + <para> + <action> + + </action> + </para> + </listitem> + </varlistentry> + + + </variablelist> + </para> + + </sect2> + + <sect2 id="commands-nv-menu-group"> + <title +>Group menu</title> + <para> + <variablelist> + + + <varlistentry id="commands-nv-menu-group-beam"> + <term +><menuchoice> + <guimenu +>Group</guimenu> + <guimenuitem +>Beam Group</guimenuitem> + </menuchoice +></term> + <listitem> + <para> + <action> + Makes the selected notes into a beamed group. + </action> + </para> + </listitem> + </varlistentry> + + + <varlistentry id="commands-nv-menu-group-auto-beam"> + <term +><menuchoice> + <guimenu +>Group</guimenu> + <guimenuitem +>Auto-Beam</guimenuitem> + </menuchoice +></term> + <listitem> + <para> + <action> + Scans the area covered by the selection and attempts + to group short notes into plausible beamed groups. + </action> + </para> + </listitem> + </varlistentry> + + + <varlistentry id="commands-nv-menu-group-break-group"> + <term +><menuchoice> + <guimenu +>Group</guimenu> + <guimenuitem +>Unbeam</guimenuitem> + </menuchoice +></term> + <listitem> + <para> + <action> + Removes the selected notes from any beamed groups + they may be part of, leaving them as separate + individuals. + </action> + If part of a beamed group is selected, the unselected + part of the group will remain beamed. + </para> + </listitem> + </varlistentry> + + <varlistentry id="commands-nv-menu-group-tuplet"> + <term +><menuchoice> + <guimenu +>Group</guimenu> + <guimenuitem +>Tuplet</guimenuitem> + </menuchoice +></term> + <listitem> + <para> + <action> + Makes a triplet or other tuplet group. + </action> + This function allows you to adjust the timing of a + short section of music in the ratio of two + durations, for example to indicate that three notes + should be played in the time of two (the classic + triplet), or nine in the time of six, or whatever. + You can set this ratio in a dialog box when you + invoke the function. + </para> + <para> + If you have selected some events before invoking the + function, it will assume that you want to make a + tuplet group out of the selected region (or as close + to its duration as possible) and will adjust the + default values available in the dialog accordingly. + </para> + </listitem> + </varlistentry> + + + <varlistentry id="commands-nv-menu-group-simple-tuplet"> + <term +><menuchoice> + <guimenu +>Group</guimenu> + <guimenuitem +>Simple Tuplet</guimenuitem> + </menuchoice +></term> + <listitem> + <para> + <action> + + Makes a tuplet group (normally of triplets) with + the most apparently obvious ratio of durations. + + </action> + Usually this function will attempt to make a triplet + group starting at the current insert cursor, or if + some events are selected, will attempt to make them + into triplets. It is possible that it might end up + making non-triplet groups if there is no obvious + valid triplet arrangement. + </para> + </listitem> + </varlistentry> + + + <varlistentry id="commands-nv-menu-group-grace"> + <term +><menuchoice> + <guimenu +>Group</guimenu> + <guimenuitem +>Make Grace Notes</guimenuitem> + </menuchoice +></term> + <listitem> + <para> + <action> + Converts the selected notes into grace notes. + </action> + </para> + </listitem> + </varlistentry> + + + + <varlistentry id="commands-nv-menu-group-ungrace"> + <term +><menuchoice> + <guimenu +>Group</guimenu> + <guimenuitem +>Ungrace</guimenuitem> + </menuchoice +></term> + <listitem> + <para> + <action> + Converts any grace notes in the selection to + normal notes. + </action> + </para> + </listitem> + </varlistentry> + + + + <varlistentry id="commands-nv-menu-group-slur"> + <term +><menuchoice> + <guimenu +>Group</guimenu> + <guimenuitem +>Slur</guimenuitem> + </menuchoice +></term> + <listitem> + <para> + <action> + Adds a slur across the selected notes. + </action> + To remove the slur, click on it + with the erase tool just as you would for a note. + </para> + </listitem> + </varlistentry> + + + + <varlistentry id="commands-nv-menu-group-crescendo"> + <term +><menuchoice> + <guimenu +>Group</guimenu> + <guimenuitem +>Crescendo</guimenuitem> + </menuchoice +></term> + <listitem> + <para> + <action> + Adds a crescendo (opening hairpin) indication + across the selected notes. + </action> + To remove the crescendo indication, click on it + with the erase tool just as you would for a note. + </para> + </listitem> + </varlistentry> + + + + <varlistentry id="commands-nv-menu-group-decrescendo"> + <term +><menuchoice> + <guimenu +>Group</guimenu> + <guimenuitem +>Decrescendo</guimenuitem> + </menuchoice +></term> + <listitem> + <para> + <action> + Adds a decrescendo (closing hairpin) indication + across the selected notes. + </action> + To remove the decrescendo indication, click on it + with the erase tool just as you would for a note. + </para> + </listitem> + </varlistentry> + + + </variablelist> + </para> + + </sect2> + + <sect2 id="commands-nv-menu-notes"> + <title +>Notes menu</title> + <para> + <variablelist> + + <varlistentry id="commands-nv-menu-notes-"> + <term +><menuchoice> + <guimenu +>Notes</guimenu> + <guimenuitem +></guimenuitem> + </menuchoice +></term> + <listitem> + <para> + <action> + + </action> + </para> + </listitem> + </varlistentry> + + + <varlistentry id="commands-nv-menu-notes-style-actionmenu"> + <term +><menuchoice> + <guimenu +>Notes</guimenu> + <guimenuitem +>Note Style</guimenuitem> + </menuchoice +></term> + <listitem> + <para> + <action> + Change the note style of the selected notes. + </action> + This submenu contains an entry for each of the <link + linkend="nv-note-styles" +>note + styles</link +> that are currently available. Choosing one + will change the note style of the selected notes to + that style. + </para> + </listitem> + </varlistentry> + + + <varlistentry id="commands-nv-menu-notes-stems"> + <term +><menuchoice> + <guimenu +>Notes</guimenu> + <guimenuitem +>Stem Direction</guimenuitem> + </menuchoice +></term> + <listitem> + <para> + <action> + Change the stem + direction of the selected notes. + </action> + This submenu allows you to specify that all the + <link linkend="nv-note-qualities" +>stems</link +> of + the selected notes should point up or down, plus an + entry to reset the stem directions to those that + Rosegarden originally chose for the notes. + </para> + </listitem> + </varlistentry> + + + <varlistentry id="commands-nv-menu-notes-slashes"> + <term +><menuchoice> + <guimenu +>Notes</guimenu> + <guimenuitem +>Slashes</guimenuitem> + </menuchoice +></term> + <listitem> + <para> + <action> + Add diagonal + slashes across the selected notes' stems. + </action> + This submenu allows you to choose a number of + diagonal strokes or <link linkend="nv-note-qualities" +>slashes</link +> to be drawn across the + stems of each of the selected notes. These may be + used, for example, to indicate repetition or rolls + to a human reader. They do not (yet) affect + performance using Rosegarden. + </para> + </listitem> + </varlistentry> + + </variablelist> + </para> + + </sect2> + + <sect2 id="commands-nv-menu-marks"> + <title +>Marks menu</title> + <para> + <variablelist> + <varlistentry> + <term +><menuchoice> + <guimenu +>blah</guimenu> + <guimenuitem +>blah</guimenuitem> + </menuchoice +></term> + <listitem> + <para +>to be continued</para> + </listitem> + </varlistentry> + </variablelist> + </para> + + </sect2> + + <sect2 id="commands-nv-menu-transforms"> + <title +>Transforms menu</title> + <para> + <variablelist> + + <varlistentry id="commands-nv-menu-transforms-normalize-rests"> + <term +><menuchoice> + <guimenu +>Transforms</guimenu> + <guimenuitem +>Normalize Rests</guimenuitem> + </menuchoice +></term> + <listitem> + <para> + <action +>Makes the rests in the selection + theoretically correct.</action> + + This function examines each sequence of consecutive + rests found in the selection, and adjusts, splits + and merges rests as necessary to ensure that the + rests have theoretically correct durations and fall + on the correct boundaries. + </para> + + <para +>For example, a 4/4 bar containing a crotchet + (quarter-note), then a minim (half-note) rest and a + crotchet rest will be rearranged to place the crotchet + rest first, as the minim rest should not cross the + central beat boundary of the bar. + </para> + + <para +>This function is also useful in occasional + situations where Rosegarden has made a bad job of + maintaining the rests correctly within a bar, for + example when editing imported &MIDI; data. Normalizing + the rests will usually make the arrangement of notes + in such a situation a bit clearer. (Rosegarden always + normalizes the rests as a matter of course when + importing or recording &MIDI;, but things can sometimes + get muddled up again.)</para> + + </listitem> + </varlistentry> + + <varlistentry id="commands-nv-menu-transforms-collapse-rests"> + <term +><menuchoice> + <guimenu +>Transforms</guimenu> + <guimenuitem +>Collapse Rests</guimenuitem> + </menuchoice +></term> + <listitem> + <para> + <action +>Makes multiple short rests into fewer longer + ones.</action> + + This function merges consecutive rests into longer + rests, wherever possible. That is, wherever two + consecutive rests in the selection are found to have + a total duration expressible as a single longer + rest, they will be merged. + </para> + </listitem> + </varlistentry> + + <varlistentry id="commands-nv-menu-transforms-collapse-notes"> + <term +><menuchoice> + <guimenu +>Transforms</guimenu> + <guimenuitem +>Collapse Equal-Pitch Notes</guimenuitem> + </menuchoice +></term> + <listitem> + <para> + <action +>Makes multiple short notes into fewer longer + ones.</action> + + This function merges consecutive notes into longer + notes, wherever possible. That is, wherever two + consecutive notes of equal pitch in the selection + are found to have a total duration expressible as a + single longer note, they will be merged. + </para> + </listitem> + </varlistentry> + + <varlistentry id="commands-nv-menu-transforms-tie-notes"> + <term +><menuchoice> + <guimenu +>Transforms</guimenu> + <guimenuitem +>Tie Equal-Pitch Notes</guimenuitem> + </menuchoice +></term> + <listitem> + <para +><action +>Ties consecutive notes whenever possible.</action> + + This function ties together any consecutive notes of + equal pitch found in the selection. Tied notes are + shown with a curved line joining the note heads, and + are played as a single long note. + </para> + </listitem> + </varlistentry> + + <varlistentry id="commands-nv-menu-transforms-untie-notes"> + <term +><menuchoice> + <guimenu +>Transforms</guimenu> + <guimenuitem +>Untie Notes</guimenuitem> + </menuchoice +></term> + <listitem> + <para +><action +>Breaks ties between notes.</action> + + Any tied notes found in the selection are untied, + and will subsequently be played as separate + notes.</para> + </listitem> + </varlistentry> + + <varlistentry id="commands-nv-menu-transforms-make-viable"> + <term +><menuchoice> + <guimenu +>Transforms</guimenu> + <guimenuitem +>Make Notes Viable</guimenuitem> + </menuchoice +></term> + <listitem> + <para +><action +>Splits notes at displayable + durations.</action +> This function is intended to deal + with notes that have excessively long durations that + overflow barlines or that are too long to be displayed + as a single note. It takes any such notes and splits + them into shorter, tied notes. + </para> + </listitem> + </varlistentry> + + <varlistentry id="commands-nv-menu-transforms-de-counterpoint"> + <term +><menuchoice> + <guimenu +>Transforms</guimenu> + <guimenuitem +>De-Counterpoint</guimenuitem> + </menuchoice +></term> + <listitem> + <para +><action +>Turns counterpoint into a series of split-and-tied notes and chords.</action> + + &rosegarden; has no explicit support for counterpoint + (multiple lines of notes edited separately on the + same staff), but it will do its best to approximate + it when it finds notes in a segment that are + apparently contrapuntal, i.e. that overlap but that + are not precise enough to be treated as chords. For + example, when a short note starts shortly after a + longer note, Rosegarden will show the longer note + and a short <quote +>spacing</quote +> rest together, followed by the + shorter note. Unfortunately this often isn't what + you want. + </para> + + <para +>The De-Counterpoint function can be applied to a + selection that contains overlapping notes. It will + split overlapping notes at the point where they + overlap, and tie together the resulting split notes, + ensuring that the music takes the form of a series of + chords and/or single notes starting and ending in neat + blocks, with some notes possibly tied. + </para> + </listitem> + </varlistentry> + + <varlistentry id="commands-nv-menu-transforms-quantize"> + <term +><menuchoice> + <guimenu +>Transforms</guimenu> + <guimenuitem +>Quantize...</guimenuitem> + </menuchoice +></term> + <listitem> + <para +><action +>Quantizes the selection.</action +></para> + </listitem> + </varlistentry> + + <varlistentry id="commands-nv-menu-transforms-fix-smoothing"> + <term +><menuchoice> + <guimenu +>Transforms</guimenu> + <guimenuitem +>Fix Smoothed Values</guimenuitem> + </menuchoice +></term> + <listitem> + <para +><action +>Makes the note durations in the current + view permanent.</action> + + When notating recorded or performance &MIDI;, + Rosegarden usually has to round off the durations of + some notes so that they can be displayed as normal + note types. This is known as <link + linkend="nv-quantization" +>smoothing</link +>, and it + normally does not affect the notes actually played, + it's just a convenience for display. The Fix + Smoothed Values function takes the current smoothed + note durations and sets them such that they are used + for performance (and editing in the matrix view, + etc) as well as for notation. + </para> + </listitem> + </varlistentry> + + <varlistentry id="commands-nv-menu-transforms-interpret"> + <term +><menuchoice> + <guimenu +>Transforms</guimenu> + <guimenuitem +>Interpret...</guimenuitem> + </menuchoice +></term> + <listitem> + <para +><action +>Modifies the velocities and timings of + notes according to any written or indicated dynamics + found.</action +> The selection of interpretations + available is as follows: + + <variablelist> + <varlistentry> + <term +>Apply text dynamics (p, mf, ff etc) + </term> + <listitem +><para +> Sets a velocity to each note + based on the last piece of text of "Dynamic" + type seen on the same staff (only texts of the + form pp, p, mp, mf, f, ff, fff etc are matched). + </para +></listitem> + </varlistentry> + + <varlistentry> + <term +>Apply hairpin dynamics + </term> + <listitem +><para +> Makes the notes gradually + increase or decrease in velocity during a + crescendo or decrescendo hairpin. + </para +></listitem> + </varlistentry> + + <varlistentry> + <term> + Stress beats + </term> + <listitem +><para +> Makes notes that land on bar or + beat boundaries slightly louder (greater + velocity) than the surrounding notes. + </para +></listitem> + </varlistentry> + + <varlistentry> + <term> + Articulate slurs, staccato, tenuto etc + </term> + <listitem +><para +> Shortens unslurred notes, + shortens staccato notes more, and gives notes + inside slurs and tenuto notes their full length. + </para +></listitem> + </varlistentry> + </variablelist> + + </para> + + </listitem> + </varlistentry> + + <varlistentry id="commands-nv-menu-transforms-transpose"> + <term +><menuchoice> + <guimenu +>Transforms</guimenu> + <guimenuitem +>Transpose</guimenuitem> + </menuchoice +></term> + <listitem> + <para +><action +>Alters the pitch of the selected + notes.</action +> This submenu contains basic + transposition functions which move the selected notes + up or down a semitone or a whole octave in pitch, as + well as a general transpose function that allows you + to choose how far up or down you want to transpose the + selection. + </para> + + <para +>These functions simply change the stored pitches + of the notes in the selection, so that they both play + and appear at the new pitches. They do not deal with + performance transposition (displaying one pitch and + playing another), for which see the main window's + segment parameter box; nor do they help you with + transposing from one key into another, for which see + the <link + linkend="commands-nv-menu-edit-add-key-signature" +>key + change</link +> function. + </para> + </listitem> + </varlistentry> + + </variablelist> + </para> + + </sect2> + + + </sect1> + </chapter> + +--> + + + <!-- + ********************************** + + PART III: + Technical material + + ********************************** + --> + + <chapter id="developers"> + <title +>Anpassa Rosegarden</title> + + <sect1 id="developers-note-fonts"> + <title +>Anpassa egna notteckensnitt</title> + + <para +>Om du har ett notteckensnitt installerat på systemet med ett skalbart format (Truetype eller Typ-1) men den för närvarande inte stöds av Rosegarden, kan du skapa din egen XML-avbildningsfil för att beskriva teckensnittets teckenavbildning och mått på ett sätt som Rosegarden kan använda. Filerna installeras i underkatalogen fonts/mappings i Rosegardens installationskatalog, och ett antal exempel ingår i distributionen.</para> + + <para +>Du kan också använda avbildningsfilerna för att definiera nya teckensnitt baserade på punktavbildning, där varje form av en viss storlek laddas från en separat punktavbildningsfil. De två standardteckensnitten för notskrift som levereras med Rosegarden-4 är punktavbildade teckensnitt som definierats exakt på detta sätt. </para> + + <para +>Det är till och med möjligt att definiera ett notteckensnitt att använda en eller flera skalbara systemteckensnitt, förbättrade med punktavbildningar för vissa storlekar eller för tecken som inte finns i de skalbara teckensnitten. Det går eftersom det mesta av avbildningsfilernas format är samma för skalbara och punktavbildade teckensnitt, och när det finns olika element för olika sorters teckensnitt är det oftast möjligt att inkludera båda. Rosegarden använder oftast punktavbildningar om de är tillgängliga, och annars skalbara teckensnitt. </para> + + <para +>Du kanske också vill redigera avbildningsfilerna som levereras med Rosegarden om du tycker att deras mått för justering eller storlek inte passar dig. (Om du tycker att någon av filerna som levereras är felaktig på något sätt, tala gärna om det för oss.) </para> + + <sect2 id="developers-note-fonts-codes-glyphs"> + <title +>Koder och glyfer</title> + + <para +></para> + </sect2> + + <sect2 id="developers-note-fonts-mapping-format"> + <title +>XML-format för avbildning av notteckensnitt</title> + + <para +>Här är en översikt över XML-elementen som kan användas i en teckensnittsavbildningsfil.</para> + + <sect3 id="developers-note-fonts-mapping-format-font-encoding"> + <title +>rosegarden-font-encoding</title> + + <para +>Elementet måste finnas i varje avbildningsfil, och ska innehålla alla övriga element. Det enda attributet är "name" som innehåller teckensnittets namn som visas i kombinationsrutan för teckensnittsval. Även om filformatet tillåter att vilket namn som helst används här, hittar Rosegarden bara teckensnittet på ett riktigt sätt om XML-filen har samma namn som det här attributets innehåll (utom att XML-filen ska namnges med små bokstäver och ska sluta med ".xml"). </para> + </sect3> + + <sect3 id="developers-note-fonts-mapping-format-font-information"> + <title +>font-information</title> + + <para +>Det här ska normalt vara första delelement i "rosegarden-font-encoding". Det kan ha vilket som helst av följande attribut, som alla är valfria: <variablelist> + <varlistentry> + <term +>origin</term> + <listitem> + <para +>En textbeskrivning av det avbildade teckensnittets troliga ursprung (inte ursprunget för avbildningsfilen).</para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>copyright</term> + <listitem> + <para +>En textbaserad beskrivning av trolig copyright-status för det avbildade teckensnittet (inte copyright-status för avbildningsfilen). Observera att eftersom avbildningsfilen innehåller information som ursprung och copyright för själva teckensnittet, är det oftast lämpligt att göra separata avbildningsfiler för separata teckensnitt när det är praktiskt, även om teckensnitten delar annan avbildningsdata.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>mapped-by</term> + <listitem> + <para +>Namnet på skaparen av avbildningsfilen (dvs. antagligen du själv).</para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>type</term> + <listitem> + <para +>Teckensnittets typ. Attributet ska innehålla ett av värdena "pixmap" eller "scalable". Teckensnitt som laddas i fönsterhanteringssystemet och är tillgängliga för Rosegarden som vanliga systemteckensnitt har typen "scalable". Teckensnitt som måste laddas från punktavbildningsfiler som motsvarar individuella storlekar på punktavbildningar (som teckensnitten feta och rg21 som ingår i Rosegarden) har typen "pixmap".</para> + + <para +>Den här informationen är bara avsett som referens för användaren. Den används i själva verket inte av Rosegarden. I praktiken är det legitimt att ett teckensnitt är en blandning av de två, men i allmänhet antar vi i den här dokumentationen att teckensnittet antingen är skalbart eller punktavbildat.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>smooth</term> + <listitem> + <para +>Ett Booleanskt attribut som anger om teckensnittet är kantutjämnat eller inte. Ska ha värdet "true" eller "false". Om teckensnittet är utjämnat, kommer andra element som balkar och legatobågar som inte skapas från teckensnittet att vara kantutjämnade.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>autocrop</term> + <listitem> + <para +>Bara relevant för skalbara (system) teckensnitt. Rosegarden förväntar sig oftast att ett teckensnitts mått innehåller de vertikala minsta omgivande rutor för element som nothuvuden och accenter, istället för att omfatta tomt utrymme ovanför eller under elementen av justeringssyfte. De flesta teckensnitt gör inte vad Rosegarden förväntar sig. Därför ska du ställa in attributet för automatisk beskärning till "true". Då beskär Rosegarden allt onödigt tomt utrymme längst upp och längst ner i elementen när de ritas upp.</para> + </listitem> + </varlistentry> + + </variablelist> + + </para> + </sect3> + + <sect3 id="developers-note-fonts-mapping-format-font-requirements"> + <title +>font-requirements</title> + <para +>Det här elementet är bara relevant för skalbara teckensnitt. Det används för att ange att teckensnittet bara ska erbjudas om vissa systemteckensnitt är tillgängliga, samt att koppla identifikationsvärden med systemteckensnitten att kunna hänvisa till i elementet <link linkend="developers-note-fonts-mapping-format-font-symbol-map" +>font-symbol-map</link +>. Den här metoden används för att bestämma vilka notteckensnitt som användaren ska erbjudas, och dessutom låta dig komponera ett notteckensnitt i Rosegarden från mer än ett systemteckensnitt om du önskar. </para> + <para +>Elementet "font-requirements" ska innehålla en lista med delelementen "font-requirement". Vart och ett av dessa har två attribut: "font-id" som innehåller en numerisk identifikation av ditt val för referenser på andra ställe in filen, och antingen attributet "name" eller "names". Om "name" tillhandahålls, används det som namnet på ett enstaka systemteckensnitt som ska höra ihop med teckensnittsidentifikationen. Om "names" tillhandahålls behandlas det som en lista av systemteckensnitt åtskilda med kommatecken, där det första som hittas kopplas ihop med teckensnittsidentifikationen. </para> + </sect3> + + <sect3 id="developers-note-fonts-mapping-format-font-sizes"> + <title +>font-sizes</title> + + <para +>Elementet "font-sizes" anger vilka storlekar av notteckensnitt som är tillgängliga, och hur den nominella teckenstorleken förhåller sig till storleken på element som inte ingår i teckensnittet, såsom skaft, notsystemlinjer och balkar. Ett notteckensnitts "storlek" antas vara avståndet i bildpunkter mellan notsystemlinjer, eller exaktare, platsen för ett vanligt nothuvud som fullständigt fyller avståndet mellan linjer: Storleken omfattar därför inte tjockleken hos någon av intilliggande notlinjer. </para> + + <para +>Det finns två möjliga delelement till "font-sizes": "font-scale" och "font-size". Deras användning beror på typ av teckensnitt som beskrivs.</para> + + <para +>För punktavbildade (inte skalbara) teckensnitt, ska elementet "font-sizes" innehålla en lista med element "font-size", ett för varje storlek av punktavbilder som är tillgängliga. Punktavbilderna själva måste vara installerade i underkatalogen fonts/<font-name>/<font-size> i Rosegardens installationskatalog, där <font-name> är teckensnittets namn (som det anges i elementet "rosegarden-font-encoding" i avbildningsfilens början), eller en version av namnet med små bokstäver, och <font-size> är teckensnittets bildpunktsstorlek. En teckenstorlek görs bara tillgänglig för användaren om den har en post i listan "font-sizes" och punktavbildningskatalogen hittas. </para> + + <para +>För skalbara teckensnitt ska elementet "font-sizes" innehålla ett element "font-scale" som definierar förhållandet mellan teckensnitt och element som inte hör till teckensnittet på ett allmänt sätt, och också definierar förhållandet mellan Rosegardens nominella teckenstorlek och motsvarande systemteckensnitts storlek. Om elementet "font-scale" hittas, antar Rosegarden att teckensnittet är tillgängligt i alla storlekar. Du kan dock fortfarande inkludera ett eller flera element "font-size" för att definiera exakta proportioner för en särskild storlek där de allmänna proportionerna inte riktigt fungerar rätt, till exempel på grund av avrundningsfel. </para> + + <para +>Attributen till "font-scale" och "font-size" är mycket lika. Den huvudsakliga skillnaden är att alla attribut till "font-scale" är flyttal i förhållande till teckenstorleken, där 1,0 är basstorleken (dvs. avståndet mellan linjer i notsystemet), medan attributen till "font-size" är heltalsvärden av bildpunkter. Tillgängliga attribut är de följande. (De som är markerade som "valfria" har i viss mån rimliga standardvärden, så det är en god idé att inte ange dem först.) </para> + + <variablelist> + + <varlistentry> + <term +>note-height</term> + <listitem> + <para +>Det här attributet är bara tillgängligt för elementet "font-size", och krävs för elementet. Det definierar teckensnittets grundstorlek som andra attribut i elementet gäller, och en storlek som erbjuds användaren och används vid uppslagning av punktavbildningar för teckensnittet.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>font-height</term> + <listitem> + <para +>Kan antingen användas i "font-size" eller "font-scale". Det är bara tillämpligt för skalbara teckensnitt, men krävs för dem om det används i elementet "font-scale". Det anger storleken på systemteckensnittet som används för att rita en given storlek av notteckensnittet.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>beam-thickness</term> + <listitem> + <para +>Valfritt. Anger tjockleken på en balk.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>staff-line-thickness</term> + <listitem> + <para +>Valfritt. Anger tjockleken på en notsystemslinje.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>stem-thickness</term> + <listitem> + <para +>Valfritt. Anger tjockleken på ett notskaft.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>flag-spacing</term> + <listitem> + <para +>Valfritt. Anger avståndet mellan notflaggor i de fall då flera flaggor ritas genom att upprepa en enstaka flagga flera gånger.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>border-x</term> + <listitem> + <para +>Valfritt. Anger att nothuvudets punktavbildning har ett fast område till vänster och höger som inte ska anses vara en del av nothuvudet. Attributet anger områdets tjocklek.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>border-y</term> + <listitem> + <para +>Valfritt. Anger att nothuvudets punktavbildning har ett fast område ovanför och under som inte ska anses vara en del av nothuvudet. Attributet anger områdets tjocklek.</para> + </listitem> + </varlistentry> + + </variablelist> + </sect3> + + <sect3 id="developers-note-fonts-mapping-format-font-symbol-map"> + <title +>font-symbol-map</title> + <para +>Det här elementet listar symbolerna som är tillgängliga i notteckensnittet, och vilka punktavbildningsfiler eller vilka kodpunkter i ett systemteckensnitt som de ska ritas upp med.</para> + + <para +>Det ska innehålla en lista med "symbol" element. De har flera möjliga attribut, där valet av vilka normalt beror på om teckensnittet är baserat på punktavbildningar eller systemteckensnitt: </para> + + <variablelist> + <varlistentry> + <term +>name</term> + <listitem> + <para +>Krävs. Det här attributet ska innehålla namnet på notsymbolen. Om symbolen finns i <ulink url="http://www.unicode.org/charts/PDF/U1D100.pdf" +>Unicode 3.2 standarden</ulink +>, ska namnet som används för att identifiera symbolen vara det som används i standarden.</para> + + <para +>De flesta symboler som Rosegarden förväntar sig att hitta ingår i standarden. Ett undantag är att många teckensnitt har en specialversion av flaggsymbolen som är avsedd att användas när flera flaggor skapas från individuella enstaga flaggor. Rosegarden kallar den för "MUSICAL SYMBOL COMBINING FLAG-0", ett namn som inte används av Unicode-standarden (som bara har flaggorna 1 - 5).</para> + + <para +>För den fullständiga uppsättningen symbolnamn som Rosegarden känner till, se filen "gui/notecharname.cpp" i Rosegardens källkodsdistribution. Observera dock att det är möjligt att använda ytterligare symbolnamn genom att lägga till dem i en <link linkend="developers-note-styles" +>notationsstil</link +>. </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>src</term> + <listitem> + <para +>Namnet på punktavbildningsfilen som ska användas för att ladda symbolen, utan katalog eller filändelse. Det är det vanliga sättet att beskriva en symbol i ett punktavbildat teckensnitt. Själva filen ska installeras i fonts/<teckensnittsnamn>/<teckenstorlek>/<källa>.xpm under Rosegardens installationskatalog. </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>inversion-src</term> + <listitem> + <para +>Namnet på en punktavbildningsfil som kan användas för att ladda en inverterad version av symbolen, utan katalog eller filändelse. Om attributet saknas och en inverterad version av symbolen behövs, skapas den helt enkelt genom att ladda den normala versionen och spegla den i den centrala x-axeln. </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>code</term> + <listitem> + <para +>Kodpunkten där symbolen kan hittas i relevant systemteckensnitt, som ett decimalt heltal. Det är ett sätt att beskriva en symbol i ett skalbart teckensnitt. Attributet används bara om ingen punktavbildningsfil tillhandahålls, eller om laddning av punktavbildningsfilen misslyckas. </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>inversion-code</term> + <listitem> + <para +>Kodpunkten där en inverterad version av symbolen kan hittas i relevant systemteckensnitt. Om attributet saknas och en inverterad version av symbolen behövs, skapas den helt enkelt genom att ladda den normala versionen och spegla den i den centrala x-axeln. </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>glyph</term> + <listitem> + <para +>Det obehandlade indexet för glyfen där symbolen kan hittas i relevant systemteckensnitt, som ett decimalt heltal. Det är ett sätt att beskriva en symbol i ett skalbart teckensnitt. Attributet används bara om ingen punktavbildningsfil tillhandahålls, eller om laddning av punktavbildningsfilen misslyckas. </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>inversion-glyph</term> + <listitem> + <para +>Det obehandlade indexet för glyfen där en inverterad version av symbolen kan hittas i relevant systemteckensnitt. Om attributet saknas och en inverterad version av symbolen behövs, skapas den helt enkelt genom att ladda den normala versionen och spegla den i den centrala x-axeln. </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>font-id</term> + <listitem> + <para +>Identifikationen för systemteckensnittet som den här symbolen ska laddas från, som det är definierat i elementet <link linkend="developers-note-fonts-mapping-format-font-requirements" +>font-requirements</link +>. Normalvärdet är 0. </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>codebase</term> + <listitem> + <para +>Det här attributet (ett decimalt heltal) kan vara användbart om många av symbolerna i ett skalbart teckensnitt täcker ett kort område med kodpunkter med början på en relativt hög kodsida. Om det anges, läggs värdet codebase till för vart och ett av efterföljande värden på code och inversion-code när en symbol slås upp. </para> + </listitem> + </varlistentry> + + </variablelist> + + <para +>Även om inget av attributen krävs, förutom namnet, måste en symbol uppenbarligen tillhandahålla åtminstone en av "src", "inversion-src", "code", "inversion-code", "glyph" eller "inversion-glyph" för att ha någon möjlighet att överhuvudtaget ritas upp. Det är förstås fullständig legitimt att tillhandahålla flera eller alla dessa attribut. </para> + + </sect3> + + <sect3 id="developers-note-fonts-mapping-format-font-hotspots"> + <title +>font-hotspots</title> + <para +> </para> + </sect3> + + </sect2> + + </sect1> + + <sect1 id="developers-note-styles"> + <title +>Skapa nya notstilar</title> + + <para +>Rosegardens notbehandlare har möjlighet att visa och redigera noter med olika standardstilar: klassisk, rombformade huvuden och så vidare. Alla stilar definieras i definitionsfiler på XML-form som installeras tillsammans med programmet, och det är möjligt att skapa en ny genom att skriva en enkel XML-fil. Rosegarden tittar helt enkelt på uppsättningen installerade filer för att avgöra vilka stilar som användaren ska erbjudas. Du kan till exempel hänvisa till standarduppsättningen med filer i underkatalogen för stilar i Rosegardens installationskatalog. </para> + + <para +>Filformatet är inte ännu särskilt omfattande. För ögonblicket är det konstruerat för att vara kraftfullt nog att beskriva standardstilarna som levereras med Rosegarden, men inte mycket mer. Om du gör ett försök att skapa nya stilar på det här sättet, är vi mycket intresserade av din återmatning via Rosegardens e-postlistor. </para> + + <sect2 id="developers-note-styles-format"> + <title +>XML-format för notstil</title> + + <para +>Här är en översikt över XML-elementen som kan användas i en stildefinitionsfil. </para> + + <sect3 id="developers-note-styles-note-style"> + <title +>rosegarden-note-style</title> + + <para +>Det här elementet måste finnas i alla stilfiler, och ska innehålla alla övriga element. Det har ett valfritt attribut, "base-style", som kan användas för att namnge en stil där den här stilen hämtar standardvärden för alla parametrar som inte anges någon annanstans i den befintliga filen. Det är ofta lämpligt att definiera en stil i form av minsta möjliga skillnader från en given basstil. Se filen Cross.xml som tillhandahålls, för ett särskilt enkelt exempel. </para> + + <para +>Observera att elementet "rosegarden-note-style" inte anger namnet på stilen som definieras, som istället tas från filens namn. Någon gång i framtiden kanske stöd för översättning av stilnamn läggs till i det här elementets attribut.</para> + </sect3> + + <sect3 id="developers-note-styles-global-note"> + <title +>global, note</title> + + <para +>I elementet "rosegarden-note-style" kan det finnas ett "global" element och hur många "note" element som helst. De beskrivs tillsammans, eftersom de har nästan identiska uppsättningar attribut. Elementet "global" tillhandahåller helt enkelt standardvärden för de parametrar som inte anges för en viss nottyp i något av följande "note" element. </para> + + <para +>Attributen för elementen är följande. Alla är valfria utom enligt beskrivningen:</para> + + <variablelist> + + <varlistentry> + <term +>type</term> + <listitem> + <para +>Gäller bara elementet "note", och krävs för det elementet. Det här attributet anger vilken sorts not som stilen gäller för. Giltiga värden är tonnamn på amerikansk eller brittisk engelska (från "64th", "sixth-fourth note", "hemidemisemiquaver" etc till "double whole note"). </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>shape</term> + <listitem> + <para +>Definierar en form för nothuvudet i den här stilen. Vilken sträng som helst är ett giltigt värde, men de enda värden som hittills är implementerade är "angled oval", "level oval", "breve", "cross", "triangle up", "triangle down", "diamond" och "rectangle". Värdet "number" känns också igen, men är ännu inte implementerat. </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>charname</term> + <listitem> + <para +>Definierar ett teckennamn i notteckensnittet som ska användas som nothuvud för stilen. Ett element kan tillhandahålla attributet "shape" eller "charname", men inte båda. Namnet ska vara ett av de som definieras i det nuvarande notskriftteckensnittets <link linkend="developers-note-fonts-mapping-format-font-symbol-map" +>symbol map</link +> (i ett attribut "name"). </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>filled</term> + <listitem> + <para +>Anger om noten ska ha ett ifyllt huvud (när det är tillämpligt, dvs. när formegenskapen anger en form som både är tillgänglig ifylld och inte). Måste vara "true" eller "false". </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>stem</term> + <listitem> + <para +>Anger om noten ska ha ett skaft. Måste vara "true" eller "false". </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>flags</term> + <listitem> + <para +>Anger hur många flaggor eller balkar som noten ska ha. Giltigt intervall är 0 till 4. </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>slashes</term> + <listitem> + <para +>Anger hur många tvärbalkar noten ska ha över skaftet. </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>hfixpoint</term> + <listitem> + <para +>Anger på vilken x-position som skaftet ansluts till nothuvudet. Acceptabla värden är "normal" (höger sida när skaftet pekar uppåt, vänster sida när det pekar neråt), "central" och "reversed" (vänster sida när skaftet pekar uppåt, höger sida när det pekar neråt). </para> + </listitem> + </varlistentry> + + <varlistentry> + <term +>vfixpoint</term> + <listitem> + <para +>Anger på vilken y-position som skaftet ansluts till nothuvudet. Acceptabla värden är "near" (skaftet ansluts till toppen när det pekar uppåt, till botten när det pekar neråt), "middle" eller "far". </para> + </listitem> + </varlistentry> + + </variablelist> + </sect3> + </sect2> + </sect1> + + + <!-- (OPTIONAL) A Programming/Scripting reference chapter should be + used for apps that use plugins or that provide their own scripting hooks + and/or development libraries. --> + + <!-- cc: I think we should document the DCOP API here, but I don't + think we should include extensive developer docs, although we should + point to where they can be found in the source tree or online. --> + <!-- + <para> + Programming <application +>Rosegarden</application +> plugins is + a joy to behold. Just read through the next + 66 pages of <acronym +>API</acronym +>'s to learn how! + </para> + --> + <!-- Use refentries to describe APIs. Refentries are fairly + complicated and you should consult the docbook reference for + further details. The example below was taken from that reference + and shortened a bit for readability. --> + <!-- + <refentry id="re-1007-unmanagechildren-1"> + <refmeta> + <refentrytitle +>XtUnmanageChildren</refentrytitle> + <refmiscinfo +>Xt – Geometry Management</refmiscinfo> + </refmeta> + <refnamediv> + <refname +>XtUnmanageChildren + </refname> + <refpurpose +>remove a list of children from a parent widget's managed list. + </refpurpose> + </refnamediv> + <refsynopsisdiv> + <refsynopsisdivinfo> + <date +>4 March 1996</date> + </refsynopsisdivinfo> + <synopsis +> + void XtUnmanageChildren(<replaceable>children</replaceable>, <replaceable>num_children</replaceable>) + WidgetList <replaceable>children</replaceable>; + Cardinal <replaceable>num_children</replaceable>; + </synopsis> + + <refsect2 id="r2-1007-unmanagechildren-1"> + <title +>Inputs</title> + <variablelist> + <varlistentry> + <term +><replaceable +>children</replaceable> + </term> + <listitem> + <para> + Specifies an array of child widgets. Each child must be of + class RectObj or any subclass thereof. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term +><replaceable +>num_children</replaceable> + </term> + <listitem> + <para +>Specifies the number of elements in <replaceable +>children</replaceable +>. + </para> + </listitem> + </varlistentry> + </variablelist> + </refsect2 +></refsynopsisdiv> + + <refsect1 id="r1-1007-unmanagechildren-1"> + <title +>Description + </title> + <para> + <function +>XtUnmanageChildren()</function +> unmaps the specified widgets + and removes them from their parent's geometry management. + The widgets will disappear from the screen, and (depending + on its parent) may no longer have screen space allocated for + them. + </para> + <para +>Each of the widgets in the <replaceable +>children</replaceable +> array must have + the same parent. + </para> + <para +>See the “Algorithm” section below for full details of the + widget unmanagement procedure. + </para> + </refsect1> + + <refsect1 id="r1-1007-unmanagechildren-2"> + <title +>Usage</title> + <para> + Unmanaging widgets is the usual method for temporarily + making them invisible. They can be re-managed with + <function +>XtManageChildren()</function +>. + </para> + <para> + You can unmap a widget, but leave it under geometry + management by calling <function +>XtUnmapWidget()</function +>. You can + destroy a widget's window without destroying the widget by + calling <function +>XtUnrealizeWidget()</function +>. You can destroy a + widget completely with <function +>XtDestroyWidget()</function +>. + </para> + <para> + If you are only going to unmanage a single widget, it is + more convenient to call <function +>XtUnmanageChild()</function +>. It is + often more convenient to call <function +>XtUnmanageChild()</function> + several times than it is to declare and initialize an array + of widgets to pass to <function +>XtUnmanageChildren()</function +>. Calling + <function +>XtUnmanageChildren()</function +> is more efficient, however, + because it only calls the parent's <function +>change_managed()</function> + method once. + </para> + </refsect1> + + <refsect1 id="r1-1007-unmanagechildren-3"> + <title +>Algorithm + </title> + <para +><function +>XtUnmanageChildren()</function +> performs the following: + </para> + <variablelist> + <varlistentry> + <term +>- + </term> + <listitem> + <para +>Ignores the child if it already is unmanaged or is being + destroyed. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term +>- + </term> + <listitem> + <para +>Otherwise, if the child is realized, it makes it nonvisible + by unmapping it. + </para> + </listitem> + </varlistentry> + </variablelist> + + </refsect1> + + <refsect1 id="r1-1007-unmanagechildren-4"> + <title +>Structures</title> + <para> + The <type +>WidgetList</type +> type is simply an array of widgets: + </para> + <screen id="sc-1007-unmanagechildren-1" +> + typedef Widget *WidgetList; + </screen> + </refsect1> + </refentry> + --> + </chapter> + + + <chapter id="credits"> + + <title +>Tack till och licens</title> + + <para> + <application +>Rosegarden</application> + </para> + <para> + <itemizedlist> + <listitem> + <para +>Rosegarden-4 är Copyright 2000-2004 Guillaume Laurent, Chris Cannam och Richard Bown. Moralisk rättighet att identifieras som upphovsmän till det här verket hävdas av Guillaume Laurent, Chris Cannam och Richard Bown. </para> + </listitem> + + <listitem> + <para +>Delar av Rosegarden-4 är härledda från Rosegarden 2.1, som är Copyright 1994 – 2001 Chris Cannam, Andrew Green, Richard Bown och Guillaume Laurent. </para> + </listitem> + + <listitem> + <para +>För visning av musikalisk notskrift använder Rosegarden-4 punktavbildningar härledda från teckensnittet Feta, som är en del av programvaran <ulink url="http://lilypond.org/" +>Lilypond</ulink +>, som är Copyright 1997 – 2001 Jan Nieuwenhuizen och Han-Wen Nienhuys. </para> + </listitem> + + <listitem> + <para +>Bland andra väsentliga bidragsgivare finns Randall Farmer, Ron Kuris, Hans Kieserman och Michael McIntyre. </para> + </listitem> + + <listitem> + <para +>Rosegardens startskärm kommer från ett vykort av Thornden-parken vid Syracuse-universitetet i Syracuse, New York, tryckt år 1900. Tack till personalen på Syracuse-universitetet för användning av det. </para> + </listitem> + + </itemizedlist> + </para> + + <para +>Dokumentation copyright 2002-2004 Chris Cannam, Richard Bown, Guillaume Laurent </para> + <!-- + <para> + Translations done by: + <itemizedlist> + <listitem> + <para +>Babel D. Fish <email +>babelfish@kde.org</email +> (Sanskrit)</para> + </listitem> + </itemizedlist> + </para> + --> + <!-- For URL links to common stuff like the one below, + always use paths like "common/gpl-licence". + In this path, "common" will be a symbolic link built at "make install" time. + This link will normally point to $KDEDIR/share/doc/HTML/en/common, + where "en" should be replaced with the current language. --> + + <para +>Det här programmet distribueras under villkoren i <ulink url="common/gpl-license.html" +>GNU General Public License</ulink +>. </para> + </chapter> + + <!-- Note that the revhistory tags apply to the documentation + version and not to the app version. That is why we use an + ItemizedList instead for this list of revisions to the app. --> + + <chapter id="rosegarden-revhistory"> + <title +>Rosegarden-4 utgåvehistorik</title> + <para> + <itemizedlist> + <listitem +><para +>0.9.9 – juli 2004: syntinsticksmoduler, utlösande segment, notationsförbättringar </para +></listitem> + <listitem +><para +>0.9.8 – maj 2004: bättre ljuddelsystem </para +></listitem> + <listitem +><para +>0.9.7 – februari 2004: </para +></listitem> + <listitem +><para +>0.9.6 – december 2003: felrättningar </para +></listitem> + <listitem +><para +>0.9.5 – november 2003: en hel del saker </para +></listitem> + <listitem +><para +>0.9.1 – maj 2003: stegvis inspelning, MUP-export, många många felrättningar </para +></listitem> + <listitem +><para +>0.9 – april 2003: många förbättringar av notation, förbättrad bankeditor, ljudförbättringar och förfiningar, översättningar </para +></listitem> + <listitem +><para +>0.8.5 – december 2002: bankeditor, MIDI-filter, panikknapp </para +></listitem> + <listitem +><para +>0.8 – oktober 2002: utskrift, LADSPA-insticksmoduler, förbättrad matrisvy </para +></listitem> + <listitem +><para +>0.2.0 – augusti 2002: WAV-filstöd, markering med svepning, kontrapunkt </para +></listitem> + <listitem +><para +>0.1.6 – juni 2002: inställningsdialogruta, Lilypond-stöd, kvantiseringsdialogruta </para +></listitem> + <listitem +><para +>0.1.5 – maj 2002: KDE 3, ALSA-stöd, JACK-ljudstöd </para +></listitem> + <listitem +><para +>0.1.4 – mars 2002: mer ångra, segmentredigering, ljuduppspelning </para +></listitem> + <listitem +><para +>0.1.3 – januari 2002: pianorulle och matrisvy, &MIDI;-inspelning </para +></listitem> + <listitem +><para +>0.1.2 – november 2001: ångra notation, transportdialogruta, positionspekare </para +></listitem> + <listitem +><para +>0.1.1 – oktober 2001: skalbar notation </para +></listitem> + <listitem +><para +>0.1 – juni 2001: första öppna utgåva av Rosegarden-4 </para +></listitem> + </itemizedlist> + </para> + </chapter> + + &documentation.index; +</book> diff --git a/doc/sv/rg-audiofilemanager.png b/doc/sv/rg-audiofilemanager.png Binary files differnew file mode 100644 index 0000000..0246b9d --- /dev/null +++ b/doc/sv/rg-audiofilemanager.png diff --git a/doc/sv/rg-audiomixer.png b/doc/sv/rg-audiomixer.png Binary files differnew file mode 100644 index 0000000..aa016dd --- /dev/null +++ b/doc/sv/rg-audiomixer.png diff --git a/doc/sv/rg-bankeditor.png b/doc/sv/rg-bankeditor.png Binary files differnew file mode 100644 index 0000000..8521244 --- /dev/null +++ b/doc/sv/rg-bankeditor.png diff --git a/doc/sv/rg-clefdialog.png b/doc/sv/rg-clefdialog.png Binary files differnew file mode 100644 index 0000000..481af7c --- /dev/null +++ b/doc/sv/rg-clefdialog.png diff --git a/doc/sv/rg-colours.png b/doc/sv/rg-colours.png Binary files differnew file mode 100644 index 0000000..48426f5 --- /dev/null +++ b/doc/sv/rg-colours.png diff --git a/doc/sv/rg-devicemanager.png b/doc/sv/rg-devicemanager.png Binary files differnew file mode 100644 index 0000000..d90a751 --- /dev/null +++ b/doc/sv/rg-devicemanager.png diff --git a/doc/sv/rg-eventlisteditor.png b/doc/sv/rg-eventlisteditor.png Binary files differnew file mode 100644 index 0000000..cd3734a --- /dev/null +++ b/doc/sv/rg-eventlisteditor.png diff --git a/doc/sv/rg-gridquantizer.png b/doc/sv/rg-gridquantizer.png Binary files differnew file mode 100644 index 0000000..8567e39 --- /dev/null +++ b/doc/sv/rg-gridquantizer.png diff --git a/doc/sv/rg-ipb-audio.png b/doc/sv/rg-ipb-audio.png Binary files differnew file mode 100644 index 0000000..f35be3a --- /dev/null +++ b/doc/sv/rg-ipb-audio.png diff --git a/doc/sv/rg-ipb-midi.png b/doc/sv/rg-ipb-midi.png Binary files differnew file mode 100644 index 0000000..a701cee --- /dev/null +++ b/doc/sv/rg-ipb-midi.png diff --git a/doc/sv/rg-ipb-synth.png b/doc/sv/rg-ipb-synth.png Binary files differnew file mode 100644 index 0000000..7a0306c --- /dev/null +++ b/doc/sv/rg-ipb-synth.png diff --git a/doc/sv/rg-keysigdialog.png b/doc/sv/rg-keysigdialog.png Binary files differnew file mode 100644 index 0000000..0dd3e6f --- /dev/null +++ b/doc/sv/rg-keysigdialog.png diff --git a/doc/sv/rg-mainwindow.png b/doc/sv/rg-mainwindow.png Binary files differnew file mode 100644 index 0000000..f2b3b2f --- /dev/null +++ b/doc/sv/rg-mainwindow.png diff --git a/doc/sv/rg-matrixview.png b/doc/sv/rg-matrixview.png Binary files differnew file mode 100644 index 0000000..ecbafef --- /dev/null +++ b/doc/sv/rg-matrixview.png diff --git a/doc/sv/rg-metronome.png b/doc/sv/rg-metronome.png Binary files differnew file mode 100644 index 0000000..ece7323 --- /dev/null +++ b/doc/sv/rg-metronome.png diff --git a/doc/sv/rg-midifilter.png b/doc/sv/rg-midifilter.png Binary files differnew file mode 100644 index 0000000..61844da --- /dev/null +++ b/doc/sv/rg-midifilter.png diff --git a/doc/sv/rg-midimixer.png b/doc/sv/rg-midimixer.png Binary files differnew file mode 100644 index 0000000..1b725bb --- /dev/null +++ b/doc/sv/rg-midimixer.png diff --git a/doc/sv/rg-notationquantizer.png b/doc/sv/rg-notationquantizer.png Binary files differnew file mode 100644 index 0000000..b1317f4 --- /dev/null +++ b/doc/sv/rg-notationquantizer.png diff --git a/doc/sv/rg-notationview-multipage.png b/doc/sv/rg-notationview-multipage.png Binary files differnew file mode 100644 index 0000000..7f750b9 --- /dev/null +++ b/doc/sv/rg-notationview-multipage.png diff --git a/doc/sv/rg-notationview.png b/doc/sv/rg-notationview.png Binary files differnew file mode 100644 index 0000000..ca4132d --- /dev/null +++ b/doc/sv/rg-notationview.png diff --git a/doc/sv/rg-pastedialog.png b/doc/sv/rg-pastedialog.png Binary files differnew file mode 100644 index 0000000..fba3675 --- /dev/null +++ b/doc/sv/rg-pastedialog.png diff --git a/doc/sv/rg-plugin-dialog.png b/doc/sv/rg-plugin-dialog.png Binary files differnew file mode 100644 index 0000000..2cd76ac --- /dev/null +++ b/doc/sv/rg-plugin-dialog.png diff --git a/doc/sv/rg-pluginbuttons.png b/doc/sv/rg-pluginbuttons.png Binary files differnew file mode 100644 index 0000000..2a780c7 --- /dev/null +++ b/doc/sv/rg-pluginbuttons.png diff --git a/doc/sv/rg-plugineditorbutton.png b/doc/sv/rg-plugineditorbutton.png Binary files differnew file mode 100644 index 0000000..45c2c99 --- /dev/null +++ b/doc/sv/rg-plugineditorbutton.png diff --git a/doc/sv/rg-segmentparameterbox.png b/doc/sv/rg-segmentparameterbox.png Binary files differnew file mode 100644 index 0000000..46bbd9d --- /dev/null +++ b/doc/sv/rg-segmentparameterbox.png diff --git a/doc/sv/rg-synthpluginbuttons.png b/doc/sv/rg-synthpluginbuttons.png Binary files differnew file mode 100644 index 0000000..b66d5ca --- /dev/null +++ b/doc/sv/rg-synthpluginbuttons.png diff --git a/doc/sv/rg-tempodialog.png b/doc/sv/rg-tempodialog.png Binary files differnew file mode 100644 index 0000000..f8a689c --- /dev/null +++ b/doc/sv/rg-tempodialog.png diff --git a/doc/sv/rg-timesigdialog.png b/doc/sv/rg-timesigdialog.png Binary files differnew file mode 100644 index 0000000..3c08ec8 --- /dev/null +++ b/doc/sv/rg-timesigdialog.png diff --git a/doc/sv/rg-trackbutton-instruments.png b/doc/sv/rg-trackbutton-instruments.png Binary files differnew file mode 100644 index 0000000..cdf1534 --- /dev/null +++ b/doc/sv/rg-trackbutton-instruments.png diff --git a/doc/sv/rg-trackbutton-labels.png b/doc/sv/rg-trackbutton-labels.png Binary files differnew file mode 100644 index 0000000..252d975 --- /dev/null +++ b/doc/sv/rg-trackbutton-labels.png diff --git a/doc/sv/rg-trackeditor.png b/doc/sv/rg-trackeditor.png Binary files differnew file mode 100644 index 0000000..56ef343 --- /dev/null +++ b/doc/sv/rg-trackeditor.png diff --git a/doc/sv/rg-transport.png b/doc/sv/rg-transport.png Binary files differnew file mode 100644 index 0000000..26d5b76 --- /dev/null +++ b/doc/sv/rg-transport.png diff --git a/doc/sv/rg-tupletdialog.png b/doc/sv/rg-tupletdialog.png Binary files differnew file mode 100644 index 0000000..9625c00 --- /dev/null +++ b/doc/sv/rg-tupletdialog.png diff --git a/doc/sv/rosegarden.po b/doc/sv/rosegarden.po new file mode 100644 index 0000000..3c37a3b --- /dev/null +++ b/doc/sv/rosegarden.po @@ -0,0 +1,7454 @@ +# translation of rosegarden.po to Swedish +# +# Stefan Asserhäll <stefan.asserhall@comhem.se>, 2005, 2006. +msgid "" +msgstr "" +"Project-Id-Version: rosegarden\n" +"POT-Creation-Date: 2006-01-06 12:01+0000\n" +"PO-Revision-Date: 2006-01-06 19:07+0100\n" +"Last-Translator: Stefan Asserhäll <stefan.asserhall@comhem.se>\n" +"Language-Team: Swedish <sv@li.org>\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: KBabel 1.11.1\n" + +#. Tag: title +#: index.docbook:204 +#, no-c-format +msgid "The Rosegarden Handbook" +msgstr "Handbok Rosegarden" + +#. Tag: author +#: index.docbook:206 +#, no-c-format +msgid "<firstname>Chris</firstname> <surname>Cannam</surname>" +msgstr "<firstname>Chris</firstname> <surname>Cannam</surname>" + +#. Tag: author +#: index.docbook:210 +#, no-c-format +msgid "<firstname>Richard</firstname> <surname>Bown</surname>" +msgstr "<firstname>Richard</firstname> <surname>Bown</surname>" + +#. Tag: author +#: index.docbook:214 +#, no-c-format +msgid "<firstname>Guillaume</firstname> <surname>Laurent</surname>" +msgstr "<firstname>Guillaume</firstname> <surname>Laurent</surname>" + +#. Tag: trans_comment +#: index.docbook:218 +#, no-c-format +msgid "ROLES_OF_TRANSLATORS" +msgstr "" +"<othercredit role=\"translator\"> <firstname>Stefan</firstname> " +"<surname>Asserhäll</surname> " +"<affiliation><address><email>stefan.asserhall@comhem.se</email></address></af" +"filiation> <contrib>Översättare</contrib></othercredit>" + +#. Tag: holder +#: index.docbook:223 +#, no-c-format +msgid "Chris Cannam, Richard Bown, Guillaume Laurent" +msgstr "Chris Cannam, Richard Bown, Guillaume Laurent" + +#. Tag: phrase +#: index.docbook:237 +#, no-c-format +msgid "&rosegarden;" +msgstr "&rosegarden;" + +#. Tag: para +#: index.docbook:239 +#, no-c-format +msgid "" +"Rosegarden is an audio and &MIDI; sequencer and musical notation editor. " +"This Handbook describes how to use it." +msgstr "" +"Rosegarden är ett program för ljud- och &MIDI;-inspelning och en editor " +"för musikalisk notskrift. Den här handboken beskriver hur det används." + +#. Tag: keyword +#: index.docbook:249 +#, no-c-format +msgid "<keyword>Rosegarden</keyword>" +msgstr "<keyword>Rosegarden</keyword>" + +#. Tag: keyword +#: index.docbook:250 +#, no-c-format +msgid "sequencer" +msgstr "musikbehandlare" + +#. Tag: keyword +#: index.docbook:251 +#, no-c-format +msgid "MIDI" +msgstr "MIDI" + +#. Tag: keyword +#: index.docbook:252 +#, no-c-format +msgid "audio" +msgstr "ljud" + +#. Tag: keyword +#: index.docbook:253 +#, no-c-format +msgid "music" +msgstr "musik" + +#. Tag: keyword +#: index.docbook:254 +#, no-c-format +msgid "notation" +msgstr "beteckning" + +#. Tag: keyword +#: index.docbook:255 +#, no-c-format +msgid "score" +msgstr "partitur" + +#. Tag: keyword +#: index.docbook:256 +#, no-c-format +msgid "<keyword>KDE</keyword>" +msgstr "<keyword>KDE</keyword>" + +#. Tag: title +#: index.docbook:272 index.docbook:2458 index.docbook:3918 +#, no-c-format +msgid "Introduction" +msgstr "Inledning" + +#. Tag: title +#: index.docbook:275 +#, no-c-format +msgid "About Rosegarden" +msgstr "Om Rosegarden" + +#. Tag: para +#: index.docbook:276 +#, no-c-format +msgid "" +"<application>Rosegarden</application> is a &MIDI; and audio sequencer and " +"musical notation editor. Rosegarden allows you to record, arrange, and " +"compose music, in the shape of traditional score or &MIDI; data, or of audio " +"files either imported or recorded from a microphone, guitar or whatever " +"audio source you care to specify. You can use Rosegarden to write, edit, and " +"organise music to create a composition, which you can then synthesise, add " +"effects to, and mix down for burning to CD or distribution on the web. " +"Rosegarden also contains professional notation editing support for high " +"quality printed output." +msgstr "" +"<application>Rosegarden</application> är ett program för ljud- och " +"&MIDI;-inspelning och en editor för musikalisk notskrift. Rosegarden låter " +"dig spela in, arrangera och komponera musik, i form av ett traditionellt " +"partitur eller &MIDI;-data, eller ljudfiler som antingen importeras eller " +"spelas in via en mikrofon, gitarr eller vilken ljudkälla du önskar. Du kan " +"använda Rosegarden för att skriva, redigera och organisera musik för att " +"skapa en komposition, som du därefter kan syntetisera, lägga till effekter " +"i och mixa för att bränna till en cd eller distribuera på webben. Rosegarden " +"innehåller också professionellt stöd för notredigering för utskrift med hög " +"kvalitet." + +#. Tag: para +#: index.docbook:289 +#, no-c-format +msgid "" +"<application>Rosegarden</application> is designed to look and act in a " +"manner familiar to experienced users coming to Linux from other platforms, " +"whilst also being accessible and friendly to users new to music software " +"generally." +msgstr "" +"<application>Rosegarden</application> är konstruerat för att se ut som och " +"fungera på ett sätt som är bekant för erfarna användare som kommer till " +"Linux från andra plattformar, medan det också är tillgängligt och " +"användarvänligt för de som är nykomlingar till musikprogramvara i " +"allmänhet." + +#. Tag: title +#: index.docbook:297 +#, no-c-format +msgid "About this Handbook" +msgstr "Om den här handboken" + +#. Tag: para +#: index.docbook:298 +#, no-c-format +msgid "" +"This handbook summarises the capabilities of &rosegarden; and provides a " +"reference for some of the concepts involved. It's designed to make sense " +"either read in order or used as a reference to the concepts and functions " +"available in Rosegarden. If you would like to read a tutorial as well, " +"<ulink " +"url=\"http://www.rosegardenmusic.com/resources/tutorial/using_en.shtml\">you " +"can find one here</ulink>." +msgstr "" +"Den här handboken ger en översikt av &rosegarden;s möjligheter, och " +"tillhandahåller en referens för en del av de begrepp som ingår. Den är " +"skapad för att antingen vara meningsfull när den läses i en följd, eller " +"när den används som en referens till begrepp och tillgängliga funktioner " +"i Rosegarden. Om du dessutom vill läsa en handledning, <ulink " +"url=\"http://www.rosegardenmusic.com/resources/tutorial/using_en.shtml\">hitt" +"ar du en här</ulink>." + +#. Tag: para +#: index.docbook:307 +#, no-c-format +msgid "" +"If there's something else that you don't understand or require further help " +"with, please visit <ulink " +"url=\"http://www.rosegardenmusic.com/support/\">the Rosegarden " +"website</ulink> for Frequently Asked Questions and mailing list instructions." +msgstr "" +"Om det finns något annat du inte förstår eller något du behöver " +"ytterligare hjälp med, besök gärna <ulink " +"url=\"http://www.rosegardenmusic.com/support/\">Rosegardens " +"webbplats</ulink> för vanliga frågor och instruktioner om användning av " +"e-postlistan." + +#. Tag: title +#: index.docbook:316 +#, no-c-format +msgid "About Menus and Shortcuts" +msgstr "Om menyer och snabbtangenter" + +#. Tag: para +#: index.docbook:316 +#, no-c-format +msgid "" +"This handbook usually refers to the functions you can use in Rosegarden by " +"describing where they live on the menus. For example, the function to add a " +"single new track to the main track editor is <menuchoice> <guimenu " +"lang=\"en\">Tracks</guimenu> <guimenuitem>Add Track</guimenuitem> " +"</menuchoice>." +msgstr "" +"Handboken hänvisar oftast till funktionerna du kan använda i Rosegarden " +"genom att beskriva var de befinner sig i menyerna. Funktionen för att " +"lägga till ett enstaka nytt spår i huvudspåreditorn är exempelvis " +"<menuchoice><guimenu lang=\"sv\">Spår</guimenu> <guimenuitem>Lägg till " +"spår</guimenuitem></menuchoice>." + +#. Tag: para +#: index.docbook:325 +#, no-c-format +msgid "" +"In many cases, this is not the only way to reach a particular function. In " +"this case the same function is also available through the keyboard shortcut " +"Ctrl+T, and it also appears as an icon on one of the main window's toolbars. " +"Both the keyboard shortcut and the icon can quickly be learned, because they " +"are shown on the menu in Rosegarden alongside the name of the function. You " +"should bear in mind that although we always give the full menu location in " +"this documentation for reference purposes, it's not necessarily the best or " +"most usual way to use a function, and you should keep an eye on the keyboard " +"shortcuts or toolbar icons as well." +msgstr "" +"I många fall är det inte det enda sättet att nå en viss funktion. I det " +"här fallet är samma funktion också tillgänglig via snabbtangenten " +"Ctrl+T, och den visas också som en ikon i en av huvudfönstrets " +"verktygsrader. Både snabbtangenten och ikonen kan snabbt läras in, " +"eftersom de visas i Rosegardens meny tillsammans med funktionens namn. Du " +"bör komma ihåg att även om vi alltid anger det fullständiga " +"menyalternativet i dokumentationen av referensskäl, är det inte " +"nödvändigtvis det bästa eller det vanligaste sättet att använda en " +"funktion, och du bör dessutom hålla ett öga på snabbtangenter och ikoner " +"i verktygsraderna." + +#. Tag: title +#: index.docbook:340 +#, no-c-format +msgid "Optional Features" +msgstr "Valfria funktioner" + +#. Tag: para +#: index.docbook:340 +#, no-c-format +msgid "" +"This Handbook assumes that your Rosegarden installation supports all the " +"features of which it is capable. Some of Rosegarden's features, including " +"some very major ones, are actually optional when building a Rosegarden " +"installation, depending on which other libraries and supporting code is " +"available. For example, the whole audio subsystem is only compiled in if " +"JACK libraries are available; synth plugin support depends on a number of " +"other modules; etc." +msgstr "" +"Handboken antar att installationen av Rosegarden stöder alla funktionerna " +"som det har möjlighet till. Vissa av Rosegardens funktioner, inklusive " +"några av de större, är i själva verket valfria när en installation av " +"Rosegarden byggs. Hela ljuddelsystemet kompileras till exempel bara om " +"JACK-biblioteken är tillgängliga, stöd för syntinsticksmoduler beror på " +"ett antal andra moduler, etc." + +#. Tag: para +#: index.docbook:348 +#, no-c-format +msgid "" +"These dependencies are documented in the Rosegarden README and configuration " +"documentation. If you find that this Handbook refers to features not visible " +"in the version of Rosegarden you're using, consult your configuration " +"documentation or distributor." +msgstr "" +"Dessa beroenden är dokumenterade i filen README och Rosegardens " +"konfigureringsdokumentation. Om du märker att handboken hänvisar till " +"funktioner som inte finns i den version av Rosegarden som du använder, " +"rådfråga konfigureringsdokumentationen eller distributören." + +#. Tag: title +#: index.docbook:370 +#, no-c-format +msgid "Rosegarden Files and Documents" +msgstr "Rosegarden-filer och -dokument" + +#. Tag: para +#: index.docbook:371 +#, no-c-format +msgid "" +"&rosegarden; stores each composition in its own document, using its own " +"internal format. When you save a document it is stored on disc as a file " +"with the .rg extension. &rosegarden; can also handle a number of other " +"standard file formats." +msgstr "" +"&rosegarden; lagrar varje komposition i ett eget dokument, med sitt eget " +"interna format. När du sparar ett dokument lagras det på disk som en fil " +"med filändelsen .rg. &rosegarden; kan också hantera ett antal andra " +"standardfilformat." + +#. Tag: title +#: index.docbook:379 +#, no-c-format +msgid "New compositions" +msgstr "Nya kompositioner" + +#. Tag: para +#: index.docbook:380 +#, no-c-format +msgid "" +"When &rosegarden; starts up, it does so with a new document, containing an " +"\"empty\" composition ready to start editing. To put something in that " +"composition, you must either record something, or create some blank lengths " +"of music (referred to as \"segments\") that you can then fill in using the " +"various editing facilities." +msgstr "" +"När &rosegarden; startar, görs det med ett nytt dokument som innehåller " +"en \"tom\" komposition som är klar att börja redigera. För att lägga " +"till något i kompositionen måste du antingen spela in något eller skapa " +"några tomma musikavsnitt (som kallas \"segment\"), som du sedan kan fylla i " +"med de olika redigeringsfunktionerna." + +#. Tag: para +#: index.docbook:388 +#, no-c-format +msgid "" +"See <link linkend=\"recording\">Recording</link> for details of how to " +"record music, and see the <link linkend=\"segment-view\">Track Editor</link> " +"section for a description of how to create, edit, and manage segments of " +"music." +msgstr "" +"Se <link linkend=\"recording\">Inspelning</link> för detaljinformation om " +"hur musik spelas in, och se avsnittet om <link " +"linkend=\"segment-view\">spåreditorn</link> för en beskrivning av hur " +"musiksegment skapas, redigeras och hanteras." + +#. Tag: title +#: index.docbook:396 +#, no-c-format +msgid "Using MIDI files" +msgstr "Använda MIDI-filer" + +#. Tag: para +#: index.docbook:397 +#, no-c-format +msgid "" +"To import and export MIDI files, use the <menuchoice> <guimenu " +"lang=\"en\">File</guimenu> <guimenuitem>Import</guimenuitem> " +"<guimenuitem>Import MIDI File</guimenuitem> </menuchoice> and <menuchoice> " +"<guimenu lang=\"en\">File</guimenu> <guimenuitem>Export</guimenuitem> " +"<guimenuitem>Export MIDI File</guimenuitem> </menuchoice> functions." +msgstr "" +"För att importera och exportera MIDI-filer, använd alternativen " +"<menuchoice><guimenu lang=\"sv\">Arkiv</guimenu> " +"<guimenuitem>Importera</guimenuitem> <guimenuitem>Importera " +"MIDI-fil</guimenuitem></menuchoice> och <menuchoice><guimenu " +"lang=\"sv\">Arkiv</guimenu> <guimenuitem>Exportera</guimenuitem> " +"<guimenuitem>Exportera MIDI-fil</guimenuitem></menuchoice>." + +#. Tag: para +#: index.docbook:412 +#, no-c-format +msgid "" +"Although &rosegarden; can load and save file formats such as MIDI, it does " +"not store MIDI data internally. You should generally prefer to save files in " +"&rosegarden;'s own format, as &rosegarden; stores quite a lot of information " +"that will be lost when exporting to MIDI." +msgstr "" +"Även om &rosegarden; kan ladda och spara filformat som MIDI, lagras inte " +"MIDI-data internt. Du bör i allmänhet föredra att spara filer med " +"&rosegarden;s eget format, eftersom &rosegarden; lagrar en hel del " +"information som går förlorad vid export till MIDI." + +#. Tag: para +#: index.docbook:419 +#, no-c-format +msgid "" +"When a MIDI file is loaded, &rosegarden; splits out the music into one track " +"per MIDI track or channel in the file, <link " +"linkend=\"studio-midi-import\">sets up the appropriate instrument " +"mappings</link>, and <link linkend=\"nv-quantization\">attempts to calculate " +"plausible notation</link> for the MIDI performance data." +msgstr "" +"När en MIDI-fil laddas, delar &rosegarden; upp musiken i ett spår per " +"MIDI-spår eller kanal i filen, <link " +"linkend=\"studio-midi-import\">ställer in lämpliga " +"instrumentavbildningar</link> och <link " +"linkend=\"nv-quantization\">försöker beräkna en trolig notering</link> " +"för utförd MIDI-data." + +#. Tag: title +#: index.docbook:430 +#, no-c-format +msgid "Merging files" +msgstr "Sammanfoga filer" + +#. Tag: para +#: index.docbook:430 +#, no-c-format +msgid "" +"As well as loading or importing files, you can also merge them into the " +"current document, adding the segments found in the file to the ones already " +"there." +msgstr "" +"Förutom att ladda eller importera filer, kan du också sammanfoga dem med " +"det nuvarande dokumentet, och lägga till segmenten som hittas i filen till " +"de som redan finns." + +#. Tag: para +#: index.docbook:436 +#, no-c-format +msgid "" +"To merge a file, just use the relevant option on the <menuchoice> <guimenu " +"lang=\"en\">File</guimenu> <guimenuitem>Merge</guimenuitem> </menuchoice> " +"submenu, instead of using the Open or Import option." +msgstr "" +"För att sammanfoga en fil, använd bara passande alternativ i undermenyn " +"<menuchoice><guimenu lang=\"sv\">Arkiv</guimenu> " +"<guimenuitem>Sammanfoga</guimenuitem></menuchoice>, istället för att " +"använda alternativen Öppna eller Importera." + +#. Tag: title +#: index.docbook:447 +#, no-c-format +msgid "Printing" +msgstr "Utskrift" + +#. Tag: para +#: index.docbook:448 +#, no-c-format +msgid "" +"You can print out a composition in the form of a musical score, using the " +"<menuchoice> <guimenu lang=\"en\">File</guimenu> " +"<guimenuitem>Print</guimenuitem> </menuchoice> function." +msgstr "" +"Du kan skriva ut en komposition i form av ett partitur, genom att använda " +"funktionen <menuchoice><guimenu lang=\"sv\">Arkiv</guimenu> " +"<guimenuitem>Skriv ut</guimenuitem></menuchoice>." + +#. Tag: para +#: index.docbook:458 +#, no-c-format +msgid "" +"Producing a score from performance data is a hard task, and in most cases " +"it's unreasonable to expect a default printout based on MIDI data to be very " +"readable. You should use the <link linkend=\"notation-view\">notation " +"editor</link> to tidy up the score before printing. (See also <link " +"linkend=\"nv-quantization\">Notation from performance data</link>.)" +msgstr "" +"Att skapa ett partitur från utförd data är en svår uppgift, och i de " +"flesta fall är det inte rimligt att förvänta sig att en standardutskrift " +"baserad på MIDI-data är särskilt läsbar. Du bör använda <link " +"linkend=\"notation-view\">notbehandlaren</link> för att städa upp " +"partituret innan du skriver ut det. (Se också <link " +"linkend=\"nv-quantization\">Notskrift från utförandedata</link>.)" + +#. Tag: para +#: index.docbook:468 +#, no-c-format +msgid "" +"&rosegarden; is capable of producing very readable scores. Even so, it is " +"designed to be a screen editor and not primarily a typesetter. If you want " +"to produce true print-quality scores you should consider using <ulink " +"url=\"http://www.lilypond.org\">Lilypond</ulink> in conjunction with " +"&rosegarden;. Lilypond is music typesetting software that reads a " +"specialised text file format and produces high-quality typeset output. " +"&rosegarden; is capable of writing Lilypond files using the <menuchoice> " +"<guimenu lang=\"en\">File</guimenu> <guimenuitem>Export</guimenuitem> " +"<guimenuitem>Export Lilypond</guimenuitem> </menuchoice> function." +msgstr "" +"&rosegarden; klarar av att skapa helt läsbara partitur. Även om det är " +"så, är programmet avsett att vara en skärmeditor, och inte i huvudsak " +"avsett för typsättning. Om du vill skapa partitur med riktig " +"utskriftskvalitet, bör du fundera på att använda <ulink " +"url=\"http://www.lilypond.org\">Lilypond</ulink> tillsammans med " +"&rosegarden;. Lilypond är programvara för typsättning av musik som läser " +"ett specialiserat textfilformat, och skapar typsatt utmatning av hög " +"kvalitet. &rosegarden; klarar av att skriva Lilypond-filer med funktionen " +"<menuchoice> <guimenu lang=\"sv\">Arkiv</guimenu> " +"<guimenuitem>Exportera</guimenuitem> <guimenuitem>Exportera " +"Lilypond-fil</guimenuitem></menuchoice>." + +#. Tag: title +#: index.docbook:487 +#, no-c-format +msgid "The Track Editor" +msgstr "Spåreditorn" + +#. Tag: title +#: index.docbook:489 index.docbook:842 +#, no-c-format +msgid "Overview" +msgstr "Översikt" + +#. Tag: para +#: index.docbook:490 +#, no-c-format +msgid "" +"&rosegarden;'s main layout is similar to many other popular sequencers. It " +"is based on a track structure — the main window shows a track editor " +"with a list of tracks and their associated instruments down the left hand " +"side. You can manipulate and move blocks of music data (referred to as " +"“segments”) on the track editor as well as opening the segments " +"themselves in specialised editors (<link " +"linkend=\"notation-view\">notation</link>, <link " +"linkend=\"matrix-view\">matrix</link>, <link " +"linkend=\"percussion-matrix-view\">percussion matrix</link>, and <link " +"linkend=\"event-view\">event list</link>)." +msgstr "" +"&rosegarden;s utseende liknar många andra populära musikbehandlare. " +"Det är baserat på en spårstruktur: Huvudfönstret visar en spåreditor " +"med en spårlista och tillhörande instrument längs med vänster sida. Du " +"kan behandla och flytta block med musikdata (som kallas " +"“segment”) i spåreditorn, samt öppna själva segmenten i " +"specialiserade editorer (<link linkend=\"notation-view\">not</link>, " +"<link linkend=\"matrix-view\">matris</link>, " +"<link linkend=\"percussion-matrix-view\">slagverksmatris</link> " +"och <link linkend=\"event-view\">händelselista</link>)." + +#. Tag: phrase +#: index.docbook:512 +#, no-c-format +msgid "&rosegarden;'s Track Editor showing two segments of music data" +msgstr "&rosegarden;s spåreditor som visar två segment med musikdata" + +#. Tag: para +#: index.docbook:518 +#, no-c-format +msgid "" +"Tracks can be assigned to a range of &MIDI;, plugin synth, or audio " +"instruments. In the picture above we see three segments in the track editor " +"on tracks assigned to General MIDI instruments." +msgstr "" +"Spår kan tilldelas en uppsättning &MIDI;-instrument, syntinsticksmoduler " +"eller ljudinstrument. I bilden ovan syns tre segment i spåreditorn för " +"spår som är tilldelade till generella MIDI-instrument." + +#. Tag: phrase +#: index.docbook:532 +#, no-c-format +msgid "&rosegarden;'s Track buttons showing track labels" +msgstr "&rosegarden;s spårknappar som visar spårnamn" + +#. Tag: para +#: index.docbook:538 +#, no-c-format +msgid "" +"The button area to the left of the segment canvas shows you the track " +"number, mute and record status, and the label of the track. You can mute or " +"unmute a track by clicking on the blue LED-style button, and select a " +"particular track as a record target by clicking on the red one. To change " +"the track label, double-click on it." +msgstr "" +"Området med knappar till vänster om segmentduken visar spårnummer, " +"tystnads- och inspelningsstatus, och spårets namn. Du kan göra ett spår " +"tyst eller inte genom att klicka på den blåa knappen i form av en lysdiod, " +"och välja ett visst spår som ska användas för inspelning genom att " +"klicka på den röda knappen. För att ändra spårnamnet, dubbelklicka " +"på det." + +#. Tag: phrase +#: index.docbook:554 +#, no-c-format +msgid "&rosegarden;'s Track buttons showing instrument assignments" +msgstr "&rosegarden;s spårknappar som visar instrumenttilldelningar" + +#. Tag: para +#: index.docbook:560 +#, no-c-format +msgid "" +"Track labels are only shown if the <menuchoice> <guimenu " +"lang=\"en\">Settings</guimenu> <guimenuitem>Show Track Labels</guimenuitem> " +"</menuchoice> menu option is enabled. Otherwise, as in this picture, the " +"instrument assignments for the tracks are shown instead." +msgstr "" +"Spårnamn visas bara om menyalternativet <menuchoice><guimenu " +"lang=\"sv\">Inställningar</guimenu> <guimenuitem>Visa " +"spårnamn</guimenuitem></menuchoice> är aktiverat. Annars visas " +"spårens instrumenttilldelningar istället, som i bilden." + +#. Tag: title +#: index.docbook:572 +#, no-c-format +msgid "Tracks and instruments" +msgstr "Spår och instrument" + +#. Tag: para +#: index.docbook:573 +#, no-c-format +msgid "" +"Each track must have an instrument assigned to it, in order to be heard. By " +"default the first 16 tracks are assigned to the 16 instruments of the first " +"available MIDI device, and the next 16 tracks are assigned to audio." +msgstr "" +"Varje spår måste ha ett tilldelat instrument för att kunna höras. " +"Normalt tilldelas de 16 första spåren till de 16 instrumenten i den " +"första tillgängliga MIDI-enheten, och de följande 16 spåren tilldelas " +"till ljud." + +#. Tag: para +#: index.docbook:579 +#, no-c-format +msgid "" +"To change the instrument assignment for a track, right-click on the track " +"label: a pop-up menu will appear from which you can select among all the " +"available instruments." +msgstr "" +"För att ändra instrumenttilldelningen för ett spår, högerklicka på " +"spårnamnet: En meny dyker upp där du kan välja bland alla tillgängliga " +"instrument." + +#. Tag: phrase +#: index.docbook:591 +#, no-c-format +msgid "&rosegarden;'s Instrument menu" +msgstr "&rosegarden;s instrumentmeny" + +#. Tag: para +#: index.docbook:597 +#, no-c-format +msgid "" +"An instrument can be understood as a single channel on a &MIDI; device, or " +"as a mono or stereo audio output or an audio synth plugin. Tracks containing " +"note data should be assigned to &MIDI; or synth plugin instruments, and " +"those containing audio to audio instruments. You can assign more than one " +"track to the same instrument, in which case the multiple tracks will use the " +"same sounds." +msgstr "" +"Ett instrument kan betraktas som en enstaka kanal i en &MIDI;-enhet, som en " +"mono- eller stereoljudutgång, eller som en ljudsyntinsticksmodul. Spår som " +"innehåller notinformation ska tilldelas till &MIDI;- eller " +"syntinsticksinstrument, och de som innehåller ljud till ljudinstrument. Du " +"kan tilldela mer än ett spår till samma instrument, och i så fall " +"använder alla dessa spår samma ljud." + +#. Tag: para +#: index.docbook:606 +#, no-c-format +msgid "" +"You can change various properties of the instrument associated with a track " +"using the <link linkend=\"segment-view-instrumentparameterbox\">Instrument " +"Parameter Box</link>. This is where, for example, you would set a MIDI " +"instrument to use a particular patch and so produce a particular sound " +"(piano, strings etc)." +msgstr "" +"Du kan ändra diverse egenskaper för instrumentet som tilldelats ett spår, " +"genom att använda <link " +"linkend=\"segment-view-instrumentparameterbox\">instrumentparameterrutan</lin" +"k>. Det är till exempel här som du kan ställa in ett MIDI-instrument så " +"att det använder en speciell ljudpatch, och på så sätt åstadkommer ett " +"speciellt ljud (piano, stråkar, etc.)." + +#. Tag: para +#: index.docbook:614 +#, no-c-format +msgid "" +"See the <link linkend=\"studio-introduction\">Studio</link> section for more " +"about instruments." +msgstr "" +"Se avsnittet <link linkend=\"studio-introduction\">Studio</link> för mer om " +"instrument." + +#. Tag: title +#: index.docbook:623 +#, no-c-format +msgid "Creating segments" +msgstr "Skapa segment" + +#. Tag: para +#: index.docbook:624 +#, no-c-format +msgid "" +"To create an empty segment, in order to begin composing something new, you " +"need to use the pencil tool. Click on the pencil on the toolbar, and then " +"click at the point where you want the segment to start (at the correct " +"height for the track you want the segment to be on, and at a distance across " +"the editor window corresponding to the correct time) and drag rightwards " +"until the segment is the right number of bars long." +msgstr "" +"För att skapa ett tomt segment när någonting nytt ska komponeras, måste " +"du använda pennverktyget. Klicka på pennan i verktygsraden, och klicka " +"därefter på stället där du vill att segmentet ska börja (på rätt " +"plats för spåret som du vill att segmentet ska finnas i, och på ett " +"avstånd i redigeringsfönstret som motsvarar rätt tid) och dra åt höger " +"till segmentet är rätt antal takter i längd." + +#. Tag: para +#: index.docbook:635 +#, no-c-format +msgid "" +"Usually each new segment starts on a barline and extends bar by bar, but " +"this snap-to-grid effect can be prevented by holding down Shift while " +"clicking and dragging." +msgstr "" +"Oftast börjar varje nytt segment på ett taktstreck och utökas takt för " +"takt, men effekten att låsa till rutnätet kan förhindras genom att hålla " +"nere Skift under klick- och dragåtgärden." + +#. Tag: para +#: index.docbook:641 +#, no-c-format +msgid "" +"Once you have created a segment, you can then begin editing using the <link " +"linkend=\"matrix-view\">matrix</link>, <link " +"linkend=\"percussion-matrix-view\">percussion matrix</link> or <link " +"linkend=\"notation-view\">notation</link> editors. To use one of these " +"editors, either double-click on the segment, or else click with the right " +"mouse button and choose the editor you want from the context menu." +msgstr "" +"När du väl har skapat ett segment kan du börja redigera det med <link " +"linkend=\"matrix-view\">matriseditorn</link>, <link " +"linkend=\"percussion-matrix-view\">slagverksmatriseditorn</link> eller " +"<link linkend=\"notation-view\">notbehandlaren</link>. För att använda en " +"av editorerna, dubbelklicka antingen på segmentet eller klicka med höger " +"musknapp och välj editorn du vill använda i den sammanhangsberoende menyn." + +#. Tag: para +#: index.docbook:650 +#, no-c-format +msgid "" +"If you are intending to <link linkend=\"recording\">record</link> from a " +"MIDI device or audio input, you don't need to create a new segment to record " +"into first -- each separate recording always goes into a new segment, " +"created automatically during recording." +msgstr "" +"Om du avser att <link linkend=\"recording\">spela in</link> från en " +"MIDI-enhet eller ljudingång, behöver du inte först skapa ett nytt segment " +"att spela in till. Varje enskild inspelning hamnar alltid i ett nytt " +"segment, som skapas automatiskt under inspelningen." + +#. Tag: title +#: index.docbook:660 +#, no-c-format +msgid "Audio segments" +msgstr "Ljudsegment" + +#. Tag: para +#: index.docbook:661 +#, no-c-format +msgid "" +"An audio segment contains recorded or sampled audio data, instead of " +"editable note-event data. Rosegarden allows you to record, play, arrange and " +"split audio segments, but does not contain audio waveform editing facilities." +msgstr "" +"Ett ljudsegment innehåller inspelad eller samplad ljuddata, istället för " +"redigerbar tonhändelsedata. Rosegarden låter dig spela in, spela upp, " +"arrangera och dela ljudsegment, men innehåller inte funktioner för " +"redigering av ljudvågformer." + +#. Tag: para +#: index.docbook:667 +#, no-c-format +msgid "" +"To create an audio segment, you can <link " +"linkend=\"recording\">record</link> from an audio source onto a track " +"assigned to an audio instrument, or you can work with existing WAV files. To " +"do this, you need to use the audio manager dialog (reached via " +"<menuchoice><guimenu lang=\"en\">Segments</guimenu><guimenuitem>Manage Audio " +"Segments</guimenuitem></menuchoice>)." +msgstr "" +"För att skapa ett ljudsegment kan du <link linkend=\"recording\">spela " +"in</link> från en ljudkälla till ett spår som hör till ett " +"ljudinstrument, eller arbeta med befintliga WAV-filer. För att göra det " +"måste du använda ljudhanteringsdialogrutan (som nås via " +"<menuchoice><guimenu lang=\"sv\">Segment</guimenu> <guimenuitem>Hantera " +"ljudsegment</guimenuitem></menuchoice>)." + +#. Tag: phrase +#: index.docbook:682 +#, no-c-format +msgid "The audio file manager" +msgstr "Ljudfilhantering" + +#. Tag: para +#: index.docbook:688 +#, no-c-format +msgid "" +"You can drag-and-drop audio files from the KDE file browser or your KDE " +"desktop into the audio file manager, or you can open them using its File " +"menu. Then you can either drag-and-drop them onto Rosegarden's track canvas, " +"or use the audio file manager's <menuchoice><guimenu " +"lang=\"en\">Action</guimenu><guimenuitem>Insert into Selected Audio " +"Track</guimenuitem></menuchoice> menu function, provided the current " +"selected track in the main window is assigned to an audio instrument. " +"Newly-recorded audio segments also appear in the audio file manager dialog." +msgstr "" +"Du kan dra och släppa ljudfiler från KDE:s filbläddrare eller " +"KDE-skrivbordet till ljudfilhanteringen, eller öppna dem med dess " +"arkivmeny. Därefter kan du antingen dra och släppa dem på Rosegardens " +"spårduk, eller använda menyfunktionen <menuchoice><guimenu " +"lang=\"sv\">Åtgärd</guimenu> <guimenuitem>Infoga i markerat " +"ljudspår</guimenuitem></menuchoice> i ljudfilhanteringen, under " +"förutsättning att spåret som för närvarande är markerat i " +"huvudfönstret är tilldelat till ett ljudinstrument. Nyinspelade " +"ljudsegment syns också i dialogrutan för ljudfilhantering." + +#. Tag: para +#: index.docbook:699 +#, no-c-format +msgid "" +"Details of the audio files associated with a particular composition are " +"saved with that composition, but the audio files themselves are not. You " +"should ensure your document has a sensible audio file search path (via " +"<menuchoice><guimenu lang=\"en\">Composition</guimenu><guimenuitem>Edit " +"Document " +"Properties...</guimenuitem><guimenuitem>Audio</guimenuitem></menuchoice>) so " +"as to keep your audio files accessible together." +msgstr "" +"Information om ljudfilerna som hör ihop med en viss komposition är sparad " +"med kompositionen, men själva ljudfilerna är inte det. Du måste " +"försäkra dig om att ditt dokument har en vettig sökväg för ljudfiler " +"(via <menuchoice><guimenu lang=\"sv\">Komposition</guimenu> " +"<guimenuitem>Redigera dokumentegenskaper...</guimenuitem> " +"<guimenuitem>Ljud</guimenuitem></menuchoice>, för att göra det möjligt " +"att komma åt dina ljudfiler tillsammans." + +#. Tag: para +#: index.docbook:707 +#, no-c-format +msgid "" +"The audio manager dialog also shows the sample-rate and other information " +"for each audio file, and marks with an asterisk any audio file whose sample " +"rate does not match that of the current JACK audio session that Rosegarden " +"is using. Rosegarden will resample these files at playback time using a fast " +"(but correspondingly very low quality) linear resampler. You are advised to " +"resample them separately using a separate dedicated audio editor instead." +msgstr "" +"Dialogrutan för ljudfilhantering visar också samplingsfrekvensen och annan " +"information för varje ljudfil, och markerar eventuella ljudfiler vars " +"samplingsfrekvens inte motsvarar nuvarande JACK-ljudsessionen som Rosegarden " +"använder. Rosegarden samplar om filerna vid uppspelning med en snabb " +"linjär omsampling (men därför med mycket dålig kvalitet). Du råds att " +"sampla om dem separat med en särskild dedicerad ljudeditor istället." + +#. Tag: title +#: index.docbook:720 +#, no-c-format +msgid "Manipulating segments" +msgstr "Hantering av segment" + +#. Tag: para +#: index.docbook:721 +#, no-c-format +msgid "" +"The main window contains a selection of \"tools\" for editing segments. " +"These are available from the main toolbar: first select the tool you want " +"from the toolbar, and then click and drag on the segments on the main canvas." +msgstr "" +"Huvudfönstret innehåller en uppsättning \"verktyg\" för att redigera " +"segment. De är tillgängliga i huvudverktygsraden: Välj först verktyget " +"du vill ha i verktygsraden, och klicka och dra därefter på segmenten i " +"huvudduken." + +#. Tag: title +#: index.docbook:729 +#, no-c-format +msgid "The Select tool" +msgstr "Markeringsverktyget" + +#. Tag: para +#: index.docbook:730 +#, no-c-format +msgid "" +"The \"select tool\" (the arrow tool) is actually a multipurpose tool: it can " +"be used to select, move, copy, resize and create segments." +msgstr "" +"\"Markeringsverktyget\" (pilverktyget) är i själva verket ett verktyg med " +"flera användningar. Det kan användas för att markera, flytta, kopiera, " +"ändra storlek och skapa segment." + +#. Tag: para +#: index.docbook:735 +#, no-c-format +msgid "" +"The most obvious use is selection: select a single segment by clicking on it " +"with the select tool, or select several by clicking with Shift held down, or " +"by clicking in an empty area of the window and dragging out an area." +msgstr "" +"Den mest uppenbara användningen är markering: Markera ett enstaka segment " +"genom att klicka på det med markeringsverktyget, eller markera flera genom " +"att klicka med Skift nertryckt, eller genom att klicka på ett tomt ställe " +"i fönstret och dra för att åstadkomma ett område." + +#. Tag: para +#: index.docbook:742 +#, no-c-format +msgid "" +"To move segments with the select tool, simply click and drag on the segment. " +"To create copies, click and drag with Ctrl held down. To resize a segment, " +"click and drag on the right-hand edge of the segment; and to create new " +"segments, click and drag on an empty area with the middle mouse button." +msgstr "" +"För att flytta segment med markeringsverktyget, klicka och dra helt enkelt " +"segmentet. För att skapa kopior, klicka och dra med Ctrl nertryckt. För " +"att ändra storlek på ett segment, klicka och dra segmentets högerkant, " +"och för att skapa nya segment klicka och dra på ett tomt ställe med " +"musens mittenknapp." + +#. Tag: para +#: index.docbook:749 +#, no-c-format +msgid "" +"The select tool doesn't replace the other tools completely, though — " +"sometimes you need to be more precise about which operation you intend, " +"particularly when working on small segments." +msgstr "" +"Markeringsverktyget ersätter ändå inte övriga verktyg helt och hållet: " +"Ibland behöver du vara noggrannare med vilken åtgärd du avsåg, särskilt " +"vid arbete med små segment." + +#. Tag: title +#: index.docbook:759 +#, no-c-format +msgid "Move and Resize tools" +msgstr "Verktygen för att flytta och ändra storlek" + +#. Tag: para +#: index.docbook:760 +#, no-c-format +msgid "" +"To move a segment to a different start time or track, use the Move tool and " +"click and drag on the segment you want to move. If you hold down the Ctrl " +"key while dragging, the segment will be copied instead of moved." +msgstr "" +"För att flytta ett segment till en annan starttid eller ett annat spår, " +"använd förflyttningsverktyget och klicka och dra segmentet du vill flytta. " +"Om du håller nere Ctrl-tangenten medan du drar, kopieras segmentet " +"istället för att flyttas." + +#. Tag: para +#: index.docbook:765 +#, no-c-format +msgid "" +"To resize a segment, use the Resize tool, and click and drag on the " +"right-hand end of the segment." +msgstr "" +"För att ändra storlek på ett segment, använd verktyget för " +"storleksändring, och klicka och dra i högra ändan av segmentet." + +#. Tag: para +#: index.docbook:768 +#, no-c-format +msgid "" +"For both move and resize you can hold Shift for fine positioning, to avoid " +"snapping to a particular grid position." +msgstr "" +"Både vid förflyttning och storleksändring kan du hålla nere Skift för " +"finpositionering, för att undvika att hoppa till en viss rutnätsposition." + +#. Tag: title +#: index.docbook:775 +#, no-c-format +msgid "Split tool" +msgstr "Delningsverktyget" + +#. Tag: para +#: index.docbook:776 +#, no-c-format +msgid "" +"You can use the split tool <inlinemediaobject> <imageobject> <imagedata " +"fileref=\"rg-split.png\"/> </imageobject> </inlinemediaobject> to split a " +"single segment into two separate segments. To split your segment, select the " +"split tool and click on the segment you wish to split." +msgstr "" +"Du kan använda delningsverktyget <inlinemediaobject> <imageobject> " +"<imagedata fileref=\"rg-split.png\"/> </imageobject> </inlinemediaobject> " +"för att dela ett enstaka segment i två separata segment. För att dela " +"segmentet, välj delningsverktyget och klicka på segmentet du vill dela." + +#. Tag: para +#: index.docbook:787 +#, no-c-format +msgid "" +"By default segments are split on the closest barline to the cursor, but this " +"can be prevented by holding down Shift while splitting the segment." +msgstr "" +"Normalt delas segment vid taktstrecket närmast markören, men det kan " +"förhindras genom att hålla nere Skift när segmentet delas." + +#. Tag: title +#: index.docbook:796 +#, no-c-format +msgid "Tempo and Time Signature" +msgstr "Tempo och taktart" + +#. Tag: title +#: index.docbook:798 +#, no-c-format +msgid "<title>Tempo</title>" +msgstr "<title>Tempo</title>" + +#. Tag: phrase +#: index.docbook:806 +#, no-c-format +msgid "&rosegarden;'s tempo dialog" +msgstr "&rosegarden;s tempodialogruta" + +#. Tag: title +#: index.docbook:814 +#, no-c-format +msgid "Time signature" +msgstr "Taktart" + +#. Tag: phrase +#: index.docbook:822 +#, no-c-format +msgid "&rosegarden;'s time signature dialog" +msgstr "&rosegarden;s taktartsdialogruta" + +#. Tag: title +#: index.docbook:832 +#, no-c-format +msgid "The Transport" +msgstr "Överföringen" + +#. Tag: para +#: index.docbook:833 +#, no-c-format +msgid "" +"When you play a composition, &rosegarden; sweeps a playback pointer across " +"the tracks from left to right playing the contents of the segments as it " +"crosses them. The pointer's position on the screen is tracked and controlled " +"by a window called the Transport." +msgstr "" +"När du spelar upp en komposition, sveper &rosegarden; en " +"uppspelningsmarkör över spåren från vänster till höger och spelar upp " +"innehållet i segmenten när den korsar dem. Markörens position på " +"skärmen följs och styrs av ett fönster som kallas Överföring." + +#. Tag: phrase +#: index.docbook:850 +#, no-c-format +msgid "&rosegarden;'s Transport window" +msgstr "&rosegarden;s överföringsfönster" + +#. Tag: para +#: index.docbook:856 +#, no-c-format +msgid "" +"If the Transport isn't visible, you can activate it with <menuchoice> " +"<guimenu lang=\"en\">Settings</guimenu> <guimenuitem>Show " +"Transport</guimenuitem> </menuchoice>." +msgstr "" +"Om överföringen inte är synlig, kan du aktivera den med <menuchoice> " +"<guimenu lang=\"sv\">Inställningar</guimenu> <guimenuitem>Visa " +"överföring</guimenuitem></menuchoice>." + +#. Tag: para +#: index.docbook:861 +#, no-c-format +msgid "" +"The Transport shows the time reached by the playback pointer, in seconds by " +"default. You can switch it to show musical time (bar and beat counts), " +"musical time with a flashing visual metronome, or audio sample frame times, " +"using the topmost of the small buttons on the left of the transport window. " +"The button immediately below that toggles the display so as to show time " +"remaining to the end of the composition instead of from the start." +msgstr "" +"Överföringen visar tiden som uppnåtts av uppspelningsmarkören, normalt i " +"sekunder. Du kan ändra den att visa metronomtid (takter och taktslag), " +"metronomtid med en blinkande visuell metronom, eller ramtider för " +"ljudsampling, med den översta av de små knapparna till vänster i " +"överföringsfönstret. Knappen direkt nedanför byter mellan att visa tid " +"som är kvar till kompositionens slut istället för tid från början." + +#. Tag: para +#: index.docbook:870 +#, no-c-format +msgid "" +"The main controls on the transport start the sequencer playing and pause it, " +"fast forward the pointer position, rewind it, stop it or jump to beginning " +"or end of composition." +msgstr "" +"Huvudknapparna i överföringen startar uppspelning med musikbehandlaren eller " +"gör paus, flyttar markörpositionen framåt, flyttar den bakåt, stoppar " +"den eller går till kompositionens början eller slut." + +#. Tag: para +#: index.docbook:876 +#, no-c-format +msgid "" +"Additional controls and a &MIDI; event display are hidden on the bottom flap " +"on the transport, which can be toggled on or off using the arrow button next " +"to it at the left. Also on this extra portion there are buttons for " +"recording, setting loops, soloing individual tracks, turning on or off the " +"metronome, and silencing your MIDI devices (panic button)." +msgstr "" +"Ytterligare knappar och visning av &MIDI;-händelser är dolda längst ner i " +"överföringsfönstret, och kan visas eller inte med pilknappen i det " +"längst till vänster. Dessutom finns knappar för inspelning, för " +"upprepning, för att spela enskilda spår solo, för att stänga av eller " +"sätta på metronomen och för att tysta dina MIDI-enheter (panikknapp) i " +"extradelen." + +#. Tag: title +#: index.docbook:885 +#, no-c-format +msgid "Recording" +msgstr "Inspelning" + +#. Tag: para +#: index.docbook:886 +#, no-c-format +msgid "" +"To record a new segment into a track, first make sure the right track is " +"selected for recording by selecting the red (for audio tracks) or yellow " +"(for MIDI tracks) LED-style button on the track label, and then use the " +"Transport's record control. This has the effect of both starting the " +"transport, thus playing the existing composition, and recording into the " +"appropriate track." +msgstr "" +"För att spela in ett nytt segment i ett spår, försäkra dig först om att " +"rätt spår är markerat för inspelning genom att klicka på den röda (för ljudspår) " +"eller gula (för MIDI-spår) lysdiodknappen vid spårets namn, och använd " +"därefter överföringens inspelningsknapp. Det ger effekten att både starta " +"överföringen, och därigenom spela upp den befintliga kompositionen, och att " +"spela in i motsvarande spår." + +#. Tag: para +#: index.docbook:895 +#, no-c-format +msgid "" +"You can only select a single MIDI track for recording, but you can record " +"any number of audio tracks at once so long as your computer is powerful " +"enough. You can also select a MIDI track and one or more audio tracks at the " +"same time. Be careful not to accidentally leave tracks selected when you " +"have finished using them and are trying to record somewhere else." +msgstr "" +"Du kan bara markera ett enda MIDI-spår för inspelning, men du kan " +"spela in hur många ljudspår som helst samtidigt så länge datorn är " +"kraftfull nog. Du kan också markera ett MIDI-spår och ett eller flera " +"ljudspår samtidigt. Var försiktig så att du inte lämnar spår markerade " +"av misstag när du är klar med användning av dem och försöker " +"spela in någon annanstans." + +#. Tag: para +#: index.docbook:903 +#, no-c-format +msgid "" +"Alternatively you can use punch-in record to separate the acts of starting " +"the transport and entering record mode. Punch-in record is toggled with the " +"Space bar. You can press Space while playing a composition to switch " +"instantly between playback and recording without stopping the transport, or " +"you can use Space to arm for recording when the transport is stopped, so " +"that a subsequent Play will in fact record as well. (The latter is handy " +"when synchronising to an <link linkend=\"transport-external\">external " +"transport</link>.)" +msgstr "" +"Som ett alternativ kan du använda punch-in inspelning för att skilja på " +"åtgärderna att starta överföringen och gå in i inspelningsläge. " +"Punch-in inspelning ändras med mellanslagstangenten. Du kan trycka på " +"mellanslag medan en komposition spelas upp för att omedelbart byta mellan " +"uppspelning och inspelning utan att stoppa överföringen, eller använda " +"mellanslag för att förbereda inspelning medan överföringen är stoppad, " +"så att följande uppspelning i själva verket också spelar in. (Det senare " +"är praktiskt vid synkronisering med en <link linkend=\"transport-external\">" +"extern överföring</link>.)" + +#. Tag: para +#: index.docbook:914 +#, no-c-format +msgid "" +"If you record to a MIDI track, your recording will be from all of the MIDI " +"devices that are selected for recording in the <link " +"linkend=\"studio-device-editor\">MIDI device manager</link>." +msgstr "" +"Om du spelar in ett MIDI-spår, sker inspelning från alla MIDI-enheter " +"som är inställda för inspelning i <link linkend=\"studio-device-editor\">" +"MIDI-enhetshanteringen</link>." + +#. Tag: para +#: index.docbook:920 +#, no-c-format +msgid "" +"If you record to audio tracks, your recording to each track will be from the " +"input currently selected for that track's instrument in the <link " +"linkend=\"segment-view-instrumentparameterbox\">instrument parameter " +"box</link>. This will either be an external audio input or an audio " +"submaster or master (for performing mixdowns). If it's an external input, it " +"will by default record from your soundcard's first available physical record " +"in. You may wish to use a JACK connection tool to connect some other JACK " +"audio application to the input instead." +msgstr "" +"Om du spelar in ljudspår, sker inspelning av varje spår från ingången som för " +"närvarande är inställd för det spårets instrument i <link " +"linkend=\"segment-view-instrumentparameterbox\">instrumentparameterrutan" +"</link>. Det är antingen en extern ljudingång eller en delnivå eller " +"huvudnivå för ljud (för att utföra ihopmixningar). Om det är en extern " +"ingång, spelas det normalt in från ljudkortets första tillgängliga " +"fysiska inspelningsingång. Du kanske vill använda ett anslutningsverktyg i " +"JACK för att ansluta ett annat ljudprogram som stöder JACK till ingången " +"istället." + +#. Tag: title +#: index.docbook:936 +#, no-c-format +msgid "Synchronising to external transports" +msgstr "Synkronisering med extern överföring" + +#. Tag: title +#: index.docbook:938 +#, no-c-format +msgid "JACK Transport" +msgstr "Överföring med JACK" + +#. Tag: para +#: index.docbook:939 +#, no-c-format +msgid "" +"Rosegarden supports the JACK transport mechanism for synchronising its " +"transport with other JACK applications on the same computer. To activate it, " +"go to <menuchoice> <guimenu lang=\"en\">Settings</guimenu> " +"<guimenuitem>Configure Rosegarden...</guimenuitem> </menuchoice> and in the " +"Sequencer page's Synchronisation tab, select \"Sync\" from the JACK " +"transport mode menu." +msgstr "" +"Rosegarden stöder överföringsmekanismen i JACK för att synkronisera " +"överföringen med andra program med JACK på samma dator. För att aktivera " +"den, gå till <menuchoice><guimenu lang=\"sv\">Inställningar</guimenu> " +"<guimenuitem>Anpassa Rosegarden...</guimenuitem></menuchoice> och välj " +"\"Synkronisera\" i menyn för JACK överföringsläge på sidan Musikbehandlare " +"under fliken Synkronisering." + +#. Tag: para +#: index.docbook:950 +#, no-c-format +msgid "" +"When the JACK transport is in use, all of the applications that are " +"subscribed to it share a common transport control, and you can start, stop, " +"and move the transport from any one of them." +msgstr "" +"När överföring med JACK används, delar alla program som prenumererar på " +"den en gemensam styrning av överföringen, och du kan starta, stoppa och " +"förflytta överföringen från vart och ett av dem." + +#. Tag: para +#: index.docbook:955 +#, no-c-format +msgid "" +"Many Linux audio applications that use the JACK audio server also support " +"JACK transport: consult their documentation for details of whether and how." +msgstr "" +"Många ljudprogram under Linux som använder ljudservern JACK stöder också " +"överföring med JACK. Titta i deras dokumentation för detaljinformation om de " +"gör det och hur." + +#. Tag: title +#: index.docbook:960 +#, no-c-format +msgid "MIDI Time Code" +msgstr "MIDI-tidkod" + +#. Tag: para +#: index.docbook:961 +#, no-c-format +msgid "" +"Rosegarden supports MIDI Time Code (MTC) synchronisation in master and slave " +"modes. This is particularly useful for synchronising the Rosegarden " +"transport with a hardware MTC-capable device, or with software running on " +"other computers connected via MIDI." +msgstr "" +"Rosegarden stöder synkronisering med MIDI-tidkod (MTC) i huvud- och slavläge. " +"Det är särskilt användbart för att synkronisera Rosegardens överföring med " +"en hårdvaruenhet som stöder MTC, eller med programvara som kör på andra " +"datorer anslutna via MIDI." + +#. Tag: para +#: index.docbook:968 +#, no-c-format +msgid "" +"To make Rosegarden the MTC Master, so that it will control any MTC slave " +"device or application connected to it, go to <menuchoice> <guimenu " +"lang=\"en\">Settings</guimenu> <guimenuitem>Configure " +"Rosegarden...</guimenuitem> </menuchoice> and in the Sequencer page's " +"Synchronisation tab, select \"MTC Master\" from the MIDI Time Code menu. To " +"make Rosegarden an MTC Slave so that Rosegarden's transport will " +"automatically be synchronised with incoming MTC events, select \"MTC Slave\"." +msgstr "" +"För att göra Rosegarden till MTC-huvudenhet, så att det styr alla MTC-slavar " +"eller program som ansluts, gå till <menuchoice><guimenu lang=\"sv\">" +"Inställningar</guimenu> <guimenuitem>Anpassa Rosegarden...</guimenuitem>" +"</menuchoice> och välj \"MTC-huvudenhet\" i menyn MIDI-tidkodsläge under " +"fliken Synkronisering på sidan Musikbehandlare. För att göra Rosegarden " +"till en slav, så att Rosegardens överföring automatiskt synkroniseras med " +"inkommande MTC-händelser, välj \"MTC-slav\"." + +#. Tag: title +#: index.docbook:986 +#, no-c-format +msgid "The Studio" +msgstr "Studion" + +#. Tag: title +#: index.docbook:989 +#, no-c-format +msgid "Devices, instruments and connections" +msgstr "Enheter, instrument och anslutningar" + +#. Tag: para +#: index.docbook:991 +#, no-c-format +msgid "" +"Rosegarden uses the term Studio to refer to everything it knows about the " +"sound systems attached to the computer. This may include &MIDI; and audio " +"hardware and other sound software, and includes information about " +"connections, configuration, &MIDI; patches and so on. The Studio is built-in " +"to every composition you create with Rosegarden." +msgstr "" +"Rosegarden använder termen studio för att ange allt som den känner till " +"om ljudsystemen anslutna till datorn. Det kan omfatta &MIDI;- och " +"ljudhårdvara och annan ljudprogramvara, och omfattar information om " +"anslutningar, inställning, &MIDI;-patchar och så vidare. Studion är " +"inbyggd i alla kompositioner du skapar med Rosegarden." + +#. Tag: para +#: index.docbook:998 +#, no-c-format +msgid "Three pieces of terminology are essential here:" +msgstr "Tre ord i terminologin är fundamentala här:" + +#. Tag: term +#: index.docbook:1003 +#, no-c-format +msgid "Device" +msgstr "Enhet" + +#. Tag: para +#: index.docbook:1005 +#, no-c-format +msgid "" +"A <quote>device</quote>, as far as Rosegarden is concerned, is simply " +"something capable of producing sounds. This may be a MIDI or audio device. " +"MIDI devices do not necessarily correspond directly to physical MIDI ports: " +"they are just things with names that you can refer to, expected to work in " +"particular ways. Configuration information such as MIDI patch maps can be " +"attached to devices." +msgstr "" +"En <quote>enhet</quote>, så vitt det angår Rosegarden, är helt enkelt " +"något som kan skapa ljud. Det kan vara en MIDI- eller ljudenhet. " +"MIDI-enheter motsvarar inte nödvändigtvis direkt med fysiska MIDI-portar: " +"De är bara saker med namn som du kan ange, som förväntas fungera på ett " +"visst sätt. Inställningsinformation som MIDI-patchavbildningar kan " +"anslutas till enheter." + +#. Tag: term +#: index.docbook:1018 +#, no-c-format +msgid "Instrument" +msgstr "Instrument" + +#. Tag: para +#: index.docbook:1020 +#, no-c-format +msgid "" +"Each device has a number of <quote>instruments</quote>, each of which is " +"assumed to make a particular sound. These are the things that you can assign " +"tracks to in order to choose which sound they play. By default, a device " +"contains 16 instruments, created for you at startup: if the device is a MIDI " +"device, then these will each be initialised to one of the 16 MIDI channels. " +"The instrument is where you set all the properties of a particular voice, " +"such as program settings, reverb, volume etc." +msgstr "" +"Varje enhet har ett antal <quote>instrument</quote>, där vart och ett antas " +"låta på ett visst sätt. Detta är det du kan tilldela spår till för att " +"välja vilket ljud de spelar. Normalt innehåller en enhet 16 instrument, " +"som skapas åt dig vid start. Om enheten är en MIDI-enhet, initieras vart " +"och ett av dem till en av de 16 MIDI-kanalerna. Instrumentet är stället " +"där du anger alla egenskaper för en viss stämma, som " +"programinställningar, eko, volym, etc." + +#. Tag: term +#: index.docbook:1035 +#, no-c-format +msgid "Connection" +msgstr "Anslutning" + +#. Tag: para +#: index.docbook:1037 +#, no-c-format +msgid "" +"While a MIDI device is simply a name and a collection of configuration " +"information, the <quote>connection</quote> specifies which MIDI port it is " +"physically attached to. This can be configured in the <link " +"linkend=\"studio-device-editor\">MIDI device manager</link>. (Audio and " +"synth plugin devices do not have connections in the same way.)" +msgstr "" +"Även om en MIDI-enhet helt enkelt är ett namn och en samling " +"inställningsinformation, anger <quote>anslutningen</quote> vilken MIDI-port " +"som den är fysiskt ansluten till. Det kan ställas in i <link " +"linkend=\"studio-device-editor\">MIDI-enhetshanteringen</link>. (Ljud- och " +"syntinsticksmodulenheter har inte anslutningar på samma sätt)." + +#. Tag: para +#: index.docbook:1050 +#, no-c-format +msgid "" +"For example, imagine a setup consisting of a PC with two physical MIDI " +"ports, one of which has an external synth attached to it. Here you would " +"normally configure Rosegarden so as to have one MIDI device, corresponding " +"to the synth. You could then configure this device with the correct name and " +"patch map, and then specify a connection for it that corresponded to the " +"relevant MIDI port on your soundcard. Each of the 16 default instruments on " +"the device could then be configured with a suitable program, and you would " +"then assign tracks to those." +msgstr "" +"Tänk dig exempelvis en konfiguration som består av en dator med två " +"fysiska MIDI-portar, där den ena har en extern synt ansluten. Då skulle du " +"normalt ställa in Rosegarden att ha en MIDI-enhet, som motsvarar synten. Du " +"skulle därefter kunna ställa in enheten med rätt namn och " +"patchavbildning, och ange en anslutning för den som motsvarar ljudkortets " +"verkliga MIDI-port. Vart och ett av de 16 standardinstrumenten på enheten " +"skulle kunna anpassas med ett lämpligt program, och därefter skulle du " +"tilldela spår till dem." + +#. Tag: para +#: index.docbook:1061 +#, no-c-format +msgid "" +"In practice, Rosegarden will by default create a device for each of the " +"available connections on startup. So in the example above, two MIDI devices " +"will be created by default even though you only need one. You would " +"generally then rename and apply patch maps to the first, and delete or " +"simply not use the second. Remember that there is no way for Rosegarden to " +"know what synths you actually have plugged in to the MIDI ports on your " +"computer: for this reason, the devices created at startup are just intended " +"to be a default set, and it's up to you to ensure that the devices you " +"configure match those you are really using." +msgstr "" +"I praktiken försöker Rosegarden normalt skapa en enhet för var och en av " +"de tillgängliga anslutningarna vid start. Så med exemplet ovan skulle två " +"MIDI-enheter normalt skapas även om du bara behöver en. Du skulle " +"därefter i allmänhet byta namn på och ange patchavbildningar för den " +"första, och ta bort eller helt enkelt inte använda den andra. Kom ihåg " +"att det finns inget sätt för Rosegarden att veta vilka syntar som du " +"verkligen har anslutit till MIDI-portarna på datorn. Av denna anledning är " +"enheterna som skapas vid start bara avsedda som en standarduppsättning, och " +"det är upp till dig att försäkra dig om att enheterna du ställer in " +"stämmer med de du verkligen använder." + +#. Tag: para +#: index.docbook:1075 +#, no-c-format +msgid "" +"Once configured, the studio setup is stored with every Rosegarden-format " +"file you save." +msgstr "" +"Så fort den är inställd, lagras studioinställningen med varje fil på " +"Rosegarden-format som du sparar." + +#. Tag: title +#: index.docbook:1081 +#, no-c-format +msgid "Managing MIDI devices" +msgstr "Hantering av MIDI-enheter" + +#. Tag: phrase +#: index.docbook:1090 +#, no-c-format +msgid "The MIDI device manager" +msgstr "MIDI-enhetshantering" + +#. Tag: para +#: index.docbook:1096 +#, no-c-format +msgid "" +"The MIDI device manager dialog shows you the MIDI devices that you currently " +"have available to you, and where they are connected. To reach this dialog, " +"use <menuchoice> <guimenu lang=\"en\">Composition</guimenu> " +"<guimenuitem>Studio</guimenuitem> <guimenuitem>Manage MIDI " +"Devices</guimenuitem> </menuchoice>." +msgstr "" +"Dialogrutan för MIDI-enhetshantering visar de MIDI-enheter som för " +"närvarande är tillgängliga, och var de är anslutna. Använd " +"<menuchoice><guimenu lang=\"sv\">Komposition</guimenu> " +"<guimenuitem>Studio</guimenuitem> <guimenuitem>Hantera " +"MIDI-enheter</guimenuitem></menuchoice> för att nå dialogrutan." + +#. Tag: para +#: index.docbook:1106 +#, no-c-format +msgid "" +"As described in the <link linkend=\"studio-introduction\">Devices, " +"Instruments and Connections</link> section, by default Rosegarden tries to " +"provide a plausible set of devices for you at startup, and to make sensible " +"connections for those devices. But the default configuration might not " +"always be suitable, and so this dialog allows you to rename devices and " +"modify their connections and play/record direction." +msgstr "" +"Som beskrivs i avsnittet <link linkend=\"studio-introduction\">Enheter, " +"instrument och anslutningar</link>, försöker Rosegarden normalt " +"tillhandahålla en rimlig uppsättning enheter vid start, och göra rimliga " +"anslutningar för enheterna. Standarduppsättningen kanske dock inte alltid " +"är lämplig, och därför låter dialogrutan dig byta namn på enheter och " +"ändra deras anslutningar och uppspelnings- eller inspelningsriktningar." + +#. Tag: para +#: index.docbook:1117 +#, no-c-format +msgid "" +"Each of the Play devices listed here provides a target for MIDI tracks to " +"talk to: if you add a new Play device, you will then have 16 new instruments " +"on this device which you can assign tracks to. If you then assign a " +"connection for that device, the tracks assigned to it will play to the " +"appropriate channel (depending on the instrument) of any MIDI synth attached " +"to that connection." +msgstr "" +"Var och en av uppspelningsenheterna här tillhandahåller en utgång för " +"MIDI-spår att skicka till: Om du lägger till en ny uppspelningsenhet, får " +"du 16 nya instrument i enheten som du kan tilldela spår till. Om du " +"därefter tilldelar en anslutning till enheten, spelas spåren som har " +"tilldelats till den på lämplig kanal (beroende på instrumentet) i vilken " +"MIDI-synt som helst som är kopplad till anslutningen." + +#. Tag: para +#: index.docbook:1127 +#, no-c-format +msgid "" +"The Record devices listed here represent possible sources for recording " +"MIDI. You can make one or more of them current (so that Rosegarden will " +"listen to them when recording) using the checkboxes on each line, as shown " +"in this dialog." +msgstr "" +"Inspelningsenheterna som listas här representerar möjliga källor för att " +"spela in MIDI. Du kan göra en eller flera av dem aktuella (så att " +"Rosegarden lyssnar på den vid inspelning) med kryssrutorna på varje rad, " +"som visas i dialogrutan." + +#. Tag: title +#: index.docbook:1136 +#, no-c-format +msgid "Managing banks and programs for MIDI devices" +msgstr "Hantera banker och program för MIDI-enheter" + +#. Tag: phrase +#: index.docbook:1145 +#, no-c-format +msgid "The MIDI bank and program editor" +msgstr "Editorn för MIDI-banker och program" + +#. Tag: para +#: index.docbook:1151 +#, no-c-format +msgid "" +"Remember that each MIDI device contains a number of instruments, and that " +"you can assign tracks to those instruments. In MIDI terms, each instrument " +"corresponds to a single channel on your MIDI synth. You can choose which of " +"the available voices (sounds) on your synth each instrument uses, but in " +"order to do this, you need to let Rosegarden know the names for all of the " +"available voices." +msgstr "" +"Kom ihåg att varje MIDI-enhet innehåller ett antal instrument, och att du " +"kan tilldela spår till instrumenten. Med MIDI-terminologi, motsvarar varje " +"instrument en enskild kanal i MIDI-synten. Du kan välja vilken av de " +"tillgängliga stämmorna (ljuden) i synten som varje instrument använder, " +"men för att göra det måste du tala om namnen på alla tillgängliga " +"stämmor för Rosegarden." + +#. Tag: para +#: index.docbook:1161 +#, no-c-format +msgid "" +"This dialog allows you to attach banks of programs (names for voices) to " +"your MIDI devices, thus permitting each instrument on a device to be set to " +"use one of those voices in the <link " +"linkend=\"segment-view-instrumentparameterbox\">Instrument Parameter " +"Box</link>." +msgstr "" +"Den här dialogrutan låter dig tilldela programbanker (namn på stämmor) " +"till MIDI-enheter, och på så sätt låta varje instrument i en enhet att " +"ställas in att använda en av stämmorna i <link " +"linkend=\"segment-view-instrumentparameterbox\"> " +"instrumentparameterrutan</link>." + +#. Tag: para +#: index.docbook:1170 +#, no-c-format +msgid "" +"The usual way to set up the program names for a device is simply to import " +"them from one of the supplied device (\".rgd\") files. To do this, select a " +"device in the list on the left of the dialog, then click the Import button " +"below the list and choose the .rgd file corresponding to your synth." +msgstr "" +"Det vanliga sättet att ställa in programnamn för en enhet är att helt " +"enkelt importera dem från en av enhetsfilerna (\".rgd\") som " +"tillhandahålls. För att göra det, markera en enhet i listan till vänster " +"i dialogrutan, klicka därefter på importknappen under listan och välj " +".rgd-filen som motsvarar din synt." + +#. Tag: para +#: index.docbook:1179 +#, no-c-format +msgid "" +"If there is no current .rgd file available for your synth, then you can use " +"this dialog to create a new bank. To do this you will have to find the " +"program map in your synth's MIDI Implementation Chart and enter all the " +"names by hand: you can then Export them to a .rgd file to share with other " +"Rosegarden users. Contact the rosegarden-user mailing list if you have made " +"a new .rgd file and would like to share it. (This is how all of the existing " +".rgd files have come to be included with Rosegarden: other users have " +"contributed them.)" +msgstr "" +"Om det inte finns en aktuell .rgd-fil tillgänglig för din synt, kan du " +"använda dialogrutan för att skapa en ny bank. För att göra det måste du " +"hitta programavbildningen i din synts MIDI-implementeringsdiagram och skriva " +"in namnen för hand: Därefter kan du exportera dem till en .rgd-fil att " +"dela med andra användare av Rosegarden. Kontakta e-postlistan " +"rosegarden-user om du har skapat en ny .rgd-fil och vill bidra med den. (Det " +"är hur alla befintliga .rgd-filer har kommit att inkluderas med Rosegarden: " +"andra användare har bidragit dem.)" + +#. Tag: title +#: index.docbook:1192 +#, no-c-format +msgid "Percussion Key Mappings" +msgstr "Tonavbildningar för slagverk" + +#. Tag: para +#: index.docbook:1194 +#, no-c-format +msgid "" +"Many MIDI synthesizers have at least one percussion program, in which each " +"\"pitch\" plays a different type of sound. Rosegarden contains a dedicated " +"percussion matrix editor to view and edit notes against a scale consisting " +"of the correct names for the pitches, instead of against the conventional " +"piano keyboard pitch scale." +msgstr "" +"Många MIDI-syntar har åtminstone ett slagverksprogram, där varje \"tonhöjd\" " +"spelar ett annorlunda ljud. Rosegarden innehåller en särskild matriseditor för " +"slagverk för att visa och redigera toner med en skala som består av de " +"riktiga namnen på tonhöjderna, istället för den konventionella tonskalan på " +"ett piano." + +#. Tag: para +#: index.docbook:1203 +#, no-c-format +msgid "" +"The key mappings available for a particular MIDI device are also defined in " +"the Rosegarden device (\".rgd\") file. Each MIDI program that is defined as " +"a percussion program can have a key mapping associated with it; if there is " +"one, then it will be used by default in any track that is assigned to this " +"program. Like program and bank definitions, key mappings can be imported " +"from and exported to .rgd files." +msgstr "" +"Tonavbildningarna som är tillgängliga för en viss MIDI-synt definieras också " +"i Rosegardens enhetsfil (\".rgd\"). Varje MIDI-program som definieras som " +"ett slagverksprogram kan ha en tillhörande tonavbildning. Om det finns en, " +"används den normalt för alla spår som tilldelas programmet. Liksom " +"program och bankdefinitioner kan tonavbildningar importeras från och " +"exporteras till .rgd-filer." + +#. Tag: title +#: index.docbook:1215 +#, no-c-format +msgid "SoundFonts" +msgstr "Ljudteckensnitt" + +#. Tag: para +#: index.docbook:1217 +#, no-c-format +msgid "" +"If you happen to be using a soft-synth or soundcard synth that uses " +"SoundFont (.sf2) files, you can simply load the correct program names " +"directly from your .sf2 file into this dialog. Just ask to Import as normal, " +"and then choose the .sf2 file that you are using instead of a .rgd file." +msgstr "" +"Om du råkar använda en programvarusynt eller ljudkortssynt som använder " +"ljudteckensnittsfiler (.sf2), kan du helt enkelt ladda riktiga programnamn " +"direkt från .sf2-filen i dialogrutan. Begär bara import som vanligt, och " +"välj därefter .sf2-filen som du använder istället för en .rgd-fil." + +#. Tag: para +#: index.docbook:1225 +#, no-c-format +msgid "" +"Note that the Studio only manages information about existing MIDI devices " +"for Rosegarden, it does not actually handle tasks such as loading a " +"SoundFont to your soundcard in the first place. If you want to make sure a " +"SoundFont is loaded to your soundcard when Rosegarden starts up, you should " +"use the special \"Load SoundFont to SoundBlaster card at startup\" option in " +"the sequencer configuration in <menuchoice> <guimenu " +"lang=\"en\">Settings</guimenu> <guimenuitem>Configure " +"Rosegarden...</guimenuitem> </menuchoice>." +msgstr "" +"Observera att studion bara hanterar information om befintliga MIDI-enheter i " +"Rosegarden. Den hanterar inte uppgifter som att ladda ett ljudteckensnitt " +"till ljudkortet från början. Om du vill försäkra dig om att ett " +"ljudteckensnitt laddas till ljudkortet när Rosegarden startas, ska du " +"använda det speciella alternativet \"Ladda ljudsamplingar till " +"Soundblaster-kort vid start\" i inställningen av musikbehandlaren under " +"<menuchoice><guimenu lang=\"sv\">Inställningar</guimenu> " +"<guimenuitem>Anpassa Rosegarden...</guimenuitem></menuchoice>." + +#. Tag: title +#: index.docbook:1240 +#, no-c-format +msgid "Variations" +msgstr "Varianter" + +#. Tag: para +#: index.docbook:1242 +#, no-c-format +msgid "" +"Some MIDI devices (for example, those from Roland) organise their program " +"names using a scheme known as \"variations\". For these devices, you " +"generally want to select a program by first selecting the basic program name " +"— such as a piano — and then selecting one of a set of " +"variations on that program — such as an electric piano. This is in " +"contrast to General MIDI-based synths, which organise their programs into " +"banks and expect you to choose a bank first and then a program from that " +"bank." +msgstr "" +"Vissa MIDI-enheter (till exempel de från Roland) organiserar programnamn " +"på ett sätt som kallas \"varianter\". För dessa enheter vill man i " +"allmänhet välja ett program genom att först ange ett grundprogramnamn, " +"som ett piano, och därefter ange en av ett antal varianter av programmet, " +"som ett elektriskt piano. Detta skiljer sig från syntar baserad på " +"generell MIDI, som organiserar programmen i banker och förväntar sig att " +"du först väljer en bank och därefter ett program i banken." + +#. Tag: para +#: index.docbook:1255 +#, no-c-format +msgid "" +"Rosegarden can support devices that use variations, but you still have to " +"enter the program names in a bank format. Internally, devices that use " +"variations still use MIDI bank select controllers to choose between the " +"variations; you need to find out from your synth's documentation whether " +"your device uses the LSB or MSB bank select to choose variations, and which " +"bank number corresponds to which variation. You can then enter the banks as " +"normal, and use the \"Show Variation list based on MSB/LSB\" option on the " +"bank dialog to tell Rosegarden to show variations instead of banks when " +"displaying that device in an instrument parameter box." +msgstr "" +"Rosegarden kan stödja enheter som använder varianter, men du måste ändå " +"skriva in programnamnen med bankformat. Internt använder enheter med " +"variationer fortfarande styrning med val av MIDI-bank för att välja bland " +"variationerna: Du måste ta reda på om enheten använder mest signifikant " +"eller minst signifikant värde i bankväljaren för att ange variationer, " +"och vilket banknummer som motsvarar vilken variant. Därefter kan du skriva " +"in bankerna som vanligt, och använda alternativet \"Visa variantlista " +"baserad på Mest signifikant värde/Minst signifikant värde\" i " +"bankdialogrutan för att tala om för Rosegarden att varianter istället " +"för banker ska visas när enheten visas i en instrumentparameterruta." + +#. Tag: title +#: index.docbook:1272 +#, no-c-format +msgid "Program mapping on &MIDI; import" +msgstr "Programavbildning vid &MIDI;-import" + +#. Tag: para +#: index.docbook:1273 +#, no-c-format +msgid "" +"When you import a &MIDI; file into a composition, &rosegarden; uses the " +"existing studio setup to determine how to map the &MIDI; programs onto " +"&rosegarden; instruments. The aim is to ensure that every &MIDI; program " +"gets mapped to an instrument that really exists in your studio (and thus is " +"actually attached to your computer), so that all the &MIDI; tracks can be " +"heard." +msgstr "" +"När du importerar en &MIDI;-fil till en komposition, använder &rosegarden; " +"befintlig studioinställning för att avgöra hur &MIDI;-programmen avbildas " +"på &rosegarden;-instrument. Målet är att försäkra att varje " +"&MIDI;-program avbildas på ett instrument som verkligen finns i studion " +"(och alltså verkligen är anslutet till datorn), så att alla &MIDI;-spår " +"kan höras." + +#. Tag: para +#: index.docbook:1283 +#, no-c-format +msgid "" +"The &MIDI; program-change and bank-select events found in the imported file " +"are used when importing, but only as an aid to help find the appropriate " +"instrument for each &MIDI; track from the set of instruments in your studio. " +"So, for example, if your studio is currently set up to contain only " +"<acronym>GM</acronym> instruments, and you import a &MIDI; file with " +"<acronym>GS</acronym> program changes onto it, &rosegarden; will remap the " +"<acronym>GS</acronym> banks back onto <acronym>GM</acronym> because they're " +"all it knows that you have at the time you import the file. It doesn't " +"remember the original <acronym>GS</acronym> program numbers." +msgstr "" +"&MIDI; programändrings- och bankvalshändelserna som hittas i den " +"importerade filen används vid import, men bara som en hjälp att hitta " +"lämpligt instrument för varje &MIDI;-spår bland instrumentuppsättningen " +"i studion. Om studion till exempel för närvarande är inställd att bara " +"innehålla <acronym>GM</acronym>-instrument, och du importerar en &MIDI;-fil " +"som innehåller <acronym>GS</acronym>-programändringar, avbildar " +"&rosegarden; <acronym>GS</acronym>-bankerna tillbaka till " +"<acronym>GM</acronym> eftersom de är allt som den vet om att du har vid " +"tiden då filen importeras. Den kommer inte ihåg ursprungliga " +"<acronym>GS</acronym>-programnummer." + +#. Tag: para +#: index.docbook:1296 +#, no-c-format +msgid "" +"This means that you should always ensure that your studio is correctly " +"configured for the devices you actually have, before you import the &MIDI; " +"file. Otherwise the program data in the &MIDI; file may be lost." +msgstr "" +"Det här betyder att du alltid ska försäkra dig om att din studio är " +"riktigt inställd för enheterna som du verkligen har, innan du importerar " +"&MIDI;-filen. Annars kan programdata i &MIDI;-filen gå förlorad." + +#. Tag: title +#: index.docbook:1308 +#, no-c-format +msgid "Audio Routing" +msgstr "Ljudfördelning" + +#. Tag: para +#: index.docbook:1309 +#, no-c-format +msgid "" +"Any Rosegarden track assigned to an audio or synth plugin instrument becomes " +"part of Rosegarden's audio routing architecture. There are 16 audio " +"instruments and 16 synth plugin instruments, and each of these has a set of " +"adjustable parameters including fader level, pan, effects and so on. These " +"are generally configurable in the <link " +"linkend=\"segment-view-instrumentparameterbox\">Instrument Parameter " +"Box</link> or <link linkend=\"studio-audio-mixer\">audio mixer</link>. Each " +"audio instrument also has an input connection, and both audio and synth " +"plugin instruments have an output connection." +msgstr "" +"Alla spår i Rosegarden som tilldelas till ett ljudinstrument eller " +"syntinsticksmodulinstrument blir en del av Rosegardens " +"ljudfördelningsarkitektur. Det finns 16 ljudinstrument och 16 " +"syntinsticksmodulinstrument, och vart och ett av dem har en uppsättning " +"justerbara parametrar som omfattar toningsnivå, panorering, effekter och " +"så vidare. De är i allmänhet inställningsbara i <link " +"linkend=\"segment-view-instrumentparameterbox\">instrumentparameterrutan</lin" +"k> eller <link linkend=\"studio-audio-mixer\">ljudmixern</link>. Varje " +"ljudinstrument har också en ingångsanslutning, och både ljudinstrument " +"och syntinsticksmodulinstrument har en utgångsanslutning." + +#. Tag: para +#: index.docbook:1323 +#, no-c-format +msgid "" +"An instrument's input connection defines where Rosegarden will read audio " +"data from when recording to this instrument. The most usual setting would be " +"to one of Rosegarden's external audio inputs, the number of which is " +"configurable in the <link linkend=\"studio-audio-mixer\">audio mixer</link>. " +"These correspond to JACK audio ports exposed by Rosegarden, to which you can " +"connect outputs from any other JACK audio application or soundcard capture " +"ports using an external JACK router application such as <ulink " +"url=\"http://qjackctl.sf.net/\">QJackCtl</ulink>. You can also set an " +"instrument's audio input to the output of one of Rosegarden's built-in audio " +"submasters or master output for mixdowns." +msgstr "" +"Ett instruments ingångsanslutning definierar varifrån Rosegarden läser " +"ljuddata vid inspelning till instrumentet. Den vanligaste inställningen är " +"en av Rosegardens externa ljudingångar, vars antal kan ställas in i <link " +"linkend=\"studio-audio-mixer\">ljudmixern</link>. De motsvarar JACK " +"ljudportar exponerade av Rosegarden, där du kan ansluta utgångar från " +"vilket JACK ljudprogram som helst eller från någon av ljudkortets portar " +"med ett externt JACK fördelningsprogram som <ulink " +"url=\"http://qjackctl.sf.net/\">QJackCtl</ulink>. Du kan också ställa in " +"ett instruments ljudingång till en av Rosegardens inbyggda " +"delnivåutgångar eller huvudutgångar för ihopmixningar." + +#. Tag: para +#: index.docbook:1337 +#, no-c-format +msgid "" +"An instrument's output connection defines where the audio goes when played. " +"Instruments default to sending their audio to Rosegarden's master output, " +"which is another (stereo pair of) external JACK port(s) that can then be " +"connected up using the same external JACK router. However, Rosegarden also " +"supports up to eight internal submaster busses, to which you can send " +"instrument outputs instead so as to group instruments into related " +"categories. You can control the number and routing of these in the <link " +"linkend=\"studio-audio-mixer\">audio mixer</link>." +msgstr "" +"Ett instruments utgångsanslutning definierar var ljudet tar vägen när det " +"spelas upp. Instrumentens normalinställning är att skicka ljud till " +"Rosegardens huvudutgång, som är en annan extern JACK port (eller ett par " +"portar vid stereo), som därefter kan anslutas genom att använda samma " +"externa JACK fördelningsprogram. Rosegarden stöder dock också upp till " +"åtta interna delutgångsbussar, dit du kan skicka utdata från instrument " +"istället, för att gruppera instrument i samhörande kategorier. Du kan " +"styra antalet och fördelningen av dem i <link " +"linkend=\"studio-audio-mixer\">ljudmixern</link>." + +#. Tag: para +#: index.docbook:1348 +#, no-c-format +msgid "" +"Rosegarden currently supports effects using a set of pre-fader insert " +"effects slots for each audio instrument. You cannot yet assign effects to " +"the submaster busses, and Rosegarden does not yet support send effects, " +"although you can obtain similar results using an external JACK effects and " +"mixing architecture." +msgstr "" +"Rosegarden stöder för närvarande effekter med en uppsättning " +"effektplatser som infogas innan toningen för varje ljudinstrument. Du kan " +"ännu inte tilldela effekter till delnivåbussarna, och Rosegarden stöder " +"ännu inte att skicka effekter, även om du kan uppnå liknande resultat " +"genom att använda JACK externa effekter och mixningsarkitektur." + +#. Tag: para +#: index.docbook:1356 +#, no-c-format +msgid "" +"Some further details of audio routing configuration, mixing, and effects are " +"discussed in the <link linkend=\"studio-audio-mixer\">audio mixer</link>, " +"<link linkend=\"segment-view-instrumentparameterbox\">instrument parameter " +"box</link> and <link linkend=\"studio-plugins\">audio plugins</link> " +"sections." +msgstr "" +"Några ytterligare detaljer angående inställning av ljudfördelning, " +"mixning och effekter beskrivs i avsnitten <link " +"linkend=\"studio-audio-mixer\"> ljudmixern</link>, <link " +"linkend=\"segment-view-instrumentparameterbox\">instrumentparameterrutan</lin" +"k> och <link linkend=\"studio-plugins\">ljudinsticksmoduler</link>." + +#. Tag: title +#: index.docbook:1365 +#, no-c-format +msgid "The Audio Mixer" +msgstr "Ljudmixern" + +#. Tag: phrase +#: index.docbook:1373 +#, no-c-format +msgid "&rosegarden;'s Audio Mixer" +msgstr "&rosegarden;s ljudmixer" + +#. Tag: para +#: index.docbook:1379 +#, no-c-format +msgid "" +"Rosegarden's audio mixer window, reached through <menuchoice> <guimenu " +"lang=\"en\">Composition</guimenu> <guimenuitem>Studio</guimenuitem> " +"<guimenuitem>Audio Mixer</guimenuitem></menuchoice>, resembles a hardware " +"audio mixer and provides a way to see and change the state of a number of " +"audio instruments at once. It contains many of the same controls as found in " +"the audio and synth plugin <link " +"linkend=\"segment-view-instrumentparameterbox\">instrument parameter " +"boxes</link>, most importantly a playback level meter and fader control for " +"each audio and synth plugin instrument, as well as routing controls, pan, " +"mono/stereo and effects plugin slots." +msgstr "" +"Rosegardens ljudmixningsfönster, som visas med <menuchoice><guimenu " +"lang=\"sv\">Komposition</guimenu> <guimenuitem>Studio</guimenuitem> " +"<guimenuitem>Ljudmixer</guimenuitem></menuchoice>, liknar en ljudmixer i " +"hårdvara och tillhandahåller ett sätt att se och ändra tillståndet för " +"ett antal ljudinstrument på en gång. Den innehåller många likadana " +"knappar som finns i ljud- och syntinsticksmodulernas <link " +"linkend=\"segment-view-instrumentparameterbox\"> " +"instrumentparameterrutor</link>, där de viktigaste är mätaren av " +"uppspelningsnivå och toningskontroll för varje ljudinstrument och " +"syntinsticksmodulinstrument, samt fördelningskontroll, panorering, " +"mono/stereo och platser för effektinsticksmoduler." + +#. Tag: para +#: index.docbook:1395 +#, no-c-format +msgid "" +"The audio mixer window is also where you see and control the master audio " +"output level (at the far right of the picture above), as well as the record " +"level (to the left of the master fader) and submaster output levels." +msgstr "" +"Ljudmixerfönstret är också platsen där du ser och styr huvudljudnivån " +"(längst till höger i bilden ovan), samt inspelningsnivån (till vänster " +"om huvudtoningen) och delutnivåer." + +#. Tag: para +#: index.docbook:1401 +#, no-c-format +msgid "" +"The audio mixer's <menuchoice> <guimenu " +"lang=\"en\">Settings</guimenu></menuchoice> menu is particularly relevant. " +"Apart from controlling what will be shown in the mixer window, this menu " +"also contains the <link linkend=\"studio-audio-routing\">audio " +"routing</link> settings for the number of stereo audio record inputs " +"available and the number of submasters. These are studio settings whose " +"values are saved with your Rosegarden format file." +msgstr "" +"Menyn <menuchoice><guimenu lang=\"sv\">Inställningar</guimenu></menuchoice> " +"i ljudmixern är särskilt relevant. Förutom att styra vad som visas i " +"mixerfönstret, innehåller menyn också inställningen av <link " +"linkend=\"studio-audio-routing\">ljudfördelningen</link> för antalet " +"ljudinspelningsingångar i stereo som är tillgängliga och för antalet " +"delnivåutgångar. De är studioinställningar som sparas med din Rosegarden " +"formatfil." + +#. Tag: para +#: index.docbook:1411 +#, no-c-format +msgid "" +"Note that if you are not actually using any submasters (i.e. if there are no " +"instruments configured to route their output to a submaster) you may see a " +"small performance improvement if you set the number of submasters explicitly " +"to None, rather than keeping unused ones in the configuration." +msgstr "" +"Observera att om du i själva verket inte använder några delnivåer (dvs. " +"om det inte finns några instrument som är inställda att skicka sin " +"utsignal till en delnivå) kan du se en liten prestandaförbättring om du " +"uttryckligen ställer in antalet delnivåer till inga, istället för att " +"behålla oanvända i inställningen." + +#. Tag: title +#: index.docbook:1420 +#, no-c-format +msgid "The MIDI Mixer" +msgstr "MIDI-mixern" + +#. Tag: phrase +#: index.docbook:1428 +#, no-c-format +msgid "&rosegarden;'s MIDI Mixer" +msgstr "&rosegarden;s MIDI-mixer" + +#. Tag: para +#: index.docbook:1433 +#, no-c-format +msgid "" +"Rosegarden's MIDI mixer window, reached through <menuchoice> <guimenu " +"lang=\"en\">Composition</guimenu> <guimenuitem>Studio</guimenuitem> " +"<guimenuitem>MIDI Mixer</guimenuitem></menuchoice>, provides a way to see " +"and edit the <link " +"linkend=\"segment-view-instrumentparameterbox-midi\">instrument parameter " +"values</link> for a number of MIDI instruments at once." +msgstr "" +"Rosegardens MIDI-mixningsfönster, som visas med <menuchoice><guimenu " +"lang=\"sv\">Komposition</guimenu> <guimenuitem>Studio</guimenuitem> " +"<guimenuitem>MIDI-mixer</guimenuitem></menuchoice>, tillhandahåller ett " +"sätt att se och redigera <link " +"linkend=\"segment-view-instrumentparameterbox-midi\">instrumentparametervärd" +"en</link> för ett antal MIDI-instrument på en gång." + +#. Tag: para +#: index.docbook:1443 +#, no-c-format +msgid "" +"The window is organised using a tabbed pane. Along the bottom, you will see " +"one tab for each playback MIDI device in your studio configuration. When you " +"select a device tab, the rest of the window will update to show the controls " +"for the 16 instruments of that device." +msgstr "" +"Fönstret är organiserat som en ruta med flikar. Längs nederkanten ser du " +"en flik för varje MIDI-uppspelningsenhet i studioinställningen. När en " +"enhetsflik väljes, uppdateras resten av fönstret för att visa knapparna " +"för enhetens 16 instrument." + +#. Tag: para +#: index.docbook:1450 +#, no-c-format +msgid "" +"The controls shown for each instrument are those set up in the control " +"parameter manager, as well as volume (corresponding to the MIDI volume " +"control change, not to MIDI velocity or audio dB levels) and an approximate " +"output level indicator." +msgstr "" +"Knapparna som visas för varje instrument är de som ställts in i " +"hanteringen av styrparametrar, samt volym (som motsvarar ändring av " +"MIDI-volymstyrningen, inte en MIDI-ljudstyrka eller ljudnivå i decibel) och " +"en ungefärlig utnivåindikator." + +#. Tag: title +#: index.docbook:1460 +#, no-c-format +msgid "Audio Plugins" +msgstr "Ljudinsticksmoduler" + +#. Tag: para +#: index.docbook:1461 +#, no-c-format +msgid "" +"An audio plugin is a piece of software, separate from Rosegarden, that " +"Rosegarden can load and use in order to perform a particular audio " +"processing task. These can be broadly divided into effects plugins and synth " +"plugins. Effects plugins take an audio input and manipulate it to produce a " +"different audio output; synth plugins take MIDI-like events as input and " +"turn them into audio output. Rosegarden uses the Linux standard LADSPA " +"plugin API for effects and the DSSI plugin API for synths, permitting the " +"use of large numbers of open-source plugins made available by many " +"developers." +msgstr "" +"En ljudinsticksmodul är en programvarumodul, skild från Rosegarden, men " +"som Rosegarden kan ladda och använda för att utföra en viss " +"ljudbehandlingsuppgift. De kan grovt delas upp i effektinsticksmoduler och " +"syntinsticksmoduler. Effektinsticksmoduler tar ljudindata och behandlar det " +"för att skapa annorlunda ljudutdata. Rosegarden använder Linux-standarden " +"LADSPA för effektinsticksmodulernas programmeringsgränssnitt, och DSSI " +"för syntinsticksmodulernas programmeringsgränssnitt, vilket gör det " +"möjligt att använda ett stort antal insticksmoduler med öppen källkod " +"som gjorts tillgängliga av många utvecklare." + +#. Tag: para +#: index.docbook:1472 +#, no-c-format +msgid "" +"The use of plugins has a cost in CPU time, as audio processing in real time " +"usually takes a significant amount of work even on a modern CPU. It also has " +"a potential cost in reliability: when Rosegarden is running a plugin, if the " +"plugin hangs or crashes, so does Rosegarden. Many plugins are very reliable, " +"but it's inevitable that some will not be so well tested." +msgstr "" +"Användning av insticksmoduler ger en kostnad i processortid, eftersom " +"ljudbehandling i realtid oftast kräver en väsentlig mängd arbete till och " +"med med en modern processor. Det ger också en potentiell kostnad i " +"tillförlitlighet: När Rosegarden kör en insticksmodul, och " +"insticksmodulen hänger sig eller kraschar, så gör Rosegarden också det. " +"Många insticksmoduler är mycket tillförlitliga, men det är oundvikligt " +"att vissa inte är så vältestade." + +#. Tag: title +#: index.docbook:1481 +#, no-c-format +msgid "Effects plugins" +msgstr "Effektinsticksmoduler" + +#. Tag: para +#: index.docbook:1481 +#, no-c-format +msgid "" +"An effects plugin is something that you can use to modify an audio signal in " +"a controllable way. Examples include reverb, delay effects, dynamic " +"compression and so on." +msgstr "" +"En effektinsticksmodul är något som du kan använda för att ändra en " +"ljudsignal på ett styrbart sätt. Exempel omfattar eko, " +"fördröjningseffekter, dynamisk komprimering och så vidare." + +#. Tag: para +#: index.docbook:1486 +#, no-c-format +msgid "" +"Every audio or synth-plugin instrument in Rosegarden has five associated " +"effects slots. By default these are empty, but you can load plugins into " +"them in order to chain up to five effects onto the audio signal before it " +"goes through fader level and pan processing." +msgstr "" +"Varje ljud- eller syntinsticksmodulinstrument i Rosegarden har fem " +"tillhörande effektplatser. Normalt är de tomma, men du kan ladda " +"insticksprogram i dem för att bilda en kedja med upp till fem effekter för " +"ljudsignalen innan den går igenom toningsnivå och panoreringsbehandling." + +#. Tag: para +#: index.docbook:1492 +#, no-c-format +msgid "" +"To load a plugin to a slot, click its button on the <link " +"linkend=\"segment-view-instrumentparameterbox-audio\">instrument parameter " +"box</link>:" +msgstr "" +"För att ladda en insticksmodul på en plats, klicka på dess knapp i <link " +"linkend=\"segment-view-instrumentparameterbox-audio\">instrumentparameterruta" +"n</link>:" + +#. Tag: phrase +#: index.docbook:1503 +#, no-c-format +msgid "Plugin Slot Buttons" +msgstr "Insticksplatsknappar" + +#. Tag: para +#: index.docbook:1508 +#, no-c-format +msgid "" +"(These buttons are also optionally available in the <link " +"linkend=\"studio-audio-mixer\">audio mixer</link> window.)" +msgstr "" +"(Dessa knappar är också alternativt tillgängliga i <link " +"linkend=\"studio-audio-mixer\">ljudmixerns fönster</link>.)" + +#. Tag: para +#: index.docbook:1511 +#, no-c-format +msgid "" +"Clicking a plugin button will pop up the plugin dialog. This shows you the " +"available categories of effects in the first menu; select one, and you can " +"then choose your plugin in the second menu." +msgstr "" +"Att klicka på en insticksmodulknapp visar insticksmoduldialogrutan. Den " +"visar tillgängliga effektkategorier i den första menyn. Markera en, så " +"kan du därefter välja insticksmodul i den andra menyn." + +#. Tag: phrase +#: index.docbook:1523 +#, no-c-format +msgid "A &rosegarden; Plugin Dialog" +msgstr "En insticksdialogruta i &rosegarden;" + +#. Tag: para +#: index.docbook:1529 +#, no-c-format +msgid "" +"Below the plugin selection menus, the dialog gives you a varying number of " +"rotary controllers showing all the modifiable parameters for the plugin you " +"have selected. To change a value, just click a rotary and drag up and down " +"or left and right. (Up or right to raise the value, down or left to lower " +"it.) You can also roll the mouse wheel to change the value, or click with " +"the middle mouse button to reset it to its initial default." +msgstr "" +"Under menyerna för val av insticksmoduler, har dialogrutan ett varierande " +"antal vridbara rattar som visar alla parametrar som kan ändras för " +"insticksprogrammet du har valt. För att ändra ett värde, klicka bara på " +"en ratt och dra uppåt och neråt, eller vänster och höger. (Uppåt " +"eller åt höger för att öka värdet, neråt eller åt vänster för att " +"minska det.) Du kan också rulla mushjulet för att ändra värdet, eller " +"klicka med musens mittenknapp för att återställa det till det " +"ursprungliga normalvärdet." + +#. Tag: para +#: index.docbook:1538 +#, no-c-format +msgid "" +"It is also possible to copy one plugin with its current configuration into " +"another slot, so as to use the same plugin settings with more than one " +"instrument, or to base one plugin configuration on another. Just click the " +"Copy button when you have the plugin set up the way you want it, and then " +"open another plugin slot's plugin dialog and click Paste." +msgstr "" +"Det är också möjligt att kopiera en insticksmodul med sin nuvarande " +"inställning till en annan plats, för att använda samma " +"insticksmodulinställningar för mer än ett instrument, eller för att " +"basera en insticksmodulinställning på en annan. Klicka bara på knappen " +"Kopiera när du har ställt in insticksmodulen som du vill ha den, och " +"öppna därefter dialogrutan för en annan insticksmodulplats och klicka på " +"Klistra in." + +#. Tag: para +#: index.docbook:1545 +#, no-c-format +msgid "" +"Finally, you can use the Bypass toggle to remove a plugin temporarily from " +"processing while retaining its configuration." +msgstr "" +"Till sist kan du använda åtgärden Förbikoppla för att tillfälligt ta " +"bort en insticksmodul från behandlingen, men ändå behålla dess " +"inställning." + +#. Tag: title +#: index.docbook:1551 +#, no-c-format +msgid "Synth plugins" +msgstr "Syntinsticksmoduler" + +#. Tag: para +#: index.docbook:1552 +#, no-c-format +msgid "" +"Synth plugins can be used in place of hardware or standalone soft-synth MIDI " +"devices, to generate sounds from your note event segments." +msgstr "" +"Syntinsticksmoduler kan användas istället för MIDI-enheter i hårdvara " +"eller fristående programvarusyntar, för att skapa ljud från segmenten med " +"tonhändelser." + +#. Tag: para +#: index.docbook:1557 +#, no-c-format +msgid "" +"Using a synth plugin gives you somewhat better control and repeatability " +"than using an external MIDI device, because Rosegarden will be able to load " +"the correct plugins for you and use the correct settings the next time you " +"load your same file. Plugins may also offer better timing resolution than " +"external MIDI devices, and synth plugin instruments have the advantage of " +"being routable like audio instruments, which also means you can add effects " +"plugins on top of them." +msgstr "" +"Att använda en syntinsticksmodul ger dig något bättre kontroll och " +"upprepningsbarhet än att använda en extern MIDI-enhet, eftersom Rosegarden " +"kan ladda rätt insticksmodul åt dig och använda riktiga inställningar " +"nästa gång du laddar samma fil. Insticksmoduler kan också ge bättre " +"tidsupplösning än externa MIDI-enheter, och syntinsticksmodulinstrument " +"har fördelen att vara fördelningsbara som ljudinstrument, vilket också " +"betyder att du kan lägga till effektinsticksmoduler ovanför dem." + +#. Tag: para +#: index.docbook:1567 +#, no-c-format +msgid "" +"To make use of a synth plugin, first <link " +"linkend=\"segment-view-instruments\">assign a track</link> to a synth plugin " +"instrument, and then load a synth plugin by clicking on the topmost button " +"in the <link " +"linkend=\"segment-view-instrumentparameterbox-synth\">instrument parameter " +"box</link>:" +msgstr "" +"För att använda en syntinsticksmodul, <link " +"linkend=\"segment-view-instruments\">tilldela först ett spår</link> till " +"ett syntinsticksmodulinstrument, och ladda därefter en syntinsticksmodul " +"genom att klicka på den översta knappen i <link " +"linkend=\"segment-view-instrumentparameterbox-synth\">instrumentparameterruta" +"n</link>:" + +#. Tag: phrase +#: index.docbook:1581 +#, no-c-format +msgid "Synth Plugin Buttons" +msgstr "Syntinsticksmodulknappar" + +#. Tag: para +#: index.docbook:1587 +#, no-c-format +msgid "" +"This will bring up the same plugin dialog as shown above for effects " +"plugins, but with a list of synth plugins instead of effects. Once again, " +"you will be shown the particular set of rotary parameters for the synth you " +"have selected. Synth plugins may also have \"programs\", selectable from a " +"menu -- this menu will only appear if you have chosen a synth that supports " +"them. When you have selected and configured a synth plugin for an " +"instrument, any MIDI data on tracks assigned to that instrument should play " +"through that synth, as should incoming MIDI data during recording or " +"monitoring." +msgstr "" +"Det här visar samma insticksmoduldialogruta som visas ovan för " +"effektinsticksmoduler, men med en lista över syntinsticksmoduler istället " +"för effekter. Återigen visas den särskilda uppsättning med vridbara " +"parametrar för synten du har valt. Syntinsticksmoduler kan också ha " +"\"program\" som kan väljas i en meny. Menyn visas bara om du har valt en " +"synt som stöder det. När du har valt och ställt in en syntinsticksmodul " +"för ett instrument, ska all MIDI-data på spår som tilldelas till det " +"instrumentet spelas via synten, liksom inkommande MIDI-data under inspelning " +"eller övervakning." + +#. Tag: title +#: index.docbook:1601 +#, no-c-format +msgid "Plugin native editor windows" +msgstr "Egna redigeringsfönster i en insticksmodul" + +#. Tag: para +#: index.docbook:1603 +#, no-c-format +msgid "" +"Most plugins can be controlled completely using the rotary controllers in " +"Rosegarden's plugin dialog. However, a few plugins (generally synths) also " +"have their own editor windows which can be switched on or off from " +"Rosegarden and which may provide more complete or more organised controls." +msgstr "" +"De flesta insticksmoduler kan styras helt och hållet med rattarna i " +"Rosegardens insticksmoduldialogruta. Dock har några få insticksmoduler (i " +"allmänhet syntar) också sina egna redigeringsfönster som kan aktiveras " +"eller inaktiveras från Rosegarden, och som kan tillhandahålla " +"fullständigare eller bättre organiserade knappar." + +#. Tag: para +#: index.docbook:1610 +#, no-c-format +msgid "" +"When you select a plugin that has its own editor window, the button at the " +"lower left of the plugin dialog labelled \"Editor\" will become active:" +msgstr "" +"När du väljer en insticksmodul som har sitt eget redigeringsfönster, " +"aktiveras knappen nere till vänster i insticksmodulens dialogruta som heter " +"\"Editor\":" + +#. Tag: phrase +#: index.docbook:1621 +#, no-c-format +msgid "A Plugin Editor Button" +msgstr "Redigeringsknappen i en insticksmodul" + +#. Tag: para +#: index.docbook:1627 +#, no-c-format +msgid "" +"(For synth plugins, there is a similar button in the instrument parameter " +"box.) Clicking this button should show the plugin's own editor window. Any " +"changes you make in this editor window should also be reflected in " +"Rosegarden's own plugin dialog, if visible, and of course should be saved in " +"your Rosegarden file as normal." +msgstr "" +"(För syntinsticksmoduler finns en liknande knapp i " +"instrumentparameterrutan.) Att klicka på knappen visar insticksmodulens " +"eget redigeringsfönster. Alla ändringar som du gör i redigeringsfönstret " +"ska också synas i Rosegardens egen insticksmoduldialogruta, och ska " +"naturligtvis sparas i din Rosegarden-fil som vanligt." + +#. Tag: title +#: index.docbook:1637 +#, no-c-format +msgid "Metronomes" +msgstr "Metronomer" + +#. Tag: para +#: index.docbook:1638 +#, no-c-format +msgid "" +"Rosegarden has two built-in metronomes, one for use during recording and one " +"that can be switched on during normal playback. They work by sending notes " +"to a MIDI instrument, and both metronomes use the same instrument, pitch and " +"velocity information." +msgstr "" +"Rosegarden har två inbyggda metronomer, en för användning under " +"inspelning och en som kan kopplas in under normal uppspelning. De fungerar " +"genom att skicka toner till ett MIDI-instrument, och båda metronomerna " +"använder samma instrument, tonhöjds- och ljudstyrkeinformation." + +#. Tag: phrase +#: index.docbook:1653 +#, no-c-format +msgid "&rosegarden;'s metronome configuration dialog" +msgstr "&rosegarden;s inställningsdialogruta för metronom" + +#. Tag: para +#: index.docbook:1658 +#, no-c-format +msgid "" +"To configure the metronomes, use <menuchoice> <guimenu " +"lang=\"en\">Composition</guimenu> <guimenu lang=\"en\">Studio</guimenu> " +"<guimenuitem>Manage Metronome</guimenuitem> </menuchoice> to bring up the " +"metronome dialog. Here you can select a MIDI instrument for the metronome " +"and choose the metronome's resolution (whether it should tick once per beat, " +"once per subdivision of a beat, or only once per bar), pitch, and " +"velocities. Properties such as the actual voice the MIDI synth uses for the " +"metronome tick depend on the instrument selected, just as the voice used for " +"a MIDI track depends on the instrument that track is assigned to. You can " +"configure the instrument by assigning a track to it on the main window and " +"selecting the correct program from the instrument parameter box." +msgstr "" +"För att ställa in metronomerna, använd <menuchoice><guimenu " +"lang=\"sv\">Komposition</guimenu> <guimenu lang=\"sv\">Studio</guimenu> " +"<guimenuitem>Hantera metronom</guimenuitem></menuchoice> för att visa " +"metronomdialogrutan. Här kan du välja ett MIDI-instrument för metronomen " +"och välja metronomens upplösning (om den ska ticka en gång per taktslag, " +"en gång per underavdelning av ett taktslag, eller bara en gång per takt), " +"tonhöjd och ljudstyrkor. Egenskaper som själva stämman som MIDI-synten " +"använder för metronomens tick beror på instrumentet som väljes, precis " +"som stämman för ett MIDI-spår beror på instrumentet som spåret är " +"tilldelat till. Du kan ställa in instrumentet genom att tilldela ett spår " +"till det i huvudfönstret och välja rätt program från " +"instrumentparameterrutan." + +#. Tag: para +#: index.docbook:1678 +#, no-c-format +msgid "" +"The record and play metronomes can be switched on or off from the Transport " +"window, using the metronome button. This button controls the record " +"metronome when recording is armed or in progress, and the play metronome at " +"other times. By default, the record metronome is switched on and the play " +"metronome switched off." +msgstr "" +"Metronomerna för inspelning och uppspelning kan aktiveras eller inaktiveras " +"från överföringsfönstret genom att använda metronomknappen. Knappen " +"styr inspelningsmetronomen när inspelning är förberedd eller pågår, och " +"annars uppspelningsmetronomen. Normalt är inspelningsmetronomen aktiverad " +"och uppspelningsmetronomen inaktiverad." + +#. Tag: para +#: index.docbook:1687 +#, no-c-format +msgid "" +"Rosegarden also has a \"visual metronome\": the transport window can be told " +"to flash brightly to mark each beat. See <link linkend=\"transport\">the " +"Transport section</link> for more details." +msgstr "" +"Rosegarden har också en \"visuell metronom\": Överföringsfönstret kan " +"ställas in att blinka starkt för att markera varje taktslag. Se avsnittet " +"om <link linkend=\"transport\">överföringen</link> för mer " +"detaljinformation." + +#. Tag: title +#: index.docbook:1695 +#, no-c-format +msgid "MIDI filters" +msgstr "MIDI-filter" + +#. Tag: phrase +#: index.docbook:1703 +#, no-c-format +msgid "The MIDI filter dialog" +msgstr "MIDI-filterdialogrutan" + +#. Tag: para +#: index.docbook:1709 +#, no-c-format +msgid "" +"Using this dialog you can decide which MIDI events Rosegarden will ignore or " +"accept, either when forwarding events using MIDI THRU or when simply " +"recording them. Use the check boxes on this dialog to tell Rosegarden which " +"types of MIDI events you don't want to forward or record." +msgstr "" +"Genom att använda den här dialogrutan kan du bestämma vilka " +"MIDI-händelser som Rosegarden ignorerar eller accepterar, antingen när " +"händelser skickas vidare med MIDI THRU, eller helt enkelt när de spelas " +"in. Använd kryssrutorna för att tala om för Rosegarden vilka typer av " +"MIDI-händelser som du inte vill skicka vidare eller spela in." + +#. Tag: title +#: index.docbook:1721 +#, no-c-format +msgid "External MIDI controllers" +msgstr "Externa MIDI-styrenheter" + +#. Tag: para +#: index.docbook:1722 +#, no-c-format +msgid "" +"Rosegarden's audio and MIDI mixer windows and main canvas can also be " +"controlled to some degree by an external MIDI device. To set this up, you " +"will need to use an ALSA MIDI connection manager such as qjackctl to connect " +"your MIDI controller device to Rosegarden's \"external controller\" input " +"and output MIDI ports." +msgstr "" +"Rosegardens ljud- och MIDI-mixningsfönster samt huvudfönstret kan " +"också i viss mån styras av en extern MIDI-enhet. För att ställa in det, " +"måste du använda ett ALSA MIDI-anslutningsprogram som qjackctl " +"för att ansluta MIDI-styrenheten till Rosegardens \"externa styringång\" " +"och MIDI-utgångarna." + +#. Tag: para +#: index.docbook:1730 +#, no-c-format +msgid "" +"Rosegarden accepts MIDI control change messages to adjust the mixer track " +"corresponding to the incoming MIDI channel on each controller event, and " +"also sends out MIDI messages when something is changed in a mixer track in " +"order to support controllers with powered faders or knobs." +msgstr "" +"Rosegarden tar emot MIDI-styrändringsmeddelanden för att justera mixerspåret " +"som motsvarar den inkommande MIDI-kanalen vid varje styrenhetshändelse, " +"och skickar också ut MIDI-meddelanden när något ändras i ett mixerspår " +"för att stödja styrenheter med motoriserade skjutreglage eller knappar." + +#. Tag: para +#: index.docbook:1737 +#, no-c-format +msgid "" +"Rosegarden accepts MIDI controller number 81 to change the currently active " +"window. Send controller 81 with data value 0-9 to select the main window, " +"10-19 to select the audio mixer window or 20-29 to select the MIDI mixer " +"window." +msgstr "" +"Rosegarden tar emot MIDI-styrenhet nummer 81 för att ändra fönstret som " +"för närvarande är aktivt. Skicka styrenhet 81 med datavärdet 0-9 för att " +"välja huvudfönstret, 10-19 för att välja ljudmixerfönstret eller 20-29 för " +"att välja MIDI-mixerfönstret." + +#. Tag: para +#: index.docbook:1741 +#, no-c-format +msgid "" +"Rosegarden accepts MIDI controller number 82 to change the currently " +"selected track in the main window. The stepping of this controller depends " +"on the number of tracks in the window -- the ratio of controller data value " +"to track number will be calculated so as to use the full MIDI controller " +"data range, provided there are no more than 128 tracks in the window." +msgstr "" +"Rosegarden tar emot MIDI-styrenhet nummer 82 för att ändra spår som " +"för närvarande är markerat i huvudfönstret. Stegningen av styrenheten " +"beror på antal spår i fönstret: förhållandet mellan styrenhetens " +"datavärde till spårnummer beräknas så att det fullständiga dataintervallet " +"i MIDI-styrenheten används, under förutsättning att det inte finns mer " +"än 128 spår i fönstret." + +#. Tag: title +#: index.docbook:1753 +#, no-c-format +msgid "Segment and Instrument Parameters" +msgstr "Segment- och instrumentparametrar" + +#. Tag: title +#: index.docbook:1756 +#, no-c-format +msgid "The Segment Parameter Box" +msgstr "Segmentparameterrutan" + +#. Tag: phrase +#: index.docbook:1765 +#, no-c-format +msgid "&rosegarden;'s segment parameter box" +msgstr "&rosegarden;s segmentparameterruta" + +#. Tag: para +#: index.docbook:1771 +#, no-c-format +msgid "" +"The segment parameter box lives at the left side of the Rosegarden main " +"window. (If you can't see it, try using <menuchoice> <guimenu " +"lang=\"en\">Settings</guimenu> <guimenuitem>Show Segment and Instrument " +"Parameters</guimenuitem> </menuchoice>.) It allows you to modify some " +"aspects of the selected segments." +msgstr "" +"Segmentparameterrutan hör hemma till vänster i Rosegardens huvudfönster. " +"(Om du inte kan se den, försök använda <menuchoice><guimenu " +"lang=\"sv\">Inställningar</guimenu> <guimenuitem>Visa segment- och " +"instrumentparametrar</guimenuitem></menuchoice>.) Den låter dig ändra " +"vissa aspekter av markerade segment." + +#. Tag: para +#: index.docbook:1777 +#, no-c-format +msgid "" +"If a single segment is currently selected, its parameters will be shown in " +"the segment parameter box and can be edited there. If several segments are " +"selected, the parameter box will only show the current values where they are " +"the same for all of the selected segments -- but you can still edit them, " +"and your changes will apply to the whole selection." +msgstr "" +"Om ett enstaka segment för närvarande är markerat, visas dess parametrar " +"i segmentparameterrutan och kan redigeras där. Om flera segment är " +"markerade, visar parameterrutan bara nuvarande värden där de är samma " +"för alla markerade segment, men du kan fortfarande redigera dem och " +"ändringarna gäller för allt som är markerat." + +#. Tag: term +#: index.docbook:1786 +#, no-c-format +msgid "Label" +msgstr "Namn" + +#. Tag: para +#: index.docbook:1788 +#, no-c-format +msgid "" +"Shows the label of the selected segment (or segments, if they all have the " +"same label). Click the \"...\" button to edit the label." +msgstr "" +"Visar namnet på det markerade segmentet (eller segmenten, om alla har " +"samma namn). Klicka på knappen \"...\" för att redigera namnet." + +#. Tag: term +#: index.docbook:1795 +#, no-c-format +msgid "Repeat" +msgstr "Upprepa" + +#. Tag: para +#: index.docbook:1797 +#, no-c-format +msgid "" +"Switches repeat on or off for the selected segments. A repeating segment " +"will repeat until the start of the following segment on the same track, or " +"until the end of the composition if there is no following segment." +msgstr "" +"Stänger av eller sätter på upprepning för markerade segment. Ett " +"upprepande segment upprepas till efterföljande segment börjar i samma " +"spår, eller till kompositionens slut om det inte finns något " +"efterföljande segment." + +#. Tag: para +#: index.docbook:1802 +#, no-c-format +msgid "" +"The repeated parts of a repeating segment are shown on the main canvas in a " +"fainter colour than the original segment. You can turn them into real " +"editable copies of the original segment either by using <menuchoice> " +"<guimenu lang=\"en\">Segments</guimenu> <guimenuitem>Turn Repeats into " +"Copies</guimenuitem> </menuchoice>, or simply by double-clicking on the " +"individual repeating blocks." +msgstr "" +"Upprepade delar av ett upprepande segment visas med en svagare färg på " +"huvudduken än det ursprungliga segmentet. Du kan ändra dem till riktiga " +"redigerbara kopior av det ursprungliga segmentet genom att antingen använda " +"<menuchoice><guimenu lang=\"sv\">Segment</guimenu> <guimenuitem>Omvandla " +"upprepningar till kopior</guimenuitem></menuchoice>, eller genom att helt " +"enkelt dubbelklicka på enskilda upprepade block." + +#. Tag: term +#: index.docbook:1815 +#, no-c-format +msgid "Quantize" +msgstr "Kvantisera" + +#. Tag: para +#: index.docbook:1817 +#, no-c-format +msgid "" +"Shows the quantization setting for the selected segments. You can change " +"this to quickly quantize the start times of all their notes. For more " +"advanced quantization, use <menuchoice> <guimenu " +"lang=\"en\">Segments</guimenu> <guimenuitem>Quantize...</guimenuitem> " +"</menuchoice>. See <link linkend=\"quantization\">Quantization</link> for " +"more details." +msgstr "" +"Visar kvantiseringsinställningen för markerade segment. Du kan ändra den " +"för att snabbt kvantisera starttider för alla deras toner. För mer " +"avancerad kvantisering, använd <menuchoice> <guimenu " +"lang=\"sv\">Segment</guimenu> <guimenuitem>Kvantisera...</guimenuitem> " +"</menuchoice>. Se <link linkend=\"quantization\">Kvantisering</link> för " +"mer detaljinformation." + +#. Tag: term +#: index.docbook:1832 +#, no-c-format +msgid "Transpose" +msgstr "Transponera" + +#. Tag: para +#: index.docbook:1834 +#, no-c-format +msgid "" +"Shows the transposition (in semitones) currently applied to the selected " +"segments. This transposition is applied when the segment is played, and is " +"not shown in the notes displayed in the matrix, notation or event list " +"editors. You can use this to quickly change the pitch of part or all of a " +"composition." +msgstr "" +"Visar transponeringen (i halvtonssteg) som för närvarande används för det " +"markerade segmentet. Transponeringen utförs när segmentet spelas upp, och " +"visas inte med noterna i matris-, not- eller händelseeditorerna. Du " +"kan använda den för att snabbt ändra tonhöjd för en del eller hela " +"kompositionen." + +#. Tag: term +#: index.docbook:1843 +#, no-c-format +msgid "Delay" +msgstr "Fördröjning" + +#. Tag: para +#: index.docbook:1845 +#, no-c-format +msgid "" +"Shows the delay currently in effect on the selected segments. You can set a " +"delay here in order to cause an entire segment to play later than written. " +"This delay is applied when the segment is played, and is not shown in the " +"notes displayed in the matrix, notation or event list editors." +msgstr "" +"Visar fördröjningen som för närvarande gäller för markerade segment. " +"Du kan ställa in en fördröjning här för att göra att ett helt segment " +"spelas upp senare än skrivet. Fördröjningen utförs när segmentet spelas " +"upp, och visas inte med noterna i matris-, not- eller " +"händelseeditorerna." + +#. Tag: para +#: index.docbook:1851 +#, no-c-format +msgid "" +"You can set a delay either in musical time (by choosing a note duration from " +"the delay dropdown), in which time the exact delay will depend on the tempo, " +"or in real time (by choosing a time in milliseconds from the dropdown)." +msgstr "" +"Du kan antingen ange en fördröjning med metronomtid (genom att välja " +"notvärde i fördröjningskombinationsrutan), då fördröjningens exakta " +"tid beror på tempot, eller med klocktid (genom att välja tiden i " +"millisekunder i kombinationsrutan)." + +#. Tag: term +#: index.docbook:1862 +#, no-c-format +msgid "Colour" +msgstr "Färg" + +#. Tag: para +#: index.docbook:1864 +#, no-c-format +msgid "" +"Shows the colour being used for the display of the selected segments. You " +"can choose another colour from the dropdown, or choose the \"Add New " +"Colour\" option if you want a colour not in the dropdown." +msgstr "" +"Visar färgen som används för att visa markerade segment. Du kan välja en " +"annan färg i kombinationsrutan, eller välja alternativet \"Lägg till ny " +"färg\" om du vill ha en färg som inte finns i kombinationsrutan." + +#. Tag: para +#: index.docbook:1869 +#, no-c-format +msgid "" +"You can also manage and rename colours using <menuchoice> <guimenu " +"lang=\"en\">Composition</guimenu> <guimenuitem>Edit Document " +"Properties...</guimenuitem> </menuchoice> (then choose the Colour page on " +"the document properties dialog). The modified colour palette will be saved " +"with the composition in the Rosegarden file." +msgstr "" +"Du kan också hantera och byta namn på färger genom att använda " +"<menuchoice><guimenu lang=\"sv\">Komposition</guimenu> <guimenuitem>Redigera " +"dokumentegenskaper...</guimenuitem></menuchoice> (och därefter välja sidan " +"Färg i dialogrutan med dokumentegenskaper). Den ändrade färgpaletten " +"sparas med kompositionen i Rosegarden-filen." + +#. Tag: phrase +#: index.docbook:1884 +#, no-c-format +msgid "&rosegarden;'s colour manager" +msgstr "&rosegarden;s färghantering" + +#. Tag: title +#: index.docbook:1897 +#, no-c-format +msgid "The Instrument Parameter Box" +msgstr "Instrumentparameterrutan" + +#. Tag: para +#: index.docbook:1898 +#, no-c-format +msgid "" +"The instrument parameter box can be found at the lower left of the " +"Rosegarden main window, below the <link " +"linkend=\"segment-view-segmentparameterbox\">Segment Parameter Box</link>. " +"(If you can't see it, try using <menuchoice> <guimenu " +"lang=\"en\">Settings</guimenu> <guimenuitem>Show Segment and Instrument " +"Parameters</guimenuitem> </menuchoice>.)" +msgstr "" +"Instrumentparameterrutan finns i nedre vänstra hörnet av Rosegardens " +"huvudfönster, nedanför <link " +"linkend=\"segment-view-segmentparameterbox\">segmentparameterrutan</link>. " +"(Om du inte kan se den, försök använda <menuchoice><guimenu " +"lang=\"sv\">Inställningar</guimenu> <guimenuitem>Visa segment- och " +"instrumentparametrar</guimenuitem></menuchoice>.)" + +#. Tag: para +#: index.docbook:1907 +#, no-c-format +msgid "" +"It shows you which instrument is assigned to the current selected track, and " +"contains all of the editable controls for that instrument. Remember that " +"because any number of tracks can be assigned to the same instrument, the " +"settings in this box may affect more than one track at a time." +msgstr "" +"Den visar vilka instrument som tilldelats nuvarande markerat spår, och " +"innehåller alla redigerbara knapparna för instrumentet. Kom ihåg att " +"eftersom hur många spår som helst kan tilldelas till samma instrument, kan " +"inställningarna i rutan påverka mer än ett spår åt gången." + +#. Tag: para +#: index.docbook:1914 +#, no-c-format +msgid "" +"The layout and contents of the instrument parameter box depend on the type " +"of instrument: MIDI, audio, or synth plugin." +msgstr "" +"Utseendet och innehållet i instrumentparameterrutan beror på " +"instrumenttypen: MIDI, ljud eller syntinsticksmodul." + +#. Tag: title +#: index.docbook:1920 +#, no-c-format +msgid "MIDI Instrument Parameters" +msgstr "MIDI-instrumentparametrar" + +#. Tag: phrase +#: index.docbook:1928 +#, no-c-format +msgid "&rosegarden;'s instrument parameter box for a MIDI instrument" +msgstr "&rosegarden;s instrumentparameterruta för ett MIDI-instrument" + +#. Tag: para +#: index.docbook:1933 +#, no-c-format +msgid "" +"When you select a track assigned to a MIDI instrument, the instrument " +"parameter box shows MIDI parameters." +msgstr "" +"När du markerar ett spår som är tilldelat till ett MIDI-instrument, visar " +"instrumentparameterrutan MIDI-parametrar." + +#. Tag: para +#: index.docbook:1936 +#, no-c-format +msgid "" +"At the top, this box shows the name of the instrument and the connection " +"that its device is using." +msgstr "" +"Längst upp visar rutan instrumentets namn och anslutningen som dess enhet " +"använder." + +#. Tag: para +#: index.docbook:1940 +#, no-c-format +msgid "" +"Below that, you can see and edit the MIDI channel number and the <link " +"linkend=\"studio-bank-editor\">bank and program</link> settings that should " +"be sent to the instrument at the start of playback (including a " +"\"percussion\" toggle that controls whether only percussion programs should " +"be offered in these settings)." +msgstr "" +"Därunder kan du se och redigera MIDI-kanalnumret och inställningar av " +"<link linkend=\"studio-bank-editor\">bank och program</link> som ska skickas " +"till instrumentet vid uppspelningens start (inklusive kryssrutan " +"\"Slagverk\" som styr om bara slagverksprogram ska erbjudas i " +"inställningarna)." + +#. Tag: para +#: index.docbook:1947 +#, no-c-format +msgid "" +"Finally this box shows you the controllers available for this device (those " +"for a General MIDI device are shown above). Any settings you make here will " +"be sent to this instrument's channel at the start of playback." +msgstr "" +"Till sist visar rutan tillgängliga styrenheter för enheten (de för en " +"generell MIDI-enhet visas ovan). Alla inställningar som du gör här " +"skickas till instrumentets kanal vid uppspelningens start." + +#. Tag: title +#: index.docbook:1955 +#, no-c-format +msgid "Audio Instrument Parameters" +msgstr "Ljudinstrumentparametrar" + +#. Tag: phrase +#: index.docbook:1963 +#, no-c-format +msgid "&rosegarden;'s instrument parameter box for an audio instrument" +msgstr "&rosegarden;s instrumentparameterruta för ett ljudinstrument" + +#. Tag: para +#: index.docbook:1968 +#, no-c-format +msgid "" +"When you select an audio track, the instrument parameter box shows audio " +"parameters." +msgstr "" +"När du markerar ett ljudspår, visar instrumentparameterrutan " +"ljudparametrar." + +#. Tag: para +#: index.docbook:1972 +#, no-c-format +msgid "" +"The box has two main faders, one with a blue surround for playback level and " +"the other with a red surround for the record level when recording to this " +"instrument. Between them is a playback level meter." +msgstr "" +"Rutan har två huvudtoningar, en omgiven av blått för uppspelning och den " +"andra omgiven av rött för inspelningsnivå vid inspelning till " +"instrumentet. Mellan dem finns en mätare av uppspelningsnivå." + +#. Tag: para +#: index.docbook:1978 +#, no-c-format +msgid "" +"The two menus at the top of the box are used to select the input and output " +"audio routing for this instrument. Below them you can select whether the " +"instrument is mono or stereo, and the pan setting for position in the stereo " +"field. (Audio instruments are always ultimately stereo, because the pan " +"setting is always applied. But if you set the instrument to mono, it will " +"reduce any audio data and effect outputs to mono before applying pan.)" +msgstr "" +"De två menyerna längst upp i rutan används för att välja ingångs- och " +"utgångsfördelning för instrumentet. Under dem kan du välja om " +"instrumentet är mono eller stereo, och panoreringsinställning för plats i " +"stereofältet. (Ljudinstrument är alltid till sist stereo, eftersom " +"panoreringsinställningen alltid tillämpas. Men om du ställer in " +"instrumentet till mono, reduceras all ljuddata och effektutdata till mono " +"innan panoreringen tillämpas.)" + +#. Tag: para +#: index.docbook:1987 +#, no-c-format +msgid "" +"The column of five buttons at lower left are the effects slots. Click on " +"them to select and activate plugin effects for this audio instrument, and to " +"control them using the plugin editor dialog. These are insert effects, " +"applied in order from top to bottom before the fader and pan." +msgstr "" +"Kolumnen med fem knappar längst ner till vänster är effektplatserna. " +"Klicka på dem för att välja och aktivera insticksmoduler för " +"ljudinstrumentet, och för att styra dem med redigeringsdialogrutan för " +"insticksmoduler. Detta är infogade effekter, som utförs i ordning " +"uppifrån och ner innan toning och panorering." + +#. Tag: title +#: index.docbook:1996 +#, no-c-format +msgid "Synth Plugin Instrument Parameters" +msgstr "Instrumentparametrar för syntinsticksmoduler" + +#. Tag: phrase +#: index.docbook:2004 +#, no-c-format +msgid "&rosegarden;'s instrument parameter box for a synth plugin instrument" +msgstr "&rosegarden;s instrumentparameterruta för ett syntinsticksmodulinstrument" + +#. Tag: para +#: index.docbook:2009 +#, no-c-format +msgid "" +"When you select a track assigned to a synth plugin instrument, the " +"instrument parameter box shows synth parameters. You will notice that " +"although a synth plugin track uses segments with MIDI data in them, in terms " +"of control and routing it behaves more like an audio track." +msgstr "" +"När du markerar ett spår som är tilldelat till ett " +"syntinsticksmodulinstrument, visar instrumentparameterrutan syntparametrar. " +"Du märker att även om en syntinsticksmodul använder segment med " +"MIDI-data, så beter den sig mer som ett ljudspår när det gäller styrning " +"och fördelning." + +#. Tag: para +#: index.docbook:2015 +#, no-c-format +msgid "" +"The most important control here is the button at top left (saying Xsynth in " +"the above picture) which shows the name of the synth plugin in use for this " +"instrument. Click this to select a particular synth and control it in the " +"standard Rosegarden plugin editor dialog. Once you've selected a plugin, you " +"may also be able to click the Editor button below it in order to open a " +"dedicated GUI editor for the particular plugin (if the plugin has one)." +msgstr "" +"Den viktigaste knappen här är den längst upp till vänster (som lyder " +"Xsynth i bilen ovan), som visar namnet på syntinsticksmodulen som används " +"för instrumentet. Klicka på den för att välja en viss synt och styra den " +"i Rosegardens vanliga redigeringsdialog för insticksmoduler. När du väl " +"har valt en insticksmodul, kanske du också kan klicka på " +"redigeringsknappen nedanför för att öppna en dedicerad grafisk editor " +"för den särskilda insticksmodulen (om insticksmodulen har någon)." + +#. Tag: para +#: index.docbook:2024 +#, no-c-format +msgid "" +"The remaining controls here are the same as for audio instruments: the " +"playback fader, playback level, output routing, mono/stereo and pan settings " +"and effects slots are all exactly the same." +msgstr "" +"Återstående knappar här är samma som för ljudinstrument: " +"Uppspelningstoning, uppspelningsnivå, utgångsfördelning, mono/stereo, " +"panoreringsinställningar och effektplatser är alla exakt likadana." + +#. Tag: title +#: index.docbook:2034 +#, no-c-format +msgid "Quantization" +msgstr "Kvantisering" + +#. Tag: para +#: index.docbook:2035 +#, no-c-format +msgid "" +"\"Quantization\" is the process of repositioning notes and other events so " +"that they start or finish on exact beat divisions. It is traditionally used " +"to make an approximate performance into a precise but rather " +"mechanical-sounding one -- either because precision is the desired effect, " +"or for reasons such as making the notes clearer in notation." +msgstr "" +"\"Kvantisering\" är processen att flytta toner och andra händelser så att " +"de börjar eller avslutas på exakta taktdelar. Det används traditionellt " +"för att göra ett ungefärligt utförande till ett precist men som låter " +"ganska mekaniskt, antingen på grund av att precision är önskad effekt, " +"eller på grund av orsaker som att göra noter tydligare i notering." + +#. Tag: para +#: index.docbook:2044 +#, no-c-format +msgid "" +"For general quantization, use <menuchoice> <guimenu " +"lang=\"en\">Segments</guimenu> <guimenuitem>Quantize</guimenuitem> " +"</menuchoice> in the main window or <menuchoice> <guimenu " +"lang=\"en\">Adjust</guimenu> <guimenuitem>Quantize</guimenuitem> " +"</menuchoice> in matrix or notation editors. This shows you a dialog in " +"which you can select the precise quantization parameters you need, and then " +"it applies these to all of the selected segments or notes. (You can also " +"quickly reach this dialog by pressing the \"=\" key.)" +msgstr "" +"För allmän kvantisering, använd <menuchoice><guimenu " +"lang=\"sv\">Segment</guimenu> " +"<guimenuitem>Kvantisera</guimenuitem></menuchoice> i huvudfönstret eller " +"<menuchoice><guimenu lang=\"sv\">Justera</guimenu> " +"<guimenuitem>Kvantisera</guimenuitem></menuchoice> i matriseditorn eller " +"notbehandlarna. Det visar en dialogruta där du kan välja precis de " +"kvantiseringsparametrarna du behöver, och tillämpar dem på alla markerade " +"segment eller toner. (Du kan också snabbt nå dialogrutan genom att " +"trycka på tangenten \"=\".)" + +#. Tag: phrase +#: index.docbook:2069 +#, no-c-format +msgid "&rosegarden;'s quantize dialog" +msgstr "&rosegarden;s kvantiseringsdialogruta" + +#. Tag: para +#: index.docbook:2075 +#, no-c-format +msgid "" +"The quantize dialog offers a selection of quantizers, each with its own set " +"of parameters. The quantizers available are:" +msgstr "" +"Kvantiseringsdialogrutan erbjuder ett urval kvantiseringsmetoder, var och en " +"med sin egen uppsättning parametrar. Tillgängliga kvantiseringsmetoder är:" + +#. Tag: term +#: index.docbook:2082 +#, no-c-format +msgid "Grid quantizer" +msgstr "Rutnätskvantisering" + +#. Tag: para +#: index.docbook:2084 +#, no-c-format +msgid "" +"The grid quantizer moves the start times of notes so that they start at the " +"nearest point on some grid (defined by various parameters of the quantizer). " +"Thus notes that initially vary slightly in start time will be aligned by the " +"quantizer, making for a more precise and mechanical performance." +msgstr "" +"Rutnätskvantiseringen flyttar starttider för toner så att de börjar på " +"den närmaste punkten i ett rutnät (definierat av de olika parametrarna " +"för kvantiseringen). På så sätt justeras toner som ursprungligen " +"varierar något i starttid av kvantiseringen, vilket ger ett mer precist och " +"mekaniskt utförande." + +#. Tag: term +#: index.docbook:2095 +#, no-c-format +msgid "Legato quantizer" +msgstr "Legato-kvantisering" + +#. Tag: para +#: index.docbook:2097 +#, no-c-format +msgid "" +"The legato quantizer carries out a simple grid quantization, and also " +"adjusts the note durations so as to remove any gaps between notes by " +"extending each note so as to (at least) continue until the start of the " +"following one. You can also obtain this legato effect without the " +"accompanying grid quantization using the <menuchoice> <guimenu " +"lang=\"en\">Adjust</guimenu> <guimenuitem>Quantize</guimenuitem> " +"<guimenuitem>Legato</guimenuitem> </menuchoice> function in the Matrix " +"editor." +msgstr "" +"Legato-kvantiseringen utför en enkel rutnätskvantisering, och justerar " +"också notvärdena så att eventuella avstånd mellan tonerna tas bort " +"genom att förlänga varje not så att den (åtminstone) fortsätter till " +"början på nästa. Du kan också få denna legato-effekt utan tillhörande " +"rutnätskvantisering med funktionen <menuchoice><guimenu " +"lang=\"sv\">Justera</guimenu> <guimenuitem>Kvantisera</guimenuitem> " +"<guimenuitem>Legato</guimenuitem></menuchoice> i matriseditorn." + +#. Tag: term +#: index.docbook:2113 +#, no-c-format +msgid "Heuristic notation quantizer" +msgstr "Heuristisk kvantisering" + +#. Tag: para +#: index.docbook:2115 +#, no-c-format +msgid "" +"The notation quantizer attempts to adjust note start times and durations so " +"as to produce readable notation. See <link " +"linkend=\"nv-quantization\">Notation from performance data</link> for a " +"description of this quantizer and its uses." +msgstr "" +"Kvantiseringen försöker justera starttider och notvärden för " +"toner så att en läsbar notering skapas. Se <link " +"linkend=\"nv-quantization\">Notskrift från utförandedata</link> för en " +"beskrivning av kvantiseringen och dess användning." + +#. Tag: para +#: index.docbook:2125 +#, no-c-format +msgid "The grid quantizer has the following adjustable parameters:" +msgstr "Rutnätskvantiseringen har följande justerbara parametrar:" + +#. Tag: term +#: index.docbook:2129 index.docbook:3711 +#, no-c-format +msgid "Base grid unit" +msgstr "Grundenhet för rutnät" + +#. Tag: para +#: index.docbook:2131 +#, no-c-format +msgid "This is the size of the grid used for quantization." +msgstr "Det här är storleken på rutnätet som används för kvantiseringen." + +#. Tag: term +#: index.docbook:2137 +#, no-c-format +msgid "Swing" +msgstr "Svaj" + +#. Tag: para +#: index.docbook:2139 +#, no-c-format +msgid "" +"This is a percentage figure which adjusts the degree by which alternate " +"beats are quantized \"late\"." +msgstr "" +"Det här är ett procenttal som justerar graden som alternerande taktslag " +"kvantiseras \"sent\"." + +#. Tag: para +#: index.docbook:2141 +#, no-c-format +msgid "" +"If set to None (the default), quantization will be to an even grid spaced " +"according to the base grid unit." +msgstr "" +"Om inställt till inget (förvalt värde), görs kvantiseringen till ett " +"jämt rutnät med avstånd enligt grundenheten för rutnätet." + +#. Tag: para +#: index.docbook:2144 +#, no-c-format +msgid "" +"If set to 100%, every second grid line will be placed two-thirds of the " +"distance between the previous and next ones, instead of only half. This will " +"result in notes being quantized to the first and third triplets of a swing " +"beat." +msgstr "" +"Om inställd till 100 %, placeras varannan rutnätslinje två tredjedelar av " +"avståndet mellan föregående och nästa, istället för halvvägs. Det " +"gör att toner kvantiseras till första och tredje triolen med en svajig " +"takt." + +#. Tag: para +#: index.docbook:2150 +#, no-c-format +msgid "" +"Other settings will produce proportionately varying degrees of swinginess. " +"You can also set this parameter to negative figures (for alternate beats to " +"start early) or to figures greater than 100%." +msgstr "" +"Övriga inställningar ger proportionellt varierande grad av svaj. Du kan " +"också ställa in parametern till negativa värden (för att omväxlande " +"taktslag ska börja tidigare) eller till värden större än 100 %." + +#. Tag: term +#: index.docbook:2158 +#, no-c-format +msgid "Iterative amount" +msgstr "Itereringsvärde" + +#. Tag: para +#: index.docbook:2160 +#, no-c-format +msgid "" +"The default behaviour of the grid quantizer is to move each note exactly " +"onto its nearest grid line. But if you set the iterative amount to something " +"less than 100% (the \"Full quantize\" default), each note will only be moved " +"that percentage of the distance toward its nearest grid line, resulting in a " +"nearly-but-not-quite quantized effect." +msgstr "" +"Rutnätskvantiseringens normalbeteende är att exakt flytta varje not till " +"den närmaste rutnätslinjen, men om du ställer in iterationsgränsen till " +"något som är mindre än 100 % (normalvärdet \"Fullständig " +"kvantisering\") flyttas varje not bara den procentandelen av avståndet till " +"närmaste rutnätslinje, vilket resulterar i en kvantiseringseffekt som " +"nästan utförs, men inte helt och hållet." + +#. Tag: para +#: index.docbook:2166 +#, no-c-format +msgid "" +"This quantizer may be applied repeatedly so as to try out gradually " +"increasing degrees of quantization, hence the name \"iterative\". Use " +"<menuchoice> <guimenu lang=\"en\">Adjust</guimenu> " +"<guimenuitem>Quantize</guimenuitem> <guimenuitem>Repeat Last " +"Quantize</guimenuitem> </menuchoice> in the Matrix editor to do so." +msgstr "" +"Kvantiseringen kan utföras upprepade gånger, för att pröva gradvis " +"ökande kvantiseringsgrader, därav namnet \"iterativ\". Använd " +"<menuchoice><guimenu lang=\"sv\">Justera</guimenu> " +"<guimenuitem>Kvantisera</guimenuitem> <guimenuitem>Upprepa senaste " +"kvantisering</guimenuitem></menuchoice> i matriseditorn för att göra det." + +#. Tag: term +#: index.docbook:2179 +#, no-c-format +msgid "Quantize durations as well as start times" +msgstr "Kvantisera både notvärden och starttider" + +#. Tag: para +#: index.docbook:2181 +#, no-c-format +msgid "" +"If this option is enabled, the quantizer will quantize the notes' end times " +"to the same grid as their start times." +msgstr "" +"Om det här alternativet är aktiverat, kvantiseras tonernas sluttider till " +"samma rutnät som deras starttider." + +#. Tag: para +#: index.docbook:2188 +#, no-c-format +msgid "" +"The quantize dialog also has an optional Advanced section containing further " +"options for <link linkend=\"nv-quantization\">notation quantization</link>." +msgstr "" +"Kvantiseringsdialogrutan har också en valfri avancerad sektion som " +"innehåller ytterligare alternativ för <link " +"linkend=\"nv-quantization\">kvantisering</link>." + +#. Tag: para +#: index.docbook:2193 +#, no-c-format +msgid "" +"Another simple way to apply a grid quantizer is to do it in the main window, " +"using the <guimenuitem>Quantize</guimenuitem> menu on the <link " +"linkend=\"segment-view-segmentparameterbox\">Segment Parameter Box</link>. " +"If you select some segments and change the value shown in the menu, the " +"segments will immediately be grid-quantized to the resolution shown in the " +"menu." +msgstr "" +"Ett annat enkelt sätt att utföra en rutnätskvantisering är att göra den " +"i huvudfönstret med menyn <guimenuitem>Kvantisera</guimenuitem> i <link " +"linkend=\"segment-view-segmentparameterbox\">segmentparameterrutan</link>. " +"Om du markerar några segment och ändrar värdet som visas i menyn, blir " +"segmenten omedelbart rutnätskvantiserade till upplösningen som visas i " +"menyn." + +#. Tag: para +#: index.docbook:2202 +#, no-c-format +msgid "" +"Finally, there is also a <link linkend=\"matrix-grid-quantize\">quantize " +"control</link> in the matrix view." +msgstr "" +"Till sist finns också en <link linkend=\"matrix-grid-quantize\">styrning av " +"kvantisering</link> i matrisvyn." + +#. Tag: title +#: index.docbook:2210 +#, no-c-format +msgid "The Matrix editor" +msgstr "Matriseditorn" + +#. Tag: para +#: index.docbook:2211 +#, no-c-format +msgid "" +"The &rosegarden; matrix editor enables you to view and edit music in a " +"simple, logical format: each note represented as a block in a grid, at a " +"height corresponding to the pitch." +msgstr "" +"&rosegarden;s matriseditor låter dig visa och redigera musik med ett enkelt " +"logiskt format: Varje not representeras som ett block i ett rutnät, på en " +"plats som motsvarar tonhöjden." + +#. Tag: phrase +#: index.docbook:2223 +#, no-c-format +msgid "&rosegarden;'s matrix editor" +msgstr "&rosegarden;s matriseditor" + +#. Tag: para +#: index.docbook:2225 +#, no-c-format +msgid "" +"Each matrix editor window shows a single segment. To edit a segment, just " +"right-click on it in the main canvas and select the matrix editor from the " +"menu. Alternatively, you can configure Rosegarden to make the matrix editor " +"the default editor available when you double-click on a segment." +msgstr "" +"Varje fönster i matriseditorn visar ett enstaka segment. För att redigera " +"ett segment, högerklicka bara på det på huvudduken och välj " +"matriseditorn i menyn. Alternativt kan du ställa in Rosegarden att göra " +"matriseditorn till standardvy som är tillgänglig genom att " +"dubbelklicka på ett segment." + +#. Tag: title +#: index.docbook:2235 +#, no-c-format +msgid "The Grid and Quantize controls" +msgstr "Styrning av rutnät och kvantisering" + +#. Tag: para +#: index.docbook:2236 +#, no-c-format +msgid "The matrix view contains Grid and Quantize menus in its main toolbar." +msgstr "Matrisvyn innehåller menyerna Rutnät och Kvantisering i huvudmenyraden." + +#. Tag: para +#: index.docbook:2240 +#, no-c-format +msgid "" +"The Grid menu controls the size of the visible grid in the background of the " +"matrix view, as well as the time resolution used when entering and moving " +"notes. After you set it to a particular time value, the normal note " +"insertion and drag operations will then snap automatically to grid points " +"spaced at that time width. You can override the snap-to-grid effect " +"temporarily by holding down Shift during editing, or you can disable it by " +"setting the Grid menu to None." +msgstr "" +"Rutnätsmenyn styr det synliga rutnätets storlek i matrisvyns bakgrund, " +"samt tidsupplösningen som används när noter skrivs in och flyttas. Efter " +"du har ställt in det till ett visst tidsvärde, låses de normala " +"åtgärderna för att infoga och dra noter automatiskt till rutnätspunkter " +"åtskilda med det tidsvärdets bredd. Du kan överskrida " +"positioneringsfunktionen tillfälligt genom att hålla nere Skift under " +"redigeringen, eller inaktivera den genom att ställa in rutnätsmenyn till " +"Ingen låsning." + +#. Tag: para +#: index.docbook:2249 +#, no-c-format +msgid "" +"The Quantize menu works rather differently. Rather than controlling the " +"behaviour of other editing tools, it actually performs an action. When you " +"change the value in this menu, the selected notes -- or the whole segment if " +"nothing is selected -- will immediately be quantized using a grid quantizer " +"of the chosen resolution." +msgstr "" +"Kvantiseringsmenyn fungerar på ett ganska annorlunda sätt. I stället för " +"att styra beteendet hos andra redigeringsverktyg, utför den verkligen en " +"åtgärd. När du ändrar värde i menyn, blir de markerade noterna, eller " +"hela segmentet om ingenting är markerat, omedelbart kvantiserade av en " +"rutnätskvantisering med vald upplösning." + +#. Tag: para +#: index.docbook:2256 +#, no-c-format +msgid "" +"The Quantize menu also shows you continuously what resolution the current " +"segment or selection is quantized to. For example, if you select a set of " +"notes that start on consecutive quarter-note beats, the Quantize menu will " +"update itself to show 1/4, as this is the coarsest resolution consistent " +"with the existing quantization of the current selection." +msgstr "" +"Kvantiseringsmenyn visar också kontinuerligt vilken upplösning som det " +"nuvarande segmentet eller markeringen är kvantiserad med. Om du till " +"exempel markerar en uppsättning noter som börjar på efterföljande " +"kvartsnotstaktslag, uppdateras kvantiseringsmenyn så att 1/4 visas, " +"eftersom det är den grövsta upplösningen som motsvarar den befintliga " +"kvantiseringen av nuvarande markering." + +#. Tag: title +#: index.docbook:2267 +#, no-c-format +msgid "Inserting notes" +msgstr "Infoga noter" + +#. Tag: para +#: index.docbook:2268 +#, no-c-format +msgid "" +"The simplest way to enter a note in the matrix view is to use the mouse. To " +"do this, select the pencil tool on the toolbar, and then click and drag on " +"the matrix editor. The note will be entered at the time and pitch " +"corresponding to the point you click at, and will have a duration " +"corresponding to the distance you drag before releasing the mouse button." +msgstr "" +"Det enklaste sättet att mata in en not i matrisvyn är att använda musen. " +"För att göra det, välj pennverktyget i verktygsraden, klicka och dra " +"därefter i matriseditorn. Noten matas in vid tiden och med tonhöjden som " +"motsvarar punkten du klickar, och har ett notvärde som motsvarar avståndet " +"du drar innan du släpper musknappen." + +#. Tag: para +#: index.docbook:2277 +#, no-c-format +msgid "" +"By default, the time and duration are snapped to a particular grid unit, " +"according to the Grid setting on the View menu or the toolbar. You can " +"prevent this effect by holding down Shift while clicking and dragging." +msgstr "" +"Normalt är tiden och notvärdet låsta till en viss rutnätsenhet enligt " +"rutnätsinställningarna i menyn Visa eller verktygsraden. Du kan förhindra " +"effekten genom att hålla nere Skift medan du klickar och drar." + +#. Tag: title +#: index.docbook:2284 +#, no-c-format +msgid "Typing notes with the PC keyboard" +msgstr "Skriva in noter med datorns tangentbord" + +#. Tag: title +#: index.docbook:2287 index.docbook:2822 +#, no-c-format +msgid "Duration" +msgstr "Notvärde" + +#. Tag: para +#: index.docbook:2289 +#, no-c-format +msgid "" +"The durations of notes entered from the keyboard are controlled by the Grid " +"setting on the View menu or toolbar. You can set this using the number keys:" +msgstr "" +"Notvärden för noter som matas in via tangentbordet styrs av " +"rutnätsinställningarna i menyn Visa eller verktygsraden . Du kan ställa " +"in det genom att använda de numeriska tangenterna:" + +#. Tag: para +#: index.docbook:2294 +#, no-c-format +msgid "<keycap>5</keycap> – Whole bar" +msgstr "<keycap>5</keycap> – Hel takt" + +#. Tag: para +#: index.docbook:2295 +#, no-c-format +msgid "<keycap>1</keycap> – Beat" +msgstr "<keycap>1</keycap> – Takt" + +#. Tag: para +#: index.docbook:2296 index.docbook:2831 +#, no-c-format +msgid "<keycap>2</keycap> – Half note (minim)" +msgstr "<keycap>2</keycap> – Halvnot" + +#. Tag: para +#: index.docbook:2297 index.docbook:2832 +#, no-c-format +msgid "<keycap>4</keycap> – Quarter note (crotchet)" +msgstr "<keycap>4</keycap> – Kvartsnot" + +#. Tag: para +#: index.docbook:2298 index.docbook:2833 +#, no-c-format +msgid "<keycap>8</keycap> – Eighth note (quaver)" +msgstr "<keycap>8</keycap> – Åttondedelsnot" + +#. Tag: para +#: index.docbook:2299 index.docbook:2834 +#, no-c-format +msgid "<keycap>6</keycap> – Sixteenth note (semiquaver)" +msgstr "<keycap>6</keycap> – Sextondedelsnot" + +#. Tag: para +#: index.docbook:2300 index.docbook:2835 +#, no-c-format +msgid "<keycap>3</keycap> – Thirty-second note (demisemiquaver)" +msgstr "<keycap>3</keycap> – Trettioandredelsnot" + +#. Tag: para +#: index.docbook:2301 index.docbook:2836 +#, no-c-format +msgid "<keycap>0</keycap> – Sixty-fourth note (hemidemisemiquaver)" +msgstr "<keycap>0</keycap> – Sextifjärdedelsnot" + +#. Tag: title +#: index.docbook:2307 index.docbook:2847 +#, no-c-format +msgid "Pitch" +msgstr "Tonhöjd" + +#. Tag: para +#: index.docbook:2309 +#, no-c-format +msgid "" +"Once the correct duration is selected in the Grid menu, you can insert a " +"note at the current position of the <link linkend=\"nv-rulers\">insert " +"cursor</link> by pressing one of the pitch keys:" +msgstr "" +"Så fort rätt notvärde är vald i rutnätsmenyn kan du infoga en not på " +"<link linkend=\"nv-rulers\">infogningsmarkörens</link> aktuella position " +"genom att trycka på en av tonhöjdstangenterna:" + +#. Tag: para +#: index.docbook:2315 index.docbook:2855 +#, no-c-format +msgid "" +"<keycap>A</keycap> – Do (the tonic of the current key in the current " +"clef)" +msgstr "<keycap>A</keycap> – C (Do, tonikan i aktuell tonart för aktuell klav)" + +#. Tag: para +#: index.docbook:2316 index.docbook:2856 +#, no-c-format +msgid "<keycap>S</keycap> – Re" +msgstr "<keycap>S</keycap> – D (Re)" + +#. Tag: para +#: index.docbook:2317 index.docbook:2857 +#, no-c-format +msgid "<keycap>D</keycap> – Mi" +msgstr "<keycap>D</keycap> – E (Mi)" + +#. Tag: para +#: index.docbook:2318 index.docbook:2858 +#, no-c-format +msgid "<keycap>F</keycap> – Fa" +msgstr "<keycap>F</keycap> – F (Fa)" + +#. Tag: para +#: index.docbook:2319 index.docbook:2859 +#, no-c-format +msgid "<keycap>J</keycap> – So" +msgstr "<keycap>J</keycap> – G (So)" + +#. Tag: para +#: index.docbook:2320 index.docbook:2860 +#, no-c-format +msgid "<keycap>K</keycap> – La" +msgstr "<keycap>K</keycap> – A (La)" + +#. Tag: para +#: index.docbook:2321 index.docbook:2861 +#, no-c-format +msgid "<keycap>L</keycap> – Ti" +msgstr "<keycap>L</keycap> – H (Ti)" + +#. Tag: para +#: index.docbook:2324 index.docbook:2867 +#, no-c-format +msgid "" +"Holding <keycap>Shift</keycap> while pressing a key will sharpen the note " +"(except for Mi and Ti, which don't have sharpened versions) and holding " +"<keycap>Shift</keycap> and <keycap>Ctrl</keycap> together will flatten it " +"(except for Fa and Do)." +msgstr "" +"Genom att hålla nere <keycap>Skift</keycap> när en tangent trycks, fås en " +"upphöjd not (utom för E och H som inte har upphöjda versioner) och genom " +"att hålla nere <keycap>Skift</keycap> och <keycap>Ctrl</keycap> tillsammans " +"fås en nersänkt not (utom för F och C)." + +#. Tag: para +#: index.docbook:2330 index.docbook:2873 +#, no-c-format +msgid "" +"To enter notes an octave higher, use the corresponding keys on the next row " +"up: <keycap>Q</keycap>, <keycap>W</keycap>, <keycap>E</keycap>, " +"<keycap>R</keycap>, <keycap>U</keycap>, <keycap>I</keycap>, and " +"<keycap>O</keycap>. Likewise to enter notes an octave lower, use " +"<keycap>Z</keycap>, <keycap>X</keycap>, <keycap>C</keycap>, " +"<keycap>V</keycap>, <keycap>B</keycap>, <keycap>N</keycap> and " +"<keycap>M</keycap>." +msgstr "" +"För att skriva in noter en oktav högre,använd motsvarande tangenter på " +"nästa rad ovanför: <keycap>Q</keycap>, <keycap>W</keycap>, " +"<keycap>E</keycap>, <keycap>R</keycap>, <keycap>U</keycap>, " +"<keycap>I</keycap> och <keycap>O</keycap>. På motsvarande sätt, för att " +"lägga till noter en oktav lägre, använd <keycap>Z</keycap>, " +"<keycap>X</keycap>, <keycap>C</keycap>, <keycap>V</keycap>, " +"<keycap>B</keycap>, <keycap>N</keycap> och <keycap>M</keycap>." + +#. Tag: title +#: index.docbook:2342 index.docbook:2930 +#, no-c-format +msgid "Other remarks" +msgstr "Övriga anmärkningar" + +#. Tag: para +#: index.docbook:2344 index.docbook:2932 +#, no-c-format +msgid "" +"All of the insertion commands are also available on a submenu of the Tools " +"menu. It's unlikely you'd ever want to navigate the menus just to insert a " +"single note, but the menus show the keyboard shortcuts and so provide a " +"useful reference in case you forget which key is which." +msgstr "" +"Alla infogningskommandon är också tillgängliga från en undermeny i menyn " +"Verktyg. Det är inte troligt att du någonsin vill navigera i menyn bara " +"för att infoga en enstaka not, men menyerna visar snabbtangenterna och " +"tillhandahåller på så sätt en användbar referens om du skulle glömma " +"vilken tangent som gör vad." + +#. Tag: para +#: index.docbook:2350 +#, no-c-format +msgid "" +"The keyboard shortcuts are currently designed for use with a QWERTY-layout " +"keyboard. There is not yet any way to remap the keys for another layout, " +"short of reassigning each key individually using <menuchoice> <guimenu " +"lang=\"en\">Settings</guimenu> <guimenuitem>Configure " +"Shortcuts...</guimenuitem> </menuchoice>." +msgstr "" +"Snabbtangenterna är för närvarande gjorda för att användas med " +"tangentbord som har QWERTY-organisation. Det finns ännu inte något sätt att " +"ändra snabbtangenter till en annan organisation, förutom att individuellt " +"ändra tilldelning av varje tangent med <menuchoice><guimenu " +"lang=\"sv\">Inställningar</guimenu> <guimenuitem>Anpassa " +"genvägar...</guimenuitem></menuchoice>." + +#. Tag: title +#: index.docbook:2363 index.docbook:2953 +#, no-c-format +msgid "Entering notes using a MIDI keyboard" +msgstr "Skriva in noter genom att använda ett MIDI-keyboard" + +#. Tag: para +#: index.docbook:2365 +#, no-c-format +msgid "" +"You can enter notes into the matrix editor one at a time using a MIDI " +"keyboard or other MIDI control device. The matrix editor uses the pitches " +"you play on the keyboard, but the durations you have selected in the Grid " +"setting of the editor itself. This is known as \"step recording\"." +msgstr "" +"Du kan lägga till noter i matriseditorn en i taget med ett MIDI-keyboard " +"eller en annan MIDI-styrenhet. Matriseditorn använder tonhöjden du spelar " +"på ett keyboard, men de notvärden du har valt i editorns egna " +"rutnätsinställningar. Det är känt som \"stegvis inspelning\"." + +#. Tag: para +#: index.docbook:2373 +#, no-c-format +msgid "" +"To start entering notes from a MIDI keyboard, first make sure the keyboard " +"is configured as your default MIDI record device. Then make sure you have " +"the right Grid setting in the View menu or toolbar, as this controls the " +"note duration. Then press the step recording button on the matrix editor's " +"toolbar, or select Step Recording from the Tools menu. From that point on " +"all notes pressed on the MIDI keyboard will be inserted at the current " +"insertion time in that window, until step recording is switched off again or " +"activated in a different window or the window is closed." +msgstr "" +"För att börja mata in noter från ett MIDI-keyboard, försäkra dig först " +"om att det är inställt som förvald MIDI-inspelningsenhet. Försäkra dig " +"därefter om att du har rätt rutnätsinställning i menyn Visa eller på " +"verktygsraden, eftersom det styr notvärdena. Tryck därefter på " +"knappen för stegvis inspelning i matriseditorns verktygsrad, eller välj " +"Stegvis inspelning i menyn Verktyg. Från detta ögonblick infogas alla " +"toner som du spelar på ditt MIDI-keyboard vid den nuvarande inmatningstiden " +"i fönstret, ända till stegvis inspelning stängs av igen, aktiveras i ett " +"annat fönster eller fönstret stängs." + +#. Tag: para +#: index.docbook:2387 +#, no-c-format +msgid "" +"You can change the Grid setting while step recording is in progress, in " +"order to insert notes of different durations." +msgstr "" +"Du kan ändra rutnätsinställningar medan stegvis inspelning pågår, för " +"att infoga noter med olika notvärden." + +#. Tag: title +#: index.docbook:2395 +#, no-c-format +msgid "Selecting notes" +msgstr "Markera noter" + +#. Tag: para +#: index.docbook:2395 +#, no-c-format +msgid "" +"To select notes in the matrix editor, switch to the Select (arrow) tool and " +"then outline a rectangular area containing the notes you want to select. The " +"selected events will then be highlighted in blue. If you instead click on a " +"single event, just that event will be selected." +msgstr "" +"För att markera noter i matriseditorn, byt till markeringsverktyget (pilen) " +"och rita upp ett rektangulärt område som innehåller noterna du vill " +"markera. Markerade händelser färgläggs då i blått. Om du istället " +"klickar på en enstaka händelse, markeras bara den händelsen." + +#. Tag: para +#: index.docbook:2402 +#, no-c-format +msgid "" +"If you hold <keycap>Shift</keycap> while dragging out a rectangle or " +"clicking on a note, the new selection will be added to any existing " +"selection instead of replacing it." +msgstr "" +"Om du håller nere <keycap>Skift</keycap> medan du ritar upp en rektangel " +"eller klickar på en not, läggs den nya markeringen till i en eventuell " +"befintlig markering istället för att ersätta den." + +#. Tag: para +#: index.docbook:2407 +#, no-c-format +msgid "" +"To clear a selection, click in an empty space on the matrix editor, or hit " +"the Escape key." +msgstr "" +"För att rensa en markering, klicka på ett tomt område i matriseditorn " +"eller tryck på Esc-tangenten." + +#. Tag: para +#: index.docbook:2411 +#, no-c-format +msgid "" +"You can also select all of the notes of a given pitch, by shift-clicking on " +"a key in the piano keyboard down the left side of the matrix editor. You can " +"also shift-click and drag to select a range of pitches. This selection is " +"added to any existing selection you have, so if you want a clean new " +"selection, clear the old one first." +msgstr "" +"Du kan också markera alla noter av en viss tonhöjd genom att skift-klicka " +"på en tangent på pianoklaviaturen längs vänster sida i matriseditorn. Du " +"kan också skift-klicka och dra för att markera en uppsättning tonhöjder. " +"Markeringen läggs till i en eventuell befintlig markering, så om du vill " +"ha en helt ny markering, avmarkera först den föregående." + +#. Tag: title +#: index.docbook:2421 +#, no-c-format +msgid "Moving and copying notes" +msgstr "Flytta och kopiera noter" + +#. Tag: para +#: index.docbook:2422 +#, no-c-format +msgid "" +"You can move notes in both time and pitch on the matrix editor by either " +"clicking and dragging them with the Move tool, or selecting them and then " +"dragging them with the Select tool." +msgstr "" +"Du kan flytta noter både i tid och tonhöjd i matriseditorn genom att " +"antingen klicka och dra dem med förflyttningsverktyget, eller markera dem " +"och därefter dra dem med markeringsverktyget." + +#. Tag: para +#: index.docbook:2428 +#, no-c-format +msgid "" +"To copy notes, select them and then use the standard copy and paste " +"functions. After the paste the pasted notes will be selected instead, and " +"you can then drag them wherever you need them." +msgstr "" +"För att kopiera noter, markera dem och använd därefter de vanliga " +"funktionerna kopiera och klistra in. Efter de har klistrats in är de " +"inklistrade noterna markerade istället, och du kan dra dem var du än vill " +"ha dem." + +#. Tag: title +#: index.docbook:2439 +#, no-c-format +msgid "The Percussion Matrix editor" +msgstr "Slagverksmatriseditorn" + +#. Tag: para +#: index.docbook:2441 +#, no-c-format +msgid "" +"The Percussion Matrix editor is identical to the <link " +"linkend=\"matrix-view\">Matrix editor</link>, except that it shows pitch " +"names on the vertical scale instead of a piano keyboard, and it does not " +"show the duration for each note. This is intended for use with percussion " +"programs on MIDI instruments, in which each note pitch plays a different " +"percussion sound." +msgstr "" +"Slagverksmatriseditorn är identisk med <link linkend=\"matrix-view\">" +"matriseditorn</link>, förutom att den visar tonhöjdsnamn på den " +"vertikala skalan istället för pianotangenter, och att den inte visar " +"notvärdet för varje not. Den är avsedd för användning med " +"slagverksprogram i MIDI-instrument, där varje tonhöjd spelar ett " +"annorlunda slagverksljud." + +#. Tag: para +#: index.docbook:2448 +#, no-c-format +msgid "See also <link linkend=\"studio-keymappings\">Percussion Key Mappings</link>" +msgstr "Se också <link linkend=\"studio-keymappings\">Tonavbildningar för slagverk</link>." + +#. Tag: title +#: index.docbook:2453 +#, no-c-format +msgid "The Notation editor" +msgstr "Notbehandlaren" + +#. Tag: para +#: index.docbook:2460 +#, no-c-format +msgid "" +"The &rosegarden; notation editor enables you to view and edit one or more " +"staffs in traditional score notation." +msgstr "" +"&rosegarden;s notbehandlare gör det möjligt att visa och redigera ett " +"eller flera notsystem med traditionell partiturnotation." + +#. Tag: phrase +#: index.docbook:2473 +#, no-c-format +msgid "&rosegarden;'s notation editor" +msgstr "&rosegarden;s notbehandlare" + +#. Tag: para +#: index.docbook:2478 +#, no-c-format +msgid "" +"&rosegarden; aims to present scores with the best possible layout compatible " +"with its primary focus as a sequencer application. This means that although " +"the editor supports chords, overlapping and nested beamed groups, triplets " +"and arbitrary tuplets, grace notes, dynamics, accents, text and so on, it " +"does not provide as much fine control over layout (especially in " +"contrapuntal music) as a dedicated score editing program might. &rosegarden; " +"does not aim to produce typeset-quality score, although it can export " +"Lilypond files, which may form a good basis for typesetting." +msgstr "" +"&rosegarden; försöker presentera partitur med bästa möjliga utläggning givet " +"dess huvudsakliga fokus som en musikbehandlare. Det betyder att även om " +"editorn stöder ackord, överlappande och nästlade balkgrupper, trioler och " +"godtyckliga annandelningar, prydnadsnoter, dynamik, accenter, text och så " +"vidare, tillhandahåller den inte så mycket detaljkontroll över utläggningen " +"(särskilt i musik med kontrapunkt) som särskilda program för redigering " +"av partitur kan göra. &rosegarden; har inte som mål att skapa partitur av " +"typsättningskvalitet, även om Lilypond-filer kan exporteras, vilka kan " +"utgöra en bra grund för typsättning." + +#. Tag: title +#: index.docbook:2496 +#, no-c-format +msgid "Single and multiple staffs" +msgstr "Enkla och flera notsystem" + +#. Tag: para +#: index.docbook:2498 +#, no-c-format +msgid "" +"There are three ways to open a notation editor from the &rosegarden; main " +"window. (They all require that you have some existing segments in the main " +"window first, so if you're starting a new composition, you should create " +"your segments before you start thinking about how to edit them.)" +msgstr "" +"Det finns tre sätt att öppna en notbehandlare i &rosegarden;s " +"huvudfönster. (Alla kräver att du först har ett befintligt segment i " +"huvudfönstret, så om du påbörjar en ny komposition, bör du skapa dina " +"segment innan du börjar fundera på hur de ska redigeras.)" + +#. Tag: term +#: index.docbook:2509 +#, no-c-format +msgid "Double-clicking on segments" +msgstr "Dubbelklicka på segment" + +#. Tag: para +#: index.docbook:2512 +#, no-c-format +msgid "" +"The most obvious way is just to double-click on a segment in the main " +"canvas. This opens the segment in whatever you have configured as the " +"default editor (notation, matrix, or event list), and by default this is the " +"notation editor. So double-clicking a single segment will open it as a " +"single staff in a Notation editor window." +msgstr "" +"Det mest uppenbara sättet är att dubbelklicka på ett segment på " +"huvudduken. Det öppnar segmentet i den editor som du har ställt in som " +"standardvy (not, matris eller händelselista), som normalt är " +"notbehandlaren. Alltså öppnas ett segment som ett enskilt notsystem i " +"notbehandlarens fönster genom att dubbelklicka på det." + +#. Tag: para +#: index.docbook:2520 +#, no-c-format +msgid "" +"You can also open a multi-staff editor this way: holding down the Shift key, " +"select (with a single mouse click) each of the segments on the main view " +"that you want to open, but double-click on the last one. All of the selected " +"segments will then be opened together in a single notation window." +msgstr "" +"Du kan också öppna en editor med flera notsystem på följande sätt: " +"Håll nere Skift-tangenten, markera (med ett enda musklick) alla segment i " +"huvudvyn som du vill öppna, men dubbelklicka på det sista. Alla markerade " +"segment öppnas då tillsammans i ett enda fönster i notbehandlaren." + +#. Tag: term +#: index.docbook:2531 +#, no-c-format +msgid "The Open in Default Editor menu function (the Return key)" +msgstr "Funktionen Öppna i standardvy (returtangenten)" + +#. Tag: para +#: index.docbook:2534 +#, no-c-format +msgid "" +"The Return key is a shortcut for the Open in Default Editor menu function, " +"which does much the same thing as double-clicking: opens all of the " +"currently selected segments together in a notation editor, or in whichever " +"other editor you have configured as your default." +msgstr "" +"Returtangenten är en snabbtangent för menyfunktionen att öppna i " +"standardvyn, som gör i stort sett samma sak som att dubbelklicka: Den " +"öppnar alla segment som för närvarande är markerade i notbehandlaren, " +"eller i någon annan editor som du har ställt in som standardvy." + +#. Tag: term +#: index.docbook:2544 +#, no-c-format +msgid "The Open in Notation Editor menu functions" +msgstr "Menyfunktionerna Öppna i notbehandlare" + +#. Tag: para +#: index.docbook:2547 +#, no-c-format +msgid "" +"Alternatively, you can use the main window's Open in Notation Editor menu " +"function, either on the Segments menu or on the right-button popup menu on a " +"segment in the canvas. Select the segments you want to edit (by " +"shift-clicking as above, or by using the Select All Segments function) and " +"then select Open in Notation Editor." +msgstr "" +"Som ett alternativ kan du använda huvudfönstrets menyalternativ Öppna i " +"notbehandlare, antingen i menyn Segment eller i menyn som visas med " +"höger musknapp över ett segment på duken. Markera segmenten du vill " +"redigera (genom att skift-klicka som ovan, eller genom att använda " +"alternativet Markera alla segment) och välj därefter Öppna i " +"notbehandlare." + +#. Tag: para +#: index.docbook:2563 +#, no-c-format +msgid "" +"If you have more than one staff (i.e. segment) visible in the notation " +"editor, only one of them can be \"current\" at once. The current staff can " +"be distinguished because it has the insert cursor on it (see <link " +"linkend=\"nv-rulers\">Rulers and Cursors</link>), and this is the staff on " +"which any editing operations that use the insert cursor will take place. The " +"topmost staff is the current one by default, but you can switch to a " +"different staff by ctrl-clicking on it or by using the Move Cursor Up Staff " +"and Move Cursor Down Staff menu functions." +msgstr "" +"Om du har mer än ett notsystem (dvs. segment) synligt i notbehandlaren " +"kan bara ett av dem vara \"aktuellt\" på en gång. Det aktuella notsystemet " +"kan urskiljas eftersom infogningsmarkören visas i det (se <link " +"linkend=\"nv-rulers\">Linjaler och markörer</link>), och det är " +"notsystemet där alla redigeringsåtgärder som använder " +"infogningsmarkören äger rum. Det översta notsystemet är normalt det " +"aktuella, men du kan byta till ett annat notsystem genom att Ctrl-klicka på " +"det eller genom att använda menyalternativen Markör upp notsystem och " +"Markör ner notsystem." + +#. Tag: title +#: index.docbook:2579 +#, no-c-format +msgid "Linear and page layouts" +msgstr "Horisontell och sidbaserad utläggning" + +#. Tag: para +#: index.docbook:2581 +#, no-c-format +msgid "" +"The usual way the notation editor displays staffs is known as Linear layout: " +"one staff on top of another, with each staff as a single, horizontally " +"scrollable long line. Some of the functions of the editor (such as the <link " +"linkend=\"nv-rulers\">Rulers</link>) are only available in Linear layout." +msgstr "" +"Det vanliga sättet som notbehandlaren visar notsystem är känt som " +"horisontell utläggning: Notsystem ovanför varandra, med varje notsystem som " +"en enda, horisontell rullande lång rad. Vissa funktioner i editorn (som " +"<link linkend=\"nv-rulers\">linjalerna</link>) är bara tillgängliga med " +"horisontell utläggning." + +#. Tag: para +#: index.docbook:2590 +#, no-c-format +msgid "" +"However, you can also display staffs in two different page-based layouts: " +"Continuous Page and Multiple Page." +msgstr "" +"Du kan dock också visa notsystem med två olika sidbaserade utläggningar: " +"Vertikal utläggning eller Sidutläggning." + +#. Tag: para +#: index.docbook:2594 +#, no-c-format +msgid "" +"In Continuous Page layout, the music is arranged in one infinitely-tall page " +"of the same width as the window. Each staff breaks at the end of a line, " +"starting a new line below the remaining staffs." +msgstr "" +"I vertikal utläggning visas noteringen på en oändligt hög sida med " +"samma bredd som fönstret. Varje notsystem bryts vid radens slut, och " +"påbörjar en ny rad under återstående notsystem." + +#. Tag: para +#: index.docbook:2599 +#, no-c-format +msgid "" +"In Multiple Page layout, the music is divided up into real pages much as it " +"will be when printed. The size of each page is calculated so that " +"approximately the same amount of music will fit on each line as it will when " +"actually printed (according to the point size specified for the printing " +"resolution in the configuration dialog). The printed version is unlikely to " +"be exactly the same, as it depends on the precise paper size and margins in " +"use when printing, but it should be fairly close if you happen to be using " +"A4 paper." +msgstr "" +"I sidutläggning visas noteringen uppdelad på riktiga sidor i stort sett " +"som den ser ut när den skrivs ut. Varje sidas storlek beräknas så att " +"ungefär samma antal noter får plats på varje rad som när det verkligen " +"skrivs ut (enligt punktstorleken som anges för utskriftsupplösningen i " +"inställningsdialogrutan). Den utskrivna versionen är troligen inte precis " +"likadan, eftersom det beror på den exakta pappersstorleken och marginalerna " +"som används vid utskrift, men det bör vara ganska nära om du råkar " +"använda A4-papper." + +#. Tag: phrase +#: index.docbook:2617 +#, no-c-format +msgid "&rosegarden;'s notation editor in Multiple Page layout" +msgstr "&rosegarden;s notbehandlare med sidutläggning" + +#. Tag: para +#: index.docbook:2621 +#, no-c-format +msgid "" +"Most, but not all, of the display and editing functions work in the page " +"layout modes as well as in linear layout." +msgstr "" +"De flesta, men inte alla, av visnings- och redigeringsfunktionerna fungerar " +"lika bra i sidutläggningslägena som i horisontell utläggning." + +#. Tag: para +#: index.docbook:2626 +#, no-c-format +msgid "" +"To switch between these layout modes, use the Linear Layout, Continuous Page " +"Layout and Multiple Page Layout menu functions." +msgstr "" +"För att byta mellan utläggningslägen, använd menyalternativen Horisontell " +"utläggning, Vertikal utläggning och Sidutläggning." + +#. Tag: title +#: index.docbook:2634 +#, no-c-format +msgid "Rulers and cursors" +msgstr "Linjaler och markörer" + +#. Tag: para +#: index.docbook:2636 +#, no-c-format +msgid "" +"The &rosegarden; Notation editor window includes two rulers and two cursors. " +"The rulers are the horizontal strips divided up with tickmarks at top and " +"bottom of the main notation canvas, and the cursors are the coloured " +"vertical lines shown initially at the start of the top staff in the editor." +msgstr "" +"&rosegarden;s notredigeringsfönster innehåller två linjaler och " +"två markörer. Linjalerna är de horisontella raderna uppdelade med " +"graderingar längst upp och längst ner på huvudnoteringsduken, och " +"markörerna är de färgade vertikala linjerna som ursprungligen visas i " +"början av det översta notsystemet i editorn." + +#. Tag: para +#: index.docbook:2645 +#, no-c-format +msgid "" +"The purple cursor is the insert cursor. It shows the point at which " +"operations such as insert and paste will take place. You can reposition the " +"insert cursor by clicking or dragging on the top ruler, or by clicking with " +"the Select tool on an empty part of the staff (avoiding any events), or by " +"clicking anywhere with <keycap>Ctrl</keycap> held down." +msgstr "" +"Den violetta markören är infogningsmarkören. Den visar platsen där " +"åtgärder som infoga och klistra in utförs. Du kan flytta " +"infogningsmarkören genom att klicka eller dra på den övre linjalen, eller " +"genom att klicka med markeringsverktyget på en tom del av notsystemet (och " +"undvika alla händelser), eller genom att klicka var som helst med " +"<keycap>Ctrl</keycap> intryckt." + +#. Tag: para +#: index.docbook:2654 +#, no-c-format +msgid "" +"You can also use the left and right arrow keys to move the insert cursor one " +"event at a time. If you hold <keycap>Ctrl</keycap> while pressing the arrow " +"keys, the cursor will move a whole bar at a time; if you hold Shift, the " +"cursor will <link linkend=\"nv-tools-selections\">select the events</link> " +"as it passes over them." +msgstr "" +"Du kan också använda vänster och höger piltangenter för att flytta " +"infogningsmarkören en händelse i taget. Om du håller nere " +"<keycap>Ctrl</keycap> medan piltangenterna trycks, flyttas markören en hel " +"takt åt gången. Om du håller nere Skift, <link " +"linkend=\"nv-tools-selections\">markeras händelserna</link> medan markören " +"rör sig över dem." + +#. Tag: para +#: index.docbook:2662 +#, no-c-format +msgid "" +"The blue cursor is the playback pointer. Just like the similar cursors in " +"the main window and the matrix views, this shows the location of the current " +"playback or record position. It can be repositioned using the bottom ruler." +msgstr "" +"Den blåa markören är uppspelningsmarkören. Precis som liknande markörer " +"i huvudfönstret och matrisvyn, visar den platsen för nuvarande uppspelning " +"eller inspelning. Den kan förflyttas genom att använda linjalen längst " +"ner." + +#. Tag: para +#: index.docbook:2669 +#, no-c-format +msgid "" +"Note that the rulers are only shown in <link linkend=\"nv-layout\">Linear " +"layout</link> mode." +msgstr "" +"Observera att linjalerna bara visas i läget <link " +"linkend=\"nv-layout\">Horisontell utläggning</link>." + +#. Tag: title +#: index.docbook:2682 +#, no-c-format +msgid "Tools and selections" +msgstr "Verktyg och markeringar" + +#. Tag: para +#: index.docbook:2683 +#, no-c-format +msgid "" +"Most of the menu and toolbar editing functions in the &rosegarden; Notation " +"editor fall into one of three categories: <quote>tools</quote>, " +"<quote>functions that operate on selections</quote>, and <quote>drag " +"operations</quote>." +msgstr "" +"De flesta redigeringsfunktioner i menyer och verktygsrader i &rosegarden;s " +"notbehandlare ingår i en av tre kategorier: <quote>verktyg</quote>, " +"<quote>funktioner som arbetar med markeringar</quote> och " +"<quote>dragåtgärder</quote>." + +#. Tag: term +#: index.docbook:2693 +#, no-c-format +msgid "Tools" +msgstr "Verktyg" + +#. Tag: para +#: index.docbook:2695 +#, no-c-format +msgid "" +"The basic tools are the selection tool, the erase tool, and those for " +"inserting notes, rests, text and so on, which are usually accessed from the " +"toolbar buttons. Choosing a tool changes the default behaviour of the mouse " +"buttons on the main notation canvas, at least until another tool is chosen " +"instead. For example, choosing the selection tool allows you to make " +"selections and so to use the selection-based functions (below); choosing an " +"insertion tool (such as one of the notes) switches the " +"<acronym>GUI</acronym>'s behaviour so as to insert notes by clicking on the " +"canvas; choosing the erase tool allows you to remove events by clicking on " +"them." +msgstr "" +"De grundläggande verktygen är markeringsverktyget, borttagningsverktyget " +"och de som används för att infoga noter, pauser, text och så vidare, " +"vilka oftast väljes med knappar i verktygsraden. Att välja ett verktyg " +"ändrar det normala beteendet hos musknapparna på huvudnoteringsduken, " +"åtminstone till ett annat verktyg väljes istället. Genom att till exempel " +"välja markeringsverktyget kan du göra markeringar och på så sätt " +"använda de markeringsbaserade funktionerna (nedan). Genom att välja ett " +"infogningsverktyg (som en av noterna) ändras det grafiska gränssnittets " +"beteende så att noter infogas genom att klicka på duken. Genom att välja " +"borttagningsverktyget gör att du kan ta bort händelser genom att klicka " +"på dem." + +#. Tag: para +#: index.docbook:2709 +#, no-c-format +msgid "You can also change the current tool using the Tools menu." +msgstr "Du kan också byta aktuellt verktyg med menyn Verktyg." + +#. Tag: term +#: index.docbook:2716 +#, no-c-format +msgid "Functions that operate on selections" +msgstr "Funktioner som arbetar med markeringar" + +#. Tag: para +#: index.docbook:2718 +#, no-c-format +msgid "" +"The majority of the remaining menu functions require a selection to be made " +"on the canvas before they can be used. Some of them (such as " +"<guimenuitem>Cut</guimenuitem> or the <guimenuitem>Note Style</guimenuitem> " +"functions) will operate on any selected events; others (such as the " +"<guimenuitem>Grace Notes</guimenuitem> or <guimenuitem>Stem " +"Directions</guimenuitem> functions) will refuse to work unless the selection " +"contains some notes." +msgstr "" +"Flertalet återstående menyalternativen kräver att en markering görs på " +"duken innan de kan användas. Vissa av dem (såsom alternativen " +"<guimenuitem>Klipp ut</guimenuitem> eller " +"<guimenuitem>Notstil</guimenuitem>) fungerar på alla händelser som " +"markerats. Andra (såsom <guimenuitem>Prydnadsnot</guimenuitem> eller " +"<guimenuitem>Skaftriktning</guimenuitem>) vägrar fungera om inte " +"markeringen innehåller några noter." + +#. Tag: para +#: index.docbook:2729 +#, no-c-format +msgid "" +"To select some events on the canvas, switch to the Select (arrow) tool and " +"then outline a rectangular area containing the events you want to select. " +"The selected events will then be highlighted in blue. If you click on a " +"single event, just that event will be selected <footnote> <para> You can " +"also double-click on a single event to open an editing dialog for that " +"event, but that's got nothing to do with selections.</para> </footnote>)." +msgstr "" +"För att markera några händelser på duken, byt till markeringsverktyget " +"(pilen) och rita därefter upp ett rektangulärt område som innehåller " +"händelserna du vill markera. De markerade händelserna färgläggs då med " +"blått. Om du klickar på en enskild händelse, markeras bara den händelsen " +"<footnote> <para> Du kan också dubbelklicka på en enskild händelse för " +"att visa en redigeringsdialogruta för händelsen, men det har ingenting att " +"göra med markeringar.</para> </footnote>)." + +#. Tag: para +#: index.docbook:2738 +#, no-c-format +msgid "" +"If you hold <keycap>Shift</keycap> while dragging out a rectangle, its " +"contents will be added to any existing selection instead of replacing it." +msgstr "" +"Om du håller nere <keycap>Skift</keycap> medan du ritar upp en rektangel, " +"läggs innehållet till i en eventuell befintlig markering istället för " +"att ersätta den." + +#. Tag: para +#: index.docbook:2743 +#, no-c-format +msgid "" +"To select a whole bar, double-click with the Select tool on some empty space " +"within that bar; to select the whole staff, click three times. The Edit menu " +"carries functions for selecting extended areas based on the location of the " +"insert cursor, and you can also select events around the insert cursor by " +"holding Shift and pressing the left or right arrow keys." +msgstr "" +"För att markera en hel takt, dubbelklicka med markeringsverktyget på ett " +"tomt utrymme i takten. För att markera hela notsystemet, klicka tre " +"gånger. Redigeringsmenyn innehåller alternativ för att markera utökade " +"områden baserat på infogningsmarkörens plats, och du kan också markera " +"händelser omkring infogningsmarkören genom att hålla nere Skift och " +"trycka på vänster eller höger piltangent." + +#. Tag: para +#: index.docbook:2752 +#, no-c-format +msgid "It is not possible to select events from more than one staff at once." +msgstr "" +"Det är inte möjligt att markera händelser i mer än ett notsystem på en " +"gång." + +#. Tag: term +#: index.docbook:2760 +#, no-c-format +msgid "Drag operations" +msgstr "Dragåtgärder" + +#. Tag: para +#: index.docbook:2762 +#, no-c-format +msgid "" +"You can also do a certain amount of editing just by dragging things around. " +"Switch to the Select (arrow) tool, and then you can change the pitch of " +"notes by just click-and-dragging their heads up or down, and change the " +"times of notes and other events by dragging them left or right. (You can't " +"drag rests or time signatures, but you can drag everything else. If you have " +"more than one event selected, the whole selection will be dragged at once.)" +msgstr "" +"Du kan också utföra en viss mängd redigering genom att bara dra omkring " +"saker. Byt till markeringsverktyget (pilen), och därefter kan du ändra " +"tonhöjd på noter genom att bara klicka och dra deras huvuden uppåt eller " +"neråt, och ändra tider för noter och andra händelser genom att dra dem " +"åt vänster eller höger. (Du kan inte dra pauser eller taktarter, " +"men du kan dra allting annat. Om du har markerat mer än en händelse, dras " +"hela markeringen på en gång.)" + +#. Tag: para +#: index.docbook:2773 +#, no-c-format +msgid "" +"Dragging is usually a less accurate way of editing things than using the " +"menu or toolbar functions, but it can be easier." +msgstr "" +"Att dra är oftast ett mindre noggrant sätt att redigera än att använda " +"funktionerna i menyn eller verktygsraden, men det kan vara enklare." + +#. Tag: title +#: index.docbook:2786 +#, no-c-format +msgid "Inserting notes and rests" +msgstr "Infoga noter och pauser" + +#. Tag: para +#: index.docbook:2788 +#, no-c-format +msgid "" +"To insert a note, select one of the note tools by clicking on a particular " +"duration of note on the toolbar, and then click on the staff at the point " +"where you want to add the note." +msgstr "" +"För att infoga en not, välj ett av notverktygen genom att klicka på ett " +"visst notvärde i verktygsraden, och därefter klicka i notsystemet på " +"platsen där du vill lägga till noten." + +#. Tag: para +#: index.docbook:2792 +#, no-c-format +msgid "" +"You can also select one of the accidentals on the toolbar to insert " +"sharpened or flattened notes. If no accidental is selected, the note " +"inserted will follow the key signature. Alternatively, you can select the " +"\"Follow previous accidental\" icon (shown as a note with an arrow pointing " +"back from where the accidental would appear) to make the note follow " +"whatever accidental was last used at the same height on the staff." +msgstr "" +"Du kan också markera en av de tillfälliga förtecknen på verktygsraden " +"för att infoga upphöjda eller nersänkta noter. Om inget tillfälligt " +"förtecken används, följer den infogade noten de fasta förtecknen. Som ett " +"alternativ kan du välja ikonen \"Följ föregående tillfälliga förtecken\" " +"(som visas som en not med en pil som pekar tillbaka från stället där " +"förtecknet skulle visas) för att få noten att följa det tillfälliga " +"förtecken som senast användes på samma plats i notsystemet." + +#. Tag: para +#: index.docbook:2800 +#, no-c-format +msgid "" +"If you add a note at the same time as an existing note of different " +"duration, the editor will generally assume that you want to create chords " +"and will split the existing or new note accordingly so as to create one or " +"more chords with ties. If you really do want to chord two different " +"durations, you can select the tied noteheads and use the Collapse " +"Equal-Pitch Notes function to merge them together. Alternatively, the " +"default behaviour can be changed in the &rosegarden; configuration dialog so " +"as not to do the split at all." +msgstr "" +"Om du lägger till en not på samma tid som en befintlig not med annat " +"notvärde, antar editorn i allmänhet att du vill skapa ackord och delar upp " +"den befintliga eller nya noten på motsvarande sätt för att skapa ett " +"eller flera bundna ackord. Om du verkligen vill skapa ett ackord med två " +"olika notvärden, kan du markera de bundna nothuvudena och använda funktionen " +"Lägg ihop noter med samma tonhöjd för att lägga ihop dem. Som ett " +"alternativ kan det förvalda beteendet ändras in &rosegarden;s " +"inställningsdialogruta, så att uppdelningen inte alls görs." + +#. Tag: para +#: index.docbook:2810 +#, no-c-format +msgid "" +"If you add a note exactly over an existing note of different duration (i.e. " +"at the same pitch), the duration of the existing note will be changed to " +"that of the new one." +msgstr "" +"Om du lägger till en not exakt ovanpå en befintlig not med annorlunda " +"notvärde (dvs. på samma tonhöjd), ändras notvärdet på den befintliga noten " +"till det nya notvärdet." + +#. Tag: para +#: index.docbook:2814 +#, no-c-format +msgid "" +"If you add a rest at the same time as an existing note, the note will be " +"silenced for the duration of the rest, shortening or possibly removing it " +"altogether." +msgstr "" +"Om du lägger till en paus på exakt samma tid som en befintlig not, blir " +"den befintliga noten tyst under pausvärdet, vilket förkortar den eller " +"möjligen tar bort den helt och hållet." + +#. Tag: title +#: index.docbook:2819 +#, no-c-format +msgid "Typing notes and rests with the PC keyboard" +msgstr "Skriva in noter och pauser med datorns tangentbord" + +#. Tag: para +#: index.docbook:2824 +#, no-c-format +msgid "" +"First, ensure a notation tool is selected to indicate the duration of note " +"(or rest) you wish to insert. You can select the various note types using " +"the number keys:" +msgstr "" +"Försäkra dig först om att ett notverktyg är valt för att ange " +"notvärdet (eller pausvärdet) som du vill infoga. Du kan välja de " +"olika nottyperna genom att använda nummertangenterna:" + +#. Tag: para +#: index.docbook:2829 +#, no-c-format +msgid "<keycap>5</keycap> – Breve" +msgstr "<keycap>5</keycap> – Brevis" + +#. Tag: para +#: index.docbook:2830 +#, no-c-format +msgid "<keycap>1</keycap> – Whole note (semibreve)" +msgstr "<keycap>1</keycap> – Helnot" + +#. Tag: para +#: index.docbook:2839 +#, no-c-format +msgid "" +"You can switch to a triplet version of the note duration by pressing the " +"<keycap>G</keycap> key. Pressing it again will switch back to the normal " +"duration. The status bar at the bottom of the window will notify you of when " +"a triplet duration is active." +msgstr "" +"Du kan byta till en triolversion av notvärdet genom att trycka på " +"tangenten <keycap>G</keycap>. Genom att trycka på den igen byter du " +"tillbaka till normalt notvärde. Statusraden längst ner i fönstret " +"underrättar dig om att ett triolvärde är aktivt." + +#. Tag: para +#: index.docbook:2849 +#, no-c-format +msgid "" +"Once a notation tool is selected, you can insert a note at the current " +"position of the <link linkend=\"nv-rulers\">insert cursor</link> by pressing " +"one of the pitch keys:" +msgstr "" +"Så fort ett notverktyg är valt, kan du infoga en not på <link " +"linkend=\"nv-rulers\">infogningsmarkörens</link> aktuella position genom " +"att trycka på en av tonhöjdstangenterna:" + +#. Tag: para +#: index.docbook:2864 +#, no-c-format +msgid "Press the \".\" key to togggle between dotted and undotted durations." +msgstr "" +"Tryck på tangenten \".\" för att växla mellan notvärden med eller utan " +"punkt." + +#. Tag: title +#: index.docbook:2885 +#, no-c-format +msgid "Rests" +msgstr "Pauser" + +#. Tag: para +#: index.docbook:2887 +#, no-c-format +msgid "" +"To insert a rest instead of a note, press <keycap>P</keycap>. Alternatively, " +"you can use the <keycap>T</keycap> and <keycap>Y</keycap> keys to switch the " +"current tool to a rest tool and back to a note tool again." +msgstr "" +"För att infoga en paus istället för en not, tryck på <keycap>P</keycap>. " +"Som ett alternativ kan du använda tangenterna <keycap>T</keycap> och " +"<keycap>Y</keycap> för att byta aktuellt verktyg till ett pausverktyg och " +"tillbaka till ett notverktyg igen." + +#. Tag: title +#: index.docbook:2895 +#, no-c-format +msgid "Chords" +msgstr "Ackord" + +#. Tag: para +#: index.docbook:2897 +#, no-c-format +msgid "" +"The default behaviour of the notation editor is to move the insert cursor " +"forward after inserting a note, so as to be ready to insert another note " +"after it in a melody; this can be changed using the <keycap>H</keycap> key, " +"which switches to chord mode so that subsequent insertions occur at the same " +"time as the last one. Pressing <keycap>H</keycap> again switches back to the " +"melody insertion behaviour." +msgstr "" +"Normalbeteendet i notbehandlaren är att flytta infogningsmarkören " +"framåt efter en not har infogats, så att den är klar att mata in en ny " +"not på efterföljande plats i en melodi. Det kan ändras med tangenten " +"<keycap>H</keycap>, som byter till ackordsläge så att efterföljande " +"inmatning sker samtidigt som den senaste. Att trycka på <keycap>H</keycap> " +"igen byter tillbaka till inmatningsbeteende för melodi." + +#. Tag: title +#: index.docbook:2909 +#, no-c-format +msgid "Changing note durations" +msgstr "Ändra notvärden" + +#. Tag: para +#: index.docbook:2911 +#, no-c-format +msgid "" +"You can use the keyboard to change the durations of notes that you've " +"already entered. Make sure the notes you want to change are selected, and " +"then press <keycap>Ctrl</keycap> plus the number key for the note you want. " +"You can also add or remove dots, by pressing <keycap>Ctrl</keycap> plus " +"\".\" — use this repeatedly to select between one dot, two dots and no " +"dots." +msgstr "" +"Du kan använda tangentbordet för att ändra notvärden som du redan " +"har skrivit in. Försäkra dig om att noterna du vill ändra är markerade, " +"och tryck därefter på <keycap>Ctrl</keycap> samt nummertangenten för " +"noten som du vill ha. Du kan också lägga till eller ta bort punkter, genom " +"att trycka <keycap>Ctrl</keycap> och \".\". Använd det upprepade gånger " +"för att välja mellan en punkt, två punkter eller ingen punkt." + +#. Tag: para +#: index.docbook:2919 +#, no-c-format +msgid "" +"If you also hold <keycap>Alt</keycap> as well as <keycap>Ctrl</keycap>, you " +"will change the durations of the notes as displayed in the notation editor " +"without changing their performed durations. This can be very useful for " +"tidying up a score: see also <link linkend=\"nv-quantization\">notation from " +"performance data</link>." +msgstr "" +"Om du håller nere <keycap>Alt</keycap> samt <keycap>Ctrl</keycap>, ändrar " +"du notvärden som de visas i notbehandlaren utan att ändra " +"utfört notvärde. Det kan vara mycket användbart för att städa upp ett " +"partitur: Se också <link linkend=\"nv-quantization\">Notskrift från " +"utförandedata</link>." + +#. Tag: para +#: index.docbook:2938 +#, no-c-format +msgid "" +"The keyboard shortcuts are currently designed for use with a QWERTY-layout " +"keyboard. There is not yet any way to remap the keys for another layout, " +"short of reassigning each key individually using the \"Configure " +"Shortcuts...\" option on the Settings menu." +msgstr "" +"Snabbtangenterna är för närvarande gjorda för att användas med " +"tangentbord som har QWERTY-organisation. Det finns ännu inte något sätt att " +"ändra snabbtangenter till en annan organisation, förutom att individuellt " +"ändra tilldelning av varje tangent med alternativet \"Anpassa genvägar...\" " +"i menyn Inställningar." + +#. Tag: para +#: index.docbook:2944 +#, no-c-format +msgid "" +"Holding the <keycap>Ctrl</keycap> key while pressing a number will select " +"the corresponding dotted-note tool." +msgstr "" +"Genom att hålla nere <keycap>Ctrl</keycap> vid tryck på en nummertangent " +"väljes motsvarande verktyg med punkt." + +#. Tag: para +#: index.docbook:2955 +#, no-c-format +msgid "" +"You can enter notes into the notation editor one at a time using a MIDI " +"keyboard or other MIDI control device — a process known as step " +"recording. The notation editor uses the pitches you play on the keyboard, " +"but the durations you have selected in the editor itself." +msgstr "" +"Du kan lägga till noter i notbehandlaren en i taget med ett " +"MIDI-keyboard eller en annan MIDI-styrenhet, en process som är känd som " +"\"stegvis inspelning\". Notbehandlaren använder tonhöjden du spelar på " +"ett keyboard, men de notvärden du har valt i själva editorn." + +#. Tag: para +#: index.docbook:2963 +#, no-c-format +msgid "" +"To start entering notes from a MIDI keyboard, first make sure the keyboard " +"is configured as your default MIDI record device. Then make sure a notation " +"tool is selected to set a duration. Then press the step recording button on " +"the notation editor's toolbar, or select Step Recording from the Tools menu. " +"From that point on all notes pressed on the MIDI keyboard will be inserted " +"at the current insertion time in that notation window, until step recording " +"is switched off again or activated in a different window or the window is " +"closed." +msgstr "" +"För att börja mata in noter från ett MIDI-keyboard, försäkra dig först " +"om att det är inställt som förvald MIDI-inspelningsenhet. Försäkra dig " +"därefter om att ett notverktyg är valt för att ange ett notvärde. " +"Tryck därefter på knappen för stegvis inspelning i notbehandlarens " +"verktygsrad, eller välj Stegvis inspelning i menyn Verktyg. Från detta " +"ögonblick infogas alla toner som du spelar på ditt MIDI-keyboard vid den " +"nuvarande inmatningstiden i noteringsfönstret, ända till stegvis " +"inspelning stängs av igen, aktiveras i ett annat fönster eller fönstret " +"stängs." + +#. Tag: para +#: index.docbook:2977 +#, no-c-format +msgid "" +"You can select another notation tool while step recording is in progress, in " +"order to insert notes of different durations; and you can also switch into " +"Chord mode to insert chords." +msgstr "" +"Du kan välja ett annat notverktyg medan stegvis inspelning pågår " +"för att infoga noter med olika notvärden, och du kan också byta till " +"ackordläge för att infoga ackord." + +#. Tag: title +#: index.docbook:2990 +#, no-c-format +msgid "Clef and key" +msgstr "Klav och tonart" + +#. Tag: para +#: index.docbook:2993 +#, no-c-format +msgid "" +"The first thing to know about the way &rosegarden; handles these is that " +"time-related changes (tempos and time signatures) are treated entirely " +"differently from clefs and keys. In order to simplify managing playback and " +"recording as well as notation, &rosegarden; requires that when the tempo or " +"time signature changes, it does so in all staffs at once. You can't have one " +"staff in 3/4 and another in 4/4 simultaneously, or one staff playing at 120 " +"to the beat and another at 90. This applies only to time: there is no such " +"restriction on the use of clef and key changes." +msgstr "" +"Det första man måste veta om hur &rosegarden; hanterar dessa är att " +"tidsrelaterade ändringar (tempo och taktarter) hanteras helt " +"annorlunda än klaver och tonarter. För att förenkla hantering av " +"uppspelning och inspelning samt notering, kräver &rosegarden; att när " +"tempo eller taktart ändras, görs det i alla notsystem på en " +"gång. Du kan inte låta ett notsystem använda 3/4 medan ett annat " +"samtidigt använder 4/4, eller ha ett notsystem som spelar med 120 taktslag " +"och ett annat med 90. Det gäller bara tid: Det finns inga sådana " +"begränsningar för användning av klav- och tonartsbyten." + +#. Tag: para +#: index.docbook:3004 +#, no-c-format +msgid "" +"To change the clef, key, tempo or time signature within a notation editor " +"window, position the <link linkend=\"nv-rulers\">insert cursor</link> at the " +"point where you want the change to happen, and use one of the Edit menu's " +"Add Clef Change..., Add Key Change..., Add Tempo Change... and Add Time " +"Signature Change... functions. You will then see a dialog box in which you " +"can choose the particular clef, key, tempo or time signature setting you " +"want to apply, as follows." +msgstr "" +"För att ändra klav, tonart, tempobeteckning eller taktart inne i ett " +"fönster i notbehandlaren, placera <link " +"linkend=\"nv-rulers\">infogningsmarkören</link> på ett ställe där du " +"vill att ändringen ska ske, och använd en av redigeringsmenyns funktioner " +"Lägg till klavbyte..., Lägg till tonartsbyte..., Byt " +"tempo... eller Byt taktart... . Då visas en " +"dialogruta där du kan välja en viss inställning för klav, tonart, " +"tempobeteckning eller taktart som du vill använda, enligt följande." + +#. Tag: title +#: index.docbook:3014 +#, no-c-format +msgid "Clef" +msgstr "Klav" + +#. Tag: phrase +#: index.docbook:3022 +#, no-c-format +msgid "&rosegarden;'s clef dialog" +msgstr "&rosegarden;s klavdialogruta" + +#. Tag: para +#: index.docbook:3028 +#, no-c-format +msgid "" +"The dialog allows you to choose a clef, but also to choose how you want the " +"clef to be applied, in cases where there are already some notes following " +"the point where the clef is to be inserted. You must choose one of the " +"following:" +msgstr "" +"Dialogrutan låter dig välja en klav, och låter dig dessutom välja hur du " +"vill att klaven ska användas, i fall där det redan finns några noter " +"efter punkten där klaven ska infogas. Du måste välja något av följande:" + +#. Tag: term +#: index.docbook:3037 +#, no-c-format +msgid "Maintain current pitches" +msgstr "Behåll nuvarande tonhöjder" + +#. Tag: para +#: index.docbook:3039 +#, no-c-format +msgid "Any notes following the clef will keep their current performance pitches." +msgstr "Alla noter som följer klaven behåller sina nuvarande utförda tonhöjder." + +#. Tag: para +#: index.docbook:3043 +#, no-c-format +msgid "" +"For example, inserting a tenor clef in the middle of a previously " +"treble-clef section will cause the notes following the clef to be moved an " +"octave higher up the staff, because they will still have their treble-clef " +"pitches." +msgstr "" +"Genom att till exempel infoga en c-klav i mitten av ett avsnitt med en " +"tidigare g-klav gör att noterna som kommer efter klaven att flyttas en " +"oktav högre i notsystemet, eftersom de fortfarande har sina tonhöjder " +"enligt g-klaven." + +#. Tag: term +#: index.docbook:3055 +#, no-c-format +msgid "Transpose into appropriate octave" +msgstr "Transponera till lämplig oktav" + +#. Tag: para +#: index.docbook:3057 +#, no-c-format +msgid "" +"Any notes following the clef will retain their pitch within the octave, but " +"may be moved into a different octave to match the new clef, and therefore " +"will play at a new pitch." +msgstr "" +"Alla noter som kommer efter klaven behåller sin tonhöjd inom oktaven, men " +"kan flyttas till en annan oktav för att passa med den nya klaven, och " +"spelas därför med annan tonhöjd." + +#. Tag: para +#: index.docbook:3064 +#, no-c-format +msgid "" +"For example, inserting a tenor clef in the middle of a previously " +"treble-clef section will cause the notes following the clef to move by one " +"staff line only to adjust to the new clef, but to play an octave lower than " +"before." +msgstr "" +"Genom att till exempel infoga en c-klav i mitten av ett avsnitt med en " +"tidigare g-klav gör att noterna som kommer efter klaven bara att flyttas en " +"linje i notsystemet för att justeras enligt den nya klaven, men spelas en " +"oktav lägre än tidigare." + +#. Tag: title +#: index.docbook:3080 +#, no-c-format +msgid "<title>Key</title>" +msgstr "<title>Tonart</title>" + +#. Tag: phrase +#: index.docbook:3088 +#, no-c-format +msgid "&rosegarden;'s key signature dialog" +msgstr "&rosegarden;s dialogruta för fasta förtecken" + +#. Tag: title +#: index.docbook:3100 +#, no-c-format +msgid "Text and lyrics" +msgstr "Text och sångtexter" + +#. Tag: para +#: index.docbook:3102 +#, no-c-format +msgid "" +"A staff can contain various sorts of text, in text events. There are two " +"basic classes of text event: single text items used for point annotations " +"etc., and lyrics. The former can be created (and so associated with a " +"particular time in the staff) using the Text tool, which is available on the " +"button marked with a big <guilabel>T</guilabel> in the toolbar. Lyrics can " +"also be created this way, but are more easily created using the <link " +"linkend=\"nv-text-lyrics\">lyric editor</link>." +msgstr "" +"Ett notsystem kan innehålla olika sorters text, i texthändelser. Det finns " +"två grundläggande klasser med texthändelser: Enstaka textobjekt som " +"används för punktnoteringar etc., och sångtexter. De förstnämnda kan " +"skapas (och på så sätt kopplas till en viss tid i notsystemet) med " +"textverktyget, som är tillgängligt från knappen markerad med ett stort " +"<guilabel>T</guilabel> i verktygsraden. Sångtext kan också skapas på " +"detta sätt, men skapas enklare med <link " +"linkend=\"nv-text-lyrics\">sångtexteditorn</link>." + +#. Tag: para +#: index.docbook:3111 +#, no-c-format +msgid "" +"To add a piece of text, select the Text tool and click at the point where " +"you want to add it. A dialog box will appear, into which you can type the " +"text and choose its intended purpose. (Rosegarden prefers to store what the " +"text is for, rather than how it should look; this is so that in future we " +"may be able to configure how the various sorts of text are presented for " +"each individual user.) The available purposes (or styles) are:" +msgstr "" +"För att lägga till ett textstycke, välj textverktyget och klicka på " +"stället där du vill lägga till den. En dialogruta visas, där du kan " +"skriva in texten och välja dess tänkta syfte. (Rosegarden föredrar att " +"lagra vad texten är till för, istället för hur. Det görs så att vi i " +"framtiden kan ställa in hur diverse textsorter presenteras för varje " +"individuell användare). Tillgängliga syften (eller stilar) är:" + +#. Tag: term +#: index.docbook:3122 +#, no-c-format +msgid "Dynamic" +msgstr "Dynamik" + +#. Tag: para +#: index.docbook:3122 +#, no-c-format +msgid "" +"Used for minor local indications such as the dynamic marks \"p\", \"mf\" " +"etc. Shown below the staff in small italic type by default." +msgstr "" +"Används för mindre lokala föredragsbeteckningar som dynamikbeteckningarna " +"\"p\", \"mf\" etc. Visas normalt under notsystemet med liten kursiv stil." + +#. Tag: term +#: index.docbook:3127 +#, no-c-format +msgid "Direction" +msgstr "Anvisning" + +#. Tag: para +#: index.docbook:3127 +#, no-c-format +msgid "" +"Used when indicating significant changes in style or mood. Shown above the " +"staff in large roman type by default." +msgstr "" +"Används för att ange väsentliga ändringar i stil eller stämning. Visas " +"normalt ovanför notsystemet med stort romerskt teckensnitt." + +#. Tag: term +#: index.docbook:3132 +#, no-c-format +msgid "Local Direction" +msgstr "Lokal anvisning" + +#. Tag: para +#: index.docbook:3132 +#, no-c-format +msgid "" +"Used to indicate less significant changes in style or mood. Shown below the " +"staff in a smaller bold-italic roman type by default." +msgstr "" +"Används för att ange mindre väsentliga ändringar i stil eller stämning. " +"Visas normalt under notsystemet med mindre romerskt teckensnitt i fetstil." + +#. Tag: term +#: index.docbook:3137 +#, no-c-format +msgid "<term>Tempo</term>" +msgstr "<term>Tempo</term>" + +#. Tag: para +#: index.docbook:3137 +#, no-c-format +msgid "" +"Used to indicate significant changes in tempo. Shown above the staff in " +"large bold roman type by default." +msgstr "" +"Används för att ange väsentliga ändringar av tempo. Visas normalt " +"ovanför notsystemet med stort romerskt teckensnitt i fetstil." + +#. Tag: term +#: index.docbook:3142 +#, no-c-format +msgid "Local Tempo" +msgstr "Lokalt tempo" + +#. Tag: para +#: index.docbook:3142 +#, no-c-format +msgid "" +"Used to indicate more minor or local changes in tempo. Shown above the staff " +"in a small bold roman type by default." +msgstr "" +"Används för att ange mindre viktiga eller lokala ändringar av tempo. " +"Visas normalt ovanför notsystemet med litet romerskt teckensnitt i fetstil." + +#. Tag: term +#: index.docbook:3147 +#, no-c-format +msgid "Lyric" +msgstr "Sångtext" + +#. Tag: para +#: index.docbook:3147 +#, no-c-format +msgid "" +"Although lyrics are usually created in the <link " +"linkend=\"nv-text-lyrics\">lyric editor</link>, they can also be entered " +"word by word if necessary using this style. This style is shown below the " +"text in a small roman type by default. (Warning: if you enter lyrics this " +"way and later edit the staff's lyrics using the lyric editor, any lyrics " +"entered this way may be modified or moved if their positioning is not " +"compatible with that expected by the lyric editor.)" +msgstr "" +"Även om sångtext oftast skapas i <link " +"linkend=\"nv-text-lyrics\">sångtexteditorn</link>, kan de också skrivas in " +"ord för ord om det behövs genom att använda den här stilen. Normalt " +"visas stilen under texten med litet romerskt teckensnitt. (Varning: Om du " +"skriver in sångtext på detta sätt och senare redigerar notsystemets " +"sångtext med sångtexteditorn, kan all sångtext som skrivs in på detta " +"sätt ändras eller flyttas om positionen inte stämmer med den som " +"sångtexteditorn förväntar sig.)" + +#. Tag: term +#: index.docbook:3158 +#, no-c-format +msgid "Annotation" +msgstr "Anteckning" + +#. Tag: para +#: index.docbook:3158 +#, no-c-format +msgid "" +"Used for helpful text that is not strictly considered part of the score. " +"Shown below the staff, boxed-out in a yellow sticky-label-style box by " +"default." +msgstr "" +"Används för hjälptext som inte strikt anses tillhöra partituret. Visas " +"normalt under notsystemet, i en gul ruta som liknar en klisterlapp." + +#. Tag: para +#: index.docbook:3166 +#, no-c-format +msgid "" +"You can also edit text after creating it, by clicking on the existing text " +"with the text tool." +msgstr "" +"Du kan också redigera text efter den skapats genom att klicka på den " +"befintliga texten med textverktyget." + +#. Tag: title +#: index.docbook:3170 +#, no-c-format +msgid "Editing lyrics" +msgstr "Redigera sångtexter" + +#. Tag: para +#: index.docbook:3172 +#, no-c-format +msgid "" +"The Lyric editor, available from the <guimenuitem>Open Lyric " +"Editor</guimenuitem> option of the <guimenu>View</guimenu> menu, allows you " +"to edit all of the lyric events for a single staff at once, using a fairly " +"rudimentary textual editing system. To use it, just activate the menu " +"option, edit the lyric text in the resulting dialog, and then hit OK." +msgstr "" +"Sångtexteditorn, tillgänglig från alternativet <guimenuitem>Öppna " +"sångtexteditor</guimenuitem> i menyn <guimenu>Visa</guimenu>, låter dig " +"redigera alla sångtexthändelser för ett enskilt notsystem på en gång, " +"med ett ganska grundläggande textbaserat redigeringssystem. För att " +"använda den, välj bara menyalternativet, redigera sångtexten i " +"dialogrutan som visas, och klicka därefter på Ok." + +#. Tag: para +#: index.docbook:3179 +#, no-c-format +msgid "" +"The lyrics you enter should follow a particular format. Bar lines are vital " +"to avoid the editor getting confused, and are represented with a slash " +"(\"/\"). Within each bar the individual syllables are separated by spaces " +"(at least one space: the editor doesn't care about any extra whitespace). " +"Each syllable in turn will be attached to the next subsequent note or chord " +"within that bar (although at the moment the editor can get quite confused by " +"chords that are not exact, i.e. that require smoothing or quantizing)." +msgstr "" +"Sångtext som du skriver in måste följa ett visst format. Taktstreck är " +"mycket viktiga för att undvika att editorn blir förvirrad, och " +"representeras med ett snedstreck (\"/\"). Inom varje takt skiljs enskilda " +"stavelser åt med mellanslag (åtminstone ett mellanslag: editorn bryr sig " +"inte om extra blanktecken). Varje stavelse kopplas i sin tur till " +"nästföljande not eller ackord i takten (även om editorn för närvarande " +"kan bli riktigt förvirrad av ackord som inte är exakta, dvs. som kräver " +"utjämning eller kvantisering)." + +#. Tag: para +#: index.docbook:3190 +#, no-c-format +msgid "" +"If you want a note to have no syllable attached to it, you need to provide a " +"dot (\".\") as the syllable for that note. (This is why the default lyric " +"text for a segment is usually full of dots.) Remember to separate the dots " +"with spaces, so that they are clearly separate syllables." +msgstr "" +"Om du vill att en not inte ska ha någon tillhörande stavelse, måste du " +"använda en punkt (\".\") som stavelse för noten. (Det är därför " +"standardtexten för ett segment oftast är full med punkter.) Kom ihåg att " +"skilja punkterna åt med mellanslag, så att de tydligt är skilda stavelser." + +#. Tag: para +#: index.docbook:3196 +#, no-c-format +msgid "" +"If you want more than one syllable on the same note, with a space between " +"them, use a tilde (\"~\") instead of the space. It will be shown as a space " +"on the score." +msgstr "" +"Om du vill ha mer än en stavelse för samma not, med ett mellanslag mellan " +"dem, använd tilde (\"~\") istället för mellanslag. Det visas som ett " +"mellanslag i partituret." + +#. Tag: para +#: index.docbook:3200 +#, no-c-format +msgid "" +"If you want to split a syllable across two notes, with a hyphen, you need to " +"enter a space following the hyphen so the editor knows to treat it as two " +"syllables. (Hyphens get no special treatment within syllables.)" +msgstr "" +"Om du vill dela en stavelse mellan två noter med ett bindestreck, måste du " +"skriva in ett mellanslag efter bindestrecket så att editorn vet att det ska " +"behandlas som två stavelser. (Bindestreck hanteras inte speciellt inne i " +"stavelser.)" + +#. Tag: para +#: index.docbook:3205 +#, no-c-format +msgid "" +"Syllables consisting only of numbers surrounded by square brackets (like " +"\"[29]\") will be ignored; this is the format used for the " +"automatically-generated bar numbers shown in the editor." +msgstr "" +"Stavelser som bara består av siffror omgivna av hakparenteser (som " +"\"[29]\") ignoreras. Det är formatet för automatiskt skapade taktnummer " +"som visas i editorn." + +#. Tag: para +#: index.docbook:3210 +#, no-c-format +msgid "" +"You should also be aware that the textual format of lyrics is only used for " +"editing: the lyrics are actually stored as distinct text events (one per " +"syllable). This means that the text format may potentially change in the " +"future to accommodate more advanced editing capabilities, although the event " +"format should not change and so your saved files should continue to be " +"compatible." +msgstr "" +"Du bör också vara medveten om att textformatet för sångtext bara " +"används för redigering: sångtexten lagras i själva verket som distinkta " +"texthändelser (en per stavelse). Det betyder att textformatet potentiellt " +"kan ändras i framtiden för att hantera mer avancerade " +"redigeringsmöjligheter, även om händelseformatet inte bör ändras och " +"sparade filer bör fortsätta att fungera." + +#. Tag: title +#: index.docbook:3225 +#, no-c-format +msgid "Slurs and hairpins" +msgstr "Legatobågar och klykor" + +#. Tag: para +#: index.docbook:3227 +#, no-c-format +msgid "" +"Slur and hairpin dynamic markings are stored as events, just like notes or " +"rests. To create one, select the area you want it to cover (a series of " +"notes or whatever), and then use the <guimenuitem>Add Slur</guimenuitem>, " +"<guimenuitem>Add Crescendo</guimenuitem> or <guimenuitem>Add " +"Decrescendo</guimenuitem> options from the <guimenu>Group</guimenu> menu." +msgstr "" +"Dynamikmarkeringarna legatobågar och klykor lagras som händelser, precis som " +"noter eller pauser. För att skapa en, markera området du vill täcka (en " +"följd av noter eller något annat), och använd därefter alternativen " +"<guimenuitem>Lägg till legatobåge</guimenuitem>, <guimenuitem>Lägg till " +"crescendo</guimenuitem> eller <guimenuitem>Lägg till " +"diminuendo</guimenuitem> i menyn <guimenu>Grupp</guimenu>." + +#. Tag: para +#: index.docbook:3235 +#, no-c-format +msgid "" +"You remove a slur or hairpin in the same way as any other event: either " +"select it with the selection tool and then hit <keycap>Delete</keycap>, or " +"click on it with the erase tool active." +msgstr "" +"Du kan ta bort en legatobåge eller klyka på samma sätt som alla andra " +"händelser: Markera den antingen med markeringsverktyget och tryck därefter " +"på <keycap>Delete</keycap>, eller klicka på den med borttagningsverktyget " +"aktivt." + +#. Tag: title +#: index.docbook:3244 +#, no-c-format +msgid "Note stems and slashes" +msgstr "Notskaft och tvärbalkar" + +#. Tag: para +#: index.docbook:3246 +#, no-c-format +msgid "" +"You can set the stem direction of any selected notes (provided they are a " +"sort that have stems) using the three Stem Direction options on the Notes " +"menu. The options allow you to either fix the stems up or down, or revert to " +"the stem direction that &rosegarden; would otherwise have chosen. See also " +"<link linkend=\"nv-beamed-groups\">Beams</link>." +msgstr "" +"Du kan ställa in skaftriktningen på alla markerade noter (under " +"förutsättning att de är av en sort som har skaft) med de tre " +"skaftriktningsalternativen i menyn Noter. Alternativen låter dig antingen " +"låsa skaften uppåt eller neråt, eller återgå till skaftriktningen som " +"&rosegarden; annars skulle ha valt. Se också <link " +"linkend=\"nv-beamed-groups\">Balkar</link>." + +#. Tag: para +#: index.docbook:3253 +#, no-c-format +msgid "" +"The <guimenu>Notes</guimenu> menu also contains options for adding slashes " +"across note stems, for example to indicate short repeated notes or drum " +"rolls. These are currently purely notational; &rosegarden; will not take " +"them into account when playing the staff or generating &MIDI;." +msgstr "" +"Menyn <guimenu>Noter</guimenu> innehåller också alternativ för att lägga " +"till tvärbalkar på notskaft, för att till exempel ange korta upprepade " +"noter eller trumvirvlar. De är för närvarande bara notation. &rosegarden; " +"tar inte hänsyn till dem när notsystemet spelas upp eller när &MIDI; " +"skapas." + +#. Tag: title +#: index.docbook:3263 +#, no-c-format +msgid "Beams" +msgstr "Balkar" + +#. Tag: para +#: index.docbook:3265 +#, no-c-format +msgid "" +"Adding beams to notes is considered a grouping operation in the &rosegarden; " +"Notation editor, available on the <guimenu>Group</guimenu> menu. Select the " +"notes you want to beam, and use the Beam <guimenu>Group</guimenu> menu " +"option. To remove a beam, select the notes and use the " +"<guimenuitem>Unbeam</guimenuitem> menu option." +msgstr "" +"Att lägga till balkar till noter anses som en grupperingsåtgärd i " +"&rosegarden;s notbehandlare, tillgänglig i menyn " +"<guimenu>Grupp</guimenu>. Markera noterna du vill lägga till en balk för, " +"och använd menyalternativet Balkar i menyn <guimenu>Grupp</guimenu>. För " +"att ta bort en balk, markera noterna och använd menyalternativet " +"<guimenuitem>Ta bort balkar</guimenuitem>." + +#. Tag: para +#: index.docbook:3271 +#, no-c-format +msgid "" +"It is possible to have more than one beamed group happening at the same time " +"— you just select and beam the separate groups one at a time — " +"but Rosegarden is usually not yet clever enough to work out which notes " +"should have stems up and which should have stems down for simultaneous " +"beamed groups, so you will probably have to set the stem directions of the " +"notes in the groups explicitly as well as beaming them." +msgstr "" +"Det är möjligt att ha mer än en balkgrupp som inträffar samtidigt. Du " +"markerar och lägger bara till balkar för enskilda grupper en åt gången. " +"Oftast är Rosegarden inte ännu smart nog för att räkna ut vilka noter " +"som bör ha skaften uppåt och vilka som bör ha skaften neråt för grupper " +"som samtidigt ges balkar, alltså behöver du troligen explicit ange " +"skaftriktningar för noter i grupperna samt ge dem balkar." + +#. Tag: para +#: index.docbook:3279 +#, no-c-format +msgid "" +"&rosegarden; can attempt to guess a sensible beaming for a piece of music, " +"provided it's not too complicated. To invoke this, select the notes you want " +"to calculate the beaming for (for example by triple-clicking to select a " +"whole staff) and then use the <guimenuitem>Auto-Beam</guimenuitem> option on " +"the <guimenu>Group menu</guimenu>. Auto-beaming is also done automatically " +"when loading a &MIDI; file, for example, and the editor also does some " +"automatic beaming as you enter notes (this can be disabled by changing the " +"\"Auto-Beam when appropriate\" setting on the configuration dialog or the " +"insertion tool's right-button menu)." +msgstr "" +"&rosegarden; kan försöka att gissa lämpliga balkar för ett musikstycke, " +"under förutsättning att det inte är alltför komplicerat. För att göra " +"det, markera noterna du vill beräkna balkar för (till exempel genom att " +"trippelklicka för att markera ett helt notsystem) och därefter använda " +"alternativet <guimenuitem>Automatiska balkar</guimenuitem> i menyn " +"<guimenu>Grupp</guimenu>. Balkar skapas också automatiskt till exempel när " +"en &MIDI;-fil laddas, och editorn skapar också vissa balkar automatiskt " +"när du skriver in noter (det kan stängas av genom att ändra " +"inställningen \"Lägg automatiskt till balkar om lämpligt\" i " +"inställningsdialogrutan eller infogningsverktygets meny som visas med " +"höger musknapp)." + +#. Tag: title +#: index.docbook:3296 +#, no-c-format +msgid "Triplets and other tuplets" +msgstr "Trioler och andra annandelningar" + +#. Tag: para +#: index.docbook:3298 +#, no-c-format +msgid "" +"A triplet group consists of three notes or chords played in the time of two. " +"(More precisely, it consists of notes with a total duration of three " +"arbitrary units played in the time of two of those units.)" +msgstr "" +"En triolgrupp består av tre toner eller ackord som spelas under samma tid " +"som två. (Mer exakt består den av toner med ett totalt notvärde av tre " +"godtyckliga enheter, som spelas under samma tid som två av enheterna.)" + +#. Tag: para +#: index.docbook:3303 +#, no-c-format +msgid "" +"We use the word <quote>tuplet</quote> to describe the general situation in " +"which notes with a total duration of any given number of units are played in " +"the time of a different number of those units: nine notes in the time of " +"eight, or six in the time of four, or a crotchet and a quaver in the time of " +"a single crotchet, or even two notes in the time of three. (At present " +"&rosegarden; does not support the last example — tuplet groups must " +"always be played with a shorter duration than written.)" +msgstr "" +"Vi använder ordet <quote>annandelning</quote> för att beskriva det allmänna " +"fallet då toner med ett totalt notvärde av ett givet antal enheter, spelas " +"under en tid som anges av ett annat antal av enheterna: Nio toner under " +"tiden för åtta, eller sex under tiden för fyra, eller en fjärdedelsnot " +"och en åttondedelsnot under tiden för en enda fjärdedelsnot, eller till och " +"med två toner under tiden för tre. (För närvarande stöder inte " +"&rosegarden; det sista exemplet. Annandelningar måste alltid spelas med ett " +"kortare notvärde än det skrivna.)" + +#. Tag: para +#: index.docbook:3313 +#, no-c-format +msgid "" +"The triplet and tuplet menu functions work by taking an existing series of " +"notes or rests and squashing them so they play quicker, filling in the " +"left-over space at the end of the series with a final rest and drawing the " +"whole as a tuplet group. You can therefore create a new series of triplets " +"by entering the first two notes of the series (in their normal form), making " +"them into triplets, and then filling in the rest left over by the triplet " +"operation with the final note of the triplet. Or you can apply the triplet " +"operation before you enter any notes, thus turning the original rest itself " +"into triplet form, and then insert the notes of the triplet on top of it. " +"Some examples may help:" +msgstr "" +"Menyfunktionerna för trioler och annandelningar fungerar genom att ta en " +"befintlig följd av noter eller pauser och trycka ihop dem så att de spelas " +"upp snabbare, och fylla i överblivet utrymme efter följden med en slutgiltig " +"paus och rita upp det hela som en annandelning. Därför kan du skapa en ny " +"följd av trioler genom att mata in de första två noterna i följden (med " +"normal form), göra dem till trioler, och därefter fylla i utrymmet som " +"blivit kvar efter triolåtgärden med den sista noten i triolen. Eller kan " +"du utföra triolåtgärden innan du matar in några noter, och på så sätt " +"omvandla den ursprungliga pausen till triolform, och därefter infoga " +"triolens noter ovanpå den. Några exempel kan vara till hjälp:" + +#. Tag: phrase +#: index.docbook:3337 +#, no-c-format +msgid "&rosegarden;'s general tuplet dialog" +msgstr "&rosegarden;s allmänna dialogruta för annandelningar" + +#. Tag: para +#: index.docbook:3343 +#, no-c-format +msgid "" +"To specify a general tuplet group, we need to know what the base note is " +"(for example, if we play three crotchets in the time of two then the base is " +"a crotchet) and the ratio of the number of base notes written to the number " +"played." +msgstr "" +"För att ange en allmän annandelning, måste man känna till vad grundnoten " +"är (om man till exempel spelar tre fjärdedelsnoter under tiden för två " +"är grundnoten en fjärdedelsnot) och förhållandet mellan antalet " +"grundnoter som skrivs till antalet som spelas." + +#. Tag: title +#: index.docbook:3357 +#, no-c-format +msgid "Paste types" +msgstr "Inklistringstyper" + +#. Tag: para +#: index.docbook:3359 +#, no-c-format +msgid "" +"The meaning of <quote>cut and paste</quote> is less obvious for a music " +"editing program than it is for something like a word processor in which the " +"letters and words go in a simple linear order. Accordingly, &rosegarden;'s " +"Notation editor offers several different types of Paste operation, as well " +"as separate Cut and Cut and Close functions." +msgstr "" +"Betydelsen av <quote>klipp ut och klistra in</quote> är inte så uppenbar " +"för musikredigeringsprogram som den är för något som en ordbehandlare, " +"där bokstäverna och orden anges i en enkel linjär ordning. I enlighet med " +"det erbjuder &rosegarden;s notbehandlare flera olika typer av " +"inklistringsåtgärder, samt separata funktioner för Klipp ut eller Klipp " +"ut och stäng." + +#. Tag: phrase +#: index.docbook:3376 +#, no-c-format +msgid "&rosegarden;'s paste-type dialog" +msgstr "&rosegarden;s inklistringstypdialogruta" + +#. Tag: para +#: index.docbook:3378 +#, no-c-format +msgid "The types of Paste operation are:" +msgstr "Typerna av inklistringsåtgärder är:" + +#. Tag: term +#: index.docbook:3386 +#, no-c-format +msgid "Restricted" +msgstr "Begränsat" + +#. Tag: para +#: index.docbook:3388 +#, no-c-format +msgid "" +"Requires an existing gap (containing nothing but rests) of enough duration " +"to completely contain the clipboard's contents. The contents are pasted into " +"the gap. If there is no gap long enough, the paste is not carried out." +msgstr "" +"Kräver ett befintligt gap (som inte innehåller något annat än pauser) " +"med tillräckligt notvärde för att helt omfatta klippbordets innehåll. " +"Innehållet klistras in i gapet. Om det inte finns ett gap som är långt " +"nog, utförs inte inklistringen." + +#. Tag: para +#: index.docbook:3394 +#, no-c-format +msgid "This is the default paste type." +msgstr "Det här är förvald inklistringstyp." + +#. Tag: term +#: index.docbook:3401 +#, no-c-format +msgid "Simple" +msgstr "Enkel" + +#. Tag: para +#: index.docbook:3403 +#, no-c-format +msgid "" +"Erases enough events to make a gap long enough to paste into, and then " +"pastes into that. The pasted events therefore completely replace any " +"existing ones in the time covered by the paste." +msgstr "" +"Raderar tillräckligt med händelser för att skapa ett gap som är långt " +"nog att klistra in i, och klistrar därefter in i det. De inklistrade " +"händelserna ersätter därför fullständigt alla eventuella befintliga i " +"tiden som täcks av inklistringen." + +#. Tag: term +#: index.docbook:3412 +#, no-c-format +msgid "Open and Paste" +msgstr "Öppna och klistra in" + +#. Tag: para +#: index.docbook:3414 +#, no-c-format +msgid "" +"The opposite of Cut and Close. Makes room for the paste by moving all of the " +"subsequent events further towards the end of the composition." +msgstr "" +"Motsatsen till Klipp ut och stäng. Gör rum för det som ska klistras in " +"genom att flytta alla efterföljande händelser längre mot kompositionens " +"slut." + +#. Tag: term +#: index.docbook:3423 +#, no-c-format +msgid "Note Overlay" +msgstr "Överlagring av noter" + +#. Tag: para +#: index.docbook:3425 +#, no-c-format +msgid "" +"Carries out a paste in the way that it would happen if you entered each of " +"the notes in the clipboard yourself using the notation editor: if there are " +"other notes overlapping with them, the new or existing notes will be split " +"into ties appropriately." +msgstr "" +"Utför en inklistring på samma sätt som skulle ske om du skrev in var och " +"en av noterna på klippbordet själv med notbehandlaren: Om det finns " +"andra noter som överlappar med dem, delas nya och befintliga noter i " +"lämpliga bindebågar." + +#. Tag: term +#: index.docbook:3435 +#, no-c-format +msgid "Matrix Overlay" +msgstr "Matrisöverlagring" + +#. Tag: para +#: index.docbook:3437 +#, no-c-format +msgid "" +"Carries out a paste in the way that it would happen if you entered each of " +"the notes in the clipboard yourself using the matrix editor: the notes " +"presently in the way of the paste will be ignored, allowing the new notes to " +"overlap arbitrarily with them." +msgstr "" +"Utför en inklistring på samma sätt som skulle ske om du skrev in var och " +"en av noterna på klippbordet själv med matriseditorn: Noterna som för " +"närvarande är ivägen för inklistringen ignoreras, och de nya noterna " +"får överlappa godtyckligt med dem." + +#. Tag: para +#: index.docbook:3448 +#, no-c-format +msgid "" +"All of these take effect at the current position of the insert cursor on the " +"current staff. To choose between the various paste types, use the Paste... " +"menu option (with dots) on the Edit menu." +msgstr "" +"Alla dessa får effekt på infogningsmarkörens aktuella position i aktuellt " +"notsystem. För att välja mellan de olika typerna av inklistring, använd " +"menyalternativet Klistra in... (med punkter) i menyn Redigera." + +#. Tag: title +#: index.docbook:3457 +#, no-c-format +msgid "Adjusting Notation" +msgstr "Justera notering" + +#. Tag: title +#: index.docbook:3461 +#, no-c-format +msgid "Adjusting note and rest durations" +msgstr "Justera not- och pausvärden" + +#. Tag: title +#: index.docbook:3464 +#, no-c-format +msgid "Normalizing Rests" +msgstr "Normalisera pauser" + +#. Tag: para +#: index.docbook:3466 +#, no-c-format +msgid "" +"Sometimes as a result of editing or quantization operations, a piece of " +"notation can end up with incorrect rest durations for the current time " +"signature. You can use the <guimenuitem>Normalize Rests</guimenuitem> " +"function to fix these. This function examines each sequence of consecutive " +"rests found in the selection, and adjusts, splits and merges rests as " +"necessary to ensure that the rests have theoretically correct durations and " +"fall on the correct boundaries." +msgstr "" +"Ibland kan ett notavsnitt råka ut för felaktiga pausvärden för " +"aktuell taktart, som ett resultat av redigering eller " +"kvantiseringsåtgärder. Du kan använda funktionen <guimenuitem>Normalisera " +"pauser</guimenuitem> för att fixa dem. Funktionen undersöker varje sekvens " +"av pauser i en följd som hittas i markeringen och justerar, delar och " +"lägger ihop pauser enligt vad som är nödvändigt för att försäkra att " +"pauserna har rätt teoretiskt pausvärde och hamnar på rätt gränser." + +#. Tag: para +#: index.docbook:3477 +#, no-c-format +msgid "" +"For example, a 4/4 bar containing a crotchet (quarter-note), then a minim " +"(half-note) rest and a crotchet rest will be rearranged to place the " +"crotchet rest first, as the minim rest should not cross the central beat " +"boundary of the bar." +msgstr "" +"Om en 4/4-takt innehåller en fjärdedelsnot, arrangeras en halvnotspaus och " +"en fjärdedelspaus om så att fjärdedelspausen placeras först, eftersom " +"halvnotspausen inte ska överlappa den centrala taktgränsen i takten." + +#. Tag: title +#: index.docbook:3560 +#, no-c-format +msgid "Interpreting Performance Cues in Notation" +msgstr "Tolka utförandeantydningar i notskrift" + +#. Tag: para +#: index.docbook:3562 +#, no-c-format +msgid "" +"You can use the Interpret function to modify the velocities and timings of " +"notes according to any written or indicated dynamics found. The selection of " +"interpretations available is as follows:" +msgstr "" +"Du kan använda tolkningsfunktionen för att ändra ljudstyrkor och tider " +"för toner enligt eventuell skriven eller angiven dynamik som hittas. " +"Tillgängliga val av tolkningar är följande:" + +#. Tag: term +#: index.docbook:3570 +#, no-c-format +msgid "Apply text dynamics (p, mf, ff etc)" +msgstr "Tillämpa dynamikbeteckningar (p, mf, ff, etc.)" + +#. Tag: para +#: index.docbook:3572 +#, no-c-format +msgid "" +"Sets a velocity to each note based on the last piece of text of \"Dynamic\" " +"type seen on the same staff (only texts of the form pp, p, mp, mf, f, ff, " +"fff etc are matched)." +msgstr "" +"Anger en ljudstyrka för varje not baserat på senaste texten av typen " +"\"Dynamik\" som observerats i samma notsystem (bara text på formen pp, p, " +"mp, mf, f, ff, fff etc känns igen)." + +#. Tag: term +#: index.docbook:3580 +#, no-c-format +msgid "Apply hairpin dynamics" +msgstr "Använd dynamikklykor" + +#. Tag: para +#: index.docbook:3582 +#, no-c-format +msgid "" +"Makes the notes gradually increase or decrease in velocity during a " +"crescendo or decrescendo hairpin." +msgstr "" +"Gör att noterna gradvis ökar eller minskar ljudstyrka under en klyka som " +"anger crescendo eller diminuendo." + +#. Tag: term +#: index.docbook:3589 +#, no-c-format +msgid "Stress beats" +msgstr "Betona taktslag" + +#. Tag: para +#: index.docbook:3592 +#, no-c-format +msgid "" +"Makes notes that land on bar or beat boundaries slightly louder (greater " +"velocity) than the surrounding notes." +msgstr "" +"Gör noter som hamnar på takt- eller taktslagsgränser något starkare " +"(större ljudstyrka) än omgivande noter." + +#. Tag: term +#: index.docbook:3599 +#, no-c-format +msgid "Articulate slurs, staccato, tenuto etc" +msgstr "Artikulationsbeteckningar" + +#. Tag: para +#: index.docbook:3602 +#, no-c-format +msgid "" +"Shortens unslurred notes, shortens staccato notes more, and gives notes " +"inside slurs and tenuto notes their full length." +msgstr "" +"Avkortar noter utan legatobågar, avkortar staccato-noter ännu mer, och ger " +"noter inne i legatobågar och tenuto-noter sina fulla notvärden." + +#. Tag: title +#: index.docbook:3616 +#, no-c-format +msgid "Notation from performance data" +msgstr "Notskrift från utförandedata" + +#. Tag: para +#: index.docbook:3618 +#, no-c-format +msgid "" +"&rosegarden; is a multi-purpose program: it is a notation editor, but it is " +"primarily a sequencer and editor for performed music. And in performance, of " +"course, the times and durations of notes are rarely as precise as they are " +"on a printed score." +msgstr "" +"&rosegarden; är ett program med flera användningsområden: Det är en " +"notbehandlare, men det är i huvudsak en musikbehandlare och editor för " +"utförd musik, och i utföranden är tonernas tider och notvärden " +"naturligtvis sällan så precisa som de är i ett tryckt partitur." + +#. Tag: para +#: index.docbook:3626 +#, no-c-format +msgid "" +"This means that it's often desirable for &rosegarden; to do a lot of tidying " +"of the basic note times and durations when attempting to make meaningful " +"notes to show in the notation editor. This is a kind of quantization, but a " +"kind that requires a surprising amount of guesswork to do well. &rosegarden; " +"includes a quantizer designed to do a slightly better job of this than the " +"plain grid quantizer." +msgstr "" +"Det betyder att det ofta är önskvärt för &rosegarden; att göra en hel " +"del uppstädning av grundläggande nottider och notvärden vid försök att " +"skapa meningsfulla noter att visa i notbehandlaren. Det är en sorts " +"kvantisering, men en sort som kräver en förvånansvärd mängd gissningar " +"för att göras bra. Det ingår en kvantisering i &rosegarden; som är " +"konstruerad för att göra ett något bättre jobb än den enkla " +"rutnätskvantiseringen." + +#. Tag: para +#: index.docbook:3636 +#, no-c-format +msgid "" +"Applying quantization strictly for notation is rather unimaginatively " +"referred to as <quote>notation quantization</quote>: it only applies to the " +"notes you see and edit in notation, and doesn't affect the notes that play, " +"or that you edit in other views such as the matrix. This quantization is " +"automatically applied to music imported or recorded from MIDI, although not " +"all of its possible capabilities are enabled by default." +msgstr "" +"Att använda kvantisering enbart för notskrift kallas ganska fantasilöst " +"för <quote>kvantisering</quote>: Den gäller bara noterna du ser " +"och redigerar i notskrift, och påverkar inte tonerna som spelas, eller det " +"du redigerar i andra vyer som matrisvyn. Kvantiseringen utförs automatiskt " +"för musik som importeras eller spelas in från MIDI, även om inte alla " +"dess möjliga funktioner normalt är aktiverade." + +#. Tag: para +#: index.docbook:3647 +#, no-c-format +msgid "" +"There are two ways to see which notes have been quantized for notation. By " +"default, each notation view contains a Raw Note Ruler (in the group of " +"rulers above the score) showing a rectangular block for each note. This " +"block is positioned so as to represent the time and duration of the note as " +"performed, but with the top and bottom edges of the rectangle extended or " +"shortened to represent the time after notation quantization. If this is too " +"much information for you, you can alternatively choose (in the configuration " +"dialog) to show in a green colour all note heads in the score that have had " +"their timings altered by notation quantization." +msgstr "" +"Det finns två sätt att se vilka noter som har kvantiserats för notskrift. " +"Normalt innehåller varje notvy en linjal för obehandlade noter (i " +"gruppen med linjaler ovanför partituret) som visar ett rektangulärt block " +"för varje not. Blocket är placerat så att det representerar tiden och " +"notvärdet för noten som utfördes, men med rektangelns övre och nedre " +"kant utökade eller avkortade för att representera tiden efter " +"kvantisering. Om det är för mycket information för dig, kan du " +"som ett alternativ välja (i inställningsdialogrutan) att visa alla " +"nothuvuden i partituret som har ändrade tider efter kvantisering " +"med grön färg." + +#. Tag: phrase +#: index.docbook:3670 +#, no-c-format +msgid "&rosegarden;'s notation quantize dialog" +msgstr "&rosegarden;s kvantiseringsdialogruta" + +#. Tag: para +#: index.docbook:3674 +#, no-c-format +msgid "" +"If the quantization &rosegarden; has used is not suitable, either for the " +"entire score or for a selection of notes, you can choose to use a different " +"level of quantization or none at all. To apply a different quantization to " +"some notes, select the notes and use the Quantize... menu function (tick the " +"box labelled <quote>Quantize for notation only</quote>). The quantization " +"level or type used by default can be changed in the configuration dialog." +msgstr "" +"Om kvantiseringen &rosegarden; har använt inte är lämplig, antingen för " +"hela partituret eller för ett antal markerade noter, kan du välja att " +"använda en annan kvantiseringsnivå eller ingen alls. För att använda en " +"annan kvantisering för vissa noter, markera noterna och använd " +"menyfunktionen Kvantisera... (markera rutan som heter <quote>Kvantisera bara " +"för notskrift</quote>). Kvantiseringsnivån som normalt används kan " +"ändras i inställningsdialogrutan." + +#. Tag: title +#: index.docbook:3686 +#, no-c-format +msgid "Configurable parameters for the heuristic notation quantizer" +msgstr "Inställningsbara parametrar för den heuristiska kvantiseringen" + +#. Tag: title +#: index.docbook:3689 +#, no-c-format +msgid "Parameters for quantization itself" +msgstr "Parametrar för själva kvantiseringen" + +#. Tag: term +#: index.docbook:3694 +#, no-c-format +msgid "Complexity" +msgstr "Komplexitet" + +#. Tag: para +#: index.docbook:3696 +#, no-c-format +msgid "" +"The \"complexity\" of a notation quantizer is its most fundamental " +"parameter. A \"complex\" quantizer will be more prepared to accept that " +"complex-looking music is in fact intended to be complex, whereas a " +"\"simple\" quantizer is more likely to assume that complex-looking music " +"results from an imprecise performance of simple music." +msgstr "" +"Kvantiseringens \"komplexitet\" är dess mest grundläggande " +"parameter. En \"komplex\" kvantisering är mer redo att acceptera att musik " +"som ser komplex ut i själva verket är avsedd att vara komplex, medan en " +"\"enkel\" kvantisering är mer redo att anta att musik som ser komplex ut " +"orsakas av ett mindre precist utförande av enkel musik." + +#. Tag: para +#: index.docbook:3704 +#, no-c-format +msgid "" +"The default setting is intended to produce reasonable results for a fairly " +"wide range of music." +msgstr "" +"Standardinställningarna är avsedda att skapa rimliga resultat för ett " +"ganska brett musikspektrum." + +#. Tag: para +#: index.docbook:3713 +#, no-c-format +msgid "" +"The base grid unit (set to a note duration value) specifies the absolute " +"minimum unit of note that will be permitted to remain in the score after " +"quantization. For example, if set to a semiquaver, all notes will be placed " +"on boundaries of a multiple of a semiquaver, with durations also a multiple " +"of a semiquaver." +msgstr "" +"Den grundläggande rutnätsenheten (inställd till ett notvärde) " +"anger den absolut minsta notenheten som tillåts bli kvar i partituret efter " +"kvantisering. Om den till exempel är inställd till en sextondedelsnot, " +"placeras alla noter på gränser som är en multipel av sextondedelsnoter, och " +"notvärdena är också multiplar av sextondedelsnoter." + +#. Tag: para +#: index.docbook:3721 +#, no-c-format +msgid "" +"The setting of the base grid unit is not quite as significant for a notation " +"quantizer as it is for a plain grid quantizer, because all it does is impose " +"an absolute limit on the level of precision permitted by the complexity " +"parameter. Mostly, when you find a case in which increasing the grid unit " +"produces better results, you've actually found a case in which the quantizer " +"simply didn't do as good a job as it should have been able to with the " +"smaller unit." +msgstr "" +"Basrutnätsenhetens Inställning är inte riktigt så viktig för " +"kvantisering som den är för den vanliga rutnätskvantiseringen, " +"eftersom allt den gör är att lägga en absolut gräns på precisionsnivån " +"som tillåts av komplexitetsparametern. Oftast när du hittar ett fall där " +"bättre resultat uppnås genom att öka rutnätsenheten, har du i själva " +"verket hittat ett fall där kvantiseringen helt enkelt inte gjorde ett så " +"bra jobb som den skulle ha kunnat göra med den mindre enheten." + +#. Tag: term +#: index.docbook:3735 +#, no-c-format +msgid "Tuplet level" +msgstr "Annandelningsnivå" + +#. Tag: para +#: index.docbook:3737 +#, no-c-format +msgid "" +"The notation quantizer is capable of identifying tuplets (triplets and other " +"time-squashed groups), within reasonable limits. This parameter controls how " +"ambitious it will attempt to be when looking for tuplets, by setting a limit " +"on how many notes per tuplet group it will attempt to identify. If it is set " +"to <quote>None</quote>, the quantizer will not attempt to identify tuplets " +"at all." +msgstr "" +"Kvantiseringen klarar av att identifiera annandelningar (trioler och andra " +"tidskomprimerade grupper), inom rimliga gränser. Parametern styr hur " +"ambitiös den försöker vara när den letar efter annandelningar, genom att " +"ange en gräns för hur många noter per annandelning som den försöker " +"identifiera. Om den är inställd till <quote>Inget</quote>, försöker inte " +"kvantiseringen identifiera annandelningar överhuvudtaget." + +#. Tag: title +#: index.docbook:3754 +#, no-c-format +msgid "Parameters that control tidying up after quantization" +msgstr "Parametrar som styr uppstädning efter kvantisering" + +#. Tag: term +#: index.docbook:3759 +#, no-c-format +msgid "Re-beam" +msgstr "Lägg till balkar igen" + +#. Tag: para +#: index.docbook:3761 +#, no-c-format +msgid "" +"Causes the notes to be re-beamed into groups appropriately after " +"quantization. This is usually desirable." +msgstr "" +"Gör att noterna placeras in i balkar med grupper som är passande efter " +"kvantiseringen. Det är ofta önskvärt." + +#. Tag: term +#: index.docbook:3770 +#, no-c-format +msgid "Add articulations (staccato, tenuto, slurs)" +msgstr "Lägg till artikulationsbeteckningar" + +#. Tag: para +#: index.docbook:3773 +#, no-c-format +msgid "" +"Causes the quantizer to attempt to identify, based on the durations of " +"individual and consecutive notes, which notes should be notated with " +"staccato marks (for notes that fall significantly short of the following " +"note, but not apparently short enough to merit a rest), tenuto (for notes " +"that almost or just overlap the following note) and slurs (for series of " +"notes that meet or overlap)." +msgstr "" +"Gör att kvantiseringen försöker identifiera vilka noter som ska markeras " +"som staccato, baserat på notvärdet hos individuella noter och noter i följd " +"(för noter som slutar väsentligt tidigare än den efterföljande " +"noten, men uppenbarligen inte tidigt nog för att vara värda en paus), " +"tenuto (för noter som nästan eller precis överlappar följande not) och " +"legatobågar (för följder av noter som möts eller överlappar)." + +#. Tag: term +#: index.docbook:3787 +#, no-c-format +msgid "Tie notes at barlines etc" +msgstr "Bind noter vid taktstreck etc." + +#. Tag: para +#: index.docbook:3789 +#, no-c-format +msgid "" +"Causes any notes that are still found after quantization to overlap barlines " +"or to have durations not exactly expressible with single note heads to be " +"split into multiple notes appropriately, and tied. This has the same effect " +"as applying the \"Tie Notes at Barlines\" function in the notation view." +msgstr "" +"Gör att alla noter som fortfarande finns kvar efter kvantisering och " +"överlappar taktstreck eller som har notvärden som inte kan uttryckas exakt " +"med enstaka nothuvuden att delas upp i flera noter på lämpligt sätt, och " +"bindas. Det får samma effekt som att utföra funktionen \"Bind noter vid " +"taktstreck\" i notvyn." + +#. Tag: para +#: index.docbook:3797 +#, no-c-format +msgid "" +"This parameter is not set by default because it changes the number of note " +"events, which is undesirable when using &rosegarden; partly or principally " +"as a MIDI sequencer." +msgstr "" +"Den här parametern är normalt inte aktiverad, delvis på grund av att den " +"ändrar antalet tonhändelser, vilket är olämpligt när &rosegarden; " +"delvis eller huvudsakligen används som en MIDI-musikbehandlare." + +#. Tag: term +#: index.docbook:3807 +#, no-c-format +msgid "Split-and-tie overlapping chords" +msgstr "Dela och bind ackordnoter med för stora notvärden" + +#. Tag: para +#: index.docbook:3809 +#, no-c-format +msgid "" +"Causes overlapping notes to be split and tied, so as to make strict chords " +"with individual noteheads tied as necessary. This has the same effect as " +"applying the \"Split-and-Tie Overlapping Chords\" function in the notation " +"view." +msgstr "" +"Gör att överlappande noter delas och binds, så att strikta ackord med " +"individuella nothuvuden bundna efter behov skapas. Det får samma effekt som " +"att utföra funktionen \"Dela och bind ackordnoter med för stora notvärden\" " +"i notvyn." + +#. Tag: para +#: index.docbook:3816 +#, no-c-format +msgid "" +"This parameter is not set by default partly because it changes the number of " +"note events, which is undesirable when using &rosegarden; partly or " +"principally as a MIDI sequencer." +msgstr "" +"Den här parametern är normalt inte aktiverad, delvis på grund av att den " +"ändrar antalet tonhändelser, vilket är olämpligt när &rosegarden; " +"delvis eller huvudsakligen används som en MIDI-musikbehandlare." + +#. Tag: title +#: index.docbook:3831 +#, no-c-format +msgid "Note styles" +msgstr "Notstilar" + +#. Tag: para +#: index.docbook:3833 +#, no-c-format +msgid "" +"&rosegarden; also allows you to change various aspects of the way the " +"various types of notes are drawn, such as the choice of note heads, the " +"number of tails, whether notes are filled or unfilled and so on." +msgstr "" +"&rosegarden; låter dig också ändra diverse aspekter av sättet som olika " +"nottyper ritas upp, som val av nothuvuden, antal flaggor, om noter är " +"ifyllda eller inte och så vidare." + +#. Tag: para +#: index.docbook:3840 +#, no-c-format +msgid "" +"A set of standard styles (Classical, Cross, Triangle and Mensural) is " +"provided, and you can change the style used for individual notes by " +"selecting them and then using the Note Style menu options. Each note " +"remembers which style has been chosen for it, and this information is saved " +"as part of the composition. You can also change the default style for new " +"notes using the <guimenuitem>Configure Rosegarden...</guimenuitem> option in " +"the <guimenu>Settings</guimenu> menu." +msgstr "" +"En uppsättning standardstilar (Klassisk, Kors, Triangel och Mensural) " +"tillhandahålls, och du kan ändra stilen som används för enskilda noter " +"genom att markera dem och därefter använda alternativen i menyn Notstil. " +"Varje not kommer ihåg vilken stil som har valts för den, och informationen " +"sparas som en del av kompositionen. Du kan också ändra förvald stil för " +"nya noter genom att använda alternativet <guimenuitem>Anpassa " +"Rosegarden...</guimenuitem> i menyn <guimenu>Inställningar</guimenu>." + +#. Tag: para +#: index.docbook:3852 +#, no-c-format +msgid "" +"It is also possible to create your own note styles by describing them in " +"<acronym>XML</acronym> files. (Even the standard styles are defined this " +"way: the only reason the editor knows that a Classical semiquaver has a " +"tilted oval filled head, a stem, two flags, etc., is that the description in " +"Classical.xml says so.) See <link " +"linkend=\"developers-note-styles\">Customising Rosegarden</link> for more " +"information." +msgstr "" +"Det är också möjligt att skapa dina egna notstilar genom att beskriva dem " +"med <acronym>XML</acronym>-filer. (Till och med standardstilarna är " +"definierade på detta sätt: Den enda orsaken att editorn vet om att en " +"klassisk sextondedelsnot har ett ovalt lutande ifyllt huvud, ett skaft, två " +"flaggor etc., är att beskrivningen i Classical.xml anger det.) Se <link " +"linkend=\"developers-note-styles\">Anpassa Rosegarden</link> för mer " +"information." + +#. Tag: title +#: index.docbook:3865 +#, no-c-format +msgid "Note fonts" +msgstr "Notteckensnitt" + +#. Tag: para +#: index.docbook:3866 +#, no-c-format +msgid "" +"&rosegarden; is supplied with a single scalable notation font, the Feta font " +"developed by the Lilypond project. Feta is an extremely high quality font " +"that should be suitable for nearly all classical work." +msgstr "" +"&rosegarden; levereras med ett enda skalbart notteckensnitt, " +"Feta-teckensnittet utvecklat i Lilypond-projektet. Feta är ett teckensnitt " +"med mycket hög kvalitet som bör vara lämpligt för nästan allt klassiskt " +"arbete." + +#. Tag: para +#: index.docbook:3873 +#, no-c-format +msgid "" +"&rosegarden; also includes support as standard for a number of other " +"notation fonts. You will need to provide the fonts themselves in TrueType " +"(.ttf) or PostScript Type-1 (.pfb, .pfa) format, and you will need the " +"relevant permissions to install them to the same place as &rosegarden; was " +"installed. To install a supported notation font, locate the share directory " +"for the &rosegarden; installation (usually a subdirectory of the KDE desktop " +"installation tree, such as /opt/kde/share/apps/rosegarden). You will find " +"that this directory has a subdirectory called \"fonts\": copy the font files " +"into there, and restart &rosegarden;. If your font is supported, it should " +"now appear on the font menu in the notation editor." +msgstr "" +"&rosegarden; innehåller också stöd som standard för ett antal andra " +"notteckensnitt. Du måste själv tillhandahålla teckensnitten på " +"formaten Truetype (.ttf) eller Postscript Typ-1 (.pfb, .pfa), och du måste " +"ha lämpliga rättigheter för att installera dem på samma plats som " +"&rosegarden; installerades. För att installera ett notteckensnitt " +"som stöds, lokalisera katalogen share för &rosegarden;s installation " +"(oftast en underkatalog till KDE-skrivbordets installationsträd, som " +"/opt/kde/share/apps/rosegarden). Du märker att katalogen har en " +"underkatalog som heter \"fonts\". Kopiera teckensnittsfilerna till den, och " +"starta om &rosegarden;. Om teckensnittet stöds, ska det nu synas i " +"teckensnittsmenyn i notbehandlaren." + +#. Tag: para +#: index.docbook:3887 +#, no-c-format +msgid "" +"Complete or partial support is currently provided for the following fonts: " +"Fughetta, by Blake Hodgetts; Petrucci, the \"original\" Finale font; " +"Maestro, the \"new\" Finale font; Opus, the Sibelius font; Inkpen, the " +"Sibelius jazz font; Sonata from Adobe; Steinberg, from the Cubase sequencer; " +"and Xinfonia. (Most of the above font names are registered trademarks of the " +"respective companies.) THE ROSEGARDEN TEAM MAKES NO REPRESENTATION AS TO THE " +"LEGAL STATUS OF ANY USE OF THESE FONTS WITH ROSEGARDEN. It is your " +"responsibility to ensure you are in compliance with the licence (if any) " +"under which a font was provided to you, before attempting to use it. If you " +"are not sure whether you have the right to use a font, don't: apart from " +"anything else, the standard Feta font is better than most of these anyway." +msgstr "" +"Fullständigt eller delvis stöd tillhandahålls för närvarande för " +"följande teckensnitt: Fughetta, av Blake Hodgetts; Petrucci, det " +"\"ursprungliga\" Finale-teckensnittet; Maestro, det \"nya\" " +"Finale-teckensnittet; Opus, Sibelius teckensnitt; Inkpen, Sibelius jazz-" +"teckensnitt; Sonata från Adobe; Steinberg, från Cubase-musikbehandlaren; " +"och Xinfonia. (De flesta av ovanstående teckensnittsnamn är registrerade " +"varumärken av respektive företag.) ROSEGARDEN-GRUPPEN GER INGA " +"UTFÄSTELSER ANGÅENDE JURIDISK STATUS FÖR ANVÄNDNING AV NÅGOT AV DESSA " +"TECKENSNITT MED ROSEGARDEN. Det är ditt ansvar att försäkra dig om att du " +"följer den licens (om det finns någon) som du erhöll teckensnittet med, " +"innan du försöker använda det. Om du inte är säker på att du har " +"rättighet att använda ett teckensnitt, gör då inte det. Förutom alla " +"andra aspekter, så är det vanliga Feta-teckensnittet ändå bättre än de " +"flesta av dem." + +#. Tag: para +#: index.docbook:3902 +#, no-c-format +msgid "" +"It is also possible to provide new mapping files so as to use new fonts. For " +"some fonts that have similar mappings or metrics to fonts in the above list, " +"this may be as simple as editing the name of the font in the mapping file. " +"See <link linkend=\"developers-note-fonts\">Customising Rosegarden</link> " +"for more information." +msgstr "" +"Det är också möjligt att tillhandahålla nya avbildningsfiler för att " +"använda nya teckensnitt. För vissa teckensnitt som har liknande " +"avbildningar eller mått som teckensnitt i listan ovan, kan det vara så " +"enkelt som att redigera teckensnittets namn i avbildningsfilen. Se <link " +"linkend=\"developers-note-fonts\">Anpassa Rosegarden</link> för mer " +"information." + +#. Tag: title +#: index.docbook:3916 +#, no-c-format +msgid "The Event List editor" +msgstr "Händelselisteditorn" + +#. Tag: para +#: index.docbook:3920 +#, no-c-format +msgid "" +"The &rosegarden; Event List editor shows the events in a single segment in a " +"raw form, and enables you to edit the precise properties of those events " +"individually." +msgstr "" +"&rosegarden;s editor för händelselistan visar händelserna i ett enstaka " +"segment i obehandlad form, och gör det möjligt att redigera de exakta " +"egenskaperna för händelserna individuellt." + +#. Tag: phrase +#: index.docbook:3932 +#, no-c-format +msgid "&rosegarden;'s event list editor" +msgstr "&rosegarden;s händelselisteditor" + +#. Tag: title +#: index.docbook:5702 +#, no-c-format +msgid "Customising Rosegarden" +msgstr "Anpassa Rosegarden" + +#. Tag: title +#: index.docbook:5705 +#, no-c-format +msgid "Configuring custom notation fonts" +msgstr "Anpassa egna notteckensnitt" + +#. Tag: para +#: index.docbook:5707 +#, no-c-format +msgid "" +"If you have a notation font installed on your system in a scalable format " +"(TrueType or Type-1) but it is not currently supported by Rosegarden, you " +"can create your own mapping XML file to describe the font's character map " +"and metrics in a way Rosegarden can use. These files are installed in the " +"fonts/mappings subdirectory of the Rosegarden installation directory, and a " +"number of samples are included with the distribution." +msgstr "" +"Om du har ett notteckensnitt installerat på systemet med ett " +"skalbart format (Truetype eller Typ-1) men den för närvarande inte stöds " +"av Rosegarden, kan du skapa din egen XML-avbildningsfil för att beskriva " +"teckensnittets teckenavbildning och mått på ett sätt som Rosegarden kan " +"använda. Filerna installeras i underkatalogen fonts/mappings i Rosegardens " +"installationskatalog, och ett antal exempel ingår i distributionen." + +#. Tag: para +#: index.docbook:5716 +#, no-c-format +msgid "" +"You can also use these mapping files to define new pixmap-based fonts, in " +"which every shape in a particular size is loaded from a separate pixmap " +"file. The two standard notation fonts supplied with Rosegarden-4 are pixmap " +"fonts defined in exactly this way." +msgstr "" +"Du kan också använda avbildningsfilerna för att definiera nya teckensnitt " +"baserade på punktavbildning, där varje form av en viss storlek laddas " +"från en separat punktavbildningsfil. De två standardteckensnitten för " +"notskrift som levereras med Rosegarden-4 är punktavbildade teckensnitt som " +"definierats exakt på detta sätt." + +#. Tag: para +#: index.docbook:5723 +#, no-c-format +msgid "" +"It is even possible to define a notation font as using one or more scalable " +"system fonts, augmented with pixmaps for particular sizes or for characters " +"not found in the scalable fonts. This is because most of the mapping file " +"format is the same for scalable and pixmap fonts, and where there are " +"different elements for the different sorts of fonts, it is usually possible " +"to include both of them. Rosegarden will usually use pixmaps where available " +"and scalable fonts otherwise." +msgstr "" +"Det är till och med möjligt att definiera ett notteckensnitt att " +"använda en eller flera skalbara systemteckensnitt, förbättrade med " +"punktavbildningar för vissa storlekar eller för tecken som inte finns i de " +"skalbara teckensnitten. Det går eftersom det mesta av avbildningsfilernas " +"format är samma för skalbara och punktavbildade teckensnitt, och när det " +"finns olika element för olika sorters teckensnitt är det oftast möjligt " +"att inkludera båda. Rosegarden använder oftast punktavbildningar om de är " +"tillgängliga, och annars skalbara teckensnitt." + +#. Tag: para +#: index.docbook:5734 +#, no-c-format +msgid "" +"You may also wish to edit the mapping files supplied with Rosegarden if you " +"find their measurements for alignment or sizing are not to your liking. (If " +"you believe that any of the supplied files are actually wrong, please let us " +"know.)" +msgstr "" +"Du kanske också vill redigera avbildningsfilerna som levereras med " +"Rosegarden om du tycker att deras mått för justering eller storlek inte " +"passar dig. (Om du tycker att någon av filerna som levereras är felaktig " +"på något sätt, tala gärna om det för oss.)" + +#. Tag: title +#: index.docbook:5741 +#, no-c-format +msgid "Codes and Glyphs" +msgstr "Koder och glyfer" + +#. Tag: title +#: index.docbook:5747 +#, no-c-format +msgid "Notation font mapping XML format" +msgstr "XML-format för avbildning av notteckensnitt" + +#. Tag: para +#: index.docbook:5749 +#, no-c-format +msgid "" +"Here is a summary of the XML elements that may be used in the font mapping " +"file." +msgstr "" +"Här är en översikt över XML-elementen som kan användas i en " +"teckensnittsavbildningsfil." + +#. Tag: title +#: index.docbook:5753 +#, no-c-format +msgid "rosegarden-font-encoding" +msgstr "rosegarden-font-encoding" + +#. Tag: para +#: index.docbook:5755 +#, no-c-format +msgid "" +"This element must exist in every mapping file, and should contain all the " +"other elements. The only attribute is \"name\", which contains the font's " +"name as shown in the font selection dropdown. Although the file format will " +"permit any name to be used here, Rosegarden will only pick up the font " +"corectly if the XML file has the same name as the contents of this attribute " +"(except that the XML file should be named in lower-case and should end in " +"\".xml\")." +msgstr "" +"Elementet måste finnas i varje avbildningsfil, och ska innehålla alla " +"övriga element. Det enda attributet är \"name\" som innehåller " +"teckensnittets namn som visas i kombinationsrutan för teckensnittsval. " +"Även om filformatet tillåter att vilket namn som helst används här, " +"hittar Rosegarden bara teckensnittet på ett riktigt sätt om XML-filen har " +"samma namn som det här attributets innehåll (utom att XML-filen ska " +"namnges med små bokstäver och ska sluta med \".xml\")." + +#. Tag: title +#: index.docbook:5767 +#, no-c-format +msgid "font-information" +msgstr "font-information" + +#. Tag: para +#: index.docbook:5769 +#, no-c-format +msgid "" +"This should normally be the first child element of " +"\"rosegarden-font-encoding\". It may have any of the following attributes, " +"all of which are optional:" +msgstr "" +"Det här ska normalt vara första delelement i \"rosegarden-font-encoding\". " +"Det kan ha vilket som helst av följande attribut, som alla är valfria:" + +#. Tag: term +#: index.docbook:5775 +#, no-c-format +msgid "origin" +msgstr "origin" + +#. Tag: para +#: index.docbook:5777 +#, no-c-format +msgid "" +"A textual description of the likely origin of the mapped font (not the " +"origin of the mapping file)." +msgstr "" +"En textbeskrivning av det avbildade teckensnittets troliga ursprung (inte " +"ursprunget för avbildningsfilen)." + +#. Tag: term +#: index.docbook:5784 +#, no-c-format +msgid "copyright" +msgstr "copyright" + +#. Tag: para +#: index.docbook:5786 +#, no-c-format +msgid "" +"A textual description of the likely copyright status of the mapped font (not " +"the copyright status of the mapping file). Note that because the mapping " +"file contains information such as origin and copyright of the font itself, " +"it is usually advisable to make separate mapping files for separate fonts " +"where practical, even if the fonts share other mapping data." +msgstr "" +"En textbaserad beskrivning av trolig copyright-status för det avbildade " +"teckensnittet (inte copyright-status för avbildningsfilen). Observera att " +"eftersom avbildningsfilen innehåller information som ursprung och copyright " +"för själva teckensnittet, är det oftast lämpligt att göra separata " +"avbildningsfiler för separata teckensnitt när det är praktiskt, även om " +"teckensnitten delar annan avbildningsdata." + +#. Tag: term +#: index.docbook:5798 +#, no-c-format +msgid "mapped-by" +msgstr "mapped-by" + +#. Tag: para +#: index.docbook:5800 +#, no-c-format +msgid "The name of the creator of the mapping file (i.e. you, presumably)." +msgstr "Namnet på skaparen av avbildningsfilen (dvs. antagligen du själv)." + +#. Tag: term +#: index.docbook:5806 index.docbook:6264 +#, no-c-format +msgid "type" +msgstr "type" + +#. Tag: para +#: index.docbook:5808 +#, no-c-format +msgid "" +"The type of the font. This attribute should contain one of the values " +"\"pixmap\" or \"scalable\". Fonts that are loaded into the windowing system " +"and are available to Rosegarden as standard system fonts have type " +"\"scalable\"; fonts that need to be loaded from pixmap files corresponding " +"to individual sizes of pixmap (such as the feta and rg21 fonts included with " +"Rosegarden) have type \"pixmap\"." +msgstr "" +"Teckensnittets typ. Attributet ska innehålla ett av värdena \"pixmap\" " +"eller \"scalable\". Teckensnitt som laddas i fönsterhanteringssystemet och " +"är tillgängliga för Rosegarden som vanliga systemteckensnitt har typen " +"\"scalable\". Teckensnitt som måste laddas från punktavbildningsfiler som " +"motsvarar individuella storlekar på punktavbildningar (som teckensnitten " +"feta och rg21 som ingår i Rosegarden) har typen \"pixmap\"." + +#. Tag: para +#: index.docbook:5817 +#, no-c-format +msgid "" +"This information is only intended for the user reference; it isn't actually " +"used by Rosegarden. It is legitimate in practice for a font to be a mixture " +"of the two, but in general we will assume in this documentation that a font " +"is either scalable or pixmap." +msgstr "" +"Den här informationen är bara avsett som referens för användaren. Den " +"används i själva verket inte av Rosegarden. I praktiken är det legitimt " +"att ett teckensnitt är en blandning av de två, men i allmänhet antar vi i " +"den här dokumentationen att teckensnittet antingen är skalbart eller " +"punktavbildat." + +#. Tag: term +#: index.docbook:5826 +#, no-c-format +msgid "smooth" +msgstr "smooth" + +#. Tag: para +#: index.docbook:5828 +#, no-c-format +msgid "" +"A boolean attribute indicating whether the font is antialiased (smooth) or " +"not. Should have the value \"true\" or \"false\". If the font is smooth, " +"other display elements such as beams and slurs that are not generated from " +"the font will also be antialiased." +msgstr "" +"Ett Booleanskt attribut som anger om teckensnittet är kantutjämnat eller " +"inte. Ska ha värdet \"true\" eller \"false\". Om teckensnittet är " +"utjämnat, kommer andra element som balkar och legatobågar som inte skapas " +"från teckensnittet att vara kantutjämnade." + +#. Tag: term +#: index.docbook:5838 +#, no-c-format +msgid "autocrop" +msgstr "autocrop" + +#. Tag: para +#: index.docbook:5840 +#, no-c-format +msgid "" +"Only relevant for scalable (system) fonts. Rosegarden usually expects the " +"metrics for a font to contain the vertically smallest bounding boxes for " +"elements such as note heads and accents, rather than including empty space " +"above or below these elements for alignment purposes. Most fonts do not do " +"what Rosegarden expects. Therefore for these fonts you should set the " +"autocrop attribute to \"true\"; then Rosegarden will crop any unnecessary " +"space from the top and bottom of these elements when rendering them." +msgstr "" +"Bara relevant för skalbara (system) teckensnitt. Rosegarden förväntar sig " +"oftast att ett teckensnitts mått innehåller de vertikala minsta omgivande " +"rutor för element som nothuvuden och accenter, istället för att omfatta " +"tomt utrymme ovanför eller under elementen av justeringssyfte. De flesta " +"teckensnitt gör inte vad Rosegarden förväntar sig. Därför ska du " +"ställa in attributet för automatisk beskärning till \"true\". Då beskär " +"Rosegarden allt onödigt tomt utrymme längst upp och längst ner i " +"elementen när de ritas upp." + +#. Tag: title +#: index.docbook:5860 +#, no-c-format +msgid "font-requirements" +msgstr "font-requirements" + +#. Tag: para +#: index.docbook:5861 +#, no-c-format +msgid "" +"This element is only relevant for scalable fonts. It is used to specify that " +"this font should only be offered if certain system fonts are available, as " +"well as to associate IDs with those system fonts to refer to in the <link " +"linkend=\"developers-note-fonts-mapping-format-font-symbol-map\">font-symbol-" +"map</link> element. This scheme is used to decide which notation fonts " +"should be offered to the user, and also allows you to compose a Rosegarden " +"notation font from more than one system font if desired." +msgstr "" +"Det här elementet är bara relevant för skalbara teckensnitt. Det används " +"för att ange att teckensnittet bara ska erbjudas om vissa systemteckensnitt " +"är tillgängliga, samt att koppla identifikationsvärden med " +"systemteckensnitten att kunna hänvisa till i elementet <link " +"linkend=\"developers-note-fonts-mapping-format-font-symbol-map\">font-symbol-" +"map</link>. Den här metoden används för att bestämma vilka " +"notteckensnitt som användaren ska erbjudas, och dessutom låta dig " +"komponera ett notteckensnitt i Rosegarden från mer än ett " +"systemteckensnitt om du önskar." + +#. Tag: para +#: index.docbook:5873 +#, no-c-format +msgid "" +"The \"font-requirements\" element should contain a list of " +"\"font-requirement\" child elements. Each of these has two attributes: " +"\"font-id\", containing a numerical ID of your choice for reference " +"elsewhere in the file, and either a \"name\" or a \"names\" attribute. If " +"\"name\" is provided, it will be used as the name of a single system font to " +"be associated with the font id; if \"names\" is provided, it will be treated " +"as a comma-separated list of system fonts and the first one found will be " +"associated with the font id." +msgstr "" +"Elementet \"font-requirements\" ska innehålla en lista med delelementen " +"\"font-requirement\". Vart och ett av dessa har två attribut: \"font-id\" " +"som innehåller en numerisk identifikation av ditt val för referenser på " +"andra ställe in filen, och antingen attributet \"name\" eller \"names\". Om " +"\"name\" tillhandahålls, används det som namnet på ett enstaka " +"systemteckensnitt som ska höra ihop med teckensnittsidentifikationen. Om " +"\"names\" tillhandahålls behandlas det som en lista av systemteckensnitt " +"åtskilda med kommatecken, där det första som hittas kopplas ihop med " +"teckensnittsidentifikationen." + +#. Tag: title +#: index.docbook:5886 +#, no-c-format +msgid "font-sizes" +msgstr "font-sizes" + +#. Tag: para +#: index.docbook:5888 +#, no-c-format +msgid "" +"The \"font-sizes\" element specifies which notation font sizes are " +"available, and how the nominal font size relates to the dimensions of " +"non-font elements such as stems, staff lines and beams. The \"size\" of a " +"notation font is assumed to be the distance in pixels between staff lines, " +"or more precisely, the height of a conventional note head that completely " +"fills the space between lines: the size therefore does not include the " +"thickness of either of the neighbouring staff lines." +msgstr "" +"Elementet \"font-sizes\" anger vilka storlekar av notteckensnitt som " +"är tillgängliga, och hur den nominella teckenstorleken förhåller sig " +"till storleken på element som inte ingår i teckensnittet, såsom skaft, " +"notsystemlinjer och balkar. Ett notteckensnitts \"storlek\" antas " +"vara avståndet i bildpunkter mellan notsystemlinjer, eller exaktare, " +"platsen för ett vanligt nothuvud som fullständigt fyller avståndet mellan " +"linjer: Storleken omfattar därför inte tjockleken hos någon av " +"intilliggande notlinjer." + +#. Tag: para +#: index.docbook:5899 +#, no-c-format +msgid "" +"There are two possible child elements of \"font-sizes\": \"font-scale\" and " +"\"font-size\". Their use depends on the type of font being described." +msgstr "" +"Det finns två möjliga delelement till \"font-sizes\": \"font-scale\" och " +"\"font-size\". Deras användning beror på typ av teckensnitt som beskrivs." + +#. Tag: para +#: index.docbook:5905 +#, no-c-format +msgid "" +"For pixmap (non-scalable) fonts, the \"font-sizes\" element should contain a " +"list of \"font-size\" elements, one for each size of pixmaps available. The " +"pixmaps themselves must be installed in the " +"fonts/<font-name>/<font-size> subdirectory of the Rosegarden " +"installation directory, where <font-name> is the name of the font (as " +"specified in the \"rosegarden-font-encoding\" element at the start of the " +"mapping file), or a lower-case version of the name, and <font-size> is " +"the pixel size of the font. A font size will only be made available to the " +"user if it has an entry in the \"font-sizes\" list and the pixmap directory " +"is found." +msgstr "" +"För punktavbildade (inte skalbara) teckensnitt, ska elementet " +"\"font-sizes\" innehålla en lista med element \"font-size\", ett för varje " +"storlek av punktavbilder som är tillgängliga. Punktavbilderna själva " +"måste vara installerade i underkatalogen " +"fonts/<font-name>/<font-size> i Rosegardens " +"installationskatalog, där <font-name> är teckensnittets namn (som " +"det anges i elementet \"rosegarden-font-encoding\" i avbildningsfilens " +"början), eller en version av namnet med små bokstäver, och " +"<font-size> är teckensnittets bildpunktsstorlek. En teckenstorlek " +"görs bara tillgänglig för användaren om den har en post i listan " +"\"font-sizes\" och punktavbildningskatalogen hittas." + +#. Tag: para +#: index.docbook:5921 +#, no-c-format +msgid "" +"For scalable fonts, the \"font-sizes\" element should contain one " +"\"font-scale\" element that defines the relationships between font and " +"non-font elements in a general way, and also defines the relationship " +"between Rosegarden's nominal font size and the size of the corresponding " +"system font. If this \"font-scale\" element is found, then Rosegarden will " +"assume the font is available in any size. You can however still include one " +"or more \"font-size\" elements to define precise proportions for any " +"particular size for which the general proportions do not quite work " +"correctly, for example because of rounding error." +msgstr "" +"För skalbara teckensnitt ska elementet \"font-sizes\" innehålla ett " +"element \"font-scale\" som definierar förhållandet mellan teckensnitt och " +"element som inte hör till teckensnittet på ett allmänt sätt, och också " +"definierar förhållandet mellan Rosegardens nominella teckenstorlek och " +"motsvarande systemteckensnitts storlek. Om elementet \"font-scale\" hittas, " +"antar Rosegarden att teckensnittet är tillgängligt i alla storlekar. Du " +"kan dock fortfarande inkludera ett eller flera element \"font-size\" för " +"att definiera exakta proportioner för en särskild storlek där de " +"allmänna proportionerna inte riktigt fungerar rätt, till exempel på grund " +"av avrundningsfel." + +#. Tag: para +#: index.docbook:5936 +#, no-c-format +msgid "" +"The attributes of \"font-scale\" and \"font-size\" are very similar. The " +"main difference is that all attributes of \"font-scale\" are floating-point " +"values relative to the font size, where 1.0 is the base font size (i.e. the " +"distance between staff lines), whereas attributes of \"font-size\" are " +"integer pixel values. The attributes available are as follows. (Those marked " +"\"optional\" have vaguely sensible defaults, so it's a good idea to try not " +"setting them first.)" +msgstr "" +"Attributen till \"font-scale\" och \"font-size\" är mycket lika. Den " +"huvudsakliga skillnaden är att alla attribut till \"font-scale\" är " +"flyttal i förhållande till teckenstorleken, där 1,0 är basstorleken " +"(dvs. avståndet mellan linjer i notsystemet), medan attributen till " +"\"font-size\" är heltalsvärden av bildpunkter. Tillgängliga attribut är " +"de följande. (De som är markerade som \"valfria\" har i viss mån rimliga " +"standardvärden, så det är en god idé att inte ange dem först.)" + +#. Tag: term +#: index.docbook:5951 +#, no-c-format +msgid "note-height" +msgstr "note-height" + +#. Tag: para +#: index.docbook:5953 +#, no-c-format +msgid "" +"This attribute is only available for the \"font-size\" element, and it is " +"mandatory in that element. It defines the base size of font to which the " +"other attributes in this element apply, and a size that will be offered to " +"the user and used when looking up pixmaps for this font." +msgstr "" +"Det här attributet är bara tillgängligt för elementet \"font-size\", och " +"krävs för elementet. Det definierar teckensnittets grundstorlek som andra " +"attribut i elementet gäller, och en storlek som erbjuds användaren och " +"används vid uppslagning av punktavbildningar för teckensnittet." + +#. Tag: term +#: index.docbook:5963 +#, no-c-format +msgid "font-height" +msgstr "font-height" + +#. Tag: para +#: index.docbook:5965 +#, no-c-format +msgid "" +"May be used in either \"font-size\" or \"font-scale\". This is only relevant " +"for scalable fonts, but is mandatory for them if used in the \"font-scale\" " +"element. This defines the size of the system font used to draw a given size " +"of notation font." +msgstr "" +"Kan antingen användas i \"font-size\" eller \"font-scale\". Det är bara " +"tillämpligt för skalbara teckensnitt, men krävs för dem om det används " +"i elementet \"font-scale\". Det anger storleken på systemteckensnittet som " +"används för att rita en given storlek av notteckensnittet." + +#. Tag: term +#: index.docbook:5974 +#, no-c-format +msgid "beam-thickness" +msgstr "beam-thickness" + +#. Tag: para +#: index.docbook:5976 +#, no-c-format +msgid "Optional. Defines the thickness of a beam." +msgstr "Valfritt. Anger tjockleken på en balk." + +#. Tag: term +#: index.docbook:5981 +#, no-c-format +msgid "staff-line-thickness" +msgstr "staff-line-thickness" + +#. Tag: para +#: index.docbook:5983 +#, no-c-format +msgid "Optional. Defines the thickness of a staff line." +msgstr "Valfritt. Anger tjockleken på en notsystemslinje." + +#. Tag: term +#: index.docbook:5988 +#, no-c-format +msgid "stem-thickness" +msgstr "stem-thickness" + +#. Tag: para +#: index.docbook:5990 +#, no-c-format +msgid "Optional. Defines the thickness of a note stem." +msgstr "Valfritt. Anger tjockleken på ett notskaft." + +#. Tag: term +#: index.docbook:5995 +#, no-c-format +msgid "flag-spacing" +msgstr "flag-spacing" + +#. Tag: para +#: index.docbook:5997 +#, no-c-format +msgid "" +"Optional. Defines the gap between note flags in cases where multiple flags " +"are drawn by drawing a single flag several times." +msgstr "" +"Valfritt. Anger avståndet mellan notflaggor i de fall då flera flaggor " +"ritas genom att upprepa en enstaka flagga flera gånger." + +#. Tag: term +#: index.docbook:6004 +#, no-c-format +msgid "border-x" +msgstr "border-x" + +#. Tag: para +#: index.docbook:6006 +#, no-c-format +msgid "" +"Optional. Specifies that the note head pixmaps have a fixed area to left and " +"right that should not be considered part of the note head. This attribute " +"gives the thickness of that area." +msgstr "" +"Valfritt. Anger att nothuvudets punktavbildning har ett fast område till " +"vänster och höger som inte ska anses vara en del av nothuvudet. Attributet " +"anger områdets tjocklek." + +#. Tag: term +#: index.docbook:6014 +#, no-c-format +msgid "border-y" +msgstr "border-y" + +#. Tag: para +#: index.docbook:6016 +#, no-c-format +msgid "" +"Optional. Specifies that the note head pixmaps have a fixed area to top and " +"bottom that should not be considered part of the note head. This attribute " +"gives the thickness of that area." +msgstr "" +"Valfritt. Anger att nothuvudets punktavbildning har ett fast område " +"ovanför och under som inte ska anses vara en del av nothuvudet. Attributet " +"anger områdets tjocklek." + +#. Tag: title +#: index.docbook:6027 +#, no-c-format +msgid "font-symbol-map" +msgstr "font-symbol-map" + +#. Tag: para +#: index.docbook:6028 +#, no-c-format +msgid "" +"This element lists the symbols available in this notation font, and which " +"pixmap files or system font code points they should be drawn from." +msgstr "" +"Det här elementet listar symbolerna som är tillgängliga i " +"notteckensnittet, och vilka punktavbildningsfiler eller vilka " +"kodpunkter i ett systemteckensnitt som de ska ritas upp med." + +#. Tag: para +#: index.docbook:6033 +#, no-c-format +msgid "" +"It should contain a list of \"symbol\" elements. These have several possible " +"attributes, the choice of which will normally depend on whether the font is " +"based on pixmaps or system fonts:" +msgstr "" +"Det ska innehålla en lista med \"symbol\" element. De har flera möjliga " +"attribut, där valet av vilka normalt beror på om teckensnittet är baserat " +"på punktavbildningar eller systemteckensnitt:" + +#. Tag: term +#: index.docbook:6041 +#, no-c-format +msgid "name" +msgstr "name" + +#. Tag: para +#: index.docbook:6043 +#, no-c-format +msgid "" +"Mandatory. This attribute should contain the name of the notation symbol. If " +"the symbol exists in the <ulink " +"url=\"http://www.unicode.org/charts/PDF/U1D100.pdf\">Unicode 3.2 " +"standard</ulink>, the name should be that used to identify the symbol in the " +"standard." +msgstr "" +"Krävs. Det här attributet ska innehålla namnet på notsymbolen. Om " +"symbolen finns i <ulink " +"url=\"http://www.unicode.org/charts/PDF/U1D100.pdf\">Unicode 3.2 " +"standarden</ulink>, ska namnet som används för att identifiera symbolen " +"vara det som används i standarden." + +#. Tag: para +#: index.docbook:6050 +#, no-c-format +msgid "" +"Most of the symbols Rosegarden expects to find are in the standard; one " +"exception is that many fonts have a special version of the flag symbol that " +"is intended to be used when composing multiple flags from individual single " +"flags. Rosegarden refers to this as \"MUSICAL SYMBOL COMBINING FLAG-0\", a " +"name not used in the Unicode standard (which has flags 1-5 only)." +msgstr "" +"De flesta symboler som Rosegarden förväntar sig att hitta ingår i " +"standarden. Ett undantag är att många teckensnitt har en specialversion av " +"flaggsymbolen som är avsedd att användas när flera flaggor skapas från " +"individuella enstaga flaggor. Rosegarden kallar den för \"MUSICAL SYMBOL " +"COMBINING FLAG-0\", ett namn som inte används av Unicode-standarden (som " +"bara har flaggorna 1 - 5)." + +#. Tag: para +#: index.docbook:6058 +#, no-c-format +msgid "" +"For a definitive set of the symbol names Rosegarden knows about, see the " +"file \"gui/notecharname.cpp\" in the Rosegarden source distribution. Note " +"however that it is possible to use additional symbol names by introducing " +"them in a <link linkend=\"developers-note-styles\">notation style</link>." +msgstr "" +"För den fullständiga uppsättningen symbolnamn som Rosegarden känner " +"till, se filen \"gui/notecharname.cpp\" i Rosegardens källkodsdistribution. " +"Observera dock att det är möjligt att använda ytterligare symbolnamn " +"genom att lägga till dem i en <link " +"linkend=\"developers-note-styles\">notationsstil</link>." + +#. Tag: term +#: index.docbook:6070 +#, no-c-format +msgid "<term>src</term>" +msgstr "<term>src</term>" + +#. Tag: para +#: index.docbook:6072 +#, no-c-format +msgid "" +"The name of the pixmap file from which this symbol should be loaded, without " +"a directory or extension. This is the usual way of describing a symbol in a " +"pixmap font. The file itself should be installed to " +"fonts/<font-name>/<font-size>/<src>.xpm under the " +"Rosegarden installation directory." +msgstr "" +"Namnet på punktavbildningsfilen som ska användas för att ladda symbolen, " +"utan katalog eller filändelse. Det är det vanliga sättet att beskriva en " +"symbol i ett punktavbildat teckensnitt. Själva filen ska installeras i " +"fonts/<teckensnittsnamn>/<teckenstorlek>/<källa>.xpm " +"under Rosegardens installationskatalog." + +#. Tag: term +#: index.docbook:6084 +#, no-c-format +msgid "inversion-src" +msgstr "inversion-src" + +#. Tag: para +#: index.docbook:6086 +#, no-c-format +msgid "" +"The name of a pixmap file from which an inverted version of this symbol may " +"be loaded, without a directory or extension. If this attribute is absent and " +"an inverted version of the symbol is required, it will be generated simply " +"by loading the normal version and reflecting it in a central x-axis." +msgstr "" +"Namnet på en punktavbildningsfil som kan användas för att ladda en " +"inverterad version av symbolen, utan katalog eller filändelse. Om " +"attributet saknas och en inverterad version av symbolen behövs, skapas den " +"helt enkelt genom att ladda den normala versionen och spegla den i den " +"centrala x-axeln." + +#. Tag: term +#: index.docbook:6097 +#, no-c-format +msgid "code" +msgstr "code" + +#. Tag: para +#: index.docbook:6099 +#, no-c-format +msgid "" +"The code point at which this symbol may be found in the relevant system " +"font, as a decimal integer. This is a way of describing a symbol in a " +"scalable font. This attribute will only be referred to if no pixmap file is " +"supplied, or if the pixmap file fails to load." +msgstr "" +"Kodpunkten där symbolen kan hittas i relevant systemteckensnitt, som ett " +"decimalt heltal. Det är ett sätt att beskriva en symbol i ett skalbart " +"teckensnitt. Attributet används bara om ingen punktavbildningsfil " +"tillhandahålls, eller om laddning av punktavbildningsfilen misslyckas." + +#. Tag: term +#: index.docbook:6110 +#, no-c-format +msgid "inversion-code" +msgstr "inversion-code" + +#. Tag: para +#: index.docbook:6112 +#, no-c-format +msgid "" +"The code point at which an inverted version of this symbol may be found in " +"the relevant system font. If this attribute is absent and an inverted " +"version of the symbol is required, it will be generated simply by loading " +"the normal version and reflecting it in a central x-axis." +msgstr "" +"Kodpunkten där en inverterad version av symbolen kan hittas i relevant " +"systemteckensnitt. Om attributet saknas och en inverterad version av " +"symbolen behövs, skapas den helt enkelt genom att ladda den normala " +"versionen och spegla den i den centrala x-axeln." + +#. Tag: term +#: index.docbook:6123 +#, no-c-format +msgid "glyph" +msgstr "glyph" + +#. Tag: para +#: index.docbook:6125 +#, no-c-format +msgid "" +"The raw glyph index at which this symbol may be found in the relevant system " +"font, as a decimal integer. This is a way of describing a symbol in a " +"scalable font. This attribute will only be referred to if no pixmap file is " +"supplied, or if the pixmap file fails to load." +msgstr "" +"Det obehandlade indexet för glyfen där symbolen kan hittas i relevant " +"systemteckensnitt, som ett decimalt heltal. Det är ett sätt att beskriva " +"en symbol i ett skalbart teckensnitt. Attributet används bara om ingen " +"punktavbildningsfil tillhandahålls, eller om laddning av " +"punktavbildningsfilen misslyckas." + +#. Tag: term +#: index.docbook:6136 +#, no-c-format +msgid "inversion-glyph" +msgstr "inversion-glyph" + +#. Tag: para +#: index.docbook:6138 +#, no-c-format +msgid "" +"The raw glyph index at which an inverted version of this symbol may be found " +"in the relevant system font. If this attribute is absent and an inverted " +"version of the symbol is required, it will be generated simply by loading " +"the normal version and reflecting it in a central x-axis." +msgstr "" +"Det obehandlade indexet för glyfen där en inverterad version av symbolen " +"kan hittas i relevant systemteckensnitt. Om attributet saknas och en " +"inverterad version av symbolen behövs, skapas den helt enkelt genom att " +"ladda den normala versionen och spegla den i den centrala x-axeln." + +#. Tag: term +#: index.docbook:6149 +#, no-c-format +msgid "font-id" +msgstr "font-id" + +#. Tag: para +#: index.docbook:6151 +#, no-c-format +msgid "" +"The id of the system font from which this symbol should be loaded, as " +"defined in the <link " +"linkend=\"developers-note-fonts-mapping-format-font-requirements\">font-requi" +"rements</link> element. The default is 0." +msgstr "" +"Identifikationen för systemteckensnittet som den här symbolen ska laddas " +"från, som det är definierat i elementet <link " +"linkend=\"developers-note-fonts-mapping-format-font-requirements\">font-requi" +"rements</link>. Normalvärdet är 0." + +#. Tag: term +#: index.docbook:6160 +#, no-c-format +msgid "codebase" +msgstr "codebase" + +#. Tag: para +#: index.docbook:6162 +#, no-c-format +msgid "" +"This (decimal integer) attribute may be of use if many of the symbols in a " +"scalable font cover a short range of code points starting at a relatively " +"high code page. If supplied, the codebase value will be added to each of the " +"subsequent code and inversion-code values when looking up a symbol." +msgstr "" +"Det här attributet (ett decimalt heltal) kan vara användbart om många av " +"symbolerna i ett skalbart teckensnitt täcker ett kort område med " +"kodpunkter med början på en relativt hög kodsida. Om det anges, läggs " +"värdet codebase till för vart och ett av efterföljande värden på code " +"och inversion-code när en symbol slås upp." + +#. Tag: para +#: index.docbook:6174 +#, no-c-format +msgid "" +"Although none of these attributes is mandatory except for the name, a symbol " +"obviously needs to supply at least one of \"src\", \"inversion-src\", " +"\"code\", \"inversion-code\", \"glyph\", or \"inversion-glyph\" to stand any " +"chance of being rendered at all. It is of course perfectly legitimate to " +"supply several or all of these attributes." +msgstr "" +"Även om inget av attributen krävs, förutom namnet, måste en symbol " +"uppenbarligen tillhandahålla åtminstone en av \"src\", \"inversion-src\", " +"\"code\", \"inversion-code\", \"glyph\" eller \"inversion-glyph\" för att " +"ha någon möjlighet att överhuvudtaget ritas upp. Det är förstås " +"fullständig legitimt att tillhandahålla flera eller alla dessa attribut." + +#. Tag: title +#: index.docbook:6186 +#, no-c-format +msgid "font-hotspots" +msgstr "font-hotspots" + +#. Tag: para +#: index.docbook:6187 +#, no-c-format +msgid " " +msgstr " " + +#. Tag: title +#: index.docbook:6196 +#, no-c-format +msgid "Creating new notation styles" +msgstr "Skapa nya notstilar" + +#. Tag: para +#: index.docbook:6198 +#, no-c-format +msgid "" +"Rosegarden's notation editor has the ability to display and edit notes in " +"various standard styles: classical, diamond heads and so on. These styles " +"are all defined in XML style definition files installed along with the " +"application, and it's possible to create a new one by writing a simple XML " +"file. Rosegarden simply looks at the set of installed files to determine " +"which styles to offer the user. You can refer to the default set of files in " +"the styles subdirectory of the Rosegarden installation directory for " +"examples." +msgstr "" +"Rosegardens notbehandlare har möjlighet att visa och redigera noter med " +"olika standardstilar: klassisk, rombformade huvuden och så vidare. Alla " +"stilar definieras i definitionsfiler på XML-form som installeras " +"tillsammans med programmet, och det är möjligt att skapa en ny genom att " +"skriva en enkel XML-fil. Rosegarden tittar helt enkelt på uppsättningen " +"installerade filer för att avgöra vilka stilar som användaren ska " +"erbjudas. Du kan till exempel hänvisa till standarduppsättningen med filer " +"i underkatalogen för stilar i Rosegardens installationskatalog." + +#. Tag: para +#: index.docbook:6210 +#, no-c-format +msgid "" +"The file format is not yet especially comprehensive; at the moment it has " +"been designed to be powerful enough to describe the standard styles that " +"come with Rosegarden, but not much more. If you should try to create new " +"styles this way, we'd be very interested in your feedback on the Rosegarden " +"mailing-lists." +msgstr "" +"Filformatet är inte ännu särskilt omfattande. För ögonblicket är det " +"konstruerat för att vara kraftfullt nog att beskriva standardstilarna som " +"levereras med Rosegarden, men inte mycket mer. Om du gör ett försök att " +"skapa nya stilar på det här sättet, är vi mycket intresserade av din " +"återmatning via Rosegardens e-postlistor." + +#. Tag: title +#: index.docbook:6220 +#, no-c-format +msgid "Notation style XML format" +msgstr "XML-format för notstil" + +#. Tag: para +#: index.docbook:6222 +#, no-c-format +msgid "" +"Here is a summary of the XML elements that may be used in a style definition " +"file." +msgstr "" +"Här är en översikt över XML-elementen som kan användas i en " +"stildefinitionsfil." + +#. Tag: title +#: index.docbook:6228 +#, no-c-format +msgid "rosegarden-note-style" +msgstr "rosegarden-note-style" + +#. Tag: para +#: index.docbook:6230 +#, no-c-format +msgid "" +"This element must exist in every style file, and should contain all the " +"other elements. It has one optional attribute, \"base-style\", which may be " +"used to name a style from which this style takes the default values for any " +"parameters not specified elsewhere in the present file. It's often good " +"practice to define a style in terms of the minimal difference from a given " +"base style: see the supplied Cross.xml for a particularly simple example." +msgstr "" +"Det här elementet måste finnas i alla stilfiler, och ska innehålla alla " +"övriga element. Det har ett valfritt attribut, \"base-style\", som kan " +"användas för att namnge en stil där den här stilen hämtar " +"standardvärden för alla parametrar som inte anges någon annanstans i den " +"befintliga filen. Det är ofta lämpligt att definiera en stil i form av " +"minsta möjliga skillnader från en given basstil. Se filen Cross.xml som " +"tillhandahålls, för ett särskilt enkelt exempel." + +#. Tag: para +#: index.docbook:6240 +#, no-c-format +msgid "" +"Note that the \"rosegarden-note-style\" element does not give the name of " +"the style being defined, which is instead currently drawn from the name of " +"the file. At some point in the future we may add internationalizable style " +"name attributes to this element." +msgstr "" +"Observera att elementet \"rosegarden-note-style\" inte anger namnet på " +"stilen som definieras, som istället tas från filens namn. Någon gång i " +"framtiden kanske stöd för översättning av stilnamn läggs till i det " +"här elementets attribut." + +#. Tag: title +#: index.docbook:6248 +#, no-c-format +msgid "global, note" +msgstr "global, note" + +#. Tag: para +#: index.docbook:6250 +#, no-c-format +msgid "" +"Within the \"rosegarden-note-style\" element, there may be one \"global\" " +"element and any number of \"note\" elements. We describe these together, as " +"they have almost identical sets of attributes. The \"global\" element simply " +"provides default values for those parameters not specified for a particular " +"note type in any following \"note\" element." +msgstr "" +"I elementet \"rosegarden-note-style\" kan det finnas ett \"global\" element " +"och hur många \"note\" element som helst. De beskrivs tillsammans, eftersom " +"de har nästan identiska uppsättningar attribut. Elementet \"global\" " +"tillhandahåller helt enkelt standardvärden för de parametrar som inte " +"anges för en viss nottyp i något av följande \"note\" element." + +#. Tag: para +#: index.docbook:6258 +#, no-c-format +msgid "" +"The attributes for these elements are as follows. All of these are optional " +"except as described:" +msgstr "" +"Attributen för elementen är följande. Alla är valfria utom enligt " +"beskrivningen:" + +#. Tag: para +#: index.docbook:6266 +#, no-c-format +msgid "" +"Only relevant to the \"note\" element, and mandatory for that element. This " +"attribute specifies which sort of note is being styled. Legal values are " +"textual American or British note names (from \"64th\", \"sixth-fourth " +"note\", \"hemidemisemiquaver\" etc to \"double whole note\")." +msgstr "" +"Gäller bara elementet \"note\", och krävs för det elementet. Det här " +"attributet anger vilken sorts not som stilen gäller för. Giltiga värden " +"är tonnamn på amerikansk eller brittisk engelska (från \"64th\", " +"\"sixth-fourth note\", \"hemidemisemiquaver\" etc till \"double whole " +"note\")." + +#. Tag: term +#: index.docbook:6277 +#, no-c-format +msgid "shape" +msgstr "shape" + +#. Tag: para +#: index.docbook:6279 +#, no-c-format +msgid "" +"Defines a note head shape for this style. Any string is a legal value, but " +"the only values implemented so far are \"angled oval\", \"level oval\", " +"\"breve\", \"cross\", \"triangle up\", \"triangle down\", \"diamond\" and " +"\"rectangle\". The value \"number\" is also recognised but not yet " +"implemented." +msgstr "" +"Definierar en form för nothuvudet i den här stilen. Vilken sträng som " +"helst är ett giltigt värde, men de enda värden som hittills är " +"implementerade är \"angled oval\", \"level oval\", \"breve\", \"cross\", " +"\"triangle up\", \"triangle down\", \"diamond\" och \"rectangle\". Värdet " +"\"number\" känns också igen, men är ännu inte implementerat." + +#. Tag: term +#: index.docbook:6290 +#, no-c-format +msgid "charname" +msgstr "charname" + +#. Tag: para +#: index.docbook:6292 +#, no-c-format +msgid "" +"Defines a note font character name to be used as the note head for this " +"style. An element may supply a \"shape\" or \"charname\" attribute, but not " +"both. The name should be one of those defined in the current notation font's " +"<link " +"linkend=\"developers-note-fonts-mapping-format-font-symbol-map\">symbol " +"map</link> (in a \"name\" attribute)." +msgstr "" +"Definierar ett teckennamn i notteckensnittet som ska användas som nothuvud " +"för stilen. Ett element kan tillhandahålla attributet \"shape\" eller " +"\"charname\", men inte båda. Namnet ska vara ett av de som definieras i det " +"nuvarande notskriftteckensnittets <link " +"linkend=\"developers-note-fonts-mapping-format-font-symbol-map\">symbol " +"map</link> (i ett attribut \"name\")." + +#. Tag: term +#: index.docbook:6304 +#, no-c-format +msgid "filled" +msgstr "filled" + +#. Tag: para +#: index.docbook:6306 +#, no-c-format +msgid "" +"Specifies whether this note should have a filled head (where applicable, " +"i.e. where the shape attribute supplies a shape that is available both " +"filled and unfilled). Must be \"true\" or \"false\"." +msgstr "" +"Anger om noten ska ha ett ifyllt huvud (när det är tillämpligt, dvs. när " +"formegenskapen anger en form som både är tillgänglig ifylld och inte). " +"Måste vara \"true\" eller \"false\"." + +#. Tag: term +#: index.docbook:6315 +#, no-c-format +msgid "stem" +msgstr "stem" + +#. Tag: para +#: index.docbook:6317 +#, no-c-format +msgid "" +"Specifies whether this note should have a stem. Must be \"true\" or " +"\"false\"." +msgstr "Anger om noten ska ha ett skaft. Måste vara \"true\" eller \"false\"." + +#. Tag: term +#: index.docbook:6324 +#, no-c-format +msgid "flags" +msgstr "flags" + +#. Tag: para +#: index.docbook:6326 +#, no-c-format +msgid "" +"Defines how many flags or beams this note should have. The valid range is 0 " +"to 4." +msgstr "" +"Anger hur många flaggor eller balkar som noten ska ha. Giltigt intervall " +"är 0 till 4." + +#. Tag: term +#: index.docbook:6333 +#, no-c-format +msgid "slashes" +msgstr "slashes" + +#. Tag: para +#: index.docbook:6335 +#, no-c-format +msgid "Defines how many slashes this note should have across its stem." +msgstr "Anger hur många tvärbalkar noten ska ha över skaftet." + +#. Tag: term +#: index.docbook:6342 +#, no-c-format +msgid "hfixpoint" +msgstr "hfixpoint" + +#. Tag: para +#: index.docbook:6344 +#, no-c-format +msgid "" +"Specifies in which x position the stem fixes to the note head. Acceptable " +"values are \"normal\" (the right side when the stem points up, the left when " +"it points down), \"central\", and \"reversed\" (left side when the stem " +"points up, right when it points down)." +msgstr "" +"Anger på vilken x-position som skaftet ansluts till nothuvudet. Acceptabla " +"värden är \"normal\" (höger sida när skaftet pekar uppåt, vänster sida " +"när det pekar neråt), \"central\" och \"reversed\" (vänster sida när " +"skaftet pekar uppåt, höger sida när det pekar neråt)." + +#. Tag: term +#: index.docbook:6354 +#, no-c-format +msgid "vfixpoint" +msgstr "vfixpoint" + +#. Tag: para +#: index.docbook:6356 +#, no-c-format +msgid "" +"Specifies in which y position the stem fixes to the note head. Acceptable " +"values are \"near\" (the stem fixes to the top when pointing up, the bottom " +"when pointing down), \"middle\", or \"far\"." +msgstr "" +"Anger på vilken y-position som skaftet ansluts till nothuvudet. Acceptabla " +"värden är \"near\" (skaftet ansluts till toppen när det pekar uppåt, " +"till botten när det pekar neråt), \"middle\" eller \"far\"." + +#. Tag: title +#: index.docbook:6517 +#, no-c-format +msgid "Credits and License" +msgstr "Tack till och licens" + +#. Tag: application +#: index.docbook:6520 +#, no-c-format +msgid "<application>Rosegarden</application>" +msgstr "<application>Rosegarden</application>" + +#. Tag: para +#: index.docbook:6525 +#, no-c-format +msgid "" +"Rosegarden-4 is Copyright 2000-2004 Guillaume Laurent, Chris Cannam and " +"Richard Bown. The moral rights of Guillaume Laurent, Chris Cannam and " +"Richard Bown to be identified as the authors of this work have been asserted." +msgstr "" +"Rosegarden-4 är Copyright 2000-2004 Guillaume Laurent, Chris Cannam och " +"Richard Bown. Moralisk rättighet att identifieras som upphovsmän till det " +"här verket hävdas av Guillaume Laurent, Chris Cannam och Richard Bown." + +#. Tag: para +#: index.docbook:6536 +#, no-c-format +msgid "" +"Parts of Rosegarden-4 are derived from Rosegarden 2.1, which is Copyright " +"1994 – 2001 Chris Cannam, Andrew Green, Richard Bown and Guillaume " +"Laurent." +msgstr "" +"Delar av Rosegarden-4 är härledda från Rosegarden 2.1, som är Copyright " +"1994 – 2001 Chris Cannam, Andrew Green, Richard Bown och Guillaume " +"Laurent." + +#. Tag: para +#: index.docbook:6546 +#, no-c-format +msgid "" +"For musical notation display Rosegarden-4 uses pixmaps derived from the Feta " +"font, part of the <ulink url=\"http://lilypond.org/\">Lilypond</ulink> " +"software, which is Copyright 1997 – 2001 Jan Nieuwenhuizen and Han-Wen " +"Nienhuys." +msgstr "" +"För visning av musikalisk notskrift använder Rosegarden-4 " +"punktavbildningar härledda från teckensnittet Feta, som är en del av " +"programvaran <ulink url=\"http://lilypond.org/\">Lilypond</ulink>, som är " +"Copyright 1997 – 2001 Jan Nieuwenhuizen och Han-Wen Nienhuys." + +#. Tag: para +#: index.docbook:6558 +#, no-c-format +msgid "" +"Other major contributors include Randall Farmer, Ron Kuris, Hans Kieserman, " +"and Michael McIntyre." +msgstr "" +"Bland andra väsentliga bidragsgivare finns Randall Farmer, Ron Kuris, Hans " +"Kieserman och Michael McIntyre." + +#. Tag: para +#: index.docbook:6567 +#, no-c-format +msgid "" +"The Rosegarden splash-screen image is from a 1900 postcard of Thornden Park " +"at Syracuse University, Syracuse, NY, used with thanks to the staff of " +"Syracuse University." +msgstr "" +"Rosegardens startskärm kommer från ett vykort av Thornden-parken vid " +"Syracuse-universitetet i Syracuse, New York, tryckt år 1900. Tack till " +"personalen på Syracuse-universitetet för användning av det." + +#. Tag: para +#: index.docbook:6579 +#, no-c-format +msgid "" +"Documentation copyright 2002-2004 Chris Cannam, Richard Bown, Guillaume " +"Laurent" +msgstr "" +"Dokumentation copyright 2002-2004 Chris Cannam, Richard Bown, Guillaume " +"Laurent" + +#. Tag: para +#: index.docbook:6598 +#, no-c-format +msgid "" +"This program is licensed under the terms of the <ulink " +"url=\"common/gpl-license.html\">GNU General Public License</ulink>." +msgstr "" +"Det här programmet distribueras under villkoren i <ulink " +"url=\"common/gpl-license.html\">GNU General Public License</ulink>." + +#. Tag: title +#: index.docbook:6609 +#, no-c-format +msgid "Rosegarden-4 Revision History" +msgstr "Rosegarden-4 utgåvehistorik" + +#. Tag: para +#: index.docbook:6612 +#, no-c-format +msgid "" +"0.9.9 – July 2004: plugin synths, triggered segments, notation " +"improvements" +msgstr "" +"0.9.9 – juli 2004: syntinsticksmoduler, utlösande segment, " +"notationsförbättringar" + +#. Tag: para +#: index.docbook:6615 +#, no-c-format +msgid "0.9.8 – May 2004: better audio subsystem" +msgstr "0.9.8 – maj 2004: bättre ljuddelsystem" + +#. Tag: para +#: index.docbook:6618 +#, no-c-format +msgid "0.9.7 – February 2004:" +msgstr "0.9.7 – februari 2004:" + +#. Tag: para +#: index.docbook:6621 +#, no-c-format +msgid "0.9.6 – December 2003: bug fixes" +msgstr "0.9.6 – december 2003: felrättningar" + +#. Tag: para +#: index.docbook:6624 +#, no-c-format +msgid "0.9.5 – November 2003: a great many stuff" +msgstr "0.9.5 – november 2003: en hel del saker" + +#. Tag: para +#: index.docbook:6627 +#, no-c-format +msgid "0.9.1 – May 2003: step recording, Mup export, many many bug fixes" +msgstr "" +"0.9.1 – maj 2003: stegvis inspelning, MUP-export, många många " +"felrättningar" + +#. Tag: para +#: index.docbook:6630 +#, no-c-format +msgid "" +"0.9 – April 2003: many notation improvements, improved bank editor, " +"audio enhancements and refinements, translations" +msgstr "" +"0.9 – april 2003: många förbättringar av notation, förbättrad " +"bankeditor, ljudförbättringar och förfiningar, översättningar" + +#. Tag: para +#: index.docbook:6633 +#, no-c-format +msgid "0.8.5 – December 2002: bank editor, MIDI filters, panic button" +msgstr "0.8.5 – december 2002: bankeditor, MIDI-filter, panikknapp" + +#. Tag: para +#: index.docbook:6636 +#, no-c-format +msgid "0.8 – October 2002: printing, LADSPA plugins, improved Matrix View" +msgstr "" +"0.8 – oktober 2002: utskrift, LADSPA-insticksmoduler, förbättrad " +"matrisvy" + +#. Tag: para +#: index.docbook:6639 +#, no-c-format +msgid "" +"0.2.0 – August 2002: WAV file support, sweep selections, contrapuntal " +"staves" +msgstr "0.2.0 – augusti 2002: WAV-filstöd, markering med svepning, kontrapunkt" + +#. Tag: para +#: index.docbook:6642 +#, no-c-format +msgid "" +"0.1.6 – June 2002: configuration dialog, Lilypond support, quantize " +"dialog" +msgstr "" +"0.1.6 – juni 2002: inställningsdialogruta, Lilypond-stöd, " +"kvantiseringsdialogruta" + +#. Tag: para +#: index.docbook:6645 +#, no-c-format +msgid "0.1.5 – May 2002: KDE 3, ALSA support, JACK audio support" +msgstr "0.1.5 – maj 2002: KDE 3, ALSA-stöd, JACK-ljudstöd" + +#. Tag: para +#: index.docbook:6648 +#, no-c-format +msgid "0.1.4 – March 2002: more undo, segment editing, audio playback" +msgstr "0.1.4 – mars 2002: mer ångra, segmentredigering, ljuduppspelning" + +#. Tag: para +#: index.docbook:6651 +#, no-c-format +msgid "0.1.3 – January 2002: piano-roll/matrix view, &MIDI; recording" +msgstr "0.1.3 – januari 2002: pianorulle och matrisvy, &MIDI;-inspelning" + +#. Tag: para +#: index.docbook:6654 +#, no-c-format +msgid "" +"0.1.2 – November 2001: notation undo, transport dialog, position " +"pointer" +msgstr "" +"0.1.2 – november 2001: ångra notation, transportdialogruta, " +"positionspekare" + +#. Tag: para +#: index.docbook:6657 +#, no-c-format +msgid "0.1.1 – October 2001: scalable notation" +msgstr "0.1.1 – oktober 2001: skalbar notation" + +#. Tag: para +#: index.docbook:6660 +#, no-c-format +msgid "0.1 – June 2001: first public release of Rosegarden-4" +msgstr "0.1 – juni 2001: första öppna utgåva av Rosegarden-4" + |
