• Welcome to the Pipe Organ Forum! This is a part of the open community Magle International Music Forums focused on pipe organs (also known as "church organs"), organists, organ music and related topics.

    This forum is intended to be a friendly place where technically advanced organists and beginners (or even non-organists) can feel comfortable having discussions and asking questions. We learn by reading and asking questions, and it is hoped that the beginners (or non-organists) will feel free to ask even the simplest questions, and that the more advanced organists will patiently answer these questions. On the other hand, we encourage complex, technical discussions of technique, music, organ-building, etc. The opinions and observations of a diverse group of people from around the world should prove to be interesting and stimulating to all of us.

    As pipe organ discussions can sometimes become lively, it should be pointed out that this is an open forum. Statements made here are the opinion of the poster, and not necessarily that of the forum itself, its administrator, or its moderators.

    In order to post a new topic - or reply to existing ones - you may join and become a member by clicking on Register New User. It's completely free and only requires a working email address (in order to confirm your registration - it will never be given away!). We strive to make this a friendly and informative forum for anyone interested in pipe organs and organ music.

    (Note: If you wish to link to and promote your own website please read this thread first.)

    Many kind regards
    smile.gif

    Frederik Magle
    Administrator

    Krummhorn
    Co-Administrator

Is it possible to create an .ODF with no ranks?

Mick Berg

New member
I want to make an ODF that mirrors my console exactly. I don't want to deal with the actual ranks of pipes at this time, just concentrate on the layout of the manuals, stops and pistons. Can I make an .odf with no ranks of pipes?
Thanks,
Mick.
 

e9925248

New member
If you don't add stops, you need no pipes.

If you add stops/ranks, each stop/rank requires at least one pipe, but you can define it as Pipe001=DUMMY

PS: Stops with only one pipe show a different behaviour (effect stop) - you get a normal stop behaviour, if you add a second dummy pipe.
 

Mick Berg

New member
If you don't add stops, you need no pipes.

If you add stops/ranks, each stop/rank requires at least one pipe, but you can define it as Pipe001=DUMMY

PS: Stops with only one pipe show a different behaviour (effect stop) - you get a normal stop behaviour, if you add a second dummy pipe.

Thanks. Is all this useful info documented anywhere? Or is it just in your head?! It sure would cut down on the number of questions you would have to answer!

I was just hoping to not have to load all those samples each time I wanted to check a small tweak to the GUI. But I found out that if you cancel the organ load once the ranks are starting to load, you still can load the GUI of the organ. Maybe I'll do this rather than removing all the ranks and putting in dummies to about 60 stops!

But I have one more question that would save me some time. Is it possible to make a GUI that has a matrix of 8 columns on each side, and eight rows of stops? I know that with this number of columns the positions would have to be entered in absolute values. If I used the standard stop images, (actually image #2) what resolution screen would I
need?

Thanks,
Mick.
 

e9925248

New member
GO ships a complete, telegram style ODF reference in its help. I try to make sure, that the ODF reference in the help always matches its GO version.

If the changes are so minor, that you can import settings from prior versions, you can set the organ to "don't load" in the organ dialog and press save.

All drawstops have the same size (same for the buttons). The HW1 layout uses 78x69 for each drawstop, 44x40 for a button. A manual octave has a width of 7 * 12. A pedal octave has a with of 11 * 7. Manual height is 32, pedal height is 40. That way, you should be able to estimate the size.
 

Mick Berg

New member
GO ships a complete, telegram style ODF reference in its help. I try to make sure, that the ODF reference in the help always matches its GO version.

If the changes are so minor, that you can import settings from prior versions, you can set the organ to "don't load" in the organ dialog and press save.

All drawstops have the same size (same for the buttons). The HW1 layout uses 78x69 for each drawstop, 44x40 for a button. A manual octave has a width of 7 * 12. A pedal octave has a with of 11 * 7. Manual height is 32, pedal height is 40. That way, you should be able to estimate the size.
Thanks.
I found in reality it wasn't necessary to make the rank-less ODF. The organ loaded very quickly after each change.
Although the help file is very good, you must agree that it is not absolutely comprehensive. Maybe instead of complaining about it I should do something about filling in the details!
While laying out the console I used a little widget that put the mouse co-ordinates on the screen. This was very helpful.
Mick.
 
Last edited:

Mick Berg

New member
I'll give it a go.
Your information is in fact pretty complete, just hard to find sometimes. I am going through the file, correcting the many typos, and expanding and clarifying when I can.
I would appreciate information on the 'switch', what it is, and why and when you would use it. The help is definitely lacking in this area.
Mick.
 

e9925248

New member
The GO demo set uses them.

A switch can be used as an input switch or as logic element.
You can use it eg. to model stop noise, apels (or even much more complex things).

You can only model a stateless logic: It should allow to (mostly) implement functions found on organ with an electric register tracker. The state of any controlled object can only determined by the state of all input switches - you can't model "if X is pressed then switch Y off". You can only model something like "while X is on and Y is off, Z is on else off".

A more complex usecase would be modelling "Freie Kombinationen" similar to http://de.wikipedia.org/wiki/Datei:RV_Liebfrauenkirche_Orgel_Spieltisch_Register.jpg
 

Mick Berg

New member
The GO demo set uses them.

A switch can be used as an input switch or as logic element.
You can use it eg. to model stop noise, apels (or even much more complex things).

You can only model a stateless logic: It should allow to (mostly) implement functions found on organ with an electric register tracker. The state of any controlled object can only determined by the state of all input switches - you can't model "if X is pressed then switch Y off". You can only model something like "while X is on and Y is off, Z is on else off".

A more complex usecase would be modelling "Freie Kombinationen" similar to http://de.wikipedia.org/wiki/Datei:RV_Liebfrauenkirche_Orgel_Spieltisch_Register.jpg

Now that is one strange console! I don't plan to try to imitate that. Sorry to have to ask but which is the GO demo organ?
Thanks,
Mick.
 
Top