Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
muse [2015/06/27 04:29]
slackermedia 		muse [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;​}mixxx|]] 
  
-[[{arrown.png|border:​0;​background:​none;​width:​0;​display:​inline-block;​position:​absolute;​top:​0;​margin-left:​2.5em;​}patchage|]] 
  
 ======Muse====== ======Muse======
Line 80: Line 78:
 When MusE first loads, it will offer to run some "​instrument initialization sequences"​. It is safe to accept this, and to mark it as safe for future instances. This sets up internal MusE MIDI connections,​ and can be changed at any time if you find them insufficient. When MusE first loads, it will offer to run some "​instrument initialization sequences"​. It is safe to accept this, and to mark it as safe for future instances. This sets up internal MusE MIDI connections,​ and can be changed at any time if you find them insufficient.
  
-{{ muse_init.jpg }}+[{{ muse_init.jpg ​| Let MusE set up your environment,​ unless you have reason not to. }}]
  
 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 MusE 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. 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 MusE 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.
Line 92: Line 90:
 Give your new track a name by double-clicking on the track label, and typing a name into the text field. Give your new track a name by double-clicking on the track label, and typing a name into the text field.
  
-With the newly create ​Wave Track selected, import your audio file via the **File** menu → **Import Wave File**. ​+With the newly create ​WAV Track selected, import your audio file via the **File** menu → **Import Wave File**. ​
  
-{{ muse_wav.jpg }}+[{{ muse_wav.jpg ​| Audio in a MusE track can intermingle with MIDI. }}]
  
 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. 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.
Line 116: Line 114:
 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**. ​ 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**. ​
  
-{{ muse_synth.jpg }}+[{{ muse_synth.jpg ​| Insert a synth into a MusE track. ​}}]
  
 MusE 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). MusE 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).
Line 126: Line 124:
 In the **TrackInfo** panel, set the **Output Port** to the port occupied by the plugin (in this case, FluidSynth). In the **TrackInfo** panel, set the **Output Port** to the port occupied by the plugin (in this case, FluidSynth).
  
-{{ muse_port.jpg }}+[{{ muse_port.jpg ​| Associate the synth with MIDI. }}]
  
 Verify your MIDI routing: Verify your MIDI routing:
Line 133: Line 131:
   * The audio output of MusE should be connected to the **System Playback** node so that your speakers or headphones receive the audio for playback   * The audio output of MusE should be connected to the **System Playback** node so that your speakers or headphones receive the audio for playback
  
-{{ muse_routing.jpg }}+[{{ muse_routing.jpg ​| MIDI and audio routing as seen in [[Patchage|patchage]]. ​}}]
  
 At this point, all MIDI signals are being routed from your external USB controller to MusE, and within MusE the MIDI data is being sent to your MIDI track (all MIDI tracks in MusE receive all MIDI signals by default). The only thing left is to configure the synthesizer itself. At this point, all MIDI signals are being routed from your external USB controller to MusE, and within MusE the MIDI data is being sent to your MIDI track (all MIDI tracks in MusE receive all MIDI signals by default). The only thing left is to configure the synthesizer itself.
Line 139: Line 137:
 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**. 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**.
  
