Differences

This shows you the differences between two versions of the page.

--- rosegarden [2015/06/27 07:55]
slackermedia created
+++ rosegarden [2021/06/03 19:48] (current)
@@ Line 1: / Line 1: @@
-[[{arrowp.png|border:0;background:none;width:0;display:inline-block;position:absolute;top:0;left:0;}render|]]
-[[{arrown.png|border:0;background:none;width:0;display:inline-block;position:absolute;top:0;margin-left:2.5em;}screenwriter|]]
 ======Rosegarden======
@@ Line 58: / Line 56: @@
 In order to compose music on a computer and have it play the music back as a complete musical work, you must use some kind of sequencer if only to get the different tracks to start at the same time. Rosegarden is a sequencer, with the ability to sequence MIDI events, route MIDI channels, place audio files, perform rudimentary mixing, apply effects, and more, making it a full fledged Digital Audio Workstation (DAW).
-==== Rosegarden with JACK ====
+===== Usage =====
 To use Rosegarden, you must run [[jack|JACK]], the audio subsystem that acts as a sort of patchbay for your system. Since not all applications send audio to JACK, JACK is used only on an as-needed basis. The order of launching your audio rig, therefore, is:
@@ Line 67: / Line 65: @@
   - Launch Rosegarden
-When Rosegarden first loads, it routes most of the important connections for you. These are:
+When Rosegarden first loads, it routes most of the important connections for you. The MIDI connections are:
-Your controller connects to the **MIDI Thru** of your MIDI system.
+  * Your controller connects to the **MIDI Thru** of your MIDI system.
-Your controller also connects to the **MIDI In** of Rosegarden.
+  * Your controller also connects to the **MIDI In** of Rosegarden.
-The **MIDI Out** of Rosegarden connects to the **MIDI In** of your controller.
+  * The **MIDI Out** of Rosegarden connects to the **MIDI In** of your controller.
+The audio connections:
-To begin a new project, select **File** menu → **New** and choose from the list of template projects available. The templates provide a few convenience tracks already in the Rosegarden workspace, but otherwise any template will do, as they can be adjusted at any time. The ''default'' template is the most basic: it creates a Master Out channel and leaves the rest up to you.
+  * System capture connects to Rosegarden **Record In**
+  * **Master Out** of Rosegarden connects to **System Playback**
-Rosegarden auto-connects its Master Out to the System Playback output in JACK, so you're all set to make music.
+[{{ rose_routing.jpg | The default routing of Rosegarden.}}]
-===== Audio =====
+For greater control, go to the **Edit** menu → **Preferences** → **Audio**. Place a tick in the box next to **Create JACK Outputs for individual audio instruments**, and optionally **for submasters**. These will provide, upon future launches, a JACK output port for each track in Rosegarden so that you route each track as you please.
-Rosegarden can handle imported audio files as well as MIDI data. To bring in an audio file, there must be a track ready to accept the audio. To create a new track, right-click in the left **Track** area, or click the **Edit** menu → **Add Track**, and select **Add Wave Track**.
-Give your new track a name by double-clicking on the track label, and typing a name into the text field.
+===== Audio =====
-With the newly create Wave Track selected, import your audio file via the **File** menu → **Import Wave File**.
+Rosegarden can handle imported audio files as well as MIDI data. To import an audio file:
-{{ muse_wav.jpg }}
-Audio tracks can be edited as you would expect; splice the track with the **Cutter** tool from the top menu bar, erase clips with the **Eraser** tool, repair cuts with **Glue**, and move clips around with the standard **Arrow** tool.
-===== MIDI =====
-Rosegarden is a full-featured DAW, so it has a plugin structure that allows you to use MIDI instruments and effects without leaving the Rosegarden, but you since Rosegarden is a JACK-aware application, there is the added flexibility of being able to use stand-alone synths and effects as well.
-==== Plugins ====
-The advantage to using plugins is that all routing information and synth settings are saved along with the DAW project itself. If you confine your music-making to plugins, you will never have to take snapshots of your JACK setup or save any session files other than that of the DAW itself.
-To add a soft synth as a plugin to Rosegarden, first add a new MIDI track.
+  - Select an audio track in the Rosegarden workspace. The audio tracks are preceded by a red light and are labelled as "Untitled Audio" in their track name field.
+  - Click on **File** → **Manage Audio Files**.
+  - In the **Audio File Manager** window, click the **Add Audio File** icon in the toolbar, or select **File** menu → **Add Audio File**.
+  - Choose audio files from your system.
+  - From the list of files you have added in the **Audio File Manager** window, select one and click the **Insert into Selected Audio Track**.
-To create a new track, right-click in the left **Track** area, or click the **Edit** menu → **Add Track**, and select **Add MIDI Track**.
+[{{ rose_audio.jpg?666 | The Audio File Manager in Rosegarden. }}]
 Give your new track a name by double-clicking on the track label, and typing a name into the text field.
