Recent Posts

Pages: 1 2 3 [4] 5 6 7 8 9 10
31
English / Re: Help! I have messed up!
« Last post by Mick Berg on 20. July 2017, 04:58:53 »
Thanks Martin.
I will do that. Maybe something else was wrong.
All the best,
Mick

PS Where are the settings in this forum? I would like to have email notifications of posts.
32
English / Re: Help! I have messed up!
« Last post by martin on 20. July 2017, 01:19:43 »
Loading the demo organ with 8 GB RAM should not crash GO even without any memory limit.
Any loading process is interruptable - so unless the loading is too fast, aborting loading before filling up the memory should be possible.

All global GO settings are stored in a file named GrandOrgueConfig in your user profile directory - remove that file.



33
English / Help! I have messed up!
« Last post by Mick Berg on 19. July 2017, 06:43:49 »
Hi.
I have upgraded the CPU, motherboard and memory in my GO computer. All went well until I tried to increase the memory allowance (I now have 8 gig) and set it to 0 which I believe means unlimited. However it did not go well and now GO crashes.

How can I start GO without loading an organ so I can change the settings back?

I tried loading the demo organ but the memory setting must have stuck as this organ crashes as well.

Thanks,
Mick
34
English / Re: Can't connect external stops
« Last post by martin on 24. June 2017, 21:24:24 »
Here you can get GO binaries for all major distributions:
https://software.opensuse.org//download.html?project=home%3Ae9925248%3Agrandorgue&package=grandorgue

As the messages are reaching the GO Log windows, there is no plattform specific code in between - it should be handled the same on all platforms.

* CPU of your organ PC?
* Linux distribution and release?
* Any distribution packages replaced?
* wxWidgets version?
* Xorg X11 in use?
* GO version?
* GO sound generation working (eg. turn a stop and key via mouse on)?
* What is exactly logged for the MIDI messages in the GO message window?
* Any (message) popup windows open/showed by GO?

If the playback is working, enable MIDI monitoring, right click on a stop, on the receive tab click on "Listen for event". The button should stay pressed and the cursor changes to the waiting symbol. Trigger a MIDI message (GO should react to 9x note, Bx control change, CX control change) - it should be listed in the Log window and the dialog content changes.


35
English / Re: Can't connect external stops
« Last post by bill.p on 23. June 2017, 16:03:46 »
Here's where I'm at now.
Using a simple program to inject sequences of bytes through Jack to GO I can now set up the stops to respond to controller messages on my desktop box. Using what is the same version of GO on the organ cpu with the same sequence of bytes coming from the Arduino GO fails to respond when 'listen to complex event' is pending. I've rebuilt GO on the organ box to ensure that it's the same version, and monitored the bytes going through jack, and it all looks identical, but no joy.

The events are logged in the GO message window, so they are reaching GO, but for some reason they don't get through to the right place?

If I run GO under gdb I see the bytes received, but I don't understand enough of the internals to track it down. It gets put onto a message queue and I assume some other thread is going to pull it off, but I don't know which file or function to look in to see what happens. Any pointers welcomed...

Bill
36
English / Re: Can't connect external stops
« Last post by martin on 22. June 2017, 09:18:38 »
I've now got the stop scanner working as far
as sending MIDI events, currently "0xB5 num 1/0" but this is only my first guess. It connects
via Jack and my jack midi monitor displays the events and looks good. :)

First, check that the MIDI device is enabled as input in the GO option.
GO also includes a display MIDI events options. After that, check, that the MIDI events are received by GO.

For stop setup, use "detect complex MIDI event".

PS: Some "num" of Control Change (0xB?) are reserved for special purposes.
37
English / Can't connect external stops
« Last post by bill.p on 21. June 2017, 12:27:51 »
Hi there,
I'm building a three-manual organ for our new church, using MIDI keyboards and various
stops and pistons, scanned using Arduinos. I've now got the stop scanner working as far
as sending MIDI events, currently "0xB5 num 1/0" but this is only my first guess. It connects
via Jack and my jack midi monitor displays the events and looks good. :)

When I fire up GO, using the Demo version, I want to programme the stops to respond to the
midi events, but it doesn't seem to like it. Using Listen for Midi Event it just sits and does nothing,
I tried filling in the details, specify device, Program On/Program Off, but still nothing doing. :-\

I've not found any detailed instructions on how to set these things up, or what restrictions apply.
Can anyone point me at a good tutorial for this, or simply tell me what to do?

Many thanks.

Bill
38
English / A question of playing MIDI's
« Last post by johnbooch on 24. May 2017, 07:22:57 »
I've been trying to use this program to playback MIDI's that were not made in it, but I can't find a way to assign a MIDI channel to each keyboard of the instruments.
Does anybody know how to do this for playing MIDI's?
39
Correction - SIXTEEN (16) GB RAM - not One (1) GB!
40
English / CAEN/ST ETEINNE and WALCKER-WIDERVANK simultaneously playing BACH
« Last post by Pneuma on 04. May 2017, 10:39:14 »
Thanks to sonusparadisi and Lars Palo, we Grand Orgue users now have a nice demo of the Cavaille-Coll organ at The Abbey of St Eteinne in CAEN, France. While the registration is huge I did not vary it, but I played a MIDI downloaded recording of a Bach piece. It can be watched and listened to at . If I were an organist and Understood proper registration it would be so much better.

The other organ playing simultaneously to round out upper-work is the free Sample Set of Walcker-Wildervank. Due to my hi-freq hearing loss I eq-ed the recording. Hope it does not hurt your ears. Loaded both organs at 20-bit, 1024 buffer and 48KHZ using 64-bit LINUX Mint with 1GB RAM. There is one tny brekup late in the piece due to overload, but it is overall worth listening to. Enjoy!
Pages: 1 2 3 [4] 5 6 7 8 9 10