OSC send not working from remote

Does there need to be some Internal Connection setup for OSC to send when being controlled remotely?
If I use the mouse on the knob, the OSC sends, but when I use my controller, it controls the knobs fine but the OSC does not send.
I only see it working on a couple knobs that have a To & From Internal connection between 2 macros, but those are exceptions.

I don't think this is basic connection issue since I can control knobs remotely, and I can send OSC back using the mouse on the knob, but no OSC is sending back when I use my controller. Could this be a bug?

 

Your remote is an OSC remote, right?
Then most likely you encountered the same issue that at least belongs to Buttons - "by design"...
OSC remote --> Button --> no OSC output!

If your remote is a MIDI Controller, then just check "remote thru" in the MIDI out property:

For MIDI input, this activates MIDI Thru AND OSC send ...while you miss the same Remote Thru property for OSC send...

All other combinations with MIDI, OSC, Mouse, IC Receive to MIDI, OSC seem to work fine. It is only OSC -> Button/knob -> OSC that fails.
When i checked that out, i forgot to take Automation data into account. So, maybe more issues when combining Automation.

This connection matrix under the hood for knobs and buttons needs a real overwhole. The issue you encountered in this area is not the only one.

 

The only workaround is to place an OSC send module to the button´s or knob´s output. Then, of course, you can´t make use of OSC learn. Instead you have to edit that OSC send from structure to set the adress.

Ah, i still checked automation one year ago:
Moving a Knob by Mouse: Automation Output is fine
Moving a Knob by MIDI: Automation Output is fine
Moving a Knob by OSC: Automation Output is fine
Moving a Knob by Snap: Automation Output is fine

!!! Moving a Knob by IC: NO Automation Output !!!

This indeed is intended behaviour by NI, but the builder should have the possibility to change it!

 

I'm using midi controllers that send 2 value encoder output and then encode them to OSC addresses and float value through javascript in Max.
There's no problem with the basic connection setup; it's specifically Reaktor not sending OSC output when I use my controller.
And this is odd because when I do use an actual midi control, the OSC does output as you said.
So it is by design for efficiency or prevent accidental feedback> If it's set up correctly that isn't an issue.
Either way, it's not the end of the world because I can still get pseudo-bi-directional feedback, it just seems inconsistent and un-intuitive.
Thanks

 

It is definetly inconsistent, imo.
What is your solution for OSC feedback?

 

Well, it's the manual input and OSC output from reaktor when a knob or button is used.
When my controller input is being converted in javascript I'm also controlling the led behavior and OSC output from reaktor is also going into the same js function to convert to LED feedback.
Ideally I preferred to get all my data from reaktors output to control the LED behavior but I guess that's not gonna happen.
I guess it's nitpicking anyway since there will always be the LED response between manual input on my controller or reaktor but again, inconsistent.

The more complicated part is doing led recall when I switch 'pages' on my controller. The same controls need to change LED values when I switch pages. Because there are too many controls in the reaktor patch, I have to use the same controls but change their output hence the need for 'pages'.
There's over 290 knobs, 72 toggles and 8 buttons. Using MIDI would also be a bottleneck and more of a hassle, so doing the logic in JS is saving me a lot of hassle, so thank god for OSC still.
So all of my realtime input values are being stored in a dictionary so recall isn't a problem. When I switch a 'page' I get all the info I need from the dictionary to change the LEDs. Of course this also helps when reloading my session.

Does that make sense?
Oh, the patch I'm talking about is Niji Tracks in the User Library. I'm excited to be able to use it like it's hardware once I'm finished programming the controls for it.

 

What would be ideal is if the OSC feedback is the same address as the input. This will save from the tedious task of either changing each controls address in reaktor or parsing it in JS.

 

I think your work around makes sense. Especially if your controller does not update itself from it´s own memory when changing pages - at least this is how i understood your description.

When using hooked OSC Send Modules instead of the panel element´s own OSC send, you will have to edit each OSC Send one time only. You can choose the same adress, then. Or isn´t it? This implies a static routing.

 

epsilonComa, what remote are you using to send OSC? Quietschboy, I'm new to OSC--maybe you could provide some guidance on my question here: https://www.native-instruments.com/forum/threads/open-sound-control-cloudlab.362383/