-A MIDI track houses nothing but MIDI data. That's all it is; an in-application representation of a MIDI file. So in order for your MIDI data (or spontaneous MIDI signals, more likely) to be of any use, you must have a destination for it. In this example, we will use a plugin.
+Audio tracks can be edited as you would expect; splice the track with the **Split** tool from the top menu bar, erase clips with the **Eraser** tool, repair cuts with **Join**, and move clips around with the standard **Arrow** tool. All of these tools are available in a pop-menu that appears upon a right-click, or via keyboard shortcuts.
-To create a new plugin track, right-click in the left **Track** area, or click the **Edit** menu → **Add Track**, and select **Add Synth Track**.
+[{{ rose_edit.jpg | Audio clips in Rosegarden tracks. }}]
-{{ muse_synth.jpg }}
+Rosegarden uses [[audacity|Audacity]] for in-depth waveform editing. To open an audio region in Audacity, right-click on the region and select **Open in default editor** from the contextual menu, or just press ''Return''.
-Rosegarden has access to MESS (its own plugin format), DSSI (a common plugin format in Linux DAWs), LADSPA (a common Linux plugin format), and LADSPA v2 (LV2). For this example, use the FluidSynth DSSI plugin (you should have this installed as part of the Slackermedia queue file).
-Next, the MIDI track and the synth plugin must be associated with one another; the MIDI data is useless if it's not directed at a listening MIDI port.
+===== MIDI =====
-Click on the MIDI track; this should reveal a **TrackInfo** panel on the left. If not, click the **TrackInfo** button in the lower left corner of the application window.
+Rosegarden is a full-featured DAW, so it has a plugin structure that allows you to use MIDI instruments and effects without leaving Rosegarden, but since Rosegarden is a JACK-aware application, there is the added flexibility of being able to use stand-alone synths and effects as well.
-In the **TrackInfo** panel, set the **Output Port** to the port occupied by the plugin (in this case, FluidSynth).
+==== Plugins ====
-{{ muse_port.jpg }}
+The advantage to using plugins is that all routing information and synth settings are saved along with the DAW project itself. If you confine your music-making to plugins, you will never have to take snapshots of your JACK setup or save any session files other than that of the DAW itself.
-Verify your MIDI routing:
+To add a soft synth as a plugin to Rosegarden, right click on a MIDI track and set it to **Synth Plugin** → **Synth Plugin #1**. This points any MIDI data on that track to whatever plugin occupies the **Synth Plugin #1** slot.
-  * The controller node should be connected to its counterpart within the Rosegarden node (Rosegarden probably did this automatically for you)
+[{{ rose_synth.jpg | Set a track to **Synth Plugin** to use a soft synth. }}]
-  * The audio output of Rosegarden should be connected to the **System Playback** node so that your speakers or headphones receive the audio for playback
-{{ muse_routing.jpg }}
+A MIDI track houses nothing but MIDI data. That's all it is; an in-application representation of a MIDI file. In order for your MIDI data (or spontaneous MIDI signals) to be of any use, you must have a destination for it.
-At this point, all MIDI signals are being routed from your external USB controller to Rosegarden, and within Rosegarden the MIDI data is being sent to your MIDI track (all MIDI tracks in Rosegarden receive all MIDI signals by default). The only thing left is to configure the synthesizer itself.
+To load a plugin in the **Synth Plugin** slot, select the MIDI track if it is not already selected, and click the **no synth** button in the **Instrument Parameters** panel on the left.
-Each synthesizer will be different, but no matter what you are using, there is some mechansism to choose what bank and patch is loaded. To get to the synthesizer interface, right-click on the name of the plugin in the **Port** column of the track panel and choose **Show Native GUI**.
+[{{ rose_plugin.jpg | Plugin parameters. }}]
-{{ muse_gui.jpg }}
+Choose a bank and patch for the synth in the plugin window that appears.
-Once you have a bank loaded, arm the MIDI track by clicking on the red **Armed** button on the far left of the track panel.
+[{{ rose_patch.jpg | Choose your weapon. }}]
-{{ muse_arm.jpg }}
 Try playing a few notes on your USB controller; you should hear the sounds over your speakers.
