One Manual Scheme for the Travelling/Deprived Organist

[larspalo]

Originally posted 2021-04-06 03:04:23.857000 by tournai in GrandOrgue discussion forum on SourceForge

Does anyone know whether there is a single-manual scheme available somewhere that I could load to GrandOrgue for free?

The need I am trying to meet (among local players) is for a setup I can plug directly into an electric keyboard or the like so that we can 'hack' a decent organ sound for small churches that refuse to do any better...

The idea is for a specification along these lines:
Diapason 8'
Flute 8' (soft-ish so it can support a soloist)
String 8'
Diapason 4'
Flute 4'
Diapason 2'

Pedal Bourdon 16' (playable on the manual by means of a bass coupler - ie. drawing this stop just doubles the lowest note in a texture an octave lower using the pedal).

Can anyone help? This evidently doesn't need to be fancy... Some built-in pistons would obviously be helpful to preset some combinations onto a numerical keypad.

Something on the Romantic-ish side probably better (ie. not super bright, more warm etc... which is less likely to shriek with bad speakers).

[larspalo]

Originally posted 2021-04-06 20:44:35.136000 by dvdgrttr in GrandOrgue discussion forum on SourceForge

Why not use one of the existing two manual and pedal sets. GrandOrgue has built in melody couplers(highest note) and bass couplers (lowest note) so that melody, accompaniment, and pedal can all be separated from a single keyboard automatically. Also it would remain possible to switch manuals on a single portable keyboard simply by changing the keyboard midi channel, which is usually quick and easy to do with one or two button presses. Stops and/or presets can be toggled by sending program change messages from a keyboard as well, a capability most usb keyboards implement. Even ODFs without on screen pistons can use the combination pistons already built into GrandOrgue
There are high quality sample sets that will easily fit into a 4meg or 8meg ram laptop or Raspberry Pi. I would suggest looking at the pekala or wildervank sample sets, or the Casavant 3742 demo set(sonus paradisis) for a warm sound. There are grandOrgue odfs for all of these available, see https://mps-orgelseite.de/home/filebase/ or the grandorgue samplesets page.
If you want to cut down one of these sets to single manual and pedal, they can easily be customized using Mr Forman's graphical editor or the command line jMakeOdf program (available in the grandorque download area) Also you could easily use or modify the grandorgue demo sample set that comes with recent installations if you have less RAM.

[larspalo]

Originally posted 2021-04-06 23:58:50.432000 by tournai in GrandOrgue discussion forum on SourceForge

Thanks for this, David.

I am a complete 'newbie', as it were, so would be grateful if you could bear with me here. I'm also inadept at all things software-related... especially in this area!

The ultimate goal is for something that is quite literally 'plug and play' - not just for me, but for everyone else.

I think Mr Forman's editor is most likely to be the one for me. Where can I download this? Can see where to get jMake Odf but not the other. And will it be possible to set up the 16' Bourdon so that when drawn on the manual, it just doubles things an octave lower?

I'd probably also add a pile of pistons so that I can hook up a USB number keyboard (or whatever it's called) and use this as a stop changer of sorts.

[larspalo]

Originally posted 2021-04-07 02:17:00.550000 by Mark Bugeja in GrandOrgue discussion forum on SourceForge

Check my website: mhpo.epizy.com

Regards,
Mark

On 06/04/2021 05:04, Tournai wrote:
>
> Does anyone know whether there is a single-manual scheme available
> somewhere that I could load to GrandOrgue for free?
>
> The need I am trying to meet (among local players) is for a setup I
> can plug directly into an electric keyboard or the like so that we can
> 'hack' a decent organ sound for small churches that refuse to do any
> better...
>
> The idea is for a specification along these lines:
> Diapason 8'
> Flute 8' (soft-ish so it can support a soloist)
> String 8'
> Diapason 4'
> Flute 4'
> Diapason 2'
>
> Pedal Bourdon 16' (playable on the manual by means of a bass coupler -
> ie. drawing this stop just doubles the lowest note in a texture an
> octave lower using the pedal).
>
> Can anyone help? This evidently doesn't need to be fancy... Some
> built-in pistons would obviously be helpful to preset some
> combinations onto a numerical keypad.
>
> Something on the Romantic-ish side probably better (ie. not super
> bright, more warm etc... which is less likely to shriek with bad
> speakers).
>
> ------------------------------------------------------------------------
>
> One Manual Scheme for the Travelling/Deprived Organist
> <https://sourceforge.net/p/ourorgan/discussion/962124/thread/b2a2aca2c1/?limit=25#f2c2>
>
> ------------------------------------------------------------------------
>
> Sent from sourceforge.net because you indicated interest in
> https://sourceforge.net/p/ourorgan/discussion/962124/
> <https://sourceforge.net/p/ourorgan/discussion/962124/>
>
> To unsubscribe from further messages, please visit
> https://sourceforge.net/auth/subscriptions/
> <https://sourceforge.net/auth/subscriptions/>
>

