• 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

GO and stops MIDI control problem in Content D2800 console

pwos

New member
Hi dears,

I've connected the computer with GO installed to the big console of Content D2800 organ - 3+P, 48 stops in total, 6 couplers etc. Then and tried to communicate it with GO (by right clicks). Pedal and manuals are working great :) but when I tried to synchronize stop buttons it turned out that the some buttons sends the same midi command from the point of GO view (so one console stop button activates a number of GO stops) :cry:. I recognized this commands with MIDIOX and noticed that there are the commands like: $B3 $16 $01; $B3 $16 $02 and so on. So they differs each to other by 3rd byte (or 2nd data byte). GO recognizes each of these events as Bx controller, channel=4, data=16 and nothing else what could make them distinguishable.
Any advice how to resolve this problem?

Kind regards
Pawel (novice GO user)
 

pwos

New member
Thank you e9925248 for fast reply. Also thank you and all people (Lars, Graham and others) who develop GO for the great effort.
Actually, I haven't try this yet but since I've posted the first thread I studied internet resources and found that my problem is very similar to kees's issue: http://sourceforge.net/p/ourorgan/discussion/962124/thread/c8c8ae66/
I still use GO 1386 (thought it is the only stable version) and didn't realize about new functionality. I will try it but I need to break into the church :). Then I will inform about the progress.
 

pwos

New member
Yes, you're right e9925248. As I read, Alborn organ stops generates as many as 3 Bx-commands after being switched ON and OFF, but also varied by 3rd byte value. My Content organ seems to generate only one Bx command varied by 3rd byte value. According to the Table 3 (http://www.midi.org/techspecs/midimessages.php#3) I suspect to get a success to follow "Complex Midi-setup detect" procedure with "RPN range" event recognition.
I meant the problem was similar in the sense that the version of GO that I and kees has used does not recognize properly full length of Bx commands - up to 3rd byte in my case and the set of these commands in kees'es case. Maybe I'm wrong - I'm still layman in MIDI standard but hope to learn :).
 

e9925248

New member
My personal guess is, that it will be detected as "Ctrl Change Bitfield" (via complex MIDI detect).

If anything is not working, please take a MIDI recording [not with the GO MIDI recorder] of the problematic elements for further investiagtion.
 

pwos

New member
Hello again,
I'm back after some tests performed with complex MIDI detection procedure, and...
e9925248, you were right - the 2-step (ON/OFF) command that stops buttons send to the GO were recognized as "Ctrl Change Bitfield", each one with different bit number parameter, so it seems to be close to the success :). For example, 1st stop for pedal is recognized by following parameters: ctrl change bitfield, channel=4, controller no=7, bit number=0. Next stop: ctrl change bitfield, channel=4, controller no=7, bit number=1, and so on.
Unfortunatelly, after programming and pressing the stop buttons they don't switch on the relative GO stops anymore - nothing happen :(.
I can't attach the file directly here, so I do it via rapidshare. The file consists of the MIDI command list of each buttons recorded via MIDI-OX. Maybe it helps to recognize the problem. Curiously, many of OFF commands for various stops are the same.
Kind regards
Pawel

Link to file: http://***************/share/FE7D232FDD05A462CA6A2FBB3ECE54CD
 

pwos

New member
Something wrong happened with the link :confused:. There is posted again as a plain text:
***************/share/FE7D232FDD05A462CA6A2FBB3ECE54CD
 

e9925248

New member
The dialog incorrectly allows only to enter up to controller 7 - I'll fix this in the next update.
 

pwos

New member
Many golden thanks, Martin. I found on sourceforge.net you have just made corrections (r1653). Your knowledge and action speed is miracle. I will wait patiently for a new GO windows built - I tried to launch GO under Ubuntu but as a green Linux user I probably can't join properly GO with audio jack panel or can't set audio jack parameters.
By the way, maybe is there something what I could make for GO developement? I consider translating GO to Polish.
 
Krummhorn

Krummhorn

Administrator
Staff member
ADMINISTRATOR
pwos said:
Something wrong happened with the link :confused:. There is posted again as a plain text:
***************/share/FE7D232FDD05A462CA6A2FBB3ECE54CD
Click to expand...

pwos said:
Upss, again the same. Please replace asteriks with 'rapidshare(dot)com'
Click to expand...

Admin Note:
FYI: rapidshare(dot)com showed up that way because it is blocked by this forums software. Rapidshare, in the past has, and continues to, violate copyright laws in its distribution of music titles. We got into trouble with ASCAP and other copyright nannies and were forced to take that action to protect ourselves from further problems with the distribution of copyrighted media.

