> That's great. I also know GeeXboX for some time and looked at > screenshots and the feature list for time to time. But I never tried > it.
All projects know about each other while barely having a try at others. This is quite similar everywhere ;-) > That sounds great. Two good things can come out of this for Freevo: > first of all, we will hve a LiveCD and second, I hope you can also > contribute code. :) So yes, I really like that idea. There'd be pro for both projects imho. First would be advertisement of course, as projects are more binded and that way much more known, which is primary target for ruling the world ;-) Then, just to let you know (and others), GeeXboX currently is a minimalistic media center. We only use Shell scripts and C programs and everything is done with these langages. We also are dealing with uClibc in order to strip everything down to a 6-7 MB ISO. Adding Python and all related stuff will take us a bit of time as unfortunately few people only from my team have a Python knowledge (time to enhance our skills too :-) So your team might of course help mine to have the basic steps done. Then, about Freevo itself, as you said, 2 things will probably come out: - official Live-Cd, as I've said, that's primary goal - have help from some of my team members to extend Freevo capabilities whn possible. More than just packaging, we've been hacking a lot on vanilla MPlayer for example over past years and many features now existing in FFMpeg/MPlayer came from some GeeXboX devs. So you might expect the same to happen to Freevo (once we'll have learned Python of course :) As I already said, I'm already skilled enough in all EVAS related stuff, it's just a matter of pythonyzing my knowledge ;-) > Freevo 1.6 works without X. I had it running (ok, I had 1.5.x running > before moving to SVN) and it works at least for Matrox G400 > framebuffer. That's good to hear. For now, we'll use Freevo 1.6 in order to start supporting Python and so on. We'll switch to Freevo2 later on with an optional support for X.org in GeeXboX some day in the future, as it seems to me as the only way to get decent perfs to decode HDTV movies (but that's another story). > As written by Jason: we need two patches in mplayer: the first one > (the important one) is to draw on top of mplayer. And we don't want to > use bmovl because it is way to slow. All communication is done using a > pipe and you can't do animations on top of mplayer. So Jason from a > patch that is not in mplayer yet. The other patch is that we want to > output mplayer to a buffer so we can show the video in a small video. Yeah, I'm aware of all of Jason's patches and efforts to both MPlayer and Xine dev lists ;-) Most MPlayer devs are lazy guys though and patches need to be pushed a bit more to get included :-( I'll try my best on that with Jason's help if needed. > That is 2.0, not 1.6. The 1.6 release doesn't use kaa at all. And it > looks like you want to output an an X11 window with X11 support in > kaa.display. Yeah I know, it was just to have a try at 2.0 release. > Evas has several backends, including framebuffer. Jason wrote an evas > wrapper (kaa.evas) and we use kaa.display to get a window to draw > to. With window we also mean DirectFB windows and the framebuffer > screen. And evas can also output to a memory buffer so you could use > evas on top of mplayer or xine. Or you can render into a mpeg file and > play the gui. Some guy from my team patched Evas a year ago to add support for VESA and VIDIX output btw, if it might be useful for someone (was just a tryout though). > BTW, since you are a mplayer developer: do you think it will ever be > possible to change at least some parts of the filter chain during > runtime? It would be nice to turn on/off deinterlacing while playing. I guess it'd be possible. I'd like to extend MPlayer slave mode as much as possible (and maybe some day make libmplayer on top of it for easier use) for such things to be possbile (like dynamic changes/control). > If you have any questions, use this list or you can also find us at > #freevo on irc.gnu.org. Same for us on #geexbox on freenode. Maybe we can have an IRC chat between freevo and geexbox devels some day around. > I hope for a good partnership, Yeah, so do I ;-) At least I'm feeling much more confortable with my new choice of using Freevo from now on. Ben ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Freevo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freevo-devel
