|
SageTV Software Discussion related to the SageTV application produced by SageTV. Questions, issues, problems, suggestions, etc. relating to the SageTV software application should be posted here. (Check the descriptions of the other forums; all hardware related questions go in the Hardware Support forum, etc. And, post in the customizations forum instead if any customizations are active.) |
|
Thread Tools | Search this Thread | Display Modes |
#41
|
|||||
|
|||||
Quote:
Quote:
Quote:
Quote:
Quote:
Honestly, the default UI looks like something from the 80's, and they can do better. Even just skinning, with no core changes, can make a huge difference (i.e. SageMC). But frankly, they need to sit down and review the flow and organization of the whole operation, because the current UI is the result of several generations of growth, and it shows. It's not natural, it's cobbled together. |
#42
|
||||
|
||||
Even the stock can be helped... some..
__________________
Intel Core Duo 2.5mhz, 2gb RAM Windows Home Server, Sage 7 beta 2 Hauppauge PVR-250, 1 PVR-500 MCE 1 HDHomeRun 4TB Storage, GB Network 2 MVPs, 1 HD100 & 1 HD300 |
#43
|
||||
|
||||
lotusvball, is that a "real tweak" or a "PhotoShopification"?
__________________
-Jim Barr SageTVTips.com HTPC: AMD ASUS M2N-E Socket AM2 Motherboard; Athlon 64 3200+ Orleans 2.0GHz; 2GB RAM; eVGA 256MB Geforce 7300LE; 1x40GB IDE HDD (OS), 2xSeagate Barracuda 320GB SATA HDD (Recordings); Antec Overture II Case; Windows XP Pro SP2; SageTV v6.5 STV: SageMC Video sources: Currently, none. I'm using SageTV for Music, Photos, and Video playback. |
#44
|
||||
|
||||
That is my real stock GUI. With custom menu STVi, a different background and different highlight bars.
__________________
Intel Core Duo 2.5mhz, 2gb RAM Windows Home Server, Sage 7 beta 2 Hauppauge PVR-250, 1 PVR-500 MCE 1 HDHomeRun 4TB Storage, GB Network 2 MVPs, 1 HD100 & 1 HD300 |
#45
|
||||
|
||||
Quote:
Quote:
But even if we grant that the Sage devs are better qualified to do this kind of work (and it's not clear that they are), that doesn't mean it's the best use of their time. There are way more of us than there are of them. If some of us less-qualified folks can do some of the trial-and-error prototyping of new UI concepts, wouldn't that make the process of redesigning the stock UI more efficient if and when the Sage devs get around to it? Quote:
__________________
-- Greg |
#46
|
||||||||
|
||||||||
Quote:
Quote:
That they should all be in the same menu? Well then you have to go through two menues to get to everything (more "clicks" to get to the recordings which is the most commonly used function). That they should all be in the main menu? Well there's only so much room, what get's bumped? Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
And despite all the posts complaining about the navigation, I still don't know how people expect it to be. |
#47
|
|||||
|
|||||
Quote:
Quote:
And I said in the original post that the figure (10 widgets/day) was completely inaccurate. I also think from experience of developing with Studio, that 10 times faster than that (100 widgets/day or 1.5 man years) is much too little. (my rss newsreader contains 860 widgets -- it definately took more than 8 days to write), I would not be at all surprised, however, if MCE's UI took 15 man-years to develop if you consider the time needed to perform: Human interface studies prototyping trialling designing developing testing redesigning redeveloping retesting etc Quote:
Quote:
Quote:
(by the way, you do know that you can include archived videos with Sage recordings by changing the Sage Recordings filter?)
__________________
Check out my enhancements for Sage in the Sage Customisations and Sageplugins Wiki Last edited by nielm; 02-08-2007 at 02:00 AM. |
#48
|
||||
|
||||
Quote:
John |
#49
|
|||
|
|||
Quote:
It seems like there are a couple of long-time users who are "defending" the current interface. Goodspike compares it to WinDVD, and says it could be a lot worse. That imo is a completely wrong way to look at it. What one should compare it too, is the apps that are being praised for their nice looking UI's, such as Vista MCE. About the techies, vs non-techies discussion, i think it's wrong to say that just because you know your way around a computer, means that you're either not interested in the way your HTPC application look, or that you can just design or install your own skin. You have to actively look for STV's. My brother-in-law is a "semi" techie, and I've promised to help him build a HTPC. When i installed Sagetv and show him what it could do, he said; "yeah that looks good, but I'd much rather have the one you use." Needless to say, I use SageMC. I don't think Sage can afford not to prioritize their UI, because a lot of their potential customers will choose or dismiss the, based on it. And if I am going to spend $'s of dollars on hardware, and a nice looking TV, I don't want ruin it by running a frontend that looks like windows 3.1... |
#50
|
||||
|
||||
I think many of us can agree on one thing--we all want sage to grow. To grow, I mean sage needs to sell more licenses/hardware. For sage to sell more hardware, sage needs better publicity. For better publicity-sage needs better reviews. For better reviews sage needs to fix the one issue that every reviewer harps on = the UI. And i'm talking about looks/skins not really functionality. I am content on functionality through plugins. I think many new users would be content too out of the box if the UI was "slicker" looking. How many of us use sagemc over the stock. That should give you a good indication.
I can tell you that if I was starting over with today, i would be very tempted to go with vista and an xbox 360---because of the slick user interface. Many people starting out go with the 'eye candy'. Thats the way we work (at least i'm fairly superficial about stuff like that). When I show off sage to friends when they come over I don't go, "hey-check out how sage manages recording conflicts and how sage handles intelligent recordinds and X,Y,Z. I say, "doesn't this look nice! Isn't it smooth. See how cool the movietimes plugin is when set as a screensaver? dostn' that look good. (well, not exactly what i say but you get the point). Many new users or people looking into PVR's read the PC mags, read the reviews and go from there. I for one, started using sage right after v2 came out. I switched from Showshifter. Why? because sage looked so much better--better than BTV even. Showshifter was purple and ugly! I didn't even consider what functionality sage had. Anyway- a nicer, flashier UI = better reivews = more sales = faster production of an HD extender for us!
__________________
Server: Athlon 2000XP; 1GB Kingston Ram; 250GB Seagate; 160GB Seagate; 160GB Western Digital; Lite-on DVD player; Hauppauge Rosyln; Hauppauge PVR-150; ATI AIW 7500; Actisys 200L; running stock v5 .stv Client: MVP Extender running SageMC |
#51
|
||||
|
||||
Quote:
I personally think the kludgy add on for the music/pictures is horrible and does not fit into the Sage UI theme at all. What's up with all the crappy looking buttons on the left side of the screen? When I first saw that in the beta, I could not believe how ugly it was and figured that it would be fixed before it was released. This coming from someone whose wife won't allow SageMC in the house, but uses the stock UI only. |
#52
|
|||
|
|||
JUC has cut to the core issue - sales.
Why did Sage decide to charge for an upgrade to V6? Either they wanted more money, they needed more money, or felt that the "free upgrades for life" was economically unsustainable in the coming marketplace. Whichever choice you pick, it boils down to the fact that new sales were not producing the income they need or want. They had to go back and mine the existing customer base. That's a good short term solution, but it's not a sustainable bump in cash flow. The fact is, Sage doesn't have to please you or me - they already have the bulk of the money you or I will send to them. They have to please tomorrow's customer. And the customer after that, and the one after that, and so on. They need new customers and new sales. And they need them in a marketplace that has just been radically altered. With the release of Vista, you are going to start seeing MANY new turnkey DVR systems, and not just the ones that sell for $4K+. You will see a LOT of sub-$1000 systems on the market, and that's going to be the place where most new customers go. Sage has to either get to those customers before they buy something else, or offer a product that will change their mind after the fact and make them want to pay for new software. Is designing a new UI the best place for Sage's resources? Maybe. Is it in the top 3? Absolutely. Sage has already built just about the most technically sound and complete product on the market. Now it's time to position it so that it compete against Vista and Tivo et. al. in today's marketplace. Pleasing you and pleasing me was fine - yesterday. But for tomorrow Sage has to clean house, starting with the UI. Let me give you one example. 5309. Need I say more? Why, after 2 full versions, is this additional functionality hidden behind the "super secret hidden feature" code? I could see that for a test release, but this stuff is cooked. Put it into the normal configuration. That's exactly the type of thing I am talking about when I say the UI is cobbled together. Every time they added a feature, they had to figure out where to shoehorn it into the existing interface. Well, at version 6 it's time to sit down and think about the whole feature set and design a UI that fits the features, instead of fitting the features into the UI. Times have changed. It's going to be very hard to tempt people away from Vista's media center. That's because it comes in the box (with in-place upgrades), but most importantly it looks and works in such a way that the average windows user can "get it", without having to dig around in forums and install plugins. And if they put 15 man-years into their MCE UI design, it's because they kept putting it in front of potential users, asking "what do you think?", and taking the answers back to make it work/look/feel better for the users. Let me give you one last example. My wife and I will be going on vacation for a couple of weeks. We have a friend who house sits for us. He's been doing it just about as long as I have had SageTV. I have a Harmony 880 remote control, with pictures and one-step buttons to control my media center. He's been using my media center for a couple of years now. You know what he does when he house-sits? He watches Cable. Through the cable box. Because even with SageMC, using the HTPC is just too daunting for him, and he's always afraid he's going to "screw something up". That's the mentality that sage has to face, and why they need to redesign. They need to make it so simple, a cave-man could use it. Last edited by src666; 02-08-2007 at 07:58 AM. |
#53
|
|||
|
|||
And to put my money where my mouth is, here are a few things that I think need to change.
Archiving: What is archiving? In SageTV, it means "I want to keep this show, but remove it from the normal list of shows". To most people I have talked to, it should mean "I want to keep this show, but I want to move it off the drive". Archiving should mean something more than a flag, or at least have the option to. You should be able to specify an archive drive that the show gets moved to, or have it compress the show, or burn it off to DVD. When I archive something, I _put it away somewhere else_. I don't just cover the label with a post-it and leave it where it is. Multiple-watcher support: My ReplayTV's understood (to a degree) that there were probably multiple people in the house. When I started watching a show on the ReplayTV in my living room, it knew that at an earlier time someone watched, but didn't finish, that show in the bedroom, and it offered me a choice of where to start playback. Sage needs to "get" the fact that there are multiple viewers in the household, and they have their own schedules and their own lives. Replay's location dependent playback logging was a good start, but Sage needs to have a way to let me know that we have a new episode of Heros that I haven't seen yet, but my wife has already watched it. That way I know I can go ahead and watch it alone guilt-free, instead of waiting 2 weeks to find out she has seen it. Perhaps a modified watched flag, that says "this has been watched, but don't take it off of the unwatched list". That way you can at least see that the new show is there, and that someone has watched it. Multiple-library support, or parental controls: We need a way to make sure that the kids only see and record programming from channels that parents approve of. This needs to be integrated into the UI in a way that makes it possible to restrict some playback devices (i.e. the extender in the kid's room) to certain content. My idea is setting up a second SageTV server that only has the channel lineup the parents want, and the kids can record/watch what they want on it. But this breaks down because the moment the kids walk downstairs to the family room, all of their programs disappear. The main SageTV server has no idea what the kid's server has done. It would be nice to have a way for one server to have access to another's data, without making it a two-way street. That way the main system can play anything, but the kid's system only has access to the kid's shows. Just a few ideas. That last one has little to do with the UI, but it would make a very marketable difference. Edit: In retrospect, I see that this list has nothing to do with the discussion at hand. These are all new features that would have to be included in the interface, not really improvements to the existing interface. They add no value to the discussion. The first thing I would fix in the interface is the video library. Recorded shows, archived shows and imported video shouldn't be separated. As was mentioned by someone else, you can include archived shows in the normal list, but if I recall correctly that's either part of the "super secret hidden features" or part of an import. I'm sure someone will correct me if I'm wrong about that. There is no reason you can use filtering to integrate these items into a unified interface. SageMC has a set of fairly useful filters in the recorded shows menu, and this can be extended to include more. One key element is that Sage really needs another way to get metadata _into_ the system. I should be able to put enough data in about an imported file for Sage to toss it into the list with all the recorded shows. For example, 2 weeks ago the cable company screwed up and Battlestar was nothing but macroblocks. So I found a replacement file, tossed it onto the system, and now it lives out in the Imported Media space. That's fine for me - I put it there. But it does no one else in the house any good. I should be able to tell sage that the file belongs with all the other Battlestar shows. Ideally, I would be able to tell sage to substitute the good file for the bad one, so that the new file has all of the old file's metadata. A media center should pull things together, not keep them apart. Allow us to categorize, to modify the metadata, to organize - that would be a useful UI change. Last edited by src666; 02-08-2007 at 08:43 AM. |
#54
|
|||
|
|||
Quote:
Quite a few people have been making this very simplistic argument. I'm not picking on you or anyone in particular. Any businessman should ask how much time and cost will be involved in overhauling the UI? How much sales growth will it generate? What features will be delayed due to the diversion of resources? Will the overhauled UI generate more sales than the features being delayed? These are just a few of the questions the company would need to answer before making a decision. None of us are in a position to answer these questions. For example would a slicker UI or a HD extender generate more sales and publicity for Sage? If you had to choose between your developers working on a new UI or a HD extender which project would be in the best interest of Sage to complete first? None of us can even begin to give an educated answer. All of us would be giving opinions and guesses. I think most everyone would agree that nicer eye candy would increase sales and publicity and needs to be addressed. The question is whether adding eye candy would yield better results than the projects the company is currently devoting its resources to. |
#55
|
||||
|
||||
Quote:
Is there a way to have Sage start on the Sage Recordings page? Thats where I want to go 99.9% of the time I start Sage, but I've never found a way to do that. There very well may be a way to do that, but it's not in detailed setup, where you'd expect it. Rather than calling SageTV ugly, I would say it's not terribly intuitive about many things--like the tip above, or those icons that appear on the TV schedule which mean nothing obvious.. To do basic things, you shouldn't have to RTFM. |
#56
|
||||
|
||||
Quote:
|
#57
|
||||
|
||||
Quote:
Quote:
Quote:
Quote:
Business isn't just about sales it's about profit margins. The bottom line is Sage will most likely never be the market leader. Their best chance is to differentiate their product by offering features not available from MS while maintaining a healthy profit margin. If not they'll be driven out of business. I agree a nicer UI would be a plus, but at the same time I realize there is no free lunch. If resources are devoted to the task they're being taken away from another project. That's one reason why I think the UI should be ever evolving and not scrapped in order to build a new one from scratch. Last edited by blade; 02-08-2007 at 09:29 AM. |
#58
|
|||
|
|||
I for one sure hope sage finishes the HD extender before trying to figure out what ugly, eye candy, poorly layed out and all the other generic statements mean.
|
#59
|
|||
|
|||
Quote:
Now, we honestly have no idea if this was a one time thing, or if every version upgrade will incur an additional charge. But until now they have been able to play fast and loose with their versioning, with many bug fixes being rolled into the next version and everyone upgrading because it was free. You start charging for upgrades, and you are going to start leaving some portion of your customer base behind. Period. They are going to have to start doing a better job of code management, fixing V6 bugs in V6 releases, instead of just rolling them into V7 and charging everyone [insert some dollar figure here]. We've already seen this happening, and a number of users were complaining about having to pay for V6 to fix V5 bugs. I can almost guarantee that they agonized over the decision to charge for upgrades to V6, and that they did it for a better reason than "everyone else is doing it". SageTV is NOT an "everyone else is doing it" company, or at least hasn't been one in the past. Like you said - profit. I'm not saying that they are "in trouble", but they are certainly playing in a different marketplace than they were a year ago and the reality of that situation cannot be lost on them. If they sell an average of 1 server, 1 client (PC/MVP/Placeshifter) per "user", then they are looking at about $120 per sale. Unless they are just a couple guys in a garage, then they need several hundred NEW sales per month to stay afloat. Heck, even a couple guys in a garage will find it challenging to run a long-term company on less than that. They charged for upgrades because they need the money, either now (decreased sales/increased expenses) or anticipate needing it later (preparing us to expect upgrade charges in the future). And the best way to increase revenue is to increase sales (obviously, without increasing the cost of a sale or reducing the income from a sale). They need to be able to compete with the products in the market today. They need to have a new user look at the system and say "Yes, that's it!". They need to ensure that the user experience is good enough that the non-geeks in the family accept it without a struggle. Otherwise, they won't be able to grow their market, and they will be stuck living off of what they can get from you and me for the next upgrade. |
#60
|
||||
|
||||
Quote:
|
Currently Active Users Viewing This Thread: 2 (0 members and 2 guests) | |
|
|