Welcome to NexusFi: the best trading community on the planet, with over 150,000 members Sign Up Now for Free
Genuine reviews from real traders, not fake reviews from stealth vendors
Quality education from leading professional traders
We are a friendly, helpful, and positive community
We do not tolerate rude behavior, trolling, or vendors advertising in posts
We are here to help, just let us know what you need
You'll need to register in order to view the content of the threads and start contributing to our community. It's free for basic access, or support us by becoming an Elite Member -- see if you qualify for a discount below.
-- Big Mike, Site Administrator
(If you already have an account, login at the top of the page)
@Assaya: None of the inidcators uses bid/ask volume.
The Better Volume indicator by Emini-Watch uses uptick/downtick volume.
My indicator is a simplified version and uses total volume.
NinjaTrader does not provide upticks and downticks for any bar types. It is possible to calculate them, but in that case a secondary bar series of 1-tick data would have to be loaded by the indicator.
Did you compare the TradeStation BetterVolume indicator to the NinjaTrader version (use DTN/IQ, Kinetick or eSignal)?
This one has reusable instances of the SMA, MIN and MAX classes.
Various uses of the double (10 significant digits) data type have been replaced with the integer (no decimal places, applicable to volume) and float (7 significant digits) data types. Calculations carried out to an excessive degree of precision unnecessarily consume resources with absolutely no benefit.
It would be possible to get uptick and downtick volume by making this indicator a subclass of the GomRecorder. If using Ninja Tick Files, no recorded Gom Data would be needed.
The zip file includes both the standard version and a paint bar version, which does not show the volume bars, but triggers the sound alerts. The sound files are also included with the zip file.
Fat Tails & other contributors thank you for the great indicator.
My only problem is that the last version seems to lack the low volume sound filter, so it triggers at the start of every new bar.
Thanks again.
@nasta: Thank you for pointing to the problem. I had set a false parenthesis which caused the indicator to trigger an alert for the first tick of every bar with setting COBC (CalculateOnBarClose) = false.
It should now work as expected. Do not hesitate to come back, if you have any further observations. The updated indicator can be downloaded here: