LTXV Temporal Envelope Inspector (v1.3.0)

The expensive thing in LTX 2.3 work isn't the node - it's finding out your schedule was wrong after a ten-minute render. The Temporal Envelope Inspector is this pack's answer to that: a non-destructive audit node that resolves your video timeline and computes the exact strength envelope a Time-Gated LoRA would apply, without loading a LoRA or patching the model.

It ships in the same Jinx138 pack as the LTXV Time-Gated LoRA (LTX 2.3) and the CPU curve preview, and it's the middle of a three-node diagnostic chain: plan the envelope, inspect it, preview the plot, then commit to the real render. The core idea is that a timeline costs almost nothing to compute, so you verify before you spend.

How it works

Feed it the final video-only video_latent and it resolves the real rendered frame count - LTX 2.3's temporal compression is fixed at 8, so the node derives the timeline from the latent's temporal dimension - then builds the envelope your settings describe. Crucially, it uses the same timing engine as the productive node, so what it reports is what the Time-Gated LoRA will actually do. That engine match is the whole reason it exists.

Inputs and outputs

Inputs mirror the main node: envelope_mode (transition_frames, v1.1_local, or v1.1_hold_strength), effect_region for the active interval, strength_before / strength_during / strength_after, ramp_mode and ramp_q for the transition shape, and transition_frames for the legacy crossfade mode. outside_strength is the one extra - only used in v1.1_local mode, it sets the level in the timeline outside the immediate before/active/after envelope. None of it touches your model.

Outputs: video_latent (passed through unchanged, so you can drop the Inspector inline without rerouting anything), report_md (human-readable), report_json (for automation), profile_plot (an IMAGE of the frame vs latent profile), and data - the same LTXV_ENVELOPE_DATA payload the CPU curve preview consumes. The README's recommended wiring:

video_latent
  -> LTXV Temporal Envelope Inspector
       data      -> LTXV Envelope Curve Preview (CPU) -> Preview Image
       report_md -> Show Text / PreviewAny

You get both the numbers and the picture, then you either remove the Inspector before the real run or leave it inline - it's harmless either way.

When it's actually worth it

Three cases. One: you're hand-planning segments (the manual_frames style of scheduling) and want exact region boundaries in rendered frames rather than percentages. Two: you've stacked multiple gated LoRAs and want to confirm their regions don't accidentally overlap or leave a gap. Three: you suspect the latent feeding the main node is wrong - the Inspector makes the mismatch visible immediately, which beats debugging it after a failed sample.

Install and caveats

Install is shared with the pack, and it's the easy kind: no dependencies, no model files, just the clone.

cd ComfyUI/custom_nodes
git clone https://github.com/Jinx138/ComfyUI-LTXV-TimeGated-LoRA

Restart and look under LTXV/Diagnostics (or ComfyUI Manager → "LTXV Time-Gated LoRA").

Caveats, because this is a young pack - first public node release, no community threads about it. The class name says v1.1, and the repo has moved on since: newer builds split the q-curve into separate in/out controls and add a much bigger Temporal Director workflow. The comfy.icu page reflects the v1.1 schema, so if your widgets look slightly different after an update, that's version drift, not you. And remember the Inspector reports the envelope you configured, not whether that envelope is a good idea - a perfectly resolved schedule can still flicker if the LoRA is a stochastic detail type like rain or grain. Use it to catch timing mistakes, not to predict quality.