Hi there,
I'm working with Faceware's Shepherd tool which can have Motive trigger its take start/stop through the XML data port (default port=1512). Things behave as expected using Motive v2.6, setting the take name and the start/stop is reflected in Shepherd. When running Motive v3 beta1 though Shepherd does not pick up on the take start/stop driven by Motive.
Has there been a change in the data streamed out from the XML data port in v3?
Cheers,
Lyle
A change in XML triggering port in v3 Beta?
-
- Posts: 3
- Joined: Thu Jan 21, 2021 12:27 pm
-
- NaturalPoint Employee
- Posts: 720
- Joined: Mon Jan 19, 2015 11:52 am
Re: A change in XML triggering port in v3 Beta?
Hello Lyle,
Thanks for reaching out to the community regarding the remote trigger XMLs.
I believe you may be comparing Motive 2.3 to Motive 3.0
Remote triggering has not been changed in Motive 3.0. The triggering port should still be the Command Port + 2. This defaults to 1512.
If you continue to struggle with this, please feel free to reach out to us directly and we can try to determine if there is an issue that needs to be addressed in the new release.
Cheers,
Steven
--
Steven Andrews
OptiTrack | Senior Customer Support Engineer
help.naturalpoint.com
wiki.optitrack.com
support@optitrack.com
Thanks for reaching out to the community regarding the remote trigger XMLs.
I believe you may be comparing Motive 2.3 to Motive 3.0
Remote triggering has not been changed in Motive 3.0. The triggering port should still be the Command Port + 2. This defaults to 1512.
If you continue to struggle with this, please feel free to reach out to us directly and we can try to determine if there is an issue that needs to be addressed in the new release.
Cheers,
Steven
--
Steven Andrews
OptiTrack | Senior Customer Support Engineer
help.naturalpoint.com
wiki.optitrack.com
support@optitrack.com
-
- Posts: 3
- Joined: Thu Jan 21, 2021 12:27 pm
Re: A change in XML triggering port in v3 Beta?
Thanks Steven, it was indeed v2.3 that it was working in. I've been in touch with your support team and with Faceware so things should hopefully be resolved in the near future.
Cheers,
Lyle
Cheers,
Lyle