Edited by dave9573490239 - 12/14/13 at 3:44pm
I bought the Homeworx a couple weeks back from Newegg (it's on V14).
I noticed that there's a wide range of delays when entering time shift mode or starting a recording depending on the external drive I'm using:
1 second - 40gb very old drive - http://www.amazon.com/Western-Digital-Passport-External-Drive/dp/B0006ZBHOW
2 seconds - 320gb old drive - http://www.amazon.com/Seagate-FreeAgent-Ultra-Portable-External-STAA320100/dp/B003ELOSEG/
8 seconds - 1tb brand new drive - http://www.amazon.com/Passport-Portable-External-Drive-Storage/dp/B006Y5UV4A/
I'd like to use the new one though it's so slow on the device, is there anything I can do to make it work faster?
note I tried formatting it on the device in both NTFS and FAT32 and it made no difference
I suspect it has to do with the peculiarities of the drive/power consumption than anything else (perhaps if I bought a good powered hub that might help)
--> partitioning the drive only makes a new problem I suspect --> would the homeworx automatically know where to record on the partitions?
I've ultimately just decided to use the 320gb drive - 40-50 hours of space is sufficient for me and has none of the headaches of troubleshooting the new drive I bought
in an ideal world...
someone would release a device based on this mstar soc that's prettier, rear mounted usb port, better ir receiver or better yet RF, and, most importantly, open source firmware that enough people would be keen to develop on so we're not reliant on crap software written by crap developers (homeworx being, seemingly, only one of the less crappy firmwares for these devices compared at least to the iview...)
I'd try to make a venture to do this, but I'm not interested enough to devote the time (i.e., if I really cared so much for a better system, I'd just spend 10x and get a Tivo or perhaps the new ChannelMaster at 5-6x if it actually works unlike their most recent attempt...)
I couldn't agree more! This box could be a pleasure to use if only it had solid firmware with a quality UI. That's obviously not going to happen unless it's open-sourced.
Are you f___ing KIDDING ME?!?
Last spring you released V17. This fall you released V7, V8, V13, *then* V10, then V14. All of which were "newer" than V17.
And now you're going to release yet another new version... and call it "V1"?!?
I cannot seem to find the right words to adequately express how mind-bogglingly stupid your firmware version numbering scheme is. If some evil saboteur intentionally set out to create as much confusion and frustration for your customers as possible, they could hardly do any worse than you're doing all by yourselves.
Similarly, how stupid do you have to be to choose NOT to embed the QAM code in the mainstream firmware version and let it be toggled on using a simple "Advanced" setting, and instead to require every single customer who wants QAM support to send you a separate email so that you can get around to sending them back a whole new 4-megabyte ROM file as an email attachment just to add that feature? And in the process, literally DOUBLE the number of firmware versions that are floating around in the userbase? Unbelievable.
Here's an example that illustrates the recording problem I'm having. Last Thursday, I pre-scheduled a recording of a three-hour overnight program on my local PBS channel from 3:00am to 6:00am Saturday. Later, on Sunday evening, I tuned into NBC Sunday Night Football on the HW-150 and manually started recording by pressing the "Record" button on the remote, then switched the TV back over to another input so my wife could continue watching her Netflix movie while the game was recording. A couple of hours later, after my wife was done with her movie, I sat back down in front of the TV to watch the game and noticed something was wrong: the activity light on the HD that I have plugged into the Homeworx, which blinks when it's recording, was on steady. Uh-oh.
Sure enough, I discovered that the unit had inexplicably stopped recording the game at some point. Upon investigating, I discovered that it had stopped at the 1:02:03 mark (one hour, two minutes, three seconds), with a file size of about 6.4 GB. So I missed most of the game. Then I checked the pre-scheduled recording from early Saturday morning, and discovered that it too had stopped early. It began at the correct time, but had stopped at the 1:02:04 mark, also with a file size of 6.4 GB. So I missed most of that program as well.
I have some relatively minor gripes with the unit's user interface, but that's almost irrelevant when the unit can't be relied upon to perform its most essential function.
Well, I just discovered what was causing all my unattended recordings to cut off at 1 hour, 2 minutes, 3 seconds: I had the "Sleep" function set to 1 hour. So after recording for an hour, the unit would put a dialog box on the screen asking for confirmation or cancellation of sleep, and begin a 120-second countdown. Since nobody was around to see this dialog, the countdown ran its course uninterrupted, and three seconds later the recording was aborted and the unit put itself to sleep.
I never imagined in my wildest nightmares that the firmware engineers for a device that's intended to make unattended recordings would be so indescribably, inexcusably stupid as to make the function that puts the unit to sleep after a certain period of time without user control input take effect EVEN when recording is in progress. I mean, that mode of operation is so utterly absurd that the floor beneath me is dented from the impact of my dropping jaw.
Obviously, this is a bug that needs to be fixed, pronto. Recording should ALWAYS override the "sleep" function — not the other way around.
If Mediasonic or Mstar won't release the source code to their craptastic firmware, then can somebody, ANYBODY, PLEASE decompile or reverse-engineer it so that it can be fixed or replaced by competent open-source developers?
Let's think about this for a moment, shall we? How many other customers have purchased this box and made the same perfectly-reasonable assumption I did: that the "sleep" function — which is obviously a mere power-saving measure intended to put the box into low-power-consumption mode when it's not doing anything useful — would surely never be programmed to cut off a recording in progress? How many other customers have lost all but the first 62 minutes of recorded programs that were important to them, causing them enormous frustration? How many other customers have wasted hours of their time trying to troubleshoot the problem, and/or given up and either returned the unit as defective or thrown it in the trash?
Meanwhile, how easy would it be for this bug to be fixed in the firmware?
Your curt response completely ignores all of these factors, and could hardly be more unhelpful.