Independent engineering & research project

O·C·E·A·N Research: Continuous Geometry & Motion Synthesis

Continuous Geometry. Deterministic Motion. Computational Engineering.

Exploring new approaches to interactive geometry, motion synthesis and computer-aided manufacturing.

O·C·E·A·N is an independent engineering and research project connecting computational geometry, motion control, CAD/CAM and digital animation. It is developed by Benjamin Thorsten Unger, a CNC/CAM practitioner with around two decades of machining experience. All research lines share one idea: describe geometry and motion continuously first, and discretise only when a machine, a renderer or a screen actually needs samples.

Four research lines

Four independent lines. One principle.

FlowSketcher, Infinity OvumPath, TSDE and TSDE TimeOS are separate projects with separate code bases and separate audiences. Choose the line you are interested in.

How to read this page
ImplementedWorking software, available or in active use.
DocumentedDescribed in project documentation or a published record.
ExperimentalPrototype or preliminary result, not validated.
PlannedDefined next step, not yet carried out.
Future conceptResearch direction, no implementation.
Line 1FlowSketcher × FlowCamImplemented

From Touch to Geometry.
From Geometry to Manufacturing.

FlowSketcher is a browser-native interactive 2D geometry environment with integrated CAM. The input is a movement of a finger, pen or mouse; the output is CNC-ready G-code. It runs on tablets, laptops and phones — no framework, no build system, no mandatory cloud service.

01Sketch

Direct Geometric Manipulation

Input

Mouse, pen or touch

Pixel-based snap tolerance — endpoint, midpoint, centre, intersection, chain joints, construction lines, polar tracking, ortho — so snapping feels the same at every zoom level.

Geometry

Interactive circular arcs

Every arc attached to an existing arc or line joins tangentially (C1) by construction. The user only chooses the side: G2 or G3. Lines, circles, Catmull-Rom splines, spline-to-arc conversion, fillets, offsets and SVG import complete the toolset.

Features

Parametric features

Slots, arc slots, chain-following slots, rectangular and circular pockets, bores and pattern distribution along curves (FollowCurve) — all editable after creation without creating duplicates.

Architecture

Offline-capable browser app

Vanilla JavaScript and Canvas. Command-pattern undo/redo with merged drag operations. No mandatory cloud service and no build environment.

FlowSketcher screen with open and closed arc chains and an offset contour
Open and closed ArcFlow chains in the sketch, one with an offset contour.
FlowSketcher screen with overlapping closed arc chains
Overlapping closed arc chains; EP marks the end points of the individual arcs.
FollowCurve screen distributing a feature six times along a curve
FollowCurve: a feature distributed N times along a curve (here N = 6), with the scale envelope in the graph below.

What FlowSketcher is not

Not a complete commercial CAD platform, not a solid modeller, not a constraint solver and not 3D. It is a precision tool for people who know what G2 and G3 mean and who operate machines. The interface is minimal because every element is needed — not because simplicity is the goal.

02ArcFlowImplemented in FlowSketcher

ArcFlow — Continuous Circular-Arc Geometry

ArcFlow constructs connected circular-arc chains with tangential continuity. Interactive manipulation updates dependent geometry through deterministic propagation.

Given a start point P, an incoming unit tangent T and an end point Q, there is exactly one circular arc (or, in the degenerate case, a straight line) that leaves P along T and ends in Q:

N = (−T.y, T.x) left normal v = Q − P t = |v|² / (2 · v·N) signed radius centre = P + t·N, r = |t| v·N ≈ 0 → straight segment

The end tangent of one arc becomes the start tangent of the next. Moving a point sends a propagation wave through all following segments; the chain behaves like a spring rod. Because only the direct predecessor supplies the tangent, propagation is deterministic and repeatable.

The objective is to preserve meaningful circular geometry instead of approximating everything with polylines — because circular arcs map directly to circular interpolation (G2/G3) on the control.

Closing a pure arc chain tangentially is checked live while dragging: green below 15° deviation, yellow from 15° to 35°, red when rotation directions are incompatible. Where the tangent does not fit, a closing blend (Catmull-Rom segment) bridges the gap with G1 continuity.

Try it: drag the points

Explanatory illustration
G2 (CW) G3 (CCW) T₀ Arcs: – Min. radius: –
Minimal re-implementation of the arc rule above, in screen units. Direction labels refer to a top view of the XY plane.

Import · SVG and splines become arcs

Dialog for pasting the d attribute of an SVG path, with presets for rectangle, circle, spline and star
SVG import: paste the d attribute of any SVG path. The curve can then be turned into tangent arcs with Spline → Arc.
An open spline converted into 11 tangent circular arcs, with a quality slider
Spline → Arc: an open spline becomes 11 tangent arcs. The quality slider trades arc count against deviation.
A closed star contour converted into 59 tangent circular arcs
A closed SVG star: 59 tangent arcs, closed without a gap — later 59 CR blocks in the NC program.

Interactive ArcFlow demo

Egg-shaped closed arc chain, morph spiral built from tangent arcs, live parameters and rubber-band control points.

Open the interactive ArcFlow demoArcFlow demo — link not yet configured
03OvumPath in CAMImplemented

OvumPath — Egg Contours as Toolpaths

