Get started

X-volume

Volume Profile Free Ultra SLI (100 Levels Value Area VWAP) - RRBVolume Profile Free Ultra SLI by RagingRocketBull 2019 Version 1.0 This indicator calculates Volume Profile for a given range and shows it as a histogram consisting of 100 horizontal bars. This is basically the MAX SLI version with +50 more Pinescript v4 line objects added as levels. It can also show Point of Control (POC), Developing POC, Value Area/VWAP StdDev High/Low as dynamically moving levels. Free accounts can't access Standard TradingView Volume Profile, hence this indicator. There are several versions: Free Pro, Free MAX SLI, Free Ultra SLI, Free History. This is the Free Ultra SLI version. The Differences are listed below: - Free Pro: 25 levels, +Developing POC, Value Area/VWAP High/Low Levels, Above/Below Area Dimming - Free MAX SLI: 50 levels, 2x SLI modes for Buy/Sell or even higher res 150 levels - Free Ultra SLI: 100 levels, packed to the limit, 2x SLI modes for Buy/Sell or even higher res 300 levels - Free History: auto highest/lowest, historic poc/va levels for each session Features: - High-Res Volume Profile with up to 100 levels (line implementation) - 2x SLI modes for even higher res: 300 levels with 3x vertical SLI, 100 buy/sell levels with 2x horiz SLI - Calculate Volume Profile on full history - POC, Developing POC Levels - Buy/Sell/Total volume modes - Side Cover - Value Area, VAH/VAL dynamic levels - VWAP High/Low dynamic levels with Source, Length, StdDev as params - Show/Hide all levels - Dim Non Value Area Zones - Custom Range with Highlighting - 3 Anchor points for Volume Profile - Flip Levels Horizontally - Adjustable width, offset and spacing of levels - Custom Color for POC/VA/VWAP levels, Transparency for buy/sell levels WARNING: - Compilation Time: 1 min 20 sec Usage: - specify max_level/min_level/spacing (required) - select range (start_bar, range length), confirm with range highlighting - select volume type: Buy/Sell/Total - select mode Value Area/VWAP to show corresponding levels - flip/select anchor point to position the buy/sell levels - use Horiz Buy/Sell SLI mode with 100 or Vertical SLI with 300 levels if needed - use POC/Developing POC/VA/VWAP High/Low as S/R levels. Usually daily values from 1-3 days back are used as levels for the current day. SLI: use SLI modes to extend the functionality of the indicator: - Horiz Buy/Sell 2x SLI lets you view 100 Buy/Sell Levels at the same time - Vertical Max_Vol 3x SLI lets you increase the resolution to 300 levels - you need at least 2 instances of the indicator attached to the same chart for SLI to work 1) Enable Horiz SLI: - attach 2 indicator instances to the chart - make sure all instances have the same min_level/max_level/range/spacing settings - select volume type for each instance: you can have a buy/sell or buy/total or sell/total SLI. Make sure your buy volume instance is the last attached to be displayed on top of sell/total instances without overlapping. - set buy_sell_sli_mode to true for indicator instances with volume_type = buy/sell, for type total this is optional. - this basically tells the script to calculate % lengths based on total volume instead of individual buy/sell volumes and use ext offset for sell levels - Sell Offset is calculated relative to Buy Offset to stack/extend sell after buy. Buy Offset = Zero - Buy Length. Sell Offset = Buy Offset - Sell Length = Zero - Buy Length - Sell Length - there are no master/slave instances in this mode, all indicators are equal, poc/va levels are not affected and can work independently, i.e. one instance can show va levels, another - vwap. 2) Enable Vertical SLI: - attach the first instance and evaluate the full range to roughly determine where is the highest max_vol/poc level i.e. 0..20000, poc is in the bottom half (third, middle etc) or - add more instances and split the full vertical range between them, i.e. set min_level/max_level of each corresponding instance to 0..10000, 10000..20000 etc - make sure all instances have the same range/spacing settings - an instance with a subrange containing the poc level of the full range is now your master instance (bottom half). All other instances are slaves, their levels will be calculated based on the max_vol/poc of the master instance instead of local values - set show_max_vol_sli to true for the master instance. for slave instances this is optional and can be used to check if master/slave max_vol values match and slave can read the master's value. This simply plots the max_vol value - you can also attach all instances and set show_max_vol_sli to true in all of them - the instance with the largest max_vol should become the master Auto/Manual Ext Max_Vol Modes: - for auto vertical max_vol SLI mode set max_vol_sli_src in all slave instances to the max_vol of the master indicator: "VolumeProfileFree_MAX_RRB: Max Volume for Vertical SLI Mode". It can be tricky with 2+ instances - in case auto SLI mode doesn't work - assign max_vol_sli_ext in all slave instances the max_vol value of the master indicator manually and repeat on each change - manual override max_vol_sli_ext has higher priority than auto max_vol_sli_src when both values are assigned, when they are 0 and close respectively - SLI is disabled - master/slave max_vol values must match on each bar at all times to maintain proper level scale, otherwise slave's levels will look larger than they should relative to the master's levels. - Max_vol (red) is the last param in the long list of indicator outputs - the only true max_vol/poc in this SLI mode is the master's max_vol/poc. All poc/va levels in slaves will be irrelevant and are disabled automatically. Slaves can only show VWAP levels. - VA Levels of the master instance in this SLI mode are calculated based on the subrange, not the whole range and may be inaccurate. Cross check with the full range. WARNING! - auto mode max_vol_sli_src is experimental and may not work as expected - you can only assign auto mode max_vol_sli_src = max_vol once due to some bug with unhandled exception/buffer overflow in Tradingview. Seems that you can clear the value only by removing the indicator instance - sometimes you may see a "study in error state" error when attempting to set it back to close. Remove indicator/Reload chart and start from scratch - volume profile may not finish to redraw and freeze in an ugly shape after an UI parameter change when max_vol_sli_src is assigned a max_vol value. Assign it to close - VP should redraw properly, but it may not clear the assigned max_vol value - you can't seem to be able to assign a proper auto max_vol value to the 3rd slave instance - 2x Vertical SLI works and tested in both auto/manual, 3x SLI - only manual seems to work (you can have a mixed mode: 2nd instance - auto, 3rd - manual) Notes: - This code uses Pinescript v3 compatibility framework - This code is 20x-30x faster (main for cycle is removed) especially on lower tfs with long history - only 4-5 sec load/redraw time vs 30-60 sec of the old Pro versions - Instead of repeatedly calculating the total sum of volumes for the whole range on each bar, vol sums are now increased on each bar and passed to the next in the range making it a per range vs per bar calculation that reduces time dramatically - 100 levels consist of 50 main plot levels and 50 line objects used as alternate levels, differences are: - line objects are always shown on top of other objects, such as plot levels, zero line and side cover, it's not possible to cover/move them below. - all line objects have variable lengths, use actual x,y coords and don't need side cover, while all plot levels have a fixed length of 100 bars, use offset and require cover. - all key properties of line objects, such as x,y coords, color can be modified, objects can be moved/deleted, while this is not possible for static plot levels. - large width values cause line objects to expand only up/down from center while their length remains the same and stays within the level's start/end points similar to an area style. - large width values make plot levels expand in all directions (both h/v), beyond level start/end points, sometimes overlapping zero line, making them an inaccurate % length representation, as opposed to line objects/plot levels with area style. - large width values translate into different widths on screen for line objects and plot levels. - you can't compensate for this unwanted horiz width expansion of plot levels because width uses its own units, that don't translate into bars/pixels. - line objects are visible only when num_levels > 50, plot levels are used otherwise - Since line objects are lines, plot levels also use style line because other style implementations will break the symmetry/spacing between levels. - if you don't see a volume profile check range settings: min_level/max_level and spacing, set spacing to 0 (or adjust accordingly based on the symbol's precision, i.e. 0.00001) - you can view either of Buy/Sell/Total volumes, but you can't display Buy/Sell levels at the same time using a single instance (this would 2x reduce the number of levels). Use 2 indicator instances in horiz buy/sell sli mode for that. - Volume Profile/Value Area are calculated for a given range and updated on each bar. Each level has a fixed length. Offsets control visible level parts. Side Cover hides the invisible parts. - Custom Color for POC/VA/VWAP levels - UI Style color/transparency can only change shape's color and doesn't affect textcolor, hence this additional option - Custom Width - UI Style supports only width <= 4, hence this additional option - POC is visible in both modes. In VWAP mode Developing POC becomes VWAP, VA High and Low => VWAP High and Low correspondingly to minimize the number of plot outputs - You can't change buy/sell level colors from input (only transparency) - this requires 2x plot outputs => 2x reduces the number of levels to fit the max 64 limit. That's why 2 additional plots are used to dim the non Value Area zones - You can change level transparency of line objects. Due to Pinescript limitations, only discrete values are supported. - Inverse transp correlation creates the necessary illusion of "covered" line objects, although they are shown on top of the cover all the time - If custom lines_transp is set the illusion will break because transp range can't be skewed easily (i.e. transp 0..100 is always mapped to 100..0 and can't be mapped to 50..0) - transparency can applied to lines dynamically but nva top zone can't be completely removed because plot/mixed type of levels are still used when num_levels < 50 and require cover - transparency can't be applied to plot levels dynamically from script this can be done only once from UI, and you can't change plot color for the past length bars - All buy/sell volume lengths are calculated as % of a fixed base width = 100 bars (100%). You can't set show_last from input to change it - Range selection/Anchoring is not accurate on charts with time gaps since you can only anchor from a point in the future and measure distance in time periods, not actual bars, and there's no way of knowing the number of future gaps in advance. - Adjust Width for Log Scale mode now also works on high precision charts with small prices (i.e. 0.00001) - in Adjust Width for Log Scale mode Level1 width extremes can be capped using max deviation (when level1 = 0, shift = 0 width becomes infinite) - There's no such thing as buy/sell volume, there's just volume, but for the purposes of the Volume Profile method, assume: bull candle = buy volume, bear candle = sell volume P.S. I am your grandfather, Luke! Now, join the Dark Side in your father's steps or be destroyed! Once more the Sith will rule the Galaxy, and we shall have peace...
Pine Script™ indicator
by RagingRocketBull
108
Pump|Dump Tickerthis is just a study to investigate the pumps and dumps that have been happened in a crypto market and it should not be used as an indicator. this is also my very first Pine Script that I've written and I am sure it is not perfect. actually I am curious to know when (I mean the exact time of the day) most pumps and dumps happen as a self investigation. the method that is used to define pumps and dumps is not good (and I know that) but I will modify it for better result in next version. to use this study, you should define whether you want to display pumps or dumps or both and also you should define percent of change (threshold).
Pine Script™ indicator
by ehsanha
R100 Wave Volume v2 (*v*)This indicator is similar to the Weis Wave Volume indicator in that it shows cumulative volume for each up and down price wave. However it is calculated differently, using the Jurik moving average to determine turning points. Use this in conjunction with the R100 Wave indicator to determine the best fit Jurik length and power settings. A great indicator to help analyse the strength of pullbacks, continuation moves and changes in behaviour. I hope you get some value out of it. Only conditions of use are that if you improve it, let me know and if you publish something that uses it, don't hide the code! Enjoy! Code pinched and modified from Zero Lag ZigZag by Duyck - thankyou Jurik Moving Average (for turning points) by Everget - thankyou and Weis Wave by Modhelius - thankyou
Pine Script™ indicator
by Rooster100
34
Trend Scores + Volume-Weighted Trend ScoresHere is a simple indicator based on Tushar Chande's TrendScore . The main purpose of the TrendScore is to determine the strength and direction of a trend, which it does by comparing the current price to the prices within a user-defined window of historical prices. In the input menu, the user defines the starting and ending period. The current price is then compared to each historical price. If the current price is greater than the given historical price, then the TrendScore is incremented, while it is decremented if it is below the given historical price. TrendScore values fluctuate between a maximum of 100 and a minimum of -100, with 100 meaning that the current price is greater than each historical price in the window and a value of -100 meaning the inverse is true. We then use the same process to calculate the volume trend score by passing in volume to the 'getTrendScore' function. Lastly, the indicator also also calculates a 'volume-weighted trend score'. This is simply the average of the price trend score and the volume trend score. It is not plotted by default, but users can set the input option to true in the input menu and it will be plotted as a yellow line (as seen in the bottom chart). The Chart: The trend scores for price are plotted as a histogram. We've summarized the meaning behind its color changes below: -If ( trendScore == 100) then color = dark green -if ( trendScore < 100 and trendScore is increasing) then color = light green -if ( trendScore > 0 and trendScore is DECREASING) then color = pink -if ( trendScore < 0) then color = red The volume trend score is plotted as a blue line. We felt that using a similar coloring system for the volume trend scores would over-crowd the chart and take away from the simplicity that makes this indicator useful. The volume-weighted trend score is plotted as a yellow line. The main price bars change color based on the price trend score to make the values easier to visualize as well. Interpretation: This is a pretty versatile indicator. We summarized the ways in which traders can use it: -Enter Long Positions when the trend score crosses zero from negative to positive territory. -Exit Long Positions when the trend score was previously 100 and begins decreasing (ie bar color changes from dark green to pink). -Spot bearish divergences when price trend score is 100 or relatively high and the volume trend score decreases significantly. -Identify bullish divergences when price trend score is relatively low and volume trend score is increasing. ~Happy Trading~
Pine Script™ indicator
by ProfitProgrammers
5
Cryptohopper OBVCryptohopper is an automated trading platform where you can automate your strategy based on technical indicators and candlestick patterns. OBV is one the indicators that you can automate with Cryptohopper. How can you automate it? OBV gives a Buy signal when the OBV value crosses up its moving average (default: EMA) and a Sell signal when it crosses down its moving average. If you include volume analyses in your trading strategy, automating OBV will give buy signals whenever volume and price are rising altogether. Start automating your trading in Cryptohopper.com --CRYPTOHOPPER--
Pine Script™ indicator
by cryptohopper
5
Bitcoin Fat Volume IndicatorBitcoin Fat Volume Indicator The script displays aggregate sums of Bitcoin dollar and Tether market volumes separately as follows: USD markets (blue): gemini, coinbase, okcoin, kraken, bitfinex, bitstamp, btce, mtgox Tether markets (orange): huobi, binance, bittrex, poloniex, hitbtc The indicator should work on all time frames on any chart so long as volume data exists. Obviously for full history use Bitcoin Liquid Index. The indicator is slow that's why I'm not including other stable coins or fiat markets at present. Use settings to turn off Tether or USD bars as desired.
Pine Script™ indicator
by RealMcafee
2
Multi-TF Avg BBandsMULTI-TF AVERAGE BBANDS - with signals (BETA) Overall, it shows where the price has support and resistance, when it's breaking through, and when its relatively low/high based on the magic of standard deviation. created by gamazama. send me a shout if u find this useful, or if you create something cool with it. %BB: The price's position in the boilinger band is converted to a range from 0-1. The midpoint is at 0.5 Description of parameters "BB:Window Length" is the standard BB size of 20 candles. The indicator plots up to 7 different %BB's on different timescales They are calculated independently of the timescale you are viewing eg 12h, 3d, 30m will be the same output You can enter 7 timescales, eg. if you want to plot a range of bbands of the 12h up to 3d graphs, enter values between 0.5 and 3 (days) - you can also select 0 to disable and use less timescales, or select hours or minutes Take note if you eg. double the main multiplier to 40, it is the same as doubling all your timescales You can turn the transparency of the 7 x %BB's to 100 to hide them, their average is plotted as a thick cyan line "Variance" is a measure of how much the 7 BB's agree, and changes colour based on the thresholds used for the strategy ---- TO START FROM SCRATCH ---- - set all except one to ZERO (0), set to 0, and everything after to 0. Turn ON and right click -> move the indicator to a new pane - this will show you the internal workings of the indicator. Then there is a few standard settings "Source Smoothing Amount" applies a basic small sma on the price. It should be turned down when viewing candles with less information, like 1D or more. Standard BBands use an SMA, there one uses a blend between VWMA or SMA Volume Weight settings, the same as SMA at 0, and the same as VWMA at 1 BB^2 is a bband drawn around the average %BB. Adjust the to change its window length The BB^2 changes color when price moves up or down Now its time to look at the parameters which affect the buy/sell signals turn on "show signal range" - you see some red lines buy and sell each have 4 settings min/max variance will affect the brigtness of the signal range range adjust will move the range up/down mix BB^2 blends between a straight line (0) and BB^2's top or bottom (1) a threshold of "variance" and "h/l points" is available to generate weaker signals. these thresholds can be increased to show more weak signals ONCE YOU ARE HAPPY WITH THE SIGNALS being generated, you can turn OFF , and move it back to the price pane the indicator then draws a bband around the price to maps some info into the chart: fills a colour between 0.5 & the mid BB^2 and converts relative to the price chart draws a line in the middle of the midband. controls how much these lines diverge from the price - adjust it to reduce noise converts the signal range (red lines) to be relative to the price chart if you like, you can adjust the sell & buy signals in the tab from and to and to match the picture. It messes with auto-scaling when moving back to though enjoy, I hope that is easy enough to understand, still trying to make this more user-friendly. If you want to send me some token of appreciation - btc: 33c2oiCW8Fnsy41Y8z2jAPzY8trnqr5cFu I promise it will put a fat smile on my face
Pine Script™ indicator
by gamazama
4
RVOL - R4RocketRelative volume or RVOL for short is an indicator that is used to measure how 'In Play' the stock is. Simply put, it helps to quantify how interested everybody is in the given stock - higher the value, higher the interest and hence higher is the probability for movement in the stock. I have tried to create RVOL (Relative Volume ) Indicator as per the description that I read on SMB Capital blog. The blog is a great resource. ................................................................................................................................................................................... How to use the indicator - The indicator is meant for INTRADAY ONLY. The indicator has following inputs - 1. RVOL Period - Value from 3 to 14 (Default Value = 4) This is used to calculate the average volume over the given period of days. e.g. average volume for the last 5 days, last 3 days, last 10 days etc. NOTE - If you use higher RVOL Period on smaller timeframes, the code will give an error. So I recommend using 4 or lower for 5 min timeframe. (Nothing will work on 1 min chart and you can experiment for other timeframes.) 2. RVOL Sectional - True / False (Default Value = False) If you check this box then you will be able to calculate the RVOL for a particular session (or between particular sessions) in that trading day. What do I mean by session? Well I have divided the trading day into 6 (almost) equally spaced sessions in time, i.e. 6 hours and 15 mins (for NSE - India) of trading day is divided into 1 hr - 1st session, 1 hr - 2nd session, 1 hr - 3rd session, 1 hr - 4th session, 1 hr - 5th session, 1 hr and 15 min - 6th session. Before using 3rd and 4th inputs of indicator, RVOL Sectional box MUST BE CHECKED FIRST. 3. RVOL From Session - 1 to 6 (Default Value = 1) 4. RVOL To Session - 1 to 6 (Default Value = 2) Now if you select 2 in "RVOL From Session" input and 3 in "RVOL To Session" input, the indicator will calculate RVOL for the 2nd and 3rd hour of the trading day. If you select 3 in both the inputs, then the indicator will give RVOL for the 3rd hour of the trading day. 5. RVOL Trigger - 0.2 to 10 (Default Value = 2) Filter to find days having RVOL above that value. The indicator turns green (or colour of your choice) when RVOL is more than "RVOL Trigger". ................................................................................................................................................................................... Hope this indicator will add some value in your trading endeavor. “Only The Game, Can Teach You The Game” – Jesse Livermore Yours sincerely, R4Rocket **If you have some awesome idea for improvement of the indicator - request you to update the code and share the same.
Pine Script™ indicator
by R4Rocket
20
Intra-bar VolumeDisclamer : READ THIS BEFORE USING IT !!! I have take and try to improuve the source code of indicator "intra-bar volume" by backtest-rookies.com This indicator categorized the volume in lower timeframe, if the candle close up it's a buying volume, if it close down... Beware that is not easy to work with different TF on tradingview so you have some limitation on the TF with this indicator. Also in TV we can't have a mutable variable in a security fonction.. so my approche is not clean but it works, if someone find better way, please comment or contact me :) So by default the indicator can work on the following TF : 5m 15m 30m 60m 120m 240m 480m 720m 1D 1W 12M. But ... this indicator need a lower timeframe and the number of bar to work correctly, in my code i suppose that the market run 24/7, so you need to adapte it or use intraday TF for other market. To make sure that the indicator work correctly i have juste add circle, if it's green the buying+selling+balance volume is equal to the volume on the last close candle. If it's red theire is a problem. I hope you enjoy it, feel free to modify the code and comment if you have any sugestion, i have just make it so maybe i will ajust some part of the code.
Pine Script™ indicator
by rimko
18
Volume Profile Free MAX SLI (50 Levels Value Area VWAP) by RRBVolume Profile Free MAX SLI by RagingRocketBull 2019 Version 1.0 All available Volume Profile Free MAX SLI versions are listed below (They are very similar and I don't want to publish them as separate indicators): ver 1.0: style columns implementation ver 2.0: style histogram implementation ver 3.0: style line implementation This indicator calculates Volume Profile for a given range and shows it as a histogram consisting of 50 horizontal bars. It can also show Point of Control (POC), Developing POC, Value Area/VWAP StdDev High/Low as dynamically moving levels. Free accounts can't access Standard TradingView Volume Profile, hence this indicator. There are several versions: Free Pro, Free MAX SLI, Free History. This is the Free MAX SLI version. The Differences are listed below: - Free Pro: 25 levels, +Developing POC, Value Area/VWAP High/Low Levels, Above/Below Area Dimming - Free MAX SLI: 50 levels, packed to the limit, 2x SLI modes for Buy/Sell or even higher res 150 levels - Free History: auto highest/lowest, historic poc/va levels for each session Features: - High-Res Volume Profile with up to 50 levels (3 implementations) - 20-30x faster than the old Pro versions especially on lower tfs with long history - 2x SLI modes for even higher res: 150 levels with 3x vertical SLI, 50 buy/sell levels with 2x horiz SLI - Calculate Volume Profile on full history - POC, Developing POC Levels - Buy/Sell/Total volume modes - Side Cover - Value Area, VAH/VAL dynamic levels - VWAP High/Low dynamic levels with Source, Length, StdDev as params - Show/Hide all levels - Dim Non Value Area Zones - Custom Range with Highlighting - 3 Anchor points for Volume Profile - Flip Levels Horizontally - Adjustable width, offset and spacing of levels - Custom Color for POC/VA/VWAP levels and Transparency for buy/sell levels Usage: - specify max_level/min_level/spacing (required) - select range (start_bar, range length), confirm with range highlighting - select volume type: Buy/Sell/Total - select mode Value Area/VWAP to show corresponding levels - flip/select anchor point to position the buy/sell levels - use Horiz SLI mode for 50 Buy/Sell or Vertical SLI for 150 levels if needed - use POC/Developing POC/VA/VWAP High/Low as S/R levels. Usually daily values from 1-3 days back are used as levels for the current day. SLI: - use SLI modes to extend the functionality of the indicator: - Horiz Buy/Sell 2x SLI lets you view 50 Buy/Sell Levels at the same time - Vertical Max_Vol 3x SLI lets you increase the resolution to 150 levels - you need at least 2 instances of the indicator attached to the same chart for SLI to work 1) Enable Horiz SLI: - attach 2 indicator instances to the chart - make sure all instances have the same min_level/max_level/range/spacing settings - select volume type for each instance: you can have a buy/sell or buy/total or sell/total SLI. Make sure your buy volume instance is the last attached to be displayed on top of sell/total instances without overlapping. - set buy_sell_sli_mode to true for indicator instances with volume_type = buy/sell, for type total this is optional. - this basically tells the script to calculate % lengths based on total volume instead of individual buy/sell volumes and use ext offset for sell levels - Sell Offset is calculated relative to Buy Offset to stack/extend sell after buy. Buy Offset = Zero - Buy Length. Sell Offset = Buy Offset - Sell Length = Zero - Buy Length - Sell Length - there are no master/slave instances in this mode, all indicators are equal, poc/va levels are not affected and can work independently, i.e. one instance can show va levels, another - vwap. 2) Enable Vertical SLI: - attach the first instance and evaluate the full range to roughly determine where is the highest max_vol/poc level i.e. 0..20000, poc is in the bottom half (third, middle etc) or - add more instances and split the full vertical range between them, i.e. set min_level/max_level of each corresponding instance to 0..10000, 10000..20000 etc - make sure all instances have the same range/spacing settings - an instance with a subrange containing the poc level of the full range is now your master instance (bottom half). All other instances are slaves, their levels will be calculated based on the max_vol/poc of the master instance instead of local values - set show_max_vol_sli to true for the master instance. for slave instances this is optional and can be used to check if master/slave max_vol values match and slave can read the master's value. This simply plots the max_vol value - you can also attach all instances and set show_max_vol_sli to true in all of them - the instance with the largest max_vol should become the master Auto/Manual Ext Max_Vol Modes: - for auto vertical max_vol SLI mode set max_vol_sli_src in all slave instances to the max_vol of the master indicator: "VolumeProfileFree_MAX_RRB: Max Volume for Vertical SLI Mode". It can be tricky with 2+ instances - in case auto SLI mode doesn't work - assign max_vol_sli_ext in all slave instances the max_vol value of the master indicator manually and repeat on each change - manual override max_vol_sli_ext has higher priority than auto max_vol_sli_src when both values are assigned, when they are 0 and close respectively - SLI is disabled - master/slave max_vol values must match on each bar at all times to maintain proper level scale, otherwise slave's levels will look larger than they should relative to the master's levels. - Max_vol (red) is the last param in the long list of indicator outputs - the only true max_vol/poc in this SLI mode is the master's max_vol/poc. All poc/va levels in slaves will be irrelevant and are disabled automatically. Slaves can only show VWAP levels. - VA Levels of the master instance in this SLI mode are calculated based on the subrange, not the whole range. Cross check with the full range. WARNING! - auto mode max_vol_sli_src is experimental and may not work as expected - you can only assign auto mode max_vol_sli_src = max_vol once due to some bug with unhandled exception/buffer overflow in Tradingview. Seems that you can clear the value only by removing the indicator instance - sometimes you may see a "study in error state" error when attempting to set it back to close. Remove indicator/Reload chart and start from scratch - volume profile may not finish to redraw and freeze in an ugly shape after an UI parameter change when max_vol_sli_src is assigned a max_vol value. Assign it to close - VP should redraw properly, but it may not clear the assigned max_vol value - you can't seem to be able to assign a proper auto max_vol value to the 3rd slave instance - 2x Vertical SLI works and tested in both auto/manual, 3x SLI - only manual seems to work Notes: - This code is 20x-30x faster (main for cycle is removed) especially on lower tfs with long history - only 2-3 sec load/redraw time vs 30-60 sec of the old Pro versions - Instead of repeatedly calculating the total sum of volumes for the whole range on each bar, vol sums are now increased on each bar and passed to the next in the range making it a per range vs per bar calculation that reduces time dramatically - hist_base for levels still results is ugly redraw - if you don't see a volume profile check range settings: min_level/max_level and spacing, set spacing to 0 (or adjust accordingly based on the symbol's precision, i.e. 0.00001) - you can view either of Buy/Sell/Total volumes, but you can't display Buy/Sell levels at the same time using a single instance (this would 2x reduce the number of levels). Use 2 indicator instances in horiz buy/sell sli mode for that. - Volume Profile/Value Area are calculated for a given range and updated on each bar. Each level has a fixed length. Offsets control visible level parts. Side Cover hides the invisible parts. - Custom Color for POC/VA/VWAP levels - UI Style color/transparency can only change shape's color and doesn't affect textcolor, hence this additional option - Custom Width - UI Style supports only width <= 4, hence this additional option - POC is visible in both modes. In VWAP mode Developing POC becomes VWAP, VA High and Low => VWAP High and Low correspondingly to minimize the number of plot outputs - You can't change buy/sell level colors from input (only plot transparency) - this requires 2x plot outputs => 2x reduces the number of levels to fit the max 64 limit. That's why 2 additional plots are used to dim the non Value Area zones - All buy/sell volume lengths are calculated as % of a fixed base width = 100 bars (100%). You can't set show_last from input to change it - There's no such thing as buy/sell volume, there's just volume, but for the purposes of the Volume Profile method, assume: bull candle = buy volume, bear candle = sell volume P.S. Gravitonium Levels Are Increasing. Unobtainium is nowhere to be found! Links on Volume Profile and Value Area calculation and usage: www.tradingview.com stockcharts.com onlinelibrary.wiley.com
Pine Script™ indicator
by RagingRocketBull
25
Vol(3MA)I just wanted to compare BTC volume from more than one exchange on the same chart. So I spent 3hrs TOSSING OFF WITH GUIs then did it in Pine. I don't like GUIs, especially when it takes me 3hrs to TOSS ONE OFF. After this "new" indicator has saved, I will be able (I hope) to add symbols (e.g. Coinbase:BTCUSD) to my Bitfinex:BTCUSD chart. I will right-click the new symbol and add an indicator to it.. and my poncy, little Volume indicator will show up so I can overlay it on the new symbol. Right now it doesn't come up in the indicator options, even tho I have written and saved it. I will repeat this with a bunch of exchanges on this one chart.. then put them on the same scale... then hide all the price charts... and FINALLY be able to compare volume of exchanges properly in kinda real time. hmm Or I might just go TOSS IT
Pine Script™ indicator
by MrRainbow
Volume Profile Free Pro (25 Levels Value Area VWAP) by RRBVolume Profile Free Pro by RagingRocketBull 2019 Version 1.0 All available Volume Profile Free Pro versions are listed below (They are very similar and I don't want to publish them as separate indicators): ver 1.0: style columns implementation ver 2.0: style histogram implementation ver 3.0: style line implementation This indicator calculates Volume Profile for a given range and shows it as a histogram consisting of 25 horizontal bars. It can also show Point of Control (POC), Developing POC, Value Area/VWAP StdDev High/Low as dynamically moving levels. Free accounts can't access Standard TradingView Volume Profile, hence this indicator. There are 3 basic methods to calculate the Value Area for a session. - original method developed by Steidlmayr (calculated around POC) - classical method using StdDev (calculated around the mean VWAP) - another method based on the mean absolute deviation (calculated around the median) POC is a high volume node and can be used as support/resistance. But when far from the day's average price it may not be as good a trend filter as the other methods. The 80% Rule: When the market opens above/below the Value Area and then returns/stays back inside for 2 consecutive 30min periods it has 80% chance of filling VA (like a gap). There are several versions: Free, Free Pro, Free MAX. This is the Free Pro version. The Differences are listed below: - Free: 30 levels, Buy/Sell/Total Volume Profile views, POC - Free Pro: 25 levels, +Developing POC, Value Area/VWAP High/Low Levels, Above/Below Area Dimming - Free MAX: 50 levels, packed to the limit Features: - Volume Profile with up to 25 levels (3 implementations) - POC, Developing POC Levels - Buy/Sell/Total/Side by Side View modes - Side Cover - Value Area, VAH/VAL dynamic levels - VWAP High/Low dynamic levels with Source, Length, StdDev as params - Show/Hide all levels - Dim Non Value Area Zones - Custom Range with Highlighting - 3 Anchor points for Volume Profile - Flip Levels Horizontally - Adjustable width, offset and spacing of levels - Custom Color for POC/VA/VWAP levels and Transparency for buy/sell levels Usage: - specify max_level/min_level for a range (required in ver 1.0/2.0, auto/optional in ver 3.0 = set to highest/lowest) - select range (start_bar, range length), confirm with range highlighting - select mode Value Area or VWAP to show corresponding levels. - flip/select anchor point to position the buy/sell levels, adjust width and spacing as needed - select Buy/Sell/Total/Side by Side view mode - use POC/Developing POC/VA/VWAP High/Low as S/R levels. Usually daily values from 1-3 days back are used as levels for the current day. - Green - buy volume of a specific price level in a range, Red - sell volume. Green + Red = Total volume of a price level in a range There's no native support for vertical histograms in Pinescript (with price axis as base) Basically, there are 4 ways to plot a series of horizontal bars stacked on top of each other: 1. plotshape style labeldown (ver 0 prototype discarded) - you can have a set of fixed width/height text labels consisting of a series of underscores and moving dynamically as levels. Level offset controls visible length. - you can move levels and scale the base width of the volume profile histogram dynamically - you can calculate the highest/lowest range values automatically. max_level/min_level inputs are optional - you can't fill the gaps between levels/adjust/extend width, height - this results in a half baked volume profile and looks ugly - fixed text level height doesn't adjust and looks bad on a log scale - fixed font width also doesn't scale and can't be properly aligned with bars when zooming 2. plot style columns + hist_base (ver 1.0) - you can plot long horizontal bars using a series of small adjacent vertical columns with level offsets controlling visible length. - you can't hide/move levels of the volume profile histogram dynamically on each bar, they must be plotted at all times regardless - you can't delete the history of a plot. - you can't scale the base width of the volume profile histogram dynamically, can't set show_last from input, must use a preset fixed width for each level - hist_base can only be a static const expression, can't be assigned highest/lowest range values automatically - you have to specify max_level/min_level manually from input - you can't control spacing between columns - there's an equalizer bar effect when you zoom in, and solid bars when you zoom out - using hist_base for levels results in ugly load/redraw times - give it 3-5 sec to finalize its shape after each UI param change - level top can be properly aligned with another level's bottom producing a clean good looking histogram - columns are properly aligned with bars automatically 3. plot style histogram + hist_base (ver 2.0) - you can plot long horizontal bars using a series of small vertical bars (horizontal histogram) instead of columns. - you can control the width of each histogram bar comprising a level (spacing/horiz density). Large enough width will cause bar overlapping and give level a "solid" look regardless of zoom - you can only set width <= 4 in UI Style - custom textbox input is provided for larger values. You can set width and plot transparency from input - this method still uses hist_base and inherits other limitations of ver 2.0 4. plot style lines (ver 3.0) - you can also plot long horizontal bars using lines with level offsets controlling visible length. - lines don't need hist_base - fast and smooth redraw times - you can calculate the highest/lowest range values automatically. max_level/min_level inputs are optional - level top can't be properly aligned with another level's bottom and have a proper spacing because line width uses its own units and doesn't scale - fixed line width of a level (vertical thickness) doesn't scale and looks bad on log (level overlapping) - you can only set width <= 4 in UI Style, a custom textbox input is provided for larger values. You can set width and plot transparency from input Notes: - hist_base for levels results in ugly load/redraw times - give it 3-5 sec to finalize its shape after each UI param change - indicator is slow on TFs with long history 10000+ bars - Volume Profile/Value Area are calculated for a given range and updated on each bar. Each level has a fixed width. Offsets control visible level parts. Side Cover hides the invisible parts. - Custom Color for POC/VA/VWAP levels - UI Style color/transparency can only change shape's color and doesn't affect textcolor, hence this additional option - Custom Widh for levels - UI Style supports only width <= 4, hence this additional option - POC is visible in both modes. In VWAP mode Developing POC becomes VWAP, VA High and Low => VWAP High and Low correspondingly to minimize the number of plot outputs - You can't change buy/sell level colors (only plot transparency) - this requires 2x plot outputs exceeding max 64 limit. That's why 2 additional plots are used to dim the non Value Area zones - Use Side by Side view to compare buy and sell volumes between each other: base width = max(total_buy_vol, total_sell_vol) - All buy/sell volume lengths are calculated as % of a fixed base width = 100 bars (100%). You can't set show_last from input - Sell Offset is calculated relative to Buy Offset to stack/extend sell on top of buy. Buy Offset = Zero - Buy Length. Sell Offset = Buy Offset - Sell Length = Zero - Buy Length - Sell Length - If you see "loop too long error" - change some values in UI and it will recalculate - no need to refresh the chart - There's no such thing as buy/sell volume, there's just volume, but for the purposes of the Volume Profile method, assume: bull candle = buy volume, bear candle = sell volume - Volume Profile Range is limited to 5000 bars for free accounts P.S. Cantaloupia Will be Free! Links on Volume Profile and Value Area calculation and usage: www.tradingview.com stockcharts.com onlinelibrary.wiley.com
Pine Script™ indicator
by RagingRocketBull
33