⏱️ Convertisseur de Temps
For when your workflow needs Planck time
- result
- output_str
There's a moment in every ComfyUI power user's arc where they think: "I need seconds, but this value is in hours, and I'm not doing that arithmetic by hand again." ⏱️ Convertisseur de Temps is the CalculatorPro node for that moment - and also for the far stranger moment where you need to convert something into Planck time, because the author included it and now it's an option.
The units
from_unit and to_unit each offer 15 choices, and the range tells you exactly what kind of pack this is. The practical set: second, millisecond, microsecond, nanosecond, picosecond, minute, hour, day, week. Then it gets opinionated:
- Mois (30.44j) - a month is defined as 30.44 days.
- Année (365.24j) - a year is defined as 365.24 days (the tropical year), not the 365.25 Julian year the node also lists separately.
- Décennie and Siècle are there too, scaled from that 365.24-day year.
- Temps de Planck (tₚ) - the Planck time, 5.391×10⁻⁴⁴ seconds. It's real physics, it's in the dropdown, and you'll probably only touch it to show off.
Same mechanism as the rest of the suite: every unit is a fixed factor relative to the second, value (FLOAT) normalizes to seconds, then divides by the target's factor. Nothing live, nothing fetched - it's a lookup table of constants.
When you'd use it
Honestly, the same way you'd use any of the converters: when a time value is an input to your workflow and you want it in a different unit downstream without recomputing. If you're driving a video workflow with frame timings or a prompt that says "a 2-hour flight" while your source value is in minutes, wire value from a widget, convert to the unit you need, and send either result (FLOAT, the bare number) or output_str (STRING, the formatted line like 2 h = 7200 s) wherever it needs to go. The string output is your dynamic-prompt friend; the float is for chained math.
The gotchas worth knowing
The two "year" definitions are the trap - "Année (365.24j)" and "Année julienne (365.25j)" are off by ~0.003%, which for most purposes is nothing, but they're separate entries precisely because they're not the same constant. If you convert a decade and then multiply by 10 you'll get a slightly different number than converting a century directly, which is a fun thing to discover in a test workflow. And the dropdowns are French, per the pack's usual - "Mois (30.44j)" reads like a label from a French calendar app, which it basically is.
Install
It's the last of the eight nodes in the CalculatorPro suite, and it ships with the same trivial install:
cd ComfyUI/custom_nodes
git clone https://github.com/orion4d/Calculator_Pro
restart ComfyUI, or search "Calculator_Pro" in ComfyUI Manager. No requirements.txt, no models, no network - a single pure-Python file that can't conflict with anything else in your environment. In a custom-node ecosystem where installs are usually the hard part, this pack being dependency-free is its quiet superpower.
Inputs (3)
| Name | Type | Default | Description |
|---|---|---|---|
| value | FLOAT | 1.00 | — |
| from_unit | COMBO | 15 options: Seconde (s), Milliseconde (ms), Microseconde (µs), Nanoseconde (ns), Picoseconde (ps), Temps de Planck (tₚ), +9 | |
| to_unit | COMBO | 15 options: Seconde (s), Milliseconde (ms), Microseconde (µs), Nanoseconde (ns), Picoseconde (ps), Temps de Planck (tₚ), +9 |
Outputs (2)
| Name | Type | Description |
|---|---|---|
| result | FLOAT | — |
| output_str | STRING | — |