VB or Sector Play Memorisation

[Firefox]

When memorising the wheel for VB play I use this system  (see attached)

I only use the black numbers as black on white is easier to see, at speed, for me. There is an error of 1 pocket sometimes as I take the nearest black number, but it doesn't make a huge deal for sector play and it simplifies the whole process.

Opposites on the wheel are important. 18 pockets, could be 19 through zero, but 0 ignored for simple quick calculations.

18pockets Wheel 1/2s

0    -  5R  -  0   -  5R  -  0

15  -  24  -  15  -  24  -  15

4    -  33  -   4   -  33  -  4

2    -  20  -   2   -   20  -  2

17  -  31  -  17  -   31  -  17

6    -  22  -   6   -   22  -  6

13  -  29  -  13  -  29   -  13

11  -  28  -  11  -  28   -  11

8    -  35  -   8   -  35   -   8

10  -  26  -  10  -  26   -   10

0    -  5R  -  0    -  5R   -   0

Then there are the various circuits of orange, yellow, and green.

For example, I associate 15 and other numbers with orange. I immediately know 15-11-31 is a 12 pocket circuit (1/3 of the wheel), again ignoring zero, and there's the associate orange circuit 17-24-28 which taken together with the other circuit gives 1/6s of the wheel.


12pockets 1/3s 6pockets 1/6s

ORANGE
15  - 11 -  31  - 15  - 31  - 11  - 15

17  - 24  - 28  - 17  - 28  -  24  - 17


YELLOW
4    -  8  -  22  -  4   - 22   -  8   -  4

6    - 33  - 35  -  6   - 35  -  33  - 6


GREEN
2    - 10  - 29  -  2   - 29   - 10  - 2

13  - 20 -  26  - 13  - 26  - 20  - 13

Eg How many pockets from 15  to 17cw? Answer 6  . How many from 15 to 31 cw? Answer 24

All these and other intervals are available for immediate recall. I have coloured stickers on my wheel at home to cement the associations.

It doesn't matter what system you use, but this works for me 

[Firefox]

This scheme can also be used for dealer's signature and other sector play like neighbours bets even if you aren't doing VB.

Once  you have learned the black framework, it's easy to slot the red numbers in between.

Rather than dotting your pen round the little card provided by the casino to count,  you can impress your friends by just knowing the distances and locations straight off!

[Steve]

Thanks firefox, good share.

[Firefox]

Heres another aid to memory for the cycles of colours yellow, orange, and green black numbers.

Using a Rubick's cube. It has some yellow, orange  and green faces.

[Firefox]

On 3 of the faces yellow, orange and green I have written the 6 black numbers of that cycle on the wheel.

Attached yellow face close up.

It also has the 0  - red 5 axis which is at right angles to the 6 - 22 axis.

[Firefox]

How does this work? Well after solving the cube I stare at one of the faces repeating over and over the relationships.

1/2 wheel 18 pockets
4 opposite 33 opposite 4
6 opposite 22 opposite 6 etc

4 - 8 - 22 - 4 - 22 - 8 - 4
1/3  wheel 12 pockets

Similar  6 -33 -35 - 6 - 35 - 33 -6

4 - 6 - 8 - 33 - 22 - 35 6ths 6 pockets

It's like learning your times tables but with weird numbers.

Just anally repeat them over and over again till you know them forwards, backwards and sideways!

Why is this important? Well, say I predict a fall off at number 4 about 7 spins out. I know for say a 4.5 second rotor, the scatter peak is about 18 pockets round the wheel, so I immediately know 33 and around is the bet.

Or for a 3.5 second rotor, the scatter peak is 24 pockets away, that gives 22 and numbers splits and streets etc round there. I could bet 22 28/28split 9/12 split etc.

I work very much on low profile wheels with large scatters. This type of approximation is fine for these wheels. You just have to bet in the zone.

Whereas for sticky wheels with tight scatter zones you need to be more accurate. Exact number of pockets ideally and tight predictions.  The long scatter wheels are much lower edge  but more forgiving on loose fuzzy VB systems like mine.

But whichever system you use, you need to have the wheel in your head and be instant on calculations. It's no good saying "4 right, let me see where's that on the wheel ... and 3.5 sec rotor, thats erm 2/3 round and 24 pockets .... well that's 4 -6 -8-22, that's 4x6 = 24 so 22 is the zone" it's got to be instant like knowing what 8x9 is without even thinking.

[Firefox]

One of the problems I have had trying to teach VB to friends is they can't visualise and remember where the numbers are.

The clock face (attached) is an attempt to help achieve this by replacing something alien with something familiar.

