On Sat, 2006-12-30 at 17:55 +0100, Dirk Meyer wrote: > Well, for fb Display == Window. But I guess it should be possible. Not > sure about other displays. What happens if you play a movie on a > buffercanvas. Is it possible to get the real display size?
For BufferCanvas, it should assume 1:1, because any display aspect corrections will be done by evas itself, and should not be compensated in kaa.popcorn. (Evas can do this correction by setting the output size to be different than the viewport size.) > So what should it be? Pixel-aspect-ratio or monitor-aspect? We could > do both (more or less). We could set the default pixel-aspect-ratio > based on the monitor aspect if provided in the config. Sure, that'd be fine. Provide display-aspect-ratio and display-pixel-aspect-ratio properties, which essentially correspond to mplayer's -monitoraspect and -monitorpixelaspect options. The user would probably normally only specify display-aspect-ratio, but can specify the pixel aspect directly if there is some weird custom setup happening. > What about osd? If the sizes always change between freevo and the > movies, we have to use per centage and not pixels in the gui. I plan > to do this anyway, but it has to be that way in that case. BTW, what Yes, it has always been my expectation that we would be using relative values, and you're right, it'd be necessary in this case because the OSD size is variable. > happens if you have a movie with 480x480 (SVCD, DVD has similar > problems) and it is scaled based on the aspect? Should be also create > an osd in 480x480 with the same aspect and let the hardware scaler > correct it? What happens if the movie aspect changes (possible for > DVD)? The pixel width and height are still the same, but the osd needs > to be drawn differently. The OSD is always 1:1 pixels, no exceptions. The frame size for NTSC DVD is 720x480 which gets hardware-scaled to 854x480. The OSD size is then 854x480. vf_overlay will do the appropriate scaling to make sure the aspect is handled properly. For mplayer, vf_overlay uses swscaler to scale the OSD onto the 720x480 frame; for xine, it will use evas to do the scaling (output size is set to the frame size, whereas the viewport size is set to the post-scaled resolution). Evas's output scaler isn't very good though (looks like nearest neighbour), so the ultimate goal is to get swscaler in xine-lib and use swscaler in the kaa driver to scale the overlay as it currently does with vf_overlay in mplayer. In any case, the bottom line is that for OSD, we see it as a canvas that has 1:1 pixels, and the canvas size is the post-scaled resolution (854x480 in the case of NTSC DVD), and any aspect correction to compensate for non-square pixels happens at a layer beneath that so we don't worry about it. Hope that made sense. Jason. ------------------------------------------------------------------------- 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 Freevo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freevo-devel
