Break speed? Theres an app 4 that....

Paul,

Have an issue on my HTC XV6700 Windows Mobile 5. Soon as I click to start recording a break it counts down about a second, then goes to the error screen with "Unable to find a break (Try a longer recording)". This happens at the pool hall as well as inside with no noise.
 
hang-the-9 said:
Paul,

Have an issue on my HTC XV6700 Windows Mobile 5. Soon as I click to start recording a break it counts down about a second, then goes to the error screen with "Unable to find a break (Try a longer recording)". This happens at the pool hall as well as inside with no noise.
Click to expand...

I can think of two possible reasons for this.

Are you double-tapping the screen to start a recording? This would cause it to read the second tap as a stop command.

The other possibility is if your phone's internal storage is full, or if it is unable to write the audio to the temp file while it records. Maybe it is unable to write into the temp folder? Basically it writes audio data to the internal storage every second while recordinng. it needs shout 5.5MBps in order to record a full 2 minutes of audio, but that is only if you let it run that long.
 
I downloaded the free trial for my BB Tour the other day and I couldn't ever get the app started. The app basically froze up to the point where I had to go into my applications list, delete it, and restart my phone.

I'll try again eventually, I really wanna check this app out!
 
pnettle said:
I can think of two possible reasons for this.

Are you double-tapping the screen to start a recording? This would cause it to read the second tap as a stop command.

The other possibility is if your phone's internal storage is full, or if it is unable to write the audio to the temp file while it records. Maybe it is unable to write into the temp folder? Basically it writes audio data to the internal storage every second while recordinng. it needs shout 5.5MBps in order to record a full 2 minutes of audio, but that is only if you let it run that long.
Click to expand...

Only used one click. I tried both the stylus and my finger, and re-aligned the screen.

For storage, I have a nearly empty 1gig card, and have over 10mb out of 54mb system space. I just emptied out some local storage space, same thing happened. Goes to the 30 second record timer, and almost immediately to the error.
 
hang-the-9 said:
Only used one click. I tried both the stylus and my finger, and re-aligned the screen.

For storage, I have a nearly empty 1gig card, and have over 10mb out of 54mb system space. I just emptied out some local storage space, same thing happened. Goes to the 30 second record timer, and almost immediately to the error.
Click to expand...

hang-the-9,

I want to try a few things, but let's move this into email so we don't fill up the forums with support stuff. Could you email me? Hit the support link on our site, and you'll get a direct email link to me.
 
Me and Mika were one of the first ones to test that app at the BCA in Las Vegas and the fever was caught!!!!!!!!! And it is awesome. One thing that will be updated on the IPhone is kmh, right now only both mph and kmh are available on Windows Mobile based phones.
 
I used it on the iPod last night. Have a few comments:

1. I think the user interface for selecting the table size should be a "rolling wheel" instead of a slider. It would be simpler to use and more intuitive.
2. Its tricky to get the cueball position exactly right. I think everything to the right of the headstring should be eliminated. This would allow you to zoom in on the area of interest behind the head string, for more precise cueball placement.
3. When placing the cueball, I like that you have the table moving, instead of the cueball. If you had the cueball moving, your finger would be directly on top of it, and impede your vision.
4. There should be a physical stop at the headstring, so you can't move the cueball past it. This would make it easier to place, since you would only have to worry about vertically controlling the screen on the iPod.
5. Maybe a few common spots saved on the table and the user just double taps on them. For instance: rail break, end of box break, center spot break.
6. I don't know what patents are applied for, but you do realize, there is prior art of using sound on a computer to record break speed. This has been around for many years, and has been shown even on these forums how to accomplish.
7. When there is an error in sound detection, and one has to manually adjust the detection, it is very difficult to zoom in and manipulate the graph. I would zoom in a few times, and then as soon as I lifted my finger to adjust the contact sounds, the screen zoom went crazy.
8. Reiterate history, max, average, min, etc.
9. Overall a good first version.
10. You are using the forum to sell your product. Would like if you supported AZ Billiards by becoming a club member, and by advertising your product with them on the home page. This would be mutually beneficial to both parties.
 
This app looks like a great usage for my iPod which does little more than collect dust unless I'm reloading.

But my table needs to be purchased first, of course.

-Measly

P.S. Kudos to the host(s) of this board! I've learned a LOT in the 12 days I've been registered, and hope to learn more (and contribute something USEFUL)!
 
Little help, please?

rope_one said:
Older valley table, tight tape 80 x 40" nose to nose
Click to expand...

Call for suggestions

Okay, and I just took a road trip to measure some tables. I found an older Valley table that measures 74" nose-to-nose. So you're right, one_rope, we have a problem to solve.

I'm still pretty confident that, with the rare exception of custom or "bargain bin" off-brand tables, 8-foot tables and above are pretty well standardized, but having learned what I just learned, I'm calling this into question as well.

