Maya Timeline vs dateTime Node: Which Approach Is Better for Time Zone‑Aware Animation?

Maya’s animation timeline operates on a global time unit (frames, seconds, etc.) and does not store any time‑zone context. When a script parses an ISO‑8601 string with the dateTime command, the offset is silently dropped unless the developer applies a manual adjustment. The time node’s timeOffset attribute can shift curves, but it works purely in frame values, making it fragile when the project’s frame rate changes.

Given these constraints, the developer must choose between two documented paths:

• Parse the timestamp with dateTime and manually apply the offset to the resulting frame number.
• Use the timeOffset attribute to shift an animation curve by the equivalent number of seconds, hoping the frame‑rate remains constant.

Which method provides the most reliable conversion from a real‑world UTC timestamp to a Maya frame while respecting local time zones? What are the documented limitations of each approach? Is there a recommended practice for synchronizing external time‑stamped data with Maya’s internal timeline?