| Both sides previous revision
Previous revision
Next revision
|
Previous revision
|
frequently_asked_questions [2009/12/01 02:35]
michael |
frequently_asked_questions [2022/05/06 16:07] (current)
|
| |
| ======Frequently Asked Questions for Rosegarden "Thorn" and Later====== | ======Frequently Asked Questions for Rosegarden 10.02 and Later====== |
| | |
| Rosegarden 10.02, codename "Thorn" is in the early alpha stage, and will be released in February of 2010. | |
| | |
| For questions about Rosegarden 1.x, please see the [[dev:1.7.x_faq|Old FAQ]]. (**Note that development on 1.7.x has been suspended, and we are no longer accepting patches or translations updates against that line of code.**) | |
| |
| =====General questions===== | =====General questions===== |
| |
| ====How to get a stack trace for a crash==== | ====How to get a stack trace for a crash==== |
| | |
| | First, make sure you are running a version of rosegarden that was built with debugging turned on. |
| | |
| | <code> |
| | -DCMAKE_BUILD_TYPE=Debug |
| | </code> |
| | |
| | Without debugging, there will be no symbols in the binary, and the backtrace will be useless. You'll likely need to build rosegarden on your own to get a debug version. Instructions can be found here: [[dev:Building Rosegarden from Source]] |
| | |
| Open a terminal window, and check to ensure that applications will be able to produce core dumps. The exact command and syntax may vary from shell to shell, but for bash it is ''ulimit -a'': | Open a terminal window, and check to ensure that applications will be able to produce core dumps. The exact command and syntax may vary from shell to shell, but for bash it is ''ulimit -a'': |
| |
| </code> | </code> |
| |
| Now start rosegarden from the command line, and reproduce the crash. You should now have a core file in your current directory. The core file is either named **core** or **core.<//number//>**. | Now start a **debug version** of rosegarden from the command line, and reproduce the crash. You should now have a core file in your current directory. The core file is either named **core** or **core.<//number//>**. |
| |
| Run ''gdb'': | Run ''gdb'': |
| ====Build requirements===== | ====Build requirements===== |
| |
| Please see the [[dev:contributing|contributing]] page for detailed dependency and build information. | Please see the [[dev:Building Rosegarden from Source]] page for detailed dependency and build information. |
| |
| |
| |
| In order to be fully functional and provide the optimal user experience, | In order to be fully functional and provide the optimal user experience, |
| Rosegarden requires the following external applications. We suggest listing | Rosegarden requires the following external applications. |
| them as your distro's equivalent of "recommends" level dependencies. (Yes, this | |
| is a long list, and yes, we really do use all of these for something.) | |
| |
| * perl | |
| * bash | * bash |
| * qsynth AND fluid-soundfont-gm* OR timidity AND freepats* | * available, functioning ALSA General MIDI soft synth (QSynth, TiMidity++, etc.) with soundfont (Fluid-Soundfont, Freepats, etc.) |
| * lilypond | * lilypond |
| * ocular OR acroread OR kpdf OR evince | * ocular OR acroread OR evince |
| * kprinter OR gtklp OR lpr OR lp | * gtklp OR lpr OR lp |
| * jackd | * jackd |
| * sox | |
| * sndfile-resample | |
| * flac | * flac |
| * oggdec | * wavpack/wvunpack |
| * mpg321 | |
| * libxml-twig-perl | |
| * qjackctl | * qjackctl |
| * DSSI plugins (any your distro carries) | * DSSI plugins (any available) |
| * LADSPA plugins (any your distro carries) | * LADSPA plugins (any available) |
| | |
| [*] the key here being that either softsynth should come with an installed | |
| soundfont or patchset in order that it can play General MIDI as configured | |
| "out of the box" | |
| |
| =====Main Window and Segment Editing===== | =====Main Window and Segment Editing===== |
| ====Can I edit all the segments at once in the matrix editor?==== | ====Can I edit all the segments at once in the matrix editor?==== |
| |
| Yes! (Probably? This is likely to be working when we release.) | Yes! |
| |
| |
| ====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: | |
| | where <build-tree-path> is the path to where Rosegarden is installed. |
| | |
| | The hardest part is deciding which .rc file contains the shortcuts that need modified. Look through the rc directory to find good candidates files. |
| | |
| | Here is a sample of the process needed to update the Transport play shortcuts to include the Space bar: |
| | |
| | * Type at the command line: |
| <code> | <code> |
| rosegardensequencer: created plugin manager | $ mkdir -p ~/.local/share/rosegarden/rc |
| MappedAudioPluginManager::discoverPlugins - discovering plugins | $ cp <build-tree-path>/data/rc/rosegardenmainwindow.rc ~/.local/share/rosegarden/rc/ |
| Rosegarden 4-0.9 - AlsaDriver - alsa-lib version 0.9.3 | </code> |
| AlsaDriver::jackSampleRate - sample rate changed to 44100 | Replace <build-tree-path> with the path to the installation directory. |
| 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: | * 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> |
| |
| 64,0 - (Rawmidi 0 - EMU10K1 MPU-401 (UART), EMU10K1 MPU-401 (UART)) (DUPLEX) [ctype 2, ptype 2, cap 127] | to |
| 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) | <code> |
| Default device name for this device is MIDI soundcard synth | <Action name="play" text="&Play" icon="transport-play" shortcut="Enter, Media Play, Ctrl+Return, Space" shortcut-context="application" /> |
| Creating device 1 in Play mode for connection 65:1 Emu10k1 Port 1 (write) | </code> |
| 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 | and the line |
| |
| rosegardensequencer: RosegardenSequencer - started OK | <code> |
| | <Action name="recordtoggle" text="P&unch in Record" icon="transport-record" shortcut="Space" 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="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. |
| |
| =====Improving Performance===== | * Save the file. |
| | * Run Rosegarden at try to shortcut. |
| |
| ====I get drop outs or xruns with JACK. How do I improve performance?==== | 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]] |
| |
| 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. | ====How do I prevent Rosegarden splitting long notes when recording?==== |
| |
| | There is a setting for that: |
| | |
| | Edit -> Preferences -> Notation -> [ ] When ... split-and-tie long ... |
| |
| to add somewhere appropriate: DSSI: no localhost | |