-{{ muse_gui.jpg }}+[{{ muse_gui.jpg ​| Select a plugin'​s native GUI to see the plugin as designed by its programmer. ​}}]
  
 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. ​ 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. ​
  
-{{ muse_arm.jpg }}+[{{ muse_arm.jpg ​| Armed for recording. ​}}]
  
 Try playing a few notes on your USB controller; you should hear the sounds over your speakers. Try playing a few notes on your USB controller; you should hear the sounds over your speakers.
Line 168: Line 166:
 In the **TrackInfo** panel, set the **Output Port** to the port associated with the synth you are targeting (in this example, Yoshimi). In the **TrackInfo** panel, set the **Output Port** to the port associated with the synth you are targeting (in this example, Yoshimi).
  
-{{ muse_xport.jpg }}+[{{ muse_xport.jpg ​| Associate a track with external MIDI data. }}]
  
 Verify your MIDI routing: Verify your MIDI routing:
Line 178: Line 176:
 At this point, all MIDI signals are being routed from your external USB controller to MusE, and within MusE the MIDI data is being sent to your MIDI track (all MIDI tracks in MusE receive all MIDI signals by default) and also through into the Yoshimi synth. ​ At this point, all MIDI signals are being routed from your external USB controller to MusE, and within MusE the MIDI data is being sent to your MIDI track (all MIDI tracks in MusE receive all MIDI signals by default) and also through into the Yoshimi synth. ​
  
-{{ muse_xrouting.jpg }}+[{{ muse_xrouting.jpg ​| MIDI and audio routing for an external synth. ​}}]
  
 The only thing left is to configure the synthesizer itself. The only thing left is to configure the synthesizer itself.
Line 186: Line 184:
 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. ​ 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. ​
  
-{{ muse_arm.jpg }}+{{ muse_arm.jpg ​| Armed for recording. ​}}
  
 Try playing a few notes on your USB controller; you should hear the sounds over your speakers. Try playing a few notes on your USB controller; you should hear the sounds over your speakers.
Line 199: Line 197:
 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. ​ 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. ​
  
-{{ muse_arm.jpg }}+[{{ muse_arm.jpg ​| Arm a track for recording. ​}}]
  
 When ready, click the **Record** button in the transport window. When ready, click the **Record** button in the transport window.
Line 207: Line 205:
 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. 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 }}+[{{ muse_transport.jpg ​| Transport control in MusE. }}]
  
 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''​. 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 }}+[{{ muse_pianoroll.jpg?​666 ​| The classic piano roll editor. ​}}]
  
 ===== Effects ===== ===== Effects =====
Line 217: Line 215:
 Effects, like synths, can be external to MusE or they can be plugins that occur within MusE. The latest versions of MusE 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 MusE or they can be plugins that occur within MusE. The latest versions of MusE 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.
  
-{{ muse_rakarrack.jpg }}+[{{ muse_rakarrack.jpg ​| Routing for external effects. ​}}]
  
 To use plugin effects from within MusE, press ''​F10''​ to view the main **Mixer** window, or select **View** menu → **Mixer A**. To use plugin effects from within MusE, press ''​F10''​ to view the main **Mixer** window, or select **View** menu → **Mixer A**.
Line 223: Line 221:
 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. 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.
  
-{{ muse_effect.jpg }}+[{{ muse_effect.jpg?666 | Inbuilt effects in MusE. }}]
  
 To configure the effect unit you have added, just double-click on the effect name in the plugin slot. Either a native or a MusE GUI will appear, depending on what is available (a native GUI is given preference). To configure the effect unit you have added, just double-click on the effect name in the plugin slot. Either a native or a MusE GUI will appear, depending on what is available (a native GUI is given preference).
Line 235: Line 233:
 To mark the "​out"​ point, use a right-click. To mark the "​out"​ point, use a right-click.
  
-{{ muse_select.jpg }} 
  
 To bounce the audio to a file, click on the **Audio** menu → **Bounce to File**. To bounce the audio to a file, click on the **Audio** menu → **Bounce to File**.
Line 243: Line 240:
  
 For full details on using MusE, see its documentation options at [[http://​muse-sequencer.org/​index.php/​Support]]. For full details on using MusE, see its documentation options at [[http://​muse-sequencer.org/​index.php/​Support]].
- 
  
 <WRAP tip> <WRAP tip>
 **See Also** \\ **See Also** \\
-Ardour \\ +[[ardour|Ardour]] \\ 
-Audacity \\ +[[audacity|Audacity]] \\ 
-Jack \\ +[[jack|JACK]] ​\\ 
-LMMS \\ +[[lmms|LMMS]] \\ 
-Rosegarden \\ +[[rosegarden|Rosegarden]] \\ 
-Qtractor+[[qtractor|Qtractor]]
 </​WRAP>​ </​WRAP>​
  
-[[{arrown.png|border:​0;​background:​none;​width:​0;​display:​inline-block;​float:​right;​}patchage|]][[{arrowp.png|border:​0;​background:​none;​width:​0;​float:​right;​}mixxx|]]+<WRAP centeralign>​ 
 +<wrap fa>[[mixxx|R]]</​wrap>​ <wrap fa>[[start|S]]</​wrap>​ <wrap fa>​[[musescore|Q]]</​wrap>​ 
 +</​WRAP>​