What can cause CV16 Out#16 to be "High"?

[mgd]

Hi Forum,

I'm experiencing a droning sound after I hit SHIFT+STOP twice. The culprit is CV16 Out#16 stilll being "high".
I'm out of ideas where to look for possibly causes.

What can create that behaviour?

I've configured all odd numbered outs -5 - +5V and use them for notes and all even numbered outs 0 - +10V used for gates. All gates are "low" except out#16.

Any hints welcome,
Michael

[XORadmin]

How do you generate a 'high'? A stop all sounds (SHIFT+STOP twice) doesn't touch voltages usually. It only stops modulators if they are active.
And depending on the add/pure settings it can get back to a voltage (if a modulator was on) which can still be seen as a 'high'.

[mgd]

For the time being all I do for gates on the CV16 is having ^11 and -16. That will change in due time but for now is enough for what I'm experimenting with. The usecase for the gates as is is opening/closing a VCA and thus effectively switch on/off the sound from the VCOs (I'll change that to ENVs soon enough, but for now...)

When I'm stopping by SHIFT+STOP twice all sound goes off (as expected) except for VCO from out#15 which is VCA controlled from out#16.

I'm pretty sure it has nothing to do with the note(s) on out#15 (the one controlled by gates out#16) because when I swap out#14 with out#16 VCO from out#15 goes silent while VCO from out#13 can be heard. Same with all other "gates" (tried them all to be sure).

I'm kind of convinced that I'm doing something stupid (because in 95% of such cases it is me), but I've run out of ideas where too look.

For the record:
All automate slots are empty and all envelopes are of type ONE SHOT and have NONE in source and destination.
Modulation is set to PURE on all 16 and Glide is off for all as well.
Envelopes and LFOs are all on their default values.
No FX on any track.

Kind regards,
Michael

[mgd]

I have gotten rid of this strange behaviour. Here is what I did:
The initial setup was done like this:
I had created a new project and assigned tracks 1, 2 and 3 in that order to NSA 1 (my CV16). Checking track setup showed
Track 1: EXT CV 1-6
Track 2: EXT CV 7-12
Track 3: EXT CV13-16 + LOC CV5 + LOC MOD5
without me doing anything special. However this was exactly how my previous project had been setup. That suited me as it was what I wanted anyway, so I did not touch any of these settings.

This is - I guess - the setting, that resulted in the behaviour as described above.

I then entered Track setup and changed
Track 2: EXT CV 7-10 + EXT CV 15-16
Track 3: EXT CV 13-14 + EXT CV 11-12 + LOC CV5 + LOC MOD5
i.e. I swapped EXT CV 11-12 for EXT CV 15-16 and vice versa.

Now CV16 out#16 behaved just normally, problem gone.

I changed the Track setup back to my initial setting and still everything works.

I'm guessing (w/o any knowledge of the underlying code and procedures involved) that it somehow is/was an initialization issue but of course I may be completely off.

Kind regards,
Michael