GO for Windows 32/64

[Cybug]

Hi
Having been using GO v0.2 for some time now I would be interested in trying the latest version v0.3.0.3? I note there seems to be a huge effort in updating GO with all kinds of new goodies and I'm looking forward to the official release:-)
I the mean time, is it possible to download a current built windows version so I can have a play?

Thanks

Chris

[e9925248]

Hi
Having been using GO v0.2 for some time now I would be interested in trying the latest version v0.3.0.3? I note there seems to be a huge effort in updating GO with all kinds of new goodies and I'm looking forward to the official release:-)
I the mean time, is it possible to download a current built windows version so I can have a play?

You can use my build from december (see http://www.magle.dk/music-forums/144...ws-7-64-a.html / https://sourceforge.net/projects/e99...es/GrandOrgue/ ).

[sesquialtera]

I've just discovered the new 0.3.0.3 version by chance ...
I didn't know there was a new version ...
Did I miss a thread with the annoucement ?
What are the advantages of the GO 3.0.3 ??
Thank you .

[Cybug]

Hi
Thanks very much for the info and the downloads. I did try and build a GO v3 some time ago but struggled. I will try again, using the new info supplied, sometime in the future :-)
Having used v2.xx on XP64 for some years with no problems, I decided to start from a known base before I plunge into the Win7 abyss and have just had a quick play with the 32bit version. Is there a list of known issues/problems available, so should I come across any, I don't duplicate? So far it sounds and looks good on a small 1Gbyte instrument.
Thanks again for your help.

Regards

Chris

[e9925248]

There is no official release yet. 0.3.0.3 has been used for all development versions of the last months - therefore I index them by build date.

For information about the changes, please read the thread, I mentioned, and look at the for menu options. You can read the ODF chapter of the help, the rest is mostly outdated.

[Cybug]

Hi
Is it fair for me to assume that the current developement build v3.0.3.0 is backward compatable with v2.0.1 .organ ODF's? I seem to ba having a lot of load failures with larger organs with regard to memory issues i.e. out of memory allocating attack, loop, release. Also with msvcrt.dll v7.0.3790.3959. I have also noticed that the Release Sample Scaling doesn't seem to function as it did in v2.0.1. eg the staccato effect is poor or non-existant on wet samples with 5 second tails.

Thanks

Chris

[Dorsetmike]

It may be my imagination but 0.3 seems to be slower loading .wav files than 0.2, but at least there is now a chance of an error message rather than just a shut down. Having said that I'm afraid some of the error messages don't mean an awful lot to me (yet).

[astazou]

Hi
Is it fair for me to assume that the current developement build v3.0.3.0 is backward compatable with v2.0.1 .organ ODF's? I seem to ba having a lot of load failures with larger organs with regard to memory issues i.e. out of memory allocating attack, loop, release..

Which sets ? I don't have any commercial set, and all the free ones I use load nicely.
You should report your problems to the development team on Sourceforge (http://sourceforge.net/projects/ourorgan)

[e9925248]

Is it fair for me to assume that the current developement build v3.0.3.0 is backward compatable with v2.0.1 .organ ODF's?

It should - if not, its a bug.

I seem to ba having a lot of load failures with larger organs with regard to memory issues i.e. out of memory allocating attack, loop, release. Also with msvcrt.dll v7.0.3790.3959.

32/64 bit GO? 32/64 bit OS? Size of the sample set (on disk)? RAM size? "Sample size" setting in the settings dialog? "Lossless compression" setting?

With "Lossless compression" off and a "Sample size" setting of 16 bit, the memory usage of the 32 bit GO trunk should be compareable to GO 0.2. Any different configuration can result in a different memory usage. File/Properties allow to check the current memory usage.

I have also noticed that the Release Sample Scaling doesn't seem to function as it did in v2.0.1. eg the staccato effect is poor or non-existant on wet samples with 5 second tails.

Work on this topic has been started.

[e9925248]

It may be my imagination but 0.3 seems to be slower loading .wav files than 0.2, but at least there is now a chance of an error message rather than just a shut down. Having said that I'm afraid some of the error messages don't mean an awful lot to me (yet).

Try creating a cache (File/Update cache)

What are the problematic error messages?

[e9925248]

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

The biggest change is the new audio engine featuring multi loop support.

[Cybug]

Hi - Thanks for the new build :-) I will try again on the same base i.e. XP 64 - 32bit GO and 3GB Ram as per my message above which I should have referenced when raising the problems - Oops sorry :-(

[Cybug]

Hi - Tried new build but the problem is still there. The organ that fails is a 3 Manual,56 Stops, 16 Couplers, 24 Presets + Generals. The total size of this organ is around 2.2Gb. I have been using this for around two years on GO v2.0 without any problems. The error message is "out of memory allocating attack" and occurs approx 2/3rds of the way through loading. It is not a RAM issue as there is still over 1.4Gb of physical memory available at this point.
On the plus side the sound quality seems much clearer than v2.xx without the use of Release Sample Scaling on the smaller organ (around 1.2Gb) that will load OK.
Both of these organs were built by me and are used often, so I'm confident that it is not the ODF's at fault. Should you need further info please ask and I'll try to help.
As an aside, they also run fine in HW1-4 and have no multiple loops but longish tails 3-5seconds.
Thanks
Chris

[e9925248]

Could you please report:

* Your total RAM size
* OS (XP 64?)
* GO (32 or 64)?
* Sample size and Lossless compression compression setting in the GO setting dialog?
* Monitor with the Windows task manager the memory usage of GO (in the process list task)?

[Cybug]

OK:-
RAM 3Gb
OS XP64 SP1
GO v3.0.3.0 32bit - your last build as above
Lossless Compression set
Total Sample size 2.1Gb
Memory usage 1,082,436 Kbytes
=============================
Repeat above with Lossless Compression unchecked
Failed again but GO Ram usage was 1,732,724 Kbytes

Chris