jaromanda wrote:I never said "GUI responsiveness will always be slower" as a standalone statement
as raspbmc was the last to use 720p UI, and given that all 3 distros use the same XBMC (close enough), then it's obvious that WHILE YOU BUCKED AGAINST the 720p UI and stayed with 1080p UI, your UI would always be slower - you can not refute this assertion - besides, you now offer 540p UI, so, you've seen the benefit of the lower res UI for responsiveness - hence my cynicism
As I said, while 720p capping does give a performance gain it also restricts the user. Raspbmc is now the only distribution that lets you toggle 720p/1080p as the menu resolution. I have reverted the 540p patch back to 720p as the extra FPS are unnecessary
I never tried to start arguments ... but while BrianM was treating me like a complete idiot, just because he's been Moss for 30+ years, you seemed to miss the point on several occasions that there was NO LOG FILE created by the isntaller - clearly, you were not reading what I wrote, but assumed I couldn't follow the simple steps for installing raspbmc
Comparing him to a fictional character does not help matters much. Yes, I see, no log file was created. Not the easiest thing to diagnose without TV output either, but I'm willing to give it a shot, and if you use your DVI cable we can get some output and I can resolve any issues that you are experiencing.
I did follow them, to the letter ... it booted, it downloaded the real raspbmc image, and THEN it failed ... this is BEYOND my control, there is no user interaction at this point
I do not believe the issue in this instance is user error.
as far as the glacial development ... I stand by that, compared to openelec (but not xbian) - every time I visited your website, things were "coming soon", but never arrived (I'm talking when I made the glacial comment, things have changed since then)
You are entitled to your opinion but I can't agree with it. Raspbmc was the first distribution to get PVR support -- even before the opdenkamp/mainline merger, as I merged it into the mainline branch. It got codec support pretty much the day after it came out. Raspbmc releases are generally quite slow in cycle time -- but as I always say, I'm a fan of not releasing early and releasing often.
you don't like your packaging of raspbian + xbmc negatively commented about .... tough ... there will always be fanbois of other distros that will take a dump on what they don't use
Granted -- not everyone likes one particular distro, that's why all the other ones exist. It's about the user using what is best for them.
I said on your forum that, by all accounts (of your fanbois, perhaps) that raspbmc is the best of both worlds, the flexibility of xbian with almost the stability of openelec, and I'm keen to get the damned thing working ... but ... your fanbois make it difficult to get support, because they just asume, because t works for them, it should just work for anyone
That is I admit, a bad assumption. Chalking up to user error is often the easiest way of denying a problem. But without visual output or a log (not your fault about the log it seems), there is little anyone can chime in to assist.
and I am NOT the only person to have the problem I described ... search this forum, you'll see there is one other who described the same issue - but perhaps there are more with the same issue, but don't want to post on your forum for help, because of the way your fanbois come in and attack, rather than try to help
This issue was common in September when we hada mirroring issue but as they are all resolved the issue seems to have faded