mdyde wrote:Are you sure you were loading the sample from the sample set cache? The first time that you load a sample set, or if you load it via the 'Organ | Load organ, adjusting rank audio output routing', or via the Design tools menu, Hauptwerk will load from the original raw samples and regenerate the sample set cache, which will be very slow. However, each time you load it subsequently via the normal 'Organ | Load organ' menu option (as opposed to 'Organ | Load organ, adjusting rank audio output routing') it should load from the sample set cache using Hauptwerk's high-speed multi-core optimised loading mechanism.
Presumably you haven't disabled the high-speed loading mechanism on the 'General settings | General options' screen?
I don't know off-hand how long the Zwolle should take to load, but I would have thought it would be *much* less than four minutes when loading normally from sample set cache.
Ah, yes, you are quite correct Martin. I have not used Huaptwerk in a long time and completely forgot about that. I decided to try a benchmark of Hauptwerk when I decided to upgrade to a SSD.
System 1 configuration:
Asus P5K Deluxe
Intel Q6600 @ 3.1 Ghz
Patriot 8GB DDR2-800
Crucial C300 256GB SSD
Windows 7 Ultimate 64-bit
Hauptwerk 3.30
Loading the Zwolle organ took 36 seconds. When I overclocked the CPU to 3.61 Ghz, loading the organ took only 32 seconds!
System 2 configuration:
Asus P6X58D-E
Intel i7 930 @ 3.0 Ghz
Corsair Dominator 12GB DDR3-1600
2 x Western Digital 750AAKS 750GB 7200rpm in RAID-0
Windows 7 Ultimate 64-bit
Hauptwerk 3.30
Loading the Zwolle took 35 seconds.
Therefore, I can confirm Timo's results that using an SSD yielded little to no improvement. Also, Martin you are also correct in suspecting the CPU speed in being the bottleneck when not limited by disk I/O.
Thanks.