• 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 for Windows 32/64

Cybug

New member
Hi
Deleted cache as requested.
1) Win7 x64 with 3.0.5 x64 No Cache compression. No out of date cache warnings at start of organ loading as expected.
Loaded organ (1.5gb) fairly quickly but then cpu went to 100% and system hung as last time. Terminated after 10minutes - reboot.
Same result with Compression set.

2) Win7 with 3.0.5 x32 No cache compression. No error message at start. After loading organ cpu went to 100% and system
hung as before. Terminated after 6 minutes - reboot.
Same result with compression set.

3) Tried build 956x64 without compression same as above.

4) Repeat above with small test organ (150mb) Able to play a few notes before the buffers filled even though cpu showed 99%.
GO crashed in module ntdll.dll after a few minutes.

5) Loaded organs in 24/3/ build and ran smoothly as before so we can assume that whatever the problem is it hopefully not my
system :)

Chris
 

erikds

New member
Hi
Deleted cache as requested.
1) Win7 x64 with 3.0.5 x64 No Cache compression. No out of date cache warnings at start of organ loading as expected.
Loaded organ (1.5gb) fairly quickly but then cpu went to 100% and system hung as last time. Terminated after 10minutes - reboot.
Same result with Compression set.

2) Win7 with 3.0.5 x32 No cache compression. No error message at start. After loading organ cpu went to 100% and system
hung as before. Terminated after 6 minutes - reboot.
Same result with compression set.

3) Tried build 956x64 without compression same as above.

4) Repeat above with small test organ (150mb) Able to play a few notes before the buffers filled even though cpu showed 99%.
GO crashed in module ntdll.dll after a few minutes.

5) Loaded organs in 24/3/ build and ran smoothly as before so we can assume that whatever the problem is it hopefully not my
system :)

Chris

I have exactly the same results here, also using Windows 7.
Also point 5 is valid here, with the problems reported earlier.

All the best.

Erik.
 

JLD

New member
You can download the latest 961+patches releases from the SourceForge site:
https://sourceforge.net/projects/ourorgan/files/Development releases/
(These are not official 'stable' development releases but since what was available had major issues, this will allow more testers to confirm the fixes are working and update trunk accordingly)

This should solve most of the problems.
Let us know if this is the case.
Would also like to hear if playability is good (sound quality, staccato, etc.)

JL
 
Last edited:

Cybug

New member
Hi
Just ran a quick test on Win7 x64. Loading issues now seem OK. Loaded and ran in Compression and Non-compression cache.
Sound is good with no apparent pops, crackles, delays etc.
Lots more to play with but promising so far:)
Thanks

Chris
 

erikds

New member
1) About the release setup_GrandOrgue_0_3_0_5_Cygwin.Mingw64.win64.961+patches.exe, dated 19-04-2012

This release runs without problems on my Windows 7 64 bit PC with Quadcore Q6600 processor.
Organ used: PiteaMHS 3 manual + pedal
Settings:
Active Polyphony management: on; Release Sample scaling: on; Randomize pipe speaking: on
Interpolation: Polyphase; Concurrency level: 32; Release concurrency level: 4
Samples per buffer: 256
Audio output: Device: Windows WDM-KS (PA), 2 channels
Very good tactile response, no noticeable latency.

I cannot add an additional device in this release.
This would be nice to be able to send each division to a separate stereo audio channel.

I did not test the corresponding 32 bit version because it is clearly stated that it will not work on a 64 bit PC


2) About the release GrandOrgue-0.3.0.5-14-04-2012-win64.exe

I have the same problems as described by Cybug on 17-04-2012.

3) About the release GrandOrgue-0.3.0.5-21-03-2012-win64.exe

This release works with certain problems (using the same PC and organ), as reported here http://www.magle.dk/music-forums/15147-more-speakers-channels-grandorgue.html
In this release i can add additional devices using the Windows WDM-KS (PA) driver.
For the PiteaMHS organ i used 3 stereo audio channels.

What is the difference between the release in point 2 and/or 3 compared to the one in point 1?
Why are there 2 different "branches"?

All the best.

Erik.
 

Ghekorg7 (Ret)

Rear Admiral Appassionata (Ret)
Hi,

