Organ package creation (GrandOrgueTool)

The new, more user friendly, way to distribute organs for GrandOrgue is with organ packages in .orgue files. Such a package file can just be dropped into the Organ Package directory, as specified in the Settings dialog (Default and Initial settings tab under Paths), and require no decompression by the user. At a start (or restart) of GrandOrgue any new organ packages will automatically be detected and available to Load from the File menu. If placed somewhere else than in your Organ Package directory the organ package can still be installed instead with the File menu option for that. Please note that you're not supposed to move around organs on your computer disk (or repeatedly change the paths to Organs, Organ Packages, Settings, Cache etc.) as that will confuse GrandOrgue!

GrandOrgueTool is a commandline tool built together with GrandOrgue to make the .orgue package creation process easier. It is available in the same bin directory as GrandOrgue itself. If you run it with:

GrandOrgueTool -h

you will get a short help description of its usage.

The tool is supposed to work on an already existing organ that you've opened/loaded in GO and will package it into a finished .orgue package for easy distribution. GrandOrgueTool also do the wavpack compression of the samples for optimal sampleset distribution size.

For using GrandOrgueTool to create a package you have to specify at least the following necessary parameters:

GrandOrgueTool -c -o OrganPackageFilename.orgue -i SamplesetRootDirectory -t "Organ Package Title String" -o1 OdfName.organ

Additionally, multiple odfs can be specified with -o1 to -o10 and if your organ package does depend on other organ packages you can specify them with -p1 to -p5. Of course, you should replace the dummy explanatory names in the above command with actual relevant ones. Also note that if a file or string supplied to the tool contain blankspaces it must be contained in quotes.

All files in the sampleset directory is included in the .orgue package, but they are not necessarily used. Thus, you really need to specify all the odfs you want to be able to use with -o1 -o2 options.

For the organ package to work all paths in the odf(s) must be specified like:

Pipe001=Subbas16\036-C.wav

This includes all file paths, not only the samples.