Axatax_ wrote:I don't think I ever posted a patch for the "beta" Mplayer I sent up. It's newer than what's in Neko maninline but probably older than current official Mplayer.
LMK if you're still interested. I have to set the Octane back up but that's not a big deal. Like alot of people life (my first kid) got in the way...
Gracious moochy Mr Ax .... that'd be super. Almost to the point of having the nekoware source build - a couple of little things in configure, a couple of missing header files, and now a linking problem, but close.
I figure after people can just pull the existing source and it builds outta the box, then can move the lever to first. No point in duplicating the dumbshit stuff.
vishnu wrote:I'll grab it and have a look at it, it's going to be a challenge because the supposedly modern version of mplayer that I've got on my Linux box links against
eighty four system libraries!
Yes, some of that stuff really doesn't have to happen if you make source for a single operating system. I don't think we need all that stuff to support JACK, for instance. And I notice that, at least in some cases, even a --disable-soandso directive doesn't actually disable those features. They don't work, of course, but it still tries to build the stuff. (Not JACK, this was iconv). And ditching gtk2 is a for-sure goal. Why would they insist on gtk2 for a command-line app ? Sheesh
Update: got this hummer to build without needing any trickeries, so in the next couple days will set up a base repository. Then you guys can have at it cuz I sure as heck don't know what I'm doing
Just to confirm, running a test of the freshly-built mplayer 1 rc 1, in top it shows two threads, one running at about 20% cpu and one at .2% cpu, on a 2p Octane. So if the Octane is "not capable of handling the heavy loads of modern codecs", well, them codecs aren't trying very hard. There's lots of cpu available to use.
