Folks,
I am referencing the organ built for Greenwood UMC, here.
http://forum.hauptwerk.com/viewtopic.php?f=17&t=15009
I have, on multiple occasions now, had a very curious audio glitch that so far (knock on wood) has only ever happened on the Sonus Paradisi Caen set. Now, I do not, in any way, think this issue is due to any fault with the set. But there is something causing this that makes it unique to that set. (Or maybe it's wild coincidence.) However, there has to be some reason that this pesky dropout (or series thereof) hasn't appeared in ANY of my other samples (SP Casavant, Armley Schulze, Silbermann, Paramount 341, SP Reuter, Redlands Casavant....). I am using the wet subset of the Caen, which requires very little RAM (relatively speaking, compared to the others).
Basic computer specs:
Hauptwerk V4
Windows 10
64GB of RAM
MOTU 24ao Interfaces
All SSD
What happens is what I can only describe as the sound of a string of firecrackers going off. It happened once, at full tutti, across all 50ish channels.... and it absolutely scared the heck out of me. It sounded like machine gun fire, or exactly like someone threw one of those strings of firecrackers up into the speaker chambers.
When this happened a while back, I thought I had solved the problem. I went into the BIOS and forced the RAM speed, rather than relying on "Auto". This seemed to have cured the issue..... for a while. Now, it has done it again - albeit, nowhere near to the extreme that had happened in the past. This time around, it is only one or two quick drop outs (which manifest themselves as loud POPS) and then it's stable again.
The audio meter never goes into the red. And it can happen no matter how full or soft the registration.
I also noticed that one of the sample rates for one of the ranks (in the Load Organ Adjusting Rank Audio...., etc.) hadn't been set the same as the others - now they are. I don't have it in front of me, but I do believe they are all set to 20-bit (or 24-bit).
My hunch is that the issues is either RAM or clocking with/between the MOTU interfaces. However, again, I can't help but feel there is some reason why CAEN is behaving differently....
Any thoughts?
I am referencing the organ built for Greenwood UMC, here.
http://forum.hauptwerk.com/viewtopic.php?f=17&t=15009
I have, on multiple occasions now, had a very curious audio glitch that so far (knock on wood) has only ever happened on the Sonus Paradisi Caen set. Now, I do not, in any way, think this issue is due to any fault with the set. But there is something causing this that makes it unique to that set. (Or maybe it's wild coincidence.) However, there has to be some reason that this pesky dropout (or series thereof) hasn't appeared in ANY of my other samples (SP Casavant, Armley Schulze, Silbermann, Paramount 341, SP Reuter, Redlands Casavant....). I am using the wet subset of the Caen, which requires very little RAM (relatively speaking, compared to the others).
Basic computer specs:
Hauptwerk V4
Windows 10
64GB of RAM
MOTU 24ao Interfaces
All SSD
What happens is what I can only describe as the sound of a string of firecrackers going off. It happened once, at full tutti, across all 50ish channels.... and it absolutely scared the heck out of me. It sounded like machine gun fire, or exactly like someone threw one of those strings of firecrackers up into the speaker chambers.
When this happened a while back, I thought I had solved the problem. I went into the BIOS and forced the RAM speed, rather than relying on "Auto". This seemed to have cured the issue..... for a while. Now, it has done it again - albeit, nowhere near to the extreme that had happened in the past. This time around, it is only one or two quick drop outs (which manifest themselves as loud POPS) and then it's stable again.
The audio meter never goes into the red. And it can happen no matter how full or soft the registration.
I also noticed that one of the sample rates for one of the ranks (in the Load Organ Adjusting Rank Audio...., etc.) hadn't been set the same as the others - now they are. I don't have it in front of me, but I do believe they are all set to 20-bit (or 24-bit).
My hunch is that the issues is either RAM or clocking with/between the MOTU interfaces. However, again, I can't help but feel there is some reason why CAEN is behaving differently....
Any thoughts?
Drew A. Worthen
Master of Music in Composition - Butler University
http://www.drewworthen.com
Director of Music & Website Admin - Greenwood UMC
http://www.greenwoodumc.org
Design Engineer - American Sound and Electronics - Indy
https://americansound.cc/
Master of Music in Composition - Butler University
http://www.drewworthen.com
Director of Music & Website Admin - Greenwood UMC
http://www.greenwoodumc.org
Design Engineer - American Sound and Electronics - Indy
https://americansound.cc/