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

Cuadros/períodos (16-4096)

Períodos/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

MARK!

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: set inn synth plugins you have good experience with

fixme: put on some audio plugin you have experience with

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: add devices you have experienced to work with out any problem

Devices that have been found not working for now

If everything works, it's time to take a look at the rosegarden documentation here: http://wiki.debian.org/DebianEdu/Documentation/Manuals/Rosegarden

And that was the index of the instrument, below you have the index overt the Percussive instruments (drums)

No.: representing the Programchange

Midi setup, in this case midisetup.rg file will I show you how to change settings. I will introduce you to some controllers that you will find usefully to your midi setup

With this out of the way, you have setup a structured setup of the midi segment that tells your synth/keyboard what it should do. And then you simply can export the midi to any devices you want, even mobile phone.(if the mobile supports polyphonic midi)

here you can download the finish setup file

midisetup.rg

Sometime you wish to use different sounds on your Synth/keyboard that not belong in the GM standard, then you have to use controller that take care of this. Controller 0 and 32.

This functions are taken in use if you also want drums on other tracks then 10. Example percussion effects on tracks 16, that my favorite tracks to use for this functions. Then with controller 32 on data1, and number 4 on data2, changes what track 16 should do, in this case drums. And then with program change 57, will that track change to effect kit.

Controller 0 and 32, with number 0, is gm standard, use it on tracks 1-9, 11-16

Controller 0 and 32, with number 1-127 are those different banks, used on track 1-9, 11-16

Controller 32, with number 4, are for mine synth drums, that is use for standard on track 10, and on special need on any track you to your liking.

Yamaha keyboard with Gm2/Xg have some more options, I recommend you to read the manual that gives you the complete overview of the instrument on your keyboard, and there also says what banks the instrument exist on.

Let me take one example for you:

my keyboard have a instrument on controller 0(MSB) on value 8, and in controller 32(LSB) on value 1, and last on program change 3.

so the following is,

controller 0 with value 8

controller 32 with value 1

and last the program change with value 3

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

remember that controller 0 and 32, have to come BEFORE program change.

i have included this in the standardupsetfile.

This is actually something I just found out. You use the instrument parameter to have the reverb, volume you want, and then the trick is to press a key on your keyboard when rosegarden count up for you, so you actually get one note in the count in before record. You can do this on every segment. And when you export the song to midi, the info will automatically be put inn. The only thing is, that you have to import the new midi file you made, and remove the note you don't need and save it again.

As I said, this is not necessary if you just held your project as a rosegarden file.

All synth have many sounds, and you will not get to all the sound that are available with the GM only on the "quick instrument parameter pick". So if you follow this way you can try to add your synth/keyboard as your default device, and take in use all sound that lives in your keyboard/synth. New devices are added on new releases of rosegarden, so if you not find your own device here, you can just wait to see if it show up, or you can help the rosegarden project and make the instrument indexing your self, and simply send the *.rgd file to them, and at the same time join the rosegarden list: http://rosegardenmusic.com/support/lists/

It's very important to be strict when there comes to where you placing your recording live instruments, vocals. Because without that you will after a wile get problem to find what files you are working on. it's not impossible, but without any structure on it, you will use allot of time find it. So lets say you have made your self a new midi melody "shallala", and you want to record your vocal on it, then you just remember to make a director that has the same name as your melody, and place your recorded audio in there.

Choose --> "composition" ---> and then "edit document properties"

You want to tell everybody the you have made this tune, so belove you see how you can add what the song name is, who has composed it

This functions have several possibility, after a played segment you sometime miss the beat, here is where the Grid Quantize comes in the picture. It's usefully to get note right on the beat automatically.

To use this the right way, can save you from a lot of work. You have to try out different way, there are always the possibility to undo the quantize if not goes as intended. So there is only just to try again with a different setting on the base grid unit. You have to try out different setting, and you will find one that fits you needs best. There are many possibility.

with this you with one keystroke change a staccato played part to legato.

and other Quantizer that you will find usefully are heuristic notation quantizer. This help you to make your played note to the right length. This is mostly used to fixing up on the notations preview. And make the note more easy to read for the musician.

