e9925248
New member
I cannot feel any diference with 32bit GOv2 and 64bit GOv3 here. I needed the 64bit one for use with my other 64bit apps (which use Asio).
Also v3 occupied 158MB on my HDD......
GO and its audio code has been improved very much (eg. new setter/coupler panels, Presets, customizations are stored in the User folder, a working cache/compression, a new flexible MIDI handling, support for non 16bit/44100 formats, limited tuning captibilties[not yet included in my last built]).
But if you playback a HW1 compatible sampleset, the audio output should not differ very much to GO 0.2.
This build includes debug symbols - so it very large.
I have no "non saved" sets running here... I'll try decompress one from my archive and post back.
Just to be clear: saved sample set = "in my GO build you pressed saved button, while the sample set was loaded"
I couldn't see any error with saved sets.
24/48000 was a test experiment. There are not yet any 24/48 sets for GO (HW1 format)......
You can upgrade Nick Appletons StAugustines. Take the 24 bit 48000 HW packages and the GrandOrgue package. Replace either the WAVs in the GO package or copy the .organfile the HW packages and adapt the paths to the WAV files.