Orbit Poses to Orbit Lists JK🐉

The mirror image of the pack's other orbit converter, and the one you reach for when the wire is pointing the other way. OrbitPoses to OrbitLists JK takes camera data in "pose" format - [radius, elevation, azimuth, center X, center Y, center Z] - and reorders it into "track list" format - [azimuth, elevation, radius, center X, center Y, center Z]. Same six numbers, different order, no magic.

Why you'd need this specific direction

If you've got an orbit that was built or exported in camera-pose order - say, from the pack's Orbit Poses JK node's orbit_camposes output, or from a saved 3D viewer camera track - and the consumer wants the track-list order, this is the adapter that makes the connection. It's the less common direction than its sibling (OrbitLists to OrbitPoses), because most generators in the pack emit track-list format natively. You typically hit this when you've been handed a pose-format orbit from somewhere else and need to reshape it.

How it works

One input, orbit_camposes; one output, orbit_lists. The values pass through untouched, just reordered per position. The node's own docstring spells out both formats, so there's no ambiguity about what lands where - which is the entire point of a node like this: to make the format contract explicit instead of leaving it to memory.

The honest take

This is a narrow utility, and if you never touch the pack's 3D side, you'll never need it. When you do need it, it's because you're building custom camera tracks for img2mesh or multiview sampling, and format mismatches are one of those silent errors that produce subtly wrong results rather than a crash - the kind that wastes an hour. Sticking a converter node between two systems that disagree is a cheap, visible way to kill that whole class of bug.

Install

Same pack, same drill:

cd ComfyUI/custom_nodes
git clone https://github.com/jakechai/ComfyUI-JakeUpgrade
pip install -r requirements.txt

Restart and it sits in the pack's 3D section between its generator and its forward-converter siblings. Pure Python, no models, no dependencies beyond the pack's standard requirements. Gotcha to internalize: since the node only reorders, feeding it malformed data (wrong number of values, lists of different lengths) won't be corrected - it'll just pass the mess through or error. Validate your source orbit first.