• 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 0.2 Beta released for testing...

ggoode.sa

New member
Hi Guys,

GrandOrgue 0.2 Beta has been released for public testing. Please go to http://www.grahamg.110mb.com/GrandOrgueOverview.htm for further information. This release inlcuded binary versions for Windows, Puppy Linux, and Debian/Ubuntu Linux.

Please help us in testing this software so that we can have a full release available soon.

Have fun,
GrahamG
Johannesburg, South Africa
 

JLD

New member
Spent the last hour playing with this new release and it works like a charm here. Congrats!:)
I am still using the Windows version but need to switch to Linux when I have time.
BTW, even if they are straightforward, we should document the new features: transpose, midi note offset, organ loading throught midi and information display on LCD.
I am wondering how many persons are using GrandOrgue but recommend to all of them to switch to this new version.
JLD
 

ggoode.sa

New member
Hi JLD,
Yes we need to create some more topics for the help file and maybe place some tutorial information on the web. If you have some spare time while at your computer could you type up some notes on the parts that you know?
Glad that it's working like a charm! I've loaded it on my Windows XP 32-bit desktop and my Windows 7 one (which dual boots to Ubuntu and Puppy). I've spent more time using GrandOrgue in Puppy Linux than in Ubuntu, and the performance is excellent.
GrahamG
 

Mathbob

New member
I just installed v2 and it is working very well, even on this limited (512/512) computer. Bob
 

L.Palo

New member
Hi!

Don't know where you want the feedback, so I'll post it here also.


  • Successfully installed GrandOrgue on Ubuntu 9.04. No problem with your instructions!
  • Program starts ok and everything seems to be working nicely.
  • It's extremely sensitive to certain .wav files. For instance the jeux2 don't load. Gives me an error "Failed to load PedPrestant4/13-C2.wav-3000000". Checked the file and .organ xml and of course I can open it by running it through wine. A few other samplesets has the same problem but I've managed to load a few without any problem also.
  • With the ones that loaded some notes had audible clicks in them. Seemed to be related to the release. Running through wine gave none of theese problems.

But at least it's good to see a version running directly in Linux! This is a good start. Thanks for the efforts!

PS, the clicking is not related to xruns in jack...

Kind regards

Lars
 

L.Palo

New member
Issue with loading of samples is fixed by the advice from another forum. Linux is of course case-sensitive. A rename to uppercase of PedPrestant4/13-c2.wav and likewise with PosNazard g#4 fixed jeux2!
 

ggoode.sa

New member
Hi Lars,
Glad you found the solution (Linux is Case Sensitive). I'll see if we can find a reason for the clicks being more pronounced in the Linux version (I can hear them in the Windows version). I have found that this is more due to the loops and release portion of the wav file, so it can be fixed in the sample...
GrahamG
 

erikds

New member
No audio ports in Jack.

Hello Graham,

In your notes you write:

When you first run GrandOrgue you will be presented with the Audio/MIDI configuration screen. Select your MIDI interface and make sure that Jack is selected in the audio drop down. Click on OK. You are now ready to load your .organ file.

I am trying to use Ubuntu 9.04.
The .deb installed successfully and i get the audio/midi config screen.
I started Jack first, and then launched GrandOrgue.
I can tick the midi in from my Midisport 4X4, but in the dropdown box labeled sound output device nothing can be visualised.
In Jack connection, for audio no readable clients/output ports appear; the writable clients/input are there.
The output ports and input ports for alsa are there.

When i start AEOLUS, everything works ok and i can play.

I uninstalled GrandOrgue and reinstalled, but this did not help.

Any idea where i should look?

All the best.

Erik.
 

ggoode.sa

New member
Hi Erik,
I also stated that Jack has to be running at 44100hz, could you check at what rate your jack setup is configured too? If Jack is running and not configured to 44.1khz then nothing will display in the GrandOrgue Sound output device dropdown.
Hope this helps,
GrahamG
 

erikds

New member
Hi Erik,
I also stated that Jack has to be running at 44100hz, could you check at what rate your jack setup is configured too? If Jack is running and not configured to 44.1khz then nothing will display in the GrandOrgue Sound output device dropdown.
Hope this helps,
GrahamG

Thank you for the info.
The sample rate was not set to 44100 hz; now it is.
But still nothing appears in the Sound Output Device dropdown box.
The same problem shows up both using Ubuntu and Puppy Linux.

In Puppy Linux and Ubuntu i can play mp3's.
(And the puppy barks loudly! :) )

Any other causes you can think of?

Thanks in advance and all the best.

Erik.
 

ggoode.sa

New member
Hi Erik,
I sent you a profile message. There are a couple of things that we can try, but let's do it off forum until we have a solution :)
GrahamG
 

ggoode.sa

New member
Hi Guys,
For those following Erik's problem in Ubuntu/Puppy Linux, we think we have discovered the problem:

"Many consumer audio interfaces support only 1 sample rate (48kHz).
When JACK used to fail to start if the user asked for 44.1kHz and the
device did not support it, users howled. So we changed it so that it
picks the closest available rate. Qjackctl displays the rate that was
obtained."

As GrandOrgue requires a sample rate of 44.1khz, it is not able to recognize Jack running at 48khz (if Jack can't run at 44.1khz it will automatically try 48khz and configure itself to that sample rate because of the issue quoted above).

There is a proposed solution that I have working on my own computer, GrandOrgue48. A version of GrandOrgue that will run at 48khz, but it also requires sample sets to be 48khz. I have not yet worked out a way to differentiate between the sample rate of the wave files and the sample rate of the audio stream that plays. So, for now, GrandOrgue48 will require that your sample sets are converted from 44.1khz to 48khz before you can load them.

GrandOrgue48 is not yet ready for release, but if you have the same issue that Erik has please let me know and you can become an Alpha Tester of GrandOrgue48 :)

