Skip to content

FAQ

Jump to bottom
Oleg Samarin edited this page Jun 28, 2022 · 13 revisions

A Note: It is usually better to ask question via the public forum than to mail GO developers directly. For common problems, you will likely get faster anwsers, because other GO users also can help. Additionally, the discussion is preserved for the public - so if somebody comes up with the same question, the previous answers are available.

  • Where can I download GrandOrgue?

Pre-built packages of binaries are provided here on GitHub for Linux, Windows and OS X.

Official builds of releases https://github.com/GrandOrgue/grandorgue/releases

Intermediate builds for testing https://github.com/GrandOrgue/grandorgue/actions

  • How do I install/upgrade GrandOrgue?

See https://github.com/GrandOrgue/grandorgue/blob/master/INSTALL.md for information on installing/upgrading GrandOrgue.

  • What about latency?

GO ships with safe (=bigger) latency settings. Lower samples per buffers decrease latency but also limit polyphony. Each sound card entry in GO has a "desired latency" setting (default: 50 ms).

  • What about ASIO?

The Windows builds on GitHub include support for ASIO. GO also directly supports WDK/KS, which is wrapped by ASIO4ALL. A previous recommendation was to use WDM/KS and WASAPI in preference over ASIO. If WASAPI does not work, try a different samplerate in GrandOrgue.

  • How is GrandOrgue developed?

GrandOrgue uses an agile development model. We determine the GrandOrgue version number based on the type of changes done to the source code in our repository. The first number indicate major version, the second number minor version, the third number build version and the last part after the dash is package information number where a -1 indicates a release and a -0.Number indicate an intermediate testing build. So a higher number means a more recent GrandOrgue.

Our CHANGELOG.md contain the changelog.

  • A bug has been fixed in GO ''1234''. Where can I download it?

Releases can be found at https://github.com/GrandOrgue/grandorgue/releases and intermediate testing builds at https://github.com/GrandOrgue/grandorgue/actions

  • How to build GrandOrgue?

See BUILD.md in the source code for instructions.

  • I want to modify/create ODF (organ definition files) for GO

GO includes a "telegram style" ODF and organ package reference in its help (Anybody is welcome to submit improvements for our help). You should also enable "strict ODF mode" in the GO settings, as this will report various potential problems. In regards to temperament handling, it will only report larger, probably incorrect retunings - each pipe of each stop still needs to be checked manually in equal temperament for smaller errors.

There is OdfEdit - a python3-based GUI tool for editing ODFs.

Clone this wiki locally