| Both sides previous revision
Previous revision
Next revision
|
Previous revision
|
frequently_asked_questions [2009/12/01 02:46]
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. |
| |
| |
| |
| to add somewhere appropriate: DSSI: no localhost | 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> |
| | <build-tree-path>/data/rc/ |
| | </code> |
| | |
| | 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> |
| | $ 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. |
| | |
| | * 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> |
| | |
| | to |
| | |
| | <code> |
| | <Action name="play" text="&Play" icon="transport-play" shortcut="Enter, Media Play, Ctrl+Return, Space" shortcut-context="application" /> |
| | </code> |
| | |
| | and the line |
| | |
| | <code> |
| | <Action name="recordtoggle" text="P&unch in Record" icon="transport-record" shortcut="Space" shortcut-context="application" /> |
| | </code> |
| | |
| | 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. |
| | |
| | * 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]] |
| | |
| | ====How do I prevent Rosegarden splitting long notes when recording?==== |
| | |
| | There is a setting for that: |
| | |
| | Edit -> Preferences -> Notation -> [ ] When ... split-and-tie long ... |
| | |
