Setting TimeTrack For A Sequence



  • THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

    On 04/04/2003 at 08:12, xxxxxxxx wrote:

    User Information:
    Cinema 4D Version:   8.100 
    Platform:      Mac OSX  ; 
    Language(s) :     C++  ;

    ---------
    I cannot find a function in the documentation to set a sequence's TimeTrack association. Help?

    Best Regards,
    bt



  • THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

    On 04/04/2003 at 08:35, xxxxxxxx wrote:

    It's "LINK ID_BASESEQ_TIME" of SEbase.res. Use something like "SetParameter(DescID(ID_BASESEQ_TIME), gedatalink, 0)" to set it.



  • THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

    On 04/04/2003 at 09:13, xxxxxxxx wrote:

    Well, I was using something similiar.

    Seems that problem is that v8 is delting the time track after I create it.

    Here is the path:

    MSG_MULTI_DOCUMENTIMPORTED
    Find tracks imported from v7 that v8 will destroy when the document is finished loading ( I understand why ).

    I find the time track if there is one and create a new one based on the v7 time curve information. Define time_Track == to the newly created track. It is null if no time track.

    Find the parameter track and turn it into several nice new parameter tracks ( this works ). If time_Track is not null set the sequence time track link to time_Track.

    Finished.

    ( If I list all the tracks my time track as well as all the time tracks I expect are listed. )

    For some reason v8 then deletes the old parameter track, the old time track ( these I understand ) and then my new time track! I thought maybe I wasn't setting some flag that v8 was evaluating to see if it was an old time track. I assume that is still it but can;t make it work.

    Help?

    Best Regards,
    bt



  • THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

    On 04/04/2003 at 12:16, xxxxxxxx wrote:

    LOL!!!
    All the incoming keyframes from the time curve have a time of zero... Therefore all of the keys overwrite each other. My validation routine was deleting the last keyframe leaving it vulnerable to the v8 import destroyer... The time has to come from the normalized sequence time stored in the x component of the vector retrieved from the basecontainer id of 1000 in the key data. Fun, fun... Now, let's see what I can make a guessing game out of next!  ;-)
    Best Regards,
    bt


Log in to reply