GO for Windows 32/64

[Cybug]

Hi - Here are the sizes as requested:-

XPx64 3Gb Memory Lossless Compression: Allocated Memory = 1960938. Cache = 0. Pool Size = 2047691.

Win7 x64 16Gb Uncompressed : Allocated Memory = 3125910. Cache = 0. Pool Size = 2047645. - This gives the Alloc errors as previously.

Win7 x64 16Gb Lossless Compression : Allocated Memory = 1828125. Cache = 0. Pool Size = 2047645.

Hope this helps - anymore info required just ask.

Cheers

Chris

[Cybug]

Hi
I'm having problems with another organ installation while loading which runs fine in GO v2. This causes GO3 to crash and requires either stopping the process using task manager or a re-boot. This is using your recent 32bit build on Win7 x64 with 16Gb ram. Do you wish me to pass on any details or should I wait until the software is more mature and try again?
Thanks
Chris

[e9925248]

I'm always interested into new problems

[Cybug]

Hi - Using your recent 32bit build on Win7 x64 with 16Gb ram I have an APPCRASH while loading a 2GB organ which runs fine on the same machine using GO v2. The crash report is as follows:- App Name: GrandOrgue, App Version: 0.3.0.3, App Timestamp: 4f1348ce, Fault Module Name: msvcrt.dll, Fault Module Version: 7.0.7600.16385, Fault Module Timestamp: 4a5bda6f, Exception Code: c0000005, Exception Offset: 0000abc7.
The Memory used from the Process Tab is 2177824K which is left after GO is closed and needs clearing manually. Hope this helps - any more info required just ask.

Chris

[Diode]

Hi All,

I have been a satisfied user of Grandorgue 0.2 since it's release and I have been eagerly awaiting 0.3. As I have an old Pentium 4 with no SSE3 support I recently installed GrandOrgue_without_sse3_build763.exe. I am very impressed with how this build sounds in comparison to 0.2.

Burea extended loads fully into 3GB of RAM under XP Pro (32) with lossless compression set. After the samples have loaded GrandOrgue's log contains 31K of "PoolAlloc failed" exceptions on my system - but I agree that they are non-fatal (GO behaves just fine if they are ignored).

0.3 build 763 definitely sounds better than 0.2 on my system when using the same sample set and the same supporting software (ASIO4All, Jack 1.9.8, qjackctl 0.3.4.10, Freeverb 3, and Savihost 1.36), and there is no obvious latency. My soundcard is an old SB Live with KX drivers. Incidentally - for anyone else using an SB Live for GO I strongly recommend that you ditch Creative's original drivers and replace them with KX as these offer noticibly better intermodulation distortion performance.

Sincere congratulations and thanks to the GrandOrgue developers for your efforts in refining GrandOrgue this far.

Regards,
Diode

[e9925248]

I have published a new build:
https://sourceforge.net/projects/e99...es/GrandOrgue/

It includes a new interpolation method: polyphase. The old method is called linear.

Polyphase has higher CPU demand. Polyphase + lossless compression enabled is currently handled as if linear has been selected.

[Cybug]

Hi - Thanks for the new builds.
I have so far tried the 32bit version on Win7x64 and XPx64 with the same result.
I am unable to "OPEN" an organ that has not previously been loaded but I can "OPEN RECENT" organ OK.
When attempting to "OPEN" an organ in Win7x64, GO crashes with the following info:
APP Crash GrandOrgue.exe
App Version: 0.3.0.4
App Timestamp: 4f37c550
Fault Module Name: wxmsw28u_core_gcc_custom.dll
Fault Module Version: 2.8.12.0
Fault Module Timestamp: 4ed5558d
Exception Code: c00000fd
Exception offset: 000db7de

Having loaded an organ in the recent list with no lossless compression all seems OK.
The "Close" organ function does nothing but you can overload another "recent" organ without any obvious problems.
Attempting to "Open" an organ even after a successful "Recent" organ, GO still crashes as above.

As you probably know I don't get any fault output when GO crashes in XPx64 but conditions are identical so I assume the crash is the same as Win7x64.

I'll try the x64 versions as soon as I can.

Cheers

Chris

[e9925248]

I'll try the x64 versions as soon as I can.

You can skip this test - please wait for my next build.

[e9925248]

Sorry for the broken version - I put a new build online, which should fix the bug.

[Cybug]

Sorry for the broken version - I put a new build online, which should fix the bug.

Hi - Absolutely no need to apologise, I'm just very grateful for the huge effort you guys are putting in and I'm very happy
to help as much as can :-)

Thanks again for the new build.

So far I have tried the 32bit and the 64bit versions on Win7 x64 with slightly different results.
On the 64 bit version I can load all "Recent" organs OK with Linear and Polyphase settings.
The audio output differs somewhat with two settings but I haven't spent too much time using
either so far.
I have also tried a new organ version which is slightly larger in memory size than I have before. This loads
fine in the 64 bit version and un-compressed shows in GO Properties Allocated Sample Memory:-1377.906MB,
Memory Cache:0 and Max Memory Pool Size:2.184MB. The Task Manger shows GO allocated: 5,656.608 MB.
The compressed figures are 3475.555Mb, 0, 15.637Mb and Task Manger 3,656.460Mb. I do also get the odd PoolAlloc
reports but seems to run OK.

