Member
- Posts: 390
- Joined: Tue Jun 19, 2007 6:23 pm
- Location: Calne, Wiltshire, UK
I have a number of pistons which I have mapped onto HW scoped pistons at a global level. I have them set up with some of the organs that I play frequently, which involves setting the scope to a group of stops (usually corresponding to a whole division) and then setting each piston individually. I haven't needed to do this for a while, but recently (since upgrading from HW 6 to 6.02) I have run into problems when trying to set up the pistons on an organ that I have previously been playing without them.
What happens is that if after activating the scope setting (either using a physical control or by clicking on the floating toolbar) I then press a scoped piston, every single stop of the organ pops out. The first time this happened it included a Cavaille-Coll Orlage and made a terrible racket before I could find the reset button. This seems to happen whether I press a physical piston corresponding to a HW scoped piston, or if I click on the HW piston on the floating toolbar. For organs where some of the pistons have previously been set up, I only get this strange behaviour when clicking on (or pressing) a previously unscoped HW piston.
At the same time the CPU meter shoots up to maximum for a few seconds and I hear a bit of crackling in addition to the tremulant wind noise and any special effect stops that have activated.
This makes it impossible to use any scoped pistons that I have not previously set up, as well as being a bit alarming if you aren't expecting it.
My computer is a fairly new Dell mini-tower workstation with a 10-core i9 and 128 GB RAM. I am using a MOTU MIDI Epress 128 MIDI interface and a MOTU ultralite Mk 4 audio interface. My keyboards are from Classic MIDI Works in Canada, but the behaviour seems to be independent of physical keyboards as I can reproduce it by clicking a toolbar.
Any ideas?
What happens is that if after activating the scope setting (either using a physical control or by clicking on the floating toolbar) I then press a scoped piston, every single stop of the organ pops out. The first time this happened it included a Cavaille-Coll Orlage and made a terrible racket before I could find the reset button. This seems to happen whether I press a physical piston corresponding to a HW scoped piston, or if I click on the HW piston on the floating toolbar. For organs where some of the pistons have previously been set up, I only get this strange behaviour when clicking on (or pressing) a previously unscoped HW piston.
At the same time the CPU meter shoots up to maximum for a few seconds and I hear a bit of crackling in addition to the tremulant wind noise and any special effect stops that have activated.
This makes it impossible to use any scoped pistons that I have not previously set up, as well as being a bit alarming if you aren't expecting it.
My computer is a fairly new Dell mini-tower workstation with a 10-core i9 and 128 GB RAM. I am using a MOTU MIDI Epress 128 MIDI interface and a MOTU ultralite Mk 4 audio interface. My keyboards are from Classic MIDI Works in Canada, but the behaviour seems to be independent of physical keyboards as I can reproduce it by clicking a toolbar.
Any ideas?