(12-14-2023, 09:46 PM)MidiSlave Wrote: 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.

(12-14-2023, 09:56 PM)XORadmin Wrote:

(12-14-2023, 09:46 PM)MidiSlave Wrote: 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?

(12-15-2023, 02:19 AM)MidiSlave Wrote:

(12-14-2023, 09:56 PM)XORadmin Wrote:

(12-14-2023, 09:46 PM)MidiSlave Wrote: 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!

(12-19-2023, 09:10 AM)XORadmin Wrote: I had your project now running in 3 sessions. 2,5 hours, 6 hours and 10+ hours and the triggers keep running....

Can you tell me if it also happen when the sequencer is running please?

(12-26-2023, 10:37 PM)MidiSlave Wrote:

(12-19-2023, 09:10 AM)XORadmin Wrote: I had your project now running in 3 sessions. 2,5 hours, 6 hours and 10+ hours and the triggers keep running....

Can you tell me if it also happen when the sequencer is running please?

Hi Thomas,

Thanks for looking into this. I will try re-calibrating the cv inputs.

Here's another example. 

I was halfway setting up this project/mapping. T1-3 of trigger16 going into CV inputs 1-3 (and then being mapped to trigger16 outs 9-11) so that I can apply calculations to achieve some kind of choke functionality to trigger a softer snare when ever trigs 1-3 (cv inputs 1-3) are not happening. after about an hour or so of messing around I start getting random values on the cv inputs when the sequencer is not running, causing outputs 9-11 to trigger erratically, soon after the trigs from the cv inputs are no longer passed to outputs 9-11.

Trigger 16 V1.0

(12-26-2023, 11:16 PM)XORadmin Wrote:

(12-26-2023, 10:37 PM)MidiSlave Wrote:

(12-19-2023, 09:10 AM)XORadmin Wrote: I had your project now running in 3 sessions. 2,5 hours, 6 hours and 10+ hours and the triggers keep running....

Can you tell me if it also happen when the sequencer is running please?

Hi Thomas,

Thanks for looking into this. I will try re-calibrating the cv inputs.

Here's another example. 

I was halfway setting up this project/mapping. T1-3 of trigger16 going into CV inputs 1-3 (and then being mapped to trigger16 outs 9-11) so that I can apply calculations to achieve some kind of choke functionality to trigger a softer snare when ever trigs 1-3 (cv inputs 1-3) are not happening. after about an hour or so of messing around I start getting random values on the cv inputs when the sequencer is not running, causing outputs 9-11 to trigger erratically, soon after the trigs from the cv inputs are no longer passed to outputs 9-11.

Trigger 16 V1.0

Do you know which values the mapping row shows when it acts erratically/randomly (like going from 0 to something)?

(12-26-2023, 11:59 PM)MidiSlave Wrote:

(12-26-2023, 11:16 PM)XORadmin Wrote:

(12-26-2023, 10:37 PM)MidiSlave Wrote:

(12-19-2023, 09:10 AM)XORadmin Wrote: I had your project now running in 3 sessions. 2,5 hours, 6 hours and 10+ hours and the triggers keep running....

Can you tell me if it also happen when the sequencer is running please?

Hi Thomas,

Thanks for looking into this. I will try re-calibrating the cv inputs.

Here's another example. 

I was halfway setting up this project/mapping. T1-3 of trigger16 going into CV inputs 1-3 (and then being mapped to trigger16 outs 9-11) so that I can apply calculations to achieve some kind of choke functionality to trigger a softer snare when ever trigs 1-3 (cv inputs 1-3) are not happening. after about an hour or so of messing around I start getting random values on the cv inputs when the sequencer is not running, causing outputs 9-11 to trigger erratically, soon after the trigs from the cv inputs are no longer passed to outputs 9-11.

Trigger 16 V1.0

Do you know which values the mapping row shows when it acts erratically/randomly (like going from 0 to something)?

in this demonstration i'm sending trigs from t16 1-3 to cv inputs. mapping the cv inputs to other NSA trig outputs (no longer being passed). unplugging the cv inputs to show their values in the mapping page. whether or not anything is plugged into cv input, Boolean value is always 1 it seems.

link for HQ video: 

https://drive.google.com/drive/folders/10IYEC9lLeEKwTbSfIM5ahNYOsn7_pq5j?usp=sharing