Quote from: tomatomic on April 24, 2007, 11:03:14 PM
i abandoned the chan file, since it seems it expects far more than i was placing in it.
The files you emailed me had the correct number of fields in them. The problems were the line ending, and the order/signage of the fields, we can figure those out.
An excerpt from some comments I added to my .chan reader in TG2:
Reads a Maya .mov file, Houdini chan file or Nuke chan file.
If file has extension ".chan" then:
{
It is assumed to be a Houdini chan file (7 channels) or Nuke chan file (8 channels)
Lines with 7 columns are assumed to be from a Houdini chan file without a frame number.
Lines with 8 columns are assumed to be from a Nuke chan file with the first value being the frame number
The last column (7th or 8th) is interpreted as vertical FOV
The last 7 columns are interpreted as camera coordinates in Houdini coordinate space
}
else:
{
It is assumed to be a Maya .mov file (which is identical to a Houdini .chan file if numchannels == 7)
The 7th column is interpreted as vertical FOV if it exists
The 8th column is not used
The last 7 columns are interpreted as camera coordinates in Houdini coordinate space
}
As for what I mean by "Houdini coordinate space", the 7 fields following the frame number are:
X (as TG2)
Y (up, as TG2)
Z (out of screen, negative to TG2)
Rotate X (pitch upwards, as TG2)
Rotate Y (anti-clockwise* heading, negative to TG2)
Rotate Z (bank left, negative to TG2)
Vertical Field of View
(*) I only call it anti-clockwise as viewed as a heading on a map, but it's actually clockwise as viewed along the Y axis in its positive direction.
Matt