Inside FlowSketcher, egg-shaped arc contours become machining geometry: offsets, morphs and spirals that stay exact circular arcs all the way to the NC program.

  1. Arc-based contourA few control points and one start tangent produce a closed chain of tangent arcs.
  2. Parametric inner shapeA scaled inner contour, a circle, an egg, or a copy of the original chain.
  3. Interactive morphCorresponding points are interpolated over ~40 selectable curves. CNC-relevant modes start and end exactly on the contours.
  4. Arc-only spiralEach spiral step is a new arc tangent to the previous one, so the resulting path is again a tangent-continuous arc chain.

OvumPath is the only CAM tool that sits directly on an ArcFlow chain instead of a feature. It generates inward offset rings with collapse detection, then morphs from the inner shape over the last full ring back to the original contour, with an optional finishing pass. OvumCircPocket uses a radial correspondence — one ray from the egg centre through each vertex — so the morph does not twist, even for an eccentric egg.

Geometry background · Line 2

Infinity OvumPath

The egg geometry itself — arc construction, axial continuation into the dual-strand egg helix, 3D sweeps and the utility-model publication — has its own research line.

Open Infinity OvumPath →
OvumPath screen with offset rings, morph spiral and analysis panel
OvumPath on a three-lobed arc contour: offset rings outside, morph spiral inside, circle as inner shape. The analysis checks every section before post-processing — minimum radius 14.927 mm against a 5 mm tool radius, 354 arcs, 25.6 m of path, nominal run time 25:35 min.
04Toolpaths · FlowCamImplemented

Six Milling Strategies, One Arc Model

Each strategy picks a source, is configured in a panel, simulates live and is stored as a path on its source. All produce arc-based paths.

StrategyPrinciple
SpiralPocketHelical plunge, spiral outwards, finishing pass, retract. Source: circular pocket or bore.
RectPocketMorph from an inner shape (circle or egg) to the rectangular contour.
BossCamMorph spiral from the picked feature to the outer stock contour (boss machining).
CirctenCircle and arc machining referenced to rectangular or circular stock.
OvumCircPocketCircular pocket with egg morph and radial correspondence.
OvumPathFree form on an ArcFlow chain: offset rings, collapse detection, morph back to the contour.
Shared infrastructure
  • Simulation with pedal (−100 % to +100 %), backplot, tool marker, stock removal, R/Z side view, phase display with feed per phase.
  • Analysis per path section: minimum radius with tool-radius indicator, arc count, length, plus nominal run time.
  • Stored paths reopen with all parameters; one path per source and cycle type, no duplicates.

Output: sketch arc = machine arc

ISO G-code (G1/G2/G3) and Heidenhain conversational (Klartext), optionally with mirrored X or swapped direction. Tool-edge paths with RL compensation — never centre paths; the control applies radius compensation. There is no approximation step between drawing and machine.

RectPocket screen with a woven morph spiral inside a rectangular pocket
RectPocket: morph spiral from an egg-shaped inner form to the rectangular pocket contour, built entirely from tangent arcs. The path simulation runs on the same distance-based motion logic as TSDE.
Circular pocket contour pass with arc lead-in and lead-out
Contour pass with arc lead-in and lead-out (dashed), simulated with pedal-controlled feed.
05CNC toolpath research

Geometry That Reaches the Machine

A toolpath is not only a shape. It is a sequence of blocks that a control has to read, plan and execute under physical limits. The geometric representation chosen in CAM affects every stage of that chain.

01

Geometric continuity

Tangent breaks force the axes to decelerate towards a stop at the corner. Tangent-continuous (C1) paths avoid these forced stops; curvature, however, still changes stepwise at arc-to-arc joints.

02

Native circular interpolation

G2/G3 describe an arc exactly in one block (end point plus centre or radius). A polyline approximation needs many short G1 blocks and introduces chord error.

03

Toolpath length

Spiral and morph strategies change the total path length and the share of cutting versus non-cutting moves. Length alone does not determine time; achievable feed matters as much.

04

Program complexity

Fewer, exact blocks mean smaller programs and less block-processing load. Where blocks are very short, block processing time can limit the effective feedrate.

05

Feedrate and curvature

On an arc of radius r at feed v, the normal acceleration is v²/r. With an acceleration limit a, the feed is bounded by v ≤ √(a·r) — small radii cost speed.

06

Machine dynamics

Look-ahead, jerk limits, servo tuning, contour tolerance settings and kinematics decide how a given path is actually executed. The same NC program can behave differently on different machines.

The FlowCam approach

FlowCam keeps the arc as the primary entity from sketch to NC block. Before post-processing, the analysis panel shows for every path section the minimum radius against the cutter radius — so radii below the cutter radius are visible before the program reaches the machine.

No universal performance claim

Benefits of native arcs and tangent-continuous paths depend on the control, its parameters, the machine, the tool and the operation. Results from one setup must not be generalised to every machine or machining task. Measured comparisons belong in the benchmark laboratory.

Run on a machineSingle run

Adaptive roughing under radius compensation

Radius compensation only works if the control can offset the programmed path equidistantly. That needs a contour rather than a point sequence, tangent continuity, and inside radii no smaller than the tool radius.

Adaptive roughing cycles are usually computed as a centre path from an engagement calculation and output as G1 point sequences or approximated arcs. Neither is a finished contour the control could offset. To our knowledge there is no adaptive cycle on the market that outputs a compensatable finished contour.

