jason

publishing the release now.

Really sorry for the GUI bug in the release, but it's safe to say this bug is gone and done. Thank you everyone for your constant support, patience, and help solving this. As most of you know, I have a few friends that help, but I'm primarily a one man show doing this all on the side of a demanding full time job and recent father. So to say the least, the community and constant warm feedback makes all the sleepless night and hard work worth it. Thank you so much everyone.

The Flirc GUI, if you fire it up after the flirc stops working. What happens? Does it detect flirc, does it upgrade the flirc automatically?

I think it fixes it, let me know on the release candidate forum if it doesn't resolve it.

can you describe what you mean?

Yeah, most likely going to be fixed with changing the interkey delay. But I believe this is only if you are rapid firing keys, is that right?

I can't post firmware images, and downgrading is a bit tricky. I think I fixed this, can you try the beta firmware image: Want to give that a shot and let me know?

Any luck? I'm 100% positive this fixed it. I was able to reproduce it, I've seen this before but very seldomly.

can you make sure you are on the latest firmware? Should say 3.1. If not, File->Advanced, force firmware upgrade. Let me know. Very Sincerely, Jason

Anyone else have feedback? I'm fairly happy with the change on my end and will make this public soon as it also fixes another long standing bug deleting keys.

That doesn't sound quite right. When it stops working, can you fire up the GUI? What happens, does the GUI detect flirc, does it upgrade the firmware automatically? Let me know, I'll get it sorted out.

That shouldn't be the case, can you give the beta a try, I compile it differently;

did you try the media center keys in the media controller view of the GUI?

it's basically a dumb fliter that expects the signal to be there multiple times before sending to the receiver. Helps prevent a false positive. I'm going to make it a bit smarter, but it does the job.

My pleasure, I poor my heart into this project, so it means a lot for the kind feedback. Yeah, I'll talk further with you about that, but I did post a new firmware image. Give it a shot, I'm pretty confident in it, but no one has tried it. Thanks so much, I really appreciate it.

Okay, I think I figured it out: Please grab the latest beta firmware, and give this a shot: It actually has a much more natural feel and seems to detect presses from holds much better now. I would also encourage you to format your configurations and relearn your keys. The reason is because the default settings after you format will likely cause people a lot less headache. They are much more generic, you probably don't need sleep detection, sequence modifiers, and anything other than an interkey delay of 3. Let me know.

I think I have an idea, I will post an image to try shortly.

What country are you in Joe? This is some really good work and I'm going to read it a few times to fully understand your suggestion. Can you also find me on skype or gchat? Both my names are jasonkotzin thanks so much Joe.

Are you seeing a few rapid key presses, or does the key feel like it's being stuck held down?

So yours is working?

I'm sure we can resurrect it. Traveling back home. I'll see what I can do when I return.

ah, interesting, and you're on 3.1?

Interkey delay is too small, need to crank it up to 3.

Interkey delay should be at 3.

The way it works now, if you don't have a sleep button mapped, but still have sleep detection enabled, any key will wake the machine up. Give that a try and let me know.