Moderators: pilkguns, m1963, David Levene, Spencer, Richard H
For practice alone, to force myself to shoot a bit quicker. Not all the time, but when I miss an exposition of a target for example.David Levene wrote:I am a bit confused by the "0.3 seconds before red light". Why would anyone want that?
I was just thinking that if you're training with lights then you might as well use the full 3 seconds as, with ESTs, you will get the score if it's registered at the target 3.3 seconds after the green light comes on.diopter wrote: Nice to train under the time limit, as RMCA has stated
Perhaps the wording is a little poor; if you set it to "When registered less than 0.3 seconds before red light", that's 0.3 seconds before the firing time is up, regardless of user interface in the app (or the setup of your physical range, if we're talking about live fire). That sentence is long as it is, but I'll see if I can think of a better way of wording it.David Levene wrote:I was just thinking that if you're training with lights then you might as well use the full 3 seconds as, with ESTs, you will get the score if it's registered at the target 3.3 seconds after the green light comes on.
I can understand training to shoot under 3 seconds on turning targets where you might not get that much of a positive variation (there is no allowably negative variation on the 3 seconds) and quick mechanisms will be reduce the allowable "skid" time, but not with lights.
It is, and that's a fair point from the both of you, there's no very good way of entering a time for that. If you're doing this with the microphone, that might not be a big problem, because you can see afterwards what your time was (so you can use the 5×3 – or create a custom event – and just shoot faster, ignoring the 3-second limit), but if you want a visual or audible cue when your time is up, you can't have that (unless you've decided to shoot in exactly 1 or 2 seconds). Especially when dry firing on the animated target, I can see how that would be useful. Perhaps adding the possibility to have tenths of seconds in custom events is really the way to go. It would definitely be doable.David Levene wrote:Specific first shot training for the 4s RFP is another matter.
Please believe me, I am not criticizing your app.ToTheZeroth wrote: Actually, as you mention the 3.3-second thing, that was my other reason for including this setting. There are so many variables here – EST vs. paper targets, turning speed, bullet travel time, sound travel time to the microphone, possible microphone latency – that a shooter might well want to calibrate for something and allow 2.9 or 3.1 or even 3.2 seconds.
Oh, I thought nothing of the sort. On the contrary, I've been kind of overwhelmed by all the positive response from everyone in this thread.David Levene wrote:Please believe me, I am not criticizing your app.
After the update the app crashes on opening. Using Android 4.4.2ToTheZeroth wrote:Update to 1.9 available now.
I can't imagine that there is. The app was designed with a single-shooter scenario in mind. I could possibly add a function where you could attach a stand-alone microphone to the gun itself and send the times to the timer via Bluetooth, but even so, I doubt it would work, because these microphones tend not to be all that good at distinguishing between very loud sounds (such as your neighbours' guns firing) and even louder sounds (such as your own gun firing).jerber wrote:Worked out OK but even adjusting the mic volume
It also registered other shooters when they shoot
Anything I can do/adjust to prevent that?
Added to version 1.11. You now have "Pace beep" and "Pace vibrate" as options in the command sequence list. They simply beep or vibrate without resetting the timer or doing anything else. You'll have to keep track of the time totalling up to 20 or 10 seconds. It could look like this:rmca wrote:ToTheZeroth
Can you add a "bip" option to the command sequence of the custom event?
It would be great to get the timing right when dry firing the 20 and 10 seconds for example.
One could create the event, then add the bips at the time he/she would like the shots to go off.
Best regards and thanks again for a great app!
I think the problem was that I was playing the sounds as notifications, which is handled differently by different devices when it comes to external speakers or headphones. I've changed this to play as music instead, which seems to work better. Please update to 1.12 and let me know if it works on your devices.dand wrote:The problem that I have is that I would like to have the sounds played thru a blue tooth speaker so that it can act as the RO for a few of us shooting together. It won't work with my phone at all (android razor). It almost works with my wife's phone (Samsung) but the sounds continue to play on the phone slightly ahead of when they play on the speaker and the volume on the speaker will not go loud enough for all to hear while wearing hearing protection. We have done this with a bullseye app.
Nice idea! Added to the shot detection settings in 1.12.dand wrote:Another question is how/if I can use the custom feature to beep a set time after a shot is fired. It might help me learn to extend my feeble follow-thru.
Good: Your hyperlink worked.ToTheZeroth wrote:You can get it from the app page on Google Play (or just search for "25m Pistol Timer").
