Just another timer.

[lookash]

Hello,
Lt-UnReaL said that latest fixed version is OK. So Let's Run It

 

[adragast]

I don't have anymore issues with it now and this timer rules...

 

[Marcell]

I haven't had any problems with the previous version, but I downloaded the nwe one for safety's sake, and this one doesn't give me new scrambles. It gives the same scramble every time. :rolleyes:
Great timer, by the way. I'm definitely gonna use it.

 

[povatix]

I haven't had any problems with the previous version, but I downloaded the nwe one for safety's sake, and this one doesn't give me new scrambles. It gives the same scramble every time. :rolleyes:
Great timer, by the way. I'm definitely gonna use it.

Same here
sometimes the timer gives new scrambles, but sometimes it doesnt.

however, best timer out there!

 

[lookash]

Ohh sorry. Now it should be OK.

 

[Marcell]

It is OK now. Thanks!

 

[hdskull]

hey, in history, how come i can't check bld times ?

 

[lookash]

Hey, it's more complicated than other categories.

As You see, graph in the "history" tab presents averages, not times, and that's why i don't know now, how to add blindfold to history.
Yhm i know, but I'm not sure.
Don't You think that 12 blind solves is too much for each session?

What is optimal number of solves to calcuate blindfold average? Maybe 5, 7?

I'm waiting for a suggestions.

 

[povatix]

How come it no longer plays the 3 second countdown sound file?

nvm soz

 

[Marcell]

lookash: it'd be nice if the program could store one "border time" for each different puzzle, so I wouldn't have to change it every time I start to do 2x2 solves afetr 3x3 for example. Is it possible?

 

[lookash]

Marcell : OK, I'll do it.
Povatix : I don't know about it. Are u sure it's program fault?

 

[Mike Hughey]

For blindfold, since the standard is indeed 12 blind solves, throwing out best and worst, I think you should really use that for the average. See:
http://www.speedcubing.com/records/recs_bf_333_av10.html

 

[aznblur]

Hmm, it doesn't save my solves after I close the timer.

 

[hdskull]

5 solves is good

 

[lookash]

@aznblur
Go to Session stats, save your times to .txt files, and then use File->Open function.
@hdskull
5 solves for blind ya? Probably I'll made 12, but I'm not sure yet ; /

 

[Jason]

The timer is great, although there seems to be a problem with the countown. The final tick of the gong (the lower pitched one) goes off late relative to the timer (by roughly a second).
Also, I was wondering if it was possible to add a DNF option for those solves that you can't be bothered to finish cos it went completely pearshaped. That way I can keep track of how much of a cheater I am.

 

[lookash]

Does anyone else have a problem with countdown? : (

 

[Lt-UnReaL]

Well I don't use countdown so it's okay for me.
But on the history tab, the times are separated by the times when you solved them and not the amount of time elapsed...
What I mean is when I look at the graph, half the graph is from January to July and the other half of it is from September to October, just because I've been solving it a lot more in the last couple of months, so it looks really uneven. You know what I mean?

 

[adragast]

I did not notice any issue with the countdown, have to double check later...

 

[Marcell]

Does anyone else have a problem with countdown? : (

Yes. When I start the program it's OK but after the first solve all four "clicks" are late. Actually, the sound seems to be right, and the times seem to be too fast, it's like there would't be 1 second between the number 4 and 3, but less. Or something like that.