I can't get BogAudio Switches to work polyphonically?

I am absolutely dependent on BogAudio’s dual and sequential switches. The sequential switches are addressable; the dual switches take a gate and have a latched and unlatched more. Neither can be said for VCV Rack’s native 4:1 or 1:4 switch.

But am I asking too much here, or misunderstanding polyphony?

With 8 channels, the switch is getting a a 5 volt high gate on Channel 2. Ergo, it should pass through a non-zero value from its ‘High’ input on Channel 2 of its output, right?

I’d ask the author, but I wrote him once asking if I could donate to his cause, and he didn’t write back, so I’m not sure a question without money involved will be more interesting to him. Thanks for your help.

in your video there is nothing connected to the LOW socket (that is the one which is selected), so it looks ok to me that the output is 0 0 0 0 0 0 0 0.

have you taken a look at the manual?

Yes, the LEDs indicate all channels are low, but that is the point. The input 2nd channel is high, so the High LED should be dim green, and the output 2nd channel should be high. That is what I get on my machine. In other words, on my machine I get what Andy is expecting.

@andy.moffitt - yes this looks like a bug. What rack version are you running? and what platform? It works as expected on my Windows 10 machine running Rack 2.5.2.

I have a vague memory from nearly two years ago (maybe a false memory) of a switch that did not seem to function unless both high and low inputs were patched. Just for yucks try patching something into the low input and see what you get. It shouldn’t make a difference, but…

Either way, you might want to contact Bogaudio, probably via an issue on GitHub

1 Like

I’m on Win 10 + Rack 2.5.2 too, and I tried with 2 polyphonic cables as well…the switch works as I was expecting it to work.
Gate “High” = passes “High” signal.

Probably I understand what you are supposing the module to be doing, but sincerely I don’t understand why it should…The manual is very simple, but maybe it’s a language barrier.

But the zeros should only pass through in channels where the gate is LOW, which is all channels BUT 1.

Did your polyphonic cable going into the Gate input contain both High and Low signals among its channels, for example: (0 volts, 0, 5, 0, 5, 5 …)

I think you use the module for something that is mysterious to me or in a much complicated circumstance. I’m sorry I can’t help

a polyphonic cable brings voltage, and I don’t think there’s a concept of “gate” inside a cable.
a gate usually is 5V but it’s not a rule.
I think I understand what you expect the module to do, but I don’t know why you expect the module to do it, since I don’t get it from the manual.

again, sorry I can’t help

A gate signal is a (usually) 5 volt steady/static/flat signal held high for an indefinite time. A cable, polyphonic or not, can carry a gate signal just as it can carry a trigger signal, or an envelope, or an LFO. All those terms just describe the typical shape and use of the voltage traveling through the cable.

Anyway, someone on Reddit solved the issue. It appears to be a bug in the module

Actually the manual does explain how you can effectively get multiple switches via polyphonic input at the gate port - each channel gets its own independent switch. Those aren’t the words in the manual, but that is what it means.

Someone on Reddit noticed that in polyphonic mode, the switch won’t respond to a HIGH gate input that exists when the patch is loaded. Similarly, it did not respond to a HIGH gate that existed in the polyphonic cable the instant I first plugged it in. When I toggled the only HIGH gate to 0 and back to HIGH the switch finally recognized it! So it seems to require a change to a HIGH rather than an initially HIGH state.

1 Like

Oh man, that is ugly - especially failure to go high when a cable is first patched if it starts out high. I just confirmed the behavior on my machine.

Now I am willing to bet my vague memory of weird behavior two years ago was related to this bug, but I misdiagnosed what was happening at the time.

Good to have an understanding now. Thanks

Did you report this bug on the Bogaudio GitHub issues?