(deforum) Convert Normalized Amplitude

Somewhere in the Deforum Nodes audio section there are two different "amplitude" types: AMPLITUDE and NORMALIZED_AMPLITUDE. ComfyUI treats custom types as distinct sockets - a node expecting one won't accept a wire from the other, even when the data underneath is basically the same numbers. (deforum) Convert Normalized Amplitude exists to bridge that: it takes a NORMALIZED_AMPLITUDE in and hands back an AMPLITUDE out. That's it. It's a type adapter, the plumbing between two parts of the pack that happen to disagree on naming.

How it works

Straight up, it doesn't transform the data. The implementation returns the normalized amplitude series unchanged - the AMPLITUDE output is the same values that came in. The whole job is the type conversion: the node declares its output as AMPLITUDE, which tells ComfyUI's socket system "this wire is compatible with any node that takes an AMPLITUDE." If the pack ever changes the internal meaning of the two types, the node's a convenient single place to remap - but today, it's pure typing glue.

That's a very common pattern in big custom-node packs, by the way. When a pack grows a family of related data types, it ends up with little one-in-one-out nodes whose only purpose is to keep the graph wiring compatible as types evolve. ConvertNormalizedAmplitude is exactly that: nothing clever, occasionally essential.

The inputs and outputs

• normalized_amp - required NORMALIZED_AMPLITUDE input. If you're staring at a node whose output won't connect to the schedule mapper you want, check its socket type - if it says NORMALIZED_AMPLITUDE, this is your bridge.
• amplitude - the single output, an AMPLITUDE series with the same values.

When you actually need it

Honestly, this is a "when you hit the wall" node rather than a daily driver. You'll reach for it in one specific situation: you've built a chain (probably coming from a normalization-style node elsewhere in the pack) that outputs NORMALIZED_AMPLITUDE, and you want to feed it into something that only accepts AMPLITUDE - a TimeSmoothing, an Amplitude to Schedule, a comparator. Without the adapter, ComfyUI just refuses the connection. If nothing in your workflow ever produces a NORMALIZED_AMPLITUDE, you'll never need this node, and that's fine. It's insurance, not a feature.

Installing it

Part of Deforum Nodes (XmYx). Via ComfyUI Manager ("Deforum Nodes") or:

cd ComfyUI/custom_nodes
git clone https://github.com/XmYx/deforum-comfy-nodes.git

Restart ComfyUI; first boot runs install.py and pulls the heavy deps (librosa, opencv-contrib-python, moviepy, numpy<2.0.0, deforum-studio backend). Python 3.10 per the README.

Where people get burned

There's no real failure mode here because there's no real computation - the only way to trip up is to not use it and then wonder why a wire snaps. When you see a red connection refusal between two audio nodes, before you go looking for a math problem, check whether you're mixing AMPLITUDE and NORMALIZED_AMPLITUDE sockets and drop this node in between. Nine times out of ten that's the fix, and it costs one node in the graph.