| Both sides previous revision
Previous revision
Next revision
|
Previous revision
Next revision
Both sides next revision
|
frequently_asked_questions [2009/12/01 02:42]
michael |
frequently_asked_questions [2010/10/04 10:35]
127.0.0.1 external edit |
| ====I've followed all your instructions but I still don't hear any sound==== | ====I've followed all your instructions but I still don't hear any sound==== |
| |
| If you've done everything we've suggested above then you can check what devices the sequencer is seeing by running the Rosegarden sequencer up by itself. Try: | FIXME This section needs to be rewritten completely. |
| | |
| | =====Improving Performance===== |
| | |
| | ====I get drop outs or xruns with JACK. How do I improve performance?==== |
| | |
| | The short answer to this is with care and with some luck. There are various recipes for improving JACK performance. Some are more labour intensive than others. Ask on the rosegarden-user and rosegarden-devel lists for the latest advice and also keep an eye on jackit-devel for more JACK tips. |
| | |
| | |
| | to add somewhere appropriate: DSSI: no localhost |
| | |
| | =====Customizing Rosegarden===== |
| | |
| | ====How do I modify keyboard shortcuts?==== |
| | |
| | The is no simple method. The current work around requires some command line calls, a text editor and a bit of searching. Rosegarden shortcuts are defined in XML files with extensions .rc which are located in |
| <code> | <code> |
| $ rosegardensequencer | <build-tree-path>/data/rc/ |
| </code> | </code> |
| and examine the output of the screen. The output for JACK and ALSA for an SBLive! should look something like this: | |
| <code> | |
| rosegardensequencer: created plugin manager | |
| MappedAudioPluginManager::discoverPlugins - discovering plugins | |
| Rosegarden 4-0.9 - AlsaDriver - alsa-lib version 0.9.3 | |
| AlsaDriver::jackSampleRate - sample rate changed to 44100 | |
| AlsaDriver::createJackInputPorts - adding input port 1 | |
| AlsaDriver::createJackInputPorts - adding input port 2 | |
| AlsaDriver::createJackInputPorts - getting ports | |
| AlsaDriver::createJackInputPorts - found 2 JACK physical inputs | |
| AlsaDriver::createJackInputPorts - connecting from "alsa_pcm:capture_1" to "rosegarden:in_1" | |
| AlsaDriver::createJackInputPorts - connecting from "alsa_pcm:capture_2" to "rosegarden:in_2" | |
| AlsaDriver::initialiseAudio - JACK sample rate = 44100Hz | |
| AlsaDriver::initialiseAudio - added output port 1 (left) | |
| AlsaDriver::initialiseAudio - added output port 2 (right) | |
| AlsaDriver::initialiseAudio - found 2 JACK physical outputs | |
| AlsaDriver::initialiseAudio - connecting from "rosegarden:out_1" to "alsa_pcm:playback_1" | |
| AlsaDriver::initialiseAudio - connecting from "rosegarden:out_1" to "alsa_pcm:playback_2" | |
| AlsaDriver::initialiseAudio - JACK playback latency 0.092879R | |
| AlsaDriver::initialiseAudio - JACK record latency 0.046439R | |
| AlsaDriver::initialiseAudio - initialised JACK audio subsystem | |
| |
| ALSA Client information: | where <build-tree-path> is the path to where Rosegarden is installed. |
| |
| 64,0 - (Rawmidi 0 - EMU10K1 MPU-401 (UART), EMU10K1 MPU-401 (UART)) (DUPLEX) [ctype 2, ptype 2, cap 127] | The hardest part is deciding which .rc file contains the shortcuts that need modified. Look through the rc directory to find good candidates files. |
| 65,0 - (Emu10k1 WaveTable, Emu10k1 Port 0) (WRITE ONLY) [ctype 2, ptype 2078, cap 66] | |
| 65,1 - (Emu10k1 WaveTable, Emu10k1 Port 1) (WRITE ONLY) [ctype 2, ptype 2078, cap 66] | |
| 65,2 - (Emu10k1 WaveTable, Emu10k1 Port 2) (WRITE ONLY) [ctype 2, ptype 2078, cap 66] | |
| 65,3 - (Emu10k1 WaveTable, Emu10k1 Port 3) (WRITE ONLY) [ctype 2, ptype 2078, cap 66] | |
| |
| Creating device 0 in Play mode for connection 65:0 Emu10k1 Port 0 (write) | Here is a sample of the process needed to update the Transport play shortcuts to include the Space bar: |
| Default device name for this device is MIDI soundcard synth | |
| Creating device 1 in Play mode for connection 65:1 Emu10k1 Port 1 (write) | |
| Default device name for this device is MIDI soundcard synth 2 | |
| Creating device 2 in Play mode for connection 65:2 Emu10k1 Port 2 (write) | |
| Default device name for this device is MIDI soundcard synth 3 | |
| Creating device 3 in Play mode for connection 65:3 Emu10k1 Port 3 (write) | |
| Default device name for this device is MIDI soundcard synth 4 | |
| Creating device 4 in Play mode for connection 64:0 Rawmidi 0 - EMU10K1 MPU-401 (UART) (duplex) | |
| Default device name for this device is MIDI external device | |
| Creating device 5 in Record mode for connection 64:0 Rawmidi 0 - EMU10K1 MPU-401 (UART) (duplex) | |
| Default device name for this device is MIDI hardware input device | |
| Record client set to (64, 0) | |
| |
| AlsaDriver::initialiseMidi - initialised MIDI subsystem | * Type at the command line: |
| | <code> |
| | $ mkdir -p ~/.local/share/rosegarden/rc |
| | $ cp <build-tree-path>/data/rc/rosegardenmainwindow.rc ~/.local/share/rosegarden/rc/ |
| | </code> |
| | Replace <build-tree-path> with the path to the installation directory. |
| |
| rosegardensequencer: RosegardenSequencer - started OK | * Open ~/.local/share/rosegarden/rc/rosegardenmainwindow.rc in a text editor. |
| | * Change the line: |
| | <code> |
| | <Action name="play" text="&Play" icon="transport-play" shortcut="Enter, Media Play, Ctrl+Return" shortcut-context="application" /> |
| </code> | </code> |
| Note the ALSA device list shows the external MIDI port and the wavetable on-board synth devices. If you're using a soft synth, you should see it here too. All of these will be available in the drop-down Instrument list inside Rosegarden. | |
| |
| You can also reach this sequencer status information by using the application itself. Go to: Settings -> Configure Rosegarden -> Sequencer status -> Details.... | to |
| |
| | <code> |
| | <Action name="play" text="&Play" icon="transport-play" shortcut="Enter, Media Play, Ctrl+Return, Space" shortcut-context="application" /> |
| | </code> |
| |
| | and the line |
| |
| =====Improving Performance===== | <code> |
| | <Action name="recordtoggle" text="P&unch in Record" icon="transport-record" shortcut="Space" shortcut-context="application" /> |
| | </code> |
| |
| ====I get drop outs or xruns with JACK. How do I improve performance?==== | to |
| |
| The short answer to this is with care and with some luck. There are various recipes for improving JACK performance. Some are more labour intensive than others. Ask on the rosegarden-user and rosegarden-devel lists for the latest advice and also keep an eye on jackit-devel for more JACK tips. | <code> |
| | <Action name="recordtoggle" text="P&unch in Record" icon="transport-record" shortcut="" shortcut-context="application" /> |
| | </code> |
| |
| | Note: Both need changed, otherwise the second one overrides the first. |
| | |
| | * Save the file. |
| | * Run Rosegarden at try to shortcut. |
| | |
| | This is a complicated example, but many more are much less complicated. For a list of shortcut key names see: [[http://doc.trolltech.com/4.6/qkeysequence.html]] |
| |
| to add somewhere appropriate: DSSI: no localhost | |