ArcFlow reverses the order: the path is an arc chain from the start — every element a true circular arc, every joint tangent by construction. A morph spiral with 658 CR blocks ran completely under RL on an iTNC 530.

; compensation built up on the approach line L X-51.576 RL M109 CR X-41.576 Y+37.603 R10.000 DR+ CR X-20.824 Y+37.595 R25054.686 DR- CR X-0.076 Y+37.586 R25054.687 DR+ ... ; 658 arcs, all under RL CR X+42.321 Y+36.929 R0.915 DR- ; cancelled on the exit line L X-159.694 Y-46.364 R0 F800
What this means on the shop floor
  • Reground cutter → enter delta R, keep going.
  • Change the allowance → change the compensation value.
  • Roughing and finishing from the same program, only the compensation value differs.
  • The operator can intervene at the machine without going back to CAM.

Control-side adaptive cycles exist as paid software options for newer controls (e.g. Heidenhain OCM); they work on the pocket and boss shapes the cycle can describe. ArcFlow addresses the CAM side: any arc contour becomes an adaptive path that leaves the CAM system as a compensatable contour — and also runs on older controls such as the iTNC 530.

Circular-pocket simulation on a star contour with RL compensation; the button switches to RR
The star contour from the SVG import as a machining source: simulation under RL with direction and lead-in; one button switches the contour side to RR.
Heidenhain NC output: CR blocks under RL compensation
Heidenhain output: L … RL on the approach line, then only CR blocks with DR+/DR−. No G1 chain, no tolerance band.
06Benchmark laboratory

Real Machines. Measurable Results. Reproducible Experiments.

Claims about toolpaths should be tested on machines, under documented conditions, with data others can check. This laboratory separates what has been observed from what still has to be measured.

Preliminary · single runMeasured 3 Sep 2026

Initial machine comparison

First comparison on a real machine against the established adaptive roughing strategy of a commercial CAM system (anonymised). Rectangular boss, same removal volume, one depth step, roughed. FlowCam is the reference; the values show the difference of the comparison strategy.

ItemFlowCamComparison
ControlHeidenhain iTNC 530, same machine for both
Run timeReference+20 s
Path lengthReference+2 m
Advantage in ae and vf—yes
Extra finishing passyesno
Radius compensationRL over the whole pathcentre path
CYCL 32 toleranceno influence on timeup to 5 s difference

FlowCam was shorter despite giving the comparison more step-over and feed, and despite running an additional finishing pass. Its run-time forecast matched the machine. A side finding — the control visibly paused at one corner because short sub-arc blocks fell below the block processing time of the iTNC 530 — led to a hybrid subdivision in BossCam.

Limitations: one run on one machine, not independently reproduced. Tolerance series (T1.0 / T0.5 / T0.05, two runs each, time from the control counter) still open. Material and tool are not documented here.

Close Beta

Independent CNC benchmark

I cannot run further benchmarks myself. The next measurements therefore come from Close Beta testers: real parts on their machines, documented so that others can check them. Every result field stays empty until it has been measured.

Status: Close Beta · testers wanted

Principles: identical machine, tool, material and fixturing for every compared strategy; multiple runs; times read from the control; raw data and NC programs published.

Planned documentation protocol

ParameterDocumented asResult
Machine model & controlManufacturer, model, control, software version, relevant parameterspending
Workpiece geometry & materialDrawing / CAD file, material grade, stock dimensions, fixturingpending
Cutting tool & manufacturerManufacturer, product code, holder, stick-outpending
Tool geometry & cutting parametersDiameter, flutes, corner radius; vc, fz, ap, aepending
CAM strategy & software versionsStrategy, settings, CAM / post-processor versions for each compared pathpending
NC programsComplete programs as executed, published for downloadpending
Actual machining timeRead from the control, several runs per strategypending
Toolpath lengthCutting and non-cutting length per programpending
Surface qualityRoughness measurement method, instrument and positionspending
Dimensional measurementsMeasured features, instrument, temperaturepending
Recorded machine footageUncut recordings of each runpending
GoPro video documentationIn-machine camera views, synchronised with run logspending
Reproducible test conditionsFull protocol so a third party can repeat the testpending
Close Beta

Close Beta testers wanted — with real machine videos

FlowSketcher and FlowCam are looking for machinists, programmers and shops who run real parts: one contour, one pocket or one boss is enough. Simulations I can run myself — what is missing is footage and data from real machines. A negative result is explicitly welcome; all reports are published with their conditions.

What a test report should contain

  • Machine and control, including software version
  • Material and stock
  • Tool: manufacturer, type, diameter
  • Cutting data: vc, fz, ap, ae
  • Programmed vs. actual run time (control counter)
  • Radius compensation used (RL/RR)
  • Alarms or stops, if any
  • NC file as executed and logs
  • Result: surface, dimensions, observations
  • Video of the run — uncut if possible
07Technical questions · CAD/CAM

Engineering FAQ — Geometry & Manufacturing

What is C1 tangential continuity?

At every joint, adjacent segments share the same point and the same tangent direction (strictly, C1 refers to a continuous first derivative of the parameterisation; G1 to a continuous tangent direction). ArcFlow chains are tangent-continuous by construction. Their curvature is piecewise constant and changes stepwise at arc joints, so they are not curvature-continuous (G2/C2).

