• 1
  • 2(current)
  • 3
  • 4
  • 5
  • 7
Raspbmc - XBMC Linux distribution for Raspberry Pi
#16
magao Wrote:Not intentionally - I've just edited my post with my better understanding of the context in which the comments were made (unfortunately, you were too quick to respond ...).

Lol! Yeah, too much heat and light over this! I'm personally gonna try out Sam's, try out whatever OpenELEC throw's out and have a bash at my own. The last option will be where all the fun is!
Reply
#17
I for one enjoy the possiblity to extend and modify the setup myself. That is what I have loved about Live.
If it is not based on ubuntu, what is it based on? Is it still debian & apt based?

EDIT: I understand it does not have to based on anything but what ever base linux is called, my question is: Are we talking access to standard repo/app centers, compiling from source or some sort of plug-in system?
Reply
#18
Jimmer Wrote:You are quoting him discussing the performance of Crystalbuntu on ATV. On this specialist platform, IT IS more stable and responsive when it comes to media playback.

He's not saying crystalbuntu is more stable and responsive on all platforms that OpenELEC is found on. That would just be plain wrong. Crystalbuntu is a single platform distro, and on that platform it is the BEST distro for the general user. Show me a better one, please.

You have set yourself up a straw-man to knock down here.....

..although, I will agree with you that the tone is unfortunate. There's obviously some history there. My X is better then your Y is never helpful and frequently harmful.....

Thanks Jimmer for explaining a few things there. I am sorry if the tone seems off in saying Crystalbuntu > openELEC but in terms of performance, stability and in my opinion design philosophy, I think it is the better bet. But this is a major digression.

Despite openELEC's differences, what I feel is sometimes a rude development team, there are some admirations. This would be how minimal the distro is, albeit at loss of expansibility. Whether they use uclibc I do not know but I remember seeing an openELEC dev striving for compiling XBMC with uclibc and I admired this greatly.

vikjon0 Wrote:I for one enjoy the possiblity to extend and modify the setup myself. That is what I have loved about Live.
If it is not based on ubuntu, what is it based on? Is it still debian & apt based?

EDIT: I understand it does not have to based on anything but what ever base linux is called, my question is: Are we talking access to standard repo/app centers, compiling from source or some sort of plug-in system?

Debian based -- Canonical have given up on ARM.

Yes, it will be appliance based in the sense that, you'll have a easy installer, and if you wish, you'll never have to mess with CLI or any of that. It will auto-update and run smooth as silk without any know how.

But no it's not an appliance in terms of expansion. As a Debian base it will basically allow you to install anything you can think of.

It's the best of both worlds.
Reply
#19
Quote:As a Debian base it will basically allow you to install anything you can think of
That sounds great!
(We have to separate appliance as in "no deskop behind xbmc" and appliance as in "do not touch" I see a point with both ideas. E.g. if you want to sell and support a top box...)
Reply
#20
Sam, this sounds superb.

Crtystalbuntu on my atv1 is just excellent - the installation method and autoupdates are spot on, if this is applied to the raspberry pi it really will be something else.
Reply
#21
Thanks for making the distinction between what you're doing Sam and an Openelec vector. I've played with Openelec, and it definitely has its niche, and if the Openelec team wants to pursue development on the RPi, more power to them.

I, for one, don't care for Openelec as a PC option because of the lack of custom driver support. I have a motherboard with a Realtek NIC PHY that doesn't work as well as it could because of the most current driver not being the best for this particular PHY. The problem is easily fixed by using an older driver. Because drivers compiled into the kernel of Openelec, the problem is not fixable unless you compile it yourself. Such is the caveat of an "appliance-only" type of build where the hardware is not also controlled. I've mentioned this problem on the Openelec boards, others have chimed in as having the same issue, and it died on the vine due to lack of dev interest.

Crystalbuntu, OTOH, allows extensibility of the underlying OS. This allows for growth and modification well beyond the scale of Openelec, even though the hardware platform is pretty much static. All of that is open to the user through an SSH session, or dropping to a terminal, but the user doesn't have to do this if they so desire. Crystalbuntu autoupdates and "Just Works©". It's this approach, IMO, that will allow for a RaspberryPi development of XBMC to flourish.

I'm also sure that there will eventually be something similar to Openelec on the RPi, and I think there will be people that use it and like it. Both implementations have their respective advantages and problems, as well as their own audiences.
Reply
#22
Sam.Nazarko Wrote:Debian based -- Canonical have given up on ARM.

That's not strictly true - Canonical have merely ended support of the older ARMv6 architecture on which the Raspberry Pi ARM11 SoC is based. Canonical continue to support ARMv7 (Cortex-A8 etc.).

Bug about it here.

Re: OpenELEC developers - I doubt they'd be able to get a stable release out for the Pi in a month of Sundays, their release procedures are laughable. Going through the v1.0 Release Candidate process with them was painful enough, I don't think they even know what RC means, they kept making major changes from one RC to the next and breaking what was previously working functionality. Rank amateurs IMHO. Well intentioned, but amateurs. And yes, very rude - they won't accept they're wrong or that they can do things better. /rant
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.
Reply
#23
MilhouseVH Wrote:Re: OpenELEC developers - I doubt they'd be able to get a stable release out for the Pi in a month of Sundays, their release procedures are laughable. Going through the v1.0 Release Candidate process with them was painful enough, I don't think they even know what RC means, they kept making major changes from one RC to the next and breaking what was previously working functionality. Rank amateurs IMHO. Well intentioned, but amateurs. And yes, very rude - they won't accept they're wrong or that they can do things better. /rant

Code welcome.
Reply
#24
natethomas Wrote:Code welcome.

Sometimes it's not about code, but process. And it's difficult to improve a process when the people behind it won't admit or acknowledge there's even a problem.

Releasing six v1.0 RC's based on Dharma code - more than a few of which introduced major and unnecessary regressions - then suggesting the first v1.0 release would actually be based on Eden not Dharma (which is what had been tested up to that point) is hardly the sign of good process. It was infuriating. And as a professional software developer by trade, embarrassing.
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.
Reply
#25
This is great news, I was very impressed with your Crystalbuntu so thanks for doing this with the R-Pi Sam.
Reply
#26
hmmm....this thread is full of anger, and I came here for information, release dates, progress updates....
Reply
#27
oneadvent Wrote:hmmm....this thread is full of anger, and I came here for information, release dates, progress updates....

Definitely not anger (at least not on my part) - just opinions (borne out of frustration). Maybe it's all OT, but IMHO it does add some additional colour as to why going with OpenELEC may not have been the best option, even though on the surface it may have been the obvious choice.

On topic: Probably a little early for release dates considering the hardware isn't yet on sale.
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.
Reply
#28
Quote:Definitely not anger (at least not on my part)
Either way drop the discussion about other solutions in this thread.
Reply
#29
Do we have a working copy though?
Reply
#30
One more thing: I noticed here: http://www.stmlabs.com/2012/01/30/raspbm...spberrypi/

that multixbmc setups were mentioned and I think that can be the big push for this device. It is so cheap to wire the whole house up. Do you think that it will be capable of recording in 1080i with tvheadend? I would think that is pretty processor heavy. I currently use the hdhomerun and there are some custom kernel requirements for that too.
Reply
  • 1
  • 2(current)
  • 3
  • 4
  • 5
  • 7

Logout Mark Read Team Forum Stats Members Help
Raspbmc - XBMC Linux distribution for Raspberry Pi7