inconsistent Odds on betting assistant

[heinz_pt]

Hello, Im trying betting assistant and I found some strange information, seen ****** at the same time.
Can anyone explain to the diference in the odd's ?



Thks.[/img]

[Shaun]

I notice a 3 second difference in the time as well.

[MarkRussell]

Hi,

The difference in the odds is going to be because of virtual odds created by Betfair's cross matching process.

Please see http://bdp.betfair.com/index.php?option=com_content&task=view&id=242&Itemid=68 which is why it is not automatically in Betting Assistant.

In our Beta version we have given the user the option to display these virtual odds on markets where we are aware that cross matching is applied.

The option is found in Preferences under the General tab and is labelled “Apply cross matching formula in recognised markets”
With the option ticked you will automatically see the same prices as the website and other API applications that have applied the cross matching formula.
Also there is another option in Preferences under the Grid Interface tab that is labelled “Highlight liquidity created by cross matching”
With this option also ticked the prices and amounts will be highlighted in yellow that result from cross matching.
When cross matching is being applied to a market there will be a green XM in the grid title bar to indicate which you can actually click on to turn on and off.

You can download our Beta version via the following link:-
http://www.gruss-software.co.uk/Betting_Assistant_Beta/Betting_Assistant_Beta.msi

I cannot explain the time difference. Our countdown clock is simply the difference between the official start time of the market as advertised by Betfair and your pc clock.

Regards,
Mark

[negapo]

Hi Mark,
Are there markets were the cross matching isn't applied? Thanks
("where we are aware that cross matching is applied. ")

[MarkRussell]

Hi Mark,
Are there markets were the cross matching isn't applied? Thanks
("where we are aware that cross matching is applied. ")

Yes there are lots where they don't apply cross matching.

[mickyxx1]

Hi just curios does a win Horse market apply cross matching by BF. If so would you have a big advantage if you will be able to see the virtual odds as your trigger can recognize it and have a better fully match success rate bet?

[MarkRussell]

Hi just curios does a win Horse market apply cross matching by BF. If so would you have a big advantage if you will be able to see the virtual odds as your trigger can recognize it and have a better fully match success rate bet?

Hi,

Cross matching is applied to in play horse racing win markets.
But even if you can't see the virtual odds you can still get matched at them.

Betfair says:-

NOTE: It is important to understand that bets placed through the API are matched in the exact same way as bets placed on the website. In other words, a bet placed through the API is matched with either direct opposite bets or with the virtual bet, if available.

Therefore, you may see prices displayed on the Betfair website that are not returned by the API, however the Betfair Sports Exchange still matches any bets placed against all bets and the equivalent cross-matched bets.

And because of "Best Execution" if better odds are available than requested you will get matched at the better odds.

Regards,
Mark

[mak]

Yes, they apply in win horse market the cross matching formula
Under Options - Preferences- General (tab) - tick apply cross matching formula in recognized markets

[mickyxx1]

Hi guys, thanks for your response the reason i ask is let say i have logged in the BA horse racing market i want on my Excel sheet and my trigger is an IF CONDITION where to place a bet when a price of X horse reaches Y (drifting or Streaming in play). If my trigger can't see this virtual prices i will be disadvantaged as others can match using that information my trigger won't be activated? And also I was wondering if anyone can explain to me how the CROSS MATCH works on in-play horse racing, i understand it for Tennis or two selection event like Cricket. Thnks again.

m