convert gate to trigger in core?

I think there is a V5 core macro called impulse that kinda does this but you would have set it up to work w/ audio or event clock signals

But a 1 followed by a 0 is the easy part of the problem you're describing, unfortunately there's no easy way to do this

That's because any audio signal above the threshold will continue to generate 1s as long as it remains above that level

So you would need some kind of hold time where a new trigger event cannot be received to get functionality you're describing

Adding some Hysterysis to the threshold detection could also help

https://community.native-instruments.com/discussion/comment/251737#Comment_251737

So a gate to trigger converter then?

That's for a trigger that's a single audio tick long

A basic audio to gate converter might be something like

If the trigger should be longer you would need a little more code.

Also, for some virtual analog type of thing, you might want to shape it… so a single sample into a (very) short decay, slew or filter to give it a more realistic vibe. Depends what its for (reasons for asking up front again!!)

Longer or shaped triggers can be useful in VA contexts like Blocks. They become more useful as exciters for pinging things. A 1 tick trigger works fine as a 'go' event in Reaktor code, but not so great e.g. as a driver for a filter based kick drum model

All comments

Its probably your understanding of the merge thats the issue. Hard to tell though, because you have given no actual example, and spent most of your reply explaining some implementation detail that doesn't work.

Post a pic of your code.

Explain exactly what you are trying to achieve. Not how your implementation was supposed to work.

Manipulating gates and triggers is fairly easy in core.

threshold trigger test.ens

use value: trigger envelope with amplitudes past a certain level

I know the merge only passes the bottom event, but not sure how else to bypass that

You still haven't explained clearly what you are trying to do.

One thing is for sure, you need to read the tool tip info on the z^-1 macro.

threshold-trigger_corrected.ens

this configuration seems to achieve what I was going for with an actual audio signal, the envelope triggers cleanly on positive threshold crossings without jumping back to 0 abruptly, so something like a drum hit can trigger another. for event/MIDI gates it works better without the duplicate filter, so multiple gates get folded down to a single voice without needing to get a note off first

https://community.native-instruments.com/discussion/comment/251643#Comment_251643

if you're referring to the bottom clock input, I figured that might be incorrect but it didn't work without a connection there either, neither did a latch(-1). I just had that wire hooked up there for simple demonstration purposes, though I know it's not an actual audio input

is there a way I could accomplish the behavior in the most recent .ens posted without having to use a full ADSR module? I really just want the 1 release stage

If you get lost in an unfamiliar city, and ask someone for directions, you should tell them where you want to go

That is your priority

The route you took when you got lost, and your mode of transport, those are secondary issues.

https://community.native-instruments.com/discussion/comment/251667#Comment_251667

to be fair, I think my phrasing in the OP was fairly detailed in describing to the particular behavior I was seeking to reproduce, and a Primary module that behaves the same way. I also mentioned the specific implementation I had tried unsuccessfully in my own attempts, which, after you requested that I share, you then rebuked with a vague implication that I hadn't consulted the official documentation, & ignoring my previous mention of why the method wasn't working.

I'm not entirely sure why posing a purely technical question would require full contextual knowledge of a totally pre-meditated creative endgoal in order for you to engage with it in good faith, but it doesn't seem like you put all that much effort into interpreting my question.

your posts come across a bit combative - not sure what exactly warranted that, but sorry if I did something to irritate you

thresh.ens

looks like it was that z-1 into the latch that was messing you up lol

One thing to note is whenever you are splitting an audio stream with a router like that you're typically going to merge the output directly, putting in a unit delay like that will only disrupt the preservatuon of the audio/clock events

https://community.native-instruments.com/discussion/comment/251676#Comment_251676

to be fair, I think my phrasing in the OP was fairly detailed in describing to the particular behavior I was seeking to reproduce, and a Primary module that behaves the same way.

I'm surprised you think that

Thread titled "convert gate to trigger in core"
Initial post was mostly about delaying events
"seems to achieve what I was going for" is an audio to gate converter

Three different things

Seemed reasonable to ask for clarification before continuing.

So, were you trying to convert audio to gates, or was it gates to triggers?

The order of operations as I conceptualize them in the patch posted there would be-

Signal enters Core Cell as either audio or events, but doesn't matter hugely in the context of the main premise of the thread, because in Reaktor they come out as events after being converted to gates. I was having trouble in trying to convert a gate to trigger by delaying a copy of the changing the value from 1 to 0, and merging it with the original signal so that the 'gate on' is immediately followed by a 'gate off' - this is my understanding of a trigger, though I'm the first to admit a flawed implementation and that my question could have been more clearly phrased.

I'm still not clear on the actual logic on how you might set up a gate on to instantly be followed by an 'off', hence the workaround with a gate feeding a multistage envelope when it would theoretically be simpler to trigger into a single stage

I think there is a V5 core macro called impulse that kinda does this but you would have set it up to work w/ audio or event clock signals

But a 1 followed by a 0 is the easy part of the problem you're describing, unfortunately there's no easy way to do this

That's because any audio signal above the threshold will continue to generate 1s as long as it remains above that level

So you would need some kind of hold time where a new trigger event cannot be received to get functionality you're describing

Adding some Hysterysis to the threshold detection could also help

Makes sense, should be easy enough to work around for now until I can think of a reason otherwise, thanks

Point taken, you cannot send an 'eventless' event through any combination of modules, this seems unintuitive on some level but is ultimately more flexible, so I will try and orient my thinking on it to be more solution-minded and less towards arbitrary 'workaround' constructions