Why are native circular arcs useful in CNC programming?

G2/G3 represent an arc exactly in a single block. Approximating it with straight G1 segments requires many blocks, introduces chord error and can let block-processing time limit the feedrate. Native arcs keep programs compact and preserve design intent such as radii and centres. The actual benefit depends on the control, its tolerance and smoothing settings, and the machine.

What is the relationship between curvature and feedrate?

Curvature is κ = 1/r. Moving at speed v along a curve requires a normal acceleration of v²·κ, so an acceleration limit caps the speed at √(a_max / κ). Tangent breaks require stopping at the corner, and sudden curvature changes produce jerk.

Can browser-based software generate CNC programs?

Yes. G-code and Heidenhain conversational programs are text, and browser JavaScript can compute geometry and write that text locally without a server — FlowSketcher does exactly this. As with any CAM system, programs must be checked by simulation and by a qualified operator against the specific machine, control and post-processor settings before running.

What makes a CNC benchmark reproducible?

Complete documentation of machine, control and parameters, tool and holder, material and fixturing, cutting data, CAM and post-processor versions; published NC programs; times read from the control over several runs; stated measurement methods for surface and dimensions; and identical conditions for every compared strategy, so a third party can repeat the test and obtain comparable data.

Line 2Infinity OvumPath — the endless egg helixDocumented

Biomorphic Geometry
from Circular Arcs.

Organic forms, built from exact geometry: an egg-shaped contour made of tangent circular arcs, continued along an axis into two counter-wound strands, and swept into three-dimensional bodies.

01Egg contour

An Egg Made of Circular Arcs

Organic-looking contours can be constructed from circular arcs whose joins share tangent directions. Parameters that change radii, arc positions and transitions create families of egg-like or biomorphic shapes while preserving a circular-arc representation.

Infinity OvumPath explores this relationship between geometric construction, parametric shape generation and interactive morphing. A contour is both a visible form and geometry that can be offset, transformed or used as a machining boundary — the same arcs that appear in FlowSketcher's OvumPath CAM tool.

Tangency alone does not make curvature continuous: at each join the radius changes stepwise. That distinction matters as soon as a shape becomes a motion path or a toolpath.

CIRCULAR-ARC CONTOURSTANGENTIAL TRANSITIONSPARAMETRIC MORPHING
An illustrative egg-like contour built from four circular arcsA closed contour made from a lower semicircle, two large side arcs and a smaller top arc, joined tangentially, with construction circles and radius lines.r2r(2−√2)rPARAMETRIC CONTOUR / CONSTRUCTION STUDY4 CIRCULAR ARCS · TANGENT JOINS
Illustrative four-arc egg construction — lower semicircle r, side arcs 2r, top arc (2−√2)r, all joins tangent. Not a reconstruction of the proprietary Infinity OvumPath algorithm; no uniqueness or novelty claim is implied.
02Axial continuationDocumented

From Contour to Endless Egg Helix

Schematic of two counter-wound strands crossing along an axis2D egg contour → axial continuationaxiscrossing
Schematic side view: two counter-wound strands crossing repeatedly along the longitudinal axis. Illustration of the principle only — not the published or proprietary geometry.

The utility-model publication describes a guide curve generated by axial continuation of a single closed, egg-shaped two-dimensional contour. Iterative multiplication and axial displacement of this contour produce exactly two counter-wound helical strands that cross repeatedly along the longitudinal axis.

The publication further describes:

  • two counter-wound, break-free strands along an egg-shaped contour,
  • a defined crossing of the strands at the zero point of the structure,
  • self-similar, scalable geometry derived from a two-dimensional egg form,
  • software-based generation with export as a point cloud (e.g. CSV) for CAD, CAM, 3D printing or simulation.

The mathematical derivation and generation variants are proprietary and not disclosed — neither in the publication nor on this page.

Egg-helix software, top view: six nested egg contours
Egg-helix software, side view: the resulting strand along the axis
Viewer: red counter-clockwise and blue clockwise strand as tubes
Viewer: both strands crossing repeatedly along the axis

Light background: the egg-helix desktop software (V1.01, not released) — top view of six nested egg contours and side view of the resulting strand. Dark background: an internal viewer showing both strands as CCW and CW point clouds (CSV, 1,356 points each), drawn as tubes.

03OvumMath GH Sweep GeneratorDocumentedOpen source: planned

Sweeps Along the Egg Helix

A Rhinoceros/Grasshopper plugin turns the guide curve into solid geometry: a cross-section is swept along both strands of the egg helix.

  • User-defined cross-sections or predefined presets.
  • A proprietary “golden cross-section scaling” tuned to the guide curve; the publication describes generation within seconds.
  • Output for 3D modelling, additive manufacturing and simulation.
  • An open-source version for private use is planned; the proprietary scaling either stays protected or is replaced by an alternative scaling.

The clip shows rendered sweep results. Generation speed and scaling method are stated as described in the utility-model publication; no independent benchmark is published.

3D sweeps along the dual-strand egg helix, rendered from the Grasshopper sweep generator. 14 s, no sound.
Rhino viewport: sweep of a custom cross-section along the egg helix
Sweep of a custom cross-section along the egg helix, Rhino viewport.
04PublicationRegistered utility model

