jason

Feature has been published: http://blog.flirc.tv/index.php/2017/12/25/flirc-just-got-a-shit-load-cooler/ No gui support, it's in the commandline app: https://flirc.gitbooks.io/flirc-instructions/content/command-line-interface-guide/macros.html I think I might be able to whip up some GUI support, it'll be crude, but should do the trick. Happy Holidays.

Let me know if you have time for a team viewer session

Hey Joe, yes, they are out of date. I migrated all my software builds to Travis. Before I was doing all my builds and releases from my personal computer, a disaster waiting to happen. Travis isn't set up to publish the SDK just yet, I'm going to get to that this next week.

Have you tried a different remote? And all in the while, you're still able to use the GUI with your flirc? ** EDIT ** One more question, have you used the zadig tool before?

Great, so glad it's working, very sorry for the initial inconvenience.

I'm using a service called travis to do building and releasing for me. Kinda new and it looks like I had an issue with the last release. I posted a new version this afternoon, should fix it. You'll need to grab the latest from the downloads section on the website. Very sorry for the inconvenience. Please let me know if all is well, we're on version 3.5.2 now.

I'm pushing a fix as we speak, should be up very shortly, let me know how it goes.

An update is coming today, please give it as hot and let me know.

I haven't put together a blog post in a while. But will do so soon. https://flirc.tv/status_board I'm trying to be as open as possible with what I'm working on. I've started both long presses and macros. I hope to have a release before the end of the year.

I'm a bit late to this one. A user pointed me to here. This is really really concerning. Should a user come across this, please let me know, as this is definitely preventable if not a simple software bug.

Yes, we're very interested in seeing this. If we could trouble you to follow up with a log, we'd be extremely grateful. Thanks for the help and the follow-up.

I think I can push a fix out this week. Hang in there.

Can you fire up the GUI, go to device log, enable ir debugging, and press and hold the button down in question? Save and post that text file here.

Can you press a couple more buttons, hold them down each time.

Okay, I have a fix in place, I can't post a firmware image here as it includes a lot of functionality that wont work with the current GUI. So hang tight, I'll push an update early next week.

No, it shouldn't be. Mine is behind my tv inbetween my wall and TV, doesn't skip a beat. Any chance you can show a picture of the setup? Perhaps your TV is causing some interference, is it in front of the TV Screen, or behind?

I'm fine with you doing this. The only thing that could go wrong, is that you lift the solder pads off the PCB, which is very likely if something is going to be hanging off the pcb. Don't worry about the warranty, it's just me to say so, so unless the board is physically damaged, it's not a big deal. The board is made to be mounted into a case, I would think it would be better to modify your case to be compatible. It's just a few holes and you can use the board as a template. Just drill three holes and call it a day. Here is the part I use: TSOP77338TR (you can figure out which pads are what based on the parts datasheet). The part you chose will work. The only thing is that if you don't solder those parts leads directly to the PCB, and you use extension wires, you're asking for frustration. Any kind of wires need to be thick enough to support the current over the length of it, plus, if they aren't shielded, and you stick them in a computer case, there are going to be all sorts of random noise. You could definitely damage the PCB if those leds touch and there isn''t good USB isolation. Let us know how it goes. Hacking is always welcome. That's how flirc started in the first place.

I see the issue, need to discuss with yawor how to proceed, hang tight.

Yes, I've been super swamped with black friday and cyber monday. Super swamped. We have an update that should allow you to do this. I'll try and push this in the next day or so. all credit to @yawor, who whipped up all the code to allow a plugin style architecture.

Glad you are up and running. Thanks so much, sorry for the bump getting started. Thanks so much for letting me know. Means a lot.

I have that remote, not sure I see that problem, I'll give it a shot tomorrow. Can you do another log like you just did, cycle through the arrow keys, and then end on the okay button ,basically simulating as if you were doing the recordings until the error? Thanks so much.

Nah nothing you can really try. Honestly, I don't want to support the old version so much anymore as it's not time effective. It's just me, and Yawor is amazing, but is a volunteer. We gave it a couple tries, not worth debugging any more beyond this. I'll still push a couple updates to the old one, but all the new features are coming to the new one. Unplug all the hardware, and see if the GUI works/updates. If it doesn't work without any hardware, the GUI wont work with the new version of hardware. These are two separate issues though. I got your PM, I'll get you a replacement.

I don't know why the app is crashing on OSX 9.5, I can't even install it to try. However, can you try running it with out the flirc present? Let's rule out that it's a problem with flirc + gui and not just the GUI. Also, it's not worth pulling our hair out over this. Shoot me a PM, I'll replace yours with the new one.

It's not the remote, but the recorded signals which are recorded noise. Give it a shot and try it again. Let us know.

updates wont work, it's now only a 64 bit app. It was too hard to make a universal app and apple is officially not supporting them anymore making it increasingly difficult to compile 32 bit compatible apps.