Report.
In my OS only commit 909 works fine without problems (except memory allocation failure when using RearouteAsio).
All other releases causing heavy crashes, very slow motion on mouse, do not allow even task manager to open and more.
Forcing many times to close my lap pressing the power button....

Then I re-install 909 and all goes super....
The only complain about 909 is that it needs about 5 minutes to load my latest test organ 4GB heavy. Memory allocation about 2.9GB. All, samples, loops ect loaded at 24/48000. Concurrency level at 127 and release at 2.
Sound SUPER. Very much enjoyment !!! so, I can wait for those 5 minutes :) :)

Just downloaded the latest 19-4-2012. I will test it too and post back.

My system : Acer 5738ZG lap win7 home premium 64bit, Intel pentium dual core T4400 at 2.2GHz, 4GB ram, HDD at 5.900rpm.
RealTek soundcard at 24/48000, Asio4all v2.10 and ReaRouteAsio for Reaper 4. Also Jack 1.9.9 beta 64/32bit
 

JLD

New member
Erik:
There is only one branch and we try to provide development releases as the code is developped.
Martin sometimes provides versions with the patches he is working on to verify if these patches are effective.
Eventually, these patches are integrated in the trunk which I use to provide the latest versions at:
https://sourceforge.net/projects/ourorgan/files/Development releases/ where the version from your point 1 comes from.
This is usually the place where you will find the latest quasi stable releases.

This time I did a small digression by adding a few patches to version 961 since we had serious problem to fix and the trunk would not work without the patches.
Since the report from multiple users are good, I will include them into the trunk today.

Ghekorg7:
Please try the version from the link just above. I believe this is the only one with the latest operational code.

Regards,
JL
 

JLD

New member
To avoid misunderstandings I just updated GrandOrgue trunk with the patches that seem to fix the recent problems and make GrandOrgue functional again.
The version of the trunk is now 966 and the installation files have been uploaded to https://sourceforge.net/projects/ourorgan/files/Development releases/
I also uploaded a version without sse3 for people with older computers.

They all seem to be operational but it would be greatly appreciated if you can test them and provide comments.

You might be surprised by the fact the size of the installer went down quite a bit but that is normal since the exe file have been cleaned.
 

e9925248

New member
I cannot add an additional device in this release.
This would be nice to be able to send each division to a separate stereo audio channel.

The current development versions only support "low end" multi channel interfaces (eg. various suround interface of builtin sound cards) - it does not work with high end interface, which provide the various channels as seperate audio interfaces.

This supports need more work, before it can be including into GO.
[If somebody want to test this, revert r943 in trunk - but don't expect it to work properly].

Regarding the last version of JLD:
It should be possible to lower both concurrency settings to about the number of cores.
 

Ghekorg7 (Ret)

Rear Admiral Appassionata (Ret)
Report.

Installed 961+patches x64. - see my system in my previous post

SUPER !!

No issues at all !! No allocation memory things, no freezing. Loads my big 4GB test set about 30 seconds faster than 909. Asio4all visible and also ReaRouteAsio.

One thing only, which was present in all GO (1,2,3) versions in my 64 bit lap (not in my 32bit one) : every one minute or so there are cracks on sound when using RearouteAsio and jack (both 64bit), any set loaded. They stop if I raise latency settings at 320 buffer and above (?) hmmmm why's that ?

Plain GO no problems, usually at 128/48000 (44100 on 1 & 2 versions)

961 rocks !! :-D

All my best
Panos
 

erikds

New member
To avoid misunderstandings I just updated GrandOrgue trunk with the patches that seem to fix the recent problems and make GrandOrgue functional again.
The version of the trunk is now 966 and the installation files have been uploaded to https://sourceforge.net/projects/ourorgan/files/Development releases/
I also uploaded a version without sse3 for people with older computers.

They all seem to be operational but it would be greatly appreciated if you can test them and provide comments.

You might be surprised by the fact the size of the installer went down quite a bit but that is normal since the exe file have been cleaned.

I have played some time now with the 966 releases:
- the 64 bit release on a Windows 7 64 bit PC
- the 32 bit release for older PC's (no sse3) on a Windows XP PC

In both cases GrandOrgue performed flawlessly and i had really low latency.

Regarding the last version of JLD:
It should be possible to lower both concurrency settings to about the number of cores.

Under Windows 7 running on a Quad Q6600 processor i had both concurrency setting at 4.
Under Windows XP these settings were at 1.
No problem in both cases.

Thanks for providing these versions; they do the job very well indeed.

All the best.

Erik.
 

Larioant

New member
I did not understand.


But with this update I seem to have gone back in time.
Who has not updated a computer can not 'use older versions of GO?


also lacks the reverb.


Antonio.
 

e9925248

New member
Could you report the achieved latencies of the last released version of JLD (including the intended latency setting and the samper per buffer setting of GO)?

Please don't use the numbers reported by GO - use something external instead.
The problem with the GO numbers is eg, that RtAudio backends simply return the result of an API call while PA based backends try to consider various effects.
In my option, these numbers don't allow an object comparision.

A comparsions between the ASIO backends (with and without PA in the name) would be interessting.
 

erikds

New member
Could you report the achieved latencies of the last released version of JLD (including the intended latency setting and the samper per buffer setting of GO)?

Please don't use the numbers reported by GO - use something external instead.
The problem with the GO numbers is eg, that RtAudio backends simply return the result of an API call while PA based backends try to consider various effects.
In my option, these numbers don't allow an object comparision.

A comparsions between the ASIO backends (with and without PA in the name) would be interessting.

Hello Martin,

Please tell me how i can verify latency using Windows 7 64 bit with an external something, and i shall report findings.

I have used the latest JLD version (966) with following backends and in all cases:
sample rate at 48000, samples per buffer at 16, desired latency at 8 ms:

- Windows WDM-KS (PA) - GO latency indication 8 ms
- ASIO (PA) - GO latency indication 13 ms
- ASIO - GO latency indication 13 ms

Other backends available are:
- DirectSound
- Windows DirectSound (PA)
- MME (PA)

Unfortunately, no WASAPI backend available.

Just a question: does (PA) in this case mean PortAudio?

All the best.

Erik.
 

Ghekorg7 (Ret)

Rear Admiral Appassionata (Ret)
Hi Erik, :)

