FAQ

Quick answers to the questions that come up most often. Each answer points to the relevant page if you want the full treatment.

Written By Axiom Admin

Last updated About 1 month ago

FAQ

Quick answers to the questions that come up most often. Each answer points to the relevant page if you want the full treatment.


Why doesn't this look like a normal MACD?

Because it is not a normal MACD. The raw MACD values are divided by ATR (to make them volatility-relative), then compressed into a bounded -100 to +100 range using a soft-clamp function. This is what makes it possible to compare readings across different timeframes and different instruments on the same scale.

If you compare the same source and timeframe with On Bar Close = OFF, the regime direction and zero-line structure should agree closely with a standard MACD using the same parameters. The absolute values will always differ because the scales are fundamentally different. If On Bar Close = ON on a same-timeframe slot, that slot is intentionally one confirmed bar behind.

Full explanation: For the Geeks


What is the best ATR Sensitivity setting?

There is no universal best. ATR Sensitivity controls how much of the -100 to +100 range the oscillator uses. Higher sensitivity means the oscillator saturates faster β€” readings spend more time near the bounds. Lower sensitivity means the oscillator stays closer to zero β€” readings rarely reach the OB/OS thresholds.

The right setting depends on how you use the oscillator:

  • If you rely on the OB/OS levels for attention, calibrate sensitivity so those levels are reached regularly but not constantly.

  • If you primarily watch the regime state (K above or below D), sensitivity matters less because the regime flip does not depend strongly on the absolute level.

  • If you want maximum mid-range resolution, lower sensitivity. If you want to see extreme readings earlier, raise it.

Start with the default of 1.0 and adjust based on what the oscillator looks like on your instrument and timeframe.

Full explanation: Settings β€” ATR Sensitivity | For the Geeks


Can I use this as a buy/sell signal?

No. The oscillator reads momentum state. It does not generate trade decisions.

A bullish blended reading means the weighted consensus favors upside momentum right now. It does not mean you should buy. A regime flip means the consensus shifted β€” not that the shift will hold, not that price will follow, and not that the timeframes driving the flip are the ones that matter most. An alignment alert means all slots agree on regime direction. It does not tell you how strong the agreement is, how long it will last, or whether the timeframes involved are genuinely distinct.

The tool measures. You decide. That division of labor is not a limitation β€” it is what keeps the tool honest. An oscillator that tells you when to trade is an oscillator that hides the assumptions behind that recommendation. This one shows you what momentum looks like and leaves the judgment where it belongs.

Full context: Limitations and Trust Boundaries


Why does my reading change after the bar closes?

You have On Bar Close set to OFF on one or more slots. When On Bar Close is off, the slot uses the current developing higher-timeframe bar's data, which updates intrabar. When that bar finally closes, the reading snaps to its confirmed value. The chart then shows only the confirmed value β€” the intrabar readings are gone.

This is not a bug. It is the designed behavior of unconfirmed data mode. If you want readings that do not change retroactively, set On Bar Close to ON for the relevant slots.

Full explanation: MTF and Repainting


What happens if I set all slots to the same timeframe?

They will produce identical readings if they also share the same source, ticker, MA settings, advanced parameters, and On Bar Close mode. Their K lines will overlap perfectly. The blend will equal any one of them.

This is not an error β€” it is the expected result of identical inputs. If you want different readings from different slots, at least one meaningful parameter must differ: the timeframe, the ticker, the MA type, or the lengths.

Multiple slots at the same timeframe can be useful if they differ in other ways β€” for example, the same timeframe with EMA versus KAMA, or the same timeframe on different instruments. But slots that share all parameters add redundancy, not perspective.


Why is the blended line flat near zero when individual slots are moving?

The blend is a weighted average. If some slots are strongly positive and others are strongly negative, they can average to near zero. The blend looks calm. The individual slots show active disagreement.

This is one of the most important things to understand about the blended reading. A blend near zero does not always mean neutral momentum. It can mean genuine neutrality (all slots near zero) or masked conflict (slots spread across the range, canceling in the average).

