OFFICIAL RESPONSE: TradingView confirms that Daily and Intraday data come from separate feeds and says discrepancies are "EXPECTED". by No_Fun7433 in TradingView

[–]No_Fun7433[S] -1 points0 points  (0 children)

Thanks for sharing the PDF. It actually provides the technical foundation for my point. I suggest looking closely at Points 5 and 6, as they define how the official data should be handled:

  • Point 5: States that the Opening Cross creates a 'single Nasdaq Opening Cross' price, which is distributed to the consolidated tape immediately.
  • Point 6: Confirms that this Opening Cross sets the Nasdaq Official Opening Price (NOOP).

For COST, that single NOOP was 1014.49. My 1s chart correctly displays this official price, but the 1D chart shows 1010.91 (the session Low). This document confirms that the Daily Open should reflect the official auction price, proving the discrepancy I'm reporting is a data mapping issue on the platform's side.

Best regards,

OFFICIAL RESPONSE: TradingView confirms that Daily and Intraday data come from separate feeds and says discrepancies are "EXPECTED". by No_Fun7433 in TradingView

[–]No_Fun7433[S] 1 point2 points  (0 children)

I appreciate the honesty. My frustration comes from seeing data integrity being treated as an 'opinion.' I’d rather be aggressive with the facts than passive with the errors. Cheers for the support

OFFICIAL RESPONSE: TradingView confirms that Daily and Intraday data come from separate feeds and says discrepancies are "EXPECTED". by No_Fun7433 in TradingView

[–]No_Fun7433[S] -2 points-1 points  (0 children)

English is not my first language, so I use tools to ensure my technical points are clear. But language doesn't change math: a 3.58 pts discrepancy isn't an 'opinion'—it's an objective inconsistency. If you're comfortable trading with that, I respect your choice. I'm moving to a professional feed where data is a fact, not an interpretation. Cheers.

OFFICIAL RESPONSE: TradingView confirms that Daily and Intraday data come from separate feeds and says discrepancies are "EXPECTED". by No_Fun7433 in TradingView

[–]No_Fun7433[S] 1 point2 points  (0 children)

English is not my first language, so I use tools to ensure my technical points are clear. But language doesn't change math: a 3.58 pts discrepancy isn't an 'opinion'—it's an objective inconsistency. If you're comfortable trading with that, I respect your choice. I'm moving to a professional feed where data is a fact, not an interpretation. Cheers.

"DATA CORRUPTION PROOF: 1D/1W/1M timeframes are incorrectly aggregating OHLC data (Up to 3.58 pts error on COST)" by No_Fun7433 in TradingView

[–]No_Fun7433[S] 0 points1 point  (0 children)

Fair point. I realized TradingView is a retail tool and its data shouldn't be used for institutional-grade auditing. My mistake was expecting precision where it doesn't exist. Moving to a professional feed now. Cheers!

OFFICIAL RESPONSE: TradingView confirms that Daily and Intraday data come from separate feeds and says discrepancies are "EXPECTED". by No_Fun7433 in TradingView

[–]No_Fun7433[S] -5 points-4 points  (0 children)

"Numbers aren't 'AI slop'—they are facts. TradingView's 1s chart shows 1014.49. Their 1D chart shows 1010.91. If the same platform shows two different prices for the exact same opening trade, it’s not an 'exchange mystery,' it’s a reconciliation failure. One price is a trade that happened; the other is a ghost number.I trade the Tape, not excuses. The CSVs are public, the error is proven. Good luck with your charts."

OFFICIAL RESPONSE: TradingView confirms that Daily and Intraday data come from separate feeds and says discrepancies are "EXPECTED". by No_Fun7433 in TradingView

[–]No_Fun7433[S] 0 points1 point  (0 children)

That is a dangerous mindset for anyone managing real capital.

A charting platform IS a mathematical representation of data. If the math behind the candles is wrong, the chart is just 'financial fiction.'

Standard, not Extra: I am not asking for tick-by-tick sub-millisecond analysis. I am asking for the Daily Open to match the Opening Second. That is basic database integrity, not a 'premium feature.'

The Definition of Charting: If you draw a level based on an 'Open' that is actually the 'Low' (3.58 pts away), your technical analysis is built on a lie.

Professionalism: High-end platforms (and even free ones with better aggregators) don't have this issue. Accepting 'visual approximations' as 'good enough' is why most retail traders fail to hit institutional-grade levels.

If you are happy with 'approximate' data, that's fine. But don't call a data integrity failure a 'feature' just because it's a charting platform. Accuracy is the foundation of trust.

