I've now installed the full sample set (with all four sample positions).
The first time I tried to load all the samples in 20 bit resolution this would not fit into my 64GB Windows 10 system.
I then tried loading all the samples again at 20 bit resolution but omitted the RP Tremulant samples and all and the Rear sampled tremulants. [There are two tremulant samples for the RP for each of the four sample positions; one operated by the RP tremulant stop and one by the organ tremulant stop. I omitted the ones for the RP Tremulant stop.] This left 0.9GB of RAM available according to HW's RAM mini control panel and the cache file was saved.
It takes a long time to load the organ when adjusting the ranks to load etc. (probably approaching an hour each time).
I set up the audio output using my "usual" surround sample set preset (offsetting the the starting note for the allocation algorithm for two of the three "positions" which I allocated to the main speakers).
When I played the instrument I was very disappointed with the sound - it was distorted and not at all pleasing.
I was unable to spend time looking into this yesterday evening and came back to it this morning.
I restarted Hauptwerk and the Groningen set loaded this time reporting 1.1 GB of RAM available (RAM meter still in the "yellow" section of the gauge). I was overjoyed when I played the instrument - it sounded wonderful! I had not made any changes to its settings and can only presume that some artifacts from the cache generation had cause the initial sound to be so poor. It may also be that having so little available RAM 0.9GB after generating the cache was the cause of the problem.
I increased the polyphony to the recommend 8000 and the RAM available reduced to 1.0GB. It still sounded magnificent, wonderful etc.
I loaded another organ in its place, played for a short while, then reload the Groningen sample set. The polyphony is still at 8000 and there is now 1.1 GB of RAM available (still in the yellow zone). The sound is still magnificent, wonderful, etc.
Other than saying that this is really a great sample set .....
I note that when you don't load some of the original samples for the tremulant (but do load others), using Original tremulant, no sound is played for those ranks/sample position that have been omitted when the tremulant is drawn - so I have no sound from rear ranks when I drawn the organ tremulant. When I draw the RP tremulant, the RP ranks don't sound. It would be nice if the sample set would switch to the artificial tremulant when it finds it does not have the samples for a particular tremulant rank loaded (but I suspect that is very difficult). I think I am happier with this compromise than using only artificial tremulants (though I could control their speed).
What do other users of this sample set do to fit into the "monster" into their available RAM?
I wonder why the sound was poor the first time the sample set was loaded when generating the cache? Is it because there is too little RAM being left available for Hauptwerk's audio engine?
All input (on topic) most welcome!
Iain
The first time I tried to load all the samples in 20 bit resolution this would not fit into my 64GB Windows 10 system.
I then tried loading all the samples again at 20 bit resolution but omitted the RP Tremulant samples and all and the Rear sampled tremulants. [There are two tremulant samples for the RP for each of the four sample positions; one operated by the RP tremulant stop and one by the organ tremulant stop. I omitted the ones for the RP Tremulant stop.] This left 0.9GB of RAM available according to HW's RAM mini control panel and the cache file was saved.
It takes a long time to load the organ when adjusting the ranks to load etc. (probably approaching an hour each time).
I set up the audio output using my "usual" surround sample set preset (offsetting the the starting note for the allocation algorithm for two of the three "positions" which I allocated to the main speakers).
When I played the instrument I was very disappointed with the sound - it was distorted and not at all pleasing.
I was unable to spend time looking into this yesterday evening and came back to it this morning.
I restarted Hauptwerk and the Groningen set loaded this time reporting 1.1 GB of RAM available (RAM meter still in the "yellow" section of the gauge). I was overjoyed when I played the instrument - it sounded wonderful! I had not made any changes to its settings and can only presume that some artifacts from the cache generation had cause the initial sound to be so poor. It may also be that having so little available RAM 0.9GB after generating the cache was the cause of the problem.
I increased the polyphony to the recommend 8000 and the RAM available reduced to 1.0GB. It still sounded magnificent, wonderful etc.
I loaded another organ in its place, played for a short while, then reload the Groningen sample set. The polyphony is still at 8000 and there is now 1.1 GB of RAM available (still in the yellow zone). The sound is still magnificent, wonderful, etc.
Other than saying that this is really a great sample set .....
I note that when you don't load some of the original samples for the tremulant (but do load others), using Original tremulant, no sound is played for those ranks/sample position that have been omitted when the tremulant is drawn - so I have no sound from rear ranks when I drawn the organ tremulant. When I draw the RP tremulant, the RP ranks don't sound. It would be nice if the sample set would switch to the artificial tremulant when it finds it does not have the samples for a particular tremulant rank loaded (but I suspect that is very difficult). I think I am happier with this compromise than using only artificial tremulants (though I could control their speed).
What do other users of this sample set do to fit into the "monster" into their available RAM?
I wonder why the sound was poor the first time the sample set was loaded when generating the cache? Is it because there is too little RAM being left available for Hauptwerk's audio engine?
All input (on topic) most welcome!
Iain