OSC Control

Hi There, I am reading conflicting things on Aximmetry forum and knowledge base about OSC. I see instructions of how to assign OSC control to individual settings on this page https://aximmetry.com/wiki/index.php?title=Using_the_OSC_protocol

but then I read in the forum that OSC is not supported as yet?

Can you confrim if this is working or not as I can add OSC to controls as in the process on the page above and it registers the OSC command to the button but then the OSC command when triggered doesn't appear to actually trigger the device it is attached to!??

Any help appreciated,

Cheers, Christian

clewispure

I seem to be able to control media sotpping and restarting fine but recalling camera move presets don't appear to work

jackiejohn

Choosing Camera Paths worked for me with TouchOSC from iPad/iPhone, but not from Bitfocus Companion.
Couldn't find out why.

Registering the OSC Commands works from both.

clewispure

Ah ok, yes I am trying to setup via Companion! I will explore TouchOSC Cheers

jackiejohn

hmm, would be nice to know why registering works with companion, but using the buttons doesnt.

And wether this Problem is on Aximmetrys or Companions side.

clewispure

I found that re-opening the Aximmetry file Companion would trigger each camera path once but then not again...

Very odd!

Katleen

Hi,

I had the same issue in Companion. But if you give a release value other than the one to trigger it will trigger the buttons.

So to trigger cam 1 I have on keydown: osc: Send integer; OSC Path /cam1; Value: 1
on Key up; osc: Send integer; OSC Path /cam1; Value: 0

jackiejohn

Ah! Thanks for the Info!

Works for me.

markusnygard_yle

more info on Companion
if you set delay to 9ms or higher you can have both value 1 & 2 on push down. 8ms or less doesnt work. Dont know why but this is how it is on my test-machine.

Eifert@Aximmetry

Hi all,

To add to what Markus is saying.

If you write your own controller software, in order to operate a button you have to send a value 1 then after a short while a value 0. It corresponds to the concept of controller button push = 1, release = 0.
This is what Markus did in Bitfocus Companion at button press down.

However! In many cases, a 9ms delay won't be enough. Aximmetry has to have a frame difference between receiving the value 1 and value 0. So set it to more like 50ms delay.

Or set the delay to an even higher value if you set the rendering frame rate lower than 30 in Aximmetry preferences:

Warmest regards,

OSC Control

Cookie consent