[NO BUG] CV inputs overload?

[XORadmin]

I've run into this issue a few times where I'm sending triggers into the CV inputs to step-trigger a table or mult trigs to several trig outputs using the automators (or now using the new and excellent mapping screen!) but i've found that after a little while it stops working.

example: I was preparing a live-set for a gig this week with 4 trigs from trigger 16 track (trigs 1-4) going into the cv inputs and sending two duplicates of each trig out T16 trigs 9-16  So that i could trigger O_C voices and also Percall. 

Everything was working fine for sometime until I stop to go get a drink and from the kitchen I hear a burst of kick drums (sequencer is stopped at this point) in the other room.

I don't know if this is a bug or miss-use or hardware problem.. CV inputs seem to come back online with a new project. But I tend to just move on with other ideas and assume that i've done something bad. But this has a happened a few times now. Sorry I didn't report this earlier.

Can you send me the project for this please? And I assume it is V2.0A?

Yep on latest firmware although i've encountered this on previous versions as well.

I've recreated the scenario and uploaded the project.

It works fine until after some time (a few hours) the cv input stops receiving the triggers. 

On another note, not sure if a bug or limitation, that only one table is able be triggered by a CV input at a time. Trying to step-trigger other tables running on other tracks simultaneously by the same cv input does not work. (see tables on tracks 1-4 in the project provided).

Thanks Thomas!

OK, got your project running now. Does it stop also when the sequencer is running? I don't want to wait until the burst is coming up so I prefer to just start it and check the trigger LED from time to time to see if it stops at some point.

Also for the table CV-IN check. Indeed, I do only a check for one CV input on the input basis. I can change that into a 'per track basis' of course.
You could instead also do the same thing through the mappings though as a workaround for now.