Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
[NO BUG] CV inputs overload?
#6
(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


Attached Files
.nrd   CHOKE.NRD (Size: 438,5 KB / Downloads: 0)
Reply


Messages In This Thread
[NO BUG] CV inputs overload? - by MidiSlave - 12-14-2023, 09:46 PM
RE: CV inputs overload? - by XORadmin - 12-14-2023, 09:56 PM
RE: CV inputs overload? - by MidiSlave - 12-15-2023, 02:19 AM
RE: CV inputs overload? - by XORadmin - 12-17-2023, 01:45 PM
RE: CV inputs overload? - by XORadmin - 12-19-2023, 09:10 AM
RE: CV inputs overload? - by MidiSlave - 12-26-2023, 10:37 PM
RE: CV inputs overload? - by XORadmin - 12-26-2023, 11:16 PM
RE: CV inputs overload? - by MidiSlave - 12-26-2023, 11:59 PM
RE: CV inputs overload? - by XORadmin - 12-27-2023, 02:58 PM

Forum Jump:


Users browsing this thread: 1 Guest(s)