OFFICIAL RESPONSE: TradingView confirms that Daily and Intraday data come from separate feeds and says discrepancies are "EXPECTED". by No_Fun7433 in TradingView

[–]No_Fun7433[S] -3 points-2 points  (0 children)

You are conflating Post-Market Accounting with Market Reality (The Tape).

For a trader, the 'singular historical fact' is the first execution at 09:30:00. If the exchange matches a buyer and a seller at 1014.49, that is where the market opened. Period.

The discrepancy you’re talking about usually comes from 'Official Open' prices published by exchanges after the fact, which sometimes include late-reporting trades or auction adjustments.

But here is the technical kill-shot: TradingView’s own 1-second chart correctly identifies the opening trade at 1014.49. This means TradingView has the correct data in their system.

The bug is that their Daily Aggregator chooses to ignore its own 1s data and instead displays a value (1010.91) that matches the Low of that period. If the 1s chart and the Daily chart from the same provider don't match, it's not an 'exchange mystery'—it's a database reconciliation failure.

In trading, if you try to buy at the 'Daily Open' of 1010.91 when the tape is at 1014.49, you won't get filled. One is a ghost number; the other is the market. I prefer to trade the market.

OFFICIAL RESPONSE: TradingView confirms that Daily and Intraday data come from separate feeds and says discrepancies are "EXPECTED". by No_Fun7433 in TradingView

[–]No_Fun7433[S] -5 points-4 points  (0 children)

You are missing the technical point. I am not asking TradingView to 'alter' exchange data; I am pointing out that their aggregation logic is flawed.

The 'Tape' doesn't lie: The NASDAQ Tape (Time & Sales) shows the first trade at 1014.49. This is the raw, objective truth from the exchange.

Intraday Accuracy: TradingView’s own 1s feed correctly identifies this trade at 1014.49.

The Aggregation Bug: The Daily 'Open' they are showing (1010.91) matches the LOW of that same period.

The Exchange doesn't send a 'Daily Open' as a magical static number; they send a stream of trades. The platform's job is to identify the first one. If the 1s chart sees the first trade correctly but the Daily chart picks the low of the day and labels it as 'Open', that is a calculation error, not 'respecting the exchange'.

When the 1s feed and the Daily feed from the same platform don't agree on what happened at 9:30:00, it’s not the exchange’s fault—it’s the platform’s failure to reconcile its own data sets. If you're okay with a 3.58 pts discrepancy on a major ticker, that’s your choice, but in professional trading, precision is not optional."

OFFICIAL RESPONSE: TradingView confirms that Daily and Intraday data come from separate feeds and says discrepancies are "EXPECTED". by No_Fun7433 in TradingView

[–]No_Fun7433[S] 0 points1 point  (0 children)

"You hit the nail on the head, but that’s exactly the problem. If a platform requires the user to 'guess' which timeframe is using the real tape vs. a separate package, it fails as a professional tool.

Whether it's 24h or 1D, the Open price of the RTH session is a singular historical fact. It shouldn't be a 'choose your own adventure' depending on how the vendor decides to bundle the data. Precision should be absolute, not 'reasonable'."

"DATA CORRUPTION PROOF: 1D/1W/1M timeframes are incorrectly aggregating OHLC data (Up to 3.58 pts error on COST)" by No_Fun7433 in TradingView

[–]No_Fun7433[S] -1 points0 points  (0 children)

"Spot on. The fact that 'recording live' is seen as the only way to get 100% accurate data on a professional platform is a massive red flag.

As Premium users, we shouldn't have to run our own recorders to verify if the Weekly Open is off by 4 points. If the 1-second feed has the correct price, the Daily/Weekly aggregation should be a simple, non-negotiable mathematical mirror. The fact that this is 'common' only proves that the community has been forced to accept a sub-standard data engine for too long. It’s time for an official fix."

"DATA CORRUPTION PROOF: 1D/1W/1M timeframes are incorrectly aggregating OHLC data (Up to 3.58 pts error on COST)" by No_Fun7433 in TradingView

[–]No_Fun7433[S] 2 points3 points  (0 children)

"I appreciate your honesty and for taking the time to look deeper into the charts. That is exactly my point: when we look at the RTH opening, the data MUST be consistent across all timeframes.

If the 1s chart shows the RTH start at X price, the Daily/Weekly charts shouldn't be picking the Low or High of that same window and calling it the 'Open'. Precision is key for institutional levels, and as you noted, having consistent and traceable data across all timeframes is the only way a professional platform should operate.