German Utility Model DE 20 2025 002 688 U1

Bibliographic data
Title
Bauteil mit fraktaler Eier-Helix-Kontur
(Component with fractal egg-helix contour)
Number
DE 20 2025 002 688 U1
Filed
9 September 2025
Published
8 January 2026
Holder
Benjamin Thorsten Unger
Classification
G06F 30/10 · G06F 30/20
Language
German

Text version provided by the German Patent and Trade Mark Office (DPMA), without drawings.

Protection claims (summary)

  1. A component with at least one guide curve generated by axial continuation of a single closed, egg-shaped 2D contour; iterative multiplication and axial displacement produce exactly two counter-wound helical strands that cross repeatedly along the longitudinal axis.
  2. Any cross-section is extruded or swept along the two strands.
  3. Single- or multi-part, in any section of the guide curve and at any scale.
  4. Manufactured additively, by casting, milling, injection moulding or other cutting or forming processes.

English summary for orientation; the German wording of the publication is authoritative. German utility models are registered without substantive examination of novelty and inventive step. This page makes no claim of worldwide novelty or uniqueness.

05Applications & status

Where the Egg Helix Could Apply

The publication names a broad set of potential application fields. They are listed here as named — without measured evidence, which has not been published for any of them.

Engineering

Construction & manufacturing

Adaptive support structures for 3D printing, CAM milling strategies, load-bearing structures.

Fluids

Flow & vortex formation

Targeted vortex formation in fluid media and flow optimisation are proposed; concrete implementations are reserved for future applications.

Design

3D modelling & education

Sweeps with custom cross-sections, decorative objects, modular and educational construction systems.

Research

Further fields named

Biotechnology and medicine (scaffolds, microfluidics), physics and astronomy (resonance models, simulations).

ComponentStatus
2D egg contour from tangent arcsImplemented in FlowSketcher (OvumPath, OvumCircPocket) and the ArcFlow demo
Dual-strand egg helixDocumented registered utility model DE 20 2025 002 688 U1
Grasshopper sweep generatorDocumented results shown in the clip above
3D viewer for the strand point clouds (CSV)Internal not released
Egg-helix desktop software V1.01 (contours, helix, CSV spline export)Internal not released
Open-source plugin for private usePlanned
CAM cycle for the egg helixIn development per the publication
Online ecosystem to configure and order 3D printsPlanned per the publication
06Technical questions · Egg helix

FAQ — Infinity OvumPath

What is the egg helix?

A guide curve obtained by continuing a closed, egg-shaped 2D contour along an axis. Repeating and displacing the contour produces two strands wound in opposite directions that cross repeatedly along the axis. Cross-sections swept along these strands produce three-dimensional bodies.

How does it relate to FlowSketcher?

The 2D egg contour is built from tangent circular arcs — the same geometric principle as ArcFlow. In FlowSketcher the egg appears as a planar machining contour (OvumPath, OvumCircPocket). The helix and the sweep generator are a separate, three-dimensional line of work.

Is the generation algorithm public?

No. The utility model publishes the claimed structure and its description; the mathematical derivation, generation variants and the golden cross-section scaling remain proprietary. The four-arc egg on this page is a generic textbook construction used for illustration.

What is a sweep?

A sweep moves a 2D cross-section along a guide curve and generates the surface or solid it traces. Orientation and scaling of the cross-section along the path determine the final shape — which is where the sweep generator's scaling method comes in.

Line 3TSDE — Temporal Spline Driven EngineImplemented · v0.9 Beta

Motion Before Frames.

Traditional position-keyframe animation constructs motion by interpolating positions assigned to specific times. TSDE approaches the problem differently: it separates geometry, velocity and time.

01Principle

Geometry. Velocity. Time.

Geometry

A spatial path — a spline — defines where movement occurs. Its geometric unwinding (arc length) is computed per track.

Velocity

A velocity function defines how movement progresses, in physical units (mm/s), driven by a per-track pedal between −100 % and +100 % of vmax.

Time

Position is derived from accumulated distance along the path. Frames are generated only when the resulting motion is sampled for output.

We don't interpolate motion between frames.
We sample frames from motion.
Audio
Signal→Sampling→Samples
TSDE
Motion→Sampling→Frames

As with audio, the mathematical description of the motion is independent of the output rate. The current TSDE engine advances its motion state on a deterministic fixed 240 Hz tick. Output frame rates such as 24, 96, 240 or 33.77 FPS are sampling settings applied to that motion — not the foundation of the motion model.

Scope of the current version

  • TSDE does not automatically calculate an optimal output frame rate. The output rate is chosen by the user.
  • Adaptive sampling based on motion characteristics (e.g. velocity or curvature) is a Future concept research direction.
  • TSDE does not replace keyframe animation — existing keyframe animations can be brought in, and the Blender host builds pivot and lens splines from them. Its strength is physically defined camera motion and rendering exactly the frames a target speed needs.
Keyframe timing

Speed as a by-product

In a keyframe animation, timing is shaped by Bézier handles; the camera's speed is whatever the curve happens to produce. For fast camera moves this leaves large jumps between frames exactly where the motion matters most. The common workaround is to render at very high frame rates — often 240 FPS — and retime in post, discarding most of the rendered frames.

