How to extract the trigger from a poly stream?

[glitchcpt]

Hi guys,

Not sure If I put that correctly,
I'm basically trying to split the signal out of the "Freq" output of the MIDI to Poly module,
into 2 Streams, for Frequency/Trigger, and then combine them later in the chain,

I can't seem to figure this out,
any help would be greatly appreciated

[MyCo]

Can you be a little more specific on what you're trying to achieve?

[nix]

If I understand correctly,
you might find it better to use the trigger or gate out of the MIDIpoly for on/off,
and freq for pitch.
If you want to create a trigger from frequency you need to do a one sample delay and use a false comparator. It will compare the current and delayed to ascertain wether there is a change in the signal, thus specifying an event. I recommend not doing this really, ie. how do we know which one is on and which is off. I would quickly lose track of what is on and off for all the streams.

[glitchcpt]

Sorry for not being more specific,

Basically its working like this so far:

I have the MIDI to Poly module frequency output running through a series of modules, but by the time it reaches the oscillator, it is only receiving the frequency information, and not the event trigger,

I could use the trigger output from the MIDI to Poly module, but how would I blend the trigger and frequency back into a single poly stream?

Thanks!

[Nubeat7]

i'm not sure if some basics are clear here,

a stream is constantly changing value (mostly 44100 times per second) while for example the green stuff in FS is trigger based which means that a value change is triggered from some source (mostly from the gui)

so a trigger in a stream would be a pulse of one sample for example at note on or note off
an you also have the gate which reacts on note on / off

it is still unclear what you mean with the poly triggers?

for the osc input you don't need any triggers you just set the frequency... if the schematic is more complex (after you are tellíng that there are a couple of modules before, you also can post the schematic and explain the problem there so it would be easier to understand instead of speculating what you mean

[glitchcpt]

OK I have made an example, the first time i picked it up was when i played around with your cable patcher, Nubeat

PS I like it alot, just can't figure this part out

[Nubeat7]

seems to work fine here, the only thing i found is that the little ruby module in the sources and in the targets module gives an error when clicking inside, i wrote the content into the event methode and it seems to fix this little issue.. but the rest is working fine now...

i saw that the generic driver (never used this) is used - this isn't working here - but with the asio drivers it works well (also asio4all)

here is the little fix (while it did work also without this as long as you don't click inside this modules..)

[glitchcpt]

Thank you!

It seems to be working fine now

strange