(PA) it is PortAudio, yes. Works good here. Also no WASAPI as there at you.

Gonna get me 966 to test it too. I 'll keep at hand 961 just in case :) :-D

Best
Panos
 

e9925248

New member
I don't know any tool, therefore I asked in this forum. The best suggestion on the mailing list has been, to send a midi note and determine the time, until the sample playback starts.

A block size of 16 will increase the overhead in GO - threading will be less effective and maximum polyphony will be likely lower.

The last version of GO changed the block size of GO from 64 to 16 to make RtAudio ASIO work with some audio interfaces (PA ASIO supports them). The change has an performance impact (up to 10% in a quick test). Therefore I'm researching all facts in favour/against this change.

Add WASAPI:
GO support it and I can compile it - JLD had some build issues in his build enviroment.
 

Ghekorg7 (Ret)

Rear Admiral Appassionata (Ret)
Thanks e :)

Report.

966 works fine. No need to keep 961 :-D
The sound is improved, yes this is my impression (my ears are still ok :-D :-D) and I'd say this is the best sound from any GO version so far here.
Loading time is improved too : loads my custom test bed 4GB set (3 x releases for each wav file = 4 wav files for each note) at 24/48000 in 4:34 min. This is 30 sec faster than any previous version. Memory allocation issue free , on this set reaches around 2.940MB. GOOD.

I know GO supports WASAPI, I tested it here and works. Just didn't see it on 961 then (I didn't know about JLD's issues).

Just one issue still remains here : When using RearouteAsio and/or Jack 199b I get cracks on sound for 2~3 sec (more or less like firecrackers show) every one minute or so.
This is not happening at all when GO v0305 is working alone with Asio4all or DS (also when I tested WASAPI).
I tried different settings, no work, except when I raised my usual 128 buffers to more than 256 (!), around 360 (256 cracks too). Then cracking stopped, but latency.... Cannot do recordings like this . Sample rate at 48000Hz as is my Realtek on board at 24/48000 too. Reaper422 at 128 24/48000, so are Jack 199b's settings.

I did a quick install on my wife's win7 i5 2410M (sandy Bridge) 2.3GHz lap with 4GB ram and Conexant on board card (+Asio4all 2.11b). Silbermann Marienkirche Mk.I set loaded super fast at 24/48000 and 80 (!) buffers. No issues at all. I didn't try Rearoute though (no Reaper there....)
 
Last edited:
Top