I've updated the 64 bit linux binaries, although you can download the 32 bit deb file and install it just fine on a 64 bit OS.The reason this would work is because I've temporarily given up on static linking. I don't know why, but for some reason, the static compile of the QT GUI was horribly slow, and created artifacts on the screen. I eventually compiled the libraries again with a bunch more options enabled and got the application to run without the artifacts, but it was still extremely slow. I felt it was not acceptable in the standard of quality I want to set. So I bit the bullet and compiled dynamically adding all the necessary dependencies.The font also doesn't look funny in the GUI anymore, so overall, I may just leave it like this. I spent far too much time compiling the QT libraries, and I've got more important things to do.Here is our list of goals:1. Finish filing patent on proprietary algorithm powering flirc.2. New version of GUI with more programming views3. Update video with new GUI on home page.4. Documentation and Help Section of the Site5. Firmware wake from suspend support6. Firmware repeat key detects
There was an update posted tonight for linux 32 bit, and OSX which addresses a problem when you save a configuration file. This crashed the application and also happens on windows and linux 64 bit, but those updates are coming soon.This was a very intermediate update. I wanted to address that issue before the next release which is going to be big, I'll post about that in a couple of days as it rightfully deserves it's own article.
A special thanks to Alex Korzh, an aspiring attorney who drafted the patent for flirc and did an amazing job. Not only am I lucky to have him do the patent, we're happy to say that Alex is now part of the founding and executive team at Flirc.
I hope it was worth the wait. I'm sure there are a few things to iron out, but overall, this is a very large update. Eric has re-architected the way the GUI works. No longer is anything hardcoded, he has re-designed everything from the ground up in a clean, elegant, and scalable solution. Each window is brought into the GUI in the form of a vector graphics image, and an XML file.The graphics image is in an SVG file format. The SVG format is actually editable as text, but it is a graphics file. All the windows in this version of the GUI have been re-done in the SVG format. The purpose of this file is to group elements on the display, keyboard keys mainly. The keyboard keys have two colors, and are grouped and labels accordingly.The xml file is used to tell the GUI what to do. Fields tell the GUI what keygroup to display, and what to swap it with when moused-over. There is more, but I won't digress into technical jargon.We will grow the shortcuts windows with time, and extend the application to pull these from a central location on your machine. You will be able to add your own windows into the folder, and of course, share them via our site.Hope everyone likes it, thanks for all the feedback, and let me know how it goes.
There is a new firmware version that I will be testing. This adds better support for the RC6 protocol aka WMCE and XBMC remotes. This will most likely make it on all new devices, which means that people who receive new hardware wont really need to read further.However, because I'm changing some code quite a bit, this will mean that any existing customer may have to re-configure their remote. There wont be an easy way to transition a saved configuration to work with the new firmware. However, unlike Apple, I let you downgrade the firmware in case you accidentally upgrade, and don't want to upgrade if you are happy.In this same version of the firmware, I will address a bug which effects some users where flirc is broken after a wake from suspend.I will also add a 'wake from suspend' button, as a temporary medium until I figure out how to do this automatically.
Whew, that wasn't nearly as bad as I thought. I've been hosting the website on my home computer, which is a mac mini, also hooked up to my living room flat screen. I figure,. Which is fun, lets me be in control, and I love having a server available all the time, and from anywhere.
My initial round of pre-orders shipped on the date promised. The version of firmware that shipped with those is 0.7, newer than what most people have, which is 0.6. Firmware 0.7 had some general enhancements related to the algorithm so that this RC6 protocol would work better. The occasional remote that doesn't, I believe is because the remote is operating at a different modulation frequency. I'm going to get to the bottom of that soon, and if this is the case, I may add an ordering option for this.Because the firmware works a bit differently, this may mean that people upgrading from 0.6 to newer will have to reprogram their remotes. Not the biggest deal, but something of which I tried to effortlessly avoid. There is no way to convert a users configuration file because of the how flirc works.FW 0.8 is what will be shipped to customers via the 0.96 GUI update. However, I don't have a handle on the bug where flirc is not detected after sleep. I can't reproduce this problem so it's a bit harder for me to tackle. On top of this, I've been pre-occupied with windows issues.GUI v0.94 and 0.95 released. These are general stability improvements and all the download links will be at 0.95 shortly, windows will be tonight most likely.FW 0.9 will solely address the issue where flirc isn't being detected after a wake on sleep, unless I magically figure out what's wrong in the next few days. Here is where you can track fw updates.I found out why wordpress wasn't emailing me notifications for comments, so expect quicker responses there too.
My initial round of pre-orders shipped on the date promised. The version of firmware that shipped with those is 0.7, newer than what most people have, which is 0.6. Firmware 0.7 had some general enhancements related to the algorithm so that this RC6 protocol would work better. The occasional remote that doesn't, I believe is because the remote is operating at a different modulation frequency. I'm going to get to the bottom of that soon, and if this is the case, I may add an ordering option for this.Because the firmware works a bit differently, this may mean that people upgrading from 0.6 to newer will have to reprogram their remotes. Not the biggest deal, but something of which I tried to effortlessly avoid. There is no way to convert a users configuration file because of the how flirc works.FW 0.8 is what will be shipped to customers via the 0.96 GUI update. However, I don't have a handle on the bug where flirc is not detected after sleep. I can't reproduce this problem so it's a bit harder for me to tackle. On top of this, I've been pre-occupied with Windows issue.GUI v0.94 and 0.95 released. These are general stability improvements and all the download links will be at 0.95 shortly, windows will be tonight most likely.FW 0.9 will solely address the issue where flirc isn't being detected after a wake on sleep, unless I magically figure out what's wrong in the next few days. Here is where you can track fw updates.
Windows is lagging a bit behind and will be posted tonight, however, the GUI is now at v v0.96 and firmware is now at v0.08Both 64 bit Linux and 32 bit Linux were updated too, I know the 64 bit fell behind, but that shouldn't be an issue anymore.The GUI now displays the current firmware version as well as helps with a problem where the device can get stuck in DFU (Device Firmware Upgrade).The latest version of the firmware has been embedded inside the GUI, and will prompt you before upgrading.We've certainly come a long way, and will take the beta name off everything soon enough.
I received the next batch of boards, I shouldn't be sold out for a while. I'm finishing off some last details and pre-orders will start shipping Friday and continue until Monday. All pre-orders will ship by Monday, thanks everyone for your patience.
I can't say it's a shock, we all knew it was coming, but it's still a truly sad day. Steve Jobs will forever be known as the world's greatest CEO, he changed everything.But what's truly amazing, was the constant fight and resilliance of an individual that did not ever want to give up. "I have always said if there ever came a day when I could no longer meet my duties and expectations as Apple’s CEO". I could only imagine how absolutely terrible he must feel physically, and mentally, to have sent that letter which was probably written at another time.Steve has not been well for a while. When I first saw him a few years ago on stage I knew something was wrong. Call it a survivors intuition. When I go to the hospital for my checkups, I'm surrounded by amazing people, all of which who are fighting for their lives. Steve looks like he has been fighting for his life. Over the last few years, there was sign after sign. The liver transplant was a pretty big one. The livers is a regenerative organ, one which you can cut in half, and it will grow back. People don't get liver transplants, it's a hard and dangerous procedure, and when I was diagnosed, I had doctors tell me it wasn't even an option. (thankfully, my cancer was contained and didn't spread to anything like the liver).In his last speech to announce iCloud, it was extremely obvious to me how much his health had declined. Every word was a reach for breath, almost as if he had just gotten out of bed. Then the news came where he pulled in the release of his biography for three months. You don't authorize a biography in the middle of your privately kept life.I've heard that Steve has been on campus every day, talking with his staff. I can't imagine how difficult this could be. He's fighting for his life, which you would think he'd want to be enjoying outside of work. It truly says something about his devotion to his company, and to the people at Apple which he's always gratefully acknowledged in his keynotes.From the bottom of my heart, I wish Steve all the best in the world, and hope he wins his fight. Apple, and Steve Jobs, has been the sole reason and motivation for which I'm always striving for perfection.
For those orders placed in the past week, they will go out this Saturday, Pacific time. I'm so sincerely sorry for the delay, I usually can make every order go out next day, however this week has been extremely stressful and busy. There is no reason they haven't left (bad parts or firmware or software, everything is fine) other than me being completely and utterly swamped.There is also a bug in fw v0.8 which will cause a lot of headaches, a key can randomly be deleted. I have fixed this and the fw image will be a part of the next GUI, but for those who want to get it now, please do so here: fw_0.9.binThe orders that ship out will have this version pre-installed.The sleep issue that some users experience is still outstanding. I've tried about every OS's on 15 different hardware machines. I can't reproduce this. Multiple modules and multiple reboots, sleep, and hibernations, and everything on my end is rock solid. A good friend of mine has about 10 machines, I will spend the weekend at his place trying to reproduce the problem. I'm certain, once I can reproduce this, the problem will be resolved rather quickly.That's it for now. I'll try to knock out some of these other promised firmware features soon.
I'm confident that the v1.0 firmware release has fixed the sleep/cold start issue described in the last post. If anyone is still experiencing this after the firmware upgrade, please, say so.A special thank you to everyone giving me feedback and testing the non public images. I'm forever grateful for you guys, your patience, and understanding.Here is what's on the drawing board for the near future. There are two issues outstanding with the firmware, which I have been making slow and steady progress. Check out this page for past fw release notes, and future firmware feature release notes. This page will get updated with tentative release dates.I will also be putting together forums. This will bring a social advantage for users to share their setups, post problems, request features, and try/discuss beta firmware releases. This has been a long time coming, but with everything quickly stabilizing, a very important necessity.But before I start publicly releasing firmware images, I'm going to be taking a break to work on finalizing one of the most important aspects of the project, the API. We will be putting together a C API for users to integrate all of the flirc functionality in their own programs. We will also be releasing source code for a QT GUI which act as an example usage program. All in this time, the public GUI will be updated for better stability.I will post API news and updates via the blog, as well as share when the forum goes up. Beta firmware releases will all be done in parallel, which will be available to anyone who wants to try them, but I don't expect to integrate them into the GUI until the API and GUI are stable.Thanks to all the great customers who make every ounce of effort worth all the hard work.
I'm calling out for your help regarding an issue effecting a small amount of users. I have been unable to make any progress on some of the other firmware features because there is one major bug that I can not re-produce, and can not solve. I'm spending all my time on this one, so I'm asking for your help.When you wake your computer up from sleep, and your flirc no longer works and requires you to unplug/plug, then please leave in the comments section the following:1. Operating System [Linux/Windows/Mac]2. Operating System Version [Lion/Snow Leopard/Hardy Heron/Vista/etc] (32/64 bit as well)3. Your Motherboard Manufacturer (If you don't know, leave your PC Model)Even if I have talked to you previously, please post a note in the comments section. I need help narrowing this down and will most likely purchase an identical unit.
All pre-orders have shipped. Patiently awaiting feedback.
Flirc forums are live.I haven't had much time to play with the forums, but I added some general places for people to start posting. If I missed something and get a lot of spam, I don't have much time to run through everything again, and will temporarily shut them down. Hopefully this wont be the case.Don't mean to be pessimistic, but I have a lot on my plate. While I know this is overdue, I don't want to have something that sucks my time. Remember, this is just primarily me, and I'm doing my best.
We've finally finished our API. A special thanks to Eric who has really helped make hard work materialize into a high standard and an acceptable product.We haven't released this publicly for general consumption yet, although the plan is definitely to get this out on the open. I'd certainly like to put the project up on Git, which will be our set of libraries and a small example application written in QT.Please touch base with me if you would like access to this before the public release (probably very early next year).I will pick up work on the beta releases of the firmware. I strongly believe that the repeat issue is done, and will be working on the waking up a sleeping PC firmware.I'm extremely pleased how well everything is maturing, and certainly hope that it shows in nothing but a beautifully simple and easy to use product.
The forums are live, and pretty hot. I should have done this sooner in retrospect, but I don't think I could have handled the additional work.I've started a forum, you'll need to register to try this out, but for those who can't wake up their machine from sleep, this is a fix. It's not a solution, but a temporary fix.This temporary fix will allow you to pair a button on your remote with a special command that will tell flirc to send a 'wake-up' signal to the computer which is in hibernation or sleeping. This wont be needed in the future, any button will essentially do this.Here is the link:Wake-Up Command Beta Release ForumPlease post in the forum with questions/feedback. Don't use this comment section of the blog.Happy beta testing!
Here is a sneak peek on the latest features of the new software. It's a massive overhaul of awesomeness. The new architecture will allow you to drop your own XML and Graphics file in a directory, they will automatically show up in the GUI allowing you to make new shortcut windows to share with your friends. Eric has thought about this for a while and it's scalability is amazing and impressive.Also included in the next release will be firmware version 0.6, nothing new, but a very important update to improve stability.
I'm hopefully confident in this new approach. Check out the forum thread release which has much more detail and instructions.Happy Beta Testing and reply directly in the thread to share feedback.Here is the link again: http://forum.flirc.tv/index.php?/topic/93-beta-firmware-release-v2/
Those of you with Apple style remotes, or remotes that don't repeat while holding the remote button down, I've got a FW beta release you can test.The changes to the firmware were very minimal, I don't expect anything can go wrong, so don't be discouraged to try this if you are experiencing this missing feature.Please post feedback directly on the forum and not in the comments section below.Long Key Press Beta Release ForumThanks Everyone!
I wanted to send a message out to everyone and wish you all a happy and healthy new year. This project has been an amazing fuel for my personal determination. I'm grateful for all the customers out there, and the amazing support and dedication they have shown to me. I wish there was a word beyond 'grateful', because I would use it.I'm truly surprised by the customer experience. I never imagined it would be as good as it's been. From pseudo7 and eskro's support on the forums, to the emails I occasionally get thanking me, it's only these things that keep me focused, determined, and make all he hard work worth it.From the bottom of my heart, thank you.
A big thing that was missing was support for media center keys. Yes, flirc shows up as a keyboard, so where was the support for your itunes/winamp controls? Play, Pause, Eject, etc.I looked all throughout the internet, and finally found a single document that pointed out some technical information that I needed. I made some modifications to the firmware, and bam, they are up, running, and they are working great.This is pretty big for me, it represents a milestone and achievement as this was a feature I personally desperately wanted, and knew existing and future customers would too. I will follow up tomorrow when my eyes aren't bleeding with tears, a forum link for registered users to download and try this out. But the modifications were so slight, this will most likely be rolled out.A quick status update on the other beta firmwares. Repeat is solid, functional, and stable. This will be rolled into the next release, in fact, I may just put it in the media key release. Wake up a suspended machine is almost there. I'm digging through the USB spec and am getting solid knowledge in order to understand why this wasn't working.
Here it is for the testing:http://forum.flirc.tv/index.php?/topic/98-beta-release/Please post in the forums to report feedback.
I've just released a new beta firmware image which is for waking the computer up from sleep. It's available on the forums here:http://forum.flirc.tv/index.php?/topic/115-beta-firmware-release-v5/I've stopped working on the media keys, there is a bug in the last beta version that caused flirc to disconnect, I've since solved that but haven't posted an image to try. I've verified on windows that these keys don't work, and I'm baffled. Everything works great on OSX, but doesn't work at all in windows and I'm not sure where I've fallen short. I think windows may need special support for this, but I'm finding very little documentation online that would help solve this. I'm not giving up, but just wanted to give everyone an update.
With the release of windows 8, there is an issue with the Flirc drivers because they weren't signed. Windows 8 doesn't allow installation of unsigned drivers enforcing you to basically turn all signature recognition off. Although, it just asked me if I wanted to 'install the driver anyways', but nonetheless, plenty of people wrote in here.I created signed drivers and attached them to the bottom of the forum.I'll make these official as soon as I get a tad bit of feedback, but they will be incorporated into the installer so you wont have to manually do an installation through device manager.On the software front I'm still cleaning up, re-vamping my build system. Today I got working a tool called NSIS on OSX. That creates an installer for windows. Why is that awesome? From my new build system and on my mac, not only will everything get compiled and updated, but I will be able to cross compile a windows executable and then even make the installer. I don't need windows anymore to do any development or deployment, just test.The hardware front is going smoothly too. I updated the boards to help with yield, as I previously mentioned in my last blog entry. I'm expecting 100 sample boards to get back to test soon.I mentioned I would follow up with how I planned on improving yield, so I'll share that as well when I get some more time.I'm going to make a huge effort to update the blog once a week. I want to do a better job of letting everyone know that I'm still working extremely hard on making this product perfect.
I just received some stock and will be getting orders ready over the weekend to drop off at the post on Monday. All preorders will be trickling out over the next couple weeks.
This past week has been incredible. Flirc was featured on the front page of xbmc.org with an article written by a truly exceptional and good hearted person, Chris aka (Pseudo7). What an exceptional honor it was to be featured on the front page of the very product flirc was created for, and by a person who has been extremely supportive, helpful, and ambitious in helping with my mission statement. I'm forever grateful, and glad to have made a great friend in such a unique way.The popularity of the article has helped spread the work. It was the first time anything has ever been written about Flirc. It's been a huge kicker as I realized we were very unprepared for the increase in demand. We're still trying to catch up but this has really kicked me into gear to figure out how to handle shipping. I'll most likely also be decreasing the shipping costs as well with other alternatives. Which will be great for international shipments.Another surprise which will be included in all new orders is the new packaging. This has been in the works for a while, and it was worth the wait.
What does this actually do to the product? Nothing. This is the same hardware and firmware, but merely symbolizes the culmination and completion of a product that I have been working so hard on for 3 years.
As promised, I wanted to give everyone an update.Not a big one today, I'm still working on the software build system, which isn't done. Getting stuck on a technical problem, I took a break from that and am working on firmware development.I'm re-structuring all my code so I can solve these bugs with sleep, sticky buttons, and long presses. I've begun strengthening my algorithm to better support other remotes and so you don't have to record keys twice with the RC6 protocol. I've also completely revamped things a bit so the firmware works differently. Previously, the firmware would set an interrupt back to the host on the event of a button being recorded. Anyone familiar with libusb, set_interrupt(), this function blocking. Which means that in order to write the host side software, I needed a separate thread to wait in set_interrupt. This isn't good and made my API terrible, confusing, and easy to get wrong when I release the software.Now, the flirc firmware uses a state machine for recording. The host PC can ask flirc the current 'state' in a polled mode, which means that I don't need a separate thread.This doesn't mean much for customers other than it's the beginning of me getting back into firmware development. For developers looking to integrate flirc into products, this actually means a lot.I've also begun working on something ultra cool, and I've got some of that up and running. Hopefully I can make an announcement in a couple of weeks.Until next week...
Thought I would share the exciting news that I've passed American, European, Australia, and New Zealand certification testing. I'm legally allowed to sell in those areas, and open communication to distributors.Everything went great, and I passed without a hitch. Here is a neat picture of the first stage of the testing, it's called an Anechoic Chamber.
They have a very large expensive antenna pointed at flirc. The antenna rotates and also moves up and down. The table the laptop is sitting on, also rotates. They measure with the antenna any emitting frequency spikes on a spectrum analyzer, and compare that against a maximum allowance. I'll post a picture of what that chart looks like. The emissions from the setup has to be less than a certain amount across all frequencies.Another test was called immunity, which meant that I had to withstand a shock of up to 6kV. Luckily, the device is well insulated, and there were no sparks, so I passed.
It's always a full time job trying to build more flircs. That will be a next step, try and figure out how to procure parts and ship them to the manufacturer without all this trouble. Each time gets easier, but nevertheless, it's always painful. Something always goes wrong, this times it was Chinese customs.100 samples of the new PCB returned and I had 99/100 work. That's pretty good yield, and I'll look into why the one didn't work. This is a slightly modified PCB to address build issues.Those 99 went out almost immediately to customers and more pre-orders should go out this week. I rushed a subset of the build to arrive next week, and those should fulfill all the pre-order needs. So we're certainly in good shape.Another update to come shortly.
Wanted to give a quick updated where things are progressing.I've started on firmware development and spent a good amount of time on sleep detection, in fact most of my time. I have something up and running and it seems to be semi decent, but unfortunately if this doesn't work, a hardware change may be necessary. I'm using a soft USB stack and because of this, the firmware is extremely timing sensitive. In order to do sleep detection, I need CPU cycles, which effect USB performance. Because of the uncertainty in this solution, the feature will be disabled by default, and will need be enabled via the Graphical User Interface or command line.I've improved a number of features inside the firmware. I've changed the way it operates so the GUI and command line no longer need a second thread. This was critical as I will be publishing the API soon as well.Iv'e also enabled error detection to prevent ghost signals. This is also disabled by default. The reason being that the logitech harmony remote only sends one signal at a time. This is going to lead to a lot of confusion should someone be trying to pair their remote and they have to press each button twice. I'll look into this and see if I can make a workaround.I'm still trying to figure out how to make a signed driver, that's been a royal pain and I'm sorry there is no better solution yet. I actually have a bid on rent-a-coder, hopefully I'll get something soon.Orders placed are also going to start going out this week as more inventory arrives. If you haven't received yours yet, keep an eye on your email. You should get an email notification.The build system has taken great shape. I've got the GUI partially in there too, which is huge being that it's written all in QT and they generally don't like when you don't use their makefile.Here is what's going to be in the next beta release* Noise detection/prevention* Sleep detection updates* Long press detection (apple remote)* Sticky Key issues (you will be able to modify settings via the GUI)* GUI visual feedback for recorded buttons* Better Windows 8 Support* (MAYBE) Media Key Support on Windows 8 and OSXThere is a lot there, so this will definitely be beta and only available to forum members.No ETA, hopefully in a couple weeks. I've made great headway.Happy New Years everyone.
I failed to update the blog these past couple of weeks and I apologize for that. I thought I would at the very least give a brief update of progress.Things are going very well and I've made tremendous improvements to the build system. I've pretty much solved all technical hurdles I was struggling with and have it about 85% complete. It's sustainable, scalable, and will allow me to cross build, deploy, and solve all my shared library issues. I have static analyzers as part of the build system and many many more improvements.I'm at the point now where I can start ripping apart the code and improving on it. It was absolutely necessary that I fixed the build system before continuing development. My git repository was an absolute cluttered and broken mess with branches going no where.All this time I've been mapping out how to restructure the firmware. My goal is to have major releases by the end of the month of both the firmware and the GUI.I'm also completely out of inventory. I have a sample test batch coming wednesday which took the manufacturers way to long to make. Should those be good, the first 100 pre-orders will go out immediately and I will start the next major build.On a separate note, does anyone use twitter anymore? I occasionally get new followers and am curious if people actually like twitter as a line of communication. Let me know in the comments. I haven't used it in quite a while.
As I mention repeatedly to supportive and patient customers, it's just me here. I have a couple friends that help, but their help is minimal when it comes to the time needed. I do shipping, logistics, support, development, the web work, reaching out, manufacturing, debugging, you name it, and it's all on the side of a very demanding full time job at a startup. It's rough. I work 80 hours a week, sometimes a lot more. But I do it because I love it, and I'm not complaining.But as a result of the work and attention required, I've been forced to get organized, and to be intelligent in the way I do things. I've learned a lot, and I want to be as open as possible in hopes that what I've learned can help someone else. Because the truth is, I've learned a lot from other people, to the point where I'm not quite sure how I would have gotten over some very big hurdles. Joe, the CEO of Saleae, is extremely open on his blog. He does a phenomenal job of communicating with customers. Sparkfun is another example of a company that is extremely open with their products and growing pains. I've at times, contacted them, or others with questions, and with no obligation, they have helped me. I was even recently featured on a sparkfun interview, and it was such an honor. I'm hoping that those who understand what flirc is, where it came from, and what I hope to accomplish feel comfortable in approaching me if they are struggling with something that I may have accomplished.As everyone knows, I've been doing a lot of behind the scenes work, and I'm sorry to say software and firmware have been extremely slow going. But I'm cleaning up. I was forced to figure out how to get orders out without killing myself, and I've got it. Shipstation has been my saving grace. They nailed it when no other company has even come close.I found a relatively new service to help with support called help scout. It's amazing, clean, simple, and helps me stay on top of customer emails. Nothing will get lost anymore, and I can better keep track of dangling emails that need response. I'm very happy with it so far. I changed the website so all emails going into the support link, email to email@example.com, and get routed to help scout. It no longer goes to my flirc inbox. Any emails leaving the site for registration, order status updates, lost passwords, come from firstname.lastname@example.org. While that seemed obvious, for the longest time it was also coming from my own flirc email address. Customers would just hit reply, and my email box was filled with important emails and junk. Now, my email will be held strictly for business and staying on top of manufacturing, working with partners, and that's it. I can manage support at help scout, and it will help me stay on top of everything by letting me know how long I've been taking to get back to people.On the development side, I'm revamping things as well. I'm changing everything in my git repository, cleaning up all my code, re-structing all the firmware, and getting my tool chains cleaned up. Software is a mess right now and it takes too long to try anything out and deploy stuff for customers to try. I rely on Eric, my partner, for deploying the windows GUI. In fact, he does an amazing job as he's done 95% of the GUI work. But when I want to add something, it's too much work. I rely on virtual machines galore. That's all getting solved. I am fixing my cross compilers, so that I'll be able to make windows, mac, and linux GUI's directly on my mac with one command. It's going to be phenomenal and result in much faster beta's that will be posted to the forums. Once that's done, I will publish the API with doxygen, and shortly after, fix these stupid beta images, make one image that combines them all, and find out what's wrong with waking the computer up from sleep.If anyone is interested in hearing about some of the electrical problems that I'm having which effect yield, leave a comment and I can follow up with some pictures and how I intend on fixing them.Thanks everyone for all the amazing support.
I sound like a broken record, but this has been a lot of work. I've spent countless hours on sleep detection alone. I've made some great progress tonight but I have quite a ways to go along with one important feature. I'm going to try so hard to finish by the end of next weekend. Wanted to post an update before I pass out.
I'm so pleased to announce that we're partnering with Njoy Digital in Europe. Njoy Digital offers a number of amazing products and I am happy to be a part of their product portfolio. This will help with European distribution and dreadful 4-8 week ship times. They currently have limited stock, so get them while you can.I'm also evaluating some of their amazing products hoping to offer those to US costumers as well. The flirc store will be expanding in the next few months so stay tuned for some neat personal and partner additions.Here is a list of our PartnersDirect Link to Flirc on Njoy Digital.
I wanted to announce with sincere pleasure two new distributors, ModMyPi in the UK and ProcSum over in South Africa.ModMyPi is located in the UK and distributes Raspberry Pi's, peripherals and accessories globally, with main market coverage in the UK, EU, Japan, US and Australia.Procsum is headed by Andrew in South Africa and he is working on getting hard to find electronics and supplying them locally at reasonable prices.I'm pleased to be working with both Procsum and Modmypi.
I wanted to let everyone know that we have a new partner and distributor, The Pi Hut. I'm really excited about this new partnership. The Pi Hut is one of the most popular online stores for raspberry pi accessories, and Flirc is now part of their offerings.Flirc is one of the best accessories for raspberry pi users looking for a great media center solution, and we have big plans for the little embedded system.On another exciting note, and no coincidence, the command line utility for flirc has been ported to run on Raspberry Pi, and should be available for download soon.
Well, I'm a few days late, but I'm just happy to have made this milestone. The next beta image has a number of improvements, and some of them are still not done. All the features that aren't quite done yet, will be polished before the release. Still to do before the next public release is a new 1.0 beta GUI release for testing, fw media key support, and finally a fix for windows media center where some keys don't work.Please read my instructions, this new firmware image is re-architected and will not work with your old GUI or old CLI.All of this was also done with the shiny new build system. Thanks for all the patience and support.Latest FW Beta Release Link
I wanted to give a special shout out to Chris and wish him a Happy and Healthy Birthday.Chris and I got introduced last year when he was one of the first customers. Like many of you, he and I became friends and since then, he's been an amazing help and support. He even wrote up the famous XBMC article that was published.Happy Birthday Chris!
I wanted to give a shout out to a new Australian and New Zealand distributor.I'm super ecstatic about this announcement. I don't enjoy shipping to Australia because of the extremely long wait times the packages spend in customs. This will increase the speed to customers, at the same price, and this was just a no brainer.
'Buy Raspberry Pi Australia distribute Raspberry Pis, accessories and peripherals to Australian and New Zealand customers. Located on Australia’s east coast, they boast fast shipping for domestic customers and a 30-day no-questions-asked money back guarantee on all orders. They have recently added the flirc .to their range of locally stocked products.'
Please check them out, and for a full list of authorized Flirc distributors, check out: http://flirc.tv/distributors/More to follow shortly...
This is a bit over due, I've worked with someone over he past couple months to figure out how to do a signed driver and package this into the installer.Done, finally. No more hack needed to install the driver. No need to turn off allowing the installation of unsigned drivers.The old 0.96 installer has been updated with the new installer that will work on Windows 8.Thanks for the patience.[Link]
I'm ecstatic to announce a new distributor to help handle online Canadian sales.Shipping to Canada can often take a long time and flirc will sit at the customs office longer than the time the product is in transit.So we have the perfect partner, a distributor of raspberry pi and raspberry pi accessories located in Canada. This was a no-brainer and we look forward to working with the Pi Supply and having them carry our upcoming products.Direct Store LinkPurchase LinkAs of now, I will no longer be shipping to Canada directly. New announcements soon. (no, not another baby)
Flirc has has a new member of the team. A little member, but promising in what's an amazing ability to make her Dad work non-stop.Audrey was born on March 4th and was so eager to start working, her delivery was only 45 minutes.Audrey is 3 months old, and her duties will be...well, just duty for now.[gallery ids="|"]
I keep saying updates soon, updates soon, and it's become a broken record. But I have been working extremely hard every day, even though it was not publicly visible.I have stable releases of the latest firmware, gui, and commandline. The remaining issues will be quickly addressed, and as soon as I have enough feedback, I will release this to the public. It's nearly ready.For those interested, please go to the forum, you must be registeredChangelogGUI v1.0.0-rc.1
This is one of the most exciting announcements to date. Flirc has a harmony XBMC profile!This has been in the making for a while. Harmony users can now add a flirc device to their remote where no codes will collide with their television, the protocol is fine tuned for flirc, and setup just got a whole lot easier.You'll need to download the latest release of the firmware: http://forum.flirc.tv/index.php?/topic/460-110-beta-download/Once added your flirc will work without the need for the pairing software with your favorite media center application, XBMC. All the buttons in this profile have been paired already with all the XBMC keyboard keys (eden), so you don't need to do any work.This will make it into the next major release of the firmware, and the goal is to have Plex, WMCE, and EyeTV harmony profiles as well.Please leave us feedback. I've turned off posting to the older firmware images because they have rolled into this one.Thanks everyone!
(excuse the grammar, it's late)
One more place to grab a flirc, check out pi-supply over in the UK:http://www.pi-supply.com/product/flirc-usb-ir-remote-dongle-for-raspberry-pi/
Copyright @ 2023 Flirc.tv, Inc. All rights reserved. All your base are belong to us.