In the spirit of the session being a 'trainer', I created the pattern as a simple gaussian, aka a 'bell curve'. The height of the bell curve would represent the depth of a suck, and another curve would be used for DT held time. User preferences would define the shape of the curves, and possibly skew them to one side or another. Depth and held time would still be affected by a random chance parameter.Tenderfoot88 wrote:What makes it worse is that you'd probably want a fairly complex pattern, or have it randomize a pattern at the start, to keep things from getting overly repetitive.
A 'score based system' can be created using cycles that I mentioned. A cycle can be defined as a preset number of sucks (16, 32, ...?), and the pattern applied to determine the desired suck time, depth, etc. Instead of failed sucks, if you did not do as desired, you would be issued a warning instead. After X number of warnings, the cycle would be considered a failure, and you would have to start over. Otherwise, depending on how well you did during the cycle it would be possible to declare the cycle as a pass early. You would then move on to another cycle. The goal would be to finish with a certain amount of successful cycles.Tenderfoot88 wrote: And since you brought up the pass/fail system - personally, I'd love to see a score based system - give the user free reign on what they're doing, and punish them based on failing to gain enough points over a given time period (more realistic - the person giving
Using this methodology splits the coding into specify chunks (patterns, cycles, warnings). I have about 70% of this done already, back with sbbj v1, it just needs rework and testing with v2. Unfortunately, coding takes a great deal of time, and my time is very limited right now. So I am waiting to see what everyone here wants the most, so when I do have some more time, I can get those things done. Items now that come to mind include:
- packaging fix (jennifer.bh)
- platform fixes (Win. cam. detection issue, app. in background issue)
- suck time limit fixes (thor)
- audio retest (custom audio, with a folder of clips for each audio 'tag'). Random & sequential clip selection
- possible upgrade to audio system, to allow mixing, audio selection based on audio length. More audio tags. (jessBaby, me)
- retest 'warnings' system
- retest / fix head play options
- put audio tease back in, app tease as well
- add custom tease options for serial attached devices (arduino, etc)
- ... and the list goes on...