As you can see have this method, changed the length on the note to right length for and 16 note, and that should be played staccato. And that will changed notations to the better in the Score Editor.

Number 1 show you how the notations was before Quantize, and number 2 is after. Number 2 are more easy for the musician to read then number 1. And at the same time is number 1 more confusing with 32 quanted notes, and some different rest note. Number 2 is more clean, and will at mostly be played the way I intended it to be played. There is one thing that it's sound great on midi, but if you want public your notations to orchestra, band, you have to take you time and clean up your notes. That was and short introductions to use of Matrix edit.

This guide show you how to set in usefully informations to the musician how you compositions should be played, Tempo, volume and what accord. That only a part of this tool, there are still much more. The picture show you how to make the note bind together, and how to put a crescendo, decrescendo on the notations.

If you look at the right menu, there are many possibility to improve the informations on the notations, the only thing you have to remember is to mark those note this info should be apart of.

If you look on the left menu, you can put manually note, rest on you notations, you can also change the clef on the notations, below you see how.

Take in use the Interpret functions

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).

There are 2 ways to put note in score editor, first way is the manually putting notes.

And you have the Step recording, that one is my favorite. And it could be a nice way for the student to learn what note and what key on the synth/keyboard the student have to push to get the note.

If you right click on the line there you want the tempo change, let's say with number 3, and then chose 'Insert Tempo Change' a dot with number 3 will shown up. And then left click and hold down after number 3, you can easy change tempo only by drag up and down.

This simply make a tempo change there you are positions on the song.

this is nice to use if you want a gradient tempo change, or reduce.

here you simply manually can type in what tempo you want, this is the best to use if you are after a special tempo, the drag functions are good to, but not so precise.

this give you the possibility to change the beat on you melody, on my example, I have started up the song with 4/4 beat, and after the tempo change I have changed the song to 3/4 beat (wals).

With this you manually can go into all you tempo change and beat change, and change to your liking

and the after you have done a successfully record of you midi song, you can add on some singing, real guitars, and so on, you have to be creative.:)

Here you have and example of music piece that have been made on rosegarden, I have got a friend of mine to play guitars.

arr/melody: Alf Tonny Bätz. Guitarist: Bjørn Nygård

Mp3 version

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

Midi version

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

To make this work at the same time you have audacity, rosegarden runing, you have to configure swami to use jack as a sound connector:

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

So now you are ready to start create your own sound to use with you musik project.

How to make a sound? Here you have to use audacity to record something, for example scream, word, or some real instruments, when you have cleaned up your new sound, you can export this as and WAV file, and import this into swami. In swami you can connect that sound to a program change number, and at last export your new sound as an SF2 file, and use fluidsynth-DSSI-plugin in rosegarden and take in use your brand new sound. Isn't that cool?

So lets go into this step by step.

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

As in many free software projects, translations of this document are kept in PO files. More information about the process can be found in usr/share/doc/debian-edu-doc-en/README.rosegarden-manual-translations for more information on this. The Git repository (see below) contains this file too. Take a look there if you want to help translating this document.

To commit your translations you need to be a member of the Alioth project debian-edu. If your Alioth username differs from your local one, create or edit ~/.ssh/config. There should be an entry like:

Host git.debian.org
User <your-alioth-username>

Then check out the debian-edu-doc source using ssh access: git clone git+ssh://git.debian.org/git/debian-edu/debian-edu-doc.git

If you only want to translate, you just need to check out some files from from Git (which can be done anonymously) and create patches. Please file a bug against the debian-edu-doc package and attach the PO file to the bugreport. You can find some instructions on how to submit bugs here.

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

Then edit the file documentation/rosegarden/rosegarden-manual.$CC.po (replacing $CC with your language code). There are many tools for translating available; we suggest using lokalize.

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

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 isn't one yet, and how to update translations.

Please keep in mind that this manual is still under development, so don't translate any string which contains " FIXME".

Basic information about Alioth (the host where our Git repository is located) and Git is available at http://wiki.debian.org/Alioth/Git.

If you are new to Git, look at the Pro Git book; it has a chapter on the recording changes to the repository. Also you might want to look at the gitk package that provides a GUI for Git.

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