Who says you have to use all the pieces? You'd also need include all the other sizes that one could produce with few pieces (and then the selection of that subset of pieces...
Given that the mother project (XBMC) also switched to DirectX on win32 this is no surprise. It makes sense too - on Windows, you get much easier hardware acceleration of videos if you're using DirectX (i.e. you can get a DirectX surface out easier)
You also tend to get better hardware support.
It appears the Boxee gues worked with the XBMC team on this - kudos. Let's hope the boxee box is open enough to get XBMC on there.
XBMC will do it (has done for 5 years now)
on
VLC 1.0.0 Released
·
· Score: 1
Just use XBMC - plays back from multi-RARs or multi-ZIPs, assuming they're stored. Even if they're compressed (which would be silly) it'll uncompress and play 'em for ya.
Any format that VLC does, it'll do (i.e. it uses FFMpeg as well).
Why multi-part rars? Obvious reason is distribution is easier through multiple channels, and it contains it's own checksum. A better reason is: Why not?
Ignoring the fact that this "news" is just blog-generated rubbish, personally I'd be quite happy to pay for a streaming service, under the assumption that we had the connection speeds to give suitable content.
720p h264 at 6Mbit (maybe 5Mbit if they really have to stretch it) with AC3 sound, and an open protocol, and that'll be just fine. You need a pretty damn good connection to ensure you get it without problems. The current stuff they have is ridiculously rubbish quality in comparison.
Given that the net connections aren't at that level yet, and likely won't be for a while, I'd also be quite happy with downloads - 6Mbit for 720p or 12Mbit for 1080p. Allow me to download in an open container (mkv is fine) and I'll be quite happy to pay the current going rate for Bluray pricing per season (even without all the extras), for the convenience of not having to rip it myself.
Actually, I'd wager _more_ than half of the population fall below the mean intelligence level. Intelligence certainly appears to be skewed to the right after all.
The Boxee client for the most part is opensource (being based on the GPL'd XBMC http://xbmc.org/, it has to be). However, the part of Boxee that handles Hulu, Netflix and the like is NOT open source. Instead, the Boxee client loads a proprietary, closed-source executable that then loads the Firefox flash or silverlight plugins.
Encourage Boxee to open things up - it's clear that they're not gaining anything by having this stuff closed off.
Boxee uses the adobe flash plugin for firefox already. Unfortunately, the loader application they use which interfaces between Boxee and the flash plugin is closed source. That's right: They took a completely open piece of software (XBMC) and added extras to it that were closed off. They get away with this by making it a separate app so that there's some semblance of separation. This should be a lesson to them: Close stuff off to try and get on the good side of content providers, and get screwed over. If they'd opened it up from the start, in the spirit of the codebase on which they rely, we wouldn't be in this situation, as the horse has bolted. As it is now, Boxee will likely still work with Hulu - it'll be switched off in a trivial manner from within the boxee codebase. Unfortunately, I suspect building boxee from source is a non-trivial exercise, given that it's not really an opensource project.
Depending on how Play On operates it may be affected by this as well. If it operates the same as Boxee did (basically using the firefox flash plugin) then it'll probably still work just fine. Boxee will likely still work just fine as well - they're taking it out because they're in the uncomfortable position of having to bend over backwards to the content providers.
Boxee could have avoided all of this by simply remaining completely opensource. The code would have still been available to anyone to use. Unfortunately they decided to close this off, and now not only are they bitten by this, but there users are as well.
The same will happen to Plex unless they open their codebase up. They've complained about the fact that Boxee's flash implementation wasn't open - let's see whether there's is (the Media Server thing they have certainly isn't open).
I'll stick with completely open software thanks very much.
Where is this "trashing of reputation"? Seems to me all this "Cyberace1/Gamester" fellow (who appears to be a project manager, rather than a "core developer") was clarifying the OP's comments WRT the origins of Plex. There was no "trashing of reputation" in his post, rather a misspelling of Elan's surname.
Nice spin attempt though.
A quick check of the plex git shows that 95% of the commits originate in the XBMC source tree. I'd personally rather let the devs doing the work know directly about any issues rather than rely on a middle man. After all, improving XBMC means users on other platforms benefit as well. Do the plex devs push their changes upstream to XBMC in any active way, or do they just do their own thing?
A quick look at the installer shows that it's only really there to wrap the DMG to run a couple of post install scripts to setup the app for the user's environment (sources.xml etc.). There doesn't seem to be any other reason than that that I can see. If you can suggest an alternative (something within the binary itself to do this at first boot?), perhaps you could notify the devs over at XBMC?
Actually, they didn't profit from the iPod collaboration at all - all moneys were donated to charity, as can be discovered from a simple websearch (check their rock and roll hall of fame induction for instance).
As to whether or not Bono helps the less fortunate, surely that's between him and his bank manager? Whether or not he advertises what he personally donates does not diminish the message in any way.
I have no comment regarding their tax dealings.
Slashdot Mirror
Who says you have to use all the pieces? You'd also need include all the other sizes that one could produce with few pieces (and then the selection of that subset of pieces...
Given that the mother project (XBMC) also switched to DirectX on win32 this is no surprise. It makes sense too - on Windows, you get much easier hardware acceleration of videos if you're using DirectX (i.e. you can get a DirectX surface out easier) You also tend to get better hardware support. It appears the Boxee gues worked with the XBMC team on this - kudos. Let's hope the boxee box is open enough to get XBMC on there.
Just use XBMC - plays back from multi-RARs or multi-ZIPs, assuming they're stored. Even if they're compressed (which would be silly) it'll uncompress and play 'em for ya. Any format that VLC does, it'll do (i.e. it uses FFMpeg as well). Why multi-part rars? Obvious reason is distribution is easier through multiple channels, and it contains it's own checksum. A better reason is: Why not?
Ignoring the fact that this "news" is just blog-generated rubbish, personally I'd be quite happy to pay for a streaming service, under the assumption that we had the connection speeds to give suitable content. 720p h264 at 6Mbit (maybe 5Mbit if they really have to stretch it) with AC3 sound, and an open protocol, and that'll be just fine. You need a pretty damn good connection to ensure you get it without problems. The current stuff they have is ridiculously rubbish quality in comparison. Given that the net connections aren't at that level yet, and likely won't be for a while, I'd also be quite happy with downloads - 6Mbit for 720p or 12Mbit for 1080p. Allow me to download in an open container (mkv is fine) and I'll be quite happy to pay the current going rate for Bluray pricing per season (even without all the extras), for the convenience of not having to rip it myself.
Actually, I'd wager _more_ than half of the population fall below the mean intelligence level. Intelligence certainly appears to be skewed to the right after all.
The Boxee client for the most part is opensource (being based on the GPL'd XBMC http://xbmc.org/, it has to be). However, the part of Boxee that handles Hulu, Netflix and the like is NOT open source. Instead, the Boxee client loads a proprietary, closed-source executable that then loads the Firefox flash or silverlight plugins. Encourage Boxee to open things up - it's clear that they're not gaining anything by having this stuff closed off.
Boxee uses the adobe flash plugin for firefox already. Unfortunately, the loader application they use which interfaces between Boxee and the flash plugin is closed source. That's right: They took a completely open piece of software (XBMC) and added extras to it that were closed off. They get away with this by making it a separate app so that there's some semblance of separation. This should be a lesson to them: Close stuff off to try and get on the good side of content providers, and get screwed over. If they'd opened it up from the start, in the spirit of the codebase on which they rely, we wouldn't be in this situation, as the horse has bolted. As it is now, Boxee will likely still work with Hulu - it'll be switched off in a trivial manner from within the boxee codebase. Unfortunately, I suspect building boxee from source is a non-trivial exercise, given that it's not really an opensource project.
Depending on how Play On operates it may be affected by this as well. If it operates the same as Boxee did (basically using the firefox flash plugin) then it'll probably still work just fine. Boxee will likely still work just fine as well - they're taking it out because they're in the uncomfortable position of having to bend over backwards to the content providers. Boxee could have avoided all of this by simply remaining completely opensource. The code would have still been available to anyone to use. Unfortunately they decided to close this off, and now not only are they bitten by this, but there users are as well. The same will happen to Plex unless they open their codebase up. They've complained about the fact that Boxee's flash implementation wasn't open - let's see whether there's is (the Media Server thing they have certainly isn't open). I'll stick with completely open software thanks very much.
Where is this "trashing of reputation"? Seems to me all this "Cyberace1/Gamester" fellow (who appears to be a project manager, rather than a "core developer") was clarifying the OP's comments WRT the origins of Plex. There was no "trashing of reputation" in his post, rather a misspelling of Elan's surname. Nice spin attempt though.
A quick check of the plex git shows that 95% of the commits originate in the XBMC source tree. I'd personally rather let the devs doing the work know directly about any issues rather than rely on a middle man. After all, improving XBMC means users on other platforms benefit as well. Do the plex devs push their changes upstream to XBMC in any active way, or do they just do their own thing?
A quick look at the installer shows that it's only really there to wrap the DMG to run a couple of post install scripts to setup the app for the user's environment (sources.xml etc.). There doesn't seem to be any other reason than that that I can see. If you can suggest an alternative (something within the binary itself to do this at first boot?), perhaps you could notify the devs over at XBMC?
... ; that the use of semicolons is ill-advised.
I take my hat off to you good sir, for sneaking in that nice little amusement.
Actually, they didn't profit from the iPod collaboration at all - all moneys were donated to charity, as can be discovered from a simple websearch (check their rock and roll hall of fame induction for instance). As to whether or not Bono helps the less fortunate, surely that's between him and his bank manager? Whether or not he advertises what he personally donates does not diminish the message in any way. I have no comment regarding their tax dealings.