There are some compromises to make it easier to memorise. 37 numbers and 18 blacks into 12 hours... if you make it exact, you get odd numbers of hours and minutes. So some rationalisation but it's not far off and the object is to remember positions and relationships. The odd pocket or two will not be important with the ball scattering all over the place. We are concerned with octants and quadrants.

The main axes of 12 to 6 and 9 to 3 are formed by zero-red 5, and 22-6.

Two black numbers (22 &6) have been used which leaves 16. These are found in 4 quadrants.

15,4,2,17 Lunch time 12.30 to 2.30

13,11,8,10 Tea time 3.30 to 5.30

24,33,20,31 Dinner time 6.30 to 9.30

29,28,35,26 Supper time 9.30 to 11.30

Each number has a time, and these are whole hours or half hours. The half hours are adjacent to the main axes, and the middle two numbers have whole hours. Apologies for English times and meals. You could replace them with continental time or whatever daily schedule fits your recollection.

You might want to associate the numbers with people dining together. The odd numbers are male and the even female. 15 and 4 are football and volleyball players. Like 2 and 17, the ladies have the lower numbers as per a volleyball team. 6  is also on the team, but she came late. All the sporty people dine at lunch. You could invent outfits they wear like a baseball cap with 15 on it etc.

Tea time is the only quadrant where odd and even blacks are in pairs. These are the gay couple 11 and 13, and the lesbians 8 and 10. Although they are same sex, they are quite well matched  (only a difference of 2). The gent red 5 is totally different. He's transexual (with red hair of course) and came late at 6!

Ok this will all sound very strange, but it is based on memory theory. You are trying to form pictures to memorise quite an abstract concept. The weirder and more memorable the better. Dinner time could be a bunch of animals, or aliens, or wherever your imagination takes you.

This graphic also introduces the red numbers. They are not as important (to me) as the blacks for the framework, but they hang on in there, and worth just as much when they win, so know where they are too, as you progress your knowledge.

[6th-sense]

I like it ..great way to remember the wheel

[Mako]

Ha, that is by far one of the best ways I've seen to make it easier.  Great stuff Firefox.

[Firefox]

Here's another idea to memorise the wheel. See photo attached.  I just laid out the main axes and the lunch quadrant for clarity.

Obtain a pack of playing cards. I have chosen 20 cards to represent the 18 black numbers plus 0 and red 5.

I have written on each card. The number eg Ace of Spades is 15, 4 of spades is 4  etc.

Also on the card is the red numbers either side, and the time in the clock face. You ruin a pack of cards costing £1 but think how much you are going to win!

Ways to play.

Shuffle the cards face down.

(a) Deal them face up one at a time. As soon as you see the number, name it's place on the clock face and visualise it in your head, name it's opposite, it's thirds cycle, and the sixth cycle. Then reds either side.

For 15 this would be
12.30
15-24
15-11-31
15-17-11-24-31-28
Red 32 Red 19

Continue through the whole pack and repeat.

(b)Deal face up but immediately put in its clockface position in the wheel, and continue dealing out the whole pack like this, till you have a circle.

Shuffle and repeat but this time deal the wheel upside down with 15 at 6.30. Red 5 will be at 12.00.

Repeat but deal the wheel on its side with 15 at 9.30, and repeat again with 15 at 3.30. Repeat at other angles.

You must be able to visualise the wheel instantly ar any angle.

You can play while watching TV, on the train to work or any spare moment.

To be successful you must be obsessive to memorize the wheel and be able to do stuff not one person in 1000 players can do.

[ego]

Thanks, Firefox for your amazing good writing topics.
There exist several ways to memorize the wheel and is a basic skill you should master.

I memorize the wheel into sectors of three numbers, except one sector including zero.
One to two weeks to memorize the wheel.

You have a cheating paper in your wallet so you can check that you repeat and memorize each sector correct.
Just repeat them when you go to sleep, dream about them.
Repeat them at breakfast, during dinner and your way to and home from work.
Then it will take less than one week.

When you memorize the wheel you will not forget the numbers.
This is how the sectors look like:

0. 26 0 32 15
1. 19 4 21
2. 2 25 17
3. 34 6 27
4. 13 36 11
5. 30 8 23
6. 10 5 24
7. 16 33 1
8, 20 14 31
9, 9 22 18
10, 29 7 28
11. 12 35 3

After you memorize the wheel, each sector in a clockwise direction you memorize each index number that belongs to each sector. The index number is to the left on the list above.
The reason you want to learn this is that you can tell any distance and travel length from any visual read to the final outcome.
It starts with listing each opposite sector, the bi-modal effect.

