This is a standalone, crossplatform, opensource timeline application. It allows you to define keyframes of values, strings and colors over time and receive the values of a specific point in time via UDP/OSC.
see: TimelinerSA
Doubleclick TimelinerSA.exe. If it crashes or nothing happens at all you may not have .net3.5 SP1 installed
The .net equivalent for other platforms is Mono. Tested on Ubuntu with mono2.4. To run simply call
mono TimelinerSA.exe
from a commandline. That should be it.
Please report all troubles/findings in the Q&A section.
press any of the following buttons on the top to create a new:
In the PinHeader to the left pins can be given a name. This name is used as the pinname within vvvv. Pressing the X-Button deletes the pin. Use dragdrop on the PinHeader to change the order of pins. ClickDragging UpDown in a small zone on the bottom of the PinHeader a pins height can be changed.
When hovering a slice with the mouse some buttons appear on the left. They allow you to delete a slice add a slice (above or below the current slice) and move them up or down.
Doubleclick within a pin to create a new keyframe. Right-Doubleclick a keyframe to delete it.
Select a keyframe by clicking on it or select multiple keyframes by click-drag spanning a selection rectangle. Use CTRL and ALT keys to add/remove keyframes to a selection.
Move keyframes by dragging them:
Pressing SHIFT while dragging allows for finer changes. Pressing CTRL while dragging makes keyframes snap to automatas states and the timebar.
Doubleclick a keyframe to open an editor and change its values. This also works when multiple keyframes are selected. Note that only values changed in the editor will be written to the keyframes. Therefore as long as you don't change the time all keyframes will stay at their time-position but only will be set to the same value.
RightClick-drag in an empty area of a pin/track:
The Midi Pin is still quite experimental and will only work on windows. By clicking on the *.mid in the PinHeader you can select a midi-file to be loaded. The individual midi-tracks as specified in the file will appear as Slices. Note that only tracks that have notes will show up.
You can edit notes in time and pitch and delete them. Adding notes or changing velocity is not yet implemented.
Pressing the [S] button next to the filename will save the file. Note: Simply loading and saving a file will alter your original midi-file! Not all information present in your original file may be saved in the new file.
Timerliner includes a simple finite state automata which lets you specify some logic that influences the course of time. Activate it via the checkbox labeled A for Automata.
Per default the automata includes the following 3 states:
that make up a simple loop. While you can get rid of or change the first two, the last one will always be there, as it sits at infinity and you'll hardly reach it.
Doubleclick in an empty area to create a new state/keyframe or doubleclick an existing state/keyframe to modify it. DoubleRightClick a state to delete it.
Note, that each state spans from the previous one to its own visual representation. The keyframes in the Automata area therefore always only specify the end of a state.
Move states in time using the left mousebutton. Use the right mousebutton to scale all keyframes of this state and move all following keyframes further in time. Use the middle mousebutton to scale the keyframes of the next state and move all previous keyframes in time accordingly. Hard to explain, still indispensable.
Every state can have any number of events that can cause a statechange at any time. Every state has one event for sure, the OnEnd event, which specifies the action to execute when the states end is reached.
DoubleClick a state/keyframe to change its name, time and specify additional events. In the middle textbox in the upcomming editor you can specify a list of event/action pairs, separated via linebreaks, like:
OnBang next OnSupa pause OnBad play
For readability it is recommended to start events with On...
Every event needs an action which will be executed as soon as the event occurs. The following is a list of built-in casesensitive actions with their corresponding icons as seen on the keyframes:
next >> previous << loop >< play > pause ||
If you write any other string next to an event it will be treated as a state and on execution of the event the automata will jump to the beginning of that event or pause if an event with such a name is not present.
By double-clicking in the empty space next to a tab you can open more instances of the timeline. Middle-click on a tab removes it.
All of Timeliners current values are being sent via UDP using the OSC protocoll. Specify a target IP address (127.0.0.1 is the localhost) and a port (default: 4444).
All values are sent in one OSC-Bundle. The individual messages addresses comprise of the base-address set in the edit-field + the pinname. e.g.:
/timeliner/Value0 /timeliner/String0 /timeliner/Color0
TimelinerSA can be controlled via OSC commands. It listenes to commands sent to the port set via the rightmost numberbox in the interface (which defaults to 5555).
Send the commands to the base-address as set in the edit field + the command you like to controll. e.g.:
/timeliner/Play 1
/timeliner/Set Time 1
/timeliner/Time In 0.234
For a listing of similar alternatives see Animation
anonymous user login
~1d ago
~1d ago
~9d ago
~11d ago
~13d ago
~16d ago
~16d ago
~23d ago
~30d ago
~30d ago