To tell the difference, check the individual slot lines. If they are clustered near zero, the blend is accurately reflecting neutral conditions. If they are spread across the range, the blend is hiding a disagreement.

Full explanation: Visuals and Logic β€” Mental model 3 | Limitations and Trust Boundaries


Does the Optional Ticker feature make readings comparable across markets?

Partially. The ATR normalization makes each instrument's reading self-relative β€” "how strong is this instrument's momentum relative to its own recent volatility." In that specific sense, a +60 on BTC and a +60 on SPY describe similar relative momentum intensity.

But "similar relative momentum intensity" does not mean the same price move, the same dollar impact, or the same quality of signal. BTC's volatility shifts faster than SPY's. The normalization is noisier on more volatile instruments. And the market context behind each reading (hours, liquidity profile, driving events) may be completely different.

Use cross-ticker readings to detect divergence between instruments rather than to assume equivalence between them. Divergence is where the feature earns its keep.

Full explanation: Multi-Ticker Mixing


Should I use Master Smoothing?

Only if you have a specific reason. Master Smoothing applies a post-blend moving average that reduces noise in the blended K/D/Histogram at the cost of lag. The K/D crossover happens later. Minor whipsaws are filtered out.

This is useful if you treat the blended regime as a slow-moving context indicator and use the individual slot lines for timing. It is counterproductive if you use the blended K/D crossover for timing decisions, because the smoothing makes the crossover late.

The default is off. If you are not sure whether you need it, you probably do not.

Full explanation: Settings β€” Master Smoothing | Workflows β€” Pattern 5


How is this different from the Lite version?

This Pro version provides:

  • Ten slots instead of three β€” more timeframe and cross-ticker coverage

  • Per-slot On Bar Close β€” each slot independently controls its own repaint behavior

  • Per-slot Hide Plot β€” you can include a slot in the blend without drawing its K line

  • Master Smoothing β€” an optional post-blend filtering pass

  • 31 alert conditions across four categories (per-slot, blended, histogram, alignment)

The core mechanics here are ATR-normalized MACD with weighted blending. This Pro version is the one for traders who need more slots, more configuration flexibility, and per-slot safety control. If you want the exact Lite feature map, check that indicator's own manual rather than assuming parity from this page.


Why do some slots' K lines barely move while others are very active?

Because each slot tracks a different timeframe. A slot at 1H on a 1-minute chart updates its reading once per hour. Between updates (with On Bar Close ON), the line holds steady. A slot at 5m updates every five minutes, and a slot at the chart timeframe updates every bar.

The slower-moving lines are not broken or lagging in a bad way. They are correctly reflecting the pace of their timeframe. A 1H slot that barely moves on a 1-minute chart is showing you that hourly momentum has not changed β€” which is itself useful information.


I changed the weights but the blend barely moved. Why?

Two possible reasons:

  1. The weight change was small relative to the total. If you have three slots at weight 33.3 each and you change one to 40, the effective change is modest. The slot went from 33% of the blend to 36%. To see a large effect, the weight ratio needs to shift substantially.

  1. The slots produce similar values. If all contributing slots are at similar readings (+45, +50, +48), changing the weights does not move the blend much because it is averaging values that are already close together. Weights have the most visible impact when the slots disagree.

Full explanation: Settings β€” The Weight System


Can I set up alerts for individual slot regime flips?

Not directly. The per-slot alerts are state alerts β€” they fire on every bar where the condition holds, not just on transitions. There is no built-in per-slot "regime flip" edge alert in this script.

TradingView frequency settings can reduce notification noise, but they do not turn a per-slot state alert into a true re-arming flip alert. For edge-based transition alerts on the composite level, use the blended alerts: "Blended MACD Regime Flip" fires once when the weighted consensus flips. If you need per-slot edge detection, watching the individual slot colors on the chart during live trading is currently the most reliable approach.

Full reference: Alerts