Attachments in original post:
https://sourceforge.net/p/ourorgan/discussion/962124/thread/b2a2aca2c1/f2c2/b324/attachment/alternate

[larspalo]

Originally posted 2021-04-07 20:24:24.775000 by dvdgrttr in GrandOrgue discussion forum on SourceForge

organ builder is available at
https://virtualpipeorgans.wordpress.com/tools/organ-builder-by-vincent-forman/

I have run it under wine in linux, but not sure it runs in windows 10

I don't think you can set up a stop such as bourdon 16 on a division or manual and have it just double the existing stops an octave lower for just the lowest note ( I assume that's what you want?) You can of course have an intramanual coupler that will double every note an octave lower. I would suggest that you can create a phantom pedal division with a bourdon 16 stop always active, then create a bass only coupler to pedal on your manual. You can of course label this coupler as "Bourdon 16" if you want.

[larspalo]

Originally posted 2021-04-07 21:28:54.954000 by Mark Bugeja in GrandOrgue discussion forum on SourceForge

It does. I used it during the initial creation of my sample-sets. I do
extensive editing and additions after that initial phase. So Vincent's
software is very good at starting off the exercise and getting a few
basic things on the preliminary odf. Sadly Vincent had no intention of
developing his software any further. Very sad indeed as his organbuilder
showed a lot of promise and great potential. If only someone continues
developing it further...... I'm sure Vincent will be delighted.

Mark