GrahamG
 
Last edited:

tittualex

New member
Dear All,

Will it be possible to load Hauptwerk 3 sound fonts in grand Orgue ? i Know it is not possible now, but can it be made possible?

Alex.
 

ggoode.sa

New member
Hi Alex,
That will depend on the license of the HW3 sample set producer. If the sample set is only released as an HW3 encrypted sample set then it will not be possible to play it with GrandOrgue.

If the sample set has been released as unencypted wav files and the sample set producer has given permission/license for the sample set to be used in other samplers (like Gigastudio/Kontakt/GrandOrgue/Soundfonts), then it is possible to create an organ defition file that will load the wave files. Sometimes the wave files will need to be resampled to 16bit 44.1khz.

As HW3 now has a free mode installation, windows users can install it and try out the HW3 organs. Milan Digital Audio have a list available on their website.

Yves has produced an organ file creator application that can be used to create the .organ file needed by GrandOrgue, so go and check it out as well.

Hope that helps!
GrahamG
 

Mathbob

New member
midi technical issues

Graham,

I now have 0.2 running on a 3GHz/2Gb machine, actually connected to the Rodgers, not just the keyboard. A couple of technical questions.

I know I saw a "help" somewhere that explains the "audio settings" settings, but I can't recall where, and the help on GO 0.2 is blank.

1) Having trouble getting the swell pedal (volume) to work. The midi processor in the organ now generates Control Change instructions to controller 7. It generates messages for channels 1-4 (0-3 hex) to keep it compatible with the Yamaha synth. [I have defined only one enclosure in GO, as my console has only one swell shoe.] For example, using channel 1, it would generate B0 07 nn, where nn is the volume level. Trying to relate this to GO's "MIDI Messages" settings, I think "Enclosure 1" should be set to Channel = 1, but what does it want for "data/offset"? Is that where the "7" goes?

2) Also having trouble with the general combinations/reversibles. The "GO Organ Definition File Format Reference" specifies "MIDIProgramChangeNumber" - but what MIDI command is this? Is it patch change, Cx? I'm now generating patch changes on channel 5, the same channel used for stops (which are working). To send a change for combination 03, it would transmit C4 03. The "audio settings" screen also has a "data/offset" for these lines, but the patch change command is only two bytes - what is it used for? Also, what is the function of "previous program" vs "next program"?

Thanks!
Bob
 

ggoode.sa

New member
Hi Bill,
We're looking at the possibility of hosting the 'help' portion online, as the linux build of GrandOrgue doesn't like the older version of 'windows help' standard files...

So on to your questions :)

1. The quickest way to setup a Swell pedal is to right click on the pedal image in GrandOrgue and select 'Listen for event' from the popup options. Then move your swell pedal. GrandOrgue should find the MIDI messages and configure the setting automatically. Please let me know if this works for you...

2. For Stops/Combinations/Reversibles you need to set up the type of MIDI messages from within the MIDI Messages Tab in the Audio -> Settings option. The 'Stop Changes' setting will define how the MIDI messages are recieved. This defaults to '9x Note On' messages, but can be changed to 'Cx Program Change', or 'Bx Control Change' messages. The "MIDIProgramChangeNumber" is then either the Midi Note On value, or the Program CHange value or the Control Change value. One can usually also use the 'Listen for Event' method to configure your Stops.

Hope that helps!
GrahamG
 

Mathbob

New member
Down to 1 problem

Graham,

Yes, that was the ticket! Everything works now except the gt-to-pd reversible. When setting up the general combinations, SO's "listen" feature immediately picked up the patch number; expression pedal picked up immediately as well. I've checked the MIDI output from the organ using MidiOx, and the gt-to-pd is generating a program change 46, but when trying to "listen" for it, even after repeated tries, SO does not capture it. [The gt-to-pd does work when clicking the piston icon on the screen.]

BTW, I've noticed that SO is 1-based on the patch numbers, while the MIDI commands are zero based. So, my "46" should be captured as "47" by SO. This did happen with the general combinations.

Any ideas about why of the resersible is having trouble? Here's the .organ code:
[ReversiblePiston001]
Name=GT-PD
Comments=
ShortcutKey=
ObjectType=COUPLER
ManualNumber=0
ObjectNumber=1
DispLabelColour=DARK blue
DispLabelFontSize=normal
Displayed=Y
DispImageNum=1
DispButtonRow=1
DispButtonCol=1
MIDIProgramChangeNumber=46
DispKeyLabelOnLeft=N

It's interesting to hear how the full organ sounds! It primary came from the Brut-Leuchten samples, so those are fairly well balanced, but overall all that remains is balance out the rest of the organ, and substitute a couple of ranks that I'm not overly pleased with.

Thanks!
Bob
 

Mathbob

New member
zero problems

Graham,

Well, I still don't know why it won't detect the gt-to-pd reversible, but just typing 47 into the popup box worked!

Suggestion for future release: It would be nice if the right-click popup box for each stop drawknob would let you set the amplitude level for that stop.

Thanks for all of your help!
Bob
 

ggoode.sa

New member
Hi Bob,
Glad you got it sorted and working :) I have also thought that it would be a good idea to see if we can add the amplitude level for the rank to the right click pop-up, so you have just confirmed it as a good idea. It will go on the list of things to decipher in the source-code to see if it can be done with our limited knowledge and understanding.. ;)

GrahamG
 
Top