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.
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.