You see the latency is about 53.3 ms, that is the lowest I can get on my laptop without jackd starting to complain about Xrun problem. You have several ways to change the latency for the best optical way for your computer, and that is

Frames/periodes (16-4096)

Periodes/buffer (1-xxx)

Take in use Audacity, I have made a documentation that help you to get started. First you just double click on the audio segment, and audacity should start automatically and load the segment you have chosen.

http://wiki.debian.org/DebianEdu/Documentation/Manuals/Audacity

MERK!

When you have done the changes on the audio file, remember to save it with the same name, and then you have to save the project in rosegarden, and reopen your project. This way you will get the changes you did in audacity applied onto rosegarden

For those who don't have a keyboard/synth can use qsynth to get midi sound on rosegarden. You can download soundfont from here: ftp://ftp.no.debian.org/debian/pool/main/f/fluid-soundfont/fluid-soundfont-gm_3.1-1_all.deb and use <gdebi> to install it.

Do not forget to choose that you want to use the qsynth in the device manager on rosegarden if not rosegarden automatically have chosen this.

There is a list of plugins you want in rosegarden when you don't have a gm keyboard/synth, but only a keyboard that send midi, use the aptitude command to get it.

fixme: legg inn synth plugins som du har erfaring med og synes er gode

fixme: legg til audio plugin som du har erfaring med og synes er gode

These have been tested with skolelinux 3, kubuntu 7.10, kubuntu 8.04 and with kernel 2.6.22.16, and 2.6.24.18

Thanks to Mario Music for allowing me to be in their store testing this equipment.

Fixme: Legg til enheter som du har funnet ut fungerer uten problemer

Enheter som har blitt testet, men ikke ville fungere

hvis alt fungerer som det skal er det på tide å ta en titt på Rosegardendokumentasjonen her; http://wiki.debian.org/DebianEdu/Documentation/Manuals/Rosegarden

Det var oversikten over instrumentene, så er det en egen oversikt over percussive instumenter (trommer)

Nr.: Er programchange

MIDI-oppsett, i dette tilfellet fila midisetup.rg, skal jeg vise deg hvordan du kan endre innstillinger på noen av controllene som du vil finne nyttig i MIDI-oppsettet

Ved å ha unnagjort dette har du lagt opp et strukturert oppsett av MIDI-segmentet som på forhånd forteller synth/keyboardet hva den skal gjøre. Da er det lettere å eksportere sangen til MIDI, og deretter publisere den slik at den kan spilles av på mobiltelefoner,(hvis mobilen har støtte for MIDI), eller andre synther,

du kan laste ned den ferdige oppsettfilen her

midisetup.rg

Noen ganger ønsker man å bruke andre lyder som finnes på synth/keyboardet og som ligger utenom gm-standarden. Da er man nødt til å bruke en controller som tar seg av dette, controller 0 og 32.

Denne funksjonen brukes også hvis det er ønskelig å ha f.eks. tromme som effekter på et annet spor en 10. Jeg har spor 16 som favoritt der, da kan man med controller 32 (data1), og nummer 4 (data2) endre oppførselen på MIDI-sporet. Ved da å velge programchange 57, vil det sporet bli effect kit.

Controller 0 og 32, med verdien 0, er gm-standarden, brukes på track 1-9, 11-16

Controller 0 og 32, med verdien 1-127 er de forskjellige bankene, brukes på track 1-9, 11-16

Controller 0 og 32, med verdien 4, er for min synth tromme, denne bruker jeg som standard på track 10, og ved spesielle behov kan andre spor også programmeres til å oppføre seg som tromme.

Nyere synther har som regel mange flere lyder enn bare GM-standaren, jeg anbefaler deg å finn fram manualen for din synth. Der finner du total oversikt over instrumenter og hvor de befinner seg, ved hjelp av MSB,LSB controller.

her har du et eksempel

Mitt keyboard har et instrument på kontroller 0(MSB) med verdi 8, og i controller 32(LSB) med verdi 1, og til slutt programendring 3.

så følgende blir det

controller 0 med verdi 8

controller 32 med verdi 1

