Hi-Lo Counting Trainer

Watches the drop zone on your screen, reads each card as it lands, counts the shoe.

no source Idle

Capture

Table overview context

Watch the whole table. Nothing here is counted.

no source
Share a screen and it feeds both panels — then drag here to box the whole table.

Drop zone detected here

The area where dealt cards come to rest.

no source
Share a screen, then drag here to box just where the cards land.

no region yet

Share once and both panels use it — then drag out a different region on each: the whole table on the left, just the landing area on the right. Detection only ever runs on the drop zone region, and the tighter you box it the faster and more accurate the read. If the two are on different monitors, share the second one separately from its own panel and each keeps its own screen.

Learning

0 learned
Taught so far
Kept between runs.

Every card that lands appears here with the picture captured of it, and the percentage is how sure the read is. Set the dropdown to what the card really is — that corrects the count and teaches the detector. Correcting a wrong read teaches it more than labelling a skipped one. Amber maybe X? tiles were seen clearly but not named confidently: they are not counted until you say what they are.

no hands yet A page per hand — closed off when the table is swept.

Nothing dealt yet. Share the drop zone and cards will show up here as they land.

Running count 0
True count 0.0
Decks remaining 8.0
Cards seen 0
Dealt 0.0 of 8 decks shuffle in 4.0

Shoe

Manual entry — keyboard: A 2-9 0 J Q K

Dealt 0

Detector tuning

Cards are read where they land. Nothing is counted while a card is in motion — a track only forms once a glyph holds one position, so a card being dealt is ignored until it comes to rest.

Rank only. A card is identified purely by its number or letter. Suit pips are discarded geometrically (the pip sits under the index) and by shape. Hitting on an amber tile teaches that shape as a non-rank.

It learns as you go. Everything you label is kept between runs, so the detector gets better at your table each session. If it reads nothing at all, open the detector view — that tells you whether it's failing to find glyphs or failing to recognise them.