How to trigger iterator to copy event table A->event table B ?

mr.datsun

I'm struggling to understand why a Button (which surely creates an event?) cannot trigger the iterator in my ensemble. And what should I be using if this is the wrong approach?

The background is that I want to copy whatever is in table A to table B. And initially drawing some data directly in table A for this test.

Please refer to my .ens

testcopy.ens

colB

This is one of those peculiar Reaktor Primary gotchas ;)

The second table in not active because its outputs are not being used.

If you wire something to an output, e.g. a numeric to the DX output, then it will work!.

The thing to watch uot for is that the little icon in the corner that shows poly vs mono, will be greyed out:

With a numeric (or some other active component) at an output, it will 'turn on':

And now the copy will work just fine!

Normally, in actual code, there will always be something at the output, so this problem isn't a problem. If not, you can use e.g. a numeric, but make it invisible, and it will still do the job.

Most modules have an 'Always Active' setting, but not this one it would seem!

colB

This is one of those peculiar Reaktor Primary gotchas ;)

The second table in not active because its outputs are not being used.

If you wire something to an output, e.g. a numeric to the DX output, then it will work!.

The thing to watch uot for is that the little icon in the corner that shows poly vs mono, will be greyed out:

With a numeric (or some other active component) at an output, it will 'turn on':

And now the copy will work just fine!

Normally, in actual code, there will always be something at the output, so this problem isn't a problem. If not, you can use e.g. a numeric, but make it invisible, and it will still do the job.

Most modules have an 'Always Active' setting, but not this one it would seem!

mr.datsun

colB. Thank-you. I'm kind of glad it was something I could not have easily predicted. I was beginning to think my fledging understanding of Reaktor had just gone back to zero.

Curious that the link from the Button shows the error, when the real problem is the other end of the structure.

colB

https://community.native-instruments.com/discussion/comment/71024#Comment_71024

Your code was just fine!

Curious that the link from the Button shows the error, when the real problem is the other end of the structure.

Not sure what you mean here?

mr.datsun

https://community.native-instruments.com/discussion/comment/71030#Comment_71030

Thanks. I'm Ok with logic but sometimes I'm not always sure what is going on inside the modules, and that takes some extra reading/thinking as I build a structure.

>Not sure what you mean here?

Well, it's nothing really – the problem is the configuration of the final Event Table object, but the existence of an error is flagged up on the link from the button in another (remote) part of the structure - which led me to think that the error was somewhere around the button itself.

But your point about the icon being greyed out is very useful and not one I was aware of before.

colB

https://community.native-instruments.com/discussion/comment/71050#Comment_71050

but the existence of an error is flagged up on the link from the button in another (remote) part of the structure

This is the bit I don't get. In what way is an error 'flagged'?

mr.datsun

https://community.native-instruments.com/discussion/comment/71171#Comment_71171

My mistake. It turns red whenever the button is pressed. (WIth or without the second table activated)

colB

https://community.native-instruments.com/discussion/comment/71173#Comment_71173

You mean the text for the button? if so, that is just highlighting the component that was most recently used so is 'selected'. Similarly in the structure, selected components are highlighted in blue.

For 'release' most builders switch off the button titles, and add separate text, or bring in bitmaps from some external graphics generation apps... similarly many folk create custom bitmaps for the buttons and the knobs. So you only see this 'feature' when throwing stuff together during the build process.

FWIW, in Reaktor there is very little in the way of built in debug help ;). So it's up to you to decide when something is an error.

All you really get is the option to see the current value on a wire as a tool tip (which can also be confusing for beginners, because sometimes it is 'not available', which is also _not_ an error. The other thing is that in core implicit feedback will show as orange wires... but again this is not really an error, more like a warning. You will sometimes see values as NaN or inf/-inf, that does indicate an error, but if that happens, you probably knew from the click/thump when the audio shut down ;)

So you really need to develop your own systems and workflow for debugging. Its not too hard, but can take a while to work out initially. Definitely ask on the forum if you have stuff you can't work out how to debug!

mr.datsun

>FWIW, in Reaktor there is very little in the way of built in debug help

yes. there are times when I'd just like to trace specific sequences of number-values to a console.

I've used some of those other devices your mention. Like the wire debugging and event order. It definitely helps.

>Definitely ask on the forum if you have stuff you can't work out how to debug!

Thank-you. I'll probably need to :)

With regards the button error I thought I was seeing - the button and the wire turn red in the structure when the button is clicked in the ensemble's UI pane. And that is after I have deselected everything in the structure. Please see attachment.

colB

https://community.native-instruments.com/discussion/comment/71186#Comment_71186

Selecting on the GUI also selects in the structure, and selecting in the structure also selects in the GUI. That is really useful, because sometimes you have multiple instances of the same module/macro/instrument, and you need to know which is which between the two panes.