Moving onto the 32 bit version.
Loading "Recent" organs seems all fine but attempting to load the larger organ fails with an AppCrash.
This occurs with No-Compression and Compression set. The failure report is as follows:
App Version: 0.3.0.5
App Timestamp: 4f3a14da
Fault Module: msvcrt.dll
Fault Module Version: 7.0.7600.16385
Fault Mod Timestamp: 425bda6f
Exception Code: c0000005
Exception Offset: 00009b60

This looks similar to the problem we saw before - see report on 25th Jan.
The Memory Allocation as given in the Task Manager for GO is 2756.752Mb
Non-compressed and 2436.564 compressed after the crash.

Anyway even with polyphase the latency has only increased a little from around 24 to 34 but
as yet, I haven't had much time to play about - my better half is recovering from an operation,
so I'm chief cook and bottlewasher at the moment :-(
I only have 3Gb on my XP box so I'll try v0.3.0.5 probably tomorrow without the new larger
organ for now.

Regards

Chris

[e9925248]

On the 64 bit version I can load all "Recent" organs OK with Linear and Polyphase settings.

Linear/polyphase is a runtime setting. You can switch it without reloading.

This loads fine in the 64 bit version and un-compressed shows in GO Properties Allocated Sample Memory:-1377.906MB,
Memory Cache:0 and Max Memory Pool Size:2.184MB. The Task Manger shows GO allocated: 5,656.608 MB.

Wasn't that a 32 bit version? 2 GB max Pool size seems to indicate a 32 bit version and -1.3 GB looks like a integer overflow (if that is true, it would 2.9 GB).

In that case, you should have got a pool alloc error.

The compressed figures are 3475.555Mb, 0, 15.637Mb and Task Manger 3,656.460Mb. I do also get the odd PoolAlloc
reports but seems to run OK.

The computer has about 15GB RAM?
These numbers should not have resulted in a pool alloc error.

Moving onto the 32 bit version.
Loading "Recent" organs seems all fine but attempting to load the larger organ fails with an AppCrash.
This occurs with No-Compression and Compression set. The failure report is as follows:
App Version: 0.3.0.5
App Timestamp: 4f3a14da
Fault Module: msvcrt.dll
Fault Module Version: 7.0.7600.16385
Fault Mod Timestamp: 425bda6f
Exception Code: c0000005
Exception Offset: 00009b60
This looks similar to the problem we saw before - see report on 25th Jan.
The Memory Allocation as given in the Task Manager for GO is 2756.752Mb
Non-compressed and 2436.564 compressed after the crash.

GO got the captibility to select the loading format for each pipe/rank seperatly (I don't remembers, if it was already present in my last 0.3.0.3 build) and tries to continue without crashing, if it rans out of memory during loading. In your case, continuing failed.

The MS crash information in that form is quite useless. The crash reporting tool produces some files [you can reach them via technical information in the crash dialog], which carry more information.

[Cybug]

Hi - Thanks for your reply.

I have now tried both x32 and x64 builds using XP64 with 3GB Ram. All Organs, obviously within the memory bounds,
load with no problems seen and sound very good.
Just as an aside, all my organ versions are 16bit single loop and I don't have a 32bit version of XP available to test.

Reference your email above - I will double check my findings today just in case I did confuse the results.

Thanks - Chris

[e9925248]

Allocated Sample Memory:-1377.906MB

Did you really get this negative number (=> GO bug) or is it just a typo?

[Cybug]

Hi - just a quick answer - yes it's a typo - sorry
Will post the details of the repeated tests tomorrow.

Chris

[Cybug]

Hi - 4 Test results on Win7 x64 16Gb Ram.

1) v3.0.5 No compression 32bit build AppCrash GO v0.3.0.5
Fault Module: msvcrt.dll
Module Version: 7.0.7600.16385
Exception Code: c0000005
Exception Offset: 00009b60
GO Process Memory in Task Manager 2,756,788K

Re-boot Win7

2) v3.0.5 compression 32bit build AppCrash GO v0.3.0.5
Fault Module: msvcrt.dll
Module Version: 7.0.7600.16385
Exception Code: c0000005
Exception Offset: 0000aba6
GO Process Memory in Task Manager 2,405,448K

Re-boot Win7

3) v3.0.5 No compression 64bit version loads OK after:
Approx 50+ PoolAlloc failures
Organ Properties:
Allocated sample memory: 1377.907 MB
Mapped memory : 0
Maximum Memory Pool size: 6.763MB
GO Process Memory in Task Manager 5,652,064K

4) v3.0.5 Compression 64bit version loads OK after:
Approx 50+ PoolAlloc failures
Organ Properties:
Allocated sample memory: 3475.556MB
Mapped memory : 0
Maximum Memory Pool size: 6.762MB
GO Process Memory in Task Manager 3,637,372K

Hope this helps.

Chris