FF versus Mark Howe computer

[Ptblltrader]

I have a question for ABC:  He says

With FF I had my first calibration after 10 or 15 spins. My first prediction was after 30 minutes of clicking! It frighten me and give me only pain, I did not even notice predicted number!
What does it mean?
MH takes every data as calibration.
FF takes only timings which are very close to default, which "makes sense" for the system.
Same during play; MH tolerate "strange" ball timings.
Strange means that I click earlier then later then again earlier during following ball revolutions.
FF needs exact on time  ball timings. Before I learned clicking FF shows me permanently 3th finger instead of prediction.

How did you 'learn' the clicking?   Do you mean just practicing?  What were you doing differently about clicking that you changed so that you got more predictions?


Thanks for your insight.

Ptblltrader

[forester]

ABC can explain what were his problems at the start and how he solved it. 

I can only highlight why FF would predict less spins then what is should do.

Theoretically FF on standard wheel should predict every spin.
If spin is not predicing, there is a reason for that.

FF is designed to work within specific limits.
That limit is based on time differences in between rotations and it is 120ms to 255ms.
Sure it can be done wider but there must be a limit somewhere. Wider limits will make system less accurate when doing different tasks during calculations.
Standard Huxley wheel which you can find in most casinos is about 180-200 ms.

So there is still plenty space for different wheel or errors in clocking and for difference if time is taken at different moment of spin. There are different controls for prediction and for what system will learn and save from spins. Limits are also changing based on ball speed. If we look one rotation at 1.00 sec per revolution the difference to previous rotation will not be same as if we had time of, for example, 1.200 sec. We can't even estimate it, we can't use one spin to define it, and we can't even say will it increase or decrease. Because it changes. My first attempt, E5, used earlier prediction and depending on a wheel I was using, system was increasing. So all of the system was based on that. Nothing wrong except if you come to a wheel where that is not the case. Ball deceleration changes and we do not know when and by how much, but IQE6 does, because it analyses all entered data and selects what is important then uses it to find even better results.
After some time it narrows limits to get the best from your clocking and decides by where in time of spin you are and how much limit is allowed for prediction.

I found out why I started getting less predicted spins. But I am not sure was that part used in that format on old chip and when did I redesign those parts of program. Basically limit was set to tight allowing only +16 or -16 ms for error in clocking. It actually should be 32. It was 32 but I changed it to different way of calculation and due to that it actually becomes only half.  Dependently how error is created the system should reduce it to zero or close to about 10 ms.  If it is 10ms it may result in 2-3 numbers of errors or system will not predict. With some tests I disabled wheel calculation to test only ball clocking and test showed more then 50% spins where within single number. So from that we have errors in rotor clocking and small error in revolution when system positioning ball over predicted number. With all together system most of the time stays within 3 numbers of accuracy. Can't wish better then that, remaining is only to find wheel where deformations on track (or slight tilt) wouldn't affect ball so much and where randomness of scatter is lower.

Another reason.
If wheel has much slower / faster deceleration system may still predict, some spins we catch ball at 1 sec and it may be out of limits but maybe when ball is slower deceleration comes within FF's limits. So we get only some percentage of predictions.

And last reason is of course really bad clocking.
I consider myself average clocker; I could run 100 spins (hand clocking) and get prediction on all of them.
That is why i was suprised with recent 70% predictions.



We really do not need such accuracy because final result is not so much dependant on that.
If we have 100% accurate system predicts as this. Where zero is prediction to rotor hit
-4
-3X
-2X
-1X
0 Xxxxxxxxxxxxxxxxx
1X
2X
3X
4

Or the other one not so accurate and predicts as this
-4
-3X
-2Xxx
-1Xxxxx
0 Xxxx
1Xxxxx
2Xxxxxx
3Xx
4
5
After scatter we will probably have same result on the end.
On top of that we have deformations and diamond deflection which makes everything harder. But if you followed few recent posts with graph you will understand how much build up at same distance from prediction is needed that after ball bouncing we still have advantage. On some wheels it can be better then on my graph but on some it could be worst or close to nothing.

We can only predict based on detected ball speed (of course and rotor), if IQE6 can't predict on particular wheel that most ball hits to rotor have constant distance to prediction, nothing will predict that wheel. There are no miracles, voodoo, or whatever someone may claim.
It is very simple, if ball with particular speed every times ends up differently, prediction is impossible.
But also if ball with same speed hits rotor with not enough consistency, that advantage after scatter is applied will be lost. Even if still exists it would be so small and it will take us thousands of spins to find where it is. Until then parameters on the wheel will probably change and we can't take advantage of that.

