Quote from rcj:
Under global settings when calculated volume is set, the value
updates correctly on a ticker page in TWS.
However the calculated volume value is not being sent thru
the API for use by some apps getting data from IB. Instead, the
"native" volume value is sent thru the AP!.
There are 2 sources of the volume: the one that is supplied by the data feed (also known as "native" volume, which includes all corrections like trade busts etc) and the one that calculated by us (also known as "calculated" volume, which is just indicative volume and does not include trade busts etc).
As a courtesy to our customers we made it possible in TWS to elect to view native or calculated via config setting discussed above. API clients has (and had for a while) access to both (native is requested using RTVolume generic tick). The config in TWS only updates UI and does not affect API (nor logically it should affect API since both data points are accessible by simply querying it).
We are checking why native volume (and high/low) is now ticking slower than it use to be (this is likely related to the fact how frequently this data is delivered to us from exchange); calculated volume is still ticking very frequently.
Thank you for bringing this up to our attention using appropriate channels.