Found it - here's what Leonard posted a while back:
Okay, it seems it is available as xml data. This should be really easy to
parse and getting the bezier curves to be accurate won't be too difficult
either.
Here is the email from Kessler Crane's lead software engineer Bruce Werf:
*
Hi Leonard,
Right now, the kOS for Windows application stores moves as Bezier curve
segments in an XML file located on your PC here:
c:\Users\<username>\AppData\Roaming\Kessler1366/app.kslx
This same file format is used when you select File->Save from the main menu.
You will want to follow the file down the path <Kessler> -> <Axes> ->
<Axis> -> <KeyFrames> -> <KeyFrame>
There you will find a plethora of information about each key frame with
both absolute and normalized (0.0 -> 1.0) values.
For example:
<P0 Time="0.000" Position="0.471"/>
<P1 Time="0.151" Position="0.471"/>
<P2 Time="0.849" Position="1.000"/>
This describes the location of the key frame in time and space relative to
the length of the run and the number of motor encoder points. P0 is the
location of the key frame itself, and P1 and P2 are the Bezier control
points between that key frame and the next.
We plan to create a leaner XML export at some point soon, and we are also
interested in exporting this information in other industry-standard formats.
Please let us know what would be useful to you in this regard.
-
Bruce Vander Werf
Kessler Crane, Inc.
*
*So, what would be "useful to us in this regard"?*
Having to go use a custom script that needs to be updated by a third party
upon changes to the CineDrive shouldn't be the final state of solution for
this.
But in the mean time you need not worry, if you end up in the position of
having to get a hand on that motion data, you definitely will be able to.
On Mon, Feb 25, 2013 at 5:51 AM, Paul Griswold <
pgrisw...@fusiondigitalproductions.com> wrote:
> Someone posted some info to the list a while back. Let me see if I can
> track it down and repost it.
>
> You'd think Kessler would ship this thing with the ability to output
> something useful - at least for things like Nuke & Fusion.
>
> -Paul
>
>
>
> On Mon, Feb 25, 2013 at 3:28 AM, Jens Lindgren <
> jens.lindgren....@gmail.com> wrote:
>
>> Looking at that XML I'm guessing it will be hard to reverse engineer
>> without a real rig to verify against.
>> But if there is specs on the format it should be relatively easy.
>>
>> /Jens
>>
>>
>> On Mon, Feb 25, 2013 at 7:30 AM, Steven Caron <car...@gmail.com> wrote:
>>
>>> is there any documentation on the format? reverse engineering it is
>>> possible but never fun
>>>
>>> s
>>>
>>>
>>> On Sun, Feb 24, 2013 at 5:43 AM, Paul Griswold <
>>> pgrisw...@fusiondigitalproductions.com> wrote:
>>>
>>>> Hey guys -
>>>>
>>>> I mentioned this a while back & if this list allows attachments, I'll
>>>> attach a Kessler XML file.
>>>>
>>>> It looks like rather than baking out a keyframe for every frame, it's
>>>> describing curves.
>>>>
>>>> In any event, it's beyond my abilities to pull anything useful to
>>>> Softimage out of it. This is a favor project again for the show Film Riot,
>>>> so if anyone wants to take a crack at this file, feel free.
>>>>
>>>> It might be nice if Softimage is the first package to have a plug-in
>>>> that can read this data anyway.
>>>>
>>>> -Paul
>>>>
>>>>
>>>
>>
>>
>> --
>> Jens Lindgren
>> --------------------------
>> Lead Technical Director
>> Magoo 3D Studios <http://www.magoo3dstudios.com/>
>>
>
>
