Anybody have a quick core workaround for converting a boolean output (from a Compare module) to a usable output? I need the 0/1 to be processed by a math module. I'm probably overlooking something, but it don't hurt to ask.
Greets,
Bolle
Compare, router, 2 latches and a merge.
Double-checked now I'm back at my pc, there is a library macro 'BoolCtl2L'
Yes, but i don't know what to do with the bottom (clock) input. It looks to me like it receives events there (from a button push or whatever) and only then is the converted boolean signal forwarded. I'll see what i can do with your first suggestion.
The clock input it to give you control over when to update the outputs. A BoolCtrl green triangle is not an event, so a change won't cause anything to happen so you need to drive it with a regular event:
I implemented your first suggestion and probably won't be testing it before my structure is finalised. But it looks solid and i'm pretty confident that it works. Many thanks!
The problem here is that the 1 at the input of the router only fires during initialisation.
Wait, what? And does that apply to all constants in core?
yep ( and extra yep for +7 characters)
But it only causes a problem with the router, surely?
It doesn't cause problems, it's just the way Reaktor Core works. Constants only generate an event at initialisation. So a latch driven by a constant will only fire during initialisation. Whatever it outputs at that time will not change during run time.
This may well be a very stupid question, but in this diagram do you mean i should try wiring the thing that goes into the bottom input of the Compare module to the two inputs of the Merge module as well?
Upper is event output lower is audio Out
This should Compare again 0.5 With two outs , upper event , lower audio
You've just rebuilt the 'BoolCtl2L', except yours is less general because you've incorporated the comparison inside the macro.
I don't like the audio output. Taking a logical process and resampling it at audio rate seems likely to be extremely wasteful in most situations I can think of. Is there some specific case where you need this at audio rate?
Anyway, what you have should work, if you want to compare the input event with 0.5 :-)
I inserted the audio out as an option , because why not , it could be useful
I did this in < 1 min , and yes the comp.sign should have been a variable located outside the macro
