|
General Discussion General discussion about SageTV and related companies, products, and technologies. |
|
Thread Tools | Search this Thread | Display Modes |
#41
|
||||
|
||||
Quote:
|
#42
|
||||
|
||||
Quote:
But you still haven't said what your problem is, and until it's expressed, I'm convinced this is a worthless topic. Quote:
|
#43
|
||||
|
||||
Dekard, would you mind listing your HW/SW details? It may ring a bell with someone who has had a similar problem.
|
#44
|
||||
|
||||
Thanks, Davin! That's step 1 to help out Dekard.
As for software business, I can speak about how it works(ed) at Microsoft while I was there. Simply stated, all software has bugs. A lot of them. What do you consider a 'bug'? At MS, a spelling or puncuation error in a dialog box or help file is considered a bug. Add that to actual functional errors in the code and the buglist can get very large indeed. MS bashers commonly say that there are 10's of thousands of 'bugs' in Windows XP which may or may not be correct but still begs the question "what is considered a bug". Since there is no way to find and quash all 'bugs' in software, one has to determine an acceptable level to promote a software build to a "shippable" product build. For XP the bar was 85% as I recall. Of the myriad of hardware/software combination out there, most beta testers (in house and outside) found no bugs worthy of stopping shipment. Bugs were still found and added to the que to get fixed, but that got balanced with how likely the bug was to crop up in the installed user base, who's fault it was (MS, or a vendor supplied driver, is there a work around, etc.), and how will the fix impact the rest of the product. All in all, it's a HUGE challenge and in my opinion, all things considered, MS did a GREAT job. Now, the Sage boys have a huge challenge as well with a fraction of a fraction of the resources that MS has. They have done an INCREDIBLE job. These guys have been doing things that even MS said 'wasn't possible' like true multi-tuner capture, shared source EPG, etc. I don't want to imply that Sage is perfect as there is no such thing as perfect software, but these brothers do 'it' like nobody else I've ever seen. You will see on these forums that a lot of posts are folks with trouble they are having. I know from experience at Microsoft that the vast majority of satisfied users will NEVER comment in forums about there successes with the product. No different here. For good or bad, we are always going to be somewhat of a group of beta testers and Sage (and ALL other software) will continue to have bugs, and work to correct them. This is the REAL nature of the software business. Fortunately Sage made some choices in the beginning that have paid off, like the 'requirement' that capture cards use a hardware encoder. Smart move, it reduces the possible hardware variabilities and makes a more robust platform. True that Sage 4.x isn't as stable as 2.2x was, wait until we get to 4.2x or 4.3x or whatever it will be. After all, we lived with 2.x for what, like a year and a half? Stablility will get there in this version as well, just be patient! -PGPfan |
#45
|
||||
|
||||
Quote:
|
#46
|
||||
|
||||
Dekard, are you on broadband? If so, you might consider getting a copy of Gentoo that Sage is using that doesn't have any Sage installed in it. If you can get it running stable, and with the latest driver builds in it, that will go a long way towards identifing where your troubles may lay.
Only at that point would I re-try the Sage.iso of it. Like I mentioned, I'm no Linux guy (I use Windows XPembedded, myself) but this is how I'd go about trying to resolve your issues. -PGPfan |
#47
|
||||
|
||||
Quote:
1) It's stable for you (the dev). 2) It's stable for your users. 1) is easy. 2) is hard, you have to rely on bug/problem reports from your beta testers and user community. Sage is a small company (used to be just Jeff and Dan, not to long ago), they simply don't have the resources to rely only on 1, they have to rely heavilly on 2, otherwise they wouldn't be able to hit their price point or maintain their free upgrade, free EPG policy. As such, it is the responsibility of the users to report problems. And I'm probably as guilty as the next guy of not filing problem reports from time to time. But if you like Sage, and have a problem, file a report so they can fix it. As Andy said, many times here I've seen complaints from (usually a single or few users) that go on for versions, inevitably, Narflex will drop in and mention that nobody reported it. I have no doubt that Sage puts out a release version with known bugs, it happens with all software. But I also have no doubt that Sage puts out code, that to the best of their knowledge, is stable and release worthy. That's one of the great things about them, Sage's betas are (in my experience) as good, if not better than many programs' release code. I understand the desire to not have to deal with problems, but if you have one report it. A debug log and steps to reproduce the problem are usually all that are needed. Heck, they may even have it fixed already and will be able to point you to a version with the fix. |
#48
|
||||
|
||||
I just had to chime in on this one. Here is my take:
- If you want something that is very simple, works just about all the time, and is cheap buy TiVo. - If you want something that is complicated, feature-rich, works most of the time, and is cheap, buy Sage. (I just bought another two client licenses and a MediaMVP license 30 minutes ago.) - If you want something that is complicated, works just about all of the time, and is very expensive, buy ..... well I'm not sure that exists in the consumer market. Look at the aerospace industry (as I believe Dekard said he is involved with). Those planes are extremely complicated and work just about all of the time and as a result they are extremely expensive. They are designed, redesigned, computer simulated, modelled, tested, refined, re-tested and re-tested. As a result they are very stable and VERY expensive. If you wanted Sage to have near perfect reliability on nearly all configurations it would cost thousands or even hundreds of thousands of dollars per license. I'd never buy that and neither would anybody else. I'll settle for decent reliability at a low cost. If it really bombs you can get your money back from Sage. Tom |
#49
|
||||
|
||||
Quote:
I have filed a bug report, I'm still waiting for Sage's response. |
#50
|
||||
|
||||
Quote:
Quote:
Quote:
Aviation certified Garmin GPSMAP 376: http://www.garmin.com/products/gpsmap396/ $2695.00 Consumer model Garmin GPSMAP 376C: http://www.garmin.com/products/gpsmap376c/ $999.99 Same thing (essentially) but the aviaiton one is 2.6x the price due to the testing it goes through. |
#51
|
||||
|
||||
Quote:
|
#52
|
||||
|
||||
Quote:
Getting Linux or windows stable hasn't been an issue, i've been running into a myriad of small bugs in the sage client and server. Mainly they have revolved around the client or the server showing all the signs of being unstable. I could name a list of issues from constant crashes, video quality having severe issues, loss of connection, stuttering... and on and on... Yes, I understand every one of these problems can be solved with the support of Sage or the group. But it seems like pushing off work onto us\me when Sage isn't handling it internally. And saying they are a small company and we should just understand (like other posters have) is an excuse, really, for poor development and poor support. If it was open source I'd understand and we wouldn't be having this discussion. But this is paid software, one they are promising is stable, reliable and easy to use. It simply does not live up to its promise. |
#53
|
||||
|
||||
Quote:
Others may be willing to accept paying good money for bad products and say 'well, you get what you pay for'. I've got better things to do with my money then waste it buying products and then taking billable hours and converting them into time to setup\debug\beta test something that claimed to have been setup\debug\beta tested by the developer. For that same money I could have gotten a heck of a nice ________. Instead of buying whatever else, I have spent it on Sage then spent *countless* hours trying to setup\debug\beta test an unstable product. That hurts. |
#54
|
|||
|
|||
Quote:
I have been using Sage for a couple of years now and have found that getting the hardware combination right is key. Yes, it is a little trial and error. I now run a 4 tuner server with 3 clients, and 4 MVPs and I can't remember when the last time was I had to re-boot the server. And yes, I am using Version 4. Lighten up.... |
#55
|
||||
|
||||
Quote:
Quote:
Please understand, I'm not trying to make lite of your issues, but more, I'm trying to make you understand "why" it is the way it is. For the record, I, and many others have completly stable SageTV setups. My setup has be stable through every release since 1.x. I'm not saying there haven't been bugs I've encountered, I have, and they've been fixed (or at the very least, acknowledged), but I can't recall experiencing a showstopper yet. My server has been up for 143 days now. I only take Sage down when an update is out. I run the latest version (beta or not) within days (if not minutes) of it being released. And I'm not alone in these results, the same sentiments are echoed by many others here. The point is, there must be something different about your configuration that Sage has not encountered before, and with the limited resources they have, the only way they can fix them is for users to report them. I can understand your frustration, but just because you've had problems, doesn't mean everyone is experiencing them, or "accepting" them, or that Sage is knowingly releasing a "buggy" product. If Sage new about the problems, they'd have fixed them, or at least be trying to fix them. FWIW, if you want help, ask for it, people will help you, but if you start a rant thread, you'll get rant answers |
#56
|
||||
|
||||
Quote:
I did notice one thing though. The SageTV store doesn't mention (that I could find anyway) that there is no support with the Linux version. OEM doesn't always mean unsupported, maybe they should clear that up during the check out process. Basically if he didn't read through the forums before buying, he didn't know he was buying an unsupported product. |
#57
|
||||
|
||||
I know when MCE came out a lot of people complained about Microsoft not releasing to the public, but only to OEMs.
This thread is exactly that reason for their descision. If you want something in between Sage and Tivo you can buy a pre-built MCE box, HP builds a very nice one. It will work for you out of the box, the media extender will work with Xbox and Xbox360. It can record and playback both HD and SD content. You do give up some flexibility on how it can be extended and modified for your own situation, but if this appeals to you I would recommend going the MCE route. My brother has done so and loves it. It suits his and his families needs. Maybe they are more inline with yours also. As for Sage I have been using it since release 1.0. My 2.0 release was rock solid and was a joy to use. I chose to upgrade to 4.0 to get HD content capability. Since then it has been a battle, similar to the version 1.0 battle. I get the same complaints from my wife and children about Sage hung, Sage won't playback the recording, etc. I file bug reports, and am eagerly waiting the next release as it is supposed to address a couple of my specific issues. I expect it to get solid again, but share frustrations at the moment. Software does have bugs, software has been and always will be sold early. I would at a software company that sells software for engineering. It costs about $750k per year per seat. It has bugs and always will, so cost is not any kind of indicator towards quality. It is far more involved than that. That saying I do this that rapid growth and capability comes from software being released as it is. If every company sat on their software until everything was perfect they would not be in business, and software growth would stagnate. In the end it is just TV, if you miss the first showing you can catch in the summer as a rerun. If it was really really good, you can catch it as a re-run for the next 10 years. All this is of course IMHO. |
#58
|
||||
|
||||
Quote:
|
#59
|
||||
|
||||
Quote:
Anyway, this topic has been beaten to death. Everything has been said and understood, lets all move on.
__________________
Mayamaniac - SageTV 7.1.9 Server. Win7 32bit in VMWare Fusion. HDHR (FiOS Coax). HDHR Prime 3 Tuners (FiOS Cable Card). Gemstone theme. - SageTV HD300 - HDMI 1080p Samsung 75" LED. |
#60
|
||||
|
||||
Quote:
__________________
www.overclockingwiki.org |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|