[abcde123]

hello All,

Ty for your question Ptblltrader

There are several reasons;
1. Totally bad clicking I mean ball timing with errors which are higher than system can take. This is nothing to do but practice.  Now I wonder how it takes me such a long time to learn. Do not try after hard and busy day, and additionally after last night in casino! Unfortunately I did.
2. I started ball timing to late!
I.e. on accuracy 2 we should  get prediction about 6 revolution before end, so there is no possibility to get prediction when start 6-5 revolutions before, no matter how perfect we can do clicking.
3. I started ball timing to early.
When we start too early ball speed is too high for timing (especially for beginners).
Same error in distance produce much higher error in percentage on one rev. so system cannot take such a data.
4. bad switch and or bad switch placing. Problems with sweet - moisture and due to that electrical  connection between skin and switch circuit. If happens signal from FF disappear.

To avoid all 4 reasons you need some knowledge and practice.  Yes I mean just practice.
After poor results in casino I decided to do my homework.
Few hours on video spins was quite enough.
First I learned how to recognize best moment for starting ball clocking depends accuracy level, than just clicking.
I worked also on switch construction. This is nothing special and confidence, but I do not want to show it on public forum.

ABC

I showed my problems with ball timing when I started to use FF only to show differences between FF and MH.
I call it " stupidity proof factor ".  FF have it and it is very high, MH not.

[forester]

Thank you ABC,

Good points, I even forgot them.  I will try to explain a bit more. 

*2. I started ball timing to late!
I.e. on accuracy 2 we should get prediction about 6 revolutions before end, so there is no possibility to get prediction when start 6-5 revolutions before, no matter how perfect we can do clicking.

This is very important. When the ball is too slow, system will not predict.
System will think that you missed a click.
Clocking is good to start few rotations earlier, as ASD said after some practice you simply know when to start. When I play exactly as it should be played, I know that the system will predict. If before selected time you clock only one rotation, system will still predict but without error correction.  Result based on average still should be within 9 numbers.


Clocking too early.
Theoretically it shouldn't be a problem.
But if ball is too fast there is no point of clocking it; system will ignore most of clocked data; only last few revolutions are what counts. Data from ball faster then 0.750s per rotation is useless. Too early clocking can produce only unpredicted spin, if something is really bad in clocking like missed revolution.

If spin is too long, it is better to wait even for rotor clocking.
For example if spin is 25 sec and we clock rotor instantly.
We do have a lot of time to the end.
The system will calculate rotor deceleration, but it is never 100% accurate.
More time and we have higher chance for error. It would not be much but everything counts.
So we can wait almost 10 sec then clock rotor. 

*4. bad switch and or bad switch placing. Problems with sweat - moisture and due to that electrical  connection between skin and switch circuit. If happens signal from FF disappear.

You are good  .
It can happen. I noticed it few times.
It can happen that pulses get weaker if skin touches contacts on the switch.
If you look switch from the front there are two small metal parts remaining from pins I've cut. If they come in contact with the skin it may produce losses or reduction of signal. It will not change accuracy of device.
When I built first device after playing too long, it took me a long time to find reason why prediction shifts .

[forester]

   IP 85.167.178.215 glossboy, sawyer, devicetest

[Myrulet-admin]

Wondering who could be such idiot, publishing this

http://www.engadget.com/2006/09/17/roulette-cheating-gadget-may-be-legal-in-the-uk/

using my email address

LISTING DETAILS
category: Internet Services
description: Roulette Computers proved to be effective and can make thousands everynight now possible through Mark Anthony Howe, inventor and Maths Genius

 even that is not enough next is

Thank you for submitting to CAwebSearch.com

Your submission to the .CA Web Search Canada Search Engine is being processed. Upon confirmation, your site will be included.

Click Here to include your site.


Submission Info:
User Email: forester747@hotmail.com
Url: http://www.predictroulette.com/


Terms & Conditions:
Please look in your inbox for the .CA Web Search Member Newsletter (WebProNews), the world's most popular newsletter for eBusiness.

When submitting your site to .CA Web Search, you agreed to the .CA Web Search terms & conditions.

I received 50 emails from all search engines 
Someone desperately wants to be Forester

P.S.
On the end it was more then 500 emails.
Bit it showed me from which IP was registrant.
Same IP as Norwegian =Mark Howe
 
 

[PJ]

I found this on the net today... http://www.roulettecomputers.com/comparison.htm..  It would seem that Mr Slippery (sorry Stephano) is mimicking you Forester.

Cheers
PJ

