Here is one problem, about which Forester say only by one sentence. That is human mistakes in clicking swich. I have some program with which i can measure mistake which i do when i click. Of course some peoples have better sense and make smaller mistakes other do biger. But still they are big enough that our prediction can varry very much only because them. And we make mistakes when we do setup of system and make mistake when we measuring ball and rotor.
Mistakes in measuring rotor is not super sensitive but in measuring ball they can be very essential. I done many tests on that, measuring diferent intervals and found that reall mistake for one interval so two clicks is in averidge about 60ms and that is absolute mistake so it can be to one side or to other. I read many articles about human reaction so acordingly them human reaction to unexpected even is about 150 ms. when we click for ball or rotor we expect that event when ball will be in particular position but here is also neuronical signal time from our eyes till hand to press. So i determine mine reaction as about 60 ms what is not enough to get right prediction.
But when we measure more ball rounds in two clicks and after do some calculations for finding something like averidge we can get much better results. From mine experiments when i click 5 ball rotations as one i can determine duration of last round +/-10 ms. And main part of clicks will be in range about +/- 3ms. That is good but time for 5 ball rotations is big and we almoust never will have enough time to bet.
Thanks Mike,
Probably there is some improvement but sometimes I just spend more time with something I write then it looks better :D.
@ rremoroulette yes it is but it’s not my mother’s tongue.
As much as I was good in learning science I was far worst in learning other languages.
After 8 years studying it in Croatia last year professor told me “I’ll pass you only because your all other marks are the best Ï hope you’ll never need English in your life.”
Actually my English was better before then I met Mike, at that time I used it more, and had to write a lot for school and work. I finished here 4 years electronics eng, and did 2 years operational management (just to improve English).
At work I use to have a nice girl when writing test procedures she was fixing mistakes I make. When talking I also have strong accent, but still when we won Australian Quality Award as a team leader I was having presentations in front of few hundred of managers.
Then for few years I didn’t write anything in English, since it wasn’t my strong point I forgot half of what I’ve learned before.
@ bebediktus
There are mistakes but not so much.
I doubt your program especially if it is made for PDA.
I suggest you take programmer and read clocked ball set rotations from FF, you’ll see the difference.
With 2 ball rotations clocked mistakes should be most of the time under 10 ms.
If it is not enough then clock 4 ball rotations, the Acrobat will use all 4 when predicting second time.
I understand what are you saying, if one rotation is clocked 30 ms longer , then next one is starting 30 ms shorter , if last click is also clocked 30 ms shorter then it may make 60 ms error.
For same reason I was laughing when Stefano showed his video where predicting leveled wheel with a single ball rotation clocked. FF even is far more accurate in measurements then a mobile phone never used a single ball rotation to predict.
Fist I thought my clocking is very accurate, it looked to me as that but when I tested it on method probably similar as you were doing I found out that it is not so accurate. Expected mistakes could be up to 30 ms but the FF never uses a single rotation when playing or when looking for samples.
The FFA –Viper when setting gives feedback about clocked ball speed. It is after correction, most of the time it was under 3 ms.
Here is the test for you.
Set the FF-Acrobat on a single spin, only one sample.
Set accuracy to 5 and play.
Try to predict 4-5 rotations to the end of spin.
Assuming the ball rotation is about 1400ms/r the ball moves 38 ms per pocket.
Now predict same spin at same time but do clocking 1 pocket to the right, then 1 pocket to the left. If you get it predicted your clocking is fine and the total error is under ~10 ms.
Yes i will plan to buy programer to see what i clocked, i done similar tests on video in calm situation all is perfect but in casino i usuall feel himself that i do setings not perfect and when clocking ball i also feel that they are not perfect.
If you can do the test it means your clocking is reasonable.
The system doesn’t have a fear sensor to make a compensation for clocking in a stressed environment.
Only joking.
You look to me as someone who plays a lot and the FFV is not your first FF, so you should be stress free. You need to find out why it is that you feel that way. I can only assume it is because of results you see.
If you are not getting results with the Acrobat sure it can be because of bad clocking but also because of many other factors. If the time differences in between rotations are smaller then of course it is easier for the system to make a mistake, especially if you are predicting earlier during the spin.
The Acrobat is equipped to predict individual diamond but there is always limit what can be done.
Let’s say until the ball is 1.2 sec the ball is slowing down 7 pockets/s^2. (7 pockets in a second on a power of 2)
While the ball deceleration is reasonably constant the time differences in between rotation changes exponentially. While at some place during the spin you can have one rotation 0.8 second and next one 1 sec with nice difference in between of them of 200ms; at the other moment you may have one rotation 0.5s and the next one 0.52s where the difference is only 20 ms.
You can see the time of rotation is about halved from 1 sec to 0.5s but the difference in between rotations reduced 10 times ; from 200 ms to 20ms. Such reduction is negative for predictions since the difference is what the computer uses. 20 ms is really not much, if you get right ball rotation that’s still something but you can forget about getting the right diamond each time. With later prediction your changes are increasing, after the ball passes one second per rotation the ball deceleration may drop, but it doesn’t matter since the difference in between rotations still is reasonable for a decent prediction.
Yes i will plan to buy programer to see what i clocked, i done similar tests on video in calm situation all is perfect but in casino i usuall feel himself that i do setings not perfect and when clocking ball i also feel that they are not perfect.
Excluding the fear clocked spins in casino are always more accurate then clocked spins from recorded video.
• Single dominant diamond,
• Only two dominant diamonds,
• Two dominant diamonds,
• Three dominant diamonds.
I’ll explain for each situation how roulette player can gain an advantage and win but the first brief description of roulette visual prediction methods.
How it is possible to visually predict a roulette wheel
In the post, you can find information from primary simple dealer’s signature to various ballistic visual prediction methods.
Traditional roulette visual prediction explains how to identify a particular ball rotation during the spin. After that it’s easy. Dominant ball drop point provides information where the ball will drop. Only what’s left for the player is to define how the rotor will move for the remaining time of the spin until the ball hits the DD. Knowing it the player will also know at which number the ball will drop.
If you need a more detailed explanation for example how to identify particular ball rotation during roulette spin, I would recommend Laurance Scotts material.
• Professional Roulette Prediction: Volume 1 — Basic Methods
• Professional Roulette Prediction: Volume 2 — Advanced Methods with Roulette Analyzer™
In the Volume one, Scott explains cross patterns, while in Volume 2 he explains visual and acoustic as a method to identify particular ball revolution. Of course, his package includes much more than just a simple explanation.
Another interesting method to identify a particular ball rotation and the best moment during the spin, when is the smallest chance for mistakes I’ve found in material from masteroulette.com. Such method was used for years by top VB roulette players.
In VB2 forums section, I explained similar method using mobile phone vibrating timer.
Roulette wheel with a single dominant diamond.
missing roulette image
On the right-hand side of the picture an example for such wheel is highlighted in red. Most of the ball hits are at the top diamond, there are few hits on the other diamonds, but from a perspective of an advantage player, for now, that can be ignored. What happens if the ball doesn’t hit main dominant diamond (DD) I’ll explain on a different example where such diamonds are getting more hits.
Tilted roulette wheel with a single dominant diamond provides the highest and easiest chances for an advantage player. You already learned how dominant diamond is getting grouped wider range of different ball speeds then of course if there is only one diamond getting most of the ball hits the ball speed range is the widest making it easiest for an advantage player to predict it.
Roulette wheel with a single dominant diamond can very successfully be predicted almost with all advantage player methods.
How roulette visual ballistic player would predict it?
VB player will, for example, identify 6th rotation to the end of the spin, at that moment read number under the diamond. Knowing there is remaining five ball rotations until the ball drops. They can convert five remaining ball rotations to time, for example, it could be 8 seconds. If the rotor is moving 4 seconds per rotation, then they know that in remaining 8 seconds the rotor will make two full rotations and at the moment when the ball drops there will be the same number they noticed just after the 6th ball rotation.
Visual players don’t have to identify 6th ball rotation every time, sometimes they can make a mistake but since the payout is 1:36 they will be ok if they do it correctly most of the time.
How a roulette computer player would predict it?
Since this is the most comfortable condition, many different approaches would do the job.
Roulette wheel with a single dominant diamond; group’s full range of ball speeds to hit at a single diamond. For example, the ball speed may be even 200 ms different, travel the same amount of rotations and still hit the same diamond. Because of so wide 200ms range, it is relatively easy to predict such wheel with a roulette computer even, some well programmed mobile phones or PDA’s can reasonably predict it. (Such devices may make just in time measurements mistakes as 20 ms but because the ball speed range is much larger as 100-200 ms; 60-80% of spins still may be predicted well. This doesn’t include additional possible errors on the wheel or human clocking but purely errors created by the inaccuracy of time measurement)
Method 1
The simplest way would be to program the computer in this way.
Set the time frame for example 1200-1400 ms to identify particular moment during the spin.
Set the remaining time from the moment until the ball drops, for example to 8 seconds.
During the spin, the player first clocks the rotor to get time how long it takes the rotor to make a full rotation. Then the player starts clocking the ball, each time when it makes a full rotation. The computer measures the time of ball rotations. For example, first ball rotation may be 800ms, then 920ms, 1100ms, 1300.
When 1300 ms ball rotation is clocked the computer identifies it within particular speed range (1200-1400 ms), it uses 8 seconds remaining time and rotor time to calculate how much the rotor will move until the ball drops at the dominant diamond.
Pros:
Since this is a basic method, this approach may only produce a bit more stability comparing it to the visual ballistic player. A roulette computer doesn’t get tired, but a VB player still keeps the greatest flexibility.
Cons:
Prediction always at the same moment during the spin, it can be suspicious. If the dealer starts calling a bit earlier no more bets the player can’t have earlier prediction since his time of prediction is defined by time frame he pre-set.
Same as the player can’t predict earlier he can’t predict later. For example, the dealer may start spinning short spins, after clocking rotor the ball speed may be already slower then defined in his time frame.
The player has to clock to many ball revolutions to get to the ball speed which computer can handle.
The player never know what to set for the time, he may set 1200-1400 trying to get 6th ball rotation, but the 6th ball rotation may be from 1260 to 1380.
Even amount of remaining ball rotations until the ball drops may be the same, it doesn’t necessary means that the ball will complete it at the same time. Since a wide range of different ball speeds is grouped to hit at a single dominant diamond, different ball speeds take different times to complete remaining rotations. The difference in time on 5-6 remaining rotations cam reach up to one second which on a rotor spinning two seconds per rotation would create 18 pockets error.
Method 1 approach; you can see on videos published by Stefano from genuine winner site.
Method 2
A better way of prediction would be with programs as Michael Barnett from survtech.com has created.
It is similar to the previously explained process, but also Michae,l has a special way how to determinate where and how wide the time frame for prediction should be.
Pros and cons are the same except point 3 because the time frame can be precisely adjusted.
In a similar way and roulette program Viper from myrulet.com for the FFA works. The Viper has some additional important options for more realistic casino conditions.
Pros:
This method can very accurately predict a single or only two dominant diamond wheels.
Cons:
Prediction always at the same moment. If the dealer starts calling a bit earlier no more bets the player can’t have earlier prediction since his time of prediction is defined by time frame he pre-set. Also constantly predicting in the same moment during the spin is not very covert.
The player has to clock to many ball revolutions to get to the ball speed which computer can handle.
Even amount of remaining ball rotations until the ball drops may be the same, it doesn’t necessarily mean that the ball will complete it in the same time. Since a wide range of different ball speeds is grouped to hit at a single dominant diamond, different ball speeds take different times to complete remaining rotations. The difference in time on 5-6 remaining rotations cam reach up to one second which with a rotor spinning two seconds per rotation would create 18 pockets error.
It may require many spins to set. For example 10 for each ball direction.
Method 3
Unlimited roulette computer program.
A few years ago we came to an idea to try to predict roulette spins but in any ball rotation.
Myrulet VB2 was created which compared to traditional roulette visual prediction is the only one method capable predicting in literally any ball rotations.
In parallel line with it, we managed to create and Unlimited program for FF roulette computers capable of predicting at any moment during the roulette spin. This was possible to achieve with good accuracy only because FF roulette computers have the most accurate hardware for time measurements. For the same reason, the FF computers are the only one capable of predicting at any time and multiple times during a single spin. It allows the players to actually test the quality of predictions at any desired moment during the spin, to get as many predictions as they like with any amount of ball rotation clocked.
There is a lot of rubbish selling on the internet under the name of a roulette computer. As usual, it is just a Java application for mobile phones, which by the look or it’s performance is not a match for covert very small and accurate professionally made roulette computers. Of course, they trying to hide stuff like this; knowing their product will struggle to predict the same spin even at same moment during the spin but the FF roulette computers can do more, and we are not afraid to show it and to let the users have it.
Pros:
This method can accurately predict a single or only two dominant diamond wheels.
It provides to the player flexibility to predict at any moment during the spin, therefore, calling earlier no more bets wouldn’t affect the player. Without any adjustment, they can simply start predicting earlier.
The unlimited system doesn’t require many ball rotations to be clocked. When players using Unlimited system (FFZ/V) they clocks every second ball rotation, it gives them much time in between to look around, so they don’t appear stare on the wheel.
More time in between clicks is good since the player can better prepare for next click for example if they are clocking very short, early ball rotations during the spin. It is also valuable if foot clocking is used.
Need more accuracy? It’s not a problem clock additional two ball rotations, and without any previous settings, the computer predicts again this time with a time of four ball rotations used.
Possible very early reasonably accurate predictions.
The Unlimited is very easy to set. While Method 2 may require many spins to set appropriately, the Unlimited can be set with a single spin, and if there is a change on the wheel, it can easily be readjusted.
On the video, you can see ow Unlimited multiple predictions at any time during the spin are predicted with FFA roulette computer.
Cons:
It may not be accurate as explained Method 2 since the system can predict at any moment during the spin which of course is like shutting a target at 50 m range or 500 meters. Another reason; the set is not so accurate as with Method 2, allowing the slightly higher amount of spins to be mispredicted.
Method 4
The Acrobat
Anything that any of previously explained methods can do the Acrobat can do better. You can read about the Acrobat here;
[quote=“lucky_strike, post:13, topic:804”]Very nice topic and i like how you illustrate the dominant drop zone using a cross - simpel and clear - very cool …
Roulette wheel with a single dominant diamond is hard to find in the casino but not impossible.
I’ve played wheels where the ball would hit a single dominant diamond 80% of times. Sometimes such high hit rate is happening only in one ball direction while in the opposite direction the percentage of hits may be far less. From some people I know, there are wheels with almost 100% single diamond hit.
Is finding such roulette wheel a guaranteed licence to print money?
As far as I can say with a roulette game nothing is ever guaranteed, finding a strongly tilted wheel is just one of predisposition for roulette advantage play.
For example, the ball may be very bouncy so what would be the point of predicting where on rotor the ball drops; if the ball from that point can jump almost equally to any other position.
On some wheels, rotor speed is far too fast making ball jumps distribution almost random and very hard for a player to adjust for rotor changes.
The wheel may be automated where the rotor speed is changed during the spin after no more bets were called.
Some wheels have inbuilt random rotor deceleration making rotor to decelerate each spin differently.
No more bets (NMB) may be called far too early where the player will not have enough time to predict and to place bets…etc
One is for sure making money at roulette is proportional to conditions the player finds; skills and knowledge he has.
missing roulette image
On the picture in the top right-hand corner, you can see the distribution of ball hits when only two dominant diamonds are involved. Instead of writing explanation I made a small video explaining why and how is possible to take advantage in such situations.
Only two dominant diamonds on the roulette wheel as usual is created by reasonable tilt on the wheel when the highest point is on a horizontal diamond. Then two nearest vertical diamonds share the highest amount of ball hits. On such wheel, if the rotor is slow, an advantage player can get almost same results as on the single dominant diamond wheel. It is because such wheel creates an effect as I’ve explained in the video. The player doesn’t need to know which of those two diamonds the ball will hit therefore nothing additional is required to play such wheel. Any advantage play method can predict it with the same principle as predicting a wheel with a single dominant diamond.
Note; such scenario on some occasions if it doesn’t have enough tilt may cause the ball to drop mostly on a horizontal diamond positioned in between two dominant diamonds. Horizontal diamond hits may cause the ball to not directly drop on the rotor but to turn in to a spinner producing random results.
Example; comparing a single with only two dominant diamonds roulette wheel.
A single dominant diamond roulette tilted wheel
Somewhere during the spin, we measure the time that takes the ball to make a revolution.
After some measurements we conclude for example; when the ball takes in between 1200 to 1400ms per rotation it spins for additional five rotations, and it hits the dominant diamond. Knowing it; we try to define when the ball is at that particular speed range and predict accordingly knowing that from that moment the ball each time will travel equal amount of rotations and hit the dominant diamond.
Only two dominant diamond roulette tilted wheel
Somewhere during the spin, we measure the time that takes the ball to make a revolution.
After some measurements we conclude for example; when the ball takes in between 1200 to 1400ms per rotation it spins for additional 5 or 4.25 rotations, and it hits one dominant diamond. Knowing it; we try to define when the ball is at that particular speed range and predict accordingly knowing that from that moment the ball each time will travel 5 or 4.25 rotations and regardless which of the diamond it hits we would still get same results.
Obviously on a single dominant diamond, if the diamond is not getting 100% of hits when the ball hits, for example, a diamond after 5.25 rotations, we can easily spot it. With two dominant diamonds, we do not always count remaining rotations so we can know if the ball made 4.25 or 5.25 by observing the number when the ball hits the diamond and drops on the rotor. If for example we play visually and we notice the ball often starts making that ¼ of rotation extra making bad results for us; we would try to predict when the ball is a bit slower. Or re-tune the offset and play two diamonds with remaining 5.25 to 6 ball rotations.
The picture represents a wheel with only two dominant diamond hits.
Diamond 4 is getting 60 percent of ball hits, and the diamond one is getting 40%.
If we precisely measure ball speed somewhere during the spin, we would find that 1320-1400 ms mostly hits the diamond 1, and 1180-1300 ms are hitting at blue diamond 4.
Roulette computers;
Method 1 (previously explained)
Will set the time frame by guessing it then observe and readjust trying to get it right
Method 2
Will to set the time frame precisely probably a bit narrower to avoid some bad predictions.
Method 3
Unlimited would leave set when the ball is somewhere at the middle range as 1300ms
Method 4
The Acrobat would set few spins for each of the dominant diamonds, this way regardless which diamond the ball hits and regardless of rotor speed results will be very accurate. With previous methods 1-3 on a wheel with two dominant diamonds prediction results will be reasonably good only if the rotor speed is slow.
The acrobat will also reduce additional errors because remaining 5 rotations are not always precisely the same time that the ball travels.
For example 1200 ms/r ball and 1300 ms/r ball may travel additional 5 rotations and hit the same diamond but of course, slower ball will take longer to complete it. The remaining time difference can be even up to one second. It means the prediction may be wrong by up to amount of pockets rotor makes in for that time difference. With a rotor moving 2 seconds per rotation such error may be up to 18 pockets, on slower rotor it may be up to 10. The acrobat simply handles it better since it doesn’t use fixed remaining time but it calculates it for each clocked sample differently.
Very true statement about the single dominant diamond wheels not always playable.
Have an automated wheel in my neighborhood with something like 80-85% of the spins hitting particular diamond and still the early NMB and fast rotor(alternating from spin to spin between ~ 1.5 and ~2 sec per rotation) makes it near impossible to obtain an edge.Still had some medium success with DS on carefully selected rotor speeds though.
If you are not getting results with the Acrobat sure it can be because of bad clocking but also because of many other factors.
I know why that happend - the main problem is that the same speed can lead to diferent distances up to whole round. That is because of diferent manier of throwing ball. say one dealer 1200-1300 ms leads to some particular diamond, but on other dealer to the same diamond leads 1150-1250ms, so if i set on that first dealear and mine set for that diamond is say 1270 so not averidge and come that second dealer then i can misss very wide and not understand what happend. But if mine set is around say 1225 then it can be good for bouth dealers.
Yes, for same reason you always must have the knowledge where the ball is expected to drop and constantly observe it.
Because with the Acrobat you can adjust individual offsets it’s added to the system that you can mark it as an especial spin and expect something else. Without it you would play blind and it would take much longer to detect that if there is a problem or change on the wheel.
If previously described method 2 is used and defined time frame 1200-1400 and after some time the ball start passing the predicted point you could try to readjust the time frame to something as 1150-1350.
With the acrobat such quick fix would be to clock ball at a bit earlier position for example ¼ of rotation and add to the offset +9 pockets to compensate for the change.
With every program player must not play like robot. He must always look what happend and do diferent adjustments. Try something diferent aproach. One of them is clocking ball not in the same place where we do setings. I found few others variants how to play and how to do settings .
It depends on what do you want and expect form predictions.
For that reason is the best to have a clear understanding of what is really happening on a roulette wheel while the ball is spinning.
I prepared a small chart with ball rotation times.
First column shows different ball times in milliseconds until the ball makes a full rotation, second column shows what would be time of next ball rotation and third column shows the difference in between two ball rotations.
To get ” t2” time of second rotation a solution for solving quadratic equation was used where
“D” represents how many pockets per second the ball slows down and
“t1” is the time of first ball rotation.
D/37 which in this example is nothing more than a percentage 5 pockets from full rotation of 37 pockets. For example if you want to calculate it when the ball slows down 7 pockets per second on a 38 pockets wheel you would use 7/38.
Bottom line is that you do not need to understand calculation but only to understand results from the chart. For an advantage player the most important part is the time difference in between ball rotations. The greater it is the easier it gets.
The chart includes samples from 500ms to 1100ms.
I deliberately excluded slower ball rotations. The reason for it is that right after about one second per rotation on most wheels the ball deceleration may rapidly drop. For the same reason it is not recommended to predict in last 3-4 ball rotations since the differences in between rotations may be reduced. AP player wants to predict when the difference in between ball rotations is the highest. Reason why the ball deceleration drops is that the ball during spinning is actually touching vertical edge of the wheel. Later on the ball leaves the vertical edge and drops more on the bottom track, it is affected by slope on the wheel and even radius on which the ball spins may be slightly reduced.
Using the quadratic equation after the 1200ms ball the next rotation may be 430 ms different when in reality due to previous explanation it may be only 200 ms, which is actually a smaller difference then 285ms from previous example. In such case rotation with highest difference 1100ms to 1385ms we call “the knee point“ and during the spin it is easier to identify it.
On a single or only two dominant diamond wheel as previously analyzed ratio for this rotation would be 20>>265 . Or we can say due to inaccuracy in clocking from 28.5 spins, 2 spins will be predicted badly and 26.5 will be predicted well. This ratio is the highest and the best for AP player, on the chart is circled in green. If an AP player is predicting at this stage during the spin they have the highest gap for error and also can isolate particular diamonds to predict.
Next on the graph circled in blue is when the ball time is about 900 ms/r with difference to next ball rotation of 129ms. This is probably the fastest ball where the player would still have reasonable winning ratio, and some chances to isolate particular diamonds.
Circled in red is the fastest ball with a time of 500ms per rotation.
Here ratio is 2 against -0.2. It means the error will not be only as some percentage in between 2 ball rotations but significant amount of errors will be across 3 ball rotations. We can’t really have -0.2 since the difference of 18 ms always exists , many spins will be predicted in that range but by 20% more may be predicted in different ball rotations.
Accuracy of prediction across 3 ball rotations even may look bad in reality it doesn’t have to be so bad.
Considering that length of rotations is only 0.5 sec therefore and remaining time to calculate how much rotor moves will be wrong by same amount of time. If the rotor moves 10 pockets per second, difference of 0.5s means + or – 5 pockets error. Understanding that at this ball sped range even predicting particular ball rotation is inaccurate definitely there is no point of predicting particular diamond hits.
This picture may be interesting.
With blue color are marked ball rotations and with green the time gap for which that rotation can be accurately predicted. Circled in red is a rotation where the tolerance for an error is the highest. Compared to another point circled in yellow it is not much wider but here it’s important to notice that next to the yellow mark are and longer ball rotations with therefore if the prediction is in different rotations error is greater.
This is important to understand before then I explain next step, predicting more common and realistic wheel conditions.
All is good , but here is one nuanse - ball deceleration per second is not constant in the same spin and if we have some ball speed exactly the same in next and in all remaining rounds ball decelaration per second can varry quite much even if spins are very close each other in time - so conditions is about the same. So if we get say 1000ms one ball round then on next round ball deceleration can varry quite big so next round after exact 1000ms in first round one time can be say 1200 but in other it can be 1100 or other. So we never can know enough exact how long ball will travel till dropp and which distance it will makes. Of course time and distance varies in some frame, but from… till…
The point of examples was not to prove if the ball deceleration is linear or not, but what to expect for time differences in between of two ball rotations. You can see that distances in between rows of data is not a length of ball rotation as we usually use, but it’s constantly 100ms. You can look the chart and get information for example when the ball is 900 ms , the difference in between rotations 130 ms. If playing a wheel where the diamond getting 50% of hits it means you have a gap of 65ms to get it right. If predicting same at 1 sec/r ball it would be 95ms.
Stefano wrote referring to FF program and capabilities to have multiple predictions;
“You may have heard a roulette computer that gets predictions anytime in the spin by assuming the ball deceleration is linear is a great thing. After all, someone sells such a device so they publish rubbish to sell their product.”
From education Stefano has only high school finished but regardless in luck of his education it is a matter of logic, and common sense. For that reason he can be understood only as someone attempting to discredit such program for whatever personal reason he has.
If the FF computer assumes the ball deceleration is a constant how on earth the FF predicts correctly at any moment during the spin. It would be possible only if the computer predicts differently than what he assumes; or if the ball deceleration is linear. Reality about FF program is [hide]that it uses ball rotation samples and predicts accordingly whatever the ball deceleration is. The FF has multiple prediction simply because it’s very accurate so it can.
On the video the computer predicts for example 26 0,0,0,0,32 it is only plus or minus one pocket difference for predictions in six different moments during the spin. Such small difference only shows how beautifully the program follows the ball deceleration curve. One pocket error is possible even if predicting at same moment during the spin. One pocket deviation is not much for all errors during clocking, calculating ball and rotor movement and on top of it for defining curve how the ball decelerates.
What you are saying is correct;
of course the ball may differently travel during the spin. AP player accepts it, the point is that there is always what is happening with the ball most of the time and to exploit it. Also to which point during the spin consistency happens most of the time. Because of such reasons I made the chart to explain up to which point during the spin is worth predicting particular wheel conditions. If the quality of wheel is so bad and from the moment when the ball is 1000ms/r the ball can travel so differently until it drops than obviously there is no point of predicting such wheel.
We can predict only based on data we get during clocking and if there is a change after that moment we can’t do anything. I did a research for example spins where the ball is 1000 ms /r and what will happen if the next rotation happen to be for example 1180 or 1200 or 1220. There was no difference , while 1180 is the fastest ball it still can drop earlier than 1220 ms ball or vice versa. My findings are same as Edward Thorp got in his research.
Let’s say we have a wheel where most of the time after 1000 ms the ball next rotation is 1200ms. Then the ball travels mostly 6 rotations. Mostly 6 rotations could mean 60% 6 rotations until it drops, 20% ¼ of rotation shorter and 20% ¼ extra. After some time due to some changes on the wheel it may change that the ball mostly makes 60% 6.5 rotations. In such case instead of 1000-1200ms as the most common rotation after 1000ms we may find 1195ms.
To use 5 ms difference on 2 rotations to make adjustment for additional half rotation (+ rotor movement) may be 30 pockets difference it would be a suicide. If first rotation you clock 2 ms shorter and next one as it is 1200 it would be already 4 ms error since for next one its expected 1198. So only 2ms wrongly clocked ball rotation would create ~25 pockets error.
Even one ms accuracy in ball clocking wouldn’t be good enough to make such adjustments. If predicting same spin 10 times each time it would be predicted differently. On top of it process to define adjustment would be close to imposable since we can’t just say for 5ms difference just add 1/2 rotation, since the real value is unknown and it depends on many factors. To be defined the player would need thousands of spins clocked with extreme accuracy.
[/hide]
Let’s say we have a wheel where most of the time after 1000 ms the ball next rotation is 1200ms. Then the ball travels mostly 6 rotations. Mostly 6 rotations could mean 60% 6 rotations until it drops, 20% ¼ of rotation shorter and 20% ¼ extra.
Here we come to that about what i talk. Lets say we set FF and think that ball will travell 60% 6 rotations until it drops, 20% ¼ of rotation shorter and 20% ¼ extra. But we not know what will be really in future , say near future when conditions are still exact the same. And maybe we set as 980 and next 1170 but we get say three spins as exact 6 full rounds after, but really in future, in long term this setting will produce only 30% 6 rotations until it drops, 20% ¼ of rotation shorter and 50% ¼ extra, what can give us very random results when we will play, and that is because of bad setings - not in the pick of speeds range which give us mostly exact 6 rounds remaining , but in the edge of range but we only randomly get good distances when we done setting.
Can’t wait more