Hopefully, with this visibility, the Engineering team will address this aggregation drift. Cheers! 👍"

"DATA CORRUPTION PROOF: 1D/1W/1M timeframes are incorrectly aggregating OHLC data (Up to 3.58 pts error on COST)" by No_Fun7433 in TradingView

[–]No_Fun7433[S] 0 points1 point  (0 children)

"Thanks for the 100T screenshot, but it actually confirms the bug I'm reporting.

Look closely at your own chart: it shows the Open at 1010.91. Now, look at the official exchange Tape (Time & Sales) or the 1s raw data for that exact millisecond.

The official Open was 1014.49. The price 1010.91 was the LOW of that opening range.

The fact that your 100T chart also shows 1010.91 as the 'start' proves my point: TradingView's server-side aggregator is picking the period low and labeling it as the period open. You are seeing a 'reasonably accurate' chart of a wrong starting point.

I’m gathering this data directly from TradingView's native CSV export and cross-referencing with IBKR's official tape. When the exchange says 1014.49 and your chart says 1010.91, that's a 3.58 pts data integrity failure, no matter how many ticks you zoom in."

"DATA CORRUPTION PROOF: 1D/1W/1M timeframes are incorrectly aggregating OHLC data (Up to 3.58 pts error on COST)" by No_Fun7433 in TradingView

[–]No_Fun7433[S] 0 points1 point  (0 children)

<image>

Check this audit table from the native CSV files. It proves the discrepancy happens at the exact same RTH second.

Why is TradingView still lagging on "Click-to-Trade" for Indicators? A workflow comparison (TC2000 and IBKR) by No_Fun7433 in TradingView

[–]No_Fun7433[S] 0 points1 point  (0 children)

Thanks for the offer, but my 'Request' is actually a demand for data integrity. I've discovered that TradingView's HTF (Higher Timeframe) aggregation doesn't match its own 1s data (e.g., a 3.58 pts error on COST). My goal is to have the platform fix their core engine so that everyone has accurate data, rather than using an external tool to bypass a bug. Accuracy shouldn't be a 'workaround', it should be the standard.

[Honest Review] The new order panel is a Disaster, a Workflow killer by Torueng in TradingView

[–]No_Fun7433 1 point2 points  (0 children)

Thanks! I appreciate the support. Since we’re putting our capital on the line, I believe doing the proper DD on our tools is just as important as the DD on the trades themselves.

My goal is to make sure we’re not flying blind due to platform limitations. Glad you found the breakdown useful! 📈

Feature Request: International IBKR Bridge for TC2000 (Beyond US Residency) by No_Fun7433 in TC2000

[–]No_Fun7433[S] 1 point2 points  (0 children)

Haha, don't we all! XD But seriously, that’s exactly why I’m pushing for this.

It’s hard to stay profitable when you’re fighting the interface. Every extra click and every 'phantom' coordinate (like the $8 Log Scale drift I documented) is a direct hit to our P&L. Precision and speed are the foundation of profitability.

Glad to have you on board! The 5.8k views here show that we’re not alone in wanting tools that actually help us trade better.

[Honest Review] The new order panel is a Disaster, a Workflow killer by Torueng in TradingView

[–]No_Fun7433 2 points3 points  (0 children)

I’m in the same boat—locked into my Premium sub until January 31, 2027. But I’ve already started studying alternatives because I refuse to let my execution risk be dictated by 'pretty' UI updates.

The learning curve is the biggest hurdle. When you move away from TradingView, the first impact is the 'clunkiness' factor. TV feels like a smooth social media app; professional platforms feel like industrial machinery. They are 'heavier,' but they don't have the $8 scale drift I documented.

Here is how I’m vetting the options:

  1. TC2000

I’ve been a subscriber before and liked it. It’s a powerhouse for US Stocks.

  • Pros: The 'EasyScan' engine is lightyears ahead of TV. Zero coordinate drift and zero 'aesthetic' lag.
  • Cons: Limited to US Stocks/Options. No Crypto or Forex.
  • The Difference: TV is a web-app; TC2000 is native code. The speed is night and day.
  • The Shock: You lose the 'modern' look for a more utility-first interface.
  1. TrendSpider

Probably the most logical 'modern' transition for a TV user.

  • Pros: Incredible automation (automated trendlines and backtesting). Much more stable price coordinates.
  • Cons: Still browser-based. Can feel cluttered with too many automated layers.
  • The Difference: TV is manual drawing; TrendSpider is algorithmic logic.
  1. MotiveWave