I don't think many home users will mind measuring their table length-wise, nose-to-nose to make sure they get the best results. But if you're out and about, we would like to provide some means of measuring a table that doesn't require a tape measure, but is still very accurate.

To this end, we are actively looking for a solution to the problem of measuring a table. I think there are some clever solutions available and I know there are some clever people here, so if you have ideas, let's hear them! If we use your idea, you'll get your name in lights in the About box of all versions of Break Speed that use your idea.

To get the creative juices flowing, here are a few options we've discussed amongst ourselves...

Provide a custom printable template. Simply lay it on the side rail and use it to measure the distance between the diamonds - the template will tell you the length of the table, nose-to-nose, based on the distance between the diamonds. On my 9-foot table, a standard 8x11 sheet of paper will not quite reach both diamonds, but folding the paper diagonally will (with enough room to spare for the printable area of the paper.) This can be folded up and placed in your cue case. This is currently our favorite idea. It's simple and most people have access to a printer either at home or at work. We will also need to make sure that people don't "shrink to fit" the template when printing, in order to provide the best accuracy.

Take an overhead picture of the cue-ball on the rail with the nearest two diamonds in view, and auto-detect the position & size of the ball and diamonds. We threw this idea out almost immediately because not all devices have a camera (read: iPod Touch).

Using measurement references: allow the user to measure the distance between diamonds relative to a row of balls. Line up a series of balls along the rail from diamond-to-diamond and provide an interface to allow the user to duplicate that relationship on-screen. We're not keen on this one because there is too much inaccuracy here (on my table, there is a 5" distance from a diamond and the inside of the rail, which makes it very hard to judge.) Other options were dollar bills (they aren't all the same size unless they're fresh, also too hard to judge when they don't land exactly on a diamond), quarters (few people will carry that many quarters with them), chalk cubes (another availability and standardized size issue), etc.

So far, the paper template provides the most accurate results. Top THAT! (please) :)
 
I love this app! In 1 hour using the tips on the video and this app I have gone from averaging 17.5 mph to averaging 22.5 with a max of 23.8. I am controling the cueball much better also.
Evan
 
I think you are correct on the 8' and up basically standard sizes. The bar box has two basic 7 foot sizes from what I have understood, 78" and 80". My personal answer was to just lay my predator bk 2 across the table, if the tip touches on cushion and the second Cushion lines up with the o it's 40" and if it's between the bk then it's 39" and the length is always double.

The nicety would be to add the custom size to the iPhone app.
 
I win :)

i know there might be some issues with the program, but i'm going to consider this result valid. :D
 

Attachments

  • IMG_0057[1].png
    IMG_0057[1].png
    40.8 KB · Views: 286
DoubleD said:
When I set my cueball on the spot, the the app says distance is 50" on a 9' table, which is the distance between the head spot and the foot spot, but isn't the distance the cueball travels, since the impact occurs 1 ball diameter less than that. Doesn't seem like much, but it is 5.5%, which will probably average out to be 1-1.3mph difference in the reading.

Unless, of course, your calculations already take this into account....

dld
Click to expand...

Yes, our calculations take this into account. If we printed the actual distance traveled, then people would complain about the fact that the distance printed on the table screen was incorrect. This is why the iPhone version doesn't display the distance.
 
Super cool app. I got the trial version thinking that I would use that till I got a new phone in a few months and then I would buy it. Next thing I know I am having fun and ran out of the free trial which made me buy it to have more fun.

Yesterday I was averaging 19mph with quite a few of them coming in exactly the same speed. Today I was averaging 20mph. I was actually quite surprised at that because I thought it was be a lot more. When I bowl I throw the ball 24-25mph...which is probably why I thought I would break a lot harder.
 
Break Speed's little brother - the G1

Doing some late-night comparison testing and thought I'd snap a picture. The phones are all well within tolerance.

We're just getting started on the Android version (that's a G1 on the left) and already we have the core audio code working, rock solid, production-quality and producing valid Break Speeds. The rest is all UI work, which typically takes the longest.

You want to know how motivated I am to get the Android version working? I'm getting up at 4am to pick up my new Sprint EVO on Friday morning. I want Break Speed on my phone, too! :)

aiw.jpg
 
I am glad to see that G1. I am really excited to get this for my phone. I just bought a predator BK2 during the BCA and have been working on my break. The "break speed" will be the icing on the cake.
 
Nice app! :thumbup:

My wish list:
Option to save/ignore each result; possibly save with comment.
Display rolling average of last n saved trials (n a user input).
Export results as csv file.
Color code break speed with reference to rolling average (eg green for faster than average, red for slower).

And I wouldn't be sad to see the number of significant figures reduced (how anal would you have to be when racking the balls AND placing the cb in order for the result to be accurate to within 1/100 mph?)
 
You must log in or register to reply here.
Back
Top