TSDE

Speed as the input

TSDE defines speed directly, in mm/s with realistic acceleration and deceleration — the way a motion-control rig or a vehicle moves. Frames are sampled at constant time steps from that motion, so a TSDE render folder reads like the output of a real camera. Slow motion and time-lapse are resampled from the same recording: you render the frames the target speed needs, not a surplus to throw away.

Illustration: one motion, many sampling rates

Explanatory illustration
A curved path with dots marking where output frames are sampled. Changing the frame rate changes the number of dots, not the path or the velocity profile. v(t) t = 2 s

Output sampling rate (FPS)

Velocity profile (same path)

Display-rate playback

Engine ticks: 480 Frames sampled: – Frame interval: –
Browser illustration of the principle, not the TSDE engine itself: distance is integrated on a 240 Hz tick; frame positions are read from that motion at the selected rate (linear interpolation between ticks in this illustration). The velocity is scaled so the path completes in 2 s.
02–05Workflow

From Recording to Rendered Frames

The toolchain follows the motion from its first recording to the final render — the same integration logic at every step.

  1. Record — TSDE Live EngineDeterministic 240 Hz engine. Any number of tracks, each with its own spline, length function, velocity curve, vmax, start position and direction. A per-track pedal (−100 % … +100 %) drives forwards and backwards motion. Recorder at 240 Hz in a separate process.
  2. Edit — Motion Synth EditorImports a recorded session. Embedded VTK 3D viewport, timeline with an editable velocity curve per track and a second graph showing the distance along the spline. A new velocity curve creates a new motion from duration, vmax and start position.
  3. Preview — camera rigFocal length, sensor size, offset, height, distance. The camera can be bound to any track or marker. Preview uses the same spline sampling, velocity curves and distance integration as the live engine.
  4. Render — Blender host (4.0+)Setup builder for camera rigs with follow-path constraints, live control, quaternion-based render export with roll, multi-rig support, PNG/EXR/WebP output, time-stretch rendering from 0.1× to 10×.

Record

TSDE setup: rig group with pivot, lens, roll and camera tracks
Setup: one rig group with motion tracks for pivot, lens, roll and camera, each with its own vmax.
TSDE engine terminal with per-track pedals and the 240 Hz recorder
Engine terminal: an individual pedal per track, live curves, and the 240 Hz recorder.
Saved TSDE recording: 36,964 samples, 38.5 s, 4 tracks
A saved recording: 36,964 samples over 38.5 s and 4 tracks — 240 samples per second per track.

Edit & preview

TSDE Motion Synth Editor with velocity curves, camera rig settings and 3D preview
Motion Synth Editor: per-track velocity curve below the geometric unwinding, camera rig and 3D preview above.
TSDE editor dialog: new motion generated from a velocity curve
New motion from a velocity curve: start at a marker, 38.5 s, vmax 400 mm/s, 5,539.4 mm of path.
TSDE full-screen preview of pivot and lens tracks
Full-screen preview: pivot and lens tracks of one rig in group mode.
Technical notes for researchers

Motion model

With pedal value p(t) ∈ [−1, 1] per track:

v(t) = p(t) · v_max [mm/s] s(t) = s₀ + ∫₀ᵗ v(τ) dτ accumulated distance P(t) = C( u(s(t)) ) position via arc-length lookup tick: Δt = 1/240 s, s[k+1] = s[k] + v(t_k)·Δt frame n: t_n = n / f_out f_out is a sampling choice

Negative pedal values move backwards along the path; 0 % is standstill.

Data integrity

  • Monotone piecewise-cubic interpolation (PCHIP) is the default for velocity curves — no overshoot, no artificial peaks.
  • Automatic spike smoothing removes small sign spikes from velocity data.
  • The original time axis is preserved without normalisation, offsets or recalibration; export reproduces the original t byte-exactly.
  • Internal sampling, distance integration and pedal mapping run faster than the 240 Hz tick to keep execution jitter-free.

Planned extensions Planned

Modulation tools (noise, variation, pattern modulation), extended camera tools, multi-track camera rigs, live preview recording.

05+Blender host integrationImplemented · Blender 4.0+

Inside Blender

The Blender host connects the engine to an existing scene: paths come in from recordings or from existing animation, rigs are built automatically, and frames go out through Blender's renderer.

Spline generator

Three ways to a path

  • Walk/Fly mode — fly the camera path freely with a controller; the recording is smoothed in real time.
  • Spline Setter — the familiar keyframe workflow: set poses step by step, but the result is a spline instead of keyframes.
  • Keyframe Retter — takes the path of an existing keyframe animation and builds pivot and lens splines from it.
Setup Builder

Rigs from curves

Builds complete camera rigs from curves: pivot, lens and roll empties, follow-path constraints set automatically, vmax configurable per track.

Engine & live control

Drive the engine from Blender

Start/stop, auto-export on changes, connection test (ping/pong), status monitoring. Play, pause and reset with manual pedal control and real-time feedback from the engine.

Recorder

240 Hz recording

Runs in a separate process with deterministic storage, sample counter and status display.

Render export

Frame-accurate output

Quaternion-based camera control with roll (no gimbal lock), multi-rig support, output manager for PNG, EXR and WebP, time-stretch rendering from 0.1× to 10×.

