This script distinguishes up/down volume based on lower resolution.
It's important to set correct input "Detailed Resolution" — it affects detalization/loading speed. If equal to chart resolution, should match builtin "volume". The lower it is, the more detalized up/down border.
Release Notes
⋅
added `lookahead=true`, because sum was one bar off,
rewrite slow loop, 100ms error should disappear.
Release Notes
⋅
`lookahead=false` was correct. But there may still be some weird bug in some cases.
Release Notes
⋅
added another style of border between up and down volume (PlusMinus),
fixed some errors (mismatches in volume), like on the first bar of the day,
added option to autofix or highlight any mismatches in volume,
show separate up/down sma's and removed input 'show ma', use styles if needed.
Wonderful job , great to validate moves and help to see what the market makers are up to . I will make good use of this . Many thanks .
AWRutland23
⋅
Awesome indicator! It was actually recommend by the trading view staff. It was exactly what I was looking for, but It does have trouble loading on some charts. What do you mean by setting the "detailed resolution"?
SergioGarofoli
⋅
Awsome, I used to add a fast, slow and very slow lines to view the volumen trends.
I added to thes code and it fits very well.
Now my charts are better to view and understand. At least from me, the Important guy who uses them.
@apozdnyakov, thank you for such a useful indicator. I am also having difficulty using 1D timeframe. I have it set to sample the 3 min detailed resolution (I have the data for this), but I'm getting errors. Sometimes the entire up or down volume for the day won't show. Would there be a fix you could apply please?
(sorry I posted this on the alpha version also by mistake).
thriftySeafowl99343
⋅
Thank you you are the best thank you of you and thank you of my god.
Modrian
⋅
Is there a guide how to use this? I don't even understand what it does exactly...
thdcbboy
⋅
Thank you very much, very good
Flopp
⋅
It repaints when you are not using the same time resolution as in the chart, can this be fixed?