He can test all levels and compare them.
Level 3 is an average.
4 would be the most accurate but not very practical for real play even some people claim they use it.
I think it is not hard for you to figure it out that accuracy and remaining time are enemies. If one goes up the other one must go down. Accuracy 3 would be minimum in practically acceptable remaining time, on an average wheel.
I am happy that he is getting better results.
I think you guys are having overconfidence problem.
Dr. Spock,
I am already in the books but for something else.
World best practice in achieving the best continues improvements within one of world wide Telecommunication Company. Developing test processes for better efficacy of product testing and reducing system brake down times. That work helped the company to receive various recognition awards. Now imagine me with my broken English holding presentations in front of few hundred managers from various companies.
Do you know what I got for that?
Peace of paper and key ring. I looked it, lift it up and asked “do I go with this key ring in a bank to pay my bills”
You are right about attention.
I never planed to have such open discussion.
If you look back you couldn’t find even single picture of FF at my site.
Only recently I placed some, including public video because some fags that like to call themselves competitors already did it. I do not care if they did publish video of their system but they did mine as well. Lucky or unlucky coincidance for me was that the FF simply can’t predict wrong even if you try to (if the wheel is predictable).
I didn`t mean to imply that it is a bad thing to mesasure in milli secs. What i was trying to say, is that if X device sometimes fails with X nano sec. you will only get the full “failure picture” if you test over several hundreds of spins.
Example: My VB gives me a “Remaining ball run time from prediction” of around 9.2 secs. before kollision with a diamond, 10 spins might look like this:
there are several spins where the ball is not going to collide where it is supposed to. The impact of those “lose stray” spins has of course an impact on the overall picture, but depending on your betting pattern and depending on wether some of the strays is creating a secondary peak that you might be able to cover using split bets, you don`t really know how much effect the strays is creating.
Same goes for the the mythified dealers signature. The dealer can anytime he wants screw up 5 - 10 spins if he wants to have a little fun with you, but if the remaining 90% is done with a drop zone, consistent wheel speed, consistent amount of ball revoloutions, there is going to be an imbalance. Personally i have booked dealers who created data that went out between 4 - 6 standard deviations (as i recall it) and lately i saw a sheet from a wheel/dealer that created a whacking 12 standard deviation over 4200 spins, not booked by myself though.
I also didnt mean to imply that i have made even remotely the same amount as Kaisan. Kaisan started out at a time where there were more opportunitys than today. His mistake were, that he didnt really go undercover but just whacked the casinos for as much as possible. So when Casino Austria barred him, it wasnt just a few casinos in Austria but the entire chain which covers more than 100 casinos all over the world. He is just about as public with his play as the open discussions in here,(his modus operandi is still a well kept secret). Look where it got him to. Today, there are still opportunitys. But they wont let him near them. His world has become extremely narrow, because the wheels he has access to, are really not playable using VB.
Using mobile phones or PDAs might be impractical because they are so “proprietary”. You’ll never know what’s going on in them. Their OS are not as well documented as an ordinary windows. And even the hardware is undocumented. This is not good for real time applications.
I would suggest two alternatives:
One is the UMPC, Ultra Mobile PC. These machines are like PDAs but more powerful and best of all, they run ordinary Windows or Linux OS! Whatever you can do on a stationary PC or laptop, you can also do on the UMPC. You have great real time control over it. And the development process might be facilitated by this uncompromised PC-compatibility. Drawback is that most of them are still today a tad too large. And the fastest ones can get too hot to have running in your pocket (they have no fan so they are quiet). But I think we will see improved products already this and next year.
The other alternative is a Java stamp. There are several around, live Jstamp or Javelin. These are small one chip computers which are Java programmable, which facilitates development process compared to a machine coded PIC. They are far less powerful than a UMPC, but it should be enough for your needs. I think it time resolution on I/O shorter than 1 ms. But chekc it out. And make sure that there is no Java garbage collection going on which can sabotage real time performance.
By the way, what would the goals be with using a new platform?
PS
I am in no way an expert on devices such as those I’ve mentioned above. But I think they are worth while to seriously consider. Since phones and PDAs do not allow total control, all development work made on them, might turn out to be compelety useless. Timings could be randomly unreliable because of undocumentedprocesses running in the background and the provider will not be helpful with information. They are very high risk platforms, IMHO.
I did look some java stamps, but that wouldn’t benefit me much. So I better use my design.
That vibrator may be interesting, but in usual they have slow response time.
Still it may be worth testing it. Thanks for the link I may get one to test it.
Actually I better send the link to ABC he may like it for his experiments
Since I am now retired at the age of 43- - I will dedicating the rest of my life on how to master the roulette wheel. So if i can ever be of any assistance THE CAUSE just kick me an email on how I can help. abc, kelly, mike, yourself and several others are a very strong knowledgable group we can all grow off of to build a nice strong foundation.
I will purchase your system on March 1, and look forward to mastering FF. Once I master your system I will start sharing my experiences and ideas to all other members here. I have all ready traveled all over the world and do just about all there is to do - - -so at this stage in my life I expect to get things moving real fast since I can dedicate up to 16 hours a day - - -7 days a week - --learning how to master FF- - -especially since my kids are all grown now up now.
Thats true. The main benefit would be to simplfy development, but you already have a working piece of code. And a stamp would hardly be capable of communicating with a voice ear phone, if that is one of the purposes with changing platform.
That vibrator may be interesting, but in usual they have slow response time.
Oh?! But the respons time should be the same every time, and should be easy to adjust for by using that mich time offset.
It doesn’t have to be that response time will be the same.
1 response time of vibrator
2 response time of person to vibration.
Once vibration starts it could be at least for some time even if we remove power supply.
Finally I made all agreements with Java developer.
We will try to do it on mobile phone / PDA.
I will make small draft of program just for ball clocking, for parameters of only one spin.
Then do the test to find out if timing can work. That will take only small fraction of time needed to complete whole project but it will tell us if it is possible to do it that way or not.
This week I have a visitor from overseas so I will be busy.
[quote=“Forester, post:47, topic:169”]It doesn’t have to be that response time will be the same.
1 response time of vibrator[/quote]
THis must always be the same. Java code running on a mobile phone might stop and go randomly without your control. But between a PIC and a vibrations motor, things will always be exactly the same everytime.
Btw, one bets over several neighboring numbers, so human reaction time cannot be an important problem.
I wish you good luck with the java on PDA/mobile phone tests! Hopefully they have sped up so that timing errors are acceptable. And aren’t there some open source linux phones around?
my brother has been a java develper and programmer for the last 20 years. He is one of the best java specialist in North America- - and I am very proud of him.
It’s always good to get atleast 2 profesional opinions on any major project- - - besides He’ll do anything I tell him to do because he is my little brother.
Is there any specific questions I can have him answer or tests that I can have him conduct?
He’s the closest thing to perfection and thouroughness on every java project he’s worked on the last 20 plus years - - - that’s why he’s one of the top and most sought after java developers in the whole country. He’s such a genius that I would bet the bank that he could build a roulette computer from scratch- - - and finish the entire project in less than 1 week. THAT’S HOW GOOD HE IS…he was a mentally gifted studed his entire child hood listed under Who’s Who in America.
The only problem is that he’s currently involved in about 20 different java projects working with mostly fortune 500 companies. He’s currently working about 100 hours a week devoted to these various projects. It’s a good thing that he’s my brother - - - that’s the only reason he’ll find the time to do as I ask him - - - because if he wasn’t my brother, than he wouldn’t give me the time of the day since he all ready have a full schedule.
For him - - TIME IS MONEY - - - since his going rate is $1000.00 US dollars per hour . That comes out to about 40,000.00 US dollars for 1 full week of work which he always get paid upfront before he even steps in the front door. He averages about 100 hours a week under his current contracts, so I’d say he’s doing pretty well. BUT I GET EVERYTHING FOR FREE SINCE HE’S MY BROTHER.
My master plan was to eventually have my brother build a roulette computer… which would never be put up for sale under any circumstances - - - but only for my own personal use. He’s to tied up right now to work on such a project — but he does currently have the time give me his professional input to anything pertaining to java development.
He’ll cut back on his hours during the summer to a regular 40 hour work week and that’s when I plan on having him start building the best roulette computer ever on the face of the earth known to mankind. 8)
Wow… can he walk on water too? No, seriously you are obviously very proud of your brother’s skills and abilities but may I suggest the following before you impose upon the guru’s time… download Avidemux and run the various videos you have of roulette spins… then at the precise moment the ball impacts with whatever number on the wheel/rotor then note carefully where the ball finally comes to rest after the effects of the scatter. You see… the ‘impact point’ is the only point the most sophisticated device will be able to identify the rest is ‘in the lap of the gods’. The test I have suggested you perform will yield some very interesting (and positive) results however we will never be able to achieve such a standard of excellence in real play with a hand held device and manual clocking…and that doesn’t matter whether you use your toe, tongue, finger or d**k to push the button… but we can achieve a proportion of what that test will give… our results in real play can never be as accurate as the results achieved by stopping the video and identifying precisely that ‘impact point’. It doesn’t matter what device or how brilliant a programmer or electronic engineer you are the results achieved can never exceed the results obtained by sitting at your desk and comfortably stopping the video to identify the ‘impact point’… so get real… get the FF… it is all that can be done in reality to identify that ‘impact point’ a reasonable number of times during play…
I agree with you pj, thats exactly what I intend to do. Everything else I am doing is more of a side project. I feel that in another 6 months that my VB skills will be up to par - - and combining my brother’s java skills with my VB skills we would make a great team for creating a device to beat the wheel. In the meantime, I plan on starting a collection of the best and brightest devices known today for beating the wheel. My first stop will be the FF and learning how to master that.
My brother could take a device like FF, and within 1 weeks time let Forester know exactly what are the best steps necessary to turn into a more powerful unit - - - and also the best way to add audio without compromising it’s accuracy.
@Mike
re your point #1… we can, but there will be errors…
re your point #2… I absolutely agree…
re your point #3… there is no doubt that the big teflon ball is the best for us… (you need big balls for this game)
re your point #4… I am lost on this one… but I can envisage some effect by those conditions… but how in the hell you can figure it… I don’t know
re your point #5… the search for the holy grail continues… but I don’t think Barnett will offer any solutions.
For me the jury is still out on that one… so I’ll wait for Spock’s bro to write the code for the algorithm… and I do hope he doesn’t forget to factor in the draft from the various air conditioning ducts… especially at Launceston.
According to mechanics, air pressure affects the air drag. Air drag is of course the dominating force on the ball early when it travels at high speed. If ball speed is measured early on, then it can be a real factor. And air pressure CAN shift substantially, for example with the opening or closing of a window, so I would not rule out that variations in air pressure alone could make the ball hit another diamond. It would be very nice if someone with a real roulette wheel could tests this issue! Make tests on two extremes on the barometer.
I guess that a way to deal with this issue practically, is to simply choose a roulette wheel where air pressure is fairly constant. Maybe one should bring an air pressure measurement device to the casino, which logs measurements over time (or read it manually now and then) to see. I don’t know anything about such gadgets and I’m not sure how weather changes compare to indoor climate control equipment in terms of air pressure. But constant conditions can never be bad.
So:
In laboratory settings, figure out if air pressure matters noticably. And if it does:
Strive to play in similar air pressure to increase predictability.
Bad news, I just have hared that some guys were caught with laptop and laser device, I think it was in Sweden. I do not know did they play leveled or tilted wheel but they did make some progress. So what could be excuse for using such equipment in casino?
During my tests I tested only ball clocking and how the FF handles that.
In usual 8 out of 10 spins it was within one pocket.
I am still not sure if java is capable of doing the job, but I will find it soon.
I really would like to do it that way because it may open additional options without much effort, display settings and easier Bluetooth control.
Roulette prediction needs solutions more then knowledge.
