Thanks guys for all these precious inputs.
As u7angel said, it's really incredible to see how many needs and whishes related a timeline. It's clear that is a key piece of software... :)
My intent is to first release a relatively simple tool, which will have all the functionalities of a basic timeline (as the old Timeliner node) plus the new feature of "dynamic keyframes". These dynamic keyframes are for me the most innovative contribution of this research and I'd like to have as soon as possible some feedbacks from the community.
Then it will be a long journey to evolve this first version of Kairos.Timeline into something else, more rich and versatile. Actually, my final goal is to get something like an Ableton Live kind of software, but incredibly superior in terms of realtime contents management. This will be Kairos.
So, coming back to the roadmap (also a reply to @readme) , this first version will come as a "centralized" editor, in which you create tracks, group them, add and edit keyframes, and so on..
then there will be a set of nodes to set and retrieve data from it, like: GetTrack, SendChannel (to send any kind of data to a channel, received for example by a dynamic keyframe), SetKeyframe, SetCustomClock, ...
I'll probably also pack some of the Kairos.Timeline features as independent vvvv nodes, eg. a Track node, which contains all the features of a single track without the rest of kairos. this module would still allow you to create amazing gradients and fades...
obviously you can still instantiate many Kairos.Timelines as individual vvvv nodes, even if not best optimized approach.
few scattered replies to your suggestions:
1. not in the first release, but def wanted
2. already now the runtime of the software is separated from the model and the editor, so it will be possible, i guess, to have some sort of independency from the vvvv fluctuating frame rate.
3. yes. It will be possible to record keyframes on the fly. I'm still thinking to a different mode in which you can record raw values, with less functionalities than keyframes but better performances.
4. and yes, editable keyframes.
5. this is totally possible (I also need it for NRT rendering). Since you can manually set the Time 64bit value (which is the position of the sampler that sample each track) you can read from the timeline as you like, eg. sending the time position of every frame from your vvvv patch...
6. right now I implemented just Time (in seconds) as the main time measurement. I already got a dynamic snap to quantize movements depending on the time zoom magnitude.
7. My plan is to put a toggle to switch between Time and Tempo (with BPM and Tempo Signature).
8. I definitively want to have hierarchies in tracks. I'm still thinking (and I'd like your suggestions) what kind of control you would have over tracks from the group level, and how to display groups in UI.
1. I already have this feature as "section markers", which have a dedicated mini track under the time bar.
you can play from any of the section markers and even call from outside (eg. vvvv node).
what's best: "section" or "chapter"?
3. sorry my ignorance, what's OTF?
4. regarding frame interpolation:
- It will be per keyframe
- types: StepIn, StepOut, Tween (with all relative settings), bezier (being able to control two handles)
- advanced SpreadCount interpolation modes
7. I'm still considering all this merging stuff... def not in this first version
9. do you mean sort of labels that you can put into the timeline of every track? like comments that you can place near the keyframes?
...chaos is my bread... :)
1. to 5. will see how much i can get in terms of external control for this first version, but definitively wanted.
I'd like to have Audio tracks in the future, don't think in this first release.
I already splitted completely the model+runtime part of the software from the editor (UI), so you can eventually edit the timeline then have just a much light player without any UI... ...or design a minimal interface.
- nesting feature def is the direction of kairos. not for this first release
- serialization: I'll def want to sort this part in a way that future version will be campatible with previous presets and scenes. so yes, I need to create a standard for this.
thanks for the link!
keyframes snapping to other keyframes: yes
you will get an animation tool already from the first version... ...hopefully :)
thanks so much for the input. I'm downloading it and I'll def give a try. tnx
I'll keep you posted with the development news and I'll ask here if I have doubts regarding some features
thanks to all
...and don't stop to send me suggestions and links for references ;)