NOOB internal connections questions

When I make an internal connection from a button(1=on 0=off) to a slider (0-1) the slider jumps to 0.5. why is that?

I need to make a xy jump to the left upper corner for example by the press of one button(trigger) via an internal connection. how is it done? How do I send 2 values sim. with the press of one button? I guess I can use 2 relays but what do I connect them to in order to make the intenal connection?

Why can i not make an internal connection from a recieve to a knob/xy?

 

the trick with internal connections is usually the min/max range values - its easiest when the ranges of the sender and reciever are the same.

 

A list with 3 entries -all 3 set to 0(!) and then connected to the xy will change the cursor to 3 positions: x: right, middle, left or y: top, mid, bottom. That would work if I could choose all 3 entries via internal connection but I guess I can't?

I've tried all kinds of things. It's not possible to do this is it?

 

Hej
one IC send for the Y value, one for the X value. I use "value" modules with constants attached and then transmit the Trig signal from the button, oldskool but it works.

 

That's easy to understand:
Button 0 = Fader 0..0.499999...
Button 1 = Fader 0.5 .....1

An interesting experiment is to change the internal connection from Fader to Button!

It's hard to understand your description; perhaps you can create a simple example which shows what you want to have (even not working).

just put an send behind the receive and connect internal to knob.

see attachment. Or you set the Button ON=0 (properties of button). But you see only a pixel (or cross) in the left upper corner. The cursor doesn't jump.
ciao herw

 

Ahh now i understand - but that could been made easier. You need to use only one IC-send. You can connect an IC-send to more than one receive, knob etc. (see MODULAR MINI 1 or 2 (Reaktor 5 only)).
ciao herw

 

That's exactly what it does! Tak for det!

I did try IC send 1 time but I must have missed sometheing. This will surely come in handy. I can then move the *cursor* around in all 4 corners.

 

Yes, but running both x and y sends using the same value will only give diagonal movement in the xy field.

 

kein problem. Feel free to email me at a[at]thecovertoperators[dot]com if you need someone to look your ensemble over or something. Frankly it would be nice for me to socialize a bit with other reaktor builders in DK.

Andy

 

Hi

Could someone please have a look at this xy trigger structure and give me some advice? 4 trig buttons for sending the cursor to each corner send values to the xy via the 2 sends. When released they send out 0 which goes down to the merge and send the 0.5 value to the xy which brings the cursor back to the middle. This works fine as long as each button is pressed and released one at a time. But when pressing button 1 -held down and then pressing button 2 -both held down then releasing button 1 the cursor will ofcourse jump to the middle again because 0 is send by the buttons release. I want the cursor to stay in the right upper corner(but 2) even if but 1 is released. Can someone give me a clue about what modules or processing I can use to make this work? Order, logic, router?

 

but that was his question pressing one button. Perhaps i misunderstood: sending two different values!
ciao herw

 

please upload a very small ensemble (zip-file) with your problem here. It is easier to answer.
ciao herw

 

i'll just try one thing first.

How do i make only the 2nd, 3rd, 4th event come through in general? Like a trigger sending out 1 two times and only the 2nd time it is passed through?

 

compare and accumulator modules may help. event first goes to the accumulator, then router. the compare opens the router. so, the first event is blocked, since the accumulator is outputting a 1,a nd the compare is checking if the event = 2 (or > 2, or >= 2, or whatever). when it hits 2, the compare sends a 1 to the router, which lets the event pass.

the trcik here is to MAKE SURE that the accumulator gets the event before the router. otherwise it wont work, itll be behind an event. also, use the event proc router. the signal proc router (relay) sends events even when you dont want it to sometimes, such as a 0 event when the pos is changed and there is no selected input. this wont always happen, but it can, and for blocking purposes, using the event processing M-> router, or regular router is always best, along with proper event ordering.

also, to get a >= out of the compare, use 2 compare/equal modules, with an OR module connected to the > output of one and the = of the other. if it is just opening a router, that is fine. if you are using the events for something more tricky, like triggering something when it hits 1, then a seperator or stepfilter may be needed.

also, the accumulator shouldnt be used if the events are of an arbitrary value, since it adds the inputs. you may want a counter instead, which always increments or decrememnts by 1, depending on the input used. if you are interested in a counter that saves it's state on restes/snapshot changes, just tell me, and ill post.

 

That was plenty of useful info for now. I have something to work with and study.

 

BLOCKING ENVENTS question

AAArgh! I have tried for too long now. I want to give up/let go and ask you again: How do I reset the accumulator without causing an event loop? I am using the Event watcher but I just can't figure it out.

You're right, the Event watcher is a great tool and this event ordering is quite difficult.

 

please upload an ensemble version of that picture you did and we can work from there.

 

an efvent loop is uaually needed. dont fear loops, just learn to control them. what i do, is disable eventloops on the instrument level (but i keep the "globally disable event loops" OFF!). then, i enable loops in just the macros that need them. the triack with eventloops is making sure something stops them. usually, seperators are the best, since in an accumulator loop, there is a count going on, and eventually the loop output value will be greater than the seperator threshold, and the loop will stop.

heres a snapsaving counter i have made, just to show what i mean. it uses an event loop, but is stable. ask any questions please and id be glad to answer.

 

hi Machinate and herw. The problem I addressed in post #10 I have solved so no need to upload an ens. Now I'm just learning about blocking and event order.

 

This structure is fine then, right? It works and stops the 1st event of 0(button set to trig 0). As soon as A is no longer > than B th compare sends out a 0 through the seperator to the set of the accum. The accum sends out 0 which makes the compare change its upper output to 1. Or is there a better way of doing it?