og til slutt program change med verdi 3

the order on when controller 0 and 32 and program change comes are important

husk at controller 0 and 32, må komme FØR program change.

jeg har inkludert dette i grunnoppsettfilen.

Dette er jeg er glad for at jeg fant ut. Ved å bruke instrumentparametre og velge instrumenter, pan, reverb, osv. kan du ved dette enkle trikset, få Rosegarden til å putte disse elementene inn i segmentet automatisk, slik at sangen blir klar for MIDI-eksport. Det du gjør, er at mens Rosegarden teller opp for record, trykker du ned en tangent på keyboardet/synthen, slik at du får en note i opptellingen. Gjør dette på alle segmentene. Når du så eksporterer sangen til MIDI ligger infoen i segmentet. Det du må huske på er å bare laste inn MIDI-filen din, og fjerne de notene som ikke skal være der.

Men som jeg har sagt, er det ikke nødvendig hvis du holder prosjektet ditt som en .rg fil.

Alle synther har som regel flere lyder en 128, så med GM får du ikke utnyttet alle lydene. og som regel under quick instrument parameter pick, får du som standard bare tak i de GM-standardiserte lydene. Så hvis du for eksempel legger til ditt musikkinstrument som standard synth i ditt studio, får du utnyttet det fulle potensialet som lever i synth/keyboardet ditt. Hvis du mot formodning ikke skulle finne instrumentet ditt liggende i listen, kan eventuelt vente på neste utgave av Rosegarden og se om den har blitt lagt til, eller du kan hjelpe Rosegardenprosjektet ved legge inn instrumentindeksen for ditt instument selv, ved å adde new device. Les i boken som fulgte med instumentet, der vil du finne oversikten over alle instrumentene. Når dette er gjort, kan du sende filen til Rosegarden listen slik at utvikklerne kan legge det til ved neste rosegarden release. Samtidig kan du melde deg inn i listen slik at du aktivt kan være med og delta i utviklingen. http://rosegardenmusic.com/support/lists/

Det er viktig å være litt nøye med å fortelle Rosegarden hvor du ønsker å plassere lydspor til dine forskjellige melodier, la oss si du har laget en melodi der du har lagt inn gitarer og sangstemme, da vil du gjerne ha kontroll over hvilken filer som tilhører den melodien. Dette er ganske enkelt å få til med Rosegarden. Et eksempel: Du lager en melodi som heter shallala,og du skal legge til stemme og gitar til denne melodie. Da lager du også en mappe som heter shallala, og plasserer alt som blir gjort i den mappa. Da har du full kontroll når du begynner å få en del prosjekter.

velg --> "composition" ---> og deretter "edit document properties"

Man ønsker jo å fortelle i noteutskriftene hva sangen heter, og hvem komponisten er. Dette kan gjøres på følgende vis

Denne funksjonen har flere muligheter. Når man har spilt inn en del av musikken kan det jo hende man har bommet litt på takten. Det er da Quantize kommer inn i bildet. Den er nyttig for å få notene rett på takten.

Ved og bruke denne rett kan du spare deg for mye arbeid. Her er det bare å prøve seg fram, det er alltids mulighet til å angre hvis Quantisering ikke gikk som forventet, så kan du forsøke igjen med andre spesifikasjoner på base gridenheten. Man må prøve seg fram og se hvilken innstilling som fungerer best. Det er mange muligheter.

Med denne kan du ved et enkelt tastetrykk endre en stakkato innspilt del til legato.

En annen Quantizer som vi skal ta i bruk er heuristic notation quantizer. Denne hjelper til med å forlenge notene til den lengden du skulle ønske. Denne brukes mest til å rydde opp i notasjonsframvisningen.

Denne metoden har forlenget noten til rett lenge på 1/16-del som skal spilles stakkato, med en påfølgende 16-dels pause, Dette forandrer notasjonsvisningen til det bedre