Settings

Sampling & export

Sampling rates, keyframe decimation tolerance, control points per spline, export defaults and the time-stretch factor.

Blender viewport with Walk/Fly-recorded pivot and lens paths and the TSDE Live Host panel
Blender: pivot and lens paths recorded in Walk/Fly mode, TSDE Live Host panel on the right.
Blender Live Control: engine connected, pedals for pivot, lens and roll
Live Control in Blender: engine connected, pedals for pivot, lens and roll, camera view.

Blender host panels

Blender panel: Spline Generator with Walk/Fly mode, Spline Setter and Keyframe Retter
Blender panel: Setup Builder with pivot and lens track, max speed, camera and roll system
Blender panel: Engine Control with rig selection, engine start and connection status

Spline Generator · Setup Builder · Engine Control.

06Download

Get the TSDE Project

Version 0.9 Beta. Because the time axis of a recording is kept unnormalised, one recording can be re-sampled into different outputs — including slow motion and time-lapse — without re-recording.

07Technical questions · Motion

Engineering FAQ — Motion Synthesis

What is velocity-driven motion synthesis?

Motion is defined by a path and a velocity function over time. Position is not specified directly; it follows from integrating velocity to an accumulated distance s(t) and mapping that distance onto the path by arc length. In TSDE each track has its own velocity curve, driven by a pedal value scaled to the track's v_max in mm/s.

How does motion sampling differ from position-keyframe interpolation?

With keyframes, positions are assigned to specific times and intermediate positions come from interpolation curves; the timing of the movement emerges from those curves. With motion sampling, a continuous motion description exists first and output frames read it at chosen times — changing the frame rate changes the sampling density, not the motion. Keyframing remains the industry standard and offers direct pose control; the two approaches suit different tasks.

Why separate path geometry from velocity?

Timing can be edited without touching geometry, and geometry without disturbing timing. Velocity can be expressed in physical units, playback can be stretched (TSDE: 0.1× to 10×) from a single recording, and the path can be refined without changing how fast the motion progresses along it.

Why does curvature matter for camera motion?

At speed v on a path of curvature κ, the lateral acceleration is v²·κ. Tight curves at high speed therefore read as abrupt; abrupt curvature changes read as jerks. Controlling velocity separately from the path lets the speed be reduced where the path bends, without editing the path itself.

Line 4TSDE TimeOSImplemented · private test

Time is the interface.

TSDE TimeOS is an operating system in the browser in which nothing is ever overwritten. Every keystroke, every window, every song is an event on one shared timeline — and any earlier moment can be restored exactly: viewed, played back, or continued from.

01Principle

Events. Fold. Time.

One log

There is exactly one source of truth: an append-only event log. Every event carries its tick k on a 120 Hz grid of absolute UTC time — the same tick on every device.

One fold

The state of every app is a pure function of the log up to time t. What is on screen is never stored; it is recomputed from the events — the present moment when live, any earlier one while scrubbing.

Fixed rules

Each event is evaluated with the rule version that was in force at its tick. Shipped rules never change. That is why a recording made today will look exactly the same years from now.

We do not store states.
We store what happened.
TSDE
Motion→Sampling→Frames
TimeOS
Events→Fold→Screen

The same idea as in line 3, one level up: there, motion is described continuously and only sampled into frames for output. In TimeOS, the history is the description — and the screen is merely its sample at time t.

The picture behind it is a cam drum: the motor is TSDE time, the cams are the tracks — pointer, touch, keyboard, windows, apps. Each cam emits time-stamped events.

What does not follow from the log

  • Clock, randomness, network and files enter the event as a finished result — the fold itself knows no clock and no randomness.
  • Media are not recorded as pictures: playback is an anchor (position, time, rate). The position at time t follows from it.
  • Whatever cannot be reconstructed — third-party ads, a stream that is no longer reachable — is marked as such instead of guessed.
02Try it

Pull on time.

Twelve seconds of history, 39 events. The screen on the left is folded anew from the log at every position of the slider — exactly how TimeOS works, only with millions of events.

One log, every moment

