Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - martin

Pages: [1] 2 3 4 5 6
The GO internal MIDI player had always played (on a two manual organ) the pedals from channel 3 [for non-GO MIDI recordings]. Before 2205, events would have been matched manual assignments too - yielding to playing the pedal from two channels.

GO MIDI recordings are different, because the various GO sysex adapt the MIDI matching.

PS: If you are using an external MIDI player, please make sure, that it creates a (virtual) MIDI port, GO can connect to.

Are the MIDI files GO recordings (played back on the same or different sampleset)?

English / Re: Grand Orgue not compatible with LINUX MINT 18.2
« on: 22. December 2017, 22:06:25 »
Determine, which Ubuntu version your Linux is based and make sure, that you install GO for that Ubuntu version.

Else: You can grab the GO source package for that Ubuntu version (3 files) and compile it yourself:
Code: [Select]
sudo apt-get install build-essential fakeroot
dpkg-source -x grandorgue*.dsc
cd grandorgue-0.3.*
dpkg-buildpackage -rfakeroot

Your computer should do the same as any expander: Receive MIDI events from the organ MIDI out and send the audio signal to any kind of speakers.

In your case, connect organ MIDI out to MIDI in of your PC and PC midi out to the organ audio in. If the audio in is intented for an expander, it should mix the external audio signal with the organ sound.

Has the organ an audio input? You need to connect the laptop audio output to the speakers.

English / Re: Loading Sample error when certain keys are pressed
« on: 15. October 2017, 22:21:23 »
You configured a MIDI organ change event in the GO settings/Organs for the loaded organ.

English / Re: Memory in Windows XP
« on: 25. July 2017, 22:59:06 »
The GO memory usage is reported in the organ properties. Otherwise look at the windows task manager.

English / Re: Help! I have messed up!
« 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.

English / Re: Can't connect external stops
« on: 24. June 2017, 21:24:24 »
Here you can get GO binaries for all major distributions:

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.

English / Re: Can't connect external stops
« 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.

English / Re: GO LIve
« on: 04. May 2017, 09:20:41 »
I doubt, that this causes boot issues - but using one stick on multiple machines might cause trouble, because eg. the saved settings have the audio interface of the other machine configured.

English / Re: Audio Interface for Grand Orgue linux
« on: 16. March 2017, 20:06:12 »
Playback-time of a 128 buffer @44.1kHz is 2.9 ms - and you need always at least two buffers, so 5.8ms is the technical minimum.

Playback-time of a 512 buffer @44.1kHz is 11.6 ms - and you need always at least two buffers, so 23.21ms is the technical minimum. The 17ms value of jack is incorrect. Either jack does not consider a second buffer, then you need at add at least 11.6 ms or its otherwise incorrect.

English / Re: Audio Interface for Grand Orgue linux
« on: 13. March 2017, 08:57:08 »
Reverb in use?

English / Re: Audio Interface for Grand Orgue linux
« on: 13. March 2017, 08:56:39 »
What did you select as desired latency? What is reported by GO as latency?

English / Re: GO LIve
« on: 19. February 2017, 13:09:49 »
1.Can I run it on a computer that has Windows already installed? As long as Windows doesn't start, can I safely just turn the computer on and off as you describe?

Yes - but you need to keep windows seperate. GOLive requires its on partition(s). Don't mount Windows partitions to keep them seperate [if Windows is shutdown (not hibernate), you many temporarily mount a windows drive - but don't forget to unmount before stopping GOLive]

2.Can I run it on a computer that has GrandOrgue installed in Windows?

GOLive does not event notice your windows installation - the live installer might just suggest to mount your windows drives.

3.In the bootable USB stick install, what about other software? I like to run KXProject for audio, would I still be able to do that? (there is a Linux version of KX)

Pointer to the linux version?

"The kX Project is an independent development project, focused on providing free WDM Audio Drivers for kX-Compatible sound cards."
Linux has not WDM driver model.

GOLive is intended to be a "as-is" ready to use preconfigured solution. Its based on openSuSE Leap 42.1, but it is different (eg. no displaymanager, systemd user sessions, ...).
If you want something flexible/configurable, start with a normal linux distribution.

4. You say the MIDI is not implemented in GO Live. I don't understand this, it's useless without MIDI. Can you clarify?

Pointer? GOLive supports MIDI (A real world example:

5. Is there detailed documentation for GOLive anywhere? I'm not finding any.
There is not much documentation. It just keeps GO running and does not offer much other things.

PS: A GOLive update is overdue - GOLive will get the persistent device name feature by running in a terminal
zypper refresh
zypper dup
chkstat -system

Pages: [1] 2 3 4 5 6