Nummer 1 viser hvordan notene så ut før Quantizeringa, og nummer 2 viser hvordan de ser ut etter. Nummer 2 er lettere for en musiker å tolke enn nummer 1 som, med 32'ende dels noter, med litt varierende pauser er forvirrende og krevende å tolke. Nummer 2 er nok bedre og tolke, og vil nok bli nærmest likt slik jeg ønsker notene skal spilles. En ting er at det høres fint ut på MIDIen, men hvis du ønsker å skrive ut noter til et orkester eller skolekorps, er det viktig å rydde litt opp, og gjøre notasjonen ryddig og oversiktlig. Dette var en kort introduksjon til hvordan man kan bruke Matrix editoren.

Ved å følge denne veiledningen får du satt forskjellige nyttige ting, som åfortelle musikeren hvordan du ønsker tempoet, hvor kraftig, og hvilken akkord. Det er bare en del av verktøyet, påfølgende bilde viser hvordan man får endret hvordan notene bindes sammen, og hvordan du kan sette inn gradvis økende styrke på notasjonen.

Hvis du ser på menyen til høyre, er der mange muligheter for å forbedre informasjonen på notasjonen. Det du behøver å huske på er bare å merke de notene du ønsker, og legge på en spesiell funksjon.

Hvis du ser på venstre side, har du muligheter til manuelt å legge inn noter og pauser i notasjonen, du kan endre fra g-nøkkel til bass-nøkken, dette skal jeg gå litt nærmere inn på.

Da bruker du funksjonen interpret

It is not possible yet, to display a piano segment in a dual system (grand staff). However here is a detailed manual on rendering such scores with LilyPond. First step is to split a segment by pitch (This feature refers to feature request 4932).

Det er to måter å mate inn noter i scoreeditor, den ene er manuell mating.

Den andre metoden er å kjøre på med step record. Den er mitt favoritt, og kan være en fin metode for studentene å lære seg å finne ut hva slags tast på synthen/keyboardet som representerer noten.

Ved å høyreklikke der du ønsker tempo endring, la oss si ved 3 tallet, og så velge 'Insert Tempo Change' Vil du få opp en prikk ved 3 tallet. Ved å venstreklikke bak den nye prikken og holde musknappen nede, kan du kjapt øke og senke tempoet.

Ved å velge denne, vil et tempoendringspunkt bli laget der du er på sangen.

Denne er fin å bruke hvis du ønsker en gradvis tempoendring.

Her kan du endre på tempo ved å skrive inn hvilket tempo du ønsker. Denne er nok den beste å bruke hvis du ønsker et spesielt tempo. Drafunksjonen er grei, men kan være litt upresis.

Denne gir deg mulighet til å endre på takten i melodien. I mitt eksempel har jeg i starten en 4/4 takt, og etter tempoendringen har jeg endret låten til en 3/4 dels takt.

Med denne kan du manuelt gå inn på alle dine tempoendringer, taktendringer og endre manuelt.

Etter at du har gjort et vellykket opptak av MIDI-sangen, kan du påbygge med vokal, eller el-guitar, osv. Her er det bare å være kreativ.

her har du et eksempel på musikk som er laget i Rosegarden. Jeg har fått en kamerat til å spille inn gitar for meg.

arr/melodi: Alf Tonny Bätz. Gitar: Bjørn Nygård

MP3-utgave

http://alfton.gfxi.no/files/upseth.mp3

MIDI-utgave

http://alfton.gfxi.no/files/upseth.mid

Hvis ønsker samtidig å ha oppe Rosegarden og audacity må du konfigurere swami til å bruke jackdeamon som lydkontroller.

After that you have to start jackd you have to manualy connect FluidSynth so you can hear what been played.

Nu er du klar til å starte å lage din egenproduserte lyd, som du kan ta i bruk i ditt musikkprosjekt

Så hvordan lage en lyd?, Her anbefaler jeg å ta i bruk audacity til å redigere lyden din, for eksempel et hyl, et ord, eller noen ekte instrumenter. Bruk audacity til å fjerne sus og eventuelle pauser. Når dette er gjort kan du eksportere dette som en WAV-fil, og importere dette inn i swami. Bruk swami til å koble dette til et "program change" nummer, og til slutt eksportere dette som en SF2-fil. Da kan du under Rosegarden ta lyden i bruk med fluidsynth-DSSI-plugin.