Please understand that we are not saying that what you have linked is copyrighted or that any violation has occurred in your behalf, but we can't allow 'rapidshare' redirects from our site to theirs for other copyright issues dealing with ASCAP and others.
 

L.Palo

New member
If you have downloaded the source files for GrandOrgue you'll find excellent instructions in the README and README.translate files in the trunk folder. Personally I use Poedit to manage the translations but there are other softwares that can do it too.

I've for a long time tried to convince my wife to make the translations of the strings into Polish but so far she didn't find the time to do it... So, if you've got a few hours to spare feel free to make the translations.

Kind regards

Lars P
 

e9925248

New member
pwos said:
Many golden thanks, Martin. I found on sourceforge.net you have just made corrections (r1653). Your knowledge and action speed is miracle. I will wait patiently for a new GO windows built - I tried to launch GO under Ubuntu but as a green Linux user I probably can't join properly GO with audio jack panel or can't set audio jack parameters.
Click to expand...
There are r1653 WIndows builts without ASIO on the OBS too (see the bottom of the page).

To support a easiert GO startup on Linux, I have created this for openSuSE 13.1:
http://software.opensuse.org/download.html?project=home:e9925248:grandorgue&package=goconfig-all

If you install it on a fresh openSuSE 13.1, it should convert it into a ready-to-use GO only configuration. I don't recommend installing it over an existing openSuSE, as it will change the way, the system works and deinstalling the package will not revert all changes.

By the way, maybe is there something what I could make for GO developement? I consider translating GO to Polish.
Click to expand...

Something to start reading:
https://sourceforge.net/p/ourorgan/discussion/962125/thread/26fe341e/
https://sourceforge.net/p/ourorgan/discussion/962124/thread/61fa53a8/
 

e9925248

New member
Krummhorn said:
Please understand that we are not saying that what you have linked is copyrighted or that any violation has occurred in your behalf, but we can't allow 'rapidshare' redirects from our site to theirs for other copyright issues dealing with ASCAP and others.
Click to expand...

The list of stop names + MIDI messages could also have been posted as part of a forum post.
 

pwos

New member
Thank you Lars for the info. I also read the sourceforge threads that Martin linked below. I think I'll be able to do the translations. Finding free time would be the biggest problem :) You've told me lately by email that you unsuccessfully tried to encourage your wife to enjoy herself being a translator.
Kind regards for you and your wife from Poland.
Pawel
 

pwos

New member
e9925248 said:
There are r1653 WIndows builts without ASIO on the OBS too (see the bottom of the page).
Click to expand...

Thank you Martin. Actually, there are, I didn't see it before. But I guess, "w/o ASIO" means there is GO compilation without audio channel managing functions? or without supporting ASIO4ALL sound drivers? I personally use kx project drivers.

e9925248 said:
To support a easiert GO startup on Linux, I have created this for openSuSE 13.1:
http://software.opensuse.org/download.html?project=home:e9925248:grandorgue&package=goconfig-all

If you install it on a fresh openSuSE 13.1, it should convert it into a ready-to-use GO only configuration. I don't recommend installing it over an existing openSuSE, as it will change the way, the system works and deinstalling the package will not revert all changes.
Click to expand...

I will try it, maybe opensuse will be more userfriendly distribution for me than Ubuntu.

e9925248 said:
Something to start reading:
https://sourceforge.net/p/ourorgan/discussion/962125/thread/26fe341e/
https://sourceforge.net/p/ourorgan/discussion/962124/thread/61fa53a8/
Click to expand...

I will follow it. Thank you.
 

e9925248

New member
pwos said:
But I guess, "w/o ASIO" means there is GO compilation without audio channel managing functions? or without supporting ASIO4ALL sound drivers? I personally use kx project drivers.
Click to expand...
It means, that you can use any ASIO drivers with this GO build (including ASIO4ALL). All other kind of sound drivers are still working.
 

pwos

New member
I've just tested controlling stops with GO (r1653) - and EUREKA!!! It works - stops, couplers, cancel button, seems that everything is OK. Martin, you are the Master. I can officially announce that GO (starting r1653) is fully compatible with Content D2800 organ, and probably with other organs made byElpro BV (NL) since mid of 1990's till ???
Many thanks Martin again. Pitea samples sounds great, thank you Lars too. So excited, I started to make polish translation of GO.
 
You must log in or register to reply here.
Top