Search results

What iPhone device are you on (3, 3GS, iPhone 4, iPod, etc.)? The most common cause of this is an echo. The initial sound hits the mic and gets registered as the break, but then an echo of the break is added to itself, which triggers the break to be re-detected in that spot. When this happens...

Did the market ever actually authorize your purchase?

The accuracy is the same as the iPhone version. It uses the same audio bit rate as the iPhone version (44.1KHz, which is very good), doesn't have any issues with post-processing (AGC, echo cancellation, etc.) and uses the same Break Detection algorithm that the iPhone version uses.

Android Just a quick note... the Android version just showed up on the Android Market a few minutes ago.

Break Speed on Android - Beta All, The Android version has reached "release candidate" stage. What that means is that *we* think it's done. But we need a few dedicated beta testers to prove to us that we're wrong (or that we're right!) The version that will be used for Beta will be the Demo...

Yep. Not sure when this is coming, but it's in the plans.

Yes, our minimum target is 1.5.

This comment absolutely made my day! Thank you! I've been up since 7am working on it and it is now 4am. I'm ready for some horizontal-ness. Android update The Android app is nearing "feature complete" stage. All the hard stuff is done. Aside from the cue-ball placement interface (the bit with...

Back in February, I did some math to study accuracy vs. power in the break shot. My findings were interesting, but not too surprising. The basic conclusion is this: If you hit your break shot with only 1% of error (i.e., 1% off from a dead-perfect hit) you lose 1.57% energy. So accuracy is...

The problem was largely internal with the way they were delivering audio data. It turns out that HTC took advantage of a new feature of the 2.1 operating system. The documentation for Android development is sketchy at best, but there's so much community support out there, that it really doesn't...

Let me start by saying that I own an EVO and I'm not about to have a version of Break Speed for my personal use that is inferior to any other version out there. :) So tonight I didn't just attack the problem, I launched a full-out assault on it... Android is open-source, which means I was able...

We're making good progress. Most of the difficult stuff is in and working (you can capture breaks, view/pan/zoom waveforms, etc.) However, we've run into a speed-bump with the EVO. There are some specific things that HTC has done in their version of the 2.1 OS that are causing havoc. These are...

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...

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.

Next time, click the Edit Result so we can see the waveform! :)

Little help, please? 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...

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.

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...

I doubt this would be accurate. I work in the entertainment industry, and we fake EVERYTHING. Most movies use very little of the actual on-set sound.

For the most part, your notes are correct. In general, though, what matters most about cue-ball position is the distance to the head ball. So if you're breaking from the head string (which is marked in the application) then you're likely to get a more accurate result because you're placing the...