• 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

Grandorgue & Windows 7 64 bit

e9925248

New member
I only have one Midi input, so I don't think that it's going to be a problem with multiple inputs. It seems to be sibelius possibly sending controller messages unasked for, for example at a manual change.

The device setting specifies loopbe, which is the only input.

wxWidgets on Windows seems to have problems with storing certain values as item data. This could cause the "any channel" problems. I'll put a workaround in the next release.

I've increased the latency to 100 - still a slight click, on all of the sound drivers, which I don't get at all in GO 0.2 with the same computer. Same problem on the 32 bit version.

GO 0.3 will definitly require more CPU power than GO 0.2.

Is the click a load issue [disappers, if you use only one stop / less polyhony], a release alignment problem [occurs, when a note is released - could be caused by a load issue too] or a sound output issue [the click occurs at regular intervals even if only one sample is playing for a long time].

I'm aware of: WASAPI seems suffers from sound output issues and WDM-KS is currently somehow broken.
 

7thGalaxy

New member
I'm using Directsound as it seems the most stable. I've got a brand new laptop, with a pentium i5 processor, so it's significantly faster than the computer I used to run GO 0.2 on, which ran even the biggest organ I used without too much trouble.

The click is a load issue, as you describe it above it happens at a thick part of the texture, specifically in one piece where there is a suspension high in the register, originally the sound sample seems to detune as well, although that has gone away for some reason. The clicks happen mid note, at one specific point in my test piece. The same registration continues for a while, but no more clicking is heard as the texture is thinner.

WASAPI is the driver which instacrashed GO, so I don't want to try it again really!
 

Dorsetmike

Member
Re setting stops; I am not a keyboard player, so I play GO with midi files generated by notation software; I've so far only used GO2, and Finalé Songwriter to generate the Midi file. Initially I found trying to select stops was a right pain in the wotsit I tried using an extra staff on a separate channel and using tied chords to generate note on/off, it worked but was awkward to say the least. I then started using Midiocre to edit in Programme change commands (Cx) to set divisionals having manually set up the divisionals and saved in memory for the work to be played. This works very well for me, but is not much use to anybody playing a keyboard. Changing instruments on a keyboard will achieve the same result, however the only keyboard I have requires 4 key presses to generate i Cx command (function select followed by 3 digits on a numeric pad) so wouldn't be much use except at the start of a work or movement.

In Songwriter (notation software) I set each staff to a separate midi channel and each midi channel plays one keyboard or pedals. I'm using an extended Stiehr-Mockers organ, with Swell set to channel 1, Great to channel 2 and peds to channel 3.

Assuming 8 divisionals per manual select them using Cx 00 through 07 on the channel associated with the relevant manual/pedal, the registration for the start of the work can be assigned by selecting the appropriate "instrument" for each staff to select the required divisionals.

For subsequent settings I edit the midi file using Midiocre inserting a Cx command at the point in the midi file where the registration changes. It as actually possible to change registration more than once in a bar/measure. For a keyboard player select an instrument that generates the CX command number for the required divisional.

The limitation with the basic GO screen is 8 divisionals per manual, however this can be extended in the .organ file, to test this I have 10 working on each manual.

Midiocre is available here --
http://download.cnet.com/Midiocre/3000-2170_4-10019301.html

Open your midi file, select the track to edit, then select "Events" right click an entry to get a drop down of options, "New" /Midi opens a further window to add or alter any valid midi message like programme or control changes, note on/off and also to set the position within a measure when the change will take place.

Hope this will be of some help, not sure if there are any changes in GO3 to affect registration by this method.
 

e9925248

New member
The limitation with the basic GO screen is 8 divisionals per manual, however this can be extended in the .organ file, to test this I have 10 working on each manual.

Hope this will be of some help, not sure if there are any changes in GO3 to affect registration by this method.

GO 0.3 will support it too. Additionally each organ has automatically 10 generals per manual/peal and 30 generals in addition to the ODF defined elements.

You could use the registration sequencer. Programm the stop changes in the sequence they occur in your music (number 0 - n). Assign 000 to one midi event and next to another. At the start of your song, trigger 000. At each registration change trigger next. As event you can anything you like (Note on 9x, Control Change Bx, Program Change Cx).

GO 0.3 will even support cheap keyboards better, eg. It support the program change extension to use more than 128 different values. You can use a 9x of an unused keyboard key to toogle a stop/tremulant/coupler.
 
Top