Forum

Using offsets in the console is a useful process when you have based your offline programming in Capture and then when you end up in the venue with the real fixtures they need an offset in order to match what you were seeing in Capture. Now, after you have applied an offset and you connect Capture on the side it will not be using these offsets and this is expected. 

The source of the problem is that the Capture libraries had the pan/tilt information wrong in the first place. If it was right you would never need to apply an offset. So the right thing to do is follow the Pan & Tilt Calibration Guide and send the results to library@ 

You can do this for any fixture you have come across that required offsets, and you will be receiving the library update in a day or two.

Ok, thank you.  All of these fixtures have their 50% pan position 90 degrees off from the front of the fixture and I am using the closest fixtures in the library for channel compatibility.  When I am in front of these again I will get together as much information as I can and send to have new fixture defs made.

If we are talking about Uknown fixtures and you are using any personality to get as close then chances are that you need to be lucky. If we were talking about branded fixtures then we could fix them right away once and for all.

I guess the thing I find odd is that with the offsets on and the placement I have the fixtures in Capture, my regular pan/tilt moves reflect fine, so the DMX that is being sent into Capture models what I see in real life.  Granted I do not know the internals of how Capture works, but I would think doing the focusing within Capture it has to know that given DMX inputs x/y the beam is pointing position x/y/z, now a focus click has happened at x+/y+/z+ the software would have to calulate the deltas of how to get to the new position from it's current input of x/y and apply them.  What I am trying to say is I guess I don't understand how the offsets make it behave incorrectly in Capture.  Unless, that is, Capture is ignoring any DMX inputs when going from point A to point B in 3d space and is using strictly internal information.

Since you are applying the offsets in another software, in that case ONYX, I would suggest that you take up this discussion with them. Capture listens to the same DMX the fixtures listen to, and responds accordingly. So if the console is applying an offset when sending out DMX is one thing, and if it applies an offset when it listens to DMX feedback from Capture is another. And this is a topic I encourage you to discuss with the ONYX team who are always very supportive. In the end please leave the conclusion in our forum too for future reference by other ONYX users.

This is a bug with latest Onyx 4.9.1249 build, which will be fixed on next build...

Regards,
Ofer

Thanks for noticing and posting Ofer! Good to know.