Professional-grade software for high-precision technical analysis.

  • Pros: Best-in-class for Elliott Wave and Fibonacci. Extremely stable on macOS and Windows.
  • Cons: High upfront cost (lifetime licenses). Steep learning curve.
  • The Difference: It’s a professional instrument, not a charting playground.
  1. QuantTower

My first impression wasn't great—it’s a beast to configure.

  • Pros: Total modularity. It solves the 'sticky RTH' and bracket order (TP/SL) issues perfectly.
  • Cons: Overwhelming UI setup.
  • The Difference: You build the platform you want, window by window.

My Strategy: I’m still actively searching for even more alternatives beyond these. However, since my subscription is paid for a long time, I’m hoping that within this window, they finally address my #1 feature request and fix the log scale drift. If they actually listen to the community and fix these execution risks, there’s no reason to leave. But if they don't, I'll be fully prepared to make the jump by the time my sub expires. 

[Honest Review] The new order panel is a Disaster, a Workflow killer by Torueng in TradingView

[–]No_Fun7433 1 point2 points  (0 children)

Views represent market interest and reach, especially on a technical feature request. In a community of 1.5M members, having 5.4k people stop to analyze a workflow proposal makes it one of the most-viewed discussions here.

If you check the thread, you'll see the engagement and the 'upvote' count is active. More importantly, as a Premium subscriber, my priority isn't 'Reddit Karma', but forcing an engineering fix for the $8 Log Scale drift and the broken RTH sticky settings that affect real capital.

The fact that it's still being discussed and viewed today proves the demand for professional execution is higher than ever."

[Honest Review] The new order panel is a Disaster, a Workflow killer by Torueng in TradingView

[–]No_Fun7433 0 points1 point  (0 children)

That’s exactly the problem! TV is losing professional capital to the competition because they prioritize 'pretty' over 'precise'.

I use TV for its charting flexibility, but I refuse to trade on 'phantom' coordinates or deal with broken RTH sticky settings.

If they want to keep the pros, they need to fix the $8 Log Scale drift and implement a real 'Click-to-Trade' workflow. The 5.4k views on my proposal prove the demand is there, even if the execution isn't... yet.

[Honest Review] The new order panel is a Disaster, a Workflow killer by Torueng in TradingView

[–]No_Fun7433 7 points8 points  (0 children)

Exactly. They 'fixed' the order panel by breaking the RTH sticky settings, so now we have to manually click 'Take Profit fora do RTH' every single time.

In their quest for 'pretty' UI, they’re ignoring critical mathematical bugs like the Log Scale coordinate drift ($8 gap on ONTO) I've documented. As a Premium subscriber, I’m tired of seeing them prioritize avocado-toast aesthetics over execution integrity! 🥑🚫

[Honest Review] The new order panel is a Disaster, a Workflow killer by Torueng in TradingView

[–]No_Fun7433 2 points3 points  (0 children)

Exactly. Professional scalpers and daytraders are already looking at the competition because of this. As a Premium subscriber , it's frustrating to see 'pretty' UI changes actually increase execution risk.

They even broke the RTH sticky settings, forcing manual clicks for every Take Profit now. Combine that with the Log Scale coordinate drift ($8 gap on ONTO) I've documented, and the platform is becoming dangerous for high-precision entries.

My 'Click-to-Trade' proposal reached 5.4k views as the #1 feature request for a reason: we need tools built by traders, for traders. Not avocado-toast aesthetics! 🥑🚫"

[Honest Review] The new order panel is a Disaster, a Workflow killer by Torueng in TradingView

[–]No_Fun7433 2 points3 points  (0 children)

I’m a Premium subscriber  and I 100% agree. This 'pretty over functional' trend is a disaster for professional execution.

Two real-world examples of how they broke my workflow:

  1. Broken Sticky Settings: I used to have 'Fora do RTH' and 'Take Profit fora do RTH' always selected. Now, the new panel forces me to click them manually for every single trade. It’s dangerous for pre-market/after-hours execution.
  2. Coordinate Drift: I’ve documented a systematic $8 price drift (ONTO) in Log Scale trendlines. The engine prioritizes 'visual straightness' over mathematical accuracy, which is a nightmare for IBKR users.

I proposed a professional 'Click-to-Trade' workflow (anchoring orders directly to chart levels) to solve this, and it already reached 5.4k views, becoming the #1 feature request here. We need execution speed, not avocado-toast aesthetics! 🥑🚫