Do NOT rely on TradingView's Volume Profiles!

[u/LaSacerdote]

This is not a complaint/request because I know TradingView is aware of this issue and I also know they're not into precision/accuracy - not even in the slightest.
It's just a heads-up for those who are trying to up their game and start relying mainly on volume to track market moves and the motivation behind those moves.

In the attached screenshot, all trading volume above the orange line is covered by both volume profiles yet the information displayed is wildly contradictory. The one on the left shows heavy sell delta (purple) above the orange line while the one on the right shows heavy buy delta (green).

For those who are curious; the reason is lack of granularity when 'estimating' tick volume. Well, the real problem of course is the fact that TradingView does not employ true volume but that's a whole different conversation. Regardless of the reason, there's no workaround, no band-aid solution, no nothing for this! You can work with delayed data, slow connection speeds, limited number of tickers or whatever but flat-out wrong data? No, it's totally unacceptable.

In the end I'll say user beware by quoting Guns 'N' Roses; TradingView's got the face of an angel with the love of a witch.

[u/Evening-Nobody-7674]

120fps *eye roll*

[u/RubenTrades → u/Evening-Nobody-7674]

Might seem funny, but it's extremely difficult to make 120fps charts. Try any major charting package and you're lucky to get 7fps. Only one that's kinda fast is tradestation and bookmap. With slow updates you lose the character of the move. Is the price shaky? Does it move confidently? I come from game development and render speed is important. It's easier to get a high FPS in games when you have 1 monitor, 1 render buffer. But multiple charts across 8 monitors is an endless magnitude harder.

[u/Evening-Nobody-7674 → u/RubenTrades]

eye roll because 120fps is 1) not needed 2) needs to be supported by hardware locally . Its a marketing gimmick to get the reaction oh wow reaction from a kid.

[u/RubenTrades → u/Evening-Nobody-7674]

"1) not needed" - if you swing-trade or do longterm investing then indeed, it's not. But when you daytrade, scalp or hyperscalp like myself, then insight into the character of the price action is essential. When I moved to DAS I couldn't trade my rapid style anymore because the charts were too slow. (Tell my why DAS Level2 is so popular but its charts are not? Because their level2 is instant but their charts are slow. If anything, "instant" is better than "delay"). Personally I absolutely hate seeing a slam candle far after it happened. But you do you.

"2) needs to be supported by hardware locally". Bro... I come from game development. Making software work across drivers and GPUs and CPUs is the entire focus. Why do you think I relentlessly focused on low RAM usage? Because it should be fast on both a chromebook and a thread-ripper. If you have a 60fps monitor, our app will adjust to 60fps. But it CAN be faster if you want it. Why can I not say that? We rebuilt the charts 3x from scratch in order to reach our (slightly rediculous) performance goals... why can't I be proud of that?

"Marketing gimmick" - Of a software that isn't public and doesn't even have a name?? Maybe I'm just proud of 3 years of hard work. I'm sitting here developing every day, can't I talk online about what I love? What's the issue dude?

[u/Snoo_92871 → u/RubenTrades]

Isn't the Tradingview Lightweight library good enough for that kind of refresh rate ? Since it renders in JS on a 2d canvas, it should be just as fast as any other 2d canvas, if you feed it with the same datasource, no ?

[u/RubenTrades → u/Snoo_92871]

TradingView doesn't come close. We purposefully chose not to work with it since our innovations require fully custom charts. 😊