How to get Playable.GetTime() when not in play mode ?

Code (CSharp):

1. public override void ProcessFrame(Playable playable, FrameData info, object userData)
2. {
3.      Debug.Log(playable.GetTime());
4. }

When used on a playable behaviour for a clip the above code always shows the clip time, in editor or playmode. When used on a mixer behaviour, i.e. for a track, it is not a reliable source in editor because the track playable time is never explictly set. It starts at 0 and advances in playmode, but is never reset for loops or if you scrub. In the editor, it's time never advances because the playback is only simulated.

If you are looking to get the time of the timeline, you can use playable.GetGraph().GetRootPlayable(0).GetTime().
The timeline playable is the (only) root of the graph, and it's time is what is displayed by the timeline playhead.

 

PrepareFrame is called 'top-down' - it is called on the mixer prior to it being called on any active clips.

ProcessFrame is called 'bottom-up' - it is called on the clips prior to it being called on the mixer.

To get the normalized time, in the clip's playable behaviour, you can call playable.GetTime()/playable.GetDuration(), depending on the functionality of your clip (clip-in and playableAsset.duration can change the meaning of that).

As for the frustrating part of writing playables in timeline, that's a pain point that we understand. Extending timeline is done through using the Playable API - not a timeline specific API. We have design drafts for creating timeline specific classes (e.g. TimelineBehaviour instead of PlayableBehaviour) to make extending timeline more intuitive, and address that frustration.

 

Not directly, the playable system doesn't work in frames, everything works in seconds. You can get the playhead time by using

playable.GetGraph().GetRootPlayable(0).GetTime().

The frame rate is stored inside the timeline asset as timelineAsset.editorSettings.fps; That's not accessible directly from a playable behaviour, but you can set it on a custom behaviour when you create one.

Code (CSharp):

1. class MyPlayableAsset {
2.     ....
3.     public override Playable CreatePlayable(PlayableGraph graph, GameObject go)
4.     {
5.         var playable = ScriptPlayable<MyBehaviour>.Create(graph);
6.         var playableDirector = go.GetComponent<PlayableDirector>();
7.         if (playableDirector != null)
8.         {
9.             var timelineAsset = playableDirector.playableAsset as TimelineAsset;
10.             if (timelineAsset != null)
11.                 playable.GetBehaviour().frameRate = timelineAsset.editorSettings.fps;      
12.         }
13.         return playable;
14.     }
15.     ...
16. }

 

Yes, that's a bug we intend to fix