Så la oss gå igjennom dette steg før steg.

1. File, create new
2. Right click on untitled, and choose Properties. (Rename it to your liking)
3. Click on the "+", and right click under Samples, 
   and choose load sample (choose the wav files you want to use for your instrument)
4. Click on the "+" behind Samples, and User, there you see your wav file. 
   In our case, there are two files, named L and R 
   (Hint: file names are truncated to 10 characters)
5. Then click on Instrument, so it gets highlighted, then click right and choose New Instrument
6. Click on the "+" behind Instrument, and right click on New item, 
   and choose properties and change name to your liking.
7. Then it's time to select the samples to be used for our new instrument: 
   Mark them within Samples/User by holding down the control key while clicking. 
   Afterwards, you can insert those samples at Instruments/Your Instrument by means of the
   Paste function in the context menu (right click).
   Your Samples have been assigned to the instrument name you made.
   (Hint: This works like a link; whenever you change sample properties,
    this will also take effect in your instrument.)

And just repeat the cyclus for each sound, and when you are finished, you just save it. And it's time to use it.

When creating a chromatic instrument from a set of samples that cover different pitch ranges (bass, mids, trebles), further actions need to be done to make sure you get a continues sound.

You will need information about what note is played in each sample. This reference note can be set either in sample properties, or you can simply move the white marker to the corresponding key. You can hear the effect instantly, when you click on the keyboard: The original pitch is played when you hit the reference note. From here it is bent up or down, depending on the distance you move right or left.

When you have set all reference notes for you samples, you should hear notes of the same pitch nonregarding what sample you select!

For continuous sounds (like organ, flute, strings), your samples can never be as long as the longest note that might be played when using your soundfont. Therefor it is necessary to define a loop range that is repeated over and over when the musician will keep a key pressed. Again, you can move two markers to find a section of constant amplitude - try to find zero crossings in the sample to prevent disturbing clicks.

CategoryPermalink CategorySound

Translations of this document are kept in PO files like in many free software projects, read usr/share/doc/debian-edu-doc-en/README.rosegarden-manual-translations for more information on this. Please read also read this, if you want to start/help translating this document.

To commit your translations you need to be a member of the Alioth project debian-edu. To translate, you just need to check out some files from from Subversion (which can be done anonymously), create patches and send those to debian-edu-doc@packages.qa.debian.org.

You can checkout the debian-edu-doc source anonymously with the following command (you need to have the subversion package installed for this to work):

Then edit the documentation/rosegarden/rosegarden-manual.$CC.po (where you replace $CC with your language code). There are many tools for translating available, we suggest to use lokalize.

Then you either commit the file directly to Subversion (if you have the rights to do so) or send the file to the mailinglist.

To update your local copy of the repository use the following command inside the debian-edu-doc directory:

Read /usr/share/doc/debian-edu-doc-en/README.rosegarden-manual-translations to find information how to create a new PO file for your language if there is none yet, and how to update translations. If you are new to Subversion, look at the Version Control with Subversion, it has a chapter on the basic workflow with Subversion.

Please report any problems.

Copyright (C) 2008, 2009 Alf Tonny Bätz < alfton@gmail.com > and others, see the Copyright chapter for the full list of copyright owners.

This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.

Version 2, June 1991

Copyright (C) 1989, 1991 Free Software Foundation, Inc. 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA. Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.

0. This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The "Program", below, refers to any such program or work, and a "work based on the Program" means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term "modification".) Each licensee is addressed as "you".

Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does.

1. You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy of this License along with the Program.

You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee.

2. You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions:

These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it.

Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Program.

In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License.

3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following:

The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable.

If distribution of executable or object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code.

4. You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.

5. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it.

6. Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License.

7. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all. For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program.

If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and the section as a whole is intended to apply in other circumstances.

It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice.

This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License.

8. If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Program under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License.

9. The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.

Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation.

10. If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally.

NO WARRANTY

11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.

12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

END OF TERMS AND CONDITIONS