Pipes/Keys relationship.

[Dorsetmike]

Hi, is it possible to have 2 or more stops with less pipes than the relevant manual has keys? Also is it possible to share stops between manuals?

Example, in my current instrument plus harpsichord experiments I'd like to have, say, a flute stop and a violin stop playable from one manual; they have slightly different ranges, must I adjust the sample sets to cover the same range, losing some notes from one or both stops, or can I have each stop cover the required range?

If I set up a 45 note manual what would happen if I try and load a stop with only 42 notes? If it can be done what if any changes should be made in the organ def file?

I could extend the range by borrowing notes from an alto flute sample to extend the flute, or do a bit of pitch shifting to add notes outside the normal range for the instrument just to keep GO happy?

My idea is to generate a simple harpsichord or organ on one manual and have 2 other "manuals" for which I could select one or two instruments e.g. flute and/or violin on one manual with Cello and/or another lower register wind like horn, cor anglais, bassoon or trombone.

Not my intention to have all instruments playing at once, just trying to set up a sort of general purpose combination in one organ file, rather than generating a separate file for each combination.

Maybe eventually have a load of manuals and play some Brandenburgs

[L.Palo]

Hi!

It's certainly possible to have stops with different number of pipes on the same manual! You set the number of pipes each stop will have and then at what logical key (FirstAccessiblePipeLogicalKeyNumber=) the pipes will start.

Borrowing in between manuals can be done either by using the same wav again or usually better by referencing with the REF:MMM:SSS:PPP where MMM = manual, SSS = stop and PPP = pipe that you want to reference.

Have a look at stop sections in the ODF of some samplesets and you'll see how the logic works.

Kind regards

Lars P

[e9925248]

I'm trying to add an ODF description covering the curent GO development builds to
its help (docbook-format). As a first step, I have manged to list all supported attributes.

The current version of today (r644) is available at:
http://ourorgan.svn.sourceforge.net/...64&view=markup

[GO 0.2 will ignore/reject attributes of features added after its release]

There is a third way for "sharing" stops: Add a (maybe invisible) manual and put the stop on it. In GO 0.3, you can use the coupler panel to couple it to your other manuals - in GO 0.2 (or if you want a coupler on the main panel) you need to add couplers.

I also have seen ODFs using a dummy WAV file for not sound pipes.

[Dorsetmike]

I seem to have another problem, when using a midi input I have to set an octave down offset for the harpsichord ranks, I have first Midi note set to 12, (for C0) in the organ file, in GO3 clicking on a key gives the correct note, but using a keyboard or a midi file input I need to set a down octave offset to get the note I require.

In the Blanchet set I've added the lower notes from the "Pedale" folder to the normal 8_I folder and pitch shifted the to get the lower notes for 8_IIluth .

I note that the Blanchet set do not follow the file naming convention used in other sets of having the midi number as part of the .wav filename, is this likely to have any effect. Bit of a pain to rename the lot!

[e9925248]

GO just uses relative path for its samples and expects everything in/beyond the folder containing the .organ file. The rest of the file system layout is up to the user.

You need to define your manual covering the expected MIDI range using:
NumberOfLogicalKeys
NumberOfAccessibleKeys
FirstAccessibleKeyLogicalKeyNumber
FirstAccessibleKeyMIDINoteNumber

"NumberOfLogicalKeys = NumberOfAccessibleKeys = number of expected manual keys" and "FirstAccessibleKeyLogicalKeyNumber=1" and "FirstAccessibleKeyLogicalKeyNumber= first MIDI note number" is one possible solution.

If one stop does not cover the whole manual, limit it with FirstAccessiblePipeLogicalKeyNumber and NumberOfAccessiblePipes.