[forester]

It was actually him who made that site first, I only added explanation.

http://www.rouletteplace.com/pages/roulette-computers.html

[Franki]

@ ABC

Did you send Nokia 6111 to Mark??

[abcde123]

No I did not.
- have no time (vacations then business duties )
- do not believe that can make sense.
- I'v got Nokia with dead socket for clicking switch which I repaired by myself. It means that I disassemble phone what was "forbidden" by Mark in manual !
To secure java application I moved it to other place, what is also "forbidden".
He claims that it is impossible in his phone.
It is only hard, original Nokia's communication socket bluetooth and infrared where mechanically destroyed.

I think to ship it anyway, than we will see what will happen.
abc

[Myrulet-admin]

[abcde123]

This is first HA I had in my hand, so cannot compare.
-Looks made by him, cables and protection with black resin are same like in switch which he supplies. Anyway looks really good.
-Looks like other loops in net.
-Require batteries. ( means ear piece ). I used it 3 times about 3-4 hours each time. Every time new batteries and after 1,5-2 hours replacement was necessary. I used only batteries which I get with HA set.
-HA works all the time, no matter if there is a signal-voice massage from phone. It transmit continuously also silence. In my opinion this is big disadvantage, makes it easy to scan.

abc

[survtech]

Hi

The hissing you hear in the earpiece is the amplifier background noise, the unit is a receiver, not a transmitter; there is nothing to detect unless the device is talking and even then the signal is very, very low.

You are much more likely to draw attention from your betting style and position at the wheel than you are from a random scan.

If you are clocking and betting (as opposed to a passive onlooker clocking and covertly sending you the data) it will send up flags if you are placing large bets or consistently winning.


Kind regards

survtech

@ forester

These devices consist of five parts; plastic shell,battery holder,amplifier chip, induction coil and transducer. If you take the components out of the protective plastic shell, they are very, very small, not much bigger than a small pea when bunched together.

I have earpieces made for me, they include a gain control which is adjusted by a jewelers screwdriver and are fitted in custom molded or generic shells; even with the shell and gain control they are still only marginally larger than their component parts. The battery is by far the largest single component, they are tiny zinc-air batteries; when you pull the tab off they start to lose capacity whether you are drawing power or not.

[forester]

I never worked with HA, of course I do have idea how they work.
I asked simply to know if Marks HA is specially made for his needs.
For induction loop we need only T- coil, not all system of HA with microphone and amplifier. I think HA can be made much smaller with simple solution of only coil without batteries. It would be easier to make it if we only need to produce noise such as "beep".
Power can be taken from magnetic field or RF.

[forester]

And....?

[forester]

I removed post, Charls  may be guys real name.

[Anarco]

Forester, I know this might be a little off topic, but the picture you showed when responding to Frank, was that perhaps Makarska outside of Split? It looks like that harbour.

[forester]

It's Dubrovnik, have you been there?

[Anarco]

Yes, I have actually. Beutiful old town. Spent many of my vacations in Makarska and Split so a visit to Dubrovnik was almost mandatory.

[forester]

I like beaches at Makarska Riviera the best.
Small rounded stones are better then sand.

[Kelly]

Question from player to player:

How do you manage to bet a 15 number sector ? A 3 number sector is easy, even if you haven`t memorized the numbers,  because you can in worst case scenario,  simply read the 3 numbers when you get the prediction.

Personally i get in trouble when i exceed a 5 number sector, with simply remembering which numbers to bet. We can make call bets up to 9 numbers but then there is still 6 numbers to be placed.

Is there a way to memorize so many neighbour numbers ?

How do you get time to do it ?

[mikemcbain]

Kelly one way is to practice memorising all the numbers around the wheel until you can count them off in both directions. Another way is to use the racetrack bets like the Tiers and just adjust the edge numbers.

[Kelly]

Ahh, smart one. That would actually make it reasonably easy to place a large bet. But you would need to learn  it backwards and forwards then. But it shouldn`t be more diffycult than learning the ABC backwards and forwards.

I don`t think i have seen any bets placed on the Tiers with adjusted edge numbers, but i could be wrong. I haven`t noticed it anyways. I might try it and see what the dealers has to say about it.

[forester]

I simply know all numbers, no matter which direction.
Sometimes I miss one. If the ball doesn't stop there it isn't problem, but if it does it hurts.
Guys who covering 15 pockets are playing orders which means placing 5 units on number and it covers additional 2 on each side.

[Fatgambler]

Question about neighboring bets. I saw at a online casino that they had this neighboring bets chart. Does it exist IRL?