BUG for OnMarketData (Page 2) - NinjaTrader Programming | futures.io
futures.io futures trading

Go Back   futures.io

> Futures Trading, News, Charts and Platforms > Platforms and Indicators > NinjaTrader > NinjaTrader Programming

BUG for OnMarketData
Started:January 24th, 2011 (08:45 PM) by timmyb Views / Replies:2,059 / 12
Last Reply:February 5th, 2011 (09:32 PM) Attachments:1

Welcome to futures.io.

Welcome, Guest!

This forum was established to help traders (especially futures traders) by openly sharing indicators, strategies, methods, trading journals and discussing the psychology of trading.

We are fundamentally different than most other trading forums:
  • We work extremely hard to keep things positive on our forums.
  • We do not tolerate rude behavior, trolling, or vendor advertising in posts.
  • We firmly believe in openness and encourage sharing. The holy grail is within you, it is not something tangible you can download.
  • We expect our members to participate and become a part of the community. Help yourself by helping others.

You'll need to register in order to view the content of the threads and start contributing to our community. It's free and simple, and we will never resell your private information.

-- Big Mike

Thread Tools Search this Thread

BUG for OnMarketData

Old January 27th, 2011, 11:52 AM   #11 (permalink)
 Vendor: www.integrity-traders.com 
East Rochester, NY
Futures Experience: Intermediate
Platform: NT
eDanny's Avatar
Posts: 327 since Jul 2009
Thanks: 17 given, 418 received

I think NT doesn't normally differentiate between current and delayed data, If there is data it will use it. A long time ago I suggested the ability to be able to set NT to take certain data from certain sources and I think it was put on the list of things to take a look at. Hopefully, now that NT7 is out and stable, they will have more time to go over the list. You may just have to give them some time.


Reply With Quote

Old January 27th, 2011, 01:07 PM   #12 (permalink)
Elite Member
Denver, CO
Futures Experience: Advanced
Platform: NinjaTrader
Broker/Data: NinjaTrader Brokerage
Favorite Futures: ES
NinjaTrader's Avatar
Posts: 1,167 since May 2010
Thanks: 132 given, 1,738 received

timmyb View Post
I am still a tad confused that when you have two connection why it would choose the delayed one whether it is first or not. Wouldn't it be smart for ninja to look at the two connections realize the second has non delayed and use that. After thinking for a few days on this it does still seem like a bug. Anyone sitting at their pc knowing their second connection has live feed would assume ninja would go to that feed to get it rather than the first delayed feed.

Does this make sense to other traders here?

Basically is you use the gomrecorder you pay for DTN to get correct tick data. But if you have indicators that use onmarketdata and you happen to not have cbot on Iqfeed you would imagine that it would use zenfire. (the second feed). But it will default to the first feed. We who record data cant put zenfire first because then gom records from zenfire. Just seems odd to me after pondering. Basically I would have to pay more to get live level 1 on dtn, but i already have zenfire that gives it. I duno let me know brother traders.

A bug is something that does not work as designed. This is not a bug. NinjaTrader was not designed to handle choosing a connection based on if a data stream is delayed or not. The reason is that not all market data vendors and brokerage API provide that information. Having NinjaTrader detect if a stream is delayed and routing the data request to another available connection that is not delayed is a good idea. It has never been suggested before so I will add this to our list of customer suggestions.

Reply With Quote

Old February 5th, 2011, 09:32 PM   #13 (permalink)
Elite Member
Italy - Roma
Futures Experience: Intermediate
Platform: Sierra Chart
Broker/Data: IB
Favorite Futures: Index futures
jagui's Avatar
Posts: 195 since Jul 2010
Thanks: 248 given, 277 received

NinjaTrader View Post
I will add this to our list of customer suggestions.

Good luck, timmyb

@NinjaTrader : make this list public and let customers vote.

Reply With Quote


futures.io > Futures Trading, News, Charts and Platforms > Platforms and Indicators > NinjaTrader > NinjaTrader Programming > BUG for OnMarketData

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Upcoming Webinars and Events (4:30PM ET unless noted)

NinjaTrader 8: Programming Profitable Trading Edges w/Scott Hodson

Elite only

Anthony Drager: Executing on Intermarket Correlations & Order Flow, Part 2

Elite only

Adam Grimes: Five critically important keys to professional trading

Elite only

Machine Learning Concepts w/FIO member NJAMC

Elite only

MarketDelta Cloud Platform: Announcing new mobile features

Dec 1

NinjaTrader 8: Features and Enhancements

Dec 6

Similar Threads
Thread Thread Starter Forum Replies Last Post
NT Providing Bad Price & Volume Data in OnMarketData!!! RJay NinjaTrader Programming 16 November 12th, 2012 09:39 AM
Using OnMarketData() on Historical data with a recording engine gomi NinjaTrader Programming 115 March 6th, 2011 06:11 PM
Programming Indicators Using OnMarketData in NT7!!! RJay NinjaTrader Programming 3 December 16th, 2010 12:16 PM
Another Bug in Ninja 7 Michael.H NinjaTrader 16 June 30th, 2010 12:02 PM
NT Bug Alert Saroj NinjaTrader Programming 1 July 20th, 2009 07:11 AM

All times are GMT -4. The time now is 12:15 PM.

Copyright © 2016 by futures.io. All information is for educational use only and is not investment advice.
There is a substantial risk of loss in trading commodity futures, stocks, options and foreign exchange products. Past performance is not indicative of future results.
no new posts

Page generated 2016-10-28 in 0.08 seconds with 20 queries on phoenix via your IP