Recent Posts

Pages: 1 2 3 4 5 [6] 7 8 9 10
51
English / Re: Bx controller problems
« Last post by Pneuma on 18. March 2017, 00:39:55 »
As a retired manufacturer of MIDI Interface Systems, all I can tell you is that Controller 7 in MIDI is the standard for controlling volume. I have one of our M128/256 MIDI Processors being used for Swell and Pedal but have not as yet lashed up our CPU Controller 7 A-to-D input. Unfortunately, I have no foot shoe for the input, so I simply have always left it jumpered HI (+5) for full Controller 7 level of 127. I recently located a test potentiometer in my workshop with a .100" socket connector and I'll try to test that soon and post a further reply.
52
English / Re: samples/buffer, keying, and reverb
« Last post by Pneuma on 18. March 2017, 00:32:55 »
I get a little pop on both the down-stroke and up-stroke of Middle C only. Sometimes it goes away. I only get it when keying on Channel 1 MIDI. Seems it may be a glitch in GO 3.1.2084. I refuse to use the later GO versions because in my setup you constantly get note on/off restarts when using heavy registrations. I learned the hard way and rolled back to 2084.

In my limited technical opinion, Ken, I would recommend a LINUX Mint 64-bit solution to try first.
53
English / Bx controller problems
« Last post by ken on 17. March 2017, 16:07:06 »
Hi everyone:

I'm having trouble with GO keeping track of my expression Bx controller. It is running thru an encoder that is connected via USB. It seems there are multiple encoders numbered in the  listed in the Midi devices menu, but in reality there is only one. If I uncheck the extra ones, then I can't detect the expresion shoe. GO seems to pick one, and then can't decide if it wants to use it.

Also, what is the element "controller No." next to the channel menu on the enclosure detection menu? A value of "7" has appeared there. I have no idea what it is referring to. If I change it to correspond to the encoder #,  nothing  works. Using ASIO version 2171 on Win 7pro.  Thanks, Ken Barta  krbar@verizon.net
54
English / samples/buffer, keying, and reverb
« Last post by ken on 17. March 2017, 15:22:22 »
Hi All:
After many years of playing GO, I eventually have discovered the following:
1:s/buffer setting lower than 1024 results in the CR not working.
2. s/buffer setting at 1024 (max) there is a an electronic popping as the key is depressed, but the CR works.
3. s/buffer setting at 512, the popping stops, but the CR stops working.
4. I'm using large sample set OMNI, but I've noticed this in small sets also.(1-3 are true)
5. What kind of conflict is going on between s/buffer, keying, and the CRev. I've tried Lars' IRs, but no difference.
6. I'm using GOvers 2171ASIO on Win7pro, multichannel speakers. These is no CPU overload. RAM is 8gig
Can someone please resolve this. Would like to have clean keying with a good reverb.
Thanks, Ken Barta krbar@verizon.net
55
English / Re: Audio Interface for Grand Orgue linux
« Last post by martin 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.
 
56
English / Re: Audio Interface for Grand Orgue linux
« Last post by eizanprime on 14. March 2017, 00:32:55 »
When using GrandOrgue directly on alsa, with 128 frames per buffer according to grandorgue, I get 10ms of latency, no matter the desred latency I put in (I wonder if it actually has any influence)

When plugging grandorgue through jack, I can't do it with less than 512 frames per buffer without getting a RT Api stream closed error from grandorgue, and with 512 frames jack tells me I have around 17ms of latency.

I'm not using any reverbs, I am even using the demo samples and piano samples in order to track down latency. With other wetter samples, I feel that my latency + the latency of the wetter sample makes it unplayable.

I'm am used to the real instrument, I feel like I can't achieve piece as long as I don't have at least less than 5ms total latency, but I won't know since I don't have it.
57
English / Re: Audio Interface for Grand Orgue linux
« Last post by martin on 13. March 2017, 08:57:08 »
Reverb in use?
58
English / Re: Audio Interface for Grand Orgue linux
« Last post by martin on 13. March 2017, 08:56:39 »
What did you select as desired latency? What is reported by GO as latency?
59
English / Audio Interface for Grand Orgue linux
« Last post by eizanprime on 12. March 2017, 19:53:28 »
 I finished my grandorgue setup on Archlinux, and I am very happy with the software. However, I feel like I am getting mad with the latency, which is probably due to my integrated soundcard that can't handle less than 256 frames per buffer, ending up with about 20 ms of latency (which definitively feels like more). Or maybe is it my cheap usb keyboard ? Or my cheap midi interface for my 100% homemade pedalboard.

 Anyway, I think I need an audio midi interface in order to have no latency (do I ? are there optimizations I could do to avoid buying one) Could you please recommend me a cheap one compatible with linux ? (I am quite broke, hence why I made the pedalboard myself from wooden planks).

Here is my config = Archlinux, intelcore i7 960, asus sabertooth x58 motherboard, 8 gigs of ram.

Thank you very much for your help !
60
English / Re: Not enough memory??
« Last post by Pneuma on 10. March 2017, 03:00:59 »
I've got four organs running simultaneously with 16GB RAM and an Intel Quad-core. Maybe you should switch to LINUX Mint 64-bit. (Four organs are Barton, Silbermann, Burea AGO, and Burea Original. Titanic Tutti!
Pages: 1 2 3 4 5 [6] 7 8 9 10