On 07/04/2021 22:24, david gritter wrote:
>
> organ builder is available at
> https://virtualpipeorgans.wordpress.com/tools/organ-builder-by-vincent-forman/
> <https://virtualpipeorgans.wordpress.com/tools/organ-builder-by-vincent-forman/>
>
> I have run it under wine in linux, but not sure it runs in windows 10
>
> I don't think you can set up a stop such as bourdon 16 on a division
> or manual and have it just double the existing stops an octave lower
> for just the lowest note ( I assume that's what you want?) You can of
> course have an intramanual coupler that will double every note an
> octave lower. I would suggest that you can create a phantom pedal
> division with a bourdon 16 stop always active, then create a bass only
> coupler to pedal on your manual. You can of course label this coupler
> as "Bourdon 16" if you want.
>
> ------------------------------------------------------------------------
>
> One Manual Scheme for the Travelling/Deprived Organist
> <https://sourceforge.net/p/ourorgan/discussion/962124/thread/b2a2aca2c1/?limit=25#e656>
>
> ------------------------------------------------------------------------
>
> Sent from sourceforge.net because you indicated interest in
> https://sourceforge.net/p/ourorgan/discussion/962124/
> <https://sourceforge.net/p/ourorgan/discussion/962124/>
>
> To unsubscribe from further messages, please visit
> https://sourceforge.net/auth/subscriptions/
> <https://sourceforge.net/auth/subscriptions/>
>

Attachments in original post:
https://sourceforge.net/p/ourorgan/discussion/962124/thread/b2a2aca2c1/e656/6cd5/attachment/alternate

[larspalo]

Originally posted 2021-04-08 07:50:40.099000 by csw900 in GrandOrgue discussion forum on SourceForge

I have personally not used the GO bass coupler or melody coupler feature but "Autobass" is quite common in some other organs such as eplayOrgan where the lowest great note below middle C can be optionally repeated in the pedal division. This is a very useful feature for any system without pedals.

Similarly "automelody" (optionally repeating the highest great note above middle C in the swell division) would be useful for systems with only one manual.

Thus you can play a 2 manual + pedals organ using only one manual (i.e. a portable keyboard).

Is there any publicly available GO sampleset which uses its bass and melody coupler feature?

csw900

[larspalo]

Originally posted 2021-04-08 09:47:28.053000 by Mark Bugeja in GrandOrgue discussion forum on SourceForge

You can check my sample-sets on mhpo.epizy.com

Mark

On 08/04/2021 09:50, csw900 wrote:
>
> I have personally not used the GO bass coupler or melody coupler
> feature but "Autobass" is quite common in some other organs such as
> eplayOrgan where the lowest great note below middle C can be
> optionally repeated in the pedal division. This is a very useful
> feature for any system without pedals.
>
> Similarly "automelody" (optionally repeating the highest great note
> above middle C in the swell division) would be useful for systems with
> only one manual.
>
> Thus you can play a 2 manual + pedals organ using only one manual
> (i.e. a portable keyboard).
>
> Is there any publicly available GO sampleset which uses its bass and
> melody coupler feature?
>
> csw900
>
> ------------------------------------------------------------------------
>
> One Manual Scheme for the Travelling/Deprived Organist
> <https://sourceforge.net/p/ourorgan/discussion/962124/thread/b2a2aca2c1/?limit=25#1196>
>
> ------------------------------------------------------------------------
>
> Sent from sourceforge.net because you indicated interest in
> https://sourceforge.net/p/ourorgan/discussion/962124/
> <https://sourceforge.net/p/ourorgan/discussion/962124/>
>
> To unsubscribe from further messages, please visit
> https://sourceforge.net/auth/subscriptions/
> <https://sourceforge.net/auth/subscriptions/>
>

Attachments in original post:
https://sourceforge.net/p/ourorgan/discussion/962124/thread/b2a2aca2c1/1196/5d9b/attachment/alternate

[larspalo]

Originally posted 2021-04-08 19:20:09.817000 by tbpr in GrandOrgue discussion forum on SourceForge

A sample set doesn't use a bass or melody coupler, the player does. In GO it is available for every sample set in the Panel/Coupler menu and is available for each manual.

[larspalo]

Originally posted 2021-04-09 10:33:11.120000 by csw900 in GrandOrgue discussion forum on SourceForge

Another potentially useful feature that some portable keyboards have is "Aftertouch". This operates when additional pressure is applied to a key after it has been pressed. This extra pressure generates midi command 0xd0 which can be used by the organ to also play the note on a different manual. While this key is held down other notes will also play on the different manual.

This feature is sometimes implemented on theatre organs but as far as I know never on church organs. And also as far as I know GO does not implement it - however it is implemented on Miditzer and eplayOrgan.

Aftertouch + bass and melody couplers would allow you to play a three manual + pedal organ using only a single portable keyboard.

csw900
P.S. Just re-discovered that GO does do aftertouch on the Barton 3-7. I will be testing out all these features when I get some spare time.

[larspalo]

Originally posted 2021-05-14 15:23:14.514000 by dvdgrttr in GrandOrgue discussion forum on SourceForge

I have just completed a portable organ, pictures attached. It uses inexpensive lighted game pushbuttons for stops( these switches accept a round paper insert for labels), regular pushbuttons for combination action, and includes the ability to play the lowest note on the great on the pedal as well. An Arduino Leonardo is used to scan the switches and send midi messages over USB to a Raspberry pi 4. The pi boots the 64 bit raspbian OS and automatically starts GrandOrgue and the jack audio daemon, so it operates headless. Connect powered speakers to the audio injector hat and one or more midi keyboards and you can play. stops in grandorgue accept 9x note messages on midi channel 5 and send back their state with midi 9x note messages on channel 6 back to the leonardo so it can respond by lighting the stop button lights and keeping track of which stops are on. Combination buttons send a single note on message to which the combination buttons in grand orgue respond with a 9x note on toggle.

Attachments in original post:
https://sourceforge.net/p/ourorgan/discussion/962124/thread/b2a2aca2c1/48aa/attachment/P1060443.JPG
https://sourceforge.net/p/ourorgan/discussion/962124/thread/b2a2aca2c1/48aa/attachment/P1060444.JPG

[larspalo]

Originally posted 2021-06-04 06:11:42.018000 by jwkb in GrandOrgue discussion forum on SourceForge

This is exactly the scenario at my church where we only have an old digital piano. I use the demo version of the Bellevue Casavant organ from Sonus Paradisi. I have created a custom ODF file which presents things in a nice compact way suitable for a single manual keyboard. There is a single 17" touch screen and an old PC which just get left by the piano for the traditional service. We make extensive use of the melody and bass couplers, although these are a bit buggy. If you'd like my ODF file I'm happy to provide it.
https://www.sonusparadisi.cz/en/blog/casavant-demo-sample-set/

[larspalo]

Originally posted 2021-06-04 12:19:20.874000 by jwkb in GrandOrgue discussion forum on SourceForge

I'll have to copy if off the PC at church on Sunday, Mark; can't find it at home - good reason to make a backup!

By 'buggy' I mean that the algorithm that determines which is the lowest / highest note being played isn't very robust. When playing hymns it is very sensitive to the order the four notes in the chord are played. I've compared it with the HW implementation which seems to work much better. I did try to analyse the GO code to determine the algorithm but couldn't figure out how it worked.

I didn't mention before but the Bellevue organ is good for use in church because it is fairly dry (especially the 'front' channels'). So many sample sets have too much reverb to use in church buildings.

