Começar

Multi

Multi Timeframe RSI - Low Time FrameThis is a follow on to my Multi-Timeframe RSI indicator . In that indicator, you could keep an eye on RSI values above your current time frame. This one allows you to look at RSI levels below your current timeframe. The idea behind this one is you may want to "buy the dip," so you can look for oversold conditions on lower time frames expecting a bounce to occur. There is one issue with this indicator is that it takes awhile to load. Seems to be pretty resource intensive, so I tend not do use it. It will get annoying if toggling fast between tickers due to the speed in which it loads.
Indicador Pine Script™
por millerrh
5
RSI Call-outs Multi-resolution [BigBitsIO]This is a simple multi-resolution (multi-timeframe) RSI indicator that overlays the current chart to show labels for specified oversold and overbought areas defined with inputs. Up to 4 different resolutions/timeframes for their respective RSI (1,2,3, or 4). RSI1 is always enabled and can not be disabled. Red labels with white text represent overbought RSI levels as defined by the user. All enabled RSI will have to qualify as overbought based on settings. Green labels with black test represent oversold RSI levels as defined by the user. All enabled RSI will have to qualify as oversold based on settings. This RSI overlay help easily call-out overbought and oversold candles on a chart where other RSI values on larger resolutions/timeframes are also oversold/overbought without sacrificing screen space for a traditional RSI indicator that is not overlayed on the chart. This indicator has alert conditions that will trigger when all enabled RSI indicators are either oversold or overbought respective to your settings. Note: The best results are to operate your chart as your smallest RSI resolution selected. Personally, I prefer to have my smallest (shortest timeframe) in RSI1, and go larger farther out to RSI4.
Indicador Pine Script™
por BigBitsIO
8
[PX] MTF RSIHello guys, this indicator uses the RSI on three different timeframes, which can be selected in the user input settings. It aims to make your multi-timeframe analysis a bit easier and see patterns, which otherwise might not be spotted. Look for confluence within all the timeframes to increase your probabilities. Because it uses multi-timeframe data, which can repaint, it comes with an optional checkbox to allow repainting or avoid it. Happy trading and stay healthy :)
Indicador Pine Script™
por paaax
5
Support and Resistance Multi Time frameSimple indicator showing the support and resistance on Daily, Weekly and Monthly time frames no matter what time frame you're currently on by highlighting the highest and lowest points on each over the last 34 bars. Daily support and resistance are coloured green. support and resistance are coloured yellow. Monthly support and resistance are coloured red. For best results check where multiple support and resistance areas line up and combine with another indicator for example oscillators to gauge if the support or resistance will reverse the market.
Indicador Pine Script™
por kaaiii
12
TimeSync by KingThies TimeSync by Kingthies Written in Pine v4 Applies one function that was published in the Tradingview Pinescript Manual The Motivation behind this script - Time is 50% of your chart. Many ignore it entirely. This should help give an idea on how to read it and incorporate it in their analysis. TimeSync by KingThies takes a simple concept and turns it into a visual tracking system of when timeframes of significant impact, all close at the same time. By utilizing several high time-frames, we see overlaps in periods and more significant events occurring when multiple periods close at once. The TFs included are 3D,1W,2W and 1M. When users use the timeframes above intraday, the resolution for these HTF's is shown. When using the LTFs, anything lower than 1D/is intraday, the user sees a similar concept but comprised of the 4H, 6H,8H and 10H charts. Users can adjust the settings to show the HTFs in sync AND also factor in if the event was on a business quarter or new year, which adds more significance to the occurrence. By seeing when these periods end in sync, we can assume more volatility is present in a given market, presenting various opportunities for traders to take advantage of a given situation. Apologies in advance for any questions that come up - I will do my best to reply or respond here on Tradingview.com. Additional Resources for this topic can be found in my account signature, located at the bottom of this post.
Indicador Pine Script™
por kingthies
4
MTF Trailing SL Alerts [QuantNomad]These are alerts for my MTF Trailing SL Strategy. Entry Long position if all 4 time-frames agree on the long signal. Exit Long positions when at least 2 time-frames disagree on the long signals. Entry to Short position if all 4 time-frames agree on Short signal. Exit from Short positions when at least 2 time-frames disagree on Short signal. Use "Once Per Bar Close" when creating alerts. Link to the strategy:
Indicador Pine Script™
por QuantNomad
8
MTF Trailing SL Strategy [QuantNomad]This is a Multi-Timeframe version of my Trailing SL Strategy. Few weeks ago I published Trailing SL Strategy. There I used only basic Trailing SL to enter positions. It worked pretty well so I tried to work on it a bit. I thought what if you can use the same ATR TSL on different timeframes and combine them into one signal. In this strategy you can use only ATR stops and choose 3 other higher timeframes in addition to your current timeframe. You'll see Trailing SL plotted on the chart form all these timeframes. Entry Long position if all 4 time-frames agree on long signal. Exit Long positions when at least 2 time-frames disagree on long signal. Entry to Short position if all 4 time-frames agree on Short signal. Exit from Short positions when at least 2 time-frames disagree on Short signal. Here is the link to my basic Trailing SL Strategy:
Estratégia Pine Script™
por QuantNomad
45
Moving Average MTF Live [Experimental]Hello Everyone, While using "Security" function for Higher Time Frames (htf) you must accept "Repainting" issue or better you must use previous day data such "security(syminfo.tickerid, 'D', close, lookahead=barmerge.lookahead_on)" that's best normally (or barmerge.lookahead_off). But the problem is (as you can see) it uses previous day data, and this causes latency. So how to draw LIVE and NON-REPAINTING HTF moving averages? Until the last candle of higher time frame all is fine and no repaint issue. when it came to last candle of HTF and if we use real data, (because of we can not know the future) while price is changing it starts drawing on each candle of current period without correcting old ones (this is repaint issue). it needs to calculate number of curent time frame candles for higher time frame and must change all points in that period as you can see in the video below. We have "50 lines" limitation in current Pine version. we hope to have unlimited lines in next versions. This work is completely experimetal. btw Thanks to all Pine Platform Developers, They are doing very good job ! Better to watch following video to see how they look like: P.S. There is no check for Higher time frame, so you should set time frame for HTF accordingly in the options. Enjoy!
Indicador Pine Script™
por LonesomeTheBlue
17
[fikira] Bollinger Bands + Higher Time FramesHere is my take on BB and MTF, based on the most excellent work of "PineCoders" (MTF Selection Framework functions)! The big advantage is that on 1 image you can easily see where price is compared to 5 or less BB Bands (each of different Time Frames). This gives a lot of Support and Resistance area's! Includes: - 1 Bollinger Bands (can be enabled/disabled - "Bollinger Bands" - 4 Bollinger Bands (each can be enabled/disabled - "HTF Selection 1-4") Each BB has its colour (can be changed) - Labels (Timeframe and price) can be enabled/disabled - Labels position and size can be changed ...
Indicador Pine Script™
por fikira
20
Donchian Cloud - evoA cloud based on the highest high and lowest low of a given period (Donchian), same lines used in Ichimoku Cloud (Conversion line or Base line). Short term line is based on current time frame, long term line is based on your given multiple of current time frame. The color of the lines is based on up or down movement. I stole a piece of code from PineCoders for the multiple time frame: I have not used this in my trades (yet) so I don't know how good it is, just posting because it looks nice :) Feel free to share your settings if you can find good ones.
Indicador Pine Script™
por EvoCrypto
1
Pivots MTF [LucF]Pivots detected at higher timeframes are more significant because more market activity—or work—is required to produce them. This indicator displays pivots calculated on the higher timeframe of your choice. Features ► Timeframe selection — The higher timeframe (HTF) can be selected in 3 different ways:  • By steps (15 min., 60 min., 4H, 1D, 3D, 1W, 1M, 1Y). This setting is the default.  • As a multiple of the current chart's resolution, which can be fractional, so 3.5 will work.  • Fixed. — The HTF used can be displayed near the last bar (default). — Note that using the HTF is not mandatory. If it is disabled, the indicator will calculate on the chart's resolution. — Non-repainting or repainting mode can be selected. This has no impact on the display of historical bars, but when no repainting is selected, pivot detection in the realtime bar will be delayed by one chart bar (not one bar at the HTF). ► Pivots — Three color schemes are provided: green/red, aqua/pink and coral/violet (the default). — Both the thickness and brightness of lines can be controlled separately for the hi and lo pivots. — The visibility of the last hi/lo pivots can be enhanced. — Prices can be displayed on pivot lines and the text's size and color can be adjusted. — The number of bars required for the left/right pivot legs can be controlled (the default is 4). — The source can be selected individually for hi and lo pivots (the default is hlc3 and low . — The mean of the hi/lo pivot values of the last few thousand chart bars can be displayed. Pivots having lasted longer during the mean's period will weigh more in the calculation. The mean can be displayed in running mode and/or only showing its last level as a long horizontal line. I don't find it very useful; maybe others will. ► Markers and Alerts — Markers can be configured on breaches of either the last hi/lo pivot levels, or the hi/lo mean. Crossovers and crossunders are controlled separately. — Alerts can be configured using any of the marker combinations. As is usual for my indicators, only one alert is used. It will trigger on the markers that are active when you create your alert. Once your markers are set up the way you want, create your alert from the chart/timeframe you want the alert to run on, and be sure to use the “Once Per Bar Close” triggering condition. Use an alert message that will remind you of the combination of markers used when creating the alert. If you use multiple markers to trigger one alert, then having the indicator show those markers will be important to help you figure out which marker triggered the alert when it fired. A quick look at the pattern of these markers will hopefully convince you that using them as entry/exit signals would be perilous, as they are prone to whipsaw. I have included them because some traders may use the markers as reminders. Using Pivots These pivots can be used in a few different ways: — When using the high / low sources they will show extreme levels, breaches of which should be more significant. — Another way to use them is with hlc3 (the average of the high , low and close ) for hi pivots and low for the lo pivots. This accounts for my personal mythology to the effect that drops typically reach previous lows more easily than rallies make newer highs. — Using low for hi pivots and high for lo pivots (so backward) can be a useful way to set stops or to detect weakness in movements. You will usually be better served by pivots if you consider them as denoting regions rather than precise levels. The flexibility in the display options of this indicator will help you adapt it to the way you use your pivots. To indicate areas rather than levels, for example, try using a brightness of 1 with a line thickness of 30. The cloud effect generated this way will show areas better than fine lines. Realize that these pivot lines are positioned in the past, and so they are drawn after the fact because a given number of bars need to elapse before calculations determine a pivot has occurred. You will thus never see a pivot top, for example, identified on the realtime bar. To detect a pivot, it takes a number of bars corresponding to the dilation of the higher timeframe in the current one, multiplied by the number of bars you use for your pivots' right leg. Also note that the Pine native function used to detect pivots in this indicator considers a summit to be a top when the number of bars in each leg are lower or equal to that top. Bars in legs do not need to be progressively lower on each side of the pivot for a pivot to be detected. If you program in Pine — See the Pinecoders MTF Selection Framework for an explanation of the functions used in this script to provide the selection mechanism for the higher timeframe. — This code uses the Pine Script Coding Conventions . Thanks — To the Pine coders asking questions in the Pine Script chat on TV ; your questions got me to write this indicator.
Indicador Pine Script™
por LucF
52
MultiTimeFrame Fractals D W M [xdecow]This indicator shows fractals in different timeframes. With the possibility of coloring the bars with any combination of current, daily, weekly and monthly timeframes. The return points are calculated as follows: high > last 3 highs and close above highest low low < last 3 lows and closes below lowest high The direction of higher timeframes fractals tend to be more durable and reliable. This indicator helps to find the fractal alignment of different timeframes, so that you can look for trade opportunities in the same direction as the higher timeframes and improve your chances.
Indicador Pine Script™
por xdecow
9