Send and receive terminals for events

I am in the process of building a structure with various connections coming from a single module and i though i would use send and receive terminals (for the first time ever) to keep things tidy and allow me to connect ports simply and with a visual idea of what is connected to what during debugging.

the problem i have come across is that it seems that an event signal is converted to an audio signal as soon as it is sent across a send/receive connection. this means that i am running signals at an audio rate when they only need to be ran at an event rate, meaning over use of CPU and a connection problem when running it back to an event signal.

i have looked around and i cant find a way to stop the terminals acting like this.
i even did a test with a single event output connected to a send terminal, to a receive terminal, and tried to connect it to an event input, but reaktor wouldnt allow it.

any ideas?

thanks

 

if a receive terminal can possibly receive an audio signal, it will be audio rate itself.
you must have an audio rate send listed in the function tab of the receive properties. remove it from the list there and it should work.

frustrating, i know, that it can't be dynamic, but such is reaktor.

 

i see.
i cant seem to figure out how to remove sends from the list though. im sure its something simple im missing.
i just played around and the only way i can figure out how to do it is to connect all the event terminals before the audio terminals, which is not really ideal in large projects.
how can i remove it from the list?

thank you

 

if you unselect the 'automatically use new sends' option, and add the receive module first, subsequent send modules will not automatically be added.

strangely i can't figure out how to remove stuff from the list, maybe a bug?

 

if the sends are already in place, it looks like you can copy/paste a receive module from a project with no sends, and the 'automatically use new sends' deselected and they get added to the list, but not assigned a number and therefore not used.

super awkward.

hope that helps!

 

ah yes that works. thanks!
if you turn the "automatic use of new sends" off, then add all your sends, you can turn them on individually by typing in the number under the "use" column.
this is fine for me because i havent actually added them yet, i stopped once i realised there was a problem, and it is still quite early in the build.

i will head over to the feedback forum after this and mention it.

thanks for the help yet again salamanderanagram

 

i was typing out my thread in the suggestions forum, and i thought i would try one more thing before i posted it.
i selected the number under the "use" column, then just deleted the number and pressed enter, which removed it from the list completely
you can still see it in the list of course, but as long as there is no "use" number then it will not affect the connectivity.

it was really that simple all along.

thanks for the help

 

nice!
i tried typing in zero there for some reason - fail.

 

hahaha so did i, a couple of times in fact!

 

BUT be careful! If you copy a macro with send and receives inside your copied send-lists are not the same. It is a well known bug (means not well defined) and very frustrating.
Ciao herw

 

thanks.
i was going to use more send/receives in my current build to keep it tidy too, but decided against it to keep the send list as small as possible.
as it stands now the only send/receives are in the main instrument, not inside any macros, but i was thinking about using more. i would have been copying macros further down the line too
i will keep them to a minimum.
thanks for the heads up

 

i create all my sends first and put 'em in a big macro, that never gets edited.
then i simply wire anything that needs to be available as a modulator into one of the inputs to that macro.

 

thats a good idea if using them for modulation routing.
i was looking into using them just to keep things tidy (like core), but it doesnt seem to be worth the hassle for that.
if only we could bend wires!

 

there is a solution but it costs high cpu usage:
use shared audiotables. You can use the index to send and receive modulation sources.
ciao herw