regards
John

[larspalo]

Originally posted 2021-06-04 16:55:11.730000 by Mark Bugeja in GrandOrgue discussion forum on SourceForge

Hello John,

On HW, keyboard are identified by playing the lowest and the highest
keys. In GO, a keyboard is identified by playing any note on that
particular manual/ key or pedal board. The bug you mention is rather odd
and I have never come across it. You got me curious indeed. I don't
think there should be anything in the code that would determine the
order of playing of notes. I would fault the keyboard that might be
sending the wrong signals (may be a variable issue because of say rust
on the contacts or faulty reed switches) or possibly the samples
themselves (wrong labelling of notes eg F plays F# and F# plays F - but
this would be a consistent / fixed error that will be corrected after
the labelling is rectified).

Yes - dry samples should be used in a big acoustic environment. Wet
samples would be best for smaller spaces like rooms in a house
particularly so if carpeted or having wooden floors and panelling. Even
in my country where houses are build in stone with ceramic tile flooring
the acoustics are rather low because rooms tend to be small and
sometimes carpeted and/or full of furniture that dampen the sounds.

Mark

On 04/06/2021 14:19, John Bowen wrote:
>
> I'll have to copy if off the PC at church on Sunday, Mark; can't find
> it at home - good reason to make a backup!
>
> By 'buggy' I mean that the algorithm that determines which is the
> lowest / highest note being played isn't very robust. When playing
> hymns it is very sensitive to the order the four notes in the chord
> are played. I've compared it with the HW implementation which seems to
> work much better. I did try to analyse the GO code to determine the
> algorithm but couldn't figure out how it worked.
>
> I didn't mention before but the Bellevue organ is good for use in
> church because it is fairly dry (especially the 'front' channels'). So
> many sample sets have too much reverb to use in church buildings.
>
> regards
> John
>
> ------------------------------------------------------------------------
>
> One Manual Scheme for the Travelling/Deprived Organist
> <https://sourceforge.net/p/ourorgan/discussion/962124/thread/b2a2aca2c1/?limit=25#314f/c76f/dc84>
>
> ------------------------------------------------------------------------
>
> Sent from sourceforge.net because you indicated interest in
> https://sourceforge.net/p/ourorgan/discussion/962124/
> <https://sourceforge.net/p/ourorgan/discussion/962124/>
>
> To unsubscribe from further messages, please visit
> https://sourceforge.net/auth/subscriptions/
> <https://sourceforge.net/auth/subscriptions/>
>

Attachments in original post:
https://sourceforge.net/p/ourorgan/discussion/962124/thread/b2a2aca2c1/314f/c76f/dc84/7edd/attachment/alternate

[larspalo]

Originally posted 2021-06-04 17:15:04.375000 by Mark Bugeja in GrandOrgue discussion forum on SourceForge

Having read csw900's message, I now understand better what the issue is.
I have noticed something similar on our Johannus Organ in church. If I
play say part of a CEG chord (EG) and then hit the lowest (C) last with
the little finger a moment after, this last note will not play in the
autobass. So autobass plays E and C simply plays in the manual. It is
important to play all the notes of a chord at the same time for the
autobass to function correctly. So it is not a unique "bug" that you
have there.

Regards
Mark

On 04/06/2021 18:55, Mark Bugeja wrote:
>
> Hello John,
>
> On HW, keyboard are identified by playing the lowest and the highest
> keys. In GO, a keyboard is identified by playing any note on that
> particular manual/ key or pedal board. The bug you mention is rather odd
> and I have never come across it. You got me curious indeed. I don't
> think there should be anything in the code that would determine the
> order of playing of notes. I would fault the keyboard that might be
> sending the wrong signals (may be a variable issue because of say rust
> on the contacts or faulty reed switches) or possibly the samples
> themselves (wrong labelling of notes eg F plays F# and F# plays F - but
> this would be a consistent / fixed error that will be corrected after
> the labelling is rectified).
>
> Yes - dry samples should be used in a big acoustic environment. Wet
> samples would be best for smaller spaces like rooms in a house
> particularly so if carpeted or having wooden floors and panelling. Even
> in my country where houses are build in stone with ceramic tile flooring
> the acoustics are rather low because rooms tend to be small and
> sometimes carpeted and/or full of furniture that dampen the sounds.
>
> Mark
>
> On 04/06/2021 14:19, John Bowen wrote:
>
> I'll have to copy if off the PC at church on Sunday, Mark; can't find
> it at home - good reason to make a backup!
>
> By 'buggy' I mean that the algorithm that determines which is the
> lowest / highest note being played isn't very robust. When playing
> hymns it is very sensitive to the order the four notes in the chord
> are played. I've compared it with the HW implementation which
> seems to
> work much better. I did try to analyse the GO code to determine the
> algorithm but couldn't figure out how it worked.
>
> I didn't mention before but the Bellevue organ is good for use in
> church because it is fairly dry (especially the 'front'
> channels'). So
> many sample sets have too much reverb to use in church buildings.
>
> regards
> John
>
> ------------------------------------------------------------------------
>
> One Manual Scheme for the Travelling/Deprived Organist
> https://sourceforge.net/p/ourorgan/discussion/962124/thread/b2a2aca2c1/?limit=25#314f/c76f/dc84
> <https://sourceforge.net/p/ourorgan/discussion/962124/thread/b2a2aca2c1/?limit=25#314f/c76f/dc84>
>
> ------------------------------------------------------------------------
>
> Sent from sourceforge.net because you indicated interest in
> https://sourceforge.net/p/ourorgan/discussion/962124/
> <https://sourceforge.net/p/ourorgan/discussion/962124/>
> https://sourceforge.net/p/ourorgan/discussion/962124/
> <https://sourceforge.net/p/ourorgan/discussion/962124/>
>
> To unsubscribe from further messages, please visit
> https://sourceforge.net/auth/subscriptions/
> <https://sourceforge.net/auth/subscriptions/>
> https://sourceforge.net/auth/subscriptions/
> <https://sourceforge.net/auth/subscriptions/>
>
> ------------------------------------------------------------------------
>
> One Manual Scheme for the Travelling/Deprived Organist
> <https://sourceforge.net/p/ourorgan/discussion/962124/thread/b2a2aca2c1/?limit=25#314f/c76f/dc84/7edd>
>
> ------------------------------------------------------------------------
>
> Sent from sourceforge.net because you indicated interest in
> https://sourceforge.net/p/ourorgan/discussion/962124/
> <https://sourceforge.net/p/ourorgan/discussion/962124/>
>
> To unsubscribe from further messages, please visit
> https://sourceforge.net/auth/subscriptions/
> <https://sourceforge.net/auth/subscriptions/>
>

Attachments in original post:
https://sourceforge.net/p/ourorgan/discussion/962124/thread/b2a2aca2c1/314f/c76f/dc84/7edd/c4c0/attachment/alternate

[larspalo]

Originally posted 2021-06-04 17:28:24.232000 by Lars Palo in GrandOrgue discussion forum on SourceForge

Ok, having tested the MEL and BAS couplers a little I can confirm that
GO does not always jump to whatever note is highest or lowest at the
moment if all the notes are not striked again. That is, if notes are
held down the algorithm might miss that the bass or melody should jump
when the melody or bass is released when the melody or bass has moved.
If one play in a strict choral way where the notes are striked anew
for every new chord it works as expected, but if the middle parts are
held while the melody or bass is moved around then the jump at a bass
or melody release is not working as one might expect it.

The question is if this is a bug or a feature... As I recall, some
very real pipe organs with bass and melody copulers behave in pretty
much the same way as GO does right now. That is, if you want the bass
and melody coupler to work, you must release and strike again every
note in the next chord to be sure that the bass and melody coupler
will find the next note they should target.

The relevant code, as I quickly can find it now, seems to be in the
GOrgueCoupler.cpp ChangeKey and SetKey functions and the m_KeyVelocity
vector. The real issue is how we would like the BAS and MEL coupler to
function...

[larspalo]

Originally posted 2021-06-04 18:55:13.676000 by Mark Bugeja in GrandOrgue discussion forum on SourceForge

The best and most logical is for these couplers to respond to any lowest
/ highest note played irrespective of any other keys held down.

This is my humble opinion based on how I expect the instrument to
respond when I am playing.

Regards
Mark

On 04/06/2021 19:28, Lars Palo wrote:
>
> Ok, having tested the MEL and BAS couplers a little I can confirm that
> GO does not always jump to whatever note is highest or lowest at the
> moment if all the notes are not striked again. That is, if notes are
> held down the algorithm might miss that the bass or melody should jump
> when the melody or bass is released when the melody or bass has moved.
> If one play in a strict choral way where the notes are striked anew
> for every new chord it works as expected, but if the middle parts are
> held while the melody or bass is moved around then the jump at a bass
> or melody release is not working as one might expect it.
>
> The question is if this is a bug or a feature... As I recall, some
> very real pipe organs with bass and melody copulers behave in pretty
> much the same way as GO does right now. That is, if you want the bass
> and melody coupler to work, you must release and strike again every
> note in the next chord to be sure that the bass and melody coupler
> will find the next note they should target.
>
> The relevant code, as I quickly can find it now, seems to be in the
> GOrgueCoupler.cpp ChangeKey and SetKey functions and the m_KeyVelocity
> vector. The real issue is how we would like the BAS and MEL coupler to
> function...
>
> ------------------------------------------------------------------------
>
> One Manual Scheme for the Travelling/Deprived Organist
> <https://sourceforge.net/p/ourorgan/discussion/962124/thread/b2a2aca2c1/?limit=50#314f/c76f/dc84/7edd/156f>
>
> ------------------------------------------------------------------------
>
> Sent from sourceforge.net because you indicated interest in
> https://sourceforge.net/p/ourorgan/discussion/962124/
> <https://sourceforge.net/p/ourorgan/discussion/962124/>
>
> To unsubscribe from further messages, please visit
> https://sourceforge.net/auth/subscriptions/
> <https://sourceforge.net/auth/subscriptions/>
>

Attachments in original post:
https://sourceforge.net/p/ourorgan/discussion/962124/thread/b2a2aca2c1/314f/c76f/dc84/7edd/156f/0852/attachment/alternate

[larspalo]

Originally posted 2021-06-04 14:05:37.816000 by csw900 in GrandOrgue discussion forum on SourceForge

Here is the code for autobass taken from eplayOrgan - it works for me and always plays the lowest note whatever order you play a chord - you can test it out for yourself.

    if(autobass && (note <= 60) && (note >= 36)){    //autobass, 60 = middle C, 36 = lowest note
      (value > 0) ? gtnotesplaying[note-36] = note : gtnotesplaying[note-36] = 0; //for autobass notes only
      lowestgtnoteplaying = 0;
      for(i=0;i<25;i++){
        if(gtnotesplaying[i] > 0){
          lowestgtnoteplaying = gtnotesplaying[i];  //get lowest great note playing
          break;
         }
      }
      if((value > 0) && (lowestgtnoteplaying != lowestnote)){  //note on
        pedal.playNoteOff(lowestnote);                         //turn off last lowest note 
        if(lowestgtnoteplaying > 0){
          pedal.playNoteOn(value, lowestgtnoteplaying);  //play the lowest great note
          lowestnote = lowestgtnoteplaying;
        }
      }
      if((value == 0) && ((note == lowestnote) || (lowestgtnoteplaying == 0))){ //note off
        pedal.playNoteOff(note);                                //turn note off
        lowestnote = 0x7f;
        if(lowestgtnoteplaying != 0){
          pedal.playNoteOn(64, lowestgtnoteplaying);    //play the new lowest great note
          lowestnote = lowestgtnoteplaying;
        }
      }
    }

The restricted width has ruined the layout but if you copy and past it into notepad it should recover.

Any useful comments will be gratefully received and if useful I may update the code accordingly.

csw900

[larspalo]

Originally posted 2021-06-07 11:28:06.324000 by jwkb in GrandOrgue discussion forum on SourceForge

Thanks everyone for your input into this issue. As Lars says, this does to some extent come down to how the couplers should behave. If you release the bottom note while other notes are held, should it jump up to the next lowest held note or not? (neither GO nor HW do jump up)

But I think the expected behaviour when you are playing consecutive block chords without any held notes is fairly clear - you always want the bottom note to go to the bass. This is where it doesn't quite work. For example if I play the progression GA --> DF# then GrandOrgue will send the G to bass, but won't send the D to bass if playing legatissimo, ie there is a tiny overlap - no matter how small - during which the G and D are both depressed. OK one might not intentionally be playing legatissimo but it's easy for this to happen from time to time. I've compared with HW and it seems (but maybe I'm imagining it - I am using different hardware for this testing) that the HW algorithm has some sort of time threshold built in to avoid this problem. Certainly with HW if the overlap is anything more than very brief, the D doesn't sound. When I get a chance I might do some more rigorous testing of HW behaviour using sequenced MIDI to see what actually happens.

Back to Bellevue, I'm attaching my .organ file and associated image directory. This adds an extra panel.

(zip file now fixed for missing image)

Attachments in original post:
https://sourceforge.net/p/ourorgan/discussion/962124/thread/b2a2aca2c1/317d/attachment/Bellevue.zip

[larspalo]

Originally posted 2021-06-07 11:30:07.398000 by jwkb in GrandOrgue discussion forum on SourceForge

Now trying to add a screenshot...

Attachments in original post:
https://sourceforge.net/p/ourorgan/discussion/962124/thread/b2a2aca2c1/7c9c/attachment/bellevue%20screenshot.jpg

[larspalo]

Originally posted 2021-06-07 15:52:46.647000 by Mark Bugeja in GrandOrgue discussion forum on SourceForge

There is a missing image in your image folder:
NewBackgroundDemoCasavant.png

The error does not allow the organ to install.
Regards
Mark

On 07/06/2021 13:30, John Bowen wrote:
>
> Now trying to add a screenshot...
>
> Attachments:
>
> * bellevue screenshot.jpg
> <https://sourceforge.net/p/ourorgan/discussion/962124/thread/b2a2aca2c1/7c9c/attachment/bellevue%20screenshot.jpg>
> (452.2 kB; image/jpeg)
>
> ------------------------------------------------------------------------
>
> One Manual Scheme for the Travelling/Deprived Organist
> <https://sourceforge.net/p/ourorgan/discussion/962124/thread/b2a2aca2c1/?limit=25#7c9c>
>
> ------------------------------------------------------------------------
>
> Sent from sourceforge.net because you indicated interest in
> https://sourceforge.net/p/ourorgan/discussion/962124/
> <https://sourceforge.net/p/ourorgan/discussion/962124/>
>
> To unsubscribe from further messages, please visit
> https://sourceforge.net/auth/subscriptions/
> <https://sourceforge.net/auth/subscriptions/>
>

Attachments in original post:
https://sourceforge.net/p/ourorgan/discussion/962124/thread/b2a2aca2c1/7c9c/cff5/attachment/alternate

[larspalo]

Originally posted 2021-06-07 19:54:20.515000 by jwkb in GrandOrgue discussion forum on SourceForge

Sorry Mark - I left out the background image from the zip. Now added.
After loading the organ, choose Compact Layout from the Panel menu.
The default screen is still there, which is the one I think you were seeing. It is needed for first use so that you can set up your single keyboard, which should be the bottom one. Just close it then - it won't open next time.
The G.O., Pos and Rec buttons will couple the relevant manual to your single keyboard.

Attachments in original post:
https://sourceforge.net/p/ourorgan/discussion/962124/thread/b2a2aca2c1/2571/attachment/Bellevue.zip

[larspalo]

Originally posted 2021-06-07 20:38:00.998000 by Mark Bugeja in GrandOrgue discussion forum on SourceForge

Hi John. Thanks.

I would have preferred to keep the original screen or at least have is
as an option (an additional selectable tab). But then, this is your
piece of artwork! I can always edit it later. I've done these things
before so it shouldn't be a problem.

Mark

On 07/06/2021 21:54, John Bowen wrote:
>
> Sorry Mark - I left out the background image from the zip. Now added
> After loading the organ, choose Compact Layout from the Panel menu.
> The default screen is still there, which is the one I think you were
> seeing. It is still needed for first use so that you can set up your
> MIDI elements - keyboard, pedals etc. Just close it - it won't open
> next time.
>
> Attachments:
>
> * Bellevue.zip
> <https://sourceforge.net/p/ourorgan/discussion/962124/thread/b2a2aca2c1/2571/attachment/Bellevue.zip>
> (2.9 MB; application/x-zip-compressed)
>
> ------------------------------------------------------------------------
>
> One Manual Scheme for the Travelling/Deprived Organist
> <https://sourceforge.net/p/ourorgan/discussion/962124/thread/b2a2aca2c1/?limit=25#2571>
>
> ------------------------------------------------------------------------
>
> Sent from sourceforge.net because you indicated interest in
> https://sourceforge.net/p/ourorgan/discussion/962124/
> <https://sourceforge.net/p/ourorgan/discussion/962124/>
>
> To unsubscribe from further messages, please visit
> https://sourceforge.net/auth/subscriptions/
> <https://sourceforge.net/auth/subscriptions/>
>

Attachments in original post:
https://sourceforge.net/p/ourorgan/discussion/962124/thread/b2a2aca2c1/2571/2424/attachment/alternate

[larspalo]

Originally posted 2021-06-07 21:03:38.230000 by Mark Bugeja in GrandOrgue discussion forum on SourceForge

I must apologise.... I think I wrote a bit too soon. It looks good. I
was expecting something different.

Re: an additional tab, this is possible for another piece of software. I
don't think it can be done on GO.

On 07/06/2021 22:38, Mark Bugeja wrote:
>
> Hi John. Thanks.
>
> I would have preferred to keep the original screen or at least have is
> as an option (an additional selectable tab). But then, this is your
> piece of artwork! I can always edit it later. I've done these things
> before so it shouldn't be a problem.
>
> Mark
>
> On 07/06/2021 21:54, John Bowen wrote:
>
> Sorry Mark - I left out the background image from the zip. Now added
> After loading the organ, choose Compact Layout from the Panel menu.
> The default screen is still there, which is the one I think you were
> seeing. It is still needed for first use so that you can set up your
> MIDI elements - keyboard, pedals etc. Just close it - it won't open
> next time.
>
> Attachments:
>
> * Bellevue.zip
> https://sourceforge.net/p/ourorgan/discussion/962124/thread/b2a2aca2c1/2571/attachment/Bellevue.zip
> <https://sourceforge.net/p/ourorgan/discussion/962124/thread/b2a2aca2c1/2571/attachment/Bellevue.zip>
> (2.9 MB; application/x-zip-compressed)
>
> ------------------------------------------------------------------------
>
> One Manual Scheme for the Travelling/Deprived Organist
> https://sourceforge.net/p/ourorgan/discussion/962124/thread/b2a2aca2c1/?limit=25#2571
> <https://sourceforge.net/p/ourorgan/discussion/962124/thread/b2a2aca2c1/?limit=25#2571>
>
> ------------------------------------------------------------------------
>
> Sent from sourceforge.net because you indicated interest in
> https://sourceforge.net/p/ourorgan/discussion/962124/
> <https://sourceforge.net/p/ourorgan/discussion/962124/>
> https://sourceforge.net/p/ourorgan/discussion/962124/
> <https://sourceforge.net/p/ourorgan/discussion/962124/>
>
> To unsubscribe from further messages, please visit
> https://sourceforge.net/auth/subscriptions/
> <https://sourceforge.net/auth/subscriptions/>
> https://sourceforge.net/auth/subscriptions/
> <https://sourceforge.net/auth/subscriptions/>
>
> ------------------------------------------------------------------------
>
> One Manual Scheme for the Travelling/Deprived Organist
> <https://sourceforge.net/p/ourorgan/discussion/962124/thread/b2a2aca2c1/?limit=25#2571/2424>
>
> ------------------------------------------------------------------------
>
> Sent from sourceforge.net because you indicated interest in
> https://sourceforge.net/p/ourorgan/discussion/962124/
> <https://sourceforge.net/p/ourorgan/discussion/962124/>
>
> To unsubscribe from further messages, please visit
> https://sourceforge.net/auth/subscriptions/
> <https://sourceforge.net/auth/subscriptions/>
>

Attachments in original post:
https://sourceforge.net/p/ourorgan/discussion/962124/thread/b2a2aca2c1/2571/2424/228e/attachment/alternate