@@ Line 142: / Line 129: @@
 ==== Stand-Alone Synth ====
-The advantage to using stand-alone synths is that it keeps your studio modular, letting you swap out what DAW you use, what sequencer you use, every last detail of how things are routed, and so on. Using tools external to Rosegarden means that you must take snapshots of your JACK setup and save all session files individually, as nothing outside of Rosegarden can be saved as Rosegarden settings.
+The advantage to using stand-alone synths is that it keeps your studio modular, letting you swap out what DAW you use, what sequencer you use, every last detail of how things are routed, and so on. However, using tools external to Rosegarden means that you must take snapshots of your JACK setup and save all session files individually, as nothing outside of Rosegarden can be saved as Rosegarden settings.
-To control a stand-alone synth from Rosegarden, first add a new MIDI track.
+A MIDI track houses nothing but MIDI data. That's all it is; an in-application representation of a MIDI file. In order for your MIDI data (or spontaneous MIDI signals, more likely) to be of any use, you must have a destination for it. In this example, use Yoshimi, which was installed as part of the Slackermedia queue file.
-To create a new track, right-click in the left **Track** area, or click the **Edit** menu → **Add Track**, and select **Add MIDI Track**.
-Give your new track a name by double-clicking on the track label, and typing a name into the text field.
-A MIDI track houses nothing but MIDI data. That's all it is; an in-application representation of a MIDI file. So in order for your MIDI data (or spontaneous MIDI signals, more likely) to be of any use, you must have a destination for it. In this example, use Yoshimi, which was installed as part of the Slackermedia queue file.
 Launch Yoshimi from the **K Menu** or from a terminal. Yoshimi automatically creates a node in [[patchage|Patchage]] or a listing in [[qjackctl|QJackCtl]].
@@ Line 156: / Line 137: @@
 Next, the MIDI track and the external synth plugin must be associated with one another; the MIDI data is useless if it's not directed at a listening MIDI port.
-Click on the MIDI track; this should reveal a **TrackInfo** panel on the left. If not, click the **TrackInfo** button in the lower left corner of the application window.
+Part of this process happens within Rosegarden, and part is purely a JACK function.
-In the **TrackInfo** panel, set the **Output Port** to the port associated with the synth you are targeting (in this example, Yoshimi).
+Starting with the routing:
-{{ muse_xport.jpg }}
+  - Connect the Yoshimi **Audio Out** to **System Playback**.
+  - Connect a **System Capture** MIDI Capture port to Yoshimi. The number of the port may vary depending on your setup, and Rosegarden creates several MIDI ports for use as "General MIDI" outputs. A little trial and error might be called for, but start from the bottom and connect the final MIDI Capture to Yoshimi first. Try playing a few notes; if there is no sound, try a different port.
-Verify your MIDI routing:
+[{{ rose_xroute.jpg | Routing MIDI. }}]
-  * Connect the **System Capture** controller node to its counterpart in the Rosegarden node
+Once you have the appropriate MIDI signals routed to your synth, go back into Rosegarden.
-  * Connect the external synth node to the Yoshimi **MIDI In**
-  * Connect the audio output of Yoshimi to the **System Playback** node
-At this point, all MIDI signals are being routed from your external USB controller to Rosegarden, and within Rosegarden the MIDI data is being sent to your MIDI track (all MIDI tracks in Rosegarden receive all MIDI signals by default) and also through into the Yoshimi synth.
+Select the first MIDI track in Rosegarden (MIDI tracks have a yellow light next to them, and are labelled "untitled"). Right-click on the track label and verify that it is set to **General MIDI** → **General MIDI Device 1**. Ignore the "Acoustic Piano" label; it's a General MIDI label which does not apply to raw MIDI signals.
-{{ muse_xrouting.jpg }}
+[{{ rose_midi.jpg | A MIDI track in Rosegarden. }}]
-The only thing left is to configure the synthesizer itself.
-Each synthesizer is different, but no matter what you are using, there is some mechanism to choose what bank and patch is loaded. Switch over to the synthesizer on your desktop and configure it.
+===== Recording MIDI =====
-Once you have a bank loaded, arm the MIDI track in MuSE by clicking on the red **Armed** button on the far left of the track panel.
+You don't need to connect the MIDI track to any synthesizer to record MIDI data (although it usually helps to hear what you are playing). You don't even need to record within Rosegarden itself. Since a MIDI track simply holds MIDI data, you can take existing MIDI files from either other sequencers or from MIDI repositories online and load them into Rosegarden, using them to drive your synths.
-{{ muse_arm.jpg }}
+To record MIDI into the selected track, arm the MIDI track you want to record to by clicking the yellow **Armed** button on the far left of the track panel.
-Try playing a few notes on your USB controller; you should hear the sounds over your speakers.
+[{{ rose_arm.jpg | Arm a track for recording. }}]
+When ready, click the **Record** button in the transport window. Recording begins immediately and records each key press on your controller.
-==== Playing and Recording MIDI ====
+==== Manual Entry of MIDI ====
-Recording MIDI input occurs on the MIDI track (not the plugin track). You don't need to connect the MIDI track to any synthesizer to record MIDI data (although it usually helps to hear what you are playing).
+If you don't want to record anything, but want an empty region for manual entry, select the **Pencil** tool from the toolbar or press ''F3''. With the pencil tool, click in the track and an empty region appears.
-You don't even need to record within Rosegarden itself. Since a MIDI track simply holds MIDI data, you can probably take existing MIDI files from either other sequencers or from MIDI repositories online and load them into Rosegarden, using them to drive your synths.
-To record your own MIDI files, arm the MIDI track you want to record to by clicking the red **Armed** button on the far left of the track panel.
+==== Editing MIDI ====
-{{ muse_arm.jpg }}
+Once you have a MIDI region in a track, edit the MIDI data (or add more) in a "piano roll" editor; click on a MIDI region and press ''m'' on your keyboard, or click the **Open in Matrix Editor** icon in the toolbar.
-When ready, click the **Record** button in the transport window.
+[{{ rose_pianoroll.jpg?666 | The familiar, comfortable piano roll interface. }}]
-The record button triggers a **Save** dialogue; since you'll be recording MIDI data, you must create a file for it to be saved into. It's usually best to save your MIDI files in a project-specific directory so that if you archive the project later, all of the files that it needs to work will go along with it. See [[planter|Planter]] for Slackermedia's contextual project management tool, or create your own solution.
-Once you have created a file for your MIDI data, press the **Play** button in the transport window. Recording begins immediately and records each key press on your controller.
-{{ muse_transport.jpg }}
-Once you have a MIDI region in a track, you can edit the MIDI data (and add more) in a "piano roll" editor; right-click on a MIDI region and choose **Piano Roll**, or select the MIDI region and press ''ctrl'' ''e''.
-{{ muse_pianoroll.jpg?666 }}
 ===== Effects =====