Index number 1-7 are 19 4 21 / 16 33 1

This is the bi-model index number with each opposite sector.

0-6
1-7
2-8
3-9
4-10
5-11

Now we will take this one step further and I don't blame you if you don't understand.
In split second I can calculate the distance and travel length from visual read to outcome in my head before the ball has landed.

I use a flexible cross.

Assume the visual read is number 34, sector 3.
Then moving two sectors apart from each I get a flexible cross.
3-6-9-0 using the index number and knowing the number that belongs to each sector.

Each of these sectors is the opposite of each other on the wheel and create a cross +
34 6 27 - 10 5 24 - 9 22 18 - 26 0 32 15

I only see the index number in my head 3-6-9-0
Assume number 26 hit, sector 0

Next time I read number 35, sector 11.
11-2-5-8 I list the index number in my head during the spin and know that sector 8 is where the last distance from the past outcome was same travel length.
It took less then one second from the next visual read to know that 20 14 31 or sector 8 is where the ball will land if the distance and travel length is the same.

No need to calculate each and every pocket by them self to know where to place your bets before you have a result.
If the result had been between 5-8 you would have a wider range of sectors to cover.
Maybe 9 numbers and sectors 7,8,9.

The flexible cross is the main approach to read and understand distance and travel length.
The whole idea is to read the ball speed and get the same spin/speed each time so the distance and travel length is the same each time. After that comes a degree of tilt, dominant drop zone and scatter patterns or ball jumps.

Assume you would play during real play and have a notebook.
Then you write down the fixable cross after each prediction.

1-4-7-10
11-2-5-8

Then you only make a sign between the sectors or around the sectors to see how close ball frequently hit.
When pattern emerge you know where the ball will land before it has and you have already placed your bets.

Cheers

[Firefox]

Thanks Ego for a great post.

It's worth anyone reading studying all these posts in detail.

What will work for one person will not suit another. Most VB players have their own ways of doing things, but choose a system that works for you.  You can borrow a bit from others and add your own stuff.

The output from most VB activity is a fall off number on the wheel. Then for that rotor speed, which you will already have calculated early in the spin, you will have a bounce/scatter in mind. This figure depends on the wheel type and the rotor speed.

Common bounce/scatters for a low profile wheel are 12 pockets (1/3) 18 pockets (1/2) 24 pockets (2/3) 30 pockets (5/6) and 36 pockets (1/1).

So say you have a prediction fall off of  35 and a rotor time period of 4.5 secs per rev. This on some wheels is commonly 18 pockets,  1/2 the wheel. Immediately you should be thinking 8 opposite  35.  And know the numbers around 8. I would bet splits in the tiers here to cover numbers quickly. 10-11 5-8 27-30 30-33 33-36 5-6  23-24 are bets you can consider. You may not be able to get them all down, but covering 5-7 numbers is good.

Or you can call out 8 and the neighbours by 5 or whatever.

But basically each spin (for me):

1. Rotor speed
2. Prediction  (35)
3. Landing (8 )
4. Bets around landing (8 )

Knowing the wheel gives you steps 2.5 to 4 in a second or so.

You are playing the role of the computer, so this is where the work comes to make those calculations fast.

[The General]

Thanks Ego for a great post.

It's worth anyone reading studying all these posts in detail.

What will work for one person will not suit another. Most VB players have their own ways of doing things, but choose a system that works for you.  You can borrow a bit from others and add your own stuff.

The output from most VB activity is a fall off number on the wheel. Then for that rotor speed, which you will already have calculated early in the spin, you will have a bounce/scatter in mind. This figure depends on the wheel type and the rotor speed.

Common bounce/scatters for a low profile wheel are 12 pockets (1/3) 18 pockets (1/2) 24 pockets (2/3) 30 pockets (5/6) and 36 pockets (1/1).

So say you have a prediction fall off of  35 and a rotor time period of 4.5 secs per rev. This on some wheels is commonly 18 pockets,  1/2 the wheel. Immediately you should be thinking 8 opposite  35.  And know the numbers around 8. I would bet splits in the tiers here to cover numbers quickly. 10-11 5-8 27-30 30-33 33-36 5-6  23-24 are bets you can consider. You may not be able to get them all down, but covering 5-7 numbers is good.

Or you can call out 8 and the neighbours by 5 or whatever.

But basically each spin (for me):

1. Rotor speed
2. Prediction  (35)
3. Landing (8 )
4. Bets around landing (8 )

Knowing the wheel gives you steps 2.5 to 4 in a second or so.

You are playing the role of the computer, so this is where the work comes to make those calculations fast.

Good post.