1. Overview
Oracle is a multi-oscillator, multi-timeframe momentum analysis indicator for TradingView. It runs as a sub-panel oscillator (overlay=false), operating on a 0–100 scale with reference lines at 20, 50, and 80.
The indicator computes five distinct momentum oscillators — Chande Momentum Oscillator (CMO), Connors RSI (CRSI), Relative Strength Index (RSI), Stochastic, and Stochastic RSI (SRSI) — on each of four user-configurable timeframes simultaneously. Results from each oscillator can be displayed individually per timeframe, blended per-timeframe into Mash-Up composites, and further compressed across all timeframes into a single Crunch line.
A global source and per-oscillator source overrides give precise control over what price data each calculation uses. A two-mode bar-state switch lets you choose between real-time tick-by-tick rendering and confirmed-bar-only rendering.
Signals — divergence markers, reversal triangles, zone background colors — are available for each oscillator family and render both in the indicator panel and as overlays on the price chart.
1.1 Panel Layout
The indicator panel displays a 0–100 scale with four reference lines:
- 100 (Roof) — invisible boundary, 0% opacity
- 80 (Hi-End) — white dashed, 25% opacity — upper threshold zone
- 50 (Midline) — white dashed, 25% opacity — neutral centerline
- 20 (Lo-End) — white dashed, 25% opacity — lower threshold zone
- 0 (Floor) — invisible boundary, 0% opacity
All oscillator lines in Oracle are normalized or rescaled to sit within this 0–100 range. The Chande CMO, for example, natively produces –100 to +100 values; it is rescaled via (value+100)/2 before plotting so it sits cleanly between 0 and 100.
1.2 Compatibility
- Platform: TradingView (any plan supporting Pine Script indicators)
- Pine Script version: v6
- Display: Sub-panel oscillator (does not overlay on price chart)
- Precision: 2 decimal places
- Asset classes: All — Stocks, ETFs, Forex, Crypto, Futures, Indices, Commodities
2. Installation
2.1 Adding to Your Chart
- Open TradingView and navigate to any chart.
- Click the Indicators button (or press /).
- Search for “Oracle” and click the result.
- The indicator loads in a new sub-panel below the price chart.
- The settings panel opens automatically on first load — configure as needed (see Section 3).
2.2 Accessing Settings
- Hover over the Oracle II label in the indicator panel, then click the gear icon (⚙).
- Or double-click any plotted line in the indicator panel.
|
💡 Start Simple The indicator ships with almost everything toggled off. Begin by enabling just one or two oscillators on TF1 and TF2 to get a feel for the panel. Add complexity gradually. |
3. Settings Reference
Oracle settings are organized into the following groups: Global Settings, four Timeframe Settings groups (TF1–TF4), one settings group per oscillator (Chande, CRSI, RSI, Stochastic, Stoch RSI), Mash-Up, Crunch, and Auto-TF.
3.1 Global Settings
| Setting | Default | Options / Range | Description |
| Source (Global) | close | Any price source | The default price source used by all oscillators unless individually overridden. Changing this affects all oscillators simultaneously. |
| Plotting Bar-State | Real Time | Real Time / Confirmed | Real Time: all lines update on every tick. Confirmed: lines update only when a bar fully closes. Confirmed mode eliminates current-bar noise and is recommended for signal reading. |
3.2 Timeframe Settings (TF1 / TF2 / TF3 / TF4)
Each timeframe has four settings. TF1 is special — its timeframe is always locked to the chart period and cannot be changed.
| Setting | Default | Options / Range | Description |
| TF1 Cannot Be Changed | true | Locked | Informational toggle. TF1 always uses the current chart timeframe. The adjacent dropdown shows ‘Chart’ and cannot be modified. |
| Disable Auto-TF / Set TF2 To | false | true / false | When false (default), TF2 is assigned automatically by the Auto-TF system. When true, TF2 uses the adjacent manual timeframe dropdown. |
| TF2 Timeframe | 120 | Any TF | Only active when the override is enabled. Default manual value is 120 (2H). |
| Default Length | 12 (TF1–3) / 12 (TF4) | ≥1 | Global fallback length used by all oscillators on this TF when their individual length override is OFF. |
| Default Weight | 1.0 (TF1–3) / 0.0 (TF4) | 0–12, step 0.1 | How much this timeframe contributes to MTF composites and the Crunch. TF4 defaults to 0 — opt-in. Set to 0 to fully exclude a timeframe from all blended calculations. |
|
⚠️ TF4 Default Weight is Zero TF4’s Default Weight ships as 0. This means TF4 is excluded from all Mash-Up and Crunch calculations until you raise its weight above 0. This is intentional — TF4 is an opt-in higher-context layer. |
3.3 Chande Momentum Oscillator Settings
| Setting | Default | Options / Range | Description |
| Weight of CMO | 0.0 | 0–2, step 0.1 | Controls CMO’s contribution to Mash-Up and Crunch calculations. Default 0 means CMO is excluded from blended math unless you opt in by raising the weight. |
| Plot TF1/2/3/4 | false | On/Off | Enables the CMO line for that timeframe individually. Lines are color-coded by timeframe (see Section 7). |
| Plot MTF Composite | false | On/Off | Plots the weighted MTF Composite of CMO across all four timeframes. |
| Signal Composite Pivots (3–97) | false | On/Off | Enables triangle signals on the panel: bullish triangle when Chande Composite crosses above 10; bearish triangle when it crosses below 90. |
| Source Override | false | On/Off | When enabled, CMO uses its own independent source instead of the Global Source. |
| Source | close | Any source | Only active when Source Override is ON. |
| Override Global Lengths | true | On/Off | When ON, per-TF CMO lengths are used. When OFF, each TF uses its Global Default Length. |
| Length TF1/2/3/4 | 2 | ≥1 | Individual CMO calculation length per timeframe. Default 2 — very short, very reactive. Effective when CMO override is ON. |
3.4 Connors RSI Settings
Connors RSI has two internal length parameters: the RSI length and the Up/Down streak RSI length. Both are independently overrideable.
| Setting | Default | Options / Range | Description |
| Weight of CRSI | 0.0 | 0–2, step 0.1 | CRSI contribution to Mash-Up/Crunch. Default 0 — opt-in. |
| Plot TF1/2/3/4 | false | On/Off | Individual CRSI line per timeframe. |
| Plot MTF Composite | false | On/Off | Weighted MTF Composite of CRSI. |
| Signals (Zone) | false | On/Off | Background color: green when CRSI TF4 < 50 AND CRSI Composite < 50 (bullish zone); pink when both > 50 (bearish zone). Renders on price chart. |
| Signals (Point) | false | On/Off | Triangle signals: bullish when TF1 CRSI crosses above Composite while TF1 is rising and Composite[1] < 25. Bearish when TF1 crosses below Composite while falling and Composite[1] < 75. |
| Signals (Divergence) | false | On/Off | Circle markers on price chart: bullish divergence when close < close[1] but CRSI TF1 > CRSI TF1[1]; bearish when close > close[1] but CRSI TF1 < CRSI TF1[1]. |
| Source Override | false | On/Off | CRSI-specific source override. |
| Override Lengths (RSI) | true | On/Off | Uses per-TF CRSI RSI lengths when ON. |
| Length RSI TF1/2/3/4 | 3 | ≥1 | RSI sub-component length inside CRSI. |
| Override Lengths (▲/▼) | true | On/Off | Uses per-TF Up/Down streak lengths when ON. |
| Length ▲/▼ TF1/2/3/4 | 2 | ≥1 | Up/Down streak RSI length inside CRSI. |
3.5 Relative Strength Index Settings
| Setting | Default | Options / Range | Description |
| Weight of RSI | 0.0 | 0–2, step 0.1 | RSI contribution to Mash-Up/Crunch. Default 0 — opt-in. |
| Plot TF1/2/3/4 | false | On/Off | Individual RSI line per timeframe. |
| Plot MTF Composite | false | On/Off | Weighted MTF Composite of RSI. |
| Plot TF1/2/3/4 MA | false | On/Off | Overlays a moving average on the RSI line for that timeframe. Thinner line (linewidth=1) vs. RSI’s linewidth=2. |
| Plot Composite MA | false | On/Off | Moving average overlay on the MTF RSI Composite. |
| Signals (Zone) | false | On/Off | Background zone coloring based on RSI conditions. |
| Signals (Point) | false | On/Off | Triangle reversal markers from RSI crossover logic. |
| Signals (Divergence) | false | On/Off | Circle divergence markers: price vs. RSI TF1 direction disagreement. |
| Source Override | false | On/Off | RSI-specific source. |
| Override Lengths (RSI) | false | On/Off | When OFF, RSI uses Global Default Lengths. When ON, per-TF RSI lengths apply. |
| Length TF1/2/3/4 | 10 | ≥1 | RSI calculation length per TF when override is active. |
| RSI MA Type | EMA | SMA/EMA/RMA/WMA/VWMA | The type of moving average applied to each RSI line. One setting controls all timeframes. |
| Override Lengths (RSI MA) | true | On/Off | When ON, per-TF MA lengths apply. |
| Length MA TF1/2/3/4 | 21 | ≥1 | Moving average length for RSI MA per timeframe. |
3.6 Stochastic Settings (🟨 Stochastic)
|
📌 Source Note Stochastic always uses close/high/low from the price chart. Its source cannot be overridden — it is hardcoded to standard OHLC data. |
| Setting | Default | Options / Range | Description |
| Weight of Stoch | 1.0 | 0–2, step 0.1 | Stochastic contribution to Mash-Up/Crunch. Default weight is 1 — active by default in blended math. |
| Plot TF1/2/3/4 K | false | On/Off | Plots the %K line for that timeframe (thicker, linewidth=2). |
| Plot MTF Composite K | false | On/Off | Weighted MTF Composite of Stoch %K. |
| Plot TF1/2/3/4 D | false | On/Off | Plots the %D line (SMA of %K) for that timeframe (thinner, linewidth=1). |
| Plot MTF Composite D | false | On/Off | Weighted MTF Composite of Stoch %D. |
| Signals (Zone) | false | On/Off | Background zone color when Stoch K Composite > Stoch D Composite (bullish) or opposite (bearish). |
| Signals (Point) | false | On/Off | Triangle signals from K Composite crossing TF4 K with directional confirmation. |
| Signals (Divergence) | false | On/Off | Divergence circles: price vs. Stoch K TF1 direction disagreement. |
| Override Lengths | false | On/Off | When ON, per-TF %K lengths apply. When OFF, Global Default Lengths are used. |
| Length %K TF1/2/3/4 | 10 | ≥1 | Lookback period for the Stochastic %K calculation per timeframe. |
| %K Smoothing | 1 | ≥1 | SMA smoothing applied to raw %K. Default 1 = no smoothing. |
| %D Smoothing | 3 | ≥1 | SMA smoothing applied to %K to produce %D. Default 3 = standard Stochastic. |
3.7 Stochastic RSI Settings
Stoch RSI has two independent length parameters: the RSI length (how long an RSI is computed first) and the Stochastic length (how wide a window the Stochastic formula then applies to that RSI).
| Setting | Default | Options / Range | Description |
| Weight of SRSI | 1.0 | 0–2, step 0.1 | SRSI contribution to Mash-Up/Crunch. Default weight is 1 — active by default. |
| Plot TF1/2/3/4 K | false | On/Off | SRSI %K line per timeframe. |
| Plot MTF Composite K | false | On/Off | Weighted MTF Composite of SRSI %K. |
| Plot TF1/2/3/4 D | false | On/Off | SRSI %D line (SMA of %K) per timeframe. |
| Plot MTF Composite D | false | On/Off | Weighted MTF Composite of SRSI %D. |
| Signals (Zone) | false | On/Off | Background zone from SRSI K/D Composite relationship. |
| Signals (Point) | false | On/Off | Triangle signals: SRSI K Composite vs. Stoch K TF4 crossovers with momentum confirmation. |
| Signals (Divergence) | false | On/Off | Divergence circles: price vs. SRSI K TF1. |
| RSI Source Override | false | On/Off | When ON, SRSI uses its own source for the internal RSI step. |
| Override Lengths (RSI) | false | On/Off | Per-TF RSI length override for the internal RSI calculation. |
| RSI Length TF1/2/3/4 | 10 | ≥1 | RSI lookback for the first step of SRSI calculation. |
| Override Lengths (Stoch) | false | On/Off | Per-TF Stochastic length override for the Stoch step applied to RSI. |
| Stoch Length TF1/2/3/4 | 10 | ≥1 | Stochastic window applied to the RSI series. |
| %K Smoothing | 1 | ≥1 | SMA smoothing of SRSI %K. |
| %D Smoothing | 3 | ≥1 | SMA applied to %K to produce %D. |
3.8 Mash-Up Settings
| Setting | Default | Options / Range | Description |
| Plot Mash-Up TF1/2/3/4 | false | On/Off | Enables the Mash-Up composite line for that timeframe. The Mash-Up is the weighted average of all active (non-zero-weight) oscillators on that timeframe. |
| Smooth by | 1 | ≥1 | Applies an SMA of this length to the Mash-Up line before plotting. 1 = no smoothing. Increase to reduce noise. |
3.9 Crunch Settings
| Setting | Default | Options / Range | Description |
| Crunch | false | On/Off | Enables the Crunch line — the weighted average of all four Mash-Up lines, weighted by each TF’s Default Weight. |
| Smooth by | 1 | ≥1 | SMA smoothing applied to the Crunch before plotting. 1 = no smoothing. |
|
⚠️ Crunch Requires Active Mash-Ups The Crunch is computed from the Mash-Up lines. For Crunch to produce meaningful output, at least one oscillator must have a non-zero weight AND at least one TF weight must be non-zero. If all oscillator weights are 0, the Crunch will divide by zero and return na. |
3.10 Auto-TF Settings
The Auto-TF section defines the complete mapping of chart timeframe → TF2/TF3/TF4 assignments. Every row covers one TF1 scenario. For each TF1 value, you can choose from a curated list of sensible higher timeframes for TF2, TF3, and TF4.
These settings only apply when the respective TF Override (Disable Auto-TF) is OFF. When you manually override a TF, its Auto-TF row is ignored.
| TF1 (Chart) | Default TF2 | Default TF3 | Default TF4 |
| 5m | 15m | 30m | 1H |
| 15m | 30m | 1H | 90m |
| 30m | 1H | 90m | 2H |
| 1H | 2H | 3H | 4H |
| 2H | 4H | 6H | 8H |
| 3H | 6H | 12H | 1D |
| 4H | 8H | 12H | 1D |
| 6H | 12H | 1D | 2D |
| 12H | 1D | 2D | 3D |
| 1D | 2D | 3D | 5D |
| 3D | 5D | 1W | 2W |
4. Understanding the Five Oscillators
Each oscillator in Oracle measures momentum through a different mathematical lens. Understanding what each one is sensitive to helps you decide which to weight heavily and which to leave at zero.
4.1 Chande Momentum Oscillator (CMO)
The CMO was developed by Tushar Chande and measures the net momentum over a period by comparing the sum of upward price changes (MOM1) against the sum of downward price changes (MOM2). The formula is:
|
CMO Formula Raw CMO = 100 × (Sum(Gains, N) − Sum(Losses, N)) / (Sum(Gains, N) + Sum(Losses, N)) Raw range: −100 to +100 Oracle II rescales to 0–100: (Raw CMO + 100) / 2 Default length: 2 (very short, highly reactive) |
At its default length of 2, CMO is extremely sensitive — it reacts to individual bar momentum shifts almost instantly. This makes it useful for catching very early turns, but it produces many false signals on its own. It is best used as one input into the Mash-Up rather than as a standalone signal.
4.2 Connors RSI (CRSI)
Connors RSI was developed by Larry Connors and is a composite of three components averaged together:
- RSI Component: A standard short-period RSI of the source price.
- Up/Down Streak RSI: An RSI applied to a streak counter. The streak counter increments by +1 for each consecutive up bar, decrements by −1 for each consecutive down bar, and resets to 0 on equal bars. This captures trend persistence.
- Percent Rank: The 100-bar percent rank of the 1-bar Rate of Change — where does today’s single-bar move rank relative to the last 100 single-bar moves?
|
CRSI Formula CRSI = Average(RSI(close, RSI_Length), UpDownRSI(streak, UD_Length), PercentRank(ROC(1), 100)) Result is naturally 0–100. No rescaling needed. Default RSI length: 3, Default UD length: 2 |
CRSI is particularly useful for mean-reversion setups — it measures not just how far price has moved, but how persistent the trend has been and how unusual the move is in historical context.
4.3 Relative Strength Index (RSI)
The RSI needs little introduction. It computes the ratio of average gains to average losses over N bars and expresses it on a 0–100 scale using Wilder’s RMA smoothing (ta.rsi in Pine Script).
What makes Oracle’s RSI implementation distinctive is the configurable moving average overlay. Any of five MA types (SMA, EMA, RMA, WMA, VWMA) can be applied to the RSI line, turning it into a signal/trigger pair — standard RSI practice elevated with full type and length control per timeframe.
The RSI MTF Composite averages the RSI value across all four timeframes (weighted). When the Composite and TF1 diverge significantly, it indicates that the higher timeframe momentum context is disagreeing with short-term momentum — a frequently meaningful signal.
4.4 Stochastic (%K and %D)
The Stochastic oscillator measures where the current closing price sits within the high-low range of the last N bars:
|
Stochastic Formula Raw %K = 100 × (Close − Lowest Low N) / (Highest High N − Lowest Low N) Smoothed %K = SMA(Raw %K, K_Smooth) %D = SMA(Smoothed %K, D_Smooth) Default K length: 10, K smooth: 1, D smooth: 3 |
The Stochastic in Oracle always uses close, high, and low from the chart (source cannot be overridden for Stochastic — this is by design, as the high/low range is fundamental to the Stochastic calculation).
Both %K and %D are tracked separately, and both have their own MTF Composites. The relationship between the %K Composite and the %D Composite drives the Zone signal coloring.
4.5 Stochastic RSI (SRSI %K and %D)
Stoch RSI applies the Stochastic formula not to price, but to RSI values. The result is an oscillator that is faster and more extreme than either RSI or Stochastic alone:
|
SRSI Formula Step 1: RSI = ta.rsi(source, RSI_Length) Step 2: Raw SRSI_K = ta.stoch(RSI, RSI, RSI, Stoch_Length) — applied to RSI as high/low/close Step 3: Smoothed %K = SMA(Raw SRSI_K, K_Smooth) Step 4: %D = SMA(Smoothed %K, D_Smooth) |
Because it uses RSI as its own high, low, and close in the Stochastic formula, SRSI maps the Stochastic across the RSI’s own range. It hits overbought and oversold territory more often and more sharply than standard RSI or Stochastic, making it very useful for timing short-term entries and exits within a larger momentum context.
5. The Blend System: Mash-Up and Crunch
5.1 Weights
Every oscillator has a Weight (0–2) and every timeframe has a Weight (0–12). These two weight sets interact in a two-stage blending pipeline.
Oscillator weights control how much each oscillator contributes to the Mash-Up. TF weights control how much each timeframe’s Mash-Up contributes to the Crunch.
|
Weight Behavior Weight = 0 → oscillator/TF is fully excluded from all composite math Weight = 1 → normal contribution (the baseline) Weight = 2 → double contribution (counts twice as much) Fractional weights (e.g. 0.7, 1.3) are supported — step = 0.1 |
5.2 Mash-Up Calculation
For each timeframe, the Mash-Up is computed as:
|
Mash-Up Formula Total_Weight = Weight_CMO + Weight_CRSI + Weight_RSI + Weight_Stoch + Weight_SRSI Total_Value = (CMO × W_CMO) + (CRSI × W_CRSI) + (RSI × W_RSI) + (Stoch_K × W_Stoch) + (SRSI_K × W_SRSI) Mash-Up = SMA( Total_Value / Total_Weight, Smooth ) Note: TF-specific weights (Weight_TF1 etc.) are NOT applied at this stage — the Mash-Up uses only per-oscillator weights. |
The smoothing parameter (Smooth by) applies an SMA of that length to the raw Mash-Up result. At 1, no smoothing. At 3 or 5, the line is noticeably smoother and slower to respond.
5.3 Crunch Calculation
The Crunch blends all four Mash-Up lines using the per-timeframe weights:
|
Crunch Formula Crunch = SMA( (MashUp_TF1 × Weight_TF1 + MashUp_TF2 × Weight_TF2 + MashUp_TF3 × Weight_TF3 + MashUp_TF4 × Weight_TF4) / (Weight_TF1 + Weight_TF2 + Weight_TF3 + Weight_TF4), Smoothing_Crunch ) |
Since TF4’s default weight is 0, the Crunch defaults to a three-timeframe blend of TF1/TF2/TF3. Raise TF4’s weight to include it.
5.4 Practical Guidance for Weights
- If you only trust two oscillators (e.g., RSI and SRSI), set the others to 0 and set your two to 1. The Mash-Up becomes a pure 50/50 blend of those two.
- If you want TF1 to dominate the Crunch, give it a high TF weight (e.g., 3) and TF2/3 lower weights (e.g., 1).
- Doubling an oscillator’s weight (setting to 2) while others are at 1 makes it account for 2/(2+count) of the blend — roughly twice as influential.
- For a pure single-oscillator Mash-Up, set one oscillator to any non-zero weight and all others to 0. The Mash-Up becomes that oscillator’s MTF weighted average.
6. Signals Reference
All signals are disabled by default. Each oscillator family has up to three signal types: Zone, Point, and Divergence. Signals for the Chande oscillator are handled separately with a single Pivots toggle.
6.1 Chande Composite Pivot Signals
| Setting | Default | Options / Range | Description |
| Bullish Pivot | — | Auto | Green triangle (▲) at panel bottom when Chande MTF Composite crosses ABOVE 10. Indicates potential recovery from extreme oversold. |
| Bearish Pivot | — | Auto | Red triangle (▼) at panel top when Chande MTF Composite crosses BELOW 90. Indicates potential reversal from extreme overbought. |
|
📌 Threshold Note Thresholds are 10 (oversold) and 90 (overbought) on the 0–100 scale. These are extreme values by design — the signal fires only at strong extremes. |
6.2 CRSI Signals
Three independent modes, each toggleable separately:
| Mode | Visual | Condition |
| Zone | Background color | Green: CRSI TF4 < 50 AND CRSI Composite < 50. Pink: both > 50. Renders on price chart via force_overlay. |
| Point | Triangles on panel | Bull: TF1 CRSI crosses above Composite, TF1 CRSI rising, Composite[1] < 25. Bear: TF1 crosses below, TF1 falling, Composite[1] < 75. |
| Divergence | Circles on price chart | Bull div: close < close[1] AND CRSI TF1 > CRSI TF1[1]. Bear div: close > close[1] AND CRSI TF1 < CRSI TF1[1]. |
6.3 Stochastic Signals
| Mode | Visual | Condition |
| Zone | Background color | Green: Stoch K Composite > Stoch D Composite. Pink: Stoch D Composite < Stoch K Composite (note: both conditions are equivalent — K>D is bullish zone). |
| Point | Triangles on panel | Bull: K Composite crosses above TF4 K, K Composite rising, D Composite also rising. Bear: K Composite crosses below TF4 K, K Composite falling, D falling. |
| Divergence | Circles on price chart | Bull div: close < close[1] AND Stoch K TF1 > Stoch K TF1[1]. Bear div: close > close[1] AND Stoch K TF1 < Stoch K TF1[1]. |
6.4 Stoch RSI Signals
| Mode | Visual | Condition |
| Zone | Background color | Green: SRSI K Composite > SRSI D Composite. Pink: SRSI D < SRSI K (mirror of Stoch zone logic). |
| Point | Triangles on panel | Bull: SRSI K Composite crosses above Stoch K TF4 (cross-oscillator comparison), K Composite rising, D Composite also rising. Bear: opposite. |
| Divergence | Circles on price chart | Bull div: close < close[1] AND SRSI K TF1 > SRSI K TF1[1]. Bear div: close > close[1] AND SRSI K TF1 < SRSI K TF1[1]. |
7. Color Coding Reference
All plot lines in Oracle follow a consistent color system by timeframe. This lets you identify which timeframe any line belongs to at a glance, regardless of which oscillator it represents.
| Timeframe | Color | Hex Code | Line Weight |
| TF1 | Pale Cream/White | #EAE2B7 | 2 (K/primary), 1 (D/MA) |
| TF2 | Golden Yellow | #FCBF49 | 2 (K/primary), 1 (D/MA) |
| TF3 | Orange | #F77F00 | 2 (K/primary), 1 (D/MA) |
| TF4 | Deep Red | #D62828 | 2 (K/primary), 1 (D/MA) |
8. Recommended Setups
The following configurations are practical starting points. Adjust weights and lengths to suit your instrument and style.
8.1 Crunch-Only — Single Consensus Line
The simplest possible setup: one line that tells you where all your preferred oscillators agree across all timeframes.
- Enable only: Crunch
- Oscillator weights: Set Stoch=1, SRSI=1, RSI=1, CMO=0, CRSI=0 (or adjust to taste)
- TF weights: TF1=1, TF2=1, TF3=1, TF4=0 (or add TF4 at 0.5)
- Bar State: Confirmed
- Crunch Smooth: 1–3
- Use the 20/50/80 lines as oversold/neutral/overbought zones
8.2 Mash-Up Stack — All Four TFs Visible
Four lines, one per timeframe, each blending your chosen oscillators. Lets you watch how momentum propagates from lower to higher timeframes.
- Enable: Plot Mash-Up TF1, TF2, TF3, TF4
- Oscillator weights: customize (start with Stoch=1, SRSI=1, RSI=1, others=0)
- Read: TF4 (red) leads TF3 (orange) leads TF2 (gold) leads TF1 (cream) — when they align, momentum is synchronized
- Bar State: Real Time for intraday watching, Confirmed for analysis
8.3 Individual Oscillator Deep-Dive
Use Oracle as a per-oscillator multi-TF viewer for any single indicator.
- Example: SRSI deep-dive on 1H chart
- Enable: SRSI K TF1, TF2, TF3 — and their D lines
- Enable: SRSI K MTF Composite
- All other oscillators: weight=0, all plots off
- You now see SRSI simultaneously on the 1H, 2H, and 3H without switching timeframes
8.4 Signal Scanning Mode
For traders who want the indicator to actively call out setups.
- Enable Stoch RSI or CRSI Point Signals
- Enable Stoch or SRSI Divergence Signals (they render on price chart)
- Bar State: Confirmed — signals on unconfirmed bars frequently repaint
- Keep Mash-Up and Crunch running in background with weights active to give signal context
- A Point signal that fires while the Crunch is below 30 (oversold) is higher quality than one while Crunch is at 50
9. Frequently Asked Questions
The Crunch line is flat / not showing. Why?
The Crunch requires at least one oscillator with a non-zero weight AND at least one TF with a non-zero weight. Check that at least one oscillator Weight (in the oscillator settings groups) is above 0, and that TF1/TF2/TF3 weights (in the Timeframe Settings) are above 0.
The Mash-Up shows ‘na’ or is blank.
Same root cause as the Crunch — all oscillator weights are 0. Set at least one oscillator weight above 0. Stochastic (Weight=1) and Stoch RSI (Weight=1) are active by default.
I changed the chart timeframe but TF2/TF3/TF4 didn’t update.
Check whether you have manually overridden TF2/3/4 (the ‘Disable Auto-TF’ toggle is ON for those TFs). If the override is on, the TF is fixed regardless of your chart timeframe. Turn the override OFF to let Auto-TF manage the assignment.
Why does the indicator show two different values for ‘Confirmed’ vs ‘Real Time’?
In Real Time mode, the current (forming) bar’s oscillator values update on every tick. These values will change as the bar develops and often settle to a very different final value when the bar closes. In Confirmed mode, the current bar shows the previous confirmed bar’s value until the current bar closes. For signal reading and backreading, Confirmed mode is always more reliable.
Can I use Oracle on Heikin Ashi or Renko charts?
The oscillators use the source price series (default: close) and for Stochastic, high/low from the chart. On Heikin Ashi charts, the close, high, and low are modified values — results will differ from standard candlestick charts. For Renko, the lack of time-based bars makes the results unreliable. Standard candlestick charts are recommended.
What is the difference between the MTF Composite and the Mash-Up?
The MTF Composite is specific to a single oscillator — for example, ‘RSI MTF Composite’ averages the RSI value across TF1/2/3/4 using TF weights. The Mash-Up, by contrast, blends multiple oscillators together within a single timeframe. They operate on different axes: MTF Composites unify timeframes for one oscillator; Mash-Ups unify oscillators within one timeframe.
Why is TF4’s default weight 0?
TF4 is designed as an optional highest-context layer. Including a very high timeframe (e.g., 1H on a 5m chart) in the default blend can make the indicator feel sluggish and unresponsive to the timeframe you are actually trading. TF4 is opt-in: raise its weight when you specifically want macro context to anchor the blend.
Do the divergence signals repaint?
The divergence signals compare the current bar’s close to the previous bar’s close (close vs. close[1]) and the current bar’s oscillator value to the previous bar’s value. The current bar’s comparison can change on every tick in Real Time mode. Switch to Confirmed mode to ensure divergence signals only appear on fully closed bars, eliminating intra-bar repainting entirely.
10. Glossary
| Term | Definition |
| CMO | Chande Momentum Oscillator. Measures net momentum as a ratio of gains to total movement over N bars. Rescaled to 0–100 in Oracle. |
| CRSI | Connors RSI. A composite of a short RSI, an Up/Down streak RSI, and a Percent Rank of the 1-bar Rate of Change. |
| RSI | Relative Strength Index. Standard momentum oscillator measuring average gain vs. average loss over N bars using Wilder smoothing. |
| Stoch / %K / %D | Stochastic oscillator. %K = current close position within N-bar high/low range. %D = SMA of %K. Measures momentum exhaustion at range extremes. |
| SRSI | Stochastic RSI. The Stochastic formula applied to RSI values instead of price. More sensitive and extreme than either RSI or Stoch alone. |
| Mash-Up | The weighted average of all active (non-zero-weight) oscillators within a single timeframe. Produces one composite momentum line per TF. |
| Crunch | The weighted average of all four Mash-Up lines across timeframes. The single-line summary of the complete multi-oscillator, multi-timeframe momentum consensus. |
| TF Weight | Per-timeframe contribution factor used in MTF Composites and the Crunch. Set to 0 to exclude a TF from all blended calculations. |
| Oscillator Weight | Per-oscillator contribution factor used in the Mash-Up. Set to 0 to exclude an oscillator from all blended calculations. |
| Auto-TF | Automatic timeframe assignment system. Reads your current chart period and assigns TF2/3/4 from a user-configurable lookup table. |
| MTF Composite | Multi-Timeframe Composite. The weighted average of a single oscillator’s values across all four timeframes. |
| Confirmed Mode | Bar State setting that restricts plotting to confirmed (fully closed) bars only. Eliminates intra-bar noise and repainting of signals. |
| Real Time Mode | Bar State setting that plots on every tick, including the currently forming bar. Maximum responsiveness, some visual noise. |
| Up/Down Streak | The consecutive-bar direction counter used inside Connors RSI. Counts +1 for each up bar, −1 for each down bar, resets to 0 on equal bars. |
| Percent Rank | ta.percentrank in Pine Script. Returns what percentage of the last N values are below the current value. Used inside CRSI to measure the relative size of the current 1-bar price move. |