Both sides previous revision
Previous revision
Next revision
|
Previous revision
|
doc:manual-en [2014/04/09 23:35] tedfelix [Overview] Minor UI updates |
doc:manual-en [2025/05/13 18:55] (current) tedfelix [Audio segments] |
Rosegarden provides three distinct ways of viewing, editing, and entering MIDI events, including a powerful notation editor that provides many advanced features not typically found in the notation facility of MIDI sequencers. Underneath these three editors, Rosegarden provides a segment-based mechanism for arranging blocks of MIDI and audio data on a canvas that brings something akin to the flexibility of a layer-based image editing program to the realm of music. | Rosegarden provides three distinct ways of viewing, editing, and entering MIDI events, including a powerful notation editor that provides many advanced features not typically found in the notation facility of MIDI sequencers. Underneath these three editors, Rosegarden provides a segment-based mechanism for arranging blocks of MIDI and audio data on a canvas that brings something akin to the flexibility of a layer-based image editing program to the realm of music. |
| |
Rosegarden is built using [[http://qt.nokia.com|Qt]] -- A cross-platform application and UI framework. It uses ALSA to provide MIDI support, and JACK for audio, both of which limit Rosegarden to Linux for the time being, but that should hopefully change in the future, with OS-X being the next most accessible platform, and Windows the most difficult to reach. | Rosegarden is built using [[http://qt-project.org/|Qt]] -- A cross-platform application and UI framework. It uses ALSA to provide MIDI support, and JACK for audio, both of which limit Rosegarden to Linux for the time being, but that should hopefully change in the future, with OS-X being the next most accessible platform, and Windows the most difficult to reach. |
| |
==== About this Manual ==== | ==== About this Manual ==== |
===== Audio segments ===== | ===== Audio segments ===== |
| |
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. | 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. |
| |
To create an audio segment, you can [[doc:manual-en#recording|record]] 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 [[audiomanager-en|audio file manager]] **File → Manage Audio Files**. | To create an audio segment, you can [[doc:manual-en#recording|record]] 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 [[audiomanager-en|audio file manager]] **File → Manage Audio Files**. |
| |
| While Rosegarden cannot edit audio waveforms on its own, it //can// launch the audio editor of your choice (e.g. Audacity) when you double-click on an audio segment. Be aware that making changes and exporting them over top of the original WAV file is **destructive**, so make backups and be careful. Also make sure you export in the format Rosegarden expects: 32-bit float. Otherwise you will hear some very unpleasantly loud noise. |
| |
===== Manipulating segments ===== | ===== Manipulating segments ===== |
===== Overview ===== | ===== Overview ===== |
| |
{{http://rosegardenmusic.com/wiki/rg-transport.png|Rosegarden's Transport window}} | {{doc:rg-transport.png|Rosegarden's Transport window}} |
| |
If the transport isn't visible, you can activate it with **Settings → Show Transport**. | If the transport isn't visible, you can activate it with **View → Show Transport**. |
| |
The transport shows the time reached by the playback pointer, in seconds by default. | The transport shows the time reached by the playback pointer, in seconds by default. |
At the top, this box shows the name of the instrument and the connection that its device is using. | At the top, this box shows the name of the instrument and the connection that its device is using. |
| |
Below that, you can see and edit the MIDI channel number and the [[/doc:bankeditordialog-en|bank and program]] 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. | Below that, you can see and edit the [[/doc:bankeditordialog-en|bank and program]] 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. |
| |
| Some devices organize their patches in terms of variations. If the device file is configured properly, you will see Program and Variation settings instead of Bank and Program. See the "Show Variation list based on MSB/LSB" setting in the [[/doc:bankeditordialog-en|Manage MIDI Banks and Programs window]] (Studio > Manage MIDI Devices > Banks...). |
| |
| The Channel setting allows you to select either "Fixed" channel assignment, where the channel will be assigned sequentially for each track, or "Auto" channel assignment, where channels will be assigned on an as-needed basis. "Auto" channel assignment can be helpful for compositions that require more than 15 instruments, but never use more than 15 at a single time. |
| |
| The "Receive external" toggle allows for easier selection of a bank/program via a MIDI device. The banks and programs tend to be rather arbitrarily organized in the bank and program dropdowns. With the "Receive external" toggle, you can use your keyboard or other MIDI device to select the bank/program. |
| |
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. | 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. |