Explanatory illustration
O·C·E·A·NLIVE

    Playhead (scrub)

    Playback

    Tick k: 1440 folded: – State: –
    Browser illustration of the principle, not TimeOS itself: state(k) = fold(apply, ∅, log[0 … k]) at 120 ticks per second. The same tick always yields the same state — visible as the same check value.
    03Experience

    An operating system with a rewind button.

    Timeline

    Scrub through your day

    The timeline sits at the bottom: sessions as light, pauses as a narrow seam. Drag to scrub, two fingers to zoom — from months down to a quarter of a second.

    Record from here

    Continue from earlier

    Last night's version of a text was better? Rewind, “record from here” — and carry on from exactly that state.

    The whole picture

    As it was

    Replay shows more than content: windows, columns, the main menu, the tile layout and the app that was tapped are exactly where they were.

    Markers & calendar

    Finding time again

    Flags with a note mark moments; the calendar shades each day by recorded time. One tap jumps right there.

    Ctrl+Z

    Undo is a jump in time

    System-wide, Ctrl+Z jumps back by one step — in every app, including embedded web apps. Nothing is swallowed silently.

    One rule set

    Phone, tablet, desktop

    One window manager for all devices: the log stores the logical place (“column 2 of 3”), never pixels. Each device draws it its own way.

    TSDE TimeOS on desktop: tile wall with live tiles, the time deck with timeline and transport at the bottom
    Desktop home: tiles, live tiles and the time deck with REC and LIVE.
    TSDE TimeOS on a tablet: Writer in the left column, the Planetarium takes two thirds, timeline below
    Tablet column grid: creative apps such as the Planetarium take two thirds; the Writer moves to the side.
    TSDE TimeOS on a phone: Writer with the system handbook, the time deck below
    On the phone: one app at a time — here the Writer with the system's own handbook.
    04Apps17 apps

    What time does to an app

    Every app follows the same rules — and gains abilities it could never have on its own.

    AppWhat time adds
    WriterWatch any text being written. Open and save DOCX, export PDF — own code, no third-party library.
    MusicWeb radio with a ring buffer: time-shifted listening, catch up to live, lift a song from the ring into the collection with ♥.
    Flow VideoPlayback as an anchor instead of a recording. From the ♥ favourites in Music it finds matching official clips: music TV from your own collection.
    TVThe broadcaster's buffer is the ring — time-shifted viewing costs no storage; replay shows the picture of the time that was on air.
    RetroAn N64 emulator on the timeline: inputs per frame in the log, replay recomputes bit-exactly. Rewind, take another path.
    PlanetariumThe solar system as a function of time, with the egg helix as orbit shape; the camera is computed in closed form so every replay is identical frame by frame.
    FlowCellA foreign web app under virtual time: clock, timers, randomness and frames come from the system — at every time mark the pixels match.
    05Privacy

    Everything belongs to you.

    A system that remembers everything must belong to no one else. So from day one:

    Implemented

    Offline

    TimeOS runs entirely on the device. Not a single request leaves it at start-up — even the fonts ship with it.

    Implemented

    No account

    No sign-up, no analytics, no ads, no telemetry. The only things that go out are what you tap yourself: a radio station, a video.

    Implemented

    Media stay where they are

    Music and videos stay on the device, the NAS or your own cloud. If a file is missing, TimeOS tells you which device has it.

    Planned

    Sync without identity

    One history on every device: only the log, encrypted on the device, accessed with an anonymous twelve-word key. The server sees nothing but unreadable blocks.

    06StatusVersion 0.14.51 · October 2026

    Measured, tested, in daily use

    Core
    120 Hzshared tick
    4096events per block, gzip
    ≈ 2 sto verify 1 million events

    Closed blocks are immutable and carry the state before them. Start-up therefore takes the same time however long the history is; old blocks load only when you jump there.

    Quality
    111automated checks
    60–110 msjump in time
    replay = livecontinuous hash check

    Every ten seconds the open tail is folded again; the check value must match the live state. Device tests on iPhone, Android phone and tablet; in private testing with family and friends.

    Technical notes for researchers

    Time and state

    k(t) = ⌊ t · 120 ⌋ t in UTC seconds S(t) = fold(apply_r, S₀, log[0 … k(t)]) apply_r = rule version in force at the event's tick block b: S_b+1 = fold(apply, S_b, E_b), hash(S_b+1) stored medium: pos(t) = pos₀ + (t − t₀) · rate − gap(t₀, t)

    gap is the time skipped between two moments (pauses, replay before “record from here”) — it does not count as playback.

    Rules for every app

    • apply is a pure function: no clock, no randomness, no DOM, no network.
    • Ids are created when writing and stored in the event; unknown events change nothing.
    • Writing happens only live; the view only reads.
    • Password fields and private areas are never recorded — hard-wired, not an option.

    Next steps Planned

    Installable without a store with offline storage, sync without an account, branches instead of deletion when re-recording, an app shell for Android, a kiosk mode for Raspberry Pi and machine control.

    07Questions

    FAQ — TSDE TimeOS

    What is TSDE TimeOS?

    An operating system in the browser by Benjamin Thorsten Unger (O·C·E·A·N) in which the entire state — windows, input, documents, media, games — is computed from a single event log. The timeline is the central control: any earlier moment can be restored exactly, played back, or taken as a new starting point.

    Does it record the screen?

    No. Only events are stored — a keystroke, a window in place 2, playback from second 41. The picture is recomputed every time by folding. That keeps the history small: a block of 4096 events compresses to roughly a twelfth.

    How is this different from undo, version control or event sourcing?

    Undo and version control work per program or per file. Event sourcing is the well-known pattern underneath. TimeOS puts the whole system on one shared 120 Hz timeline — window manager, input, media playback, emulator and embedded web apps — and makes time itself the interface: you scrub through your day like through a video.

    How does replay stay exact while the software evolves?

    Through rule versions. The log states which rules applied; each event is evaluated with the version active at its tick. A shipped version is never changed — new behaviour is always a new version.

    What about content from outside — radio, video, TV?

    It enters the log as a result, not as a picture: which station, which title, which position. Radio can be recorded into a ring on request; TV uses the broadcaster's own buffer. Whatever can no longer be loaded later is marked “not reconstructable” in replay.

    Can I use TimeOS?

    Not publicly yet. TimeOS is in private testing; a public, installable version is the next step. The principle stays: offline, no account, the data belongs to the user.

    ↑