On Mon, Feb 26, 2007 at 11:39:14AM +0100, Robert Millan [ackstorm] wrote: > > On Mon, Feb 26, 2007 at 11:09:06AM +0100, Diego Biurrun wrote: > > > It was my understanding that hardware scaling is necessary for _slow_ > > > machines, not fast ones. But you seem to contradict that. Please can > > > you explain? > > > > Hardware scaling is not for slow machines. Hardware scaling is simply > > the faster way to scale. Not supporting hardware scaling amounts to not > > having fullscreen playback on moderately fast or slow machines that > > could otherwise perfectly handle the load and needlessly burning CPU > > cycles on fast ones. > > > > If your machine is fast enough, go ahead, add vo=x11 to your > > configuration file. But using this as a package default is going to do > > a lot of damage for almost everybody else. Not to mention that the -zoom > > option is necessary to get scaling at all then. > > Why a lot of damage? How many machines are too slow for software scaling?
I would guess about 80% of all the machines out there. You know, not everybody has a machine fast enough to run Beryl or can afford one. All machines below 2GHz I would guess, this excludes every non-x86 right away. My last generation PowerBook is not fast enough, even for a video of moderate size. When the machine is too slow to scale the video, video and audio go out of sync and the movie becomes unwatchable. I would guess the number of people taking screenshots at all is in the low one-digit percent of the users of MPlayer. It's not unreasonable at all to expect them to take appropriate measures. The situation is the same for all other multimedia players, btw. Does this give you an idea how much damage such a change would do? > OTOH, the power user who is compiling things and running boinc will > have an idea how to tune up her mplayer. This power user should also have an idea how to read an FAQ or a man page. Taking screenshots is explained there. > > > Sorry, I didn't explain well. I _can_ take screenshots, it's just that > > > the video is displayed blue. This is not a Beryl bug, it'll happen to > > > everything that captures the X display. > > > > > > See attached screenshots. In one of them, video appears to be completely > > > blue, but in the real screen I see the video in 2D. I.e. as if after > > > rotating the display the video was inserted only in the blue part (without > > > rotation). > > > > I perfectly understood what you were referring to. I'm well familiar > > with this effect. This is because X does not handle the overlay video > > memory directly. Now why don't you try the screenshot filter as I > > suggested? > > That's a workaround. For plain screenshots it'd be enough to enable this > workaround by default. > > For Beryl, we would need another workaround, and presumably a more complicated > one. We shouldn't assume that is even possible to do that sanely. This is not a workaround, this is the only feasible solution. Now would you please try it? I feel extremely silly discussing this proposition at all. Broken distro packages defaulting to the x11 video output driver was the #1 source of complaints about MPlayer upstream. Needless to say, it was all blamed on us instead of on the packagers. I have single-handedly reviewed several distro packages and talked to the packagers to make them avoid this dreadful mistake. Now please stop insisting on this insanity, thank you very much. Diego -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