-Effects, like synths, can be external to Rosegarden or they can be plugins that occur within Rosegarden. The latest versions of Rosegarden have access to DSSI, LADSPA, and LV2 effects, so there's little reason to use external effect units. In fact, using inbuilt effects gives you finer control over which track gets what effect, so mostly you'll probably want to default to them. But a few effects are only stand-alone, so you can use external effects as needed; it's just a matter of routing the audio properly.
+Effects, like synths, can be external to Rosegarden or they can be plugins that occur within Rosegarden. If you use an external effect, just route the audio from a track through the effect, and then back into the **System Playback**.
-{{ muse_rakarrack.jpg }}
+[{{ rose_fxroute.jpg | Routing effects. }}]
-To use plugin effects from within Rosegarden, press ''F10'' to view the main **Mixer** window, or select **View** menu → **Mixer A**.
+To use plugin effects from within Rosegarden, select a MIDI or Audio track. In the **Instrument Parameters** panel on the left, click a **no plugin** button and choose an effect to load.
-In the **Mixer** window, right-click on a plugin slot of a track you want to route through an effect and choose **new** from the contextual menu.
+[{{ rose_effect.jpg | Defining an effect plugin. }}]
-{{ muse_effect.jpg }}
-To configure the effect unit you have added, just double-click on the effect name in the plugin slot. Either a native or a Rosegarden GUI will appear, depending on what is available (a native GUI is given preference).
 ===== Exporting / Bouncing =====
-Exporting your final project to a file (in audio terms, this is usually referred to as "bouncing") requires a full, real-time playback of the selected area of your project.
+Exporting your final project to a file (in audio terms, this is usually referred to as "bouncing") requires a full, real-time playback of the selected area of your project and a recording application. The easiest recording application to use with JACK is aptly named [[jackapps|Jack Capture]].
-By default, the "in" point of your playback region is the beginning of the project; it's indicated by a blue transport marker. You can move this position with a middle-click.
+By default, the "in" point of your playback region is the beginning of the project. Set an out point with the **End Loop** button in the transport window.
-To mark the "out" point, use a right-click.
+[{{ rose_io.jpg | Set an active region. }}]
-{{ muse_select.jpg }}
+The marked region is highlighted as white in the top timecode bar.
-To bounce the audio to a file, click on the **Audio** menu → **Bounce to File**.
+To begin recording, click the **record** button on Jack Capture and **Play** in the Rosegarden transport window. Let the song play all the way through, and listen carefully for any trailing reverb or echo before stopping Jack Capture.
 ===== Documentation =====
-For full details on using Rosegarden, see its documentation options at [[http://muse-sequencer.org/index.php/Support]].
+For full details on using Rosegarden, see its documentation options at [[http://www.rosegardenmusic.com]].
 <WRAP tip>
 **See Also** \\
-Ardour \\
+[[ardour|Ardour]] \\
-Audacity \\
+[[audacity|Audacity]] \\
-Jack \\
+[[jack|Jack]] \\
-LMMS \\
+[[lmms|LMMS]] \\
-Rosegarden \\
+[[muse|MusE]] \\
-Qtractor
+[[qtractor|Qtractor]]
 </WRAP>
-[[{arrown.png|border:0;background:none;width:0;display:inline-block;float:right;}screenwriter|]][[{arrowp.png|border:0;background:none;width:0;float:right;}render|]]
+<WRAP centeralign>
+<wrap fa>[[render|R]]</wrap> <wrap fa>[[start|S]]</wrap> <wrap fa>[[samplv1|Q]]</wrap>
+</WRAP>