Cybug
New member
The cache contains some checksum to detect incompatible caches - but this does not catch all situations.
I will try this out tomorrow.
Thanks
Chris
The cache contains some checksum to detect incompatible caches - but this does not catch all situations.
Hi
Deleted cache as requested.
1) Win7 x64 with 3.0.5 x64 No Cache compression. No out of date cache warnings at start of organ loading as expected.
Loaded organ (1.5gb) fairly quickly but then cpu went to 100% and system hung as last time. Terminated after 10minutes - reboot.
Same result with Compression set.
2) Win7 with 3.0.5 x32 No cache compression. No error message at start. After loading organ cpu went to 100% and system
hung as before. Terminated after 6 minutes - reboot.
Same result with compression set.
3) Tried build 956x64 without compression same as above.
4) Repeat above with small test organ (150mb) Able to play a few notes before the buffers filled even though cpu showed 99%.
GO crashed in module ntdll.dll after a few minutes.
5) Loaded organs in 24/3/ build and ran smoothly as before so we can assume that whatever the problem is it hopefully not my
system
Chris
I cannot add an additional device in this release.
This would be nice to be able to send each division to a separate stereo audio channel.
To avoid misunderstandings I just updated GrandOrgue trunk with the patches that seem to fix the recent problems and make GrandOrgue functional again.
The version of the trunk is now 966 and the installation files have been uploaded to https://sourceforge.net/projects/ourorgan/files/Development releases/
I also uploaded a version without sse3 for people with older computers.
They all seem to be operational but it would be greatly appreciated if you can test them and provide comments.
You might be surprised by the fact the size of the installer went down quite a bit but that is normal since the exe file have been cleaned.
Regarding the last version of JLD:
It should be possible to lower both concurrency settings to about the number of cores.
also lacks the reverb.
also lacks the reverb.
Could you report the achieved latencies of the last released version of JLD (including the intended latency setting and the samper per buffer setting of GO)?
Please don't use the numbers reported by GO - use something external instead.
The problem with the GO numbers is eg, that RtAudio backends simply return the result of an API call while PA based backends try to consider various effects.
In my option, these numbers don't allow an object comparision.
A comparsions between the